Scot L. Harris wrote:
My question was, if the known_hosts file is hashed how do you identify the entry for the particular host so it can be removed when needed?
The warning message tells you the line number of the entry in the known_hosts file:
Add correct host key in /home/rmy/.ssh/known_hosts to get rid of this message. Offending key in /home/rmy/.ssh/known_hosts:22 RSA host key for localhost has changed and you have requested strict checking. Host key verification failed.
Ron
Whenever I try to use gpg to encrypt a single file on CentOS 4.2, I get the below error:
/root/.gnupg/.#lk0x56a998.localhost.localdomain.19548': No such file or directory gpg: keyblock resource `/root/.gnupg/secring.gpg': general error gpg: failed to create temporary file `/root/.gnupg/.#lk0x56aca8.localhost.localdomain.19548': No such file or directory gpg: keyblock resource `/root/.gnupg/pubring.gpg': general error gpg: no default secret key: secret key not available gpg: /home/ra/Desktop/zoo001.jpg: sign+encrypt failed: secret key not available
It happens for normal and root users.
Does anyone know what I am doing wrong? I've tried "gpg -e [filename]" and numerous other flags...
thanks
On Sun, Mar 12, 2006 at 08:35:42AM -0500, ryan enlightened us:
Whenever I try to use gpg to encrypt a single file on CentOS 4.2, I get the below error:
/root/.gnupg/.#lk0x56a998.localhost.localdomain.19548': No such file or directory gpg: keyblock resource `/root/.gnupg/secring.gpg': general error gpg: failed to create temporary file `/root/.gnupg/.#lk0x56aca8.localhost.localdomain.19548': No such file or directory gpg: keyblock resource `/root/.gnupg/pubring.gpg': general error gpg: no default secret key: secret key not available gpg: /home/ra/Desktop/zoo001.jpg: sign+encrypt failed: secret key not available
It happens for normal and root users.
Does anyone know what I am doing wrong? I've tried "gpg -e [filename]" and numerous other flags...
Have you generated a private key? (hint: gpg --genkey)
Also, I seem to remember gpg not creating the .gnupg directory on its own, so you might want to create one with pretty strict permissions (700) since that's where the private key is stored.
Matt
That was it, thanks. gpg --gen-key was erroring out and I wasn't paying close attention.
On Sunday 12 March 2006 8:35 am, Matt Hyclak wrote:
Also, I seem to remember gpg not creating the .gnupg directory on its own, so you might want to create one with pretty strict permissions (700) since that's where the private key is stored.
/root/.gnupg/.#lk0x56a998.localhost.localdomain.19548': No such file or directory gpg: keyblock resource `/root/.gnupg/secring.gpg': general error gpg: failed to create temporary file `/root/.gnupg/.#lk0x56aca8.localhost.localdomain.19548': No such file or directory gpg: keyblock resource `/root/.gnupg/pubring.gpg': general error gpg: no default secret key: secret key not available gpg: /home/ra/Desktop/zoo001.jpg: sign+encrypt failed: secret key not available
Since it says secret key not available, I'd assume you either haven't set up a gpg keypair, or your user can't read your keypair for some reason.
-- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety'' Benjamin Franklin 1775
On 3/12/06, Ron Yorston rmy@tigress.co.uk wrote:
Scot L. Harris wrote:
My question was, if the known_hosts file is hashed how do you identify the entry for the particular host so it can be removed when needed?
The warning message tells you the line number of the entry in the known_hosts file:
Add correct host key in /home/rmy/.ssh/known_hosts to get rid of this message. Offending key in /home/rmy/.ssh/known_hosts:22 RSA host key for localhost has changed and you have requested strict checking. Host key verification failed.
They also add a "-F hostname" option to ssh-keygen that searches known_hosts for lines matching a particular hostname (whether hashed or not).
Josh Kelley
-
Jim Perrin -
Josh Kelley -
Matt Hyclak -
Ron Yorston -
ryan