On Thu, Mar 04, 2004 at 11:30:44PM -0700, Ryan Cox wrote:* Disclaimer: I work for a division of OIT*
They said they purposely don't enable reverse DNS for
connections that are NATed from resnet because it is a security issue.
When I lived in the dorms in 2000-2001 I had the exact same problem.
The people at OIT I talked to were a bunch of idiots. It's unbelievable how clueless they are. I was having basically the
exact same problem you were talking about. FTP, Telnet, SSH, etc. wouldn't
work to many servers because their reverse DNS wasn't set up right, but
trying to explain that to them was hopeless. Their comments didn't
reflect at all what I was saying.
I find it odd that they would say that reverse DNS is a security issue on our side (although for reasons i will point out in a second it kind of makes sense why they would say this) Generally reverse DNS is used as a security measure to make sure that someone connecting to you or sending email to you is really who they say they are (though a lot of people argue that it is a very inneffective security measure that really doesn't do anything except effect legitimate users), i have never heard it refered to as a security hole to have reverse DNS enabled, although i guess you could argue that reverse DNS gives you information about the range of addresses applied to a domain name and a little other information, but nothing that would be at all difficult to find with reverse DNS turned off.
Now to the issue of dealing with OIT, we have to remember that very few people who work for OIT are CS or CE majors and really have very little experience with computers. They are trained how to do specific things and that is what they know how to do, but not much beyond that. As a point at my job the default shell on a machine i was using was k-shell, i don't have root so i had to call someone who could change it for me and so i did and asked to have it changed to bash, well this person had no clue what bash was so i got the run around about how the tools were set up to work in a certain environment and i wouldn't be able to do my job if i wasn't using what they had set up, finally i was told that if i REALLY wanted it then my boss would have to call and request it. Well that much trouble for something as trivial as changing the default shell for one employee shows that we should not be surprised if a student wants them to implement a new service on production servers across campus.
Many people are very concerned about security, and the less they know about computers the more paranoid they are so don't be surprised, and try not to get too upset, when people are reluctant to make any changes (no matter how trivial they may be) to the computers on campus.
-chris
____________________
BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
