similar to: installation procedure

x11-ssh-askpass version 1.2.4 (code name: Boudin) is now available from the following locations: http://www.poboxc.com/~jmknoble/software/x11-ssh-askpass/ http://www.ntrnet.net/~jmknoble/software/x11-ssh-askpass/ x11-ssh-askpass is a passphrase dialog for use with OpenSSH <http://www.openssh.com/> under the X Window System. Significant changes since version 1.2.2 include: - Minor

x11-ssh-askpass version 1.2.4 (code name: Boudin) is now available from the following locations: http://www.poboxc.com/~jmknoble/software/x11-ssh-askpass/ http://www.ntrnet.net/~jmknoble/software/x11-ssh-askpass/ x11-ssh-askpass is a passphrase dialog for use with OpenSSH <http://www.openssh.com/> under the X Window System. Significant changes since version 1.2.2 include: - Minor

I've got RedHat 7.1 and when I downloaded the SRPM for openssh-2.9p2-1.src.rpm and tried to rpm --recompile it bombed. Here's the error message that it generated: + pushd x11-ssh-askpass-1.2.0 /usr/src/redhat/BUILD/openssh-2.9p2/x11-ssh-askpass-1.2.0 /usr/src/redhat/BUILD/openssh-2.9p2 + xmkmf -a imake -DUseInstalled -I/usr/X11R6/lib/X11/config make Makefiles Makefile:1052: *** target

Greetings - I don't think this is a bug; just something I don't understand. I'm using RedHat Linux v7.0 with an i686 processor. I've been using openssl v0.9.5a with openssh v2.2.1 I've upgraded to openssl v0.9.6b and openssh v2.9.p2 I've built both packages with the '--prefix=/usr' option. During the openssh 'make install' at 'host-key' I get

OK. I've had a few replies to my earlier question about auth agent forwarding that indicate that it is currently supported. So now I'm confused as to why it is not working for me. I'm trying to chain between servers. With v1 I could load my key into the ssh-agent on my workstation (a) and ssh to server b and ssh from there to server c, all without typing a passphrase/password. Now

Hi, I'm having a real difficulty here, and I'll keep this very short; ask for needed details. I've got two nearly identically configured RedHat 8 systems, call them A and B. I've generated keys with passphrases on both, added the public key for B to ~/.ssh/authorized_hosts on A and vice versa. On either machine, I can use ssh-agent with no problems. In particular, if I run

Could someone familear with the OpenBSD tree please point me to nanoslep. scp.c now uses it and it's not in all plattorms so we'll ethier have to add one to openbsd-compat or ifdef that chunk. Thanks. -- Tim Rice Multitalents (707) 887-1469 tim at multitalents.net

I have compiled openssh for sun solaris 2.6, no errors When I try to run SSHD daemon it says the following error. This platform does not support both privilege separation and compression Compression disabled Privilege separation user sshd does not exist Any one that have answer to this problem mail me on daniel.d.olsson at telia.se <mailto:daniel.d.olsson at telia.se> //Daniel

hints? -------------- next part -------------- An embedded message was scrubbed... From: Markus Friedl <msfriedl at cip.informatik.uni-erlangen.de> Subject: Why we can't login ? Date: Thu, 19 Apr 2001 09:18:02 +0200 (MET DST) Size: 4357 Url: http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20010419/b433827e/attachment.mht

IRIX64 6.5 01101245 IP27 20010425 CVS - (djm) Include crypt.h if available in auth-passwd.c cc-1143 cc: ERROR File = /usr/include/crypt.h, Line = 38 Declaration is incompatible with "void des_encrypt(unsigned long *, struct des_ks_struct *, int)" (declared at line 150 of "/usr/local/ssl/include/openssl/des.h"). extern void des_encrypt(char *, int);

I'm confused about the status of auth agent forwarding while using v2 protocols. I found an old newsgroup post that said it was not available but an entry in the ChangeLog entry dated 20001113 seems to indicate that it was added. So. Does agent forwarding work while using v2 protocols? I've been unable to get it to work since I switched to using v2. Thanks, Ben -- Ben Beuchler

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I note that ssh-askpass-gnome was moved into the contrib/ directory of portable OpenSSH and the configure option for it (--with-gnome-askpass) was removed. I can understand not wanting a configure option for one particular askpass program, but it would be useful to have a general replacement, as in % ./configure

Does OpenSSH support using a different --prefix at runtime? I have different customers installing ssh in different locations, and I'd really prefer to maintain one build for them, and only have them change their runtime environment as appropriate. Usually, the order is 1. Is --prefix defined on the command line? If not, 2. Is prefix defined via an environment variable? If not, 3. Use

Can somebody install an attachment filter on the listserv? Please? -- John Hardin <johnh at aproposretail.com> Internal Systems Administrator voice: (425) 672-1304 Apropos Retail Management Systems, Inc. fax: (425) 672-0192 ----------------------------------------------------------------------- "Rather than form a

My libcrypto does dynamic library linking (dlopen(), etc) and consequently prerequires libdl. I.e. if you link with -lcrypto, you must also specify -ldl. I don't know how unique this situation is to me, but it causes configure to fail. The symptom is that configure complains that libcrypto does not exist (because it does a test link to test for existence of libcrypto and assumes that any

Hi All, Where do I get ssh-keygen (1 and 2) free downloads? How are RSA-1, RSA-2 and DSA-2 related to ssh-keygen1 and ssh-keygen2? Thanks Amarpal.

Hi all, I want to configure Kerberos as the authenticating service for Secure Shell.I am using a Linux machine as the KDC. I have successfully configured the server (Linux machine) as KDC. My client machine is HP-UX Version 11.11. Now when i initialize the client for kerberos by running "kinit" in the HP-UX machine(client), it displays "kinit: Time is out of bounds

Is there a way to change the default no-argument behavior of ssh-add from adding $HOME/.ssh/identity to another type? Thanks, Eric

Hello everyone, As some of you may know, I maintain a patch that puts a '.' chroot hack into OpenSSH. Unfortunately users seem to have had trouble applying the patch. This is because I use gnu's patch and diff and many systems come with a patch and diff that doesn't seem to understand -u or -N. Anyway... the point of this email is to ask if anyone had any objections to me

Currently, openssh's PAM service name is a compile-time choice. That's fine when one uses one sshd to serve normal shell logins and the like. But this will not work IF sshd is nor run as root (which I don't want it to do), because pam_open_session usually requires access to one's shadow information (for account expiration perhaps?), and there is no way (and need: this sshd is