Please help us test the behavior of different Unices

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Please help us test the behavior of different Unices

Justus Winter
Hello,

I have written a small test program and I would like to ask you to run
it on UNIX platforms that you care about.  (Care as in you want to be
able to run GnuPG on it the future).

This program tests how different UNIX implementations cope with UNIX
domain sockets being created in paths that exceed sizeof (struct
sockaddr_un.sun_path).

The hypothesis is that it is okay to create sockets there, as long as
one uses relative paths for bind and connect.

Building and running this program should be as easy as:

  % make test-unix-sockets && ./test-unix-sockets

This is an example output:

System: GNU:0.9:GNU-Mach 1.8-686-dbg/Hurd-0.9
sizeof addr.sun_path: 108
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '', addrlen: 3
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned '', addrlen: 3
Running test with strlen (cwd): 130, name: 'socket'
  getsockname returned '', addrlen: 3
Running test with strlen (cwd): 1102, name: 'socket'
  getsockname returned '', addrlen: 3

Please post the results here.


Thanks,
Justus

_______________________________________________
Gnupg-devel mailing list
[hidden email]
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

signature.asc (497 bytes) Download Attachment
test-unix-sockets.c (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Please help us test the behavior of different Unices

Patrick Brunschwig-2
On 01.03.17 14:22, Justus Winter wrote:

> Hello,
>
> I have written a small test program and I would like to ask you to run
> it on UNIX platforms that you care about.  (Care as in you want to be
> able to run GnuPG on it the future).
>
> This program tests how different UNIX implementations cope with UNIX
> domain sockets being created in paths that exceed sizeof (struct
> sockaddr_un.sun_path).
>
> The hypothesis is that it is okay to create sockets there, as long as
> one uses relative paths for bind and connect.
>
> Building and running this program should be as easy as:
>
>   % make test-unix-sockets && ./test-unix-sockets
>
> This is an example output:
>
> System: GNU:0.9:GNU-Mach 1.8-686-dbg/Hurd-0.9
> sizeof addr.sun_path: 108
> Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
>   getsockname returned '', addrlen: 3
> Running test with strlen (cwd): 22, name: 'socket'
>   getsockname returned '', addrlen: 3
> Running test with strlen (cwd): 130, name: 'socket'
>   getsockname returned '', addrlen: 3
> Running test with strlen (cwd): 1102, name: 'socket'
>   getsockname returned '', addrlen: 3
>
> Please post the results here.

macOS Sierra (10.12):

System: Darwin:16.4.0:Darwin Kernel Version 16.4.0: Thu Dec 22 22:53:21
PST 2016; root:xnu-3789.41.3~3/RELEASE_X86_64
sizeof addr.sun_path: 104
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 106
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 106
Running test with strlen (cwd): 126, name: 'socket'
  getsockname returned 'socket', addrlen: 106
Running test with strlen (cwd): 1062, name: 'socket'
  getsockname returned 'socket', addrlen: 106

-Patrick

_______________________________________________
Gnupg-devel mailing list
[hidden email]
http://lists.gnupg.org/mailman/listinfo/gnupg-devel
Reply | Threaded
Open this post in threaded view
|

Re: Please help us test the behavior of different Unices

Jochen Saalfeld
In reply to this post by Justus Winter
Hi Justus,

System: Linux:4.9.11-1-ARCH:#1 SMP PREEMPT Sun Feb 19 13:45:52 UTC 2017
sizeof addr.sun_path: 108
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 32
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 9
Running test with strlen (cwd): 130, name: 'socket'
  getsockname returned 'socket', addrlen: 9
Running test with strlen (cwd): 1102, name: 'socket'
  getsockname returned 'socket', addrlen: 9

Cheers,
Jochen

On Wednesday, March 1, 2017 2:22:08 PM CET Justus Winter wrote:

> Hello,
>
> I have written a small test program and I would like to ask you to run
> it on UNIX platforms that you care about.  (Care as in you want to be
> able to run GnuPG on it the future).
>
> This program tests how different UNIX implementations cope with UNIX
> domain sockets being created in paths that exceed sizeof (struct
> sockaddr_un.sun_path).
>
> The hypothesis is that it is okay to create sockets there, as long as
> one uses relative paths for bind and connect.
>
> Building and running this program should be as easy as:
>
>   % make test-unix-sockets && ./test-unix-sockets
>
> This is an example output:
>
> System: GNU:0.9:GNU-Mach 1.8-686-dbg/Hurd-0.9
> sizeof addr.sun_path: 108
> Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
>   getsockname returned '', addrlen: 3
> Running test with strlen (cwd): 22, name: 'socket'
>   getsockname returned '', addrlen: 3
> Running test with strlen (cwd): 130, name: 'socket'
>   getsockname returned '', addrlen: 3
> Running test with strlen (cwd): 1102, name: 'socket'
>   getsockname returned '', addrlen: 3
>
> Please post the results here.
>
>
> Thanks,
> Justus

--
[hidden email] | intevation.de/ | 0541335083214 | PGPkey: 0x64B67DF4
Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
_______________________________________________
Gnupg-devel mailing list
[hidden email]
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

signature.asc (849 bytes) Download Attachment
ilf
Reply | Threaded
Open this post in threaded view
|

Re: Please help us test the behavior of different Unices

ilf
In reply to this post by Justus Winter
Justus Winter:
> Please post the results here.

System: FreeBSD:7.3-STABLE

sizeof addr.sun_path: 104
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 106
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 106
Running test with strlen (cwd): 126, name: 'socket'
  getsockname returned 'socket', addrlen: 106
Running test with strlen (cwd): 1062, name: 'socket'
  getsockname returned 'socket', addrlen: 106

--
ilf

Über 80 Millionen Deutsche benutzen keine Konsole. Klick dich nicht weg!
                -- Eine Initiative des Bundesamtes für Tastaturbenutzung

_______________________________________________
Gnupg-devel mailing list
[hidden email]
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Please help us test the behavior of different Unices

Daniel Kahn Gillmor-7
In reply to this post by Justus Winter
On Wed 2017-03-01 05:22:08 -0800, Justus Winter wrote:
> I have written a small test program and I would like to ask you to run
> it on UNIX platforms that you care about.  (Care as in you want to be
> able to run GnuPG on it the future).

System: Linux:4.9.0-1-amd64:#1 SMP Debian 4.9.6-3 (2017-01-28)
sizeof addr.sun_path: 108
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 32
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 9
Running test with strlen (cwd): 130, name: 'socket'
  getsockname returned 'socket', addrlen: 9
Running test with strlen (cwd): 1102, name: 'socket'
  getsockname returned 'socket', addrlen: 9

Regards,

        --dkg

_______________________________________________
Gnupg-devel mailing list
[hidden email]
http://lists.gnupg.org/mailman/listinfo/gnupg-devel
Reply | Threaded
Open this post in threaded view
|

Re: Please help us test the behavior of different Unices

Steven M. Schweda-2
In reply to this post by Justus Winter
From: Justus Winter <[hidden email]>

> [...]  UNIX platforms that you care about.  (Care as in you want to be
> able to run GnuPG on it the future).

   I don't claim to care about any of the systems shown below, but
someone might.  (And my junk collection could use the exercise.)

> Building and running this program should be as easy as:
>
>   % make test-unix-sockets && ./test-unix-sockets

   Thare's an optimist.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
   HP-UX 11.11 (PA-RISC):

dy# uname -a
HP-UX dy B.11.11 U 9000/785 2012616114 unlimited-user license

dy# gcc --version
gcc (GCC) 4.4.2
[...]

dy# gcc -o test-unix-sockets test-unix-sockets.c

dy# ./test-unix-sockets
System: HP-UX:B.11.11:U
sizeof addr.sun_path: 92
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 94
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 94
Running test with strlen (cwd): 114, name: 'socket'
  getsockname returned 'socket', addrlen: 94
Running test with strlen (cwd): 1034, name: 'socket'
  getsockname returned 'socket', addrlen: 94

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
   HP-UX 11.31 (IA64):

rux# uname -a
HP-UX rux B.11.31 U ia64 1678555272 unlimited-user license

rux# cc -V  
(Bundled) cc: HP C/aC++ B3910B A.06.12 [Oct 11 2006]

rux# cc -o test-unix-sockets test-unix-sockets.c
"test-unix-sockets.c", line 101: warning #2167-D: argument of type
          "socklen_t *" is incompatible with parameter of type "int *"
    if (getsockname (server, (struct sockaddr *) &addr, &addrlen) < 0)
                                                        ^

rux# ./test-unix-sockets                          
System: HP-UX:B.11.31:U
sizeof addr.sun_path: 92
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 94
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 94
Running test with strlen (cwd): 114, name: 'socket'
  getsockname returned 'socket', addrlen: 94
Running test with strlen (cwd): 1034, name: 'socket'
  getsockname returned 'socket', addrlen: 94

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
   Solaris 10 (SPARC):

ra# uname -a
SunOS ra 5.10 Generic_141444-09 sun4u sparc SUNW,UltraSPARC-IIi-cEngine

ra# cc -V
cc: Sun C 5.9 SunOS_sparc Patch 124867-01 2007/07/12
[...]

ra# cc -o test-unix-sockets test-unix-sockets.c
Undefined                       first referenced
 symbol                             in file
bind                                test-unix-sockets.o
getsockname                         test-unix-sockets.o
accept                              test-unix-sockets.o
listen                              test-unix-sockets.o
socket                              test-unix-sockets.o
connect                             test-unix-sockets.o
ld: fatal: Symbol referencing errors. No output written to test-unix-sockets

ra# cc -o test-unix-sockets test-unix-sockets.c -lsocket

ra# ./test-unix-sockets
System: SunOS:5.10:Generic_141444-09
sizeof addr.sun_path: 108
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 110
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 110
Running test with strlen (cwd): 130, name: 'socket'
  getsockname returned 'socket', addrlen: 110
Running test with strlen (cwd): 1102, name: 'socket'
  getsockname returned 'socket', addrlen: 110

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
   Solaris 11 (x86):

soli7# uname -a
SunOS soli7 5.11 11.1 i86pc i386 i86pc

soli7# cc -V
cc: Sun C 5.12 SunOS_i386 2011/11/16

soli7# cc -o test-unix-sockets test-unix-sockets.c
Undefined                       first referenced
 symbol                             in file
bind                                test-unix-sockets.o
getsockname                         test-unix-sockets.o
accept                              test-unix-sockets.o
listen                              test-unix-sockets.o
socket                              test-unix-sockets.o
connect                             test-unix-sockets.o
ld: fatal: symbol referencing errors. No output written to test-unix-sockets

soli7# cc -o test-unix-sockets test-unix-sockets.c -lsocket

soli7# ./test-unix-sockets
System: SunOS:5.11:11.1
sizeof addr.sun_path: 108
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 110
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 110
Running test with strlen (cwd): 130, name: 'socket'
  getsockname returned 'socket', addrlen: 110
Running test with strlen (cwd): 1102, name: 'socket'
  getsockname returned 'socket', addrlen: 110

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
   Tru64 V5.1B:

urtx# uname -a
OSF1 urtx.antinode.info V5.1 2650 alpha

urtx# sizer -v
HP Tru64 UNIX V5.1B (Rev. 2650); Wed Feb 17 22:59:59 CST 2016

urtx# cc -V
Compaq C V6.5-303 (dtk) on HP Tru64 UNIX V5.1B (Rev. 2650)
Compiler Driver V6.5-302 (dtk) cc Driver

urtx# cc -o test-unix-sockets test-unix-sockets.c
cc: Error: test-unix-sockets.c, line 57: In this declaration,
 "socklen_t" must specify a type. (badparsedecl)
  socklen_t addrlen;
--^
cc: Error: test-unix-sockets.c, line 99: In this statement, "addrlen" is
 not declared. (undeclared)
  addrlen = sizeof addr;
--^

urtx# cc -o test-unix-sockets -D_XOPEN_SOURCE=500 test-unix-sockets.c

urtx# ./test-unix-sockets
System: OSF1:V5.1:2650
sizeof addr.sun_path: 104
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 106
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 106
Running test with strlen (cwd): 126, name: 'socket'
  getsockname returned 'socket', addrlen: 106
Running test with strlen (cwd): 1062, name: 'socket'
  getsockname returned 'socket', addrlen: 106

------------------------------------------------------------------------

   Steven M. Schweda               sms@antinode-info
   382 South Warwick Street        (+1) 651-699-9818
   Saint Paul  MN  55105-2547

_______________________________________________
Gnupg-devel mailing list
[hidden email]
http://lists.gnupg.org/mailman/listinfo/gnupg-devel
Reply | Threaded
Open this post in threaded view
|

Re: Please help us test the behavior of different Unices

Phil Pennock-18
In reply to this post by ilf
On 2017-03-01 at 17:40 +0100, ilf wrote:
> Justus Winter:
> > Please post the results here.
>
> System: FreeBSD:7.3-STABLE

Ditto on FreeBSD:10.3-RELEASE series (kernel -p11)

No difference in output whether compiled with the system compiler (clang
3.4.1) or gcc 4.9.4.  Didn't expect any, but didn't hurt to check.

System: FreeBSD:10.3-RELEASE-p11:FreeBSD 10.3-RELEASE-p11 #0: Mon Oct 24 18:49:24 UTC 2016     [hidden email]:/usr/obj/usr/src/sys/GENERIC
sizeof addr.sun_path: 104
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 106
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 106
Running test with strlen (cwd): 126, name: 'socket'
  getsockname returned 'socket', addrlen: 106
Running test with strlen (cwd): 1062, name: 'socket'
  getsockname returned 'socket', addrlen: 106

-Phil

_______________________________________________
Gnupg-devel mailing list
[hidden email]
http://lists.gnupg.org/mailman/listinfo/gnupg-devel
Reply | Threaded
Open this post in threaded view
|

Re: Please help us test the behavior of different Unices

Jochen Saalfeld
In reply to this post by Justus Winter
Hi again,

some additional Information from other sources[1]:

NetBSD 6, 7 and current are all the same on multiple architectures:
System: NetBSD:6.1_STABLE:NetBSD 6.1_STABLE (LUNA-$Revision: 6.2 $) #0: Mon
Jan  9 21:39:01 UTC 2017  [hidden email]:/usr/release/obj-vax/sys/arch/vax/
compile/LUNA
sizeof addr.sun_path: 104
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 106
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 106
Running test with strlen (cwd): 126, name: 'socket'
  getsockname returned 'socket', addrlen: 106
Running test with strlen (cwd): 1062, name: 'socket'
  getsockname returned 'socket', addrlen: 106

Mac OS X (PowerPC, amd64) are the same:
System: Darwin:9.8.0:Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT
2009; root:xnu-1228.15.4~1/RELEASE_PPC
sizeof addr.sun_path: 104
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 106
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 106
Running test with strlen (cwd): 126, name: 'socket'
  getsockname returned 'socket', addrlen: 106
Running test with strlen (cwd): 1062, name: 'socket'
  getsockname returned 'socket', addrlen: 106

On IBM Power8 running Ubuntu GNU/Linux (ppc64le):
System: Linux:4.4.0-64-generic:#85-Ubuntu SMP Mon Feb 20 17:05:51 UTC 2017
sizeof addr.sun_path: 108
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 32
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 9
Running test with strlen (cwd): 130, name: 'socket'
  getsockname returned 'socket', addrlen: 9
Running test with strlen (cwd): 1102, name: 'socket'
  getsockname returned 'socket', addrlen: 9

Kind regards,
Jochen

[1] - https://www.reddit.com/r/GnuPG/comments/5ww75f/
please_help_us_test_the_behavior_of_different/deemis8/?context=3

On Wednesday, March 1, 2017 2:22:08 PM CET Justus Winter wrote:

> Hello,
>
> I have written a small test program and I would like to ask you to run
> it on UNIX platforms that you care about.  (Care as in you want to be
> able to run GnuPG on it the future).
>
> This program tests how different UNIX implementations cope with UNIX
> domain sockets being created in paths that exceed sizeof (struct
> sockaddr_un.sun_path).
>
> The hypothesis is that it is okay to create sockets there, as long as
> one uses relative paths for bind and connect.
>
> Building and running this program should be as easy as:
>
>   % make test-unix-sockets && ./test-unix-sockets
>
> This is an example output:
>
> System: GNU:0.9:GNU-Mach 1.8-686-dbg/Hurd-0.9
> sizeof addr.sun_path: 108
> Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
>   getsockname returned '', addrlen: 3
> Running test with strlen (cwd): 22, name: 'socket'
>   getsockname returned '', addrlen: 3
> Running test with strlen (cwd): 130, name: 'socket'
>   getsockname returned '', addrlen: 3
> Running test with strlen (cwd): 1102, name: 'socket'
>   getsockname returned '', addrlen: 3
>
> Please post the results here.
>
>
> Thanks,
> Justus

--
[hidden email] | intevation.de/ | 0541335083214 | PGPkey: 0x64B67DF4
Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
_______________________________________________
Gnupg-devel mailing list
[hidden email]
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Please help us test the behavior of different Unices

NIIBE Yutaka
In reply to this post by Justus Winter
Hello,

Justus Winter <[hidden email]> writes:
>   % make test-unix-sockets && ./test-unix-sockets

$ uname -a
AIX power-aix 1 7 00F84C0C4C00
$ make CC=gcc test-unix-sockets
        gcc -O  test-unix-sockets.c -o test-unix-sockets
$ ./test-unix-sockets
System: AIX:1:7
sizeof addr.sun_path: 1023
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 1025
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 1025
chdir: File name too long
$


$ uname -a
AIX power8-aix 2 7 00FA74164C00
$ make CC=gcc test-unix-sockets
        gcc -O  test-unix-sockets.c -o test-unix-sockets
$ ./test-unix-sockets
System: AIX:2:7
sizeof addr.sun_path: 1023
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 1025
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 1025
chdir: File name too long
$
--

_______________________________________________
Gnupg-devel mailing list
[hidden email]
http://lists.gnupg.org/mailman/listinfo/gnupg-devel
Reply | Threaded
Open this post in threaded view
|

Re: Please help us test the behavior of different Unices

Justus Winter
Hi,

NIIBE Yutaka <[hidden email]> writes:
> $ ./test-unix-sockets
> System: AIX:1:7
> sizeof addr.sun_path: 1023

That is amazing.  Well, I guess we wouldn't have these kind of problems
on AIX in the first place.

> Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
>   getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 1025
> Running test with strlen (cwd): 22, name: 'socket'
>   getsockname returned 'socket', addrlen: 1025
> chdir: File name too long

I guess we're hitting PATH_MAX here, and AIX is actually serious about
it.

I have revised the test program to be a little more conservative here.
Would you be so kind to rerun it?

(There is no need to rerun the test on systems where the previous
version succeeded.)


Thanks,
Justus

_______________________________________________
Gnupg-devel mailing list
[hidden email]
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

signature.asc (497 bytes) Download Attachment
test-unix-sockets.c (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Please help us test the behavior of different Unices

NIIBE Yutaka
Justus Winter <[hidden email]> writes:
> I have revised the test program to be a little more conservative here.
> Would you be so kind to rerun it?

Here they are.


$ ./test-unix-sockets
System: AIX:1:7
sizeof addr.sun_path: 1023
PATH_MAX: 1023
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 1025
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 1025
Running test with strlen (cwd): 122, name: 'socket'
  getsockname returned 'socket', addrlen: 1025
Running test with strlen (cwd): 822, name: 'socket'
  getsockname returned 'socket', addrlen: 1025
$

$ ./test-unix-sockets
System: AIX:2:7
sizeof addr.sun_path: 1023
PATH_MAX: 1023
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 1025
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 1025
Running test with strlen (cwd): 122, name: 'socket'
  getsockname returned 'socket', addrlen: 1025
Running test with strlen (cwd): 822, name: 'socket'
  getsockname returned 'socket', addrlen: 1025
$
--

_______________________________________________
Gnupg-devel mailing list
[hidden email]
http://lists.gnupg.org/mailman/listinfo/gnupg-devel
Reply | Threaded
Open this post in threaded view
|

Re: Please help us test the behavior of different Unices

Brian C. Lane
In reply to this post by Justus Winter
On Wed, Mar 01, 2017 at 02:22:08PM +0100, Justus Winter wrote:
> Hello,
>
> I have written a small test program and I would like to ask you to run
> it on UNIX platforms that you care about.  (Care as in you want to be
> able to run GnuPG on it the future).

A bit late to the party, but I didn't notice any Fedora/RHEL systems:

System: Linux:3.10.0-327.el7.x86_64:#1 SMP Thu Oct 29 17:29:29 EDT 2015
sizeof addr.sun_path: 108
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 32
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 9
Running test with strlen (cwd): 130, name: 'socket'
  getsockname returned 'socket', addrlen: 9
Running test with strlen (cwd): 1102, name: 'socket'
  getsockname returned 'socket', addrlen: 9

System: Linux:4.10.10-200.fc25.x86_64:#1 SMP Thu Apr 13 01:11:51 UTC 2017
sizeof addr.sun_path: 108
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 32
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 9
Running test with strlen (cwd): 130, name: 'socket'
  getsockname returned 'socket', addrlen: 9
Running test with strlen (cwd): 1102, name: 'socket'
  getsockname returned 'socket', addrlen: 9

And a Beagle Bone Black:

System: Linux:4.4.30-ti-r64:#1 SMP Fri Nov 4 21:23:33 UTC 2016
sizeof addr.sun_path: 108
Running test with strlen (cwd): 22, name: '/tmp/test-unix-sockets/socket'
  getsockname returned '/tmp/test-unix-sockets/socket', addrlen: 32
Running test with strlen (cwd): 22, name: 'socket'
  getsockname returned 'socket', addrlen: 9
Running test with strlen (cwd): 130, name: 'socket'
  getsockname returned 'socket', addrlen: 9
Running test with strlen (cwd): 1102, name: 'socket'
  getsockname returned 'socket', addrlen: 9

--
Brian C. Lane (PST8PDT)

_______________________________________________
Gnupg-devel mailing list
[hidden email]
http://lists.gnupg.org/mailman/listinfo/gnupg-devel