From dam at opencsw.org Sun Jun 7 22:31:44 2026 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 7 Jun 2026 22:31:44 +0200 Subject: installing swig on cfarm210? In-Reply-To: References: Message-ID: Hi Pat, > Am 07.06.2026 um 20:28 schrieb Patrice Dumas : > The new GNU/Texinfo SWIG interface test fails on opencsw for solaris 10. > Could it be possible, please, to install SWIG on cfarm210 such that I > can try to reproduce the issue? Sure, cfarm 210 and cfarm 211 now have OpenCSW swig installed. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 From dam at opencsw.org Sun Jun 7 22:47:50 2026 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 7 Jun 2026 22:47:50 +0200 Subject: new test result files for opencsw texinfo In-Reply-To: References: Message-ID: Hi Pat, > Am 07.06.2026 um 20:47 schrieb Patrice Dumas : > There are now two new test suites results which logs could be useful > on https://buildfarm.opencsw.org for texinfo, namely: > > Pod-Simple-Texinfo/test-suite.log > tta/swig/perl/test-suite.log > > Could you please add them? > > I do not remember who can add new log files to be output, so I send to > you both. Sure, done. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 From pertusus at free.fr Mon Jun 8 01:25:28 2026 From: pertusus at free.fr (Patrice Dumas) Date: Mon, 8 Jun 2026 01:25:28 +0200 Subject: new test result files for opencsw texinfo In-Reply-To: References:

Message-ID: On Sun, Jun 07, 2026 at 10:47:50PM +0200, Dagobert Michelsen wrote: > Hi Pat, > > > Am 07.06.2026 um 20:47 schrieb Patrice Dumas : > > There are now two new test suites results which logs could be useful > > on https://buildfarm.opencsw.org for texinfo, namely: > > > > Pod-Simple-Texinfo/test-suite.log > > tta/swig/perl/test-suite.log > > > > Could you please add them? > > > > I do not remember who can add new log files to be output, so I send to > > you both. > > Sure, done. Thanks! -- Pat From pertusus at free.fr Mon Jun 8 22:43:10 2026 From: pertusus at free.fr (Patrice Dumas) Date: Mon, 8 Jun 2026 22:43:10 +0200 Subject: installing swig on cfarm210? In-Reply-To: References:

Message-ID: On Sun, Jun 07, 2026 at 10:31:44PM +0200, Dagobert Michelsen wrote: > Hi Pat, > > > Am 07.06.2026 um 20:28 schrieb Patrice Dumas : > > The new GNU/Texinfo SWIG interface test fails on opencsw for solaris 10. > > Could it be possible, please, to install SWIG on cfarm210 such that I > > can try to reproduce the issue? > > Sure, cfarm 210 and cfarm 211 now have OpenCSW swig installed. Thanks a lot. I did not manage to reproduce the issue I had on OpenCSW (the new test log in OpenCSW allowed to fix the issue), because iconv cannot be built together with Perl flags on cfarm 210, while it does without Perl flags on cfarm 210, and with Perl flags in OpenCSW. More precisely, building without Perl flags works ok on cfarm 210, the command-line that succeeds is: gcc -o conftest -g -D_STDC_C99= -I/opt/csw/include/ -D_REENTRANT -I/usr/local/include -L/opt/csw/lib/ conftest.c /usr/local/lib/libiconv.so -L/usr/local/lib/64 -L/usr/local/lib -R/usr/local/lib With the Perl flags, there is a failure. The command-line is: /opt/SUNWspro/bin/cc -o conftest -g -D_STDC_C99= -D_REENTRANT -xO3 -m32 -xarch=sparc -I/opt/csw/bdb48/include -I/opt/csw/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPERL_USE_SAFE_PUTENV -I/opt/csw/include/ -D_REENTRANT -I/usr/local/include -L/opt/csw/lib/ -R /opt/csw/lib -m32 -xarch=sparc -L/opt/csw/lib -lperl -L/opt/csw/bdb48/lib -L/opt/csw/lib -L/usr/lib -L/usr/ccs/lib -L/lib conftest.c /usr/local/lib/libiconv.so -L/usr/local/lib/64 -L/usr/local/lib -L/usr/lib/sparcv9 -R/usr/local/lib The failure: ld: fatal: file /usr/local/lib/libiconv.so: wrong ELF class: ELFCLASS64 This above comes from config.log, I do not have access to config.log on OpenCSW, but what I can compare are the Perl flags as they are output by configure, and they seem very similar between cfarm 210 and texinfo-solaris10-sparc. I do not know Solaris enough to understand what is normal, what is not, but in case it can be useful to you, I reported what I could, though I do not have any specific demand (for now ;-), it is for your information. -- Pat From dam at opencsw.org Mon Jun 8 22:54:10 2026 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 8 Jun 2026 22:54:10 +0200 Subject: installing swig on cfarm210? In-Reply-To: References:

Message-ID: <9DA78026-F073-47FF-8091-770DA72459A4@opencsw.org> Hi Pat, > Am 08.06.2026 um 22:43 schrieb Patrice Dumas : > I did not manage to reproduce the issue I had on OpenCSW (the new test > log in OpenCSW allowed to fix the issue), because iconv cannot be built > together with Perl flags on cfarm 210, while it does without Perl flags > on cfarm 210, and with Perl flags in OpenCSW. > > More precisely, building without Perl flags works ok on cfarm 210, the > command-line that succeeds is: > gcc -o conftest -g -D_STDC_C99= -I/opt/csw/include/ -D_REENTRANT -I/usr/local/include -L/opt/csw/lib/ conftest.c /usr/local/lib/libiconv.so -L/usr/local/lib/64 -L/usr/local/lib -R/usr/local/lib > > With the Perl flags, there is a failure. The command-line is: > /opt/SUNWspro/bin/cc -o conftest -g -D_STDC_C99= -D_REENTRANT -xO3 -m32 -xarch=sparc -I/opt/csw/bdb48/include -I/opt/csw/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPERL_USE_SAFE_PUTENV -I/opt/csw/include/ -D_REENTRANT -I/usr/local/include -L/opt/csw/lib/ -R /opt/csw/lib -m32 -xarch=sparc -L/opt/csw/lib -lperl -L/opt/csw/bdb48/lib -L/opt/csw/lib -L/usr/lib -L/usr/ccs/lib -L/lib conftest.c /usr/local/lib/libiconv.so -L/usr/local/lib/64 -L/usr/local/lib -L/usr/lib/sparcv9 -R/usr/local/lib > The failure: > ld: fatal: file /usr/local/lib/libiconv.so: wrong ELF class: ELFCLASS64 > > This above comes from config.log, I do not have access to config.log on > OpenCSW, but what I can compare are the Perl flags as they are output by > configure, and they seem very similar between cfarm 210 and > texinfo-solaris10-sparc. > > I do not know Solaris enough to understand what is normal, what is not, > but in case it can be useful to you, I reported what I could, though I do > not have any specific demand (for now ;-), it is for your information. The error means you are trying to link a 64 bit library to a 32 bit build and /usr/local/lib/libiconv.so is 64 bit. I suggest to use /opt/csw/lib for libiconv.so . Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 From pertusus at free.fr Thu Jun 11 00:11:23 2026 From: pertusus at free.fr (Patrice Dumas) Date: Thu, 11 Jun 2026 00:11:23 +0200 Subject: installing swig on cfarm210? In-Reply-To: <9DA78026-F073-47FF-8091-770DA72459A4@opencsw.org> References:

<9DA78026-F073-47FF-8091-770DA72459A4@opencsw.org> Message-ID: On Mon, Jun 08, 2026 at 10:54:10PM +0200, Dagobert Michelsen wrote: > Hi Pat, > > > More precisely, building without Perl flags works ok on cfarm 210, the > > command-line that succeeds is: > > gcc -o conftest -g -D_STDC_C99= -I/opt/csw/include/ -D_REENTRANT -I/usr/local/include -L/opt/csw/lib/ conftest.c /usr/local/lib/libiconv.so -L/usr/local/lib/64 -L/usr/local/lib -R/usr/local/lib > > > > With the Perl flags, there is a failure. The command-line is: > > The failure: > > ld: fatal: file /usr/local/lib/libiconv.so: wrong ELF class: ELFCLASS64 > The error means you are trying to link a 64 bit library to a 32 bit build > and /usr/local/lib/libiconv.so is 64 bit. I suggest to use /opt/csw/lib > for libiconv.so . I tried --without-libiconv-prefix and indeed, it allowed the linking with libiconv with Perl compiler and flags to work, with this command in the configure test: /opt/SUNWspro/bin/cc -o conftest -g -D_STDC_C99= -D_REENTRANT -xO3 -m32 -xarch=sparc -I/opt/csw/bdb48/include -I/opt/csw/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPERL_USE_SAFE_PUTENV -I/opt/csw/include/ -D_REENTRANT -I/opt/csw/include -L/opt/csw/lib/ -R /opt/csw/lib -m32 -xarch=sparc -L/opt/csw/lib -lperl -L/opt/csw/bdb48/lib -L/opt/csw/lib -L/usr/lib -L/usr/ccs/lib -L/lib conftest.c /opt/csw/lib//libiconv.so -R/opt/csw/lib/ However, in the main directory, with this command for the configure test: gcc -o conftest -g -D_STDC_C99= -I/opt/csw/include/ -D_REENTRANT -L/opt/csw/lib/ conftest.c -liconv There is this error at linked program runtime: ld.so.1: conftest: fatal: libiconv.so.2: open failed: No such file or directory I checked that /opt/csw/lib/libiconv.so.2 exists. This time there is an obvious difference with OpenCSW setup, Sun CC is used in OpenCSW, and I verified that linking against iconv in configure works on cfarm21O, with CC=cc. In that case the command is: cc -o conftest -g -D_STDC_C99= -I/opt/csw/include/ -D_REENTRANT -I/opt/csw/include -L/opt/csw/lib/ conftest.c /opt/csw/lib//libiconv.so -R/opt/csw/lib/ I do not know if the failure with gcc is an error on my side, or an issue in cfarm210. -- Pat From dam at opencsw.org Thu Jun 11 09:02:54 2026 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 11 Jun 2026 09:02:54 +0200 Subject: installing swig on cfarm210? In-Reply-To: References:

