similar to: Private key files closed twice --

NOTE: If you know how to properly use load_private_key for dsa keys and NOTE: don't want to read my long post, simply reply with that info and NOTE: I will really appreciate it. thanks. I've been playing with the source code and trying to create extra apps. All has been going well except the fact that I can't load a dsa private key. To highlight my problem I stole some code

Hello, I am going through the source of openssh-3.9p1 and I have a quick question on how the sshd daemon loads the host keys. In the default configuration of SSH2 protocol, the private DSA hostkey is found in the file 'ssh_host_dsa_key' and the public DSA hostkey counterpart in 'ssh_host_dsa_key.pub'. Likewise, the private and public RSA hostkeys are found in

I get error: %SSHD-3-ERROR: Could not load host key: /tmp/ssh_host_dsa_key: Bad file descriptor Jan 26 23:58:52: %SSHD-6-INFO: Disabling protocol version 2. Could not load host key Everything looks okay, the file exists, (it was generated using command: ssh-keygen -d -f ssh_host_dsa_key -N '') I also do 'ls' and find the file exists with permissions: -rw------- 1 root group

The patch below does two things. 1. If invoked with no arguments, attempt to add both RSA and DSA keys. 2. Remember the last successful passphrase and attempt to use it on subsequent key files which are added. Note that the latter part of the patch extends the period of time during which the passphrase is held in clear text in the ssh-add process, but doesn't introduce any _new_

Hi ALL, Can you please help me on how to determine the prediction error for ordinary kriging?Below are all the commands i used to generate the OK plot: rsa2 <- readShapeSpatial("residentialsa", CRS("+proj=tmerc +lat_0=39.66666666666666 +lon_0=-8.131906111111112 +k=1 +x_0=0 +y_0=0 +ellps=intl +units=m +no_defs")) x2 <- readShapeSpatial("ptna2",

Hey All, Can anyone tell me what the following message implies? What does PEM_read_PrivateKey do and why would it fail? This is the result of trying to setup ssh for autologin. Though I follow the man page, it doesn't work. debug1: PEM_read_PrivateKey failed Thanks, Bill Rees More Debug Output ========== debug2: service_accept: ssh-userauth debug1:

Hello, I'm having a problem with my ssh client, on FreeBSD 5.4 and 6.1 the same issue. OpenSSH_3.8.1p1 FreeBSD-20040419, OpenSSL 0.9.7e 25 Oct 2004 but also same problem with OpenSSH_4.3 When I make a key, everything goes fine. When I try to change the password on the key it give me the 'PEM_read_PrivateKey failed' problem, this also prevents me from connecting to another host.

http://bugzilla.mindrot.org/show_bug.cgi?id=806 Summary: openssh after 3.6.1p1 can not authenticate via public rsa2 key Product: Portable OpenSSH Version: 3.8p1 Platform: HPPA OS/Version: HP-UX Status: NEW Severity: major Priority: P2 Component: ssh AssignedTo: openssh-bugs at

This (very quick) patch allows you to connect with the commercial ssh.com windows client and use x509 certs for hostkeys. You have to import your CA cert (ca.crt) in the windows client and certify your hostkey: $ cat << 'EOF' > x509v3.cnf CERTPATHLEN = 1 CERTUSAGE = digitalSignature,keyCertSign CERTIP = 0.0.0.0 [x509v3_CA]

Hello, Would it be possible to add generic engine support to OpenSSH? One use in particular would be to support TCP forwarding for secure mail server connections and similar applications. This would permit an administrator to configure in an arbitrary external engine to establish a secure RSA-based tunnel. OpenSSH would need no information built into it to accomodate any particular engine. One

--On Friday, May 08, 2015 09:58:32 AM -0400 "James B. Byrne" <byrnejb at harte-lyne.ca> wrote: > While attempting to debug something else I ran across this: > > ssh -vvv somehost > . . . > debug1: Connection established. > debug1: permanently_set_uid: 0/0 > debug1: identity file /root/.ssh/identity type -1 > debug1: identity file /root/.ssh/identity-cert

Devin Reade wrote: > --On Friday, May 08, 2015 09:58:32 AM -0400 "James B. Byrne" > <byrnejb at harte-lyne.ca> wrote: > >> While attempting to debug something else I ran across this: >> >> ssh -vvv somehost >> . . . >> debug1: Connection established. >> debug1: permanently_set_uid: 0/0 >> debug1: identity file /root/.ssh/identity

On Fri, May 8, 2015 13:23, m.roth at 5-cent.us wrote: > Devin Reade wrote: >> --On Friday, May 08, 2015 09:58:32 AM -0400 "James B. Byrne" >> <byrnejb at harte-lyne.ca> wrote: >> >>> While attempting to debug something else I ran across this: >>> >>> ssh -vvv somehost >>> . . . >>> debug1: Connection established.

Can anybody help me with this : ? I first generated rsa key with this : ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key then I went on to generate the DSA key too....(just incase my SSHD does not like RSA). ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key and then I ran root at 00_00_09_PECA_NP1:/usr/bin# sshd -d -d -d -d -d -d -d -d -d debug3: RNG is ready, skipping seeding debug2:

Executive summary: Why can I not have a private key which is `public' ? Gory details .... I'm new to openssh. I've been using ssh for years. However, I'm in the process of investigating RH 7.* (0.91 at the moment) and am wanting to be as `standard' as possible, so trying openssh. I looked on http://www.openssh.com/list.html but could not find a list for "general

The manual page for ssh-keygen says: "For RSA1 keys, there is also a comment field in the key file this is only for convenience to the user to help identify the key." It seems though that RSA2 and DSA keys also have comment fields, not just RSA1. Is this just an error in the documentation? Also the documentation says that only RSA1 key comments can be changed with ssh-keygen's

Guys, I think that I have ran into a bug. I am running openbsd 2.8 and I upgraded to the lastest verison of openssh 2.9 but when I did that it started giving me this error "ssh_exchange_identification: Connection closed by remote host" when I try to log into the machine even when I am on the machine and try to ssh localhost it gives me the same message. I have read every FAQ I could find

Hi, I'm trying to figure out how to read OpenSSH's log files (to assist our people in diagnosing "why is it always asking me for passwords"). All clients and servers are 3.0p1. First: server does not have the client's RSA2 key in known_host. debug1: done: ssh_kex2. debug1: send SSH2_MSG_SERVICE_REQUEST debug1: service_accept: ssh-userauth debug1: got

Hi, I'm trying to compile openssh2.3.0p1 on aix3.2.5. Can I ignore this list of warning messages? bsd-bindresvport.c: In function `bindresvport_af': bsd-bindresvport.c:94: warning: implicit declaration of function `bind' bsd-rresvport.c: In function `rresvport_af': bsd-rresvport.c:64: warning: implicit declaration of function `bzero' bsd-rresvport.c:82: warning: implicit

This is just portable todo list. From the sounds of it Markus has his own to do list. But can everyone review and let me know if there is anything missing from this list. (Note.. I'm not looking for 'SSH should support XYZ feature.' unless it's directly related to portability.) Or if there is anything on this list that has been completed. (Namely Tru64 SIA support?) Thanks.