Linux - Security This forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
10-06-2005, 08:50 AM
|
#1
|
Member
Registered: Feb 2005
Location: Ottawa/Montréal
Distribution: Slackware + Darwin (MacOS X)
Posts: 468
Rep:
|
ssh login reverse mapping failed, should I worry?
Code:
Address 67.71.152.11 maps to 10.152.71.61.in-addr.arpa, but this
does not map back to the address - POSSIBLE BREAKIN ATTEMPT!
I just got this when logging in to my Slackware box from my campus wifi (first time I've used the campus wifi, new system). Could that be the culprit?
PS 67.71.152.11 is the address of my server as reported by ifconfig | grep ppp0.
|
|
|
10-06-2005, 04:44 PM
|
#2
|
Member
Registered: Apr 2002
Posts: 498
Rep:
|
It just means that the reverse DNS for your campus wifi is not properly configured and SSH could not determine a hostname for the IP in question. Personally, I don't know why SSH gripes about this, but I'm sure there is a (somewhat) legitimate reason somewhere.
|
|
|
10-06-2005, 05:34 PM
|
#3
|
Senior Member
Registered: Mar 2003
Location: Beautiful BC
Distribution: RedHat & clones, Slackware, SuSE, OpenBSD
Posts: 1,791
Rep:
|
From the sshd_config manpages
Quote:
UseDNS Specifies whether sshd should lookup the remote host name
and check that the resolved host name for the remote IP
address maps back to the very same IP address.
The default is "yes"
|
Last edited by ppuru; 10-06-2005 at 05:36 PM.
|
|
|
10-16-2005, 09:27 AM
|
#4
|
Member
Registered: Feb 2005
Location: Ottawa/Montréal
Distribution: Slackware + Darwin (MacOS X)
Posts: 468
Original Poster
Rep:
|
I had a feeling it was UseDNS, but I'm never sure whether it's the sshd or ssh that outputs those messages (i.e., I wasn't totally sure whether it was my end or the server end that was complaining about the DNS entry being wrong).
Thanks.
|
|
|
All times are GMT -5. The time now is 12:48 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|