Re: Connect to Unix domain socket instead of host:port

[Andreas B]

Hi Gary,

One of the reasons I want to use a Unix domain socket exclusively, is to not expose anything to the network.

If all clients are local, I thought that this was an example of doing things 'the smart way'.

If I'm not going to use TCP, why expose it?

But there's no efficiency argument, you say? There is no network stack involved; wouldn't that increase efficiency a little tiny bit?

Best,

Andreas

On Thu, Dec 19, 2024 at 10:31 PM Gary E. Miller <gem@rellim.com> wrote:

Yo Pinnacle!

On Thu, 19 Dec 2024 08:58:17 -0500
Pinnacle Systems Group <pinnaclesystemsgroup@gmail.com> wrote:

> It's possible to configure gpsd to use a UNIX domain socket instead
> of the typical TCP host:port setup.

Not "instead of" but "in addition to".

> If your GNSS receiver communicates via a UNIX domain socket, you can
> specify the device using its path. For example:

OP says he wants to client conenct, not receiver conenct.

>    2. Client Connection to gpsd via a UNIX Domain Socket
>
> To allow clients to connect to gpsd through a UNIX domain socket, you
> can specify the socket path when starting gpsd. Use the -S flag to
> disable the default TCP listener and instead specify a UNIX socket
> path with the -F flag:

Dunno why you want to disable TCP clients.

>    This approach is often used to improve security and reduce
> overhead by avoiding TCP communication.

If you don't trust your host, you should not run gpsd on it.  The code
path's is the same for both, so no "efficiency" argument can be made.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        gem@rellim.com  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin