|
Grex > Garage > #23: Telnetd removal from OpenBSD >= 3.8 and grex. | |
|
| Author |
Message |
| 25 new of 57 responses total. |
steve
|
|
response 25 of 57:
| 
Jan 3 05:51 UTC 2006 |
The issue isn't if telnetd will work with future versions of
OpenBSD or not. There are others doing what we did, so I'm not
too concerned about being able to run it. The real question is
how do we best do this. I think giving several months notice
about a telnet phase out is the way to go, along with a web
page here explainging how to get ssh clients for Windows/MacOS.
|
cross
|
|
response 26 of 57:
|
Jan 3 15:40 UTC 2006 |
That sounds reasonable.
|
remmers
|
|
response 27 of 57:
|
Jan 4 16:47 UTC 2006 |
Re #25: Mac OS X comes with an ssh client.
|
bhoward
|
|
response 28 of 57:
|
Jan 12 09:22 UTC 2006 |
I get a lot of "helper" write sessions and just got a relevant one
today. Person logged in, wanted to be able to sign in with ssh but
didn't have a clue about unix/linux -- did not know what a shell
is, how to edit a file, make a directory but he did know about
putty...apparently was using it with other systems though how, I
don't know.
We will need to have clear instructions on how to locate and/or
generate your public key under putty and have a dead simple way for
them to cut-n-paste it to something that will properly configure
their .ssh/authorized* files.
Based on my conversation just now, this is something we will need
to transition very carefully and slowly. I would not want to scare
away non-technical users or those lacking exposure to unix. The
first of those two groups are often the ones that make the best
conferencing participants!
|
cross
|
|
response 29 of 57:
|
Jan 12 15:16 UTC 2006 |
Why not just start with passwords under PuTTY?
|
gull
|
|
response 30 of 57:
|
Jan 14 02:28 UTC 2006 |
I agree with resp:29. I wouldn't expect users to start using public
key authentication right off the bat. Most people don't need that
level of security, and most SSH clients lack a point-and-click way to
do it.
|
eteepell
|
|
response 31 of 57:
|
Jan 6 00:22 UTC 2007 |
I'm of the opinion to keep the telnetd going until major OS's ship with SSH
in the base system. I like the idea of security but not at the expense of
causing troubles for newbies. In my circumstance I am often on grex at work,
which uses Windows, and which has a corporate policy of not allowing
installation of software of company computers (see my point?), a web based
solution, like a java ssh would be nice, then theres the pesky surfcontrol
|
maus
|
|
response 32 of 57:
|
Jan 7 00:50 UTC 2007 |
Can you execute a third-party command if it does not require
installation? If so, look into putty. You can have full ssh capabilities
with 2 files without having to install anything. As another alternative,
I think you can download MindTerm for free if you just want it for
personal use. You can then simply execute "java -jar mindterm.zip
cyberspace.org".
|
denise
|
|
response 33 of 57:
|
Jan 23 23:24 UTC 2007 |
Maybe a bit late in the discussion, I do hope telnet stays for awhile for us
non-techies on board. Though I've heard of ssh here, I have absolutely no idea
what that [or putty] is. So an easy, non-techie based option for being on
grex would be cool. :-)
|
nharmon
|
|
response 34 of 57:
|
Jan 24 01:12 UTC 2007 |
Denise, I would say that using PuTTY is actually less "techie" than
using Windows telnet to access Grex.
Download a copy of PuTTY and give it a try.
|
cross
|
|
response 35 of 57:
|
Jan 24 16:03 UTC 2007 |
I agree with nharmon; PuTTY is actually easier to use than Windows telnet.
Grab a copy from here: http://www.putty.nl/latest/x86/putty-0.58-installer.
exe
and give it a whirl....
|
denise
|
|
response 36 of 57:
|
Jan 24 22:54 UTC 2007 |
What IS putty? Or does it explain what it is on the web site? I guess its
just something that I haven't ever been exposed to [but am willing to try and
learn].
|
cross
|
|
response 37 of 57:
|
Jan 24 23:57 UTC 2007 |
In a nutshell, PuTTY is a "terminal program" that allows you to connect to
remote systems (like grex) over the Internet. It provides a superset of the
functionality of Windows telnet, which you might currently be using to connect
to grex.
|
denise
|
|
response 38 of 57:
|
Jan 25 03:33 UTC 2007 |
Ok, thanks. I'll definitely check it out sometime in the next day or two when
I have a bit more time. :-)
|
remmers
|
|
response 39 of 57:
|
Jan 25 17:30 UTC 2007 |
In circumstances where I've been forced to use Windows, I used PuTTY a
lot for connecting to systems with a terminal interface. Definitely
recommended.
One downside was non-standard copy-paste behavior (borrowed from X
Windows, if I recall correctly) that could have unfortunate consequences
if you weren't aware of it. I don't recall the exact details - it's
been a few years - and maybe it's been fixed.
|
nharmon
|
|
response 40 of 57:
|
Jan 25 17:42 UTC 2007 |
Anything you highlight in PuTTY is copied onto the clipboard and right
clicking will paste everything in the clipboard.
|
remmers
|
|
response 41 of 57:
|
Jan 25 17:56 UTC 2007 |
Oh, right. Still not fixed, eh?
Accidental copies followed by accidental pastes into a command line
interface can have unfortunate consequences. Regardless what you think
of Windows, applications for it *should* follow standard user interface
behavior.
|
nharmon
|
|
response 42 of 57:
|
Jan 25 18:40 UTC 2007 |
Fixed implies it is broken, John. I kinda like that behavior. :-)
|
cross
|
|
response 43 of 57:
|
Jan 25 19:21 UTC 2007 |
Yeah, that's one thing about PuTTY that I do NOT like.
|
twenex
|
|
response 44 of 57:
|
Jan 25 20:14 UTC 2007 |
I love it.
What I hate about PuTTY is that it's only necessary on Windows!
|
remmers
|
|
response 45 of 57:
|
Jan 25 23:29 UTC 2007 |
I don't mind the behavior either, but then I'm an X Window veteran,
where it's standard. But if you're going to make a product that's
friendly to the poor folks who are stuck on Windows, you shouldn't have
unpleasant little traps waiting for them. I guess a user preference for
X Window behavior or standard Windows behavior, with the latter being
the default, would be ok.
|
cross
|
|
response 46 of 57:
|
Jan 25 23:47 UTC 2007 |
I agree with remmers here.
|
nharmon
|
|
response 47 of 57:
|
Jan 26 01:03 UTC 2007 |
It appears that my version of PuTTY allows you to turn this feature off.
Window --> Selection --> (Options controlling copy and paste)
|
gull
|
|
response 48 of 57:
|
Jan 27 22:12 UTC 2007 |
I kind of prefer the Windows behavior, and I configure my X systems to
follow it.
|
gull
|
|
response 49 of 57:
|
Jan 27 22:13 UTC 2007 |
It also occurrs to me that maybe it should be referred to as "Mac
behavior," since it originated there and Windows copied it. ;)
|