libutil.so.8 - libutil.so.9, WAS: openssh-portable fails to build on ia64, sparc

2010-01-27 Thread Anton Shterenlikht
I didn't get any reply from ports@, so maybe somebody here can help - Forwarded message from Anton Shterenlikht me...@bristol.ac.uk - maybe this has been discussed already, my apologies in that case. on current r203046 I'm trying to rebuild openssh-portable-5.2.p1_2,1 due to an upgrade

Re: libutil.so.8 - libutil.so.9, WAS: openssh-portable fails to build on ia64, sparc

2010-01-27 Thread Jason
...@bristol.ac.uk - maybe this has been discussed already, my apologies in that case. on current r203046 I'm trying to rebuild openssh-portable-5.2.p1_2,1 due to an upgrade from libutil.so.8 to libutil.so.9 I get this error on sparc64 and ia64 (don't have any other arch to check): === Building

Re: libutil.so.8 - libutil.so.9, WAS: openssh-portable fails to build on ia64, sparc

2010-01-27 Thread Anton Shterenlikht
discussed already, my apologies in that case. on current r203046 I'm trying to rebuild openssh-portable-5.2.p1_2,1 due to an upgrade from libutil.so.8 to libutil.so.9 I get this error on sparc64 and ia64 (don't have any other arch to check): === Building for openssh-portable-5.2.p1_2,1 cc

Re: Problem building openssh-portable with KERBEROS, GSSAPI, KERB_GSSAPI.

2008-07-31 Thread Lowell Gilbert
Valeriu Mutu [EMAIL PROTECTED] writes: I am trying to build 'openssh-portable' from ports (security/openssh-portable/) with the following configuration options: PAM=on Enable pam(3) support TCP_WRAPPERS=on Enable tcp_wrappers support LIBEDIT=on Enable readline support

Problem building openssh-portable with KERBEROS, GSSAPI, KERB_GSSAPI.

2008-07-30 Thread Valeriu Mutu
Hi all, I am trying to build 'openssh-portable' from ports (security/openssh-portable/) with the following configuration options: PAM=on Enable pam(3) support TCP_WRAPPERS=on Enable tcp_wrappers support LIBEDIT=on Enable readline support to sftp(1) KERBEROS=on Enable

security/openssh-portable

2008-03-11 Thread Philip M. Gollucci
Hi, I'm setting up a 'chrooted' SFTP only set of users: /etc/make.conf: .if ${.CURDIR:M*/usr/ports/security/openssh-portable*} WITH_SUID_SSH =yes WITH_OPENSSH_CHROOT =yes WITH_HPN =yes WITH_OVERWRITE_BASE =yes .endif /etc/rc.conf: sshd_enable=NO openssh_enable

Re: security/openssh-portable

2008-03-11 Thread Jerry McAllister
On Tue, Mar 11, 2008 at 06:08:44PM -0400, Philip M. Gollucci wrote: Hi, I'm setting up a 'chrooted' SFTP only set of users: /etc/make.conf: .if ${.CURDIR:M*/usr/ports/security/openssh-portable*} WITH_SUID_SSH =yes WITH_OPENSSH_CHROOT =yes WITH_HPN =yes

Re: security/openssh-portable

2008-03-11 Thread Philip M. Gollucci
Feb 2007 debug1: Remote protocol version 1.99, remote software version OpenSSH_4.7p1-hpn12v20 FreeBSD-openssh-portable-overwrite-base-4.7.p1_1,1 debug1: match: OpenSSH_4.7p1-hpn12v20 FreeBSD-openssh-portable-overwrite-base-4.7.p1_1,1 pat OpenSSH* debug2: channel 0: open confirm rwindow 0 rmax

Re: security/openssh-portable

2008-03-11 Thread Jerry McAllister
-openssh-portable-overwrite-base-4.7.p1_1,1 debug1: match: OpenSSH_4.7p1-hpn12v20 FreeBSD-openssh-portable-overwrite-base-4.7.p1_1,1 pat OpenSSH* debug2: channel 0: open confirm rwindow 0 rmax 32768 Request for subsystem 'sftp' failed on channel 0

Can't get openssh-portable to use PAM

2007-05-21 Thread Matt Bostock
Hi all, I'm using security/openssh-portable to provide chroot-ssh, but would now also like to enable PAM for SSH so that I can take advantage of OPIE in certain scenarios. I've compiled openssh-portable with the PAM option (and something PAM-related flashes by during 'configure'), and have

Openssh-portable

2007-03-20 Thread Jeffrey Meyer
Hello all, I recently installed the port openssh-portable. Since then I receive the following when attempting to ssh into the box: Permission denied (publickey). I believe that I am getting this because sshd is attempting to use public key authentication, but I don't want to use

Openssh-portable

2007-03-20 Thread Jeffrey Meyer
Hello all, I recently installed the port openssh-portable. Since then I receive the following when attempting to ssh into the box: Permission denied (publickey). I believe that I am getting this because sshd is attempting to use public key authentication, but I don't want to use

Re: Openssh-portable

2007-03-20 Thread Jeremy Gransden
On 3/20/07, Jeffrey Meyer [EMAIL PROTECTED] wrote: Hello all, I recently installed the port openssh-portable. Since then I receive the following when attempting to ssh into the box: Permission denied (publickey). I believe that I am getting this because sshd is attempting to use public key

Re: error installing openssh-portable

2005-04-12 Thread Redmond Militante
case. [Tue, Mar 29, 2005 at 09:14:07AM -0500] This one time, at band camp, Lowell Gilbert said: Redmond Militante [EMAIL PROTECTED] writes: hi all i get this installing the openssh-portable port on a 4.8-RELEASE machine === Building

Re: error installing openssh-portable

2005-03-31 Thread Redmond Militante
said: Redmond Militante [EMAIL PROTECTED] writes: hi all i get this installing the openssh-portable port on a 4.8-RELEASE machine === Building for openssh-portable-3.9.0.1,1 if test ! -z ; then /usr/bin/perl5 ./fixprogs ssh_prng_cmds ; fi (cd openbsd-compat

Re: error installing openssh-portable

2005-03-30 Thread Lowell Gilbert
: hi all i get this installing the openssh-portable port on a 4.8-RELEASE machine === Building for openssh-portable-3.9.0.1,1 if test ! -z ; then /usr/bin/perl5 ./fixprogs ssh_prng_cmds ; fi (cd openbsd-compat make) cc -o ssh ssh.o readconf.o clientloop.o sshtty.o

Re: error installing openssh-portable

2005-03-29 Thread Lowell Gilbert
Redmond Militante [EMAIL PROTECTED] writes: hi all i get this installing the openssh-portable port on a 4.8-RELEASE machine === Building for openssh-portable-3.9.0.1,1 if test ! -z ; then /usr/bin/perl5 ./fixprogs ssh_prng_cmds ; fi (cd openbsd-compat make) cc -o ssh ssh.o

Re: error installing openssh-portable

2005-03-29 Thread Redmond Militante
all i get this installing the openssh-portable port on a 4.8-RELEASE machine === Building for openssh-portable-3.9.0.1,1 if test ! -z ; then /usr/bin/perl5 ./fixprogs ssh_prng_cmds ; fi (cd openbsd-compat make) cc -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o

error installing openssh-portable

2005-03-28 Thread Redmond Militante
hi all i get this installing the openssh-portable port on a 4.8-RELEASE machine === Building for openssh-portable-3.9.0.1,1 if test ! -z ; then /usr/bin/perl5 ./fixprogs ssh_prng_cmds ; fi (cd openbsd-compat make) cc -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect1.o

Re: can't connect after update to openssh-portable 3.6.1p2-5

2003-09-27 Thread Dag-Erling Smørgrav
Jon Noack [EMAIL PROTECTED] writes: [...] I am not responsible for the OpenSSH ports. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send

can't connect after update to openssh-portable 3.6.1p2-5

2003-09-26 Thread Jon Noack
On 4.8-RELEASE-p10 machines I can't connect after updating to openssh-portable 3.6.1p2-5. Updating steps: 1) cvsup 2) portupgrade -ar 3) /usr/local/bin/rc.d/sshd.sh stop 4) /usr/local/bin/rc.d/sshd.sh start This worked fine on 5.1-RELEASE-p8 machines and has worked for several years now (since

Re: can't connect after update to openssh-portable 3.6.1p2-5

2003-09-26 Thread Jon Noack
the ChallengeResponseAuthentication line. This effectively turns on PAM, according to the sshd_config man page. This solution did not work for 4.8-RELEASE-p10 (same messages logged as above). I have tried portupgrade -rRf openssh-portable, by the way. So it seems the PAM fix broke password authentication when

Re: can't connect after update to openssh-portable 3.6.1p2-5 [RESOLVED with update to 3.7.1p2]

2003-09-26 Thread Jon Noack
This was resolved with the update to 3.7.1p2. Jon Noack Jon Noack wrote: On 4.8-RELEASE-p10 machines I can't connect after updating to openssh-portable 3.6.1p2-5. Updating steps: 1) cvsup 2) portupgrade -ar 3) /usr/local/bin/rc.d/sshd.sh stop 4) /usr/local/bin/rc.d/sshd.sh start