similar to: Why we can't login ? (fwd)

fyi http://wwwcip.informatik.uni-erlangen.de/~msfriedl/openssh/TODO

[See my comments below.] ----- Forwarded message from an x11-ssh-askpass customer ----- Date: Fri, 30 Mar 2001 16:34:28 -0800 Subject: x11-ssh-askpass 1.2.0 To: jmknoble at jmknoble.cx I just installed x11-ssh-askpass 1.2.0 on some systems, and ran into a couple of minor problems: OpenSSH 2.5.2p2 by default is looking for ssh-askpass in /usr/local/libexec, not /usr/local/libexec/openssh. It

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

The INSTALL file in the current distribution has the passphrase request at http://www.ntrnet.net/~jmknoble/software/x11-ssh-askpass/index.html maybe this should be changed to http://www.liquidmeme.net/software/x11-ssh-askpass ?? -- Antonino Iannella Santos Ltd 91 King William St ADELAIDE SA 5000 Ph +618 8224 7712 Fax +618 8224 7577 Mobile +61408 800007 Email antonino.iannella at

I would like to put a patch in OpenSSH start lbxproxy on the server if both ends of the connection support LBX. I'm having difficulty figuring out where to put this code, specifically I can't seem to find where the X11 handshaking happens. Could someone help me out on this?? -Carl

x11-ssh-askpass version 1.0.1 is now available from the following locations: http://www.jmknoble.cx/software/x11-ssh-askpass/ http://www.ntrnet.net/~jmknoble/software/x11-ssh-askpass/ x11-ssh-askpass is a passphrase dialog for use with OpenSSH (www.openssh.com) under the X Window System. The important changes since version 1.0 are as follows: - Bugfixes: - If the keyboard or

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

https://bugzilla.mindrot.org/show_bug.cgi?id=1550 Summary: Move from 3DES to AES-256 for private key encryption Product: Portable OpenSSH Version: 5.1p1 Platform: All OS/Version: All Status: NEW Keywords: patch Severity: enhancement Priority: P2 Component: ssh-keygen AssignedTo:

Makefile.in is not fixed ! in old ssh.h # define SSH_ASKPASS_DEFAULT "/usr/X11R6/bin/ssh-askpass" in new pathnames.h #define _PATH_SSH_ASKPASS_DEFAULT "/usr/X11R6/bin/ssh-askpass" but in Makefile.in PATHS=...-DSSH_ASKPASS_DEFAULT=\"$(ASKPASS_PROGRAM)\" ----------------------------------------------------------- about patch: - remove unused defines:

Is there a risk associated with having authorized_keys files set to readable but "StrictMode no"? I am thinking particularly in the case of having public keys all centralized in a directory in /etc or something. Is it really a potential hack vector if someone can read a public key, or is the only real danger if they were writable? --- Don Hoover dxh at yahoo.com

x11-ssh-askpass version 1.2.1 (code name: Fatoomsh) is now available from the following locations: http://www.jmknoble.cx/software/x11-ssh-askpass/ http://www.ntrnet.net/~jmknoble/software/x11-ssh-askpass/ x11-ssh-askpass is a passphrase dialog for use with OpenSSH (www.openssh.com) under the X Window System. The important changes since version 1.2.1 are as follows: - Added a

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

https://bugzilla.mindrot.org/show_bug.cgi?id=69 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |djm at mindrot.org Alias| |generalised-askpass -- Configure bugmail:

Hi, I noticed one small possible error in the openssh-2.3.0p1/contrib/redhat/sshd.init script. In the stop option: stop) echo -n "Shutting down sshd: " if [ -f $PID_FILE ] ; then killproc sshd [ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/sshd fi echo

https://bugzilla.mindrot.org/show_bug.cgi?id=1586 Summary: [FEATURE REQ] PermitRootLogin and restricting to specific hosts Product: Portable OpenSSH Version: 5.2p1 Platform: amd64 OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: Miscellaneous

could someone please review this change? http://131.188.30.102/~msfriedl/openssh/SSHD_AUTH_PATCH is a diff against openbsd's cvs and will commited ASAP. the patch tries to unify various challenge/response methods in ssh1 and ssh2. faking s/key is dropped, since i am not sure what do do for faking cryptocard and other challenge/response methods. -markus

IF ssh is a replacement for rlogin,rsh etc I can accept it respecting rlogin=false as rlogin does and rsh does not, however scp is a replacement for rcp, and rcp does NOT use rlogin attribute, so the implementation is NOT standard as scp fails if rlogin=false, but rcp succeeds, as documented. thanks mark

hello, i'm building a solaris package of openssh 2.5.1 for my employer. my configure string is this: ./configure --prefix=/usr/share/jon --with-xauth=/usr/openwin/bin/xauth --with-ipv4-default --with-tcp-wrappers --with-pid-dir=/etc --sysconfdir=/etc i use a prefix of /usr/share/jon , then build the system V package from there. most things work great, but somehow scp does not. it seems

Hello, I have been having issues with x11 forwarding using my linux-mandrake based servers. I checked my XAUTHORITY variable and it was set to ~/.Xauthority ... After reading the mail archives, I found the /tmp/ssh* directory created during my ssh session, and did this: export XAUTHORITY="/tmp/ssh-hzuA1805/cookies" xeyes ...and the X11 forwarding worked! I'm using the