bb_matt
Executive Member
Just want to know how safe this is :-
Situation :-
Home Network, connects via IPCop to bridged ADSL router.
Setup port forwarding to a Slackware box to port 22, only 165.165.0.0/255 can access.
Setup dyndns
I can now ssh into my slackware box from work and from there, do a samba mount to my windows box.
Windows box - just SharedDocs has a share.
I can only mount the share using the local network - iow, I can't use an external IP. I can also only mount the share from the slackware box. The windows box is otherwise locked down.
I would imagine if I changed sshd on my slackware box to listen on some obscure port, it would be better.
So, is it safe enough to do this ?
EDIT: I'm also wondering if I can use my dnydns.org hostname in the allowed connections to port 22 - IOW, instead of 165.165.0.0/255 - that would be even safer.
Situation :-
Home Network, connects via IPCop to bridged ADSL router.
Setup port forwarding to a Slackware box to port 22, only 165.165.0.0/255 can access.
Setup dyndns
I can now ssh into my slackware box from work and from there, do a samba mount to my windows box.
Windows box - just SharedDocs has a share.
I can only mount the share using the local network - iow, I can't use an external IP. I can also only mount the share from the slackware box. The windows box is otherwise locked down.
I would imagine if I changed sshd on my slackware box to listen on some obscure port, it would be better.
So, is it safe enough to do this ?
EDIT: I'm also wondering if I can use my dnydns.org hostname in the allowed connections to port 22 - IOW, instead of 165.165.0.0/255 - that would be even safer.
Last edited: