search for: id_dsa

Hi. If I submit patches that make the prompts look more like prompts, would those patches be welcome? Before: ecashin at nilda ecashin$ ssh-add ~/.ssh/id_dsa Need passphrase for /home/ecashin/.ssh/id_dsa Enter passphrase for /home/ecashin/.ssh/id_dsa After (model 1): ecashin at nilda ecashin$ ssh-add ~/.ssh/id_dsa Need passphrase for /home/ecashin/.ssh/id_dsa Enter passphrase for "/home/ecashin/.ssh/id_dsa": After (model 2): ec...

...h-keymanager\" will help you to do that." echo "" echo " - It generates your public/private \"DSA\" keys using ssh-keygen. They" echo " are encrypted on disk using DES, via your passphrase. The keys will" echo " be saved in ~/.ssh as \"id_dsa\" and \"id_dsa.pub\"." echo " Your public DSA key will get the name \"${USER}-id_dsa.pub\" which is" echo " a copy of \"id_dsa.pub\"". echo "" echo " - The \"${USER}-id_dsa.pub\" will be added to \"~/.ssh/...

...it asks for my password and once I'm logged in, it performs ls and quits again. So why does it still read the authorized_keys file since I deleted the key ? I looked into it a bit further and I found that the public key file on my client is the one messing up. If I rename it (by default, it is id_dsa.pub) then everything works fine (password authentication and then I'm logged in with a shell). It seems somehow that the public key file is read no matter what and compares it to the keys found in authorized_keys. So bug or not ? Thanks for your answers. #######################################...

I have a problem in ssh login without password Systems: vmware-centos 5.2: 192.168.0.4 vista copssh: 192.168.0.2 [192.168.0.4 $] ssh-keygen -t dsa [192.168.0.4 $] scp -p id_dsa.pub tester at 192.168.0.2:.ssh [192.168.0.2 $] cat .ssh/id_dsa.pub >> .ssh/authorized_keys [192.168.0.2 $] chmod 700 .ssh [192.168.0.2 $] chmod 600 .ssh/authorized_keys [192.168.0.4 $] ssh id at 192.168.0.2 Permission denied (publickey). But with password, I can connect to 192.168.0.2. Th...

I've been running ssh-clients-2.3.0p1-4 on RedHat 7.0 and upgraded to 2.5.1p2-1 yesterday from ftp://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/rpm/SRPMS/. I noticed that 2.5.1p2-1 ssh-add won't look for id_dsa.pub by default -- if I have no identity file it just says "/home/klotz/.ssh/identity: No such file or directory" The 2.5.1p1-1 I got from RedHat's rawhide site *does* look for it. Is this a RedHat patch? It works if I explicitly specify /home/klotz/.ssh/id_dsa.pub I looked in ssh-...

...ftp from a 2.9.9p2 client, connecting to a F-Secure 2.4.0 server, but consistently get the following. debug1: authentications that can continue: hostbased,publickey,password debug1: next auth method to try is publickey debug1: try privkey: /path/acct/.ssh/id_rsa debug1: try pubkey: /path/acct/.ssh/id_dsa debug1: authentications that can continue: hostbased,publickey,password debug1: next auth method to try is password acct at remotehostsftp's password: Entering the password allow access. But I'm trying to authenticate with having to enter a password. The remote host has a copy of the pub...

...1p1 Platform: All OS/Version: All Status: NEW Severity: major Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org ReportedBy: pepper at rockefeller.edu As a test, I made a private key world readable. Note that id_dsa is a symlink to this key. When I tried to ssh without a running agent, ssh complained about permissions and said it would ignore this key, but then prompted me for its passphrase. If I'm understanding correctly, this is a failure of a security feature. Note that this is the OpenSSH currently s...

...one machine has been exchanged to another machine and a normal user issues, from the first machine, ssh -l root machine2, The normal user on machine one will be logged in as root on machine2. Steps to recreate: On Machine #1: 1. Make yourself root 2. ssh-keygen -b 2048 -t dsa 3. scp .ssh/id_dsa.pub root at machine2:/root (you must enter a password at this point) 4. exit the root shell to normal shell On Machine #2: 1. Make yourself root 2. cat id_dsa.pub >>.ssh/authorized_keys2 3. logout On Machine #1: (note, you should be a normal user now.) 1. ssh -l root machine2 2....