<9DA78026-F073-47FF-8091-770DA72459A4@opencsw.org> Message-ID: <2466A9B1-FAA1-47A6-85EE-8B517D1F43EE@opencsw.org> Hi Pat, > Am 11.06.2026 um 00:11 schrieb Patrice Dumas : > > On Mon, Jun 08, 2026 at 10:54:10PM +0200, Dagobert Michelsen wrote: >> Hi Pat, >> >>> More precisely, building without Perl flags works ok on cfarm 210, the >>> command-line that succeeds is: >>> gcc -o conftest -g -D_STDC_C99= -I/opt/csw/include/ -D_REENTRANT -I/usr/local/include -L/opt/csw/lib/ conftest.c /usr/local/lib/libiconv.so -L/usr/local/lib/64 -L/usr/local/lib -R/usr/local/lib >>> >>> With the Perl flags, there is a failure. The command-line is: >>> The failure: >>> ld: fatal: file /usr/local/lib/libiconv.so: wrong ELF class: ELFCLASS64 > >> The error means you are trying to link a 64 bit library to a 32 bit build >> and /usr/local/lib/libiconv.so is 64 bit. I suggest to use /opt/csw/lib >> for libiconv.so . > > I tried --without-libiconv-prefix and indeed, it allowed the linking > with libiconv with Perl compiler and flags to work, with this command > in the configure test: > /opt/SUNWspro/bin/cc -o conftest -g -D_STDC_C99= -D_REENTRANT -xO3 -m32 -xarch=sparc -I/opt/csw/bdb48/include -I/opt/csw/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPERL_USE_SAFE_PUTENV -I/opt/csw/include/ -D_REENTRANT -I/opt/csw/include -L/opt/csw/lib/ -R /opt/csw/lib -m32 -xarch=sparc -L/opt/csw/lib -lperl -L/opt/csw/bdb48/lib -L/opt/csw/lib -L/usr/lib -L/usr/ccs/lib -L/lib conftest.c /opt/csw/lib//libiconv.so -R/opt/csw/lib/ > > However, in the main directory, with this command for the configure test: > gcc -o conftest -g -D_STDC_C99= -I/opt/csw/include/ -D_REENTRANT -L/opt/csw/lib/ conftest.c -liconv > There is this error at linked program runtime: > ld.so.1: conftest: fatal: libiconv.so.2: open failed: No such file or directory > I checked that /opt/csw/lib/libiconv.so.2 exists. > > This time there is an obvious difference with OpenCSW setup, Sun CC is > used in OpenCSW, and I verified that linking against iconv in configure > works on cfarm21O, with CC=cc. In that case the command is: > cc -o conftest -g -D_STDC_C99= -I/opt/csw/include/ -D_REENTRANT -I/opt/csw/include -L/opt/csw/lib/ conftest.c /opt/csw/lib//libiconv.so -R/opt/csw/lib/ > > I do not know if the failure with gcc is an error on my side, or an > issue in cfarm210. The difference is -R/opt/csw/lib which includes the runpath in the binary. You can check with dump -Lv e.g. dam at unstable10s [unstable10s]:/home/dam/mgar/pkg/apache24/trunk > dump -Lv /opt/csw/bin/gcc /opt/csw/bin/gcc: **** DYNAMIC SECTION INFORMATION **** .dynamic: [INDEX] Tag Value [1] NEEDED libkstat.so.1 [2] NEEDED libiconv.so.2 [3] NEEDED libm.so.2 [4] NEEDED librt.so.1 [5] NEEDED libc.so.1 [6] INIT 0x90704 [7] FINI 0x90720 [8] RUNPATH /opt/csw/lib/$ISALIST:/opt/csw/lib:/opt/csw/lib [9] RPATH /opt/csw/lib/$ISALIST:/opt/csw/lib:/opt/csw/lib [10] HASH 0x11094 For testing you can directly insert the runpath in the linker by setting export LD_OPTIONS=/opt/csw/lib But beware! This insert the runpath before any other path set during build. Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 From pertusus at free.fr Thu Jun 11 10:12:23 2026 From: pertusus at free.fr (Patrice Dumas) Date: Thu, 11 Jun 2026 10:12:23 +0200 Subject: installing swig on cfarm210? In-Reply-To: <2466A9B1-FAA1-47A6-85EE-8B517D1F43EE@opencsw.org> References:

