Sometimes people seem to think that bruteforcing a random server would a good idea. I don’t agree with them. They just fill up my auth.log and cause several alarm bells to ring. If you use fail2ban, fine, it will handle this for you. If you don’t use it, you could still ban them manually.
If you just want to ban a single source IP - beware of faked sources adresses - until the next reboot of your machine, use this:
iptables -I INPUT -s <sourceip> -j DROP
This reads as follows: Inside the input chain look for the source adress <sourceip> and the jump to chain “DROP”.
If you want to remove this entry you’ll just need to replace the -I in front of INPUT by -D.
Thought about Backup recently? What about Key-Backup?
If you happen to use OpenPGP to encrypt your files, you’ll probably want to do a key backup so you can decrypt them later if your OpenPGP installation should get lost. You’ll only need a few simple commands.
gpg -ao mypublic.key --export <keyid>
gpg -ao myprivate.key --export-secret-key <keyid>
This will export (-o) the public (–export) and private keys (–export-secret-key) of the keypair with the id <keyid> to two seperate files in ASCII (Base64) encoding (-a). How you find out the keyid? Use the parameter –list-keys.
OpenVPN is a great VPN solution: Easy to use, flexible and stable. But it lacks documentation. When trying to assign static ip adresses to my VPN clients I felt a bit lost. The solution is to create a directory inside the OpenVPN configuration directory and put the client-dependent configuration snippets there. Lets assume this directory is called “ccd” for “Client Configuration Directory”. Then you need to add the line “client-config-dir ccd” to your server.conf.
Inside the ccd you create one file for each client you want to configure and call the file exactly as the common name from the clients certificate. In this files you can use ordinary OpenVPN configuration statements. For assigning fixed IPs you would use “ipconfig-push 10.8.0.X 10.8.0.0″ if you use the suggested subnet of “10.8.0.0″.
After migrating to the latest Eclipse Release 3.4 aka Ganymede, I had to reinstall the essential plugins. Neither PDT nor Subclipse did work OOTB. For PDT you can follow the instructions from the PDT Wiki and for Subclipse have a look at the mailing list archives.
Did you every want to actually improve your favorite distribution? Then go to http://ddtp.debian.net/ddtss/index.cgi/xx and help translating Debian to your language!
Since I’ve installed the final release of Firefox 3 on my Debian “lenny” system there is this annoying bug, that Firefox keeps switching to offline mode all the time, i.e. when I close it.
After some searching I found out that there are others who have the same problem and that this is a “feature” related to an application called “Network Manager”. Altough Network Manager is installed - I can’t tell why - I did never use it. So why does Firefox keeps annoying me? I don’t want to click on “File -> Work Offline” everytime I start Firefox to get access to the Internet. If you experience the same problem and wan’t to check if it is NM’s fault then run this command in a terminal and see if you get a result of “3″ (which means that NM thinks you are online) or “4″ (which means offline).
A developer claimed that setting “toolkit.networkmanager.disable” to true would cause Firefox to stop this behavior, I’ll try it out … Nope, doesn’t work. Only completly removing NetworkManager helps.
An interesting Screencast showing some of the new features in Eclipse 3.4 Ganymede can be found at the Screencast Blog.
Is was trying to get Teamspeak 2 (Client) running on a recent Version of Debian Lenny. The Problem was that, the Kernel was compiled w/o OSS Support. Installing “alsa-oss” solved my problem and Teamspeak ran perfect.
tarzan: M$ will odf als standartformat anbieten und amd liefert seine neuen grafikkarten mit linux treibern auf der cd aus…
tarzan: komischer tag
tarzan: wenn heute mal nicht die hölle zufriert
Letzte Kommentare