more security

Post Reply
Message
Author
bmike1
Posts: 113
Joined: Mon Jul 23, 2012 8:35 pm

more security

#1 Post by bmike1 »

It is neat. I was asked to show a log file on a machine who's x server was not running so I jumped on the machine and I could log in to a tty. so I ran:
scp <file to copy> <user>@<ipaddress>:<file>
Well scp would not work. It replied 'Connection timed out'. So I jumped on the other computer and tried:
scp <user>@<ipaddress>:<file> <file to copy>
and it would ask for a passwd but would never recognize the passwd entered.
After learning the solution to the x problem I finally figured out the scp problem: a little bit ago I had mapped the ip addresses to words in my router so I wouldn't have to type out the 192.168.0.1,2,3,4,or whatever. I had forgotten I did that and I didn't know that it would not recognize the <ipaddress> as valid. SO I guess if you're real paranoid you can put another layer of protection down (in that they will need a blind guess as to the host name instead of knowing it is 192.168.?.? <or one of the other public addresses>).

Post Reply

Return to “Older Versions”