LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Red Hat
User Name
Password
Red Hat This forum is for the discussion of Red Hat Linux.

Notices


Reply
  Search this Thread
Old 12-14-2006, 01:54 PM   #1
jmj99385
Member
 
Registered: Aug 2005
Distribution: Slackware, Fedora, CentOS
Posts: 42

Rep: Reputation: 15
Telnet Port 25 Issue


I am trying to deny access to anyone using telnet to my SMTP server.

So far I've shut down xinetd, but the connection still comes up as if I did nothing.

Any suggestions would be greatly appreciated!
 
Old 12-14-2006, 02:16 PM   #2
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985
xinetd has nothign to do with smtp, why did you think it did?

you can't (easily) block access from a telnet client to any tcp port, i guess you're not really clear on what the use of telnet in that situation is. telnet in itself is an extremely simple client, which does virtually nothing. the only slightly "clever" bit is the server which spawns a login shell on the telnet port when connected to it. as the client is so simple, it can be used in many different ways to troubleshoot servers and netwrok connectivity. it basically just allows a human user to interact with whatever serivce is connected to a tcp port. when used in this way, it's really *not* telnet at all, just a pipe to a tcp port.

as you're hopefully aware telnet is regarded as a huge security risk, and i'd assume that's why you wish to stop it here, but the risk is actually the use of the client and the sever and the way a login esssion works across the two, not the client itself at all.

basically don't try to block it, there's no point and i'm not really even sure it's possible as telnet clients don't really identify themselves in any way at all on connection, they just send whatever keypresses you make and show you what the server replies with, hence it's many many uses debugging smtp, http, etc...
 
Old 12-14-2006, 02:17 PM   #3
Dudydoo
Member
 
Registered: Sep 2003
Location: UK
Distribution: I use 'em all ;-)
Posts: 275

Rep: Reputation: 38
You can't stop it as far as I know, and there is nothing unsafe about people using a telnet client to access your mail server. It's the telnet server which is unsafe and you are shutting that down with xinetd.
 
Old 12-14-2006, 02:33 PM   #4
jmj99385
Member
 
Registered: Aug 2005
Distribution: Slackware, Fedora, CentOS
Posts: 42

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by acid_kewpie
xinetd has nothign to do with smtp, why did you think it did?

you can't (easily) block access from a telnet client to any tcp port, i guess you're not really clear on what the use of telnet in that situation is. telnet in itself is an extremely simple client, which does virtually nothing. the only slightly "clever" bit is the server which spawns a login shell on the telnet port when connected to it. as the client is so simple, it can be used in many different ways to troubleshoot servers and netwrok connectivity. it basically just allows a human user to interact with whatever serivce is connected to a tcp port. when used in this way, it's really *not* telnet at all, just a pipe to a tcp port.

as you're hopefully aware telnet is regarded as a huge security risk, and i'd assume that's why you wish to stop it here, but the risk is actually the use of the client and the sever and the way a login esssion works across the two, not the client itself at all.

basically don't try to block it, there's no point and i'm not really even sure it's possible as telnet clients don't really identify themselves in any way at all on connection, they just send whatever keypresses you make and show you what the server replies with, hence it's many many uses debugging smtp, http, etc...
Chris,

I am quite aware that xinetd has nothing to do with SMTP. But, using Telnet you can access the SMTP server. Go here for an example -- http://www.pantz.org/email/misc/smtptelnet.shtml.

What I am trying to do is restrict access to that. In other words, I do not want anyone using telnet to connect to the SMTP server. So my questions remains, how do I do this? Setting in qmail-smtp? Firewall settings? Shutting down xinetd?

Thank you in advance for your help.
 
Old 12-14-2006, 03:04 PM   #5
Dudydoo
Member
 
Registered: Sep 2003
Location: UK
Distribution: I use 'em all ;-)
Posts: 275

Rep: Reputation: 38
You can't stop it
 
Old 12-14-2006, 03:07 PM   #6
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985
did you not read what i wrote?? I'm a network architect, i spend all day working with ethernet and tcp/ip. i know what the issues are here, and going by your reply you really don't understand your own question. maybe if you wish to keep persuing this, actaully give a reason as to why you think this is a bad thign to do.
 
Old 12-15-2006, 02:53 AM   #7
vimalkumar_k
LQ Newbie
 
Registered: Nov 2006
Posts: 14

Rep: Reputation: 0
use iptables to block it... or tcp wrapper...
 
Old 12-15-2006, 02:59 AM   #8
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985Reputation: 1985
Quote:
Originally Posted by vimalkumar_k
use iptables to block it... or tcp wrapper...
no, you didn't read the question correctly. what he wants is not possible. unless you wish to provie otherwise with an example that is...
 
Old 12-25-2006, 07:46 AM   #9
Jaiprakash
LQ Newbie
 
Registered: Dec 2006
Posts: 2

Rep: Reputation: 0
In SMTP, there is two type of relay.

If your SMTP service is in open relay, any one can use your SMTP server to send mails. To resolve this we need to change the relay to closed relay. If you did like this you can safe guard your SMTP server and all of them can get response from port 25 but they can't use your service to send mails without authorization.


Regards,
JP
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
PLESK [Solution] Change port to 23 (telnet) instead of default port 8443 x5452 Linux - Software 6 05-10-2009 05:58 AM
telnet to different port kenhrl Linux - Networking 3 10-29-2004 04:15 PM
telnet to port 80 davee Linux - Networking 5 08-06-2003 03:09 PM
Can't telnet to port 25 scooby_scrappy Linux - Networking 1 05-15-2002 02:28 AM
telnet port 80 doodah Linux - Networking 4 04-27-2001 08:01 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Red Hat

All times are GMT -5. The time now is 09:47 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration