Akonadi's unix sockets location
 

https://bugs.kde.org/show_bug.cgi?id=179006#c5
> in the current version of Akonadi server you can specify a custom
> socket path by entering
>
> [Connection]
> SocketDirectory=/tmp/akonadi-myuser/
>
> into $HOME/.config/akonadi/akonadiserverrc

How about setting that as default, away from $HOME that can be a NFS
filesystem? I have had problems with it sometimes and that's
probably not a rare case.

Just to avoid problems if locking, whatever doesn't work correctly
in that particular server.

I can't imagine what harm that would cause to default under /tmp?

Of course, that posting refers to 'current' which may not be the
version in Fedora, so this should be planned for future releases.


Tuju

--
You want to throw out the baby with the bathwater! - K. Kofler
Your baby is my bathwater. I don't want the OS you're building. - J. Keating
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Akonadi's unix sockets location
 

Juha Tuomala wrote:

> https://bugs.kde.org/show_bug.cgi?id=179006#c5
>> in the current version of Akonadi server you can specify a custom
>> socket path by entering
>>
>> [Connection]
>> SocketDirectory=/tmp/akonadi-myuser/
>>
>> into $HOME/.config/akonadi/akonadiserverrc
>
> How about setting that as default, away from $HOME that can be a NFS
> filesystem?

Indeed, a solution similar to kde's
~/.kde/socket-<hostname> => /tmp/ksocket-<username>
symlink is likely needed here too.

-- Rex

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Akonadi's unix sockets location
 

On Tue, 16 Mar 2010, Rex Dieter wrote:
>> How about setting that as default, away from $HOME that can be a NFS
>> filesystem?
>
> Indeed, a solution similar to kde's
> ~/.kde/socket-<hostname> => /tmp/ksocket-<username>
> symlink is likely needed here too.

Symlinks are duct-tape, why not just set it to /tmp with
global rc file?


Tuju

--
You want to throw out the baby with the bathwater! - K. Kofler
Your baby is my bathwater. I don't want the OS you're building. - J. Keating
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Akonadi's unix sockets location
 

Juha Tuomala wrote:

> On Tue, 16 Mar 2010, Rex Dieter wrote:
>>> How about setting that as default, away from $HOME that can be a NFS
>>> filesystem?
>>
>> Indeed, a solution similar to kde's
>> ~/.kde/socket-<hostname> => /tmp/ksocket-<username>
>> symlink is likely needed here too.
>
> Symlinks are duct-tape, why not just set it to /tmp with
> global rc file?

Sure, but still need to encode username into the filename (or randomize/uniq
it) somehow.

-- Rex

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Akonadi's unix sockets location
 

Juha Tuomala wrote:

>
>
>
> On Tue, 16 Mar 2010, Rex Dieter wrote:
>>> How about setting that as default, away from $HOME that can be a NFS
>>> filesystem?
>>
>> Indeed, a solution similar to kde's
>> ~/.kde/socket-<hostname> => /tmp/ksocket-<username>
>> symlink is likely needed here too.
>
> Symlinks are duct-tape, why not just set it to /tmp with
> global rc file?

fyi, tracking here,
https://bugzilla.redhat.com/show_bug.cgi?id=574056

-- Rex

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Akonadi's unix sockets location
 

On Tue, 16 Mar 2010, Rex Dieter wrote:
>> Symlinks are duct-tape, why not just set it to /tmp with
>> global rc file?
>
> Sure, but still need to encode username into the filename (or randomize/uniq
> it) somehow.

Could that be it:

http://techbase.kde.org/KDE_System_Administration/Configuration_Files#Example:_Dynamic_Entries



Tuju

--
You want to throw out the baby with the bathwater! - K. Kofler
Your baby is my bathwater. I don't want the OS you're building. - J. Keating
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Akonadi's unix sockets location
 

On Tue, 2010-03-16 at 08:56 -0500, Rex Dieter wrote:
> Juha Tuomala wrote:
>
> > On Tue, 16 Mar 2010, Rex Dieter wrote:
> >>> How about setting that as default, away from $HOME that can be a NFS
> >>> filesystem?
> >>
> >> Indeed, a solution similar to kde's
> >> ~/.kde/socket-<hostname> => /tmp/ksocket-<username>
> >> symlink is likely needed here too.
> >
> > Symlinks are duct-tape, why not just set it to /tmp with
> > global rc file?
>
> Sure, but still need to encode username into the filename (or randomize/uniq
> it) somehow.
>

Any reason this cannot be an abstract socket ? Of course, then you have
to check peer creds and figure out a way to communicate the socket name,
but at least you don't have to worry about the usual races and
permission problem you have with unix sockets.

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Akonadi's unix sockets location
 

On Tue, Mar 16, 2010 at 10:54 AM, Matthias Clasen <mclasen@redhat.com> wrote:
>
> Any reason this cannot be an abstract socket ? Of course, then you have
> to check peer creds and figure out a way to communicate the socket name,
> but at least you don't have to worry about the usual races and
> permission problem you have with unix sockets.

People - reliably finding other programs and initiating communication
with them is 99% of the reason that DBus was created and exists in the
OS.

In this case, the right thing is to claim a bus name (org.blah.MyApp),
export a method on it "org.blah.MyApp.GetSocket", which returns the
randomly-named path to your socket in /tmp.

Using abstract sockets does NOT mean you don't have to worry about
permissions. Any other uid can still connect to the socket, so you
either need to do some sort of peer credentials if you want to
restrict it to the same uid.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Akonadi's unix sockets location
 

On 03/16/2010 11:17 AM, Colin Walters wrote:
> On Tue, Mar 16, 2010 at 10:54 AM, Matthias Clasen<mclasen@redhat.com> wrote:
>
>> Any reason this cannot be an abstract socket ? Of course, then you have
>> to check peer creds and figure out a way to communicate the socket name,
>> but at least you don't have to worry about the usual races and
>> permission problem you have with unix sockets.
>>
> People - reliably finding other programs and initiating communication
> with them is 99% of the reason that DBus was created and exists in the
> OS.
>
> In this case, the right thing is to claim a bus name (org.blah.MyApp),
> export a method on it "org.blah.MyApp.GetSocket", which returns the
> randomly-named path to your socket in /tmp.
>
> Using abstract sockets does NOT mean you don't have to worry about
> permissions. Any other uid can still connect to the socket, so you
> either need to do some sort of peer credentials if you want to
> restrict it to the same uid.
>
PLEASE do not use /tmp for communications. Use /var/run if the service
is running as root, or can create a socket in /var/run.

Processes running with different UID communicating over /tmp will break
in a namespace environment.
Evil users have successfully in the past caused privileged apps to do
evil things when the priv apps do stuff in /tmp.

I believe it is a good idea to avoid priv apps using any directory where
random users can write.


--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Akonadi's unix sockets location
 

On Tue, Mar 16, 2010 at 12:16 PM, Daniel J Walsh <dwalsh@redhat.com> wrote:
>
> PLEASE do not use /tmp for communications. *Use /var/run if the service is
> running as root, or can create a socket in /var/run.

In this case I believe it's a per-user service. In which case you
don't have much of a choice, because you can't use $HOME or you'll be
broken by the sysadmins that inflict NFS on users.

The dbus session socket is currently in /tmp, but with a random name,
and the session bus rejects connections by processes not matching its
own uid.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel