h. First, to be in the right habit. Second
>> >>> because it will do things that telnet won't, like tunnel X.
>> >>
>> >> Ah but will it tunnel wayland?? Enquiring minds want to know :)
>> >
>> > Yes.
>> >
>> yes here t
Christmas's
> wish :-)
Oh, you mean that. That is not telnet, that comes from the kernel. Even
sleep has this.
Regards,
--
Nicolas George
alent socat mode (say line-mode with readline editing or something).
> > That
> > would be a market niche, wouldn't it?
>
> I am not sure what you are saying: telnet does not have a line mode with
> readline editing;
It does have a line mode with local echo (meaning you can
ould be a market niche, wouldn't it?
I am not sure what you are saying: telnet does not have a line mode with
readline editing; anything of that kind you observe is on the server
side. socat, OTOH, has.
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
a LATIN SMALL LETTER Y WITH
> DIAERESIS in ISO-8859-1.
Most definitely :-)
> Anyway, the treatment done by telnet is not bad per se, provided we know
> (1) that they happen, (2) if we need them in our use case and (3) how to
> turn them off. I guess most people who use telnet as a gen
to...@tuxteam.de (12023-12-04):
> Which, in the case of interaction with HTTP (and most others) actually
> comes in handy. Those explicit \r\n get old pretty fast...
Just hope you will not need to emit a LATIN SMALL LETTER Y WITH
DIAERESIS in ISO-8859-1.
Anyway, the treatment done by
On Mon, Dec 04, 2023 at 08:01:10PM +0100, Nicolas George wrote:
> to...@tuxteam.de (12023-12-04):
> > These days, even bash can do it:
>
> Zsh could years before.
>
> > (alas, it can't do TCP server, which is a pity)
>
> socat can do TCP server. And UDP client, and UDP server, and TLS/SSL
>
to...@tuxteam.de (12023-12-04):
> These days, even bash can do it:
Zsh could years before.
> (alas, it can't do TCP server, which is a pity)
socat can do TCP server. And UDP client, and UDP server, and TLS/SSL
client and server, and Unix sockets, and SOCKS, and tun, and…
(And zsh seems to be
On Mon, Dec 04, 2023 at 09:23:16AM +0100, Nicolas George wrote:
> Charles Curley (12023-12-03):
> > True. None the less, there is at least one perfectly good use for
> > telnet: testing connections to servers.
>
> Wrong. The telnet client is not entirely transparent, as
On Mon, Dec 04, 2023 at 05:32:20PM +0100, Nicolas George wrote:
> Curt (12023-12-04):
> > Telnet doesn't alter the actual data being transmitted
>
> Yes it does, read the doc before posting wrong information here.
Which, in the case of interaction with HTTP (and most others)
Curt (12023-12-04):
> I think you're buggering yet another fly here.
I think you should read the docs and shut up. I know what I am saying.
--
Nicolas George
On 2023-12-04, Nicolas George wrote:
> Curt (12023-12-04):
>> Telnet doesn't alter the actual data being transmitted
>
> Yes it does, read the doc before posting wrong information here.
>
I think you're buggering yet another fly here.
Curt (12023-12-04):
> Telnet doesn't alter the actual data being transmitted
Yes it does, read the doc before posting wrong information here.
--
Nicolas George
Marco Moock (12023-12-04):
> Is that really the case?
Yes.
> Other applications like telnet or vi don't care about it, so I
> assume(d), it is up to the application to handle it.
Applications can decide to change the mode of the tty or catch SIGINT.
Regards,
--
Nicolas George
Am 04.12.2023 um 09:28:30 Uhr schrieb Nicolas George:
> Marco Moock (12023-12-04):
> > ncat also uses ^C to kill the process.
>
> No, this effect of ^C is part of the operating system.
Is that really the case?
Other applications like telnet or vi don't care about it, so I
assu
> ncat also uses ^C to kill the process.
>
>
Telnet doesn't alter the actual data being transmitted, which is the
denotation of transparent in this context, so I think his point is
ludicrously small, if inexistant.
gene heskett wrote:
> On 12/4/23 05:22, Anssi Saari wrote:
> > debian-u...@howorth.org.uk writes:
> >
> >>> I concur, and would add that even on an isolated network one
> >>> should prefer ssh. First, to be in the right habit. Second
> >>>
On Mon, Dec 4, 2023, 2:23 AM Nicolas George wrote:
> Charles Curley (12023-12-03):
> > True. None the less, there is at least one perfectly good use for
> > telnet: testing connections to servers.
>
> Wrong. The telnet client is not entirely transparent, as the teln
On 04/12/2023 11:30, gene heskett wrote:
On 12/4/23 05:22, Anssi Saari wrote:
debian-u...@howorth.org.uk writes:
I concur, and would add that even on an isolated network one should
prefer ssh. First, to be in the right habit. Second because it will do
things that telnet won't, like tunnel X
On Mon, 4 Dec 2023, Michael Kj?rling wrote:
On 4 Dec 2023 10:29 +, from debianu...@woodall.me.uk (Tim Woodall):
Some years ago I abandoned firefox because there was no way to override
one of its 'I'm sorry Dave, I'm afraid I can't do that' spasms.
It's crazy that they make things like
On 4 Dec 2023 10:29 +, from debianu...@woodall.me.uk (Tim Woodall):
> Some years ago I abandoned firefox because there was no way to override
> one of its 'I'm sorry Dave, I'm afraid I can't do that' spasms.
>
> It's crazy that they make things like certificate pinning *impossible*
> to
On 12/4/23 05:22, Anssi Saari wrote:
debian-u...@howorth.org.uk writes:
I concur, and would add that even on an isolated network one should
prefer ssh. First, to be in the right habit. Second because it will do
things that telnet won't, like tunnel X.
Ah but will it tunnel wayland
On Sun, 3 Dec 2023, Greg Wooledge wrote:
On Sun, Dec 03, 2023 at 11:52:51AM -0700, Charles Curley wrote:
True. None the less, there is at least one perfectly good use for
telnet: testing connections to servers.
charles@hawk:~$ telnet hawk
Trying 127.0.1.1...
telnet: Unable to connect
debian-u...@howorth.org.uk writes:
>> I concur, and would add that even on an isolated network one should
>> prefer ssh. First, to be in the right habit. Second because it will do
>> things that telnet won't, like tunnel X.
>
> Ah but will it tunnel wayland?? Enquiring minds want to know :)
Yes.
Marco Moock (12023-12-04):
> ncat also uses ^C to kill the process.
No, this effect of ^C is part of the operating system.
Regards,
--
Nicolas George
Am 04.12.2023 um 09:23:16 Uhr schrieb Nicolas George:
> If you want to test a network protocol, you should use a really
> transparent client. Traditionally people use netcat (nc), but it
> handles EOF approximatively.
ncat also uses ^C to kill the process.
Charles Curley (12023-12-03):
> True. None the less, there is at least one perfectly good use for
> telnet: testing connections to servers.
Wrong. The telnet client is not entirely transparent, as the telnet
protocol defines an escape octet to introduce commands.
If you want to test a n
t aggressively, as machines
> > which are currently on an isolated network might not remain there
> > forever.
>
> I concur, and would add that even on an isolated network one should
> prefer ssh. First, to be in the right habit. Second because it will do
> things that
an isolated network might not remain there forever.
I concur, and would add that even on an isolated network one should
prefer ssh. First, to be in the right habit. Second because it will do
things that telnet won't, like tunnel X.
--
Does anybody read signatures any more?
https://charlescurl
On Sun, Dec 03, 2023 at 11:52:51AM -0700, Charles Curley wrote:
> On Sun, 3 Dec 2023 17:00:44 +0100
> Marco Moock wrote:
>
> > >
> > > How do you find 1994? It seems to be a mail from yesterday:
> >
> > For me it sounded like a joke.
> >
>
On Sun, 3 Dec 2023 17:00:44 +0100
Marco Moock wrote:
> >
> > How do you find 1994? It seems to be a mail from yesterday:
>
> For me it sounded like a joke.
>
> Telnet is unencrypted (although it is possible to run it over TLS to
> encrypt it) and SSH exists more
For me it sounded like a joke.
Telnet is unencrypted (although it is possible to run it over TLS to
encrypt it) and SSH exists more than 20 years.
On 2023-12-02, Andy Smith wrote:
> Can someone examine the list's configuration? This email from 1994
> seems to have only just been delivered.
How do you find 1994? It seems to be a mail from yesterday:
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com
Hello,
On Sat, Dec 02, 2023 at 09:50:00AM -0600, William Torrez Corea wrote:
> My telnet not operate, try connect my laptop by means of telnet:
Can someone examine the list's configuration? This email from 1994
seems to have only just been delivered.
Thanks,
Andy
--
https://bitfolk.
On Sat, Dec 02, 2023 at 05:01:37PM +0100, Marco Moock wrote:
> Am 02.12.2023 um 09:50:00 Uhr schrieb William Torrez Corea:
>
> > sudo telnet 192.168.1.1
Also, just for the record, there is *no* need to use sudo here.
Am 02.12.2023 um 09:50:00 Uhr schrieb William Torrez Corea:
> sudo telnet 192.168.1.1
> > Trying 192.168.1.1...
> > Connected to 192.168.1.1.
> > Escape character is '^]'.
That means that the telnet connection was successful
> > Telnet connection from 192.168.1.5
idea whose policy you refer to, so I don't know if it's policy
or not. One of the main reasons telnet is deprecated is because it
sends passwords in the clear, so a malevolent snooper can harvest
passwords.
>
> A session is routinely opened with xterm, gnome-terminal, lxterm and
> etc
.
> They didn't even bother putting a comment in the script, ...
## telnet ... is a comment. Although ## is styled as formal
syntax. Why not just prefix the telnet line with "#" and add a comment
such as
# telnet is commented out in case you installed it but don't really want
On Fri, Oct 11, 2019 at 01:59:07PM +0100, Tixy wrote:
> On Fri, 2019-10-11 at 04:00 -0700, pe...@easthope.ca wrote:
> [...]
> > Ideally the syntax
> > required for correct threading would be posted in the debian site.
>
> What's it got to do with Debian? Correct email threading is a property
>
On Fri, 2019-10-11 at 04:00 -0700, pe...@easthope.ca wrote:
[...]
> Ideally the syntax
> required for correct threading would be posted in the debian site.
What's it got to do with Debian? Correct email threading is a property
of the email clients the senders and receivers of emails use. You'd
From: David Wright
Date: Fri, 11 Oct 2019 00:12:45 -0500
> Maybe sometime you'd explain why you prefer telnet to ssh.
Several years ago ssh was about 15-20 s connecting whereas telnet
required less than a second. Consequently I adopted the habit of using
telnet with a password. Recentl
On Thu 10 Oct 2019 at 06:48:16 (-0700), pe...@easthope.ca wrote:
> Incidently the hyperlinks in my reply to Charles Curley
> ( https://lists.debian.org/debian-user/2019/10/msg00479.html ) seem OK.
> The list server is is flummoxed when there are more than 2 or 3 or 4
> References? Then I
quot;
with the two sentences in apposition in order to contrast the choices
you said you have available: "Protocols Telnet and SSH are available;…"
Maybe sometime you'd explain why you prefer telnet to ssh.
Perhaps you could also restate where you had got to in this thread.
I assumed t
issue.
> Recency is minded but shouldn't dictate.
Fair enough.
> > sshd is ... secure.
>
> This scenario is in one machine which is running shorewall. The LAN
> has another firewall. What are the risks to the telnet protocol in
> this case?
netcat (which I use very frequently) mi
nother firewall. What are the risks to the telnet protocol in
this case?
> Why would you be typing a password after typing ssh localhost?
> Just type:
>
> $ cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
Valid point.
Incidently the hyperlinks in my reply to Charles Curley
(
; > shell. So it would help our understanding if you were to explain
> > what your use case is for this new interactive shell session.
>
> Oberon has a client for protocol Telnet and a client for SSH. bash,
> dash, sudo, rlogin and many other tools don't exist in Oberon. I
td in a
> Debian system.
>
> This illustrates why I tried to avoid mention of Oberon at the
> outset. It's a distraction, not essential to the question. The
> telnet client might also be in MS Windows running in QEMU in the
> debian system or in FreeDOS in QEMU in the debian system
It's a distraction, not essential to the question. The telnet client
might also be in MS Windows running in QEMU in the debian system or in
FreeDOS in QEMU in the debian system. They might provide analogous
contexts. But the question was about the telnetd server in debian;
not about the
DISCLAIMER & WARNING: Threading may still be incorrect. Tempting as
this message might be, if incorrect threading upsets you please stop
reading. =8~)
To my understanding In-Reply-To and References were added to the
earlier message correctly but the list server put them in the Web
based
ve asked just what you are trying to do, and
all you have done is obfuscate the matter.
If you want to have multiple shell sessions on the same account on the
same computer, telnet is at best an unnecessary complication and at
worst a security nightmare.
If you are running a GUI, most desktop en
e case is for this new interactive shell session.
Oberon has a client for protocol Telnet and a client for SSH. bash,
dash, sudo, rlogin and many other tools don't exist in Oberon. I
avoided discussing this deliberately. For most readers it's an
annoying digression; for some will cause mental u
entication. Can telnet
> > work similarly?
> ... no-one has a clue what the actual question ...
When quoting my question you must have read it.
> lxterminal runs a GUI application on your host. It
> uses libc so that your CPU can communicate directly with
> your keyboard an
On Thu, 3 Oct 2019 at 14:20, David wrote:
[...]
Sorry, I didn't see this had already been discussed.
(broken threading, gmail interface, didn't read everything
before sending anything)
On Thu, 3 Oct 2019 at 05:38, Thomas Schmitt wrote:
> Reco wrote:
> > Threading is broken, as usual.
>
> This is probably due to extra characters in the "References:" header:
>
> > > From: pe...@easthope.ca
> > > X-Mailer: Oberon Mail (ejz) on LinuxA2 Gen. 32-bit, rev.8586
> > > To:
Hi,
pe...@easthope.ca wrote:
> > Hopefully this is readable.
Reco wrote:
> Threading is broken, as usual.
This is probably due to extra characters in the "References:" header:
> > From: pe...@easthope.ca
> > X-Mailer: Oberon Mail (ejz) on LinuxA2 Gen. 32-bit, rev.8586
> > To:
Hi.
On Wed, Oct 02, 2019 at 11:52:51AM -0700, pe...@easthope.ca wrote:
> Hopefully this is readable.
It is. Threading is broken, as usual.
> > Hence aforementioned "echo" command above.
>
> Ie.
> > 2) echo 'telnet stream tcp nowait root/usr/s
cho" command above.
>
> Ie.
> > 2) echo 'telnet stream tcp nowait root/usr/sbin/tcpd
> > /usr/sbin/telnetd -a none -E /bin/bash' >> /etc/inetd.conf
>
> To my understanding that would wipe out all the other services.
> I read your instruction as
Hopefully this is readable.
From: Reco , Wed, 2 Oct 2019 09:45:12 +0300
> No, it should not be there because it disables telnetd this way.
Thanks.
> Hence aforementioned "echo" command above.
Ie.
> 2) echo 'telnet stream tcp nowait root/usr/sbin/tcpd
> /usr/s
On 2019-10-02, Greg Wooledge wrote:
> On Wed, Oct 02, 2019 at 04:55:29PM -, Curt wrote:
>> On 2019-10-02, Greg Wooledge wrote:
>> > On Wed, Oct 02, 2019 at 09:45:12AM +0300, Reco wrote:
>> >
>> > So, I'm done with you. I'm adding you to the same file that the
>> > illustrious Mr. Owlett is
On Tuesday, October 01, 2019 01:40:51 PM Thomas Schmitt wrote:
> David wrote:
> > > Oh dear, I'm sorry again, this time for mixing you up with Thomas!
>
> to...@tuxteam.de wrote:
> > I can't know how Thomas feels about it.
>
> I regularly run whoami to avoid any local confusion.
Thanks, I
On Wed, Oct 02, 2019 at 04:55:29PM -, Curt wrote:
> On 2019-10-02, Greg Wooledge wrote:
> > On Wed, Oct 02, 2019 at 09:45:12AM +0300, Reco wrote:
> >
> > So, I'm done with you. I'm adding you to the same file that the
> > illustrious Mr. Owlett is in, so I never have to read your mangled,
>
On Tuesday, October 01, 2019 11:08:09 AM Brad Rogers wrote:
> On Wed, 2 Oct 2019 00:54:19 +1000
> David wrote:
>
> Hello David,
>
> >I've written a few shitty messages to this list too, when people don't
> >meet my expectations of behaviour. But usually when I'm finished,
> >I press "delete"
On 2019-10-02, Greg Wooledge wrote:
> On Wed, Oct 02, 2019 at 09:45:12AM +0300, Reco wrote:
>
> So, I'm done with you. I'm adding you to the same file that the
> illustrious Mr. Owlett is in, so I never have to read your mangled,
> nonsensical crap again.
>
Aren't you delivering the right
On Wed, Oct 02, 2019 at 09:45:12AM +0300, Reco wrote:
> On Tue, Oct 01, 2019 at 09:12:42PM -0700, pe...@easthope.ca wrote:
> > peter@joule:~$ grep telnet /etc/inetd.conf
> > ## telnet stream tcp nowait root/usr/sbin/tcpd
> > /usr/sbin/telnetd -a none -E /bin/b
On Tue, Oct 01, 2019 at 09:12:42PM -0700, pe...@easthope.ca wrote:
> From: Reco , Tue, 1 Oct 2019 09:48:09 +0300
> > 2) echo 'telnet stream tcp nowait root/usr/sbin/tcpd
> > /usr/sbin/telnetd -a none -E /bin/bash' >> /etc/inetd.conf
>
> peter@joule:~$
From: Reco Tue, 1 Oct 2019 22:26:35 +0300
> apt install inetutils-telnetd openbsd-inetd
root@joule:~# dpkg -l | grep inet
ii inetutils-telnetd2:1.9.4-7
i386 telnet server
ii openbsd-inetd0.2016082
On Tue, Oct 01, 2019 at 07:40:51PM +0200, Thomas Schmitt wrote:
> Hi,
>
> David wrote:
> > > Oh dear, I'm sorry again, this time for mixing you up with Thomas!
>
> to...@tuxteam.de wrote:
> > I can't know how Thomas feels about it.
>
> I regularly run whoami to avoid any local confusion.
Hi.
On Tue, Oct 01, 2019 at 10:42:20AM -0700, pe...@easthope.ca wrote:
> > Try it:
> >
> > 1) apt install inetutils-inetd openbsd-inetd
>
> Debian 10 allows me to install one or the other but not both.
> I removed inetutils-inetd and installed openbsd-inetd.
There's this saying here
s me to install one or the other but not both.
I removed inetutils-inetd and installed openbsd-inetd.
> 2) echo 'telnet stream tcp nowait root/usr/sbin/tcpd
> /usr/sbin/telnetd -a none -E /bin/bash' > /etc/inetd.conf
peter@joule:~$ dpkg -l | grep telnet /etc/inetd.conf
telnet
Hi,
David wrote:
> > Oh dear, I'm sorry again, this time for mixing you up with Thomas!
to...@tuxteam.de wrote:
> I can't know how Thomas feels about it.
I regularly run whoami to avoid any local confusion.
Have a nice day :)
Thomas
On Wed, Oct 02, 2019 at 01:57:34AM +1000, David wrote:
> On Wed, 2 Oct 2019 at 01:49, wrote:
> > On Wed, Oct 02, 2019 at 01:29:01AM +1000, David wrote:
>
> > > You are Mr "have a nice day" after all :)
>
> > No, that is Thomas (our names are pretty similar, but he is
> > far less grumpy than me
On Wed, 2 Oct 2019 at 01:49, wrote:
> On Wed, Oct 02, 2019 at 01:29:01AM +1000, David wrote:
> > You are Mr "have a nice day" after all :)
> No, that is Thomas (our names are pretty similar, but he is
> far less grumpy than me and besides he has quite a bit of
> free software out there to show
On Wed, Oct 02, 2019 at 01:29:01AM +1000, David wrote:
> On Wed, 2 Oct 2019 at 01:16, wrote:
> > On Wed, Oct 02, 2019 at 12:54:19AM +1000, David wrote:
>
> > > I've written a few shitty messages to this list too [...]
>
> I'm sorry, the word "too" should not appear in my sentence
> above, I did
On Wed, 2 Oct 2019 00:54:19 +1000
David wrote:
Hello David,
>I've written a few shitty messages to this list too, when people don't
>meet my expectations of behaviour. But usually when I'm finished,
>I press "delete" instead of "send", and then find something fun to
Been there, done that.
On Wed, 2 Oct 2019 at 01:16, wrote:
> On Wed, Oct 02, 2019 at 12:54:19AM +1000, David wrote:
> > I've written a few shitty messages to this list too [...]
I'm sorry, the word "too" should not appear in my sentence
above, I did not notice that it carries implications that I did
not intend,
On Wed, Oct 02, 2019 at 12:54:19AM +1000, David wrote:
> On Tue, 1 Oct 2019 at 22:57, wrote:
> > On Tue, Oct 01, 2019 at 08:52:48AM -0400, Greg Wooledge wrote:
>
> > > Why in the hell [...]
>
> > Now try in a more polite and friendly way. [...]
>
> > Thanks for trying :)
>
> I agree that
On Tue, 1 Oct 2019 at 22:57, wrote:
> On Tue, Oct 01, 2019 at 08:52:48AM -0400, Greg Wooledge wrote:
> > Why in the hell [...]
> Now try in a more polite and friendly way. [...]
> Thanks for trying :)
I agree that polite and friendly is the goal.
I see that a polite way was tried already by
On Tue, Oct 01, 2019 at 08:52:48AM -0400, Greg Wooledge wrote:
[...]
> Why in the hell is anyone running telnetd in 2019?
>
> What is the PURPOSE of this idiocy? To recreate that 1992 feeling? For
> nostalgia?
Now try in a more polite and friendly way. Then you'd have a chance
of achieving
On Tue, Oct 01, 2019 at 09:48:09AM +0300, Reco wrote:
> On Mon, Sep 30, 2019 at 09:36:51PM -0700, pe...@easthope.ca wrote:
> > peter@joule:~$ grep telnet /etc/inetd.conf
> > telnet stream tcp nowait root /usr/sbin/tcpd /usr/sbin/in.telnetd -a user
> > # Restart inetd.
Why
On Mon, Sep 30, 2019 at 09:36:51PM -0700, pe...@easthope.ca wrote:
> From: Reco
> Date: Sat, 28 Sep 2019 19:23:45 +0300
> > telnetd(8), "-a" and "-L" parameters.
>
> OK.
> peter@joule:~$ grep telnet /etc/inetd.conf
> telnet stream tcp nowait root
From: Reco
Date: Sat, 28 Sep 2019 19:23:45 +0300
> telnetd(8), "-a" and "-L" parameters.
OK.
peter@joule:~$ grep telnet /etc/inetd.conf
telnet stream tcp nowait root /usr/sbin/tcpd /usr/sbin/in.telnetd -a user
# Restart inetd.
Then the result from telnet to loca
get confused because your posting style is incredibly
difficult to follow. You break threads and give very little detail.
Help us to help you.
> ... telnet opens in about 1 s. ... ssh requires about 15 s.
If your SSH takes 15 seconds to connect to localhost then you have a
configuration
your posting style is incredibly
difficult to follow. You break threads and give very little detail.
Help us to help you.
> > ... telnet opens in about 1 s. ... ssh requires about 15 s.
If your SSH takes 15 seconds to connect to localhost then you have a
configuration issue. As a first gues
Andy Smith wrote:
>
> Is it a case that the hosts you are dealing with are too
> underpowered CPU-wise to cope with SSH's encryption?
>
For what it's worth, I used to routinely SSH in to an appliance running
on an extremely underpowered CPU (by today's standards), a 30 MHz MIPS
core. The
23:45 +0300
> > I have to ask - what are you trying to achieve?
> An interactive shell session with minimal overhead. (Or maximal
> efficiency.) The telnet client in the Oberon subsystem is noticeably
> faster than competitors.
I now notice that the reason that "Oberon"
On Sun, Sep 29, 2019 at 02:36:02PM -0700, pe...@easthope.ca wrote:
> From: Reco
> Date: Sat, 28 Sep 2019 19:23:45 +0300
> > I have to ask - what are you trying to achieve?
>
> An interactive shell session with minimal overhead. (Or maximal
> efficiency.) The telnet
On Mon, 2019-09-30 at 14:43 +1000, David wrote:
[...]
> A final puzzle is that I vaguely recall from other
> messages that you use something named Oberon.
It came up in the discussion of why he breaks threads every time he
posts to this list. The X-Mailer header in his emails says 'Oberon
Mail'
On Sun, 29 Sep 2019 at 01:33, wrote:
> Opening a terminal emulator in default configuration on localhost,
> LXTerminal for example, doesn't require authentication. Can telnet
> work similarly? Ie. "telnet localhost" succeeds without login.
Ok, the guessing game continue
a
Date: Mon, 14 Jun 2010 11:03:50 -0700
> ... telnet opens in about 1 s. ... ssh requires about 15 s.
Any computer built since 1990 should be able to run
a plain old terminal session.
Regards, ... P.
--
https://en.wikibooks.org/wiki/Medical_Machines
Tel: +1 604 670 0
hines
> before SSH was invented: rlogin.
Oh, I see now that you were interested in passwordless equivalent of
"telnet localhost".
It is confusing why you would need to do this to localhost as you
could just type "bash" (or dash or zsh or whatever) to get a new
shell. So it
Hello,
On Sun, Sep 29, 2019 at 02:36:02PM -0700, pe...@easthope.ca wrote:
> From: Reco
> > I have to ask - what are you trying to achieve?
>
> An interactive shell session with minimal overhead. (Or maximal
> efficiency.) The telnet client in the Oberon subsystem is noticea
From: Reco
Date: Sat, 28 Sep 2019 19:23:45 +0300
> I have to ask - what are you trying to achieve?
An interactive shell session with minimal overhead. (Or maximal
efficiency.) The telnet client in the Oberon subsystem is noticeably
faster than competitors.
> ... your request
Hi.
On Sat, Sep 28, 2019 at 08:15:07AM -0700, pe...@easthope.ca wrote:
> Opening a terminal emulator in default configuration on localhost,
> LXTerminal for example, doesn't require authentication. Can telnet
> work similarly? Ie. "telnet localhost" succeeds with
Opening a terminal emulator in default configuration on localhost,
LXTerminal for example, doesn't require authentication. Can telnet
work similarly? Ie. "telnet localhost" succeeds without login.
Can this be accomplished by configuration of PAM ?
Thanks,.
Todos nos ja utilizamos o ssh porem o telnet era muito utilizado principalmente
para acesso a roteadores, ainda existem muitos telnet por ai, e coisas
incríveis como assistir o filme Star Wars pelo telnet, eu pensei se algo como
Stunnel tornaria o telnet tão seguro quanto o ssh?
Em 28/05/2019
um terminal (console ou X) basta usar:
ssh ip-ou-host
Caso seja necessário, a preciso liberar a porta 22 no firewall.
Se a necessidade e acessar um roteador ou outro appliance que não suporta
ssh, se recomenda limitar o telnet a rede local.
On Tue, May 28, 2019 at 12:29 PM Vitor Hugo wrote:
>
Fiquei curioso... cada vez mais vejo perguntas criativas... qual o contexto?
Observo o uso de telnet para troubleshooting... e alguns dispositivos
antigos que só tem ele como opção de acesso... mas vc chegou dar uma
olhada no man? Fala à respeito disso... provavelmente terá que
compilar com
É possível utilizar o telnet de forma segura?
Le 25/05/2017 à 17:03, bernard.schoenac...@free.fr a écrit :
> bonjour,
>
> je fait quelques essais avec telnet pour envoyer un courriel contenant des
> accents et le résultat escompté est déplorable comme si tout était en 7bits
>
> comment faire pour corriger le tir ?
>
Le Thu, 25 May 2017 17:03:06 +0200 (CEST),
bernard.schoenac...@free.fr a écrit :
> bonjour,
>
> je fait quelques essais avec telnet pour envoyer un courriel
> contenant des accents et le résultat escompté est déplorable comme si
> tout était en 7bits
>
> comment faire pour
1 - 100 of 1862 matches
Mail list logo
