It seems this thread made its way onto usenet, and I reproduce the
text of an email exchange that resulted:
> On Wed, Mar 19, 2003 at 02:37:21PM +1100, (somebody) wrote:
> > Hi Pigeon,
> >
> > I just read your usenet thread
> > http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=2
* Pigeon ([EMAIL PROTECTED]) [030215 20:05]:
> So, I rename 'identity' to 'id_rsa' and try again... IT WORKS!!! Huh?
> The authorized_keys on the host still ends in
> '/home/pigeon/.ssh/identity', which doesn't exist on either machine.
Well, this is unsurprising. The last field of a public key li
On Sat, Feb 15, 2003 at 08:50:29PM -0500, jereme wrote:
> Pigeon <[EMAIL PROTECTED]> writes:
> > Since protocol 1 is now working, I'm not too bothered about 2 not
> > working, but it would be nice to fix it purely on the grounds of not
> > liking to have broken stuff around especially when it works
On Sat, Feb 15, 2003 at 12:40:08PM -0800, Vineet Kumar wrote:
> * Pigeon ([EMAIL PROTECTED]) [030215 11:03]:
> > Since protocol 1 is now working, I'm not too bothered about 2 not
> > working, but it would be nice to fix it purely on the grounds of not
> > liking to have broken stuff around especial
Pigeon <[EMAIL PROTECTED]> writes:
> Since protocol 1 is now working, I'm not too bothered about 2 not
> working, but it would be nice to fix it purely on the grounds of not
> liking to have broken stuff around especially when it works for
> everyone else!
I see in your first message you combed th
* Pigeon ([EMAIL PROTECTED]) [030215 11:03]:
> On Sat, Feb 15, 2003 at 11:28:12PM +0800, Sukanta Kumar Hazra wrote:
> > Hi!
> >
> > copy th id_dsa key to .ssh/authorized_keys2 and make sure the
> > permission mode is 600. ssh2 would work then.
> >
> > - Sukanta
>
> Thanks - but unfortunately, it
On Sat, Feb 15, 2003 at 11:28:12PM +0800, Sukanta Kumar Hazra wrote:
> Hi!
>
> copy th id_dsa key to .ssh/authorized_keys2 and make sure the
> permission mode is 600. ssh2 would work then.
>
> - Sukanta
Thanks - but unfortunately, it doesn't.
There was a previous thread on this, from Jan 19, co
On Sat, Feb 08, 2003 at 11:31:12PM -0800, Vineet Kumar wrote:
> * Pigeon ([EMAIL PROTECTED]) [030208 20:16]:
> > > > debug3: Not a RSA1 key file /root/.ssh/id_rsa.
> > (and the same for id_dsa)
> >
> > Looking in these files, I find they don't look right compared to the
> > id_?sa.pub files. The .
* Pigeon ([EMAIL PROTECTED]) [030208 20:16]:
> > > debug3: Not a RSA1 key file /root/.ssh/id_rsa.
> (and the same for id_dsa)
>
> Looking in these files, I find they don't look right compared to the
> id_?sa.pub files. The .pub files contain "ssh-rsa fv487t509n0etcetcetc=
> root@pigeon" all as one
On Fri, Feb 07, 2003 at 10:38:17PM -0700, Tim Ayers wrote:
> When you generate your keys and it asks for a passphrase, just hit
> . Don't use a passphrase and it won't prompt you for one.
No, that's how I did it. It's not asking for a passphrase, it's asking
for a password, just as if I had no ke
heya,
are you sure your sshd_config is configured to allow PubkeyAuthentication?
sean
On Sat, Feb 08, 2003 at 12:03:22AM +, Pigeon wrote:
> Hi,
>
> I'm trying to set up ssh to enable passwordless logins from
> 192.168.1.1 to 192.168.1.2. I have used ssh-keygen to generate key
> pai
Hi,
I'm trying to set up ssh to enable passwordless logins from
192.168.1.1 to 192.168.1.2. I have used ssh-keygen to generate key
pairs for root on 192.168.1.1 and copied the .pub files into
/root/.ssh/authorized_keys. According to man ssh, as I understand it,
this should be enough to get passwor
12 matches
Mail list logo
