search for: atomicgears

...#else - break; + if (x11_use_localhost) { + if (num_socks == NUM_SOCKS) + break; + } else { + break; + } #endif } freeaddrinfo(aitop); In article <Pine.HPX.4.44.0204301333550.2022-100000 at jenny> (at Tue, 30 Apr 2002 13:35:52 -0700 (PDT)), Kevin Steves <kevin at atomicgears.com> says: > itojun, > > do you have any recommendations on this? > > http://bugzilla.mindrot.org/show_bug.cgi?id=164 > > ---------- Forwarded message ---------- > Date: Mon, 29 Apr 2002 11:32:21 +0200 > From: Stig Venaas <Stig.Venaas at uninett.no> > To:...

In case this hasn't already been reported or discussed... It took some doing for me to get openssh working on HPUX 11i. The fixes are quite simple. First, one must have the IPV6 package installed: em 512# swlist -l product | grep IPV6 IPV6AA A.01.01.5D IPv6 11i product Second, I have to edit config.h to undefine HAVE_GETADDRINFO. Without IPV6, ssh can't connect

Hi everybody, I've never posted here before but I seem to be having a similar problem to what Tim Rice had in July, namely when running the configure script I get the following: configure: error: *** zlib missing - please install first or check config.log *** However, I have definitely installed zlib (see below): dngwks1:/tmp/openssh-3.0p1 # swlist # Initializing... # Contacting target

...t;my $tmp " : :Execution of ./mdoc2man.pl aborted due to compilation errors. : :*** Error exit code 255 it seems your perl is wrong. my guess is configure found /usr/contrib/bin/perl which won't work. also, for HP-UX users: "Building and Installing OpenSSH on HP-UX" http://www.atomicgears.com/papers/osshhpux.html

Hello, I have just installed Openssh 3.1 sur HPUX 11.00. the command ssh-keygen -t dsa -f /opt/openssh2/etc/ssh_host_dsa_key -N "" doesn't stop, it seems waiting some other parameters. How to configure this please. An idea ? Best regards. Gerard breiner gerard.breiner at ias.fr Institut d'Astrophysique spatiale Orsay France

I wasn't paying much attention when there was a lot of conversation about these issues. I recently ran into a problem where an X app won't run with OpensSSH 3.1p1's default "X11UseLocalhost yes" setting. If I run the X app with the display set to "localhost:16.0" it gets a "BadAccess" error, but if I run it with the display set to

And lsof the agent too - see what files it has open... Nico -- > -----Original Message----- > From: Kevin Steves [mailto:kevin at atomicgears.com] > Sent: Friday, August 23, 2002 4:48 PM > To: openssh-unix-dev at mindrot.org > Cc: stevesk at pobox.com > Subject: Re: 3.4p1 ssh-agent auth-retry patch available: was: Re: > Updated ssh-agent authentication retry patch available > > > On Tue, Aug 20, 2002 at 04:42:58...

I gueess it is not a DNS problem, because either using name or IP, I have always the problem. I guess the problem is that I am using ssh on inetd.conf (sshd -i), so It has to generate a key each time I start a session. What do you think ? -----Mensagem original----- De: Dan Kaminsky [mailto:dan at doxpara.com] Enviada em: segunda-feira, 10 de junho de 2002 20:51 Para: Jorge Cleber Teixeira de

No "ssh -X hostname" doesn't work. But when you "export DISPLAY=..." it works!? I set the the Display Hack so that I can see my IP with "env" or "echo SSH_CLIENT" when I'm connect via VPN-Tunnel and I don't know my IP in the Net I'm connected through. Andreas Kerl ----------------------------------------- DTS Medien GmbH Heidestrasse 38

...oering - Munich, Germany > gert at greenie.muc.de > fax: +49-89-35655025 > gert.doering at physik.tu-muenchen.de > > --__--__-- > > Message: 11 > Date: Wed, 24 Jul 2002 16:32:08 +0200 > From: Gert Doering <gert at greenie.muc.de> > To: Kevin Steves <kevin at atomicgears.com> > Cc: Tony Finch <dot at dotat.at>, openssh-unix-dev at mindrot.org, > stevesk at pobox.com > Subject: Re: privilege separation breaks dns lookups > > Hi, > > On Sat, Jun 29, 2002 at 12:38:35PM -0700, Kevin Steves wrote: > > On Wed, Jun 26, 2002 at 11:26:...

OpenBSD tree is heading into a lock and this includes OpenSSH. So we are winding up for a 3.5 release. If we can get people to test the current snapshots and report any problems that would improve the odds that your platform won't be broke for 3.5. Issues I know off of right now. 1. I can't test NeXT. So I TRULY need someone in that community to test for me. Last I heard there was

i'm working on this. this is what i have now. sp_inact is not handled consistently across shadow platforms, so i'm going to not address that right now. the following is the predecessor to bug14. what is the timeframe for 3.2.1p1? markus suggested a few more weeks. Index: auth.c =================================================================== RCS file: /var/cvs/openssh/auth.c,v

We don't currently support SVR4-style fd passing which involves I_SENDFD/I_RECVFD ioctls. I'm not sure if that might help some p platforms with privsep. Some platforms that use STREAMS ptys use a set-uid root helper to handle the privileged portions of pty creation. grantpt(3) has a bit more info. on Solaris 8 it's: /usr/lib/pt_chmod on HP-UX it's: /usr/lbin/chgpt Perhaps this

I would like to remove setsockopt(SO_LINGER), as there does not seem to be a reason for its use. If you know of specific reasons we should keep any of these let me know, or run this patch in local test trees where possible. This is against OpenBSD, but should apply to portable with some fuzz. Index: channels.c =================================================================== RCS file:

is this ok (complete, correct)? Index: INSTALL =================================================================== RCS file: /var/cvs/openssh/INSTALL,v retrieving revision 1.53 diff -u -r1.53 INSTALL --- INSTALL 13 May 2002 05:22:21 -0000 1.53 +++ INSTALL 24 Jun 2002 00:50:20 -0000 @@ -105,11 +105,6 @@ There are a few other options to the configure script: ---with-rsh=PATH allows you to

Hi, This is included in the release now; any feedback? Privilege separation, or privsep, is method in OpenSSH by which operations that require root privilege are performed by a separate privileged monitor process. Its purpose is to prevent privilege escalation by containing corruption to an unprivileged process. More information is available at: