search for: d_wllms

Here's what I get: bash-2.02# sshd -ddd -p 1234 debug3: Seeding PRNG from /usr/local/libexec/ssh-rand-helper debug1: sshd version OpenSSH_3.5p1 debug1: private host key: #0 type 0 RSA1 debug3: Not a RSA1 key file /etc/ssh/ssh_host_rsa_key. debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug3: Not a RSA1 key file /etc/ssh/ssh_host_dsa_key. debug1: read PEM

second time, is there anybody that can tell me where I can send contributions to the man pages? Dom <<small addition to the scp man page>> -------------- next part -------------- An embedded message was scrubbed... From: "Cressatti, Dominique" <Dominique.Cressatti at lansa.co.uk> Subject: small addition to the scp man page Date: Mon, 9 Sep 2002 13:37:41 +0100 Size:

Is this a known issue? (ignore the pervasive MS-outlook capitalization) Ssh-agent /bin/ksh Ssh-add /root/.ssh/id_rsa Blah blah Ssh -vvv some_server date ... debug1: ssh_rsa_verify: signature correct debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: Enabling compression at level 6. debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1:

Hi, Suppose my backup server has to copy every day at the end of the night, all files from the Web Server. So every day I will have a script that copies files using SCP. I USE HP-UX . But this script must work without anyone entering passwords. I know that SCP will need Passwords. How can I make a script with this feature ? Using keygen ? If posssible, describe with details how

...lding portable to support quite a few Unices and have relyed on the snapshots for my source. Do I need to switch my efforts to building off of the source from CVS?? DW -- David M. Williams Phone: 505-665-5021 Systems Engineer, CCN-2 Fax: 505-667-7428 Los Alamos National Laboratory Email: d_wllms at lanl.gov

...most certain that the posted bogus advisory was also intended to cause alarm amongst communities using OpenSSH, through miss-information. Global InterSec LLC. -- David M. Williams, CISSP Phone: 505-665-8062 Systems Engineer, CCN-2 Fax: 505-667-7428 Los Alamos National Laboratory Email: d_wllms at lanl.gov

Remote users on external networks unable to connect to the host using F-Secure SSH from their workstations. The Host is installed with openssh-3.4p1 from IBM. Previously the host was installed with F-Secure 1.2.26 and there wasn't any problems. What can we do. I've checked in the sshd_config file and the AllowHosts and Allow Users tags are in there with the host ips and usernames that

We are heading into a lock here. So we need to get people to test their respective platforms if they wish them to be supported out of the tar file. So if you have any patches you need to ensure your platform works speak up. We are looking at a lock on the 17th. I believe I have an AIX/Cray patch and a Tru64 patch sitting in my mailbox that I'll be looking at soon and more than likely

Is it possible to use encryption only for authenticate and then switch to no encryption? I've looked at the code for OpenSSH 3.5p1, cipher.c, and it looks like the answer is no, at least for protocol 1. However, I cannot tell if that is a deliberate design limitation of the implementation or if it is inherent in ssh protocol 2. My dilemma is a customer who wants to use their network IDS

Hi. Solaris packages created by buildpkg.sh don't create privsep user or group and sshd won't start until they are created (or privsep is disabled): ## Executing postinstall script. starting /usr/local/sbin/sshd... Privilege separation user sshd does not exist /etc/init.d/opensshd: Error 255 starting /usr/local/sbin/sshd... bailing. The attached patch (against -cvs) ports the relevant

OpenBSD tree is heading into a lock and this includes OpenSSH. So we are winding up for a 3.5 release. If we can get people to test the current snapshots and report any problems that would improve the odds that your platform won't be broke for 3.5. Issues I know off of right now. 1. I can't test NeXT. So I TRULY need someone in that community to test for me. Last I heard there was

Hey All, Found a very minor problem with client implementation of KerberosTgtPassing command line flag in ssh.c (first diff). We also made some readability patches to the config files and manpages to make the option clearer (the remainder of the diffs). diffs are against -current Index: ssh.c =================================================================== RCS file: