How to restrict users to SFTP only instead of SSH
Sometimes you want to have users, that have access to files on your server, but don’t want them to be able to log in and execute commands on your server.
A chronological documentation test project, nothing serious, really!
Sometimes you want to have users, that have access to files on your server, but don’t want them to be able to log in and execute commands on your server.
If you have the Apache webserver running on port 80 that will provide a suitable test candidate. If not you can choose another port you know is in use.
There are many common scenarios where keeping track of open network connections is useful. General troubleshooting or fixing specific problems are two obvious cases which spring to mind. The most useful tool I’ve discovered for this purpose is tcptrack.
There are times when you’re looking for a particular library, or file, which you know is available to Debian/Ubuntu but you cannot find the package which contains it. This is the kind of job that the Debian packages site helped with in the past, but given its current unavailability we’ll look at another approach.
I needed a way to block some websites permanently and others outside of certain hours. After looking at some inline solutions I realised that I could easily do what was needed with squid alone. I created the following ACLs in squid’s config file : acl blockedsites url_regex -i “/etc/squid/blocked.txt” acl bannedsites url_regex -i “/etc/squid/banned.txt” acl […]