From: Martin Galvan <martin.galvan@tallertechnologies.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: overseers@sourceware.org, hp@bitrange.com
Subject: Re: Lost SSH key
Date: Wed, 02 Mar 2016 14:00:00 -0000 [thread overview]
Message-ID: <CAOKbPbYna0LsweNJUKx66H3HRbwH0f42hreuMVgAhBzrwOb19g@mail.gmail.com> (raw)
In-Reply-To: <20160302135136.GQ53794@elastic.org>
On Wed, Mar 2, 2016 at 10:51 AM, Frank Ch. Eigler <fche@elastic.org> wrote:
> Hi -
>
> On Wed, Mar 02, 2016 at 10:28:30AM -0300, Martin Galvan wrote:
>> [...]
>> -rw------- 1 martin-galvan martin-galvan 1766 feb 25 16:31 id_rsa
>> -rw-r--r-- 1 martin-galvan martin-galvan 381 mar 1 15:14 id_rsa.pub
>
> That looks weird; those two files should have apprx. the same
> timestamp. Did you generate -two- sets of keys recently, or some
> other way intermix public & private keys?
Good point. Both files were generated at the same time; what happened
is that I later removed the user@host at the end of id_rsa.pub just in
case that was causing the issue.
next prev parent reply other threads:[~2016-03-02 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 19:52 Martin Galvan
2016-02-26 0:36 ` Ian Lance Taylor
2016-03-01 18:15 ` Martin Galvan
2016-03-02 4:47 ` Ian Lance Taylor
2016-03-02 5:34 ` Hans-Peter Nilsson
2016-03-02 6:00 ` Ian Lance Taylor
2016-03-02 13:29 ` Martin Galvan
2016-03-02 13:51 ` Frank Ch. Eigler
2016-03-02 14:00 ` Martin Galvan [this message]
2016-03-02 14:37 ` Martin Galvan
-- strict thread matches above, loose matches on Subject: below --
2021-03-11 8:59 Robin Dapp
2019-07-08 13:43 Andrew Sutton
2019-07-08 13:53 ` Carlos O'Donell
2012-02-22 14:54 Lost ssh key Ed Smith-Rowland
2012-02-22 16:10 ` Ian Lance Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOKbPbYna0LsweNJUKx66H3HRbwH0f42hreuMVgAhBzrwOb19g@mail.gmail.com \
--to=martin.galvan@tallertechnologies.com \
--cc=fche@elastic.org \
--cc=hp@bitrange.com \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).