similar to: OpenSSH on Reliant UNIX

Hi ! To all: A Happy New Year ! During the last week I did some investigations why the X11 forwarding on Reliant UNIX Versions 5.44 and 5.45 does not work out of the box with OpenSSH-2.3.0p1. The result fo my investigation is: 1. The OpenSSH sshd opens a TCP/IP-port 6000 + display number and listens to it. This is fine and works with Solaris 7, DEC-OSF 4.0D, Linux and FreeBSD-4.2 but not

Hi ! I promised to report the result to the list. Here it is: Damien Miller [SMTP:djm at mindrot.org] wrote yesterday on his keyboard: > On Mon, 8 Jan 2001, Bladt Norbert wrote: [...] >> During the last week I did some investigations why the X11 forwarding >> on Reliant UNIX Versions 5.44 and 5.45 does not work out of the box >> with OpenSSH-2.3.0p1. >> >> The

Damien Miller [SMTP:djm at mindrot.org] wrote: > On Mon, 8 Jan 2001, Bladt Norbert wrote: [...] >> The result fo my investigation is: >> 3. All standard X-applications try to determine whether >> they are running locally, i.e. if the DISPLAY on >> computer HOSTX is HOSTX:10.0 the X-applications detect >> that this is the local computer and try to open the

Hi ! I upgraded one of our Reliant UNIX systems from 2.1.1 to 2.3.0p1. Now, I suddenly can't login any more. The error message is: Attempting authentication for illegal user ... The reason is: Password expiration Although I don't use my password to login, at all. I login via RSAAuthentication and this did work with version 2.1.1. Version 2.3.0p1, obviously, checks the password

Hello ! I think a problem was introduced in openssh-2.3.0p1 which is still there in the latest openssh-2.5.2p1. I just noticed it before my vacation and could not send this mail earlier than today. The problem is: You can't use the Rhosts-RSA authentication based on the hosts.equiv file and the host keys. The only possible way to do rhosts-RSA authentication is to allow the usage of the

Hi ! Karsten Thygesen wrote: >>>>> "carl" == carl <carl at bl.echidna.id.au> writes: > carl> Marc, I'm seeing the same problem if I use the inbuilt entropy > carl> generator, but if I use SUNWski's /dev/random, it's fine. > carl> ssh also coredumps if I use the built in entropy generator if I > carl> run it in verbose mode.

> John Horne [SMTP:J.Horne at plymouth.ac.uk] wrote: > > Emanuel Borsboom <emanuel at heatdeath.org> wrote: >> Trying to install the portable OpenSSH on Solaris 2.6. Compiling from >> openssh-2.1.0.tar.gz using gcc. Compiles and installs fine. sshd >> starts fine. First connection from another system works. Child sshd is >> forked, but the parent dies

> Andre Lucas [SMTP:andre.lucas at dial.pipex.com] wrote: > > No! The error message is because I used 'error()' instead of 'debug()'. > That's changed in the 2.1.0p1 release, I believe. (I don't have access > to it right now.) This was discussed last week for 2.1.0 - just change > error() to debug() for those two messages. Sorry, you are completely right.

Joe Warren-Meeks [SMTP:joe at hole-in-the.net] wrote: > open("/usr/local/etc/ssh_prng_cmds", O_RDONLY) = 3 open of the command file succeeded. > brk(0x000E6DB8) = 0 "malloc" in user land, i.e. sshd > brk(0x000E8DB8) = 0 "malloc" in user land, i.e. sshd > fstat64(3, 0xFFBEECD8)

> jeff at ntcor.com [SMTP:jeff at ntcor.com] wrote: > > I have a ssh enabled server and client machine (we'll call them "server" > and "client" respectively...) OK :-) > They both have proper RSA and DSA keys,using protocol version 2 works > fine between them. (so ssh itself and the network is working fine) OK. > However, I want to get something that

Hi! I am resending the following message about problems with utmp handling. * In the meantime I had some request in private mail from people asking whether I have new information. * The problem is still persistant in 2.9p2. * My own new investigations show, that the problem only appears with protocol 2, not with protocol 1, I therefore only started to note it when protocol 2 became the

Hi all, I'm not on the list but I thought it might interest some of you to know that openssh 2.2.0p1 compiles quite well under sco5. Although not right out of the box. I'm not using gcc on those platforms, so I had to change the call to gettimeofday() because the sco cc want only one of the two arguments (SCO doesn't care with timezone). So I had to modify those files to get it work:

Hello, I'm unsure what kind of problem this is, but If I use eval $(ssh-agent) ssh-add scp ... (several times) ssh-add -D exit There are many ssh processes around in the system: UID PID PPID C STIME TTY TIME COMMAND root 4266 1 0 11:33:56 pts/0 0:00 /usr/local/bin/ssh -x -oFallBack ToRsh no -oFallBackToRsh no root 1876 9788 0 11:11:26 ? 0:01

This to announce a test release of 2.1.0p1 before making it widely available. This release includes many fixes to problems reported over the last week. In particular: - spurious error and coredumps caused by the inbuilt entropy gathering - RSAref detection - Compilation fixes for Solaris and others It also contains (completely untested) support for compiling without RSA support. This may be

Hi, stevesk at sweden.hp.com wrote: > Has any progress been made on this issue? I've included an older > message that has a stack trace, which if I recall was still the same in > 2.1.1p1. I can provide a newer trace or additional information if > needed. not really... On a non-trusted system with HP AnsiC it seems to work if changing shutdown(fdin, SHUT_WR) to shutdown(fdin,

comments? alternatives: sigsetjmp(ugly) and pselect(not portable, available) drawback: additional filedescriptors. Index: serverloop.c =================================================================== RCS file: /home/markus/cvs/ssh/serverloop.c,v retrieving revision 1.82 diff -u -r1.82 serverloop.c --- serverloop.c 10 Oct 2001 22:18:47 -0000 1.82 +++ serverloop.c 11 Oct 2001 18:06:33 -0000 @@

Hi, attached please find some patches for ReliantUNIX. This was tested under Reliant UNIX V5.43C40 with Compiler CDSDEV V2.0C00. Here is what I did: - there is a common misunderstanding how to use /usr/libucb/libucb.a: There are some library functions only in libucb.a under ReliantUNIX, so one needs to bind it. The problem is: there are some other functions in this library you should never

Howdy, After upgrading to 2.9 (OpenSSH_2.9p1, SSH protocols 1.5/2.0, OpenSSL 0x0090600f) I'm unable to ssh between two systems any more (the two that I've upgraded). I've recompiled from the original source several times, each time with no errors, regenerated host keys, regenerated client keys (using rsa), etc., to no avail. Below are some relevant snippets of debugging output

No response yet, so resending. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords ---------- Forwarded message ---------- Date: Fri, 12 Oct 2001 09:44:54 +0300 (EEST) From: Pekka Savola <pekkas at netcore.fi> To: Damien Miller

Hi! I am distributing 2.5.1p1 for production use on my system by now and prepare switching to protocol 2 as default protocol. I just noted, that ssh-agent can be used for protocol 1 and 2, but the keys kept in ssh-agent are not compared against keys in .ssh. Example: I have a DSA key in id_dsa which I load into ssh-agent on login. When connecting to an account accepting the key everything is