Sunday, September 27, 2009
Disabling SSH Tunneling
As a corollary to my last post I wanted to describe how to disable TCP forwarding.
You will want to add or uncomment the following line and make sure it is set to no in /etc/ssh/sshd_config
The default is “yes"
Note you will want to make sure that users do not have permissions to set their own forwarders, but this is the global disabling.
This can also be done on a per user basis with the enforce key-based authentication and use per-key directives in each user's authorized_keys file. This is further explained in "AUTHORIZED_KEYS FILE FORMAT" section of sshd http://man.he.net/man5/authorized_keys
I have not done this myself but maybe something you want to evaluate if you are hosting a shared resource.
You will want to add or uncomment the following line and make sure it is set to no in /etc/ssh/sshd_config
AllowTcpForwarding noThe default is “yes"
Note you will want to make sure that users do not have permissions to set their own forwarders, but this is the global disabling.
This can also be done on a per user basis with the enforce key-based authentication and use per-key directives in each user's authorized_keys file. This is further explained in "AUTHORIZED_KEYS FILE FORMAT" section of sshd http://man.he.net/man5/authorized_keys
I have not done this myself but maybe something you want to evaluate if you are hosting a shared resource.
Labels: Linux, Remote Administraton, SSH, Tunneling
Friday, June 20, 2008
Configuring a home Vyatta router with DHCP Client/Server and NAT
I struggled with this quite a bit the first time around finding a source of information to configure Vyatta's router solution just because examples are hard to find (not that there are any problems with it) so here is the configuration and examples that I had, I left IP addresses in there for examples but they may have to be changed depending on your home network setup
Before entering the below commands you have to be in configure mode and after commit them to memory (the commits are in there but will not put the configure in as you could do it all in one or multipule configure sessions)
Configure Outside interface for DHCP (eth0 is my outside interface)
Configure DHCP server for the internal network (note because of line wrap this looks funny but "set service" is the start of a new line that continues all the way to the next set service. One per line)
Set NAT (genaric rule to enable nat)
Forwarding SSH (creates a rule to forward ssh from any source to any destination that comes to the outside interface eth0 , this is because I have a dynamic IP address externaly so setting the destination is not useful and do not know the IP that I will be coming from) This acts like "port forwarding" in home routers
Before entering the below commands you have to be in configure mode and after commit them to memory (the commits are in there but will not put the configure in as you could do it all in one or multipule configure sessions)
Configure Outside interface for DHCP (eth0 is my outside interface)
dhclient eth0Configure inside interface with static IP address (eth1 is my inside interface)
commit
set interfaces ethernet eth1 address 192.168.11.1/24
commit
Configure DHCP server for the internal network (note because of line wrap this looks funny but "set service" is the start of a new line that continues all the way to the next set service. One per line)
set service dhcp-server shared-network-name LAN subnet 192.168.11.0/24 start 192.168.11.10This toruns on the dhcp server for the 192.168.11.0/24 network and starts handing out IP addresses at 10 and stops at 50 I also set my outside DNS server as handed out by DHCP and the default router handed out
set service dhcp-server shared-network-name LAN subnet 192.168.11.0/24 start 192.168.11.10 stop 192.168.11.50
set service dhcp-server shared-network-name LAN subnet 192.168.11.0/24 dns-server 24.159.193.40
set service dhcp-server shared-network-name LAN subnet 192.168.11.0/24 default-router 192.168.11.1
commit
Set NAT (genaric rule to enable nat)
set service nat rule 1 outbound-interface eth0
set service nat rule 1 source address 192.168.11.0/24
set service nat rule 1 type masquerade
Forwarding SSH (creates a rule to forward ssh from any source to any destination that comes to the outside interface eth0 , this is because I have a dynamic IP address externaly so setting the destination is not useful and do not know the IP that I will be coming from) This acts like "port forwarding" in home routers
set service nat rule 2
set service nat rule 2 type destination
set service nat rule 2 inbound-interface eth0
set service nat rule 2 protocol tcp
set service nat rule 2 destination address 0.0.0.0/0
set service nat rule 2 destination port ssh
set service nat rule 2 source address 0.0.0.0/0
set service nat rule 2 inside-address address 192.168.11.48
commit
Labels: Linux, NAT, router, Vyatta
Thursday, June 5, 2008
Samba configuration
I have run across multiple times having overly complex SAMBA configurations to share with a windows system. I wanted to post a simplified version of my configuration file. This is in share mode with a single directory who's share name is str
[global]
security = share
[str]
path = /str/
writable = yes
browsable = yes
public = no
username = username
What this does is share out the file /str/ to people specified with the username filed. These users will then need a samba password setup with the smbpasswd command run in their session on the Linux machine (so for example account test1 would have to be logged in and run "smbpasswd" and set a file sharing password)
This will allow you to restrict access to just the people specified with their password.
Removing the username = field and changing the public = yes will allow you to openly share the files and make them writeable if you so desire
Another useful option is the netbios name = option (not above) which allows you to set the computers netbios name rather then having to navigate to it by IP address
Labels: Filesharing, Linux, Samba
Subscribe to Posts [Atom]