search for: eosdata

Just as a suggestion, I liked the way the ssh.com's ssh would move the old binaries to filename.old then install the new ones....so that way you have an old copy to revert back to if needed (without copying them all by hand).

I'm observing that mac clients using F-Secure ssh v1 client log into the ssh server, and then the client just hangs with nothing on the screen. In the SYSLOG file, I see this: Accepted password for user from host port whatever Packet integrity error (62 != 58) at session.c:350 Disconnecting: Packet integrity error. (34) This is sshd running on IRIX 6.5.3f

I installed 2.5.1p2 on an irix system and noticed that if a user logged in typed "logname" it was providing the wrong username. File creations were correct, "w" produces the correct output....so something is funky in p2 that wasn't there in p1.

I get this error: cc -o32 -g -I/usr/local/include -I/var/tmp/openssl-o32/include -I/var/tmp/openssl-o32/include -I. -I./openbsd-compat -I. -DETCDIR=\"/usr/local/ssh/etc\" -D_PATH_SSH_PROGRAM=\"/usr/local/ssh/bin/ssh\" -D_PATH_SSH_ASKPASS_DEFAULT=\"/usr/local/ssh/libexec/ssh-askpass\" -D_PATH_SFTP_SERVER=\"/usr/local/ssh/libexec/sftp-server\" -DHAVE_CONFIG_H

Another wonderful email from me. :) The ssh.com version of ssh will log information on the remotely executed command in the syslog: Mar 7 15:29:20 6D:marx sshd[21346]: log: executing remote command as root: ls It seems that openssh doesn't do that by default. If you put the server in debug mode you'll see the command, but a lot of extra stuff that you don't want to see. Feature

I'm now using the openssh-2.5.2p1 version, and the X forwarding on the linux machine is still not working. It's a Redhat 6.2 machine running kernel 2.2.17-14 It doesn't appear to be adding anything to the /tmp/ssh-whatever/cookies file when you log in. I posted some debug info yesterday. Does anyone have some ideas of what I can try next, or is this a known bug?

I had UseLogin enabled....this was breaking the X forwarding code somehow. This is the second OS I've come across that has major difficulties with the UseLogin option.

Is there a new syntax, or procecure for handling specific port forwarding through tcp wrappers (as is done with the ssh.com version)? It looks like someone had a patch back in october, but the source code has changed a lot since then and I'm not sure how to incorporate it. Any help is appeciated.

Hello, I'm running the newest version of Samba on an Irix 6.4 server. One of our NT clients is having a problem. When the user tries to access the server (Start-->Run-->"\\SERVER"), the username/password field comes up. When that user puts in his valid username/password, and error pops up that says "User not authorized to connect from this station." No valid

Another quick Samba question: I've set up 4-5 shared printers. The smb.conf section on them looks like this: [las7] comment = HP LaserJet 4siMX in S181A path = /var/spool/samba postscript = yes printer = las7_direct printable = yes public = yes writable = no create mode = 0700 I want people to be able to print to these printers without having to supply a

Occasionally, we're noticing that sshd is core dumping on our IRIX 6.5.18f machine. The only time we've really noticed it is when users are logging in with putty from offsite (although I'm not really sure it's a client issue). The user manages to log in, sshd apparently core dumps, but the user is not logged out, the privilege separated user is still running their own

I'm logging in from an irix machine to a linux machine (both running openssh-2.5.1p2) and am unable to run any X applications. I ran a verbose session and this happens: debug: fd 6 IS O_NONBLOCK debug: channel 0: new [X11 connection from host port 4572] debug: X11 connection uses different authentication protocol. debug: X11 rejected 0 i1/o16 debug: channel 0: read failed debug: channel 0:

Are there plans, or does someone have a fix, for having openssh force users to change passwords when they're expired? Right now the program closes the connection....the commercial ssh manages to exec /bin/passwd after they enter their current password. Any ideas?