I'd like to propose a couple of tweaks to ssh-copy-id: o Change the default ID_FILE from identity.pub to id_dsa.pub or perhaps {id_dsa,id_rsa,identity}.pub to cover all the bases, although the patch below deals only with id_dsa.pub - it would need some more tweaking to deal with more than one (possibly non-existent) file. o If the destination authorized_keys file already contains the keys, they shou...

Can some point out what is wrong here? I get the follwing error with code structure in puppet. err: Could not create /root.ssh/id_dsa: You cannot specify more than one of content, source, target at /manifests/classes/set-root.pp # # set root files # class common-root { file { "/root/.ssh/id_dsa": mode => 600, owner => root, gr...

installed freenx server on CentOS 4 server installed nxclient from nomachine.com on workstation so far so good. following directions from web site... http://fedoranews.org/contributors/rick_stout/freenx/ where I tried both /etc/nxserver/client/client.id_dsa.key and /var/lib/nxserver/home/.ssh/client.id_dsa.key copied them to my workstation and then used the 'import' function in nxclient to import the keys and try to connect and always get the following detail when I failed to connect... NX> 203 NXSSH running with pid: 21106 NX> 285 Ena...

...responding to a SSH private key is not in ~/.ssh and public key authentication fails, ssh will ask for your key's password, even if it is has already been added to ssh-agent. Steps to Reproduce: 1. Place a SSH private key with an associated password in ~/.ssh/. 2. Remove the corresponding .ssh/id_dsa.pub file. 3. SSH somewhere where the public key is authorized. 4. SSH somewhere where the public key is unauthorized. Expected Results: The public key authentication fails. Actual Results: A prompt appears requesting your key password. Regression: The password prompt does not appear if public-ke...

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 fine. If the key is not accepted, slogin will not recognize that the key was already tried from ssh-agent and will ask me again to enter the password to unlock the key (for another failure). This is...

On Mac OS, in order to allow ssh using dsa keys, I would copy ~/.ssh/id_dsa.pub from my machine into ~/.ssh/authorized_keys of the target machine. I've created .ssh directories in my account home as well as in /root and copied the respective keys to authorized_keys files in each. Strangely, I can now ssh as root with no password but my own user account still promp...

...red with: --prefix=/usr/local/openssh --enable-gnome-askpass --with-tcp-wrappers --with-ipv4-default --with-ipaddr-display My goal here is to, as root, forward a local privileged port over an ssh tunnel to another host using a normal user's login, i.e.: root:# ssh -2 -l jamesb -i ~jamesb/.ssh/id_dsa -L 26:localhost:25 remotehost So far, I am finding it impossible or impractical to do this. Am I doing something wrong? Here's a description of my experiences: 1) First I tried it as shown above, specifying the unprivileged user's key on the command line with the -i switch. But for som...

http://bugzilla.mindrot.org/show_bug.cgi?id=884 Summary: DSA keys (id_dsa.pub) with 8192 bytes or more aren't correctly recognized Product: Portable OpenSSH Version: 3.8.1p1 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: ssh...

http://bugzilla.mindrot.org/show_bug.cgi?id=884 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO|822 |914 nThis| | ------- You are receiving this mail because: ------- You are the assignee for

http://bugzilla.mindrot.org/show_bug.cgi?id=884 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #663 is|0 |1 obsolete| | ------- Additional Comments From dtucker at zip.com.au 2004-10-29 22:03 -------

http://bugzilla.mindrot.org/show_bug.cgi?id=884 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Additional Comments From dtucker at zip.com.au 2004-12-06

http://bugzilla.mindrot.org/show_bug.cgi?id=884 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED ------- Additional Comments From dtucker at zip.com.au 2005-03-10 09:07 ------- With the release of OpenSSH 4.0, these bugs