- WLUG - wlug.mailman3.com

Re: [Wlug] ssh known_hosts

by frank p

Is '10.14.36.204' your client or your server? First reaction is that you should just replace the old ip with the new one in the known_hosts file, though maybe it's no that simple. It could be that either your client doesn't want to connect to a server it doesn't know about, or your server doesn't want to accept connections from a client it doesn't know about. It could be changes needed in your ~/.ssh/known_hosts on the client or /etc/ssh/ssh_known_hosts on the server. Can you be a little more explicit about exactly what you are trying to do? Maybe include output from doing a 'ssh -v <host/ip>'... np, -poz On Tue, 27 Apr 2004, Bill Mills-Curran wrote: > I'm having a problem with known (or unknown!) hosts since changing the > IP address on a server. > > Server info: > Redhat 8.0 > ssh -V: OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f > > Client info: > Redhat 9 > ssh -V: OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f > > When logging into the server, I'm getting the following message: > > RSA host key for IP address '10.14.36.204' not in list of known hosts. > > I've played around with ~/.ssh/known_hosts (even renaming it), but I > still get the message. Looking at the documentation for the > known_hosts file format (in sshd man page), my current known_hosts > file, looks quite a bit different (many fields are omitted). > > Why do I get the message, and how do I get rid of it? > > TIA, > Bill

April 27, 2004

ssh known_hosts

by Bill Mills-Curran

I'm having a problem with known (or unknown!) hosts since changing the IP address on a server. Server info: Redhat 8.0 ssh -V: OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f Client info: Redhat 9 ssh -V: OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f When logging into the server, I'm getting the following message: RSA host key for IP address '10.14.36.204' not in list of known hosts. I've played around with ~/.ssh/known_hosts (even renaming it), but I still get the message. Looking at the documentation for the known_hosts file format (in sshd man page), my current known_hosts file, looks quite a bit different (many fields are omitted). Why do I get the message, and how do I get rid of it? TIA, Bill

April 27, 2004

Re: [Wlug] test

by gma2004＠verizon.net

Bill Smith wrote: > > > What were you testing? > New email address. Wanted to make sure I was still here and see who it said I was. Greg

April 26, 2004

Re: [Wlug] test

by Bill Smith

On Fri, 23 Apr 2004 17:27:06 -0400 gma2004(a)verizon.net wrote: > test What were you testing? -- William Smith wsmith(a)chezsmith.com Fall River, MA

April 26, 2004

Re: [Wlug] PGP Keysigning

by gma2004＠verizon.net

Theo, Thanks. No, I didn't import revoke.asc, and your suggestion worked. Next step is to figure out encryption. Greg Theo Van Dinter wrote: > On Fri, Apr 23, 2004 at 05:39:38PM -0400, gma2004(a)verizon.net wrote: > >>I did gpg --fingerprint >> >>When I do gpg --list-sigs, my new key is listed as revoked. Did I screw >>up on following the first set of directions? > > > It depends. Did you do something like "gpg --import revoke.asc" ? > If so, you revoked your public key. The last version of your key that I > saw on the keyserver isn't revoked, so ... You could, in theory, go in, > delete your public key from your keyring, then do a recv-key to download > the non-revoked one. > > > more info on revoking in: http://www.hackdiary.com/archives/000042.html, > http://www.gnupg.org/(en)/documentation/faqs.html#q4.17 >

April 24, 2004

Re: [Wlug] PGP Keysigning

by gma2004＠verizon.net

OK, I guess that older key is really mine. I was able to change the password, but I'm still not sure about how to handle this. If I do use this older key, how do I change the email address on it? Is adduser the correct command for this? Would it make more sense to revoke that one and make a new one? Greg gma2004(a)verizon.net wrote: > I got as far as 'Really sign?' and then it didn't like my passphrase. > > I did gpg --fingerprint > > It seems that I already have a key that I allegedly made in December 2003. I don't remember doing this, and I don't understand how I could have done it without going through the procedure that we all just used this week. > > When I do gpg --list-sigs, my new key is listed as revoked. Did I screw up on following the first set of directions? > > I tried putting the new key ID in the default key line of my options file, and when I try to sign someone's key, I get the message > gpg: no default secret key: unusable secret key > > Any suggestions on what to do? > > Thanks > > Greg Avedissian

April 23, 2004

Re: [Wlug] PGP Keysigning

by Theo Van Dinter

