okay, paul, i'm officially recruiting you, hammer-and-tongs, as a newbiedoc contributor. your prose is wonderful and echoes frmo hill and dale with a sparkling clarity that... oh, hell, you can write, man! delightful!
and kevin, when the light goes on, and all the fog clears, imagine how much hair-pulling you'll save the next poor soul if you document what you learned... hmm? http://sourceForge.net/projects/newbiedoc/ On Wed, Apr 11, 2001 at 03:39:55AM -0400, Paul D. Smith wrote: > %% Kevin Stokes <[EMAIL PROTECTED]> writes: > ks> There is something that Linux needs much more than anything else, > ks> and that is a decent help system. We need something about 50 > ks> times larger than the man pages. Something which always has an > ks> extensive chapter in simple layman language, and lots of examples > ks> with clear steps with *explanations*. And also a way to get to > ks> the more typically man page type stuff for the people who need > ks> that. > > ks> Who is willing to create such a thing? Not me, I'm not a Linux > ks> devotee. > > That's the problem. The people writing the program write documentation > that makes sense to them and to other people using it. This > documentation is naturally technical in nature. There's a certain > "critical mass" of knowledge you need to obtain before you can really > start understanding the documentation. > > What's needed is for people like _you_ to help write "super newbie" > docs. We can't do it. We're not newbies. We don't know what newbies > need. i beg to differ! http://sourceForge.net/projects/newbiedoc/ > ks> But the bottom line is that the Windows Help system totally blows > ks> away all the confusing HOWTO's, man pages, or archived email > ks> searches. > > See, here's a prime example of the differences in our perspective. > > The Windows Help system _sucks_ huge boulders through coffee stirrers. > It totally blows chunks. that may wind up in a ~/.signature soon! :) > ks> Anyway... Does anybody know what steps I need to do in order make > ks> ssh work so I can log in remotely? I wanted to try to use Tera > ks> Term Pro with the SSH extenstion to log onto my Linux machine from > ks> a Windows machine on the local network. > > ks> Right now if I type: > > ks> ssh -v -l root rocky > > Here's the thing. > > You can't login remotely as root, by default, over ssh: the ssh setup > disallows this (as with everything in UNIX, this is configurable if you > really want to do it--it's a bad idea so it's disabled initially). > > You don't want to work as root, at all, ever, anytime, anywhere, > anyplace. Even for testing. _Especially_ for testing. Use root only > when you must do root operations, then run screaming into the bushes > again immediately after you've done that operation. wonderful! > Be careful! That private key is like your password; anyone who gets a > copy can get into your system. It's a good idea to sign the key with a > passphrase when ssh-keygen asks for one: then people not only need the > private key but they also need your passphrase. This is more secure > because the passphrase is used only to unlock the key locally; neither > the passphrase _NOR_ the key itself are ever transmitted over the > network. > > Public/private key cryptography is not the most straightforward thing in > the world, unfortunately. or fortunately, depending on which facet you're looking into. :) -- americans should never read anything so subversive as what's at http://www.salon.com/people/col/pagl/2001/03/21/spring/index1.html [EMAIL PROTECTED] http://sourceForge.net/projects/newbiedoc -- we need your brain! http://www.dontUthink.com/ -- your brain needs us!
