|
Shut down Port 23? Exactly how did they do that? If they used the
port blocking (I'm sure I am mis-mangling the name) then you won't get
non-ssl telnet through that port.
A Telnet Exit program can limit access to known good user profiles and
known good IP addresses, but if your firewall is doing NAT (likely),
I'm not sure either approach would buy you much.
The real question is why allow one user to bypass SSL, are you sure
there is not a way to have that user connect securely?
jte
On Aug 24, 2010, at 6:13 PM, Trevor Perry wrote:
I have a customer who has turned off port 23 and only uses SSL. We
have a
requirement where we must use port 23 for unsecured telnet. How can
I ensure
that opening port 23 does not expose telnet beyond their DMZ/firewall?
Thanks!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--John Earl
President and CEO
Patrick Townsend Security Solutions
"The Encryption Company"
Olympia, WA | www.patownsend.com
Office: 360-357-8971 Ext 118
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.