l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
December 2: Social Gathering
Next Installfest:
TBA
Latest News:
Nov. 18: Officers elected
Page last updated:
2004 Jul 15 11:11
Events
 Meetings
 Installfests
 Demos
 Photos
Services
 Library
 LERT
 Jobs
 Documents
Interact
 Mailing Lists
 - Search
 - Archives
 Chat (IRC)
 Social Networks
About Us
 Members
 Projects
 Testimonials
 Call for Speakers
 Why Not MS?
 Finances
 Sponsors

^Home
?Search
?News & RSS
?Calendar
@Contact Us
$Buy Stuff
=Printable


The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] SSH Auth keys via PuTTY
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] SSH Auth keys via PuTTY



On Thu, Jul 15, 2004 at 10:36:16AM -0700, Bill Kendrick wrote:
> 
> Hi, I've been given an account on a server to do some volunteer webmastering,
> and was asked to provide my SSH public key.
> 
> Since I'm currently on dialup via WindowsXP at home (*sigh*) [*], I'm
> SSH'ing in through PuTTY.
> 
> I downloaed "puttygen.exe", which can generate various kinds of
> public/private key combinations.  I created a 1024bit SSH2 DSA key pair,
> and save the public and private keys to disk.  I grabbed the contents of the
> public key and sent it to the server's administrator, who presumely did
> whatever needs to be done with it...
> 
> I then created a PuTTY session to connect to that host via SSH, and
> told it to use my private key.  (Connection->SSH->Auth->Private key file...)
> 
> Unfortunately, despite everything seeming 'proper' on my end, I have been
> unable to connect.  I know very little about this (on either end; client or
> server), and don't know _precisely_ what he's done on the server, but I'm
> going under the assumption that he knows what he's doing, since he's done it
> for other users.
> 
> 
> The error that PuTTY seems to be throwing back is:
> 
>   Server refused our key
>   No supported authentication methods left to try!
> 
> 
> Any ideas?!  (I know, it's a long-shot :^) )

No ideas for you to try. *They* should make sure that
${BILLS_HOME}/.ssh/authorized_keys is chmodded to 0644. SSH will
refuse to accept any key in an authorized_keys file that is group or
world writeable (even if you're the only person in the group). This is
a security feature that protects an attacker from sticking a new key
into the file and gaining access to your account that way.

-- 
I usually have a GPG digital signature included as an attachment.
See http://www.gnupg.org/ for info about these digital signatures.
My key was last signed 10/14/2003. If you use GPG *please* see me about 
signing the key. ***** My computer can't give you viruses by email. ***

Attachment: signature.asc
Description: Digital signature

_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


LinkedIn
LUGOD Group on LinkedIn
facebook
LUGOD Group on Facebook

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
1105 Kennedy Place, Suite 1, Davis, CA 95616
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
nerdbooks.com
For numerous book donations.