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=20030208053009%246b20%40gated-at.bofh.it&rnum=10&prev=/groups%3Fq%3D%2522debug1%2522%2B%2522try%2Bpubkey:%2522%2B%2522.ssh/id_dsa%2522%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3D20030208053009%25246b20%2540gated-at.bofh.it%26rnum%3D10 > > > > I had the _exact_ same problem as you. After reading the thread and > > doing the same things I have it working as well. If you wouldn't have > > posted this message, I would not have it working at all. > > > > You should document it perhaps? There would be many people out there who > > would appreciate it. It's certainly a problem with ssh-keygen / sshd not > > allowing the keys to be terminated with [EMAIL PROTECTED], but allowing a > > non-existing file. > > > > Thanks a lot > Pigeon wrote: > > So it got onto usenet? Wow, I had no idea. It was on the debian-user > list ([EMAIL PROTECTED]) that I posed the question > originally. > > I'm glad you found it useful! > > There's not much point in me documenting it as I don't have a website > on which to publish the documentation. However, there are various > people on debian-user who maintain FAQs and lists of helpful hints > etc, so I shall pass the suggestion on. (Having removed your personal > details, of course.) > > According to Vineet, who was my debian-user mentor on this, the > termination of the key is supposed to be a comment, so it shouldn't > make any difference whether it's an address or a nonexistent file. The > fact that this is not the case on your system as well as mine suggests > to me that I should also file a bug against sshd. I am reluctant to file bugs in case I end up wasting the developers' time over something which is actually my brain not working or a peculiarity of my setup. Since there are evidently other people having the same problem, does the list feel I should go ahead? And are any FAQ-writers interested in (somebody)'s suggestion? Pigeon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