<9DA78026-F073-47FF-8091-770DA72459A4@opencsw.org> <2466A9B1-FAA1-47A6-85EE-8B517D1F43EE@opencsw.org> Message-ID: On Thu, Jun 11, 2026 at 09:02:54AM +0200, Dagobert Michelsen wrote: > Hi Pat, > > The difference is -R/opt/csw/lib which includes the runpath in the binary. > You can check with > dump -Lv > e.g. Ok. I think that it is probably right for the iconv detection autoconf macros to leave out the runpath in that case, as there is no perfect automatic solution here. > For testing you can directly insert the runpath in the linker by setting > export LD_OPTIONS=/opt/csw/lib > But beware! This insert the runpath before any other path set during build. Ok, noted. I am personnally actually more interested by using Solaris cc in general on cfarm210, given my use for Texinfo, but it could still be useful. Thanks a lot! -- Pat From dam at opencsw.org Tue Jun 23 08:01:30 2026 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 23 Jun 2026 08:01:30 +0200 Subject: cfarm211 sshd is old In-Reply-To: <4873767.LvFx2qVVIh@cagnes> References: <4873767.LvFx2qVVIh@cagnes> Message-ID: Hi Bruno, hi Freya, > Am 23.06.2026 um 01:59 schrieb Bruno Haible : > Since I just upgraded to a new Linux distro version, that ships with > > $ ssh -V > OpenSSH_10.2p1 Ubuntu-2ubuntu3.2, OpenSSL 3.5.5 27 Jan 2026 > > I cannot connect to cfarm211.cfarm.net any more. The login to > cfarm210.cfarm.net, on the other hand, works. > > What is the difference? > > cfarm210 (OK): > > debug1: Local version string SSH-2.0-OpenSSH_10.2p1 Ubuntu-2ubuntu3.2 > debug1: Remote protocol version 2.0, remote software version OpenSSH_10.2 > debug1: compat_banner: match: OpenSSH_10.2 pat OpenSSH* compat 0x04000000 > > cfarm211 (FAIL): > > debug1: Local version string SSH-2.0-OpenSSH_10.2p1 Ubuntu-2ubuntu3.2 > debug1: Remote protocol version 2.0, remote software version Sun_SSH_2.4 > debug1: compat_banner: no match: Sun_SSH_2.4 > > debug2: KEX algorithms: diffie-hellman-group-exchange-sha256,diffie-hellman- > group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 > debug2: host key algorithms: ssh-rsa,ssh-dss > > > The background: > - ssh-dss is disabled in OpenSSH 10. > - I don't have an ssh-rsa key. > - I have an ssh-ed25519 key, but that is apparently not supported by > Sun_SSH_2.4. > > Could you please install OpenSSH sshd on cfarm211, like you did on cfarm210? This is the SSH package from FractalKit. @Freya: Would you mind updating the package on cfarm211 too? Best regards ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 From dam at opencsw.org Tue Jun 23 09:49:06 2026 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 23 Jun 2026 09:49:06 +0200 Subject: ACLs opencsw In-Reply-To: <93512b38-dcd9-466e-97d1-fce523a21b05@cs.fau.de> References: <93512b38-dcd9-466e-97d1-fce523a21b05@cs.fau.de> Message-ID: Hallo Phillip, > Am 19.06.2026 um 14:43 schrieb Phillip Raffeck : > k?nntest du uns bitte mitteilen, welche von den folgenden Eintr?gen noch > ben?tigt werden und ?ber welche Ports sie erreichbar sein m?ssen? Die restlichen > Ports werden dann defaultm??ig geblockt. > > opencsw2.informatik.uni-erlangen.de (131.188.40.75) > opencsw2-rsync.informatik.uni-erlangen.de (131.188.40.76) > opencsw2-mirror.informatik.uni-erlangen.de (131.188.40.77) > opencsw2-pkg.informatik.uni-erlangen.de (131.188.40.78) > opencsw2-lom.informatik.uni-erlangen.de (131.188.40.79) > opencsw-rsync.informatik.uni-erlangen.de (131.188.40.80) > opencsw-new.informatik.uni-erlangen.de (131.188.40.81) > opencsw-mirror.informatik.uni-erlangen.de (131.188.40.82) > opencsw-pkg.informatik.uni-erlangen.de (131.188.40.83) > opencsw-lom.informatik.uni-erlangen.de (131.188.40.84) > > Aktuell sind folgende Regeln bei uns hinterlegt: > > permit tcp 213.178.77.170 131.188.40.79 22 Das ist korrekt - wird f?r das Monitoring gebraucht. > permit tcp 213.178.77.178 131.188.40.79 22 Das ist auch korrekt - das ist mein Service-SSH-Zugang von der Buildfarm hier. > Ist das ausreichend? ?ffentlich f?r alle brauchen wir zum runterladen der Pakete ?ber HTTP, HTTPS und rsync 131.188.40.82 fe80::8:20ff:fe7c:9466/10 auf den Ports 80, 443 und 873. Von der Buildfarm aus 213.178.77.176 m?ssen noch Pakete pushen, das ist per SSH und rsync auf die 131.188.40.82. Ich hoffe, das sind alle. Sonst m?ssen wir noch einmal schauen. Vielen Dank ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruno at haible.de Tue Jun 23 01:59:53 2026 From: bruno at haible.de (Bruno Haible) Date: Tue, 23 Jun 2026 01:59:53 +0200 Subject: cfarm211 sshd is old Message-ID: <4873767.LvFx2qVVIh@cagnes> Hi Dagobert, Since I just upgraded to a new Linux distro version, that ships with $ ssh -V OpenSSH_10.2p1 Ubuntu-2ubuntu3.2, OpenSSL 3.5.5 27 Jan 2026 I cannot connect to cfarm211.cfarm.net any more. The login to cfarm210.cfarm.net, on the other hand, works. What is the difference? cfarm210 (OK): debug1: Local version string SSH-2.0-OpenSSH_10.2p1 Ubuntu-2ubuntu3.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_10.2 debug1: compat_banner: match: OpenSSH_10.2 pat OpenSSH* compat 0x04000000 cfarm211 (FAIL): debug1: Local version string SSH-2.0-OpenSSH_10.2p1 Ubuntu-2ubuntu3.2 debug1: Remote protocol version 2.0, remote software version Sun_SSH_2.4 debug1: compat_banner: no match: Sun_SSH_2.4 debug2: KEX algorithms: diffie-hellman-group-exchange-sha256,diffie-hellman- group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: host key algorithms: ssh-rsa,ssh-dss The background: - ssh-dss is disabled in OpenSSH 10. - I don't have an ssh-rsa key. - I have an ssh-ed25519 key, but that is apparently not supported by Sun_SSH_2.4. Could you please install OpenSSH sshd on cfarm211, like you did on cfarm210? Thanks! Bruno From saoirse at axiom-networks.org Tue Jun 23 08:02:21 2026 From: saoirse at axiom-networks.org (Freya Fractal) Date: Mon, 22 Jun 2026 23:02:21 -0700 Subject: cfarm211 sshd is old In-Reply-To: References: <4873767.LvFx2qVVIh@cagnes> Message-ID: <3f34078e-5064-4e33-ad75-3b56e8db205c@axiom-networks.org> yep, I'll get on upgrading that, sorry, I've been kinda burnt out as hell recently On 6/22/2026 23:01, Dagobert Michelsen wrote: > Hi Bruno, hi Freya, > >> Am 23.06.2026 um 01:59 schrieb Bruno Haible : >> Since I just upgraded to a new Linux distro version, that ships with >> >> $ ssh -V >> OpenSSH_10.2p1 Ubuntu-2ubuntu3.2, OpenSSL 3.5.5 27 Jan 2026 >> >> I cannot connect to cfarm211.cfarm.net any more. The login to >> cfarm210.cfarm.net, on the other hand, works. >> >> What is the difference? >> >> cfarm210 (OK): >> >> debug1: Local version string SSH-2.0-OpenSSH_10.2p1 Ubuntu-2ubuntu3.2 >> debug1: Remote protocol version 2.0, remote software version OpenSSH_10.2 >> debug1: compat_banner: match: OpenSSH_10.2 pat OpenSSH* compat 0x04000000 >> >> cfarm211 (FAIL): >> >> debug1: Local version string SSH-2.0-OpenSSH_10.2p1 Ubuntu-2ubuntu3.2 >> debug1: Remote protocol version 2.0, remote software version Sun_SSH_2.4 >> debug1: compat_banner: no match: Sun_SSH_2.4 >> >> debug2: KEX algorithms: diffie-hellman-group-exchange-sha256,diffie-hellman- >> group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 >> debug2: host key algorithms: ssh-rsa,ssh-dss >> >> >> The background: >> - ssh-dss is disabled in OpenSSH 10. >> - I don't have an ssh-rsa key. >> - I have an ssh-ed25519 key, but that is apparently not supported by >> Sun_SSH_2.4. >> >> Could you please install OpenSSH sshd on cfarm211, like you did on cfarm210? > This is the SSH package from FractalKit. > @Freya: Would you mind updating the package on cfarm211 too? > > > Best regards > > ? Dago > From dam at opencsw.org Wed Jun 24 18:45:48 2026 From: dam at opencsw.org (Dagobert Michelsen) Date: Wed, 24 Jun 2026 18:45:48 +0200 Subject: [aods] ACLs opencsw In-Reply-To: <7271ad38-de87-4e05-bb1b-e6c2ba5668b1@cs.fau.de> References: <93512b38-dcd9-466e-97d1-fce523a21b05@cs.fau.de> <7271ad38-de87-4e05-bb1b-e6c2ba5668b1@cs.fau.de> Message-ID: Hallo Phillip, > Am 24.06.2026 um 10:05 schrieb Phillip Raffeck : > danke f?r die schnelle Antwort. > > > ?ffentlich f?r alle brauchen wir zum runterladen der Pakete ?ber HTTP, HTTPS und > > rsync > > 131.188.40.82 > > fe80::8:20ff:fe7c:9466/10 > > auf den Ports 80, 443 und 873. > > Das ist ne link-local IPv6-Adresse. Die IPv6-Adresse von opencsw- > mirror.informatik.uni-erlangen.de ist 2001:638:a000:4140::ffff:82. Ich vermute > mal, die war gemeint und hab sie auch so eingetragen. Ah, okay, ja. > Nur nochmal zur Sicherheit: Dies restlichen DNS-Eintr?ge sind nicht mehr in > Benutzung und k?nnen bei Bedarf entfernt werden? > > Viele Gr??e > Phillip > > On 23-06-2026 9:49 AM, Dagobert Michelsen wrote: >> Hallo Phillip, >>> Am 19.06.2026 um 14:43 schrieb Phillip Raffeck : >>> k?nntest du uns bitte mitteilen, welche von den folgenden Eintr?gen noch >>> ben?tigt werden und ?ber welche Ports sie erreichbar sein m?ssen? Die restlichen >>> Ports werden dann defaultm??ig geblockt. >>> >>> opencsw2.informatik.uni-erlangen.de (131.188.40.75) >>> opencsw2-rsync.informatik.uni-erlangen.de (131.188.40.76) >>> opencsw2-mirror.informatik.uni-erlangen.de (131.188.40.77) >>> opencsw2-pkg.informatik.uni-erlangen.de (131.188.40.78) >>> opencsw2-lom.informatik.uni-erlangen.de (131.188.40.79) >>> opencsw-rsync.informatik.uni-erlangen.de (131.188.40.80) >>> opencsw-new.informatik.uni-erlangen.de (131.188.40.81) >>> opencsw-mirror.informatik.uni-erlangen.de (131.188.40.82) >>> opencsw-pkg.informatik.uni-erlangen.de (131.188.40.83) >>> opencsw-lom.informatik.uni-erlangen.de (131.188.40.84) >>> >>> Aktuell sind folgende Regeln bei uns hinterlegt: >>> >>> permit tcp 213.178.77.170 131.188.40.79 22 >> Das ist korrekt - wird f?r das Monitoring gebraucht. >>> permit tcp 213.178.77.178 131.188.40.79 22 >> Das ist auch korrekt - das ist mein Service-SSH-Zugang von der Buildfarm hier. >>> Ist das ausreichend? >> ?ffentlich f?r alle brauchen wir zum runterladen der Pakete ?ber HTTP, HTTPS und rsync >> 131.188.40.82 >> fe80::8:20ff:fe7c:9466/10 >> auf den Ports 80, 443 und 873. >> Von der Buildfarm aus 213.178.77.176 m?ssen noch Pakete pushen, das ist per SSH und rsync auf die 131.188.40.82. >> Ich hoffe, das sind alle. Sonst m?ssen wir noch einmal schauen. Die 131.188.40.75 brauchen wir auch ?ber Port 22 von der 213.178.77.178 aus. Ansonsten m?ssen wir da halt mal probieren - Du kannst ja mal ein paar Eintr?ge auskommentieren. Viele Gr??e ? Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896 From raffeck at cs.fau.de Wed Jun 24 10:05:11 2026 From: raffeck at cs.fau.de (Phillip Raffeck) Date: Wed, 24 Jun 2026 10:05:11 +0200 Subject: [aods] Re: ACLs opencsw In-Reply-To: References: <93512b38-dcd9-466e-97d1-fce523a21b05@cs.fau.de> Message-ID: <7271ad38-de87-4e05-bb1b-e6c2ba5668b1@cs.fau.de> Hallo Dago, danke f?r die schnelle Antwort. > ?ffentlich f?r alle brauchen wir zum runterladen der Pakete ?ber HTTP, HTTPS und > rsync > 131.188.40.82 > fe80::8:20ff:fe7c:9466/10 > auf den Ports 80, 443 und 873. Das ist ne link-local IPv6-Adresse. Die IPv6-Adresse von opencsw- mirror.informatik.uni-erlangen.de ist 2001:638:a000:4140::ffff:82. Ich vermute mal, die war gemeint und hab sie auch so eingetragen. Nur nochmal zur Sicherheit: Dies restlichen DNS-Eintr?ge sind nicht mehr in Benutzung und k?nnen bei Bedarf entfernt werden? Viele Gr??e Phillip On 23-06-2026 9:49 AM, Dagobert Michelsen wrote: > Hallo Phillip, > >> Am 19.06.2026 um 14:43 schrieb Phillip Raffeck : >> k?nntest du uns bitte mitteilen, welche von den folgenden Eintr?gen noch >> ben?tigt werden und ?ber welche Ports sie erreichbar sein m?ssen? Die restlichen >> Ports werden dann defaultm??ig geblockt. >> >> ?opencsw2.informatik.uni-erlangen.de (131.188.40.75) >> ?opencsw2-rsync.informatik.uni-erlangen.de (131.188.40.76) >> ?opencsw2-mirror.informatik.uni-erlangen.de (131.188.40.77) >> ?opencsw2-pkg.informatik.uni-erlangen.de (131.188.40.78) >> ?opencsw2-lom.informatik.uni-erlangen.de (131.188.40.79) >> ?opencsw-rsync.informatik.uni-erlangen.de (131.188.40.80) >> ?opencsw-new.informatik.uni-erlangen.de (131.188.40.81) >> ?opencsw-mirror.informatik.uni-erlangen.de (131.188.40.82) >> ?opencsw-pkg.informatik.uni-erlangen.de (131.188.40.83) >> ?opencsw-lom.informatik.uni-erlangen.de (131.188.40.84) >> >> Aktuell sind folgende Regeln bei uns hinterlegt: >> >> ?permit tcp 213.178.77.170 131.188.40.79 22 > > Das ist korrekt - wird f?r das Monitoring gebraucht. > >> ?permit tcp 213.178.77.178 131.188.40.79 22 > > Das ist auch korrekt - das ist mein Service-SSH-Zugang von der Buildfarm hier. > >> Ist das ausreichend? > > ?ffentlich f?r alle brauchen wir zum runterladen der Pakete ?ber HTTP, HTTPS und > rsync > ? 131.188.40.82 > ??fe80::8:20ff:fe7c:9466/10 > auf den Ports 80, 443 und 873. > > Von der Buildfarm aus?213.178.77.176 m?ssen noch Pakete pushen, das ist per SSH > und rsync auf die?131.188.40.82. > > Ich hoffe, das sind alle. Sonst m?ssen wir noch einmal schauen. > > > Vielen Dank > > ? ? Dago > > > -- > "You don't become great by trying to be great, you become great by wanting to do > something, > and then doing it so hard that you become great in the process." - xkcd #896 > From raffeck at cs.fau.de Thu Jun 25 09:51:46 2026 From: raffeck at cs.fau.de (Phillip Raffeck) Date: Thu, 25 Jun 2026 09:51:46 +0200 Subject: [aods] ACLs opencsw In-Reply-To: References: <93512b38-dcd9-466e-97d1-fce523a21b05@cs.fau.de> <7271ad38-de87-4e05-bb1b-e6c2ba5668b1@cs.fau.de> Message-ID: <57c1ccfd-7014-4753-9b82-db0d5b5c527d@cs.fau.de> Hallo Dago, On 24-06-2026 6:45 PM, Dagobert Michelsen wrote: > Hallo Phillip, > >> Am 24.06.2026 um 10:05 schrieb Phillip Raffeck : >> danke f?r die schnelle Antwort. >> >>> ?ffentlich f?r alle brauchen wir zum runterladen der Pakete ?ber HTTP, HTTPS und >>> rsync >>> 131.188.40.82 >>> fe80::8:20ff:fe7c:9466/10 >>> auf den Ports 80, 443 und 873. >> >> Das ist ne link-local IPv6-Adresse. Die IPv6-Adresse von opencsw- >> mirror.informatik.uni-erlangen.de ist 2001:638:a000:4140::ffff:82. Ich vermute >> mal, die war gemeint und hab sie auch so eingetragen. > > Ah, okay, ja. > >> Nur nochmal zur Sicherheit: Dies restlichen DNS-Eintr?ge sind nicht mehr in >> Benutzung und k?nnen bei Bedarf entfernt werden? > > > >> >> Viele Gr??e >> Phillip >> >> On 23-06-2026 9:49 AM, Dagobert Michelsen wrote: >>> Hallo Phillip, >>>> Am 19.06.2026 um 14:43 schrieb Phillip Raffeck : >>>> k?nntest du uns bitte mitteilen, welche von den folgenden Eintr?gen noch >>>> ben?tigt werden und ?ber welche Ports sie erreichbar sein m?ssen? Die restlichen >>>> Ports werden dann defaultm??ig geblockt. >>>> >>>> opencsw2.informatik.uni-erlangen.de (131.188.40.75) >>>> opencsw2-rsync.informatik.uni-erlangen.de (131.188.40.76) >>>> opencsw2-mirror.informatik.uni-erlangen.de (131.188.40.77) >>>> opencsw2-pkg.informatik.uni-erlangen.de (131.188.40.78) >>>> opencsw2-lom.informatik.uni-erlangen.de (131.188.40.79) >>>> opencsw-rsync.informatik.uni-erlangen.de (131.188.40.80) >>>> opencsw-new.informatik.uni-erlangen.de (131.188.40.81) >>>> opencsw-mirror.informatik.uni-erlangen.de (131.188.40.82) >>>> opencsw-pkg.informatik.uni-erlangen.de (131.188.40.83) >>>> opencsw-lom.informatik.uni-erlangen.de (131.188.40.84) >>>> >>>> Aktuell sind folgende Regeln bei uns hinterlegt: >>>> >>>> permit tcp 213.178.77.170 131.188.40.79 22 >>> Das ist korrekt - wird f?r das Monitoring gebraucht. >>>> permit tcp 213.178.77.178 131.188.40.79 22 >>> Das ist auch korrekt - das ist mein Service-SSH-Zugang von der Buildfarm hier. >>>> Ist das ausreichend? >>> ?ffentlich f?r alle brauchen wir zum runterladen der Pakete ?ber HTTP, HTTPS und rsync >>> 131.188.40.82 >>> fe80::8:20ff:fe7c:9466/10 >>> auf den Ports 80, 443 und 873. >>> Von der Buildfarm aus 213.178.77.176 m?ssen noch Pakete pushen, das ist per SSH und rsync auf die 131.188.40.82. >>> Ich hoffe, das sind alle. Sonst m?ssen wir noch einmal schauen. > > Die 131.188.40.75 brauchen wir auch ?ber Port 22 von der 213.178.77.178 aus. Hab ich aufgenommen. > > Ansonsten m?ssen wir da halt mal probieren - Du kannst ja mal ein paar Eintr?ge auskommentieren. Alles klar. Sobald die neuen ACLs aktiv sind, sind sie ja dann eh erstmal nicht erreichbar. Falls feststeht, dass bestimmte Domains gar nicht mehr ben?tigt werden, gerne bei uns Bescheid geben, damit wir da etwas aufr?umen k?nnen. Viele Gr??e Phillip From raffeck at cs.fau.de Fri Jun 26 17:14:35 2026 From: raffeck at cs.fau.de (Phillip Raffeck) Date: Fri, 26 Jun 2026 17:14:35 +0200 Subject: [i4server] =?utf-8?q?Einschr=C3=A4nkung_Erreichbarkeit_VLAN_40_ab_1=2E7=2E?= Message-ID: <9454dd80-cd42-4f8a-8677-3a99757de5e3@cs.fau.de> Hallo zusammen, wir haben eure gew?nschten Portfreigaben ans RRZE weitergeleitet. Ab 1.7. wird der restliche Traffic von au?en ins VLAN 40 geblockt. Falls doch noch weitere Freigaben n?tig sind, gerne einfach jederzeit per aods at cs.fau.de erfragen. Falls ihr DNS-Eintr?ge irgendwann einmal nicht mehr ben?tigt, freuen wir uns, wenn ihr uns das mitteilt, damit wir die Eintr?ge entsprechend wegr?umen k?nnen. Viele Gr??e Phillip -- i4server mailing list -- i4server at lists.informatik.uni-erlangen.de To unsubscribe send an email to i4server-leave at lists.informatik.uni-erlangen.de