On Tue, Nov 25, 2014 at 10:42:18AM -0700, Warren Young wrote:
> It doesn’t look like CentOS 7’s in.telnetd supports this anyway. I
> base that on two bits of evidence:
>
> 1. The man page: " -a authmode ...not available in the current version.”
>
> 2. ldd /usr/sbin/in.telnetd doesn’t show that
On Nov 24, 2014, at 6:04 PM, Jonathan Billings wrote:
> On Nov 24, 2014, at 3:46 PM, Warren Young wrote:
>> Now compare telnet: always vulnerable, all the time, since the day it was
>> created, before most of the people on this list were born:
>
> Technically, you can run kerberized (krb5) tel
Thanks all. It is working now.
Regards
On 24 Nov 2014 20:11, "Frank Cox" wrote:
> On Mon, 24 Nov 2014 08:46:33 -0600
> John R. Dennison wrote:
>
> > Why are you wanting to use telnet in the first place?
>
> I don't know what his use case is, but I installed telnet on this computer
> a while back
On Mon, Nov 24, 2014 at 3:59 PM, John R Pierce wrote:
> On 11/24/2014 6:38 AM, Mauricio Tavares wrote:
>>
>>I will not go over the question about running telnet in your
>> laptop; others will chime in. Now that is out, did you check whether
>> telnet is running using ps and netstat?
>
>
>
On Nov 24, 2014, at 3:46 PM, Warren Young wrote:
> Now compare telnet: always vulnerable, all the time, since the day it was
> created, before most of the people on this list were born:
Technically, you can run kerberized (krb5) telnet/telnetd, and it's not quite
as insecure as unkerberized tel
On 11/24/2014 6:38 AM, Mauricio Tavares wrote:
I will not go over the question about running telnet in your
laptop; others will chime in. Now that is out, did you check whether
telnet is running using ps and netstat?
useless advise, since telnet is almost always run from a socket, the
t
On Nov 24, 2014, at 11:04 AM, Les Mikesell wrote:
> On Mon, Nov 24, 2014 at 11:38 AM, Leon Fauster
> wrote:
>>
>> best practice is to not use clear text protocols anymore.
>
> Umm, yeah. Encrypted protocols would never be compromised….
That’s absolutist thinking. There is no such thing as
On Mon, Nov 24, 2014 at 12:04:30PM -0600, Les Mikesell wrote:
>
> Umm, yeah. Encrypted protocols would never be compromised
Which do you think is more likely? Someone sniffing a cleartext
credential set on the wire or someone subverting an alleged "secure"
encrypted protocol?
Nothing is b
On Mon, Nov 24, 2014 at 12:12 PM, John R. Dennison wrote:
> On Mon, Nov 24, 2014 at 12:04:30PM -0600, Les Mikesell wrote:
>>
>> Umm, yeah. Encrypted protocols would never be compromised
>
> Which do you think is more likely? Someone sniffing a cleartext
> credential set on the wire or someo
On 11/24/2014 10:04 AM, Les Mikesell wrote:
mm, yeah. Encrypted protocols would never be compromised
door locks can be picked, so I should never lock my doors?
--
john r pierce 37N 122W
somewhere on the middle of the left coast
___
The original poster has not replied, so we do not know his reasoning.
On Mon, Nov 24, 2014 at 1:17 PM, Les Mikesell wrote:
> On Mon, Nov 24, 2014 at 12:12 PM, John R. Dennison wrote:
>> On Mon, Nov 24, 2014 at 12:04:30PM -0600, Les Mikesell wrote:
>>>
>>> Umm, yeah. Encrypted protocols
On Mon, Nov 24, 2014 at 11:38 AM, Leon Fauster
wrote:
> Am 24.11.2014 um 18:11 schrieb Frank Cox :
>> On Mon, 24 Nov 2014 08:46:33 -0600
>> John R. Dennison wrote:
>>
>>> Why are you wanting to use telnet in the first place?
>>
>> I don't know what his use case is, but I installed telnet on this c
Am 24.11.2014 um 18:11 schrieb Frank Cox :
> On Mon, 24 Nov 2014 08:46:33 -0600
> John R. Dennison wrote:
>
>> Why are you wanting to use telnet in the first place?
>
> I don't know what his use case is, but I installed telnet on this computer a
> while back for the Android Remote Keyboard app.
On Mon, 24 Nov 2014 08:46:33 -0600
John R. Dennison wrote:
> Why are you wanting to use telnet in the first place?
I don't know what his use case is, but I installed telnet on this computer a
while back for the Android Remote Keyboard app.
https://play.google.com/store/apps/details?id=de.onyxbi
On Mon, Nov 24, 2014 at 03:33:24PM +0100, Samson wrote:
>
> Trying 127.0.0.1...
> telnet: connect to address 127.0.0.1: Connection refused
Because telnet is 1970s tech that should die in a fire; it's not enabled
by default nor does the firewall permit it by default.
Why are you wanting to use tel
On Mon, Nov 24, 2014 at 9:38 AM, Mauricio Tavares wrote:
> On Mon, Nov 24, 2014 at 9:33 AM, Samson wrote:
>> I just install Centos 7 on my laptop. I have also installed telnet-server
>> and telnet.
>> I can telnet to other server from my local CentOS 7 but can not telnet
>> localhost also, i can
On Mon, Nov 24, 2014 at 9:33 AM, Samson wrote:
> I just install Centos 7 on my laptop. I have also installed telnet-server
> and telnet.
> I can telnet to other server from my local CentOS 7 but can not telnet
> localhost also, i can not telnet to my localhost from other server.
>
> I try to check
I just install Centos 7 on my laptop. I have also installed telnet-server
and telnet.
I can telnet to other server from my local CentOS 7 but can not telnet
localhost also, i can not telnet to my localhost from other server.
I try to check telnet file in /etc/xinetd.d directory but the file "telne
18 matches
Mail list logo