On Fri, Apr 23, 2004 at 05:39:38PM -0400, gma2004(a)verizon.net wrote: > I did gpg --fingerprint > > When I do gpg --list-sigs, my new key is listed as revoked. Did I screw > up on following the first set of directions? It depends. Did you do something like "gpg --import revoke.asc" ? If so, you revoked your public key. The last version of your key that I saw on the keyserver isn't revoked, so ... You could, in theory, go in, delete your public key from your keyring, then do a recv-key to download the non-revoked one. more info on revoking in: http://www.hackdiary.com/archives/000042.html, http://www.gnupg.org/(en)/documentation/faqs.html#q4.17 -- Randomly Generated Tagline: "At least it had heated rear windows--so your hands would stay warm while you pushed." - Unknown about the Yugo

April 23, 2004

Re: [Wlug] PGP Keysigning

by gma2004＠verizon.net

I got as far as 'Really sign?' and then it didn't like my passphrase. I did gpg --fingerprint It seems that I already have a key that I allegedly made in December 2003. I don't remember doing this, and I don't understand how I could have done it without going through the procedure that we all just used this week. When I do gpg --list-sigs, my new key is listed as revoked. Did I screw up on following the first set of directions? I tried putting the new key ID in the default key line of my options file, and when I try to sign someone's key, I get the message gpg: no default secret key: unusable secret key Any suggestions on what to do? Thanks Greg Avedissian Charles R. Anderson wrote: > To complete the PGP Keysigning process: > > 1. Sign All The Verified IDs On The Verified Keys > > gpg --keyserver pgp.mit.edu --recv-keys <Key_ID> > gpg --sign-key <Key_ID> > > [ Verify the fingerprint against your sheet. You probably want to select > (3) I have done very careful checking in this case, since we > met in person and verified physical photo ID's. ] > > 2. Send The Signed Keys Back Up To The Designated Keyserver > > gpg --keyserver pgp.mit.edu --send-key <Key_ID> > > Finally, once everyone has signed everyone else's keys and sent them > to the keyserver, you will want to download the signed versions once > more from the keyserver. You can do this at any time without fear of > overwritting keys--GnuPG will always merge the changes into your local > keyring (--recv-keys) or the remote keyserver (--send-keys) as > necessary. > > 3. Download the Signed Keys from The Designated Keyserver > > gpg --keyserver pgp.mit.edu --recv-key <Key_ID> > > It is a good idea to periodically re-download keys to receive new > signatures, learn of revoked keys, etc. You can tell a signature was > added by the output of --recv-keys. You can list key signatures with: > > gpg --list-sigs [<Key_ID>] > > where <Key_ID> is optional. > > You may notice some keys signed by unknown user ids. If you receive > those keys from the keyserver(s) you can build your Web Of Trust to > include people you don't know. This gets into how much you trust > people with whom you have verified keys directly to sign *other* > people's keys properly/securely. More on this later.... > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > >

April 23, 2004

test

by gma2004＠verizon.net

test

April 23, 2004

Re: [Wlug] PGP Keysigning

by gma2004＠verizon.net

I got as far as Really sign? And then it asked for my passphrase, but I'm not sure it really knows who I am. It has my rcn address, which is not the one I used to create the key. WTF??? What do I do if my passphrase fails? Why is my middle initial missing? Why is my key ID different from what it was when I created it, and how did I create it in 2003? when I do gpg --fingerprint, I get the key I didn't know about, the one I made this week, and one from somebody I don't know and who doesn't appear in my address book (Vincent Danen). When I do gpg --list-sigs, my new key is listed as revoked. Did I screw up on following the first set of directions? Greg Charles R. Anderson wrote: > To complete the PGP Keysigning process: > > 1. Sign All The Verified IDs On The Verified Keys > > gpg --keyserver pgp.mit.edu --recv-keys <Key_ID> > gpg --sign-key <Key_ID> > > [ Verify the fingerprint against your sheet. You probably want to select > (3) I have done very careful checking in this case, since we > met in person and verified physical photo ID's. ] > > 2. Send The Signed Keys Back Up To The Designated Keyserver > > gpg --keyserver pgp.mit.edu --send-key <Key_ID> > > Finally, once everyone has signed everyone else's keys and sent them > to the keyserver, you will want to download the signed versions once > more from the keyserver. You can do this at any time without fear of > overwritting keys--GnuPG will always merge the changes into your local > keyring (--recv-keys) or the remote keyserver (--send-keys) as > necessary. > > 3. Download the Signed Keys from The Designated Keyserver > > gpg --keyserver pgp.mit.edu --recv-key <Key_ID> > > It is a good idea to periodically re-download keys to receive new > signatures, learn of revoked keys, etc. You can tell a signature was > added by the output of --recv-keys. You can list key signatures with: > > gpg --list-sigs [<Key_ID>] > > where <Key_ID> is optional. > > You may notice some keys signed by unknown user ids. If you receive > those keys from the keyserver(s) you can build your Web Of Trust to > include people you don't know. This gets into how much you trust > people with whom you have verified keys directly to sign *other* > people's keys properly/securely. More on this later.... > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > >

April 23, 2004