[QCLUG] Server admin

[Mark Overholser Jr]

---------------------- multipart/alternative attachment
You should eliminate the ",1" from the protocol line, leaving only "Protocol
2" so that it will only accept connections that use the more secure SSH2
protocol. There were vulnerabilities identified in the original protocol,
and most (if not all) clients can use SSH2 so there should be no
compatibility issues with using the newer protocol.

On 4/20/07, Juanita Moore <jjmoore@att.net> wrote:
>
> Hi Mark,
>
> Ok, iptables . . . I've read a lot from google searches, wiki, etc, my
> main problem, I would guess, is not knowing just WHAT to search FOR!
> :-)     I keep thinking maybe there's even a class locally, but my
> better half says I've already probably learned a semester or two's worth
> on my own.
>
> Yeah, wasn't that good?  On Diceware?  Telling you to draw the curtains
> shut, burn your notes after memorizing the passphrase, then flush down
> the toilet??!  For maximum security, of course.
>
> I checked--it says Protocol 2,1
>
> I'm going step by step using putty's docs, but I guess I need to look
> for more info, as I don't quite get how the keys come into play.  Or
> else it's really ssh2 and I need to do the authorized_keys file
> differently than I did, thinking it was ssh1.
>
> What fun, and am I ever getting smart.  Not too many people I can talk
> to about it, tho!  Who's gonna understand how wonderful it was for me
> the first time I logged onto the server on the command line?!
>
> Thanks for the input,
>
> Juanita
>
> _______________________________________________
> QCLUG mailing list
> QCLUG@qclug.org
> http://qclug.org/mailman/listinfo/qclug
>

---------------------- multipart/alternative attachment
An HTML attachment was scrubbed...
URL: http://qclug.org/pipermail/qclug/attachments/620fb1b8/attachment.htm

---------------------- multipart/alternative attachment--