Guest User

The paranoid #! Security Guide

a guest
Feb 20th, 2015
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 83.67 KB | None | 0 0
  1. Table of Contents:
  3. Introduction
  5. Basic Considerations
  7. BIOS-Passwords
  9. Encryption
  10. Making TrueCrypt Portable
  11. Hardware Encryption
  12. Attacks on Full-Disk-Encryption
  13. Attacks on encrypted Containers
  14. Debian's encrypted LVM pwned
  15. Solutions
  16. eCryptfs
  17. Encrypting SWAP using eCryptfs
  18. Tomb
  19. Advanced Tomb-Sorcery
  21. Keyloggers
  22. Software Keyloggers
  23. Defense against Software Keyloggers
  24. Hardware Keyloggers
  25. Defense against Hardware Keyloggers
  27. Secure File-Deletion
  28. BleachBit
  29. srm [secure rm]
  30. Other Ways to securely wipe Drives
  32. Your Internet-Connection
  33. ipkungfu
  34. Configuring /etc/sysctl.conf
  35. Modem & Router
  37. Intrusion-Detection, Rootkit-Protection & AntiVirus
  38. Snort
  39. RKHunter
  40. RKHunter-Jedi-Tricks
  41. chkrootkit
  42. Tiger
  43. Lynis
  44. debsums
  45. sha256
  46. ClamAV
  48. DNS-Servers
  49. Using secure and censor-free DNS
  50. DNSCrypt
  52. Firefox/Iceweasel
  53. Firefox-Sandbox: Sandfox
  54. Firefox-Preferences
  55. Plugins
  56. Addons
  57. SSL-Search-Engines
  58. Flash-Settings
  59. about:config
  60. Prevent Browser-Fingerprinting
  62. TOR [The Onion Router]
  63. TOR-Warning
  65. I2P
  67. Freenet
  69. Secure Peer-to-Peer-Networks
  71. Mesh-Networks
  73. Proxies
  74. Proxy-Warning
  76. VPN (Virtual Private Network)
  78. The Web
  79. RSS-Feeds
  81. Secure Mail-Providers
  83. Disposable Mail-Addresses
  85. Secure Instant-Messaging/VoIP
  86. TorChat
  87. OTR [Off-the-Record-Messaging]
  88. Secure and Encrypted VoIP
  90. Social Networking
  91. Facebook
  92. Alternatives to Facebook
  94. Passwords
  95. pwgen
  96. KeePass
  98. Live-CDs and VM-Images that focus on security and anonymity
  100. Further Info/Tools
  103. Introduction
  105. Hi all!
  107. This is my first attempt to contribute something to the community. Basically you can find everything I write here somewhere else on the web or in some book - but exactly that is the problem. You can literally spend weeks digging up all this stuff. And to save you some trouble I thought: "Heck, let's just put this into a little manual."
  109. You're dealing with a somewhat paranoid security setup for debian-based systems like #!.
  110. [This is the end-user and not the |-|4xx0|2-version. We are not getting into virtual-virtual-virtual-machine-double-vpn-ssh-proxy-chain-from-your-internet-cafe-type-stuff.]
  112. In this small guide I simply provide several "recipes" for securing both your box and your internet-connection and web-applications. I won't go into the why of all of this in too much detail as I want to provide a simple how-to that people can follow to make their system more secure without having to read through hundreds of pages of explanations. This information can easily be found elsewhere. If you're interested in a certain topic then just fire up a web-search and give it a read.
  114. This guide is not exhaustive of course. As they say, security is a process - and so this guide can only be a place to start which needs to be adjusted to your personal needs.
  116. If you consider to use this information and you find something to be too overcautious for your particular need - just ignore it and move on. One last thing before we begin: I am not a "security-guru" (far from it) - but more appropriately (as my nick suggests) some dude wrapping his head around things...
  117. Basic considerations
  118. BIOS-Passwords
  120. For the physical security of your data you should always employ encrypted drives. But before we get to that make sure you set strong passwords in BIOS for both starting up and modifying the BIOS-settings. Also make sure to disable boot for any media other than your harddrive.
  121. Encryption
  123. With #! this is easy. In the installation you can simply choose to use an encrypted LVM. (For those of you who missed that part on installation and would still like to use an encrypted partition withouth having to reinstall: use these instructions to get the job done.) For other data, e.g. data you store on transportable media you can use TrueCrypt - which is better than e.g. dmcrypt for portable media since it is portable, too. You can put a folder with TrueCrypt for every OS out there on to the unencrypted part of your drive and thus make sure you can access the files everywhere you go.
  125. This is how it is done:
  126. Making TrueCrypt Portable
  128. Download yourself some TC copy.
  130. Extract the tar.gz
  132. Execute the setup-file
  134. When prompted choose "Extract .tar Package File"
  136. go to /tmp
  138. copy the tar.gz and move it where you want to extract/store it
  140. extract it
  142. once it's unpacked go to "usr"->"bin" grab "truecrypt"-binary
  144. copy it onto your stick
  146. give it a test-run
  148. There is really not much more in that tarball than the binary. Just execute it and you're ready for some crypto.
  150. I don't recommend using TrueCrypt's hidden container, though. Watch this vid to find out why. If you don't yet know how to use TrueCrypt check out this guide. [TrueCrypt's standard encryption is AES-256. This encryption is really good but there are ways to attack it and you don't know how advanced certain people already got at this. So when prompted during the creation of a TrueCrypt container use: AES-Twofish-Serpent and as hash-algorithm use SHA-512. If you're not using the drive for serious video-editing or such you won't notice a difference in performance. Only the encryption process when creating the drive takes a little longer. But we get an extra scoop of security for that... wink]
  151. Hardware Encryption
  153. There are three different types of hardware encrypted devices available, which are generally called: SED (Self Encrypting Devices)
  155. - Flash-Drives (Kingston etc.)
  156. - SSD-Drives (Samsung etc.)
  157. - HD-Drives (WD, Hitachi, Toshiba etc.)
  159. They all use AES encryption. The key is generated within the device's microprocessor and thus no crucial data - neither password nor key are written to the host system. AES is secure - and thus using these devices can give some extra protection.
  161. But before you think that all you need to do is to get yourself one of these devices and you're safe - I have to warn you: You're not.
  163. So let's get to the reasons behind that.
  164. Attacks on Full-Disk-Encryption
  166. Below we will have a look at a debian specific attack using a vulnerability common with encrypted LVMs.
  168. But you need to be aware that all disk-encryption is generally vulnerable - be it software- or hardware-based. I won't go into details how each of them work exactly - but I will try to at least provide you with a short explanation.
  170. For software-based disk-encryption there are these known attacks:
  172. - DMA-Attacks (DMA/HDMI-Ports are used to connect to a running, locked machine to unlock it)
  174. - Cold-Boot-Attacks (Keys are extracted from RAM after a cold reboot)
  176. - Freezing of RAM (RAM is frozen and inserted into the attacker's machine to extratct the key)
  178. - Evil-Maid-Attacks (Different methods to boot up a trojanized OS or some kind of software-keylogger)
  180. For hardware-based disk-encryption there are similar attacks:
  182. - DMA-Attacks (same as with SW-based encryption)
  184. - Replug-Attacks (Drive's data cable is disconnected and connected to attacker's machine via SATA-hotplugging)
  186. - Reboot-Attacks (Drive's data cable is disconnected and connected to attacker's machine after enforced reboot. Then the bios-password is circumvented through the repeated pressing of the F2- and enter-key. After the bios integrated SED-password has been disabled the data-cable is plugged into the attacker's machine. This only works on some machines.)
  188. - Networked-Evil-Maid-Attacks (Attacker steals the actual SED and replaces it with another containing a tojanized OS. On bootup victim enters it's password which is subsequently send to the attacker via network/local attacker hot-spot. Different method: Replacing a laptop with a similar model [at e.g. airport/hotel etc.] and the attacker's phone# printed on the bottom of the machine. Victim boots up enters "wrong" password which is send to the attacker via network. Victim discovers that his laptop has been misplaced, calls attacker who now copies the content and gives the "misplaced" laptop back to the owner.)
  190. A full explanation of all these attacks been be found in this presentation. (Unfortunately it has not yet been translated into English.) An English explanation of an evil-maid-attack against TrueCrypt encrypted drives can be found here
  191. Attacks on encrypted Containers
  193. There are also attacks against encrypted containers. They pretty much work like cold-boot-attacks, without the booting part.
  194. An attacker can dump the container's password if the computer is either running or is in hibernation mode - either having the container open and even when the container has been opened during that session - using temporary and hibernation files.
  195. Debian's encrypted LVM pwned
  197. This type of "full" disk encryption can also be fooled by an attack that could be classified as a custom and extended evil-maid-attack. Don't believe me? Read this!
  199. The problem basically is that although most of the filesystem and your personal data are indeed encrypted - your boot partition and GRUB aren't. And this allows an attacker with physical access to your box to bring you into real trouble.
  201. To avoid this do the following:
  202. Micah Lee wrote:
  204. If you don’t want to reinstall your operating system, you can format your USB stick, copy /boot/* to it, and install grub to it. In order to install grub to it, you’ll need to unmount /boot, remount it as your USB device, modify /etc/fstab, comment out the line that mounts /boot, and then run grub-install /dev/sdb (or wherever your USB stick is). You should then be able to boot from your USB stick.
  206. An important thing to remember when doing this is that a lot of Ubuntu updates rewrite your initrd.img, most commonly kernel upgrades. Make sure your USB stick is plugged in and mounted as /boot when doing these updates. It’s also a good idea to make regular backups of the files on this USB stick, and burn them to CDs or keep them on the internet. If you ever lose or break your USB stick, you’ll need these backups to boot your computer.
  208. One computer I tried setting this defense up on couldn’t boot from USB devices. I solved this pretty simply by making a grub boot CD that chainloaded to my USB device. If you google “Making a GRUB bootable CD-ROM,” you’ll find instructions on how to do that. Here’s what the menu.1st file on that CD looks like:
  210. default 0
  211. timeout 2
  212. title Boot from USB (hd1)
  213. root (hd1)
  214. chainloader +1
  216. I can now boot to this CD with my USB stick in, and the CD will then boot from the USB stick, which will then boot the closely watched initrd.img to load Ubuntu. A little annoying maybe, but it works.
  218. (Big thanks to Micah Lee!)
  220. Note: Apparently there is an issue with installing GRUB onto USB with waldorf/wheezy. As soon as I know how to get that fixed I will update this section.
  221. Solutions
  223. You might think that mixing soft- and hardware-based encryption will solve these issues. Well, no. They don't. An attacker can simply chain different methods and so we are back at square one. Of course this makes it harder for an attacker to reach his goals - but he/she will not be stopped by it. So the only method that basically remains is to regard full-disk-encryption as a first layer of protection only.
  225. Please don't assume that the scenarios described above are somewhat unrealistic. In the US there are about 5000 laptops being lost or stolen each week on airports alone. European statistics indicate that about 8% of all business-laptops are at least once either lost or stolen.
  227. A similar risk is there if you leave the room/apartment with your machine locked - but running. So the first protection against these methods is to always power down the machine. Always.
  229. The next thing to remind yourself off is: You cannot rely on full-disk-encryption. So you need to employ further layers of encryption. That means that you will have to encrypt folders containing sensitive files again using other methods such as tomb or TrueCrypt. That way - if an attacker manages to get hold of your password he/she will only have access to rather unimportant files. If you have sensitive or confidential data to protect full-disk encryption is not enough!
  231. When using encrypted containers that contain sensitive data you should shutdown your computer after having used them to clear all temporary data stored on your machine that could be used by an attacker to extract passwords.
  233. If you have to rely on data being encrypted and would be in danger if anyone would find the data you were encrypting you should consider only using a power-supply when using a laptop - as opposed to running on power and battery. That way if let's say, you live in a dictatorship or the mafia is out to get you - and they are coming to your home or wherever you are - all you need to do when you sense that something weird is going on is to pull the cable and hope that they still need at least 30 secs to get to your ram. This can help prevent the above mentioned attacks and thus keep your data safely hidden.
  234. eCryptfs
  236. If for some reason (like performance or not wanting to type in thousands of passwords on boot) you don't want to use an encrypted LVM you can use ecryptfs to encrypt files and folders after installation of the OS.
  238. To find out about all the different features of ecryptfs and how to use them I would like to point you to bodhi.zazen's excellent ecryptfs-tutorial.
  240. But there is one thing that is also important for later steps in this guide and is generally a good idea to do:
  241. Encrypting swap using ecryptfs
  243. Especially when using older machines with less ram than modern computers it can happen quite frequently that your machine will use swap for different tasks when there's not enough ram available to do the job. Apart from the lack of speed this is isn't very nice from a security standpoint: as the swap-partition is not located within your ram but on your harddrive - writing into this partion will leave traces of your activities on the harddrive itself. If your computer happens to use swap during your use of encryption tools it can happen that the passwords to the keys are written to swap and are thus extractable from there - which is something you really want to avoid.
  245. You can do this very easily with the help of ecryptfs.
  247. First you need to install it:
  249. $ sudo apt-get install ecryptfs-utils cryptsetup
  251. Then we need to actually encrypt our swap using the following command:
  253. $ sudo ecryptfs-setup-swap
  255. Your swap-partition will be unmounted, encrypted and mounted again.
  257. To make sure that it worked run this command:
  259. $ sudo blkid | grep swap
  261. The output lists your swap partion and should contain "cryptswap".
  263. To avoid error messages on boot you will need to edit your /etc/fstab to fit your new setup:
  265. $ sudo geany /etc/fstab
  267. Copy the content of that file into another file and save it. You will want to use it as back-up in case something gets screwed up.
  269. Now make sure to find the entry of the above listed encrypted swap partition. If you found it go ahead and delete the other swap-entry relating to the unencrypted swap-partition. Save and reboot to check that everything is working as it should be.
  270. Tomb
  272. Another great crypto-tool is Tomb provided by the dyne-crew.
  274. Tomb uses LUKS AES/SHA-256 and can thus be consider secure. But Tomb isn't just a possible replacement for tools like TrueCrypt.
  276. It has some really neat and easy to use features:
  278. 1) Separation of encrypted file and key
  279. 2) Mounting files and folders in predefined places using bind-hooks
  280. 3) Hiding keys in picture-files using steganography
  282. The documentation on Tomb I was able to find, frankly, seems to be scattered all over the place.
  283. After I played around with it a bit I also came up with some tricks that I did not see being mentioned in any documentation.
  285. And because I like to have everything in one place I wrote a short manual myself:
  287. Installation:
  289. First you will need to import dyne's keys and add them to your gpg-keylist:
  291. $ sudo gpg --fetch-keys
  293. Now verify the key-fingerprint.
  295. $ sudo gpg --fingerprint | grep fingerprint
  297. The output of the above command should be:
  299. Key fingerprint = 8E1A A01C F209 587D 5706 3A36 E314 AFFA 8A7C 92F1
  301. Now, after checking that you have the right key you can trust add it to apt:
  303. $ sudo gpg --armor --export > dyne.gpg
  304. $ sudo apt-key add dyne.gpg
  306. After you did this you want to add dyne's repos to your sources.list:
  308. $ sudo geany /etc/apt/sources.list
  310. Add:
  312. deb dyne main
  313. deb-src dyne main
  315. To sync apt:
  317. $ sudo apt-get update
  319. To install Tomb:
  321. $ sudo apt-get install tomb
  323. Usage:
  325. If you have your swap activated Tomb will urge you to turn it off or encrypt it. If you encrypt it and leave it on you will need to include --ignore-swap into your tomb-commands. To turn off swap for this session you can run
  327. $ swapoff -a
  329. To disable it completely you can comment out the swap in /etc/fstab. So it won't be mounted on reboot. (Please be aware that disabling swap on older computers with not much ram isn't such a good idea. Once your ram is being used fully while having no swap-partition mounted processes and programs will crash.)
  331. Tomb will create the crypto-file in the folder you are currently in - so if you want to create a tomb-file in your documents-folder make sure to
  333. $ cd /home/user/documents
  335. Once you are in the right folder you can create a tomb-file with this command:
  337. $ tomb -s XX create FILE
  339. XX is used to denote the size of the file in MB. So in order to create a file named "test" with the size of 10MB you would type this:
  341. $ tomb -s 10 create test
  343. Please note that if you haven't turned off your swap you will need to modify this command as follows:
  345. $ tomb --ignore-swap -s 10 create test
  347. To unlock and mount that file on /media/test type:
  349. $ tomb open test.tomb
  351. To unlock and mount to a different location:
  353. $ tomb open test.tomb /different/location
  355. To close that particular file and lock it:
  357. $ tomb close /media/test.tomb
  359. To close all tomb-files:
  361. $ tomb close all
  363. or simply:
  365. $ tomb slam
  367. After these basic operations we come to the fun part:
  368. Advanced Tomb-Sorcery
  370. Obviously having a file lying around somewhere entitled: "secret.tomb" isn't such a good idea, really.
  372. A better idea is to make it harder for an attacker to even find the encrypted files you are using. To do this we will simply move its content to another file.
  374. Example:
  376. $ touch true-story.txt true-story.txt.key
  377. $ mv secret.tomb true-story.txt
  378. $ mv secret.tomb.key true-story.txt.key
  380. Now you have changed the filename of the encrypted file in such a way that it can't easily be detected.
  382. When doing this you have to make sure that the filename syntax tomb uses is conserved:
  384. filename.suffix
  385. filename.suffix.key
  387. Otherwise you will have trouble opening the file.
  389. After having hidden your file you might also want to move the key to another medium.
  391. $ mv true-story.txt.key /medium/of/your/choice
  393. Now we have produced quite a bit of obfuscation. Now let's take this even further:
  395. After we have renamed our tomb-file and separated key and file we now want to make sure our key can't be found either.
  397. To do this we will hide it within a jpeg-file.
  399. $ tomb bury true-story.txt.key invisible-bike.jpg
  401. You will need to enter a steganography-password in the process.
  403. Now rename the original keyfile to something like "true-story.txt.key-backup" and check if everything worked:
  405. $ tomb exhume true-story.txt.key invisible-bike.jpg
  407. Your key should have reappeared now. After making sure that everything works you can safely bury the key again and delete the residual key that usually stays in the key's original folder.
  409. By default Tomb's encrypted file and key need to be in one folder. If you have separated the two you will have to modify your opening-command:
  411. $ tomb -k /medium/of/your/choice/true-story.txt.key open true-story.txt
  413. To change the key-files password:
  415. $ tomb passwd true-story.txt.key
  417. If, let's say, you want to use Tomb to encrypt your icedove mail-folders you can easily do that. Usually it would be a pain in the butt to do this kind of stuff with e.g. truecrypt because you would need to setup a container, move the folder to the container and when using the folder you would have to move back to its original place again.
  419. Tomb does this with ease:
  421. Simply move the folders you want to encrypt into the root of the tomb-file you created.
  423. Example:
  425. You want to encrypt your entire .icedove folder. Then you make a tomb-file for it and move the .icedove folder into that tomb. The next thing you do is create a file named "bind-hooks" and place it in the same dir. This file will contain a simple table like this:
  427. .icedove .icedove
  428. .folder-x .folder-x
  429. .folder-y .folder-y
  430. .folder-z .folder-z
  432. The fist column denotes the path relative to the tomb's root. The second column represents the path relative to the user's home folder.
  434. So if you simply wanted to encrypt your .icedove folder - which resides in /home/user/ the above notation is fine. If you want the folder to be mounted elsewhere in the your /home you need to adjust the lines accordingly.
  436. One thing you need to do after you moved the original folder into the tomb is to create a dummy-folder into which the original's folders content can be mounted. So you simply go into /home/user and create a folder named ".icedove" and leave it empty.
  438. The next time you open and mount that tomb-file your .icedove folder will be where it should be and will disappear as soon as you close the tomb. Pretty nice, hu?
  440. I advise to test this out before you actually move all your mails and prefs into the tomb. Or simply make a backup. But use some kind of safety-net in order not to screw up your settings.
  441. Keyloggers
  443. Keyloggers can pose a great thread to your general security - but especially the security of your encrypted drives and containers. If someone manages to get a keylogger onto your system he/she will be able to collect all the keystrokes you make on your machine. Some of them even make screenshots.
  445. So what kind of keyloggers are there?
  446. Software Keyloggers
  448. For linux there are several software-keyloggers available. Examples are lkl, uberkey, THC-vlogger, PyKeylogger, logkeys.
  449. Defense against Software Keyloggers
  451. 1) Never use your system-passwords outside of your system
  453. Generally everything that is to be installed under linux needs root access or some priveliges provided through /etc/sudoers. But an attacker could have obtained your password if he/she was using a browser-exploitation framework such as beef - which also can be used as a keylogger on the browser level. So if you have been using your sudo or root password anywhere on the internet it might have leaked and could thus be used to install all kinds of evil sh*t on your machine. Keyloggers are also often part of rootkits. So do regular system-checks and use intrusion-detection-systems.
  455. 2) Make sure your browser is safe
  457. Often people think of keyloggers only as either a software tool or a piece of hardware equipment installed on their machine. But there is another threat that is actually much more dangerous for linux users: a compromised browser. You will find a lot of info on how to secure your browser further down. So make sure you use it.
  459. Compromising browsers isn't rocket science. And since all the stuff that is actually dangerous in the browser is cross-plattform - you as a linux-user aren't safe from that. No matter what short-sighted linux-enthusiasts might tell you. A java-script exploit will pwn you - if you don't secure your browser. No matter if you are on OSX, Win or debian.
  461. 3) Check running processes
  463. If your attacker isn't really skilled or determined he/she might not think about hiding the process of the running keylogger. You can take a look at the output of
  465. $ ps -aux
  467. or
  469. $ htop
  471. or
  473. $ pstree
  475. and inspect the running processes. Of course the attacker could have renamed it. So have a look for suspicious processes you have never heard of before. If in doubt do a search on the process or ask in a security-related forum about it.
  477. Since a lot of keyloggers come as the functionality of a rootkit it would be much more likely that you would have one of these.
  479. 4) Do daily scans for rootkits
  481. I will describe tools for doing that further below. RKHunter and chkrootkit should definitely be used. The other IDS-tools described give better results and are much more detailed - but you actually need to know a little about linux-architecture and processes to get a lot out of them. So they're optional.
  483. 5) Don't rely on virtual keyboards
  485. The idea to defeat a keylogger by using a virtual keyboard is nice. But is also dangerous. There are some keyloggers out there that will also capture your screen activity. So using a virtual keyboard is pretty useless and will only result in the false feeling of security.
  486. Hardware Keyloggers
  488. There is also an ever growing number of hardware keyloggers. Some of which use wifi. And some of them can be planted inside your keyboard so you wouldn't even notice them if you inspected your hardware from the outside.
  489. Defense against Hardware Keyloggers
  491. 1) Inspect your Hardware
  493. This one's obvious.
  495. 2) Check which devices are connected to your machine
  497. There is a neat little tool called USBView which you can use to check what kind of usb-devices are connected to your machine. Some - but not all - keyloggers that employ usb will be listed there. It is available through the debian-repos.
  499. $ sudo apt-get install usbview
  501. Apart from that there's not much you can do about them. If a physical attack is part of your thread-model you might want to think about getting a laptop safe in which you put the machine when not in use or if you're not around. Also, don't leave your laptop unattended at work, in airports, hotels and on conferences.
  502. Secure File-Deletion
  504. Additional to encrypted drives you may also want to securely delete old data or certain files. For those who do not know it: regular "file deletion" does not erase the "deleted" data. It only unlinks the file's inodes thus making it possible to recover that "deleted" data with forensic software.
  506. There are several ways to securely delete files - depending on the filesystem you use. The easiest is:
  507. BleachBit
  509. With this little tool you can not only erase free disc space - but also clean your system from various temporary files you don't need any longer and that would give an intruder unnecessary information about your activities.
  511. To install:
  513. $ sudo apt-get install bleachbit
  515. to run:
  517. $ bleachbit
  519. Just select what you need shredding. Remember that certain functions are experimental and may cause problems on your system. But no need to worry: BleachBit is so kind to inform you about that and give you the chance to cancel your selection.
  521. Another great [and much more secure] tool for file deletion is:
  522. srm [secure remove]
  524. $ sudo apt-get install secure-delete
  526. Usage:
  528. Syntax: srm [-dflrvz] file1 file2 etc.
  530. Options:
  531. -d ignore the two dot special files "." and "..".
  532. -f fast (and insecure mode): no /dev/urandom, no synchronize mode.
  533. -l lessens the security (use twice for total insecure mode).
  534. -r recursive mode, deletes all subdirectories.
  535. -v is verbose mode.
  536. -z last wipe writes zeros instead of random data.
  538. Other ways to securely wipe drives
  540. To overrite data with zeros:
  542. # dd if=/dev/zero of=/dev/sdX
  544. or:
  546. $ sudo dd if=/dev/zero of=/dev/sdX
  548. To overwrite data with random data (makes it less obvious that data has been erased):
  550. # dd if=/dev/urandom of=/dev/sdX
  552. or:
  554. $ sudo dd if=/dev/urandom of=/dev/sdX
  556. Note: shred doesn't work reliably with ext3.
  557. Your Internet-Connection
  559. Generally it is advised to use a wired LAN-connection - as opposed to wireless LAN (WLAN).
  560. For further useful information in regards to wireless security read this. If you must use WLAN please use WPA2 encryption. Everything else can be h4xx0red by a 12-year-old using android-apps such as anti.
  562. Another thing is: Try only to run services on your machine that you really use and have configured properly. If e.g. you don't use SSH - deinstall the respective client to make sure to save yourself some trouble. Please note that IRC also is not considered to be that secure. Use it with caution or simply use a virtual machine for stuff like that.
  564. If you do use SSH please consider using Denyhosts or SSHGuard. (If you want to find out what might happen if you don't use such protection see foozer's post.)
  566. So, let's begin with your firewall. For debian-like systems there are several possible firewall-setups and different guis to do the job. However, I found ipkungfu [an iptables-script] to do the best job while being easy to set up. This is how you set it up:
  567. ipkungfu [basic configuration]
  569. download and install:
  571. $ sudo apt-get install ipkungfu
  573. configure:
  575. $ sudo geany /etc/ipkungfu/ipkungfu.conf
  577. uncomment (and adjust):
  579. # IP Range of your internal network. Use ""
  580. # for a standalone machine. Default is a reasonable
  581. # guess.
  582. LOCAL_NET=""
  584. ---
  586. # Set this to 0 for a standalone machine, or 1 for
  587. # a gateway device to share an Internet connection.
  588. # Default is 1.
  589. GATEWAY=0
  591. ---
  593. # Temporarily block future connection attempts from an
  594. # IP that hits these ports (If module is present)
  595. FORBIDDEN_PORTS="135 137 139"
  597. ---
  599. # Drop all ping packets?
  600. # Set to 1 for yes, 0 for no. Default is no.
  601. BLOCK_PINGS=1
  603. ---
  605. # What to do with 'probably malicious' packets
  609. ---
  611. # What to do with obviously invalid traffic
  612. # This is also the action for FORBIDDEN_PORTS
  616. ---
  618. # What to do with port scans
  622. enable ipkungfu to start with the system:
  624. $ sudo geany /etc/default/ipkungfu
  626. change: "IPKFSTART = 0" ---> "IPKFSTART=1"
  628. start ipkungfu:
  630. $ sudo ipkungfu
  632. fire up GRC's Shields Up! and check out the awesomeness.
  634. (special thanks to the ubuntu-community)
  635. Configuring /etc/sysctl.conf
  637. Here you set different ways how to deal with ICMP-packets and other stuff:
  639. $ sudo geany /etc/sysctl.conf
  641. # Do not accept ICMP redirects (prevent MITM attacks)
  642. net.ipv4.conf.all.accept_redirects=0
  643. net.ipv6.conf.all.accept_redirects=0
  644. net.ipv4.tcp_syncookies=1
  645. #lynis recommendations
  646. #net.ipv6.conf.default.accept_redirects=0
  647. net.ipv4.tcp_timestamps=0
  648. net.ipv4.conf.default.log_martians=1
  649. # TCP Hardening - [url][/url]
  650. net.ipv4.icmp_echo_ignore_broadcasts=1
  651. net.ipv4.conf.all.forwarding=0
  652. net.ipv4.conf.all.rp_filter=1
  653. net.ipv4.tcp_max_syn_backlog=1280
  654. kernel.core_uses_pid=1
  655. kernel.sysrq=0
  656. #ignore all ping
  657. net.ipv4.icmp_echo_ignore_all=1
  658. # Do not send ICMP redirects (we are not a router)
  659. net.ipv4.conf.all.send_redirects = 0
  660. # Do not accept IP source route packets (we are not a router)
  661. net.ipv4.conf.all.accept_source_route = 0
  662. net.ipv6.conf.all.accept_source_route = 0
  663. # Log Martian Packets
  664. net.ipv4.conf.all.log_martians = 1
  666. After editing do the following to make the changes permanent:
  668. sudo sysctl -p
  670. (thanks to tradetaxfree for these settings)
  671. Modem & Router
  673. Please don't forget to enable the firewall features of your modem (and router), disable UPnP and change the usernames and admin-passwords. Also try to keep up with the latest security info and updates on your firmware to prevent using equipment such as this. You might also want to consider setting up your own firewall using smoothwall.
  675. Here you can run a short test to see if your router is vulnerable to UPnP-exploits.
  677. The best thing to do is to use after-market-open-source-firmware for your router such as dd-wrt, openwrt or tomato. Using these you can turn your router into an enterprise grade device capable of some real Kungfu. Of course they come with heavy artillery - dd-wrt e.g. uses an IP-tables firewall which you can configure with custom scripts.
  678. Intrusion-Detection, Rootkit-Protection & AntiVirus
  679. snort [basic configuration]
  681. The next thing you might want to do is to take a critical look at who's knocking at your doors.
  683. For this we use snort. The setup is straight forward and simple:
  685. $ sudo apt-get install snort
  687. run it:
  689. $ snort -D (to run as deamon)
  691. to check out packages live type:
  693. $ sudo snort
  695. Snort should automatically start on reboot.
  697. If you want to check out snort's rules take a look at: /etc/snort/rules
  699. To take a look at snorts warnings:
  701. $ sudo geany /var/log/snort/alert
  703. Snort will historically list all the events it logged.
  705. There you will find nice entries like this...
  707. [**] [1:2329:6] MS-SQL probe response overflow attempt [**]
  708. [Classification: Attempted User Privilege Gain] [Priority: 1]
  709. [Xref => [url]][/url]
  711. ...and will thank the flying teapot that you happen to use #! wink
  712. RKHunter
  714. The next thing to do is to set up RKHunter - which is short for [R]oot[K]itHunter.
  716. What does it do? You guessed it: It hunts down rootkits.
  718. Installation again is simple:
  720. $ sudo apt-get install rkhunter
  722. The best is to run rkhunter on a clean installation - just to make sure nothing has been tampered with already.
  724. One very important thing about rkhunter is that you need to give it some feedback: everytime you e.g. make an upgrade to your sytem and some of your binaries change rkhunter will weep and tell you you've been compromised. Why? Because it can only detect suspicious files and file-changes. So, if you go about and e.g. upgrade the coreutils package a lot of change will be happening in /usr/bin - and when you subsequently ask rkhunter to check your system's integrity your log file will be all red with warnings. It will tell you that the file-properties of your binaries changed and you start freaking out. To avoid this simply run the command rkhunter --propupd on a system which you trust to not have been compromised.
  726. In short: directly after commands like apt-get update && apt-get upgrade run:
  728. $ sudo rkhunter --propupd
  730. This tells rkhunter: 'sall good. wink
  732. To run rkhunter:
  734. $ sudo rkhunter -c --sk
  736. You find rkhunter's logfile in /var/log/rkhunter.log. So when you get a warning you can in detail check out what caused it.
  738. To set up a cronjob for RKHunter:
  740. $ sudo geany /etc/cron.daily/
  742. insert and change the mail-address:
  744. #!/bin/bash
  745. /usr/local/bin/rkhunter -c --cronjob 2>&1 | mail -s "RKhunter Scan Details"
  747. make the script executable:
  749. $ sudo chmod +x /etc/cron.daily/
  751. update RKHunter:
  753. $ sudo rkhunter --update
  755. and check if it functions the way it's supposed to do:
  757. $ sudo rkhunter -c --sk
  759. Of course you can leave out the email-part of the cronjob if you don't want to make the impression on someone shoulder-surfing
  760. your email-client that the only one who's sending you emails is your computer... wink
  762. Generally, using snort and rkhunter is a good way to become paranoid - if you're not already. So please take the time to investigate the alerts and warnings you get. A lot of them are false positives and the listings of your system settings. Often enough nothing to worry about. But if you want to use them as security tools you will have to invest the time to learn to interpret their logs. Otherwise just skip them.
  763. RKHunter-Jedi-Tricks
  765. If you're in doubt whether you did a rkhunter --propupd after an upgrade and you are getting a warning you can run the following command:
  767. $ sudo rkhunter --pkgmgr dpkg -c --sk
  769. Now rkhunter will check back with your package-manager to verify that all the binary-changes were caused by legitimate updates/upgrades. If you previously had a warning now you should get zero of them. If you still get a warning you can check which package the file that caused the warning belongs to.
  771. To do this:
  773. $ dpkg -S /folder/file/in/doubt
  775. Example:
  777. $ dpkg -S /bin/ls
  779. Output:
  781. coreutils: /bin/ls
  783. This tells you that the file you were checking (in this case /bin/ls) belongs to the package "coreutils".
  785. Now you can fire up packagesearch.
  787. If you haven't installed it:
  789. $ sudo apt-get install packagesearch
  791. To run:
  793. $ sudo packagesearch
  795. In packagesearch you can now enter coreutils in the field "search for pattern". Then you select the package in the box below. Then you go over to the right and select "files". There you will get a list of files belonging to the selected package. What you want to do now is to look for something like:
  797. /usr/share/doc/coreutils/changelog.Debian.gz
  799. The idea is to get a file belonging to the same package as the file you got the rkhunter-warning for - but that is not located in the binary-folder.
  801. Then you look for that file within the respective folder and check the file-properties. When it was modified at the same time as the binary in doubt was modified you can be quite certain that the change was caused by a legitimate update. I think it is save to say that some script-kiddie trying to break into your system will not be that thorough. Also make sure to use debsums when in doubt. I will get to that a little further down.
  803. Another neat tool with similar functionality is:
  804. chkrootkit
  806. To install:
  808. $ sudo apt-get install chkrootkit
  810. To run:
  812. $ sudo chkrootkit
  814. Other nice intrusion detection tools are:
  815. tiger
  817. Tiger is more thorough than rkhunter and chkrootkit and can aid big time in securing your box:
  819. $ sudo apt-get install tiger
  821. to run it:
  823. $ sudo tiger
  825. you find tiger's logs in /var/log/tiger/
  826. Lynis
  828. If you feel that all the above IDS-tools aren't enough - I got something for you:
  830. Lynis
  831. Lynis wrote:
  833. Lynis is an auditing tool for Unix (specialists). It scans the system and available software, to detect security issues. Beside security related information it will also scan for general system information, installed packages and configuration mistakes.
  835. This software aims in assisting automated auditing, software patch management, vulnerability and malware scanning of Unix based systems
  837. I use it. It is great. If you think you might need it - give it a try. It's available through the debian repos.
  839. $ sudo apt-get install lynis
  841. To run:
  843. $ sudo lynis -c
  845. Lynis will explain its findings in the log-file.
  846. debsums
  848. debsums checks the md5-sums of your system-files against the hashes in the respective repos.
  850. Installation:
  852. $ sudo apt-get install debsums
  854. To run:
  856. $ sudo debsums -ac
  858. This will list all the files to which the hashes are either missing or have been changed. But please don't freak out if you find something like: /etc/ipkungfu/ipkungfu.conf after you have been following this guide... wink
  859. sha256
  861. There are some programs that come with sha256 hashes nowadays. For example: I2P
  863. debsums won't help with that. To check these hashes manually:
  865. $ cd /folder/you/downloaded/file/to/check/to -sha256sum -c file-you-want-to-check
  867. Then compare it to the given hash. Note: This tool is already integrated to debian-systems.
  868. ClamAV
  870. To make sure eveything that gets into your system is clean and safe use ClamA[nti]V[irus].
  872. To install:
  874. $ sudo apt-get install clamav
  876. To update:
  878. $ sudo freshclam
  880. To inspect e.g. your download folder:
  882. $ sudo clamscan -ri /home/your-username/downloads
  884. This will ClamAV do a scan recursively, i.e. also scan the content of folders and inform you about possibly infected files.
  886. To inspect your whole system:
  888. $ sudo clamscan -irv --exclude=/proc --exclude=/sys --exclude=/dev --exclude=/media --exclude=/mnt
  890. This will make ClamAV scan your system recursively in verbose mode (i.e. show you what it is doing atm) whilst excluding folders that shouldn't be messed with or are not of interest and spit out the possibly infected files it finds. To also scan attached portable media you need to modify the command accordingly.
  892. Make sure to test everything you download for possible infections. You never know if servers which are normally trustworthy haven't been compromised. Malicious code can be hidden in every usually employed filetype. (Yes, including .pdf!)
  894. Remember: ClamAV is known for its tight nets. That means that you are likely to get some false positives from time to time. Do a web-search if you're in doubt in regards to its findings.
  896. After you set up your host-based security measures we can now tweak our online security.
  898. Starting with:
  899. DNS-Servers
  900. Using secure and censor-free DNS
  902. To make changes to your DNS-settings:
  904. $ sudo geany /etc/resolv.conf
  906. change your nameservers to trustworthy DNS-Servers. Otherwise your modem will be used as "DNS-Server" which gets its info from your ISP's DNS.
  907. And nah... We don't trust the ISP... wink
  908. Here you can find secure and censor-free DNS-servers. The Germans look here.
  910. HTTPS-DNS is generally preferred for obvious reasons.
  912. Your resolv.conf should look something like this:
  914. nameserver
  915. #CCC DNS-Server
  916. nameserver
  917. #FoeBud DNS-Server
  919. Use at least two DNS-Servers to prevent connectivity problems when one server happens to be down or experiences other trouble.
  921. To prevent this file to be overwritten on system restart fire up a terminal as root and run:
  923. $ sudo chattr +i /etc/resolv.conf
  925. This will make the file unchangeble - even for root.
  927. To revoke this for future changes to the .conf run:
  929. $ sudo chattr -i /etc/resolv.conf
  931. This forces your web-browser to use the DNS-servers you provided instead of the crap your ISP uses.
  933. To test the security of your DNS servers go here.
  934. DNScrypt
  936. What you can also do to secure your DNS-connections is to use DNScrypt.
  938. The thing I don't like about DNScrypt is one of its core functions: to use OpenDNS as your resolver. OpenDNS has gotten quite a bad rep in the last years for various things like aggressive advertising and hijacking google-searches on different setups. I tested it out yesterday and couldn't replicate these issues. But I am certain that some of these "features" of OpenDNS have been actively blocked by my Firefox-setup (which you find below). In particular the addon Request Policy seems to prevent to send you to OpenDNS' search function when you typed in an address it couldn't resolve. The particular issue about that search function is that it apparently is powered by yahoo! and thus yahoo! would log the addresses you are searching for.
  940. Depending on your threat-model, i.e. if you don't do anything uber-secret you don't want anybody to know, you might consider using DNScrypt, as the tool seems to do a good job at encrypting your DNS-traffic. There also seems to be a way to use DNScrypt to tunnel your queries to a DNS-server other than OpenDNS - but I haven't yet checked the functionality of this.
  942. So, if you don't mind that OpenDNS will know every website you visit you might go ahead and configure DNScrypt:
  944. Download the current version.
  946. Then:
  948. $ sudo bunzip2 -cd dnscrypt-proxy-*.tar.bz2 | tar xvf -
  949. $ cd dnscrypt-proxy-*
  951. Compile and install:
  953. $ sudo ./configure && make -j2
  954. $ sudo make install
  956. Adjust -j2 with the number of cpu-cores you want to use for the compilation or have at your disposal.
  958. Go and change your resolv.conf to use localhost:
  960. $ geany /etc/resolv.conf
  962. Modify to:
  964. nameserver
  966. Run DNScrypt as daemon:
  968. $ sudo dnscrypt-proxy --daemonize
  970. According to the developer:
  971. jedisct1 wrote:
  973. DNSCrypt will chroot() to this user's home directory and drop root privileges for this user's uid as soon as possible.
  975. I have to admit that OpenDNS is really fast. What you could do is this: You could use OpenDNS for your "normal" browsing. When you start browsing for stuff that you consider to be private for whatever reasons change your resolv.conf back to the trustworthy DNS-servers mentioned above - which you conveniently could keep as a backup file in the same folder. Yeah, that isn't slick, I know. If you come up with a better way to do this let me know. (As soon as I checked DNScrypt's function to use the same encryption for different DNS-Servers I will make an update.)
  977. The next thing on our list is:
  978. Firefox/Iceweasel
  979. Firefox-Sandbox: Sandfox
  981. Sandfox is a neat little script provided by IgnorantGuru which runs firefox (and other applications) in a sandboxed environment which prevents firefox's access to crucial filesystem-areas in case it gets compromised.
  983. To install:
  985. $ sudo -s
  986. $ gpg --keyserver --recv-keys 7977070A723C6CCB696C0B0227A5AC5A01937621
  987. $ gpg --check-sigs 0x01937621
  988. $ bash -c 'gpg --export -a 01937621 | apt-key add -'
  989. $ echo "deb [url][/url] unstable main" >> /etc/apt/sources.list
  990. $ apt-get update
  991. $ apt-get install sandfox
  993. (Thanks to tradetaxfree)
  995. To run:
  997. $ sudo sandfox firefox
  999. Type "/" into firefox address-bar to check out whether it works. Firefox should now only have access to files it really needs to function and not e.g. /root.
  1001. To be able to download stuff from the web you need to add a bind in sandfox's default profile:
  1003. $ sudo geany /etc/sandfox/default.profile
  1005. add:
  1007. bind=/home/$user/downloads
  1009. Check your systems filename-capitalization to make sure you really grant sandfox access to the right folder
  1011. In #! you can easily set this configuration as your default: simply go to "settings"->"openbox"->"GUI Menu Editor"->"Openbox"->"Web Browser". Then simply add the command "sandfox firefox". For this to work you need to once run
  1013. $ sudo sandfox firefox
  1015. after a system start to create a sandbox. If you happen to find this too much hassle simply go with tradetaxfree's init-script.
  1017. After you successfully sandboxed your browser we now continue to make that particular application much more secure than it is by default.
  1019. First go to:
  1020. Firefox-Preferences
  1022. and change these settings:
  1024. [Some of these are defaults already - but depending on who was/is using the machine you access the interwebs with and other varying factors you might want to control these settings.]
  1026. "General"->"when Firefox starts"->"Show a blank page"
  1027. "General"->"save files to:"Downloads"
  1028. "Content"->check:"Block pop-up windows"
  1029. "Content"->uncheck:"Enable JavaScript" [optional - NoScript Add-on will block it anyway]
  1030. "Content"->"Fonts & Colors"->"Advanced"->"Serif":"Liberation Sans"
  1031. "Content"->"Fonts & Colors"->"Advanced"->"Sans-serif":"Liberation Sans"
  1032. "Content"->"Fonts & Colors"->"Advanced"->uncheck:"Allow pages to choose their own fonts"
  1033. "Content"->"Languages"->choose *only*:"en-us" [remove all others, if any]
  1034. "Applications"->choose:"Always ask" for every application - if not possible:choose:"Preview in Firefox/Nightly"
  1035. "Privacy"->"Tracking"->check:"Tell websites I do not want to be tracked"
  1036. "privacy"->"History"->"Firefox will:"Use custom settings for history"
  1037. "privacy"->"History"->uncheck:"Always use private browsing mode"
  1038. "privacy"->"History"->uncheck:"Remember my browsing and download history"
  1039. "privacy"->"History"->uncheck:"Remember search and form history"
  1040. "privacy"->"History"->uncheck:"Accept cookies from sites"
  1041. "privacy"->"History"->uncheck:"Accept third-party cookies"
  1042. "privacy"->"History"->check:"Clear history when Firefox/Nightly closes"
  1043. "privacy"->"History"->"settings":check all -> except:"Site Preferences"
  1044. [to enable cookies for certain trusted sites: use:"Exceptions" and paste URL of site and modify settings according to your preference. If you additionally use Cookie-Monster (Add-on) you need to uncheck "Block all cookies" in CM-Options]
  1045. "privacy"->"location bar"->"When using the location bar, suggest:"->choose:"Nothing"
  1046. "security"->check:"Warn me when sites try to install add-ons"
  1047. "security"->check:"Block reported attack sites"
  1048. "security"->check:"Block reported web forgeries"
  1049. "security"->"Passwords"->uncheck:"Remember passwords for sites"
  1050. "security"->"Passwords"->uncheck:"Use a master password"
  1051. "advanced"->"General"->"System Defaults"->uncheck:"Submit crash reports"
  1052. "advanced"->"General"->"System Defaults"->uncheck:"Submit performance data"
  1053. "advanced"->"Update"->check:"Automatically install updates"
  1054. "advanced"->"Update"->check:"Warn me if this will disable any of my add-ons"
  1055. "advanced"->"Update"->check:"Automatically update Search Engines"
  1056. "advanced"->"Encryption"->"Protocols"->check:"Use SSL 3.0"
  1057. "advanced"->"Encryption"->"Protocols"->check:"Use TLS 1.0"
  1058. "advanced"->"Encryption"->"Certificates"->"When a server requests my personal certificate"->check:"Ask me every time"
  1060. Plugins
  1062. at the most use:
  1064. Java
  1066. Flash [Be aware of the latest security holes in flash!
  1068. Only allow them to run on trusted sites!
  1069. Addons
  1071. Empty Cache Button [optional]
  1073. Calomel SSL Validation [cool little addon which does exactly what its name says and also has some more tweaks in the settings]
  1075. Adblock Edge
  1077. [---> Filter Supscriptions: make sure you get some anti-tracking filters up and running! (depending on location & internet use)]
  1079. Easylist
  1081. EasyPrivacy
  1083. fanboy-adblock
  1085. Fanboy's Tracking List
  1087. Fanboy's Annoyance List
  1089. [---]
  1091. BetterPrivacy [LSO/Flash-Cookie-Protection]
  1093. Cookie Monster [Allows you to Manage your Cookie-Policies. For less baggage use Firefox/Iceweasel "Preferences" -> "Privacy"]
  1095. HTTPS-Everywhere [Download via] [settings: enable SSL-Observatory but don't allow to transmit ISP-data]
  1097. HTTPS Finder
  1099. NoScript [go to "settings" and check "also apply on whitelisted sites"]
  1101. Perspectives [SSL-Cerfiticate-Control - go to settings: "notary servers" -> check "only contact when websites cause security error"]
  1103. RefControl [controls your HTTP-Referers - setting: "block" -> "3rd parties only"]
  1105. Request Policy [rejects cross-site requests]
  1107. WOT [Web of Trust - user based website ratings that show up in websearches. Caution: Not very accurate. Always double check when in doubt. This addon tends
  1108. to get abused by different groups of users who either give malicious sites good ratings - or flag perfectly good sites.]
  1110. PwdHash [Nice addon to help your password management. Use "F2" when entering a password into a password field when setting up a new account somewhere to create a MD5-hash using your password and the domain. (When logging in you have to select the password-field and press F2 again to run the hashing.) This way you can use the same password on different sites without having to worry about security implications - because every site gets its own password generated through the hash. The tool is provided by Standford University and can be trusted. No data is actually transmitted to their servers. The hash is generated using your local java-script. If you need to login from a machine that doesn't have pwdhash installed: go to -> their SSL is very strong.]
  1112. FoxyProxy [a convenient Proxy Switcher]
  1114. Useragent Switcher [Does exactly that. But be careful: If you set your user-agent as shown below - using this addon it will overwrite these settings and will not automatically restore them if you turn off the switcher. So you would have to manually reconfigure about:config again. Which kinda sucks. But you can get a whole load really cool user agents here. Simply download the .xml and import it to the Useragent Switcher. There are really neat current agents in there: e.g. all kinds of different web browser for all OSs and of course various bots. Google bot comes in handy when you need access to some forum... wink]
  1116. Web Developer [Has some cool features. If you like inspecting websites just check it out.]
  1118. Bloody Vikings [Creates disposable mail-addresses]
  1120. Note: You don't need Ghostery. The above mentioned Adblock lists do a much better job protecting you from web-tracking without using the additional resourced Ghostery uses.
  1122. Of course there are more addons you could use. But I don't really see the point of them. Most of them either are snake-oil or even dangerous. But please inform me if you happen to come across something really cool which could help improve security which none of the setting provided here can do.
  1124. To keep your ISP and possible MITM-attackers from reading what you do on the web always use SSL - as far as it is available. To help with this use:
  1125. SSL-Search Engines
  1127. To get them go here.
  1129. The user "SSL Search Bar" has provided easily installable SSL-searchbar-plugins
  1131. You get SSL-plugins for all the alternative search-engines like ixquick, duckduckgo etc. there. Install those you happen to use.
  1133. Privatelee also looks promising. But I haven't tried it out extensively.
  1135. The next thing to do is to change macromedias flash-settings:
  1136. Flash-Settings
  1138. Go here.
  1140. And fight yourself through their nasty settings-manager. Set everything to "0" or "never allow"/"never ask again" and
  1141. delete all stored website-content. Give special attention to the "webcam and mic"-options... wink
  1143. You might as well set the permissions of your .macromedia folder to read only - but that's kind of unnecessary because you want to make sure to edit the options mentioned above - to make sure that you don't allow websites to use your mic or webcam... [I actually take this one step further by disabling them in BIOS and sticking some neatly cut little piece of black cardboard on my webcam. Just because you're paranoid doesn't mean they aren't after you... big_smile ] And if you set the parameters in the settings-manager accordingly nothing will be written to that folder anyway.
  1145. Now we come to the fun part. Finetuning Firefox using about:config. If you've never done this before: No reason to freak out. It's really easy.
  1146. about:config
  1148. [You can simply copy/paste these variables into the search-bar at the top: e.g. "browser.cache.disk.enable" and
  1149. then double-click on the entry that shows up to modify the settings.]
  1151. ---disable browser cache:
  1152. browser.cache.disk.enable:false
  1153. browser.cache.disk_cache_ssl:false
  1154. browser.cache.offline.enable:false
  1155. browser.cache.memory.enable:false
  1156. browser.cache.disk.capacity:0
  1157. browser.cache.disk.smart_size.enabled:false
  1158. browser.cache.disk.smart_size.first_run:false
  1159. browser.cache.offline.capacity:0
  1162. dom.indexedDB.enabled:false
  1163. dom.battery.enabled:false
  1164. ---disable history & localization
  1166. browser.sessionstore.resume_from_crash:false
  1167. geo.enabled:false
  1168. ---misc other tweaks:
  1169. keyword.enabled:false
  1170. network.dns.disablePrefetch:true -> very important when using TOR
  1171. network.dns.disablePrefetchFromHTTPS -> very important when using TOR
  1172. dom.disable_window_open_feature.menubar:true
  1173. dom.disable_window_open_feature.personalbar:true
  1174. dom.disable_window_open_feature.scrollbars:true
  1175. dom.disable_window_open_feature.toolbar:true
  1176. browser.identity.ssl_domain_display:1
  1177. browser.urlbar.autocomplete.enabled:false
  1178. browser.urlbar.trimURL:false
  1179. privacy.sanitize.sanitizeOnShutdown:true
  1180. network.http.sendSecureXSiteReferrer:false
  1181. network.http.spdy.enabled:false ---> use http instead of google's spdy
  1182. plugins.click_to_play:true ---> also check each drop-down-menu under "preferences"->"content"
  1183. security.enable_tls_session_tickets:false ---> disable https-tracking
  1184. security.ssl.enable_false_start:true ---> disable https-tracking
  1185. extensions.blocklist.enabled:false ---> disble Mozilla's option to block/disable your addons remotely
  1186. webgl.disabled:true ---> disable WebGL ([url][/url])
  1187. network.websocket.enabled:false ---> ***Tor Users: This is extremely important as it could blow your cover! See: [url]***[/url]
  1188. ---make your browsing faster:
  1189. network.http.pipelining:true
  1190. network.http.pipelining.ssl:true
  1191. network.http.proxy.pipelining:true
  1192. network.http.max-persistent-connections-per-proxy:10
  1193. network.http.max-persistent-connections-per-server:10
  1194. network.http.max-connections-per-server:15
  1195. network.http.pipelining.maxrequests:15
  1196. network.http.redirection-limit:5
  1197. network.dns.disableIPv6:true
  1199. dom.popup_maximum Mine:10
  1200. network.prefetch-next:false
  1201. browser.backspace_action:0
  1202. browser.sessionstore.max_tabs_undo:5
  1203. browser.sessionhistory.max_entries:5
  1204. browser.sessionstore.max_windows_undo:1
  1205. browser.sessionstore.max_resumed_crashes:0
  1206. browser.sessionhistory.max_total_viewers:0
  1207. browser.tabs.animate:0
  1209. [thanks to machinebacon for these last entries.
  1210. Prevent Browser Fingerprinting [still in about:config]
  1213. For all Firefox Versions after 17.0 [you should be using current versions and update them regularly anyway - to do this go to "preferences"->"advanced"->"update" select: "automatically install updates" & "warn me if this will disable any of my addons"] [not required for iceweasel]
  1215. For the following changes right-click in about:config and select "new"->"string" and enter in this order:
  1217. Variable: Value:
  1219. general.useragent.override Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0
  1220. general.appname.override Netscape
  1221. general.appversion.override 5.0 (Windows)
  1222. general.oscpu.override Windows NT 6.1
  1223. general.platform.override Win32
  1224. general.productSub.override 20100101
  1225. general.buildID.override 0
  1226. general.useragent.vendor [enter variable - but leave value blank]
  1227. general.useragent.vendorSub [enter variable - but leave value blank]
  1228. intl.accept_languages en-us,en;q=0.5
  1229. network.http.accept.default text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
  1230. network.http.accept-encoding gzip, deflate
  1232. This creates a fake-profile of your browser via the readable HTTP-headers it sends.
  1234. Check out if your browser is profilable.
  1236. With all the above settings I get 8.1 bits of identifying information at Panopticlick for my browser - which is really good.
  1238. Considering:
  1240. "In particular, a fingerprint that carries no more than 15-20 bits of identifying information will in almost all cases be sufficient to uniquely identify a particular browser, given its IP address, its subnet, or even just its Autonomous System Number."
  1242. Source: EFF's "Browser Uniqueness" [page 3]
  1244. Also check your settings on - but don't rely on it. Apparently they are quite busy promoting their JonDonym-Browser and services - which quite frankly I don't think anyone needs. I would rather warn you to use it since according to this defcon-talk JAP/JonDonym has implemented tracking-features which are disabled by default but can be activated anytime. So don't use it.
  1246. Now, after having configured your host-based security and your web-browser we can start connecting to the web. But there are different options:
  1247. TOR [The Onion Router]
  1249. TOR is probably the most famous anonymizing-tool available. You could consider it a safe-web proxy. [Update: I wouldn't say that any longer. See the TOR-Warning below for more info.] Actually, simply put, it functions as a SOCKS-proxy which tunnels your traffic through an encrypted network of relays in which your ip-address can not be traced. When your traffic exits the network through so-called exit-nodes the server you are contacting will only be able to retrieve the ip-address of the exit-node. It's pretty useful - but also has a few drawbacks:
  1251. First of all it is slow as f**k. Secondly exit-nodes are often times honey-pots set up by cyber-criminals and intelligence agencies. Why? The traffic inside the TOR-network is encrypted - but in order to communicate with services on the "real" internet this traffic needs to be decrypted. And this happens at the exit-nodes - which are thus able to inspect your packets and read your traffic. Pretty uncool. But: you can somewhat protect yourself against this kind of stuff by only using SSL/https for confidential communications such as webmail, forums etc. Also, make sure that the SSL-certificates you use can be trusted, aren't broken and use secure algorithms. The above mentioned Calomel SSL Validation addon does a good job at this. Even better is the Qualys SSL Server Test.
  1253. The third bummer with TOR is that once you start using TOR in an area where it is not used that frequently which will be almost everywhere - your ISP will directly be able to identify you as a TOR user if he happens to use DPI (Deep Packet Inspection) or flags known TOR-relays. This of course isn't what we want. So we have to use a workaround. (For more info on this topic watch this vid: How the Internet sees you [27C3])
  1255. This workaround isn't very nice, I admit, but basically the only way possible to use TOR securely.
  1257. So, the sucker way to use TOR securely is to use obfuscated bridges. If you don't know what this is please consider reading the TOR project's info on bridges
  1259. Basically we are using TOR-relays which are not publicly known and on top of that we use a tool to hide our TOR-traffic and change the packets to look like XMPP-protocol.
  1261. Why does this suck? It sucks because this service is actually meant for people in real disaster-zones, like China, Iran and other messed up places. This means, that everytime we connect to TOR using this technique we steal bandwidth from those who really need it. Of course this only applies if you live somewhere in the Western world. But we don't really know what information various agencies and who-knows-who collect and how this info will be used if, say, our democratic foundations crumble. You could view this approach as being proactive in the West whereas it is necessary and reactive in the more unfortunate places around the world.
  1263. But, there is of course something we can do about this: first of all only use TOR when you have to. You don't need TOR for funny cat videos on youtube. Also it is good to have some regular traffic coming from your network and not only XMPP - for obvious reasons. So limit your TOR-use for when it is necessary.
  1265. The other thing you/we can do is set up our own bridges/relays and contribute to the network. Then we can stream the DuckTales the whole darn day using obfuscated bridges without bad feelings... wink
  1267. How to set up a TOR-connection over obfuscated bridges?
  1269. Simple: Go to -> The Tor project's special obfsproxy page and download the appropriate pre-configured Tor-Browser-Bundle. wink
  1271. Extract and run. (Though never as root!)
  1273. If you want to use the uber-secure webbrowser we configured above simply go to the TOR-Browsers settings and check the port it uses for proxying. (This will be a different port every time you start the TOR-Bundle.)
  1275. Then go into your browser and set up your proxy accordingly. Close the TOR-Browser and have phun! - But don't forget to: check if you're really connected to the network.
  1277. To make this process of switching proxies even more easy you can use the FireFox-addon: FoxyProxy. This will come in handy if you use a regular connection, TOR and I2P all through the same browser.
  1279. Tipp: While online with TOR using google can be quite impossible due to google blocking TOR-exit-nodes - but with a little help from HideMyAss! we can fix this problem. Simply use the HideMyAss! web interface to browse to google and do your searchin'. You could also use search engines like ixquick, duckduckgo etc. - but if you are up for some serious google hacking - only google will do... wink [Apparently there exists an alternative to the previously shut-down scroogle: privatelee which seems to support more sophisticated google search queries. I just tested it briefly after digging it up here. So you need to experiment with it.]
  1281. But remember that in case you do something that attracts the attention of some three-letter-organization HideMyAss! will give away the details of your connection. So, only use it in combination with TOR - and: don't do anything that attracts that kind of attention to begin with.
  1283. Warning: Using Flash whilst using TOR can reveal your real IP-Address. Bear this in mind! Also, double-check to have network.websocket.enabled set to false in your about:config! -> more info on that one here.
  1285. Another general thing about TOR: If you are really concerned about your anonymity you should never use anonymized services along non-anonymized services. (Example: Don't post on "frickkkin'-anon-ops-forum.anon" while browsing to your webmail "")
  1287. And BTW: For those who didn't know it - there are also the TOR hidden services...
  1289. One note of caution: When dealing with darknets such as TOR's hidden services, I2P and Freenet please be aware that there is some really nasty stuff going on there. In fact in some obscure place on these nets everything you can and can't imagine is taking place. This is basically a side-effect of these infrastructure's intended function: to facilitate an uncensored access to various online-services from consuming to presenting content. The projects maintaining these nets try their best to keep that kind of stuff off of the "official" search engines and indexes - but that basically is all that can be done. When everyone is anonymous - even criminals and you-name-it are.
  1291. What has been seen...
  1293. To avoid that kind of exposure and thus keep your consciousness from being polluted with other people's sickness please be careful when navigating through these nets. Only use search-engines, indexes and trackers maintained by trusted individuals. Also, if you download anything from there make sure to triple check it with ClamAV. Don't open even one PDF-file from there without checking.
  1295. To check pdf-files for malicious code you can use wepawet. Or if you are interested in vivisecting the thing have a look at Didier Steven's PDFTools or PeePDF.
  1297. Change the file-ownership to a user with restricted access (i.e. not root) and set all the permissions to read only. Even better: only use such files in a virtual machine. The weirdest code thrives on the darknets... wink I don't want to scare you away: These nets generally are a really cool place to hang out and when you exercise some common sense you shouldn't get into trouble.
  1299. [Another short notice to the Germans: Don't try to hand over stuff you may find there to the authorities, download or even make screenshots of it. This could get you into serious trouble. Sad but true. For more info watch this short vid.]
  1300. TOR-Warning
  1302. The above mentioned issues unfortunately aren't the only ones. I have come across more and more reasons not to use TOR:
  1304. - When using TOR you use about five times your normal bandwidth - which makes you stick out for your ISP - even with obfuscate bridges in use.
  1306. - TOR-nodes (!) and TOR-exit-nodes can be and are being used to deploy malicious code and to track and spy on users.
  1308. - There are various methods of de-anonymizing TOR-users: from DNS-leaks over browser-info-analysis to traffic-fingerprinting.
  1310. I won't explain all these issues in detail but if you are interested in finding out why TOR isn't safe to use (and you should if you actually think that TOR is making you anonymous) I recommend you watch these talks:
  1312. Attacking TOR at the Application-Layer
  1313. De-TOR-iorate Anonymity
  1314. Taking Control over the Tor Network
  1315. Dynamic Cryptographic Backdoors to take over the TOR Network
  1316. Security and Anonymity vulnerabilities in Tor
  1317. Anonymous Internet Communication done Right (I disagree with the speaker on Proxies, though. See info on proxies below.)
  1318. Owning Bad Guys and Mafia with Java-Script Botnets
  1320. And if you want to see how TOR-Exit-Node sniffing is done live you can have a look at this:
  1321. Tor: Exploiting the Weakest Link
  1323. To make something clear: I have nothing against the TOR-project. In fact I like it really much. But TOR is simply not yet able to cash in the promises it makes. Maybe in a few years time it will be able to defend against a lot of the issues that have been raised and illustrated. But until then I can't safely recommend using it to anybody. Sorry to disappoint you.
  1324. I2P
  1326. I2P is a so-called darknet. It functions differently from TOR and is considered to be way more secure. It uses a much better encryption and is generally faster. You can theoretically use it to browse the web - but it is generally not advised and even slower as TOR using it for this purpose. I2P has some cool sites to visit, an anonymous email-service and a built-in anonymous torrent-client. wink
  1328. For I2P to run on your system you need Open-JDK/JRE since I2P is a java-application. To install:
  1330. Go to-> The I2P's website download, verify the SHA256 and install:
  1332. $ cd /directory/you/downloaded/the/file/to && java -jar i2pinstall_0.9.4.jar
  1334. Don't install as root - and even more important: Never run as root!
  1336. To start: $ cd /yourI2P/folder ./i2prouter start
  1337. To stop: $ cd /yourI2P/folder ./i2prouter stop
  1339. Once running you will be directed to your Router-Console in FireFox. From there you have various options. You should consider to give I2P more bandwidth than default for a faster and more anonymous browsing experience.
  1341. The necessary browser configuration can be found here.
  1343. For further info go to the project's website.
  1344. Freenet
  1346. A darknet I have not yet tested myself, since I only use TOR and I2P is Freenet. I heard that it is not that populated and that it is mainly used for filesharing. A lot of nasty stuff also seems to be going on on Freenet - but this is only what I heard and read about it. The nasty stuff issue of course is also true for TOR's hidden services and I2P. But since I haven't been on it yet I can't say anything about that. Maybe another user who knows Freenet better can add her/his review.
  1348. Anyhow...:
  1350. You get the required software here.
  1352. If you want to find out how to use it - consult their helpsite.
  1353. Secure Peer-to-Peer-Networks
  1355. GNUnet
  1357. RetroShare
  1358. Mesh-Networks
  1360. If you're asking yourself what mesh-networks are take a look at this short video.
  1364. Netsukuku Community
  1366. OpenWireless
  1368. Commotion
  1370. FabFi
  1372. Mesh Networks Research Group
  1374. Byzantium live Linux distro for mesh networking
  1376. (Thanks to cyberhood!)
  1377. Proxies
  1379. I have not yet written anything about proxy-servers. In short: Don't ever use them.
  1381. There is a long and a short explanation. The short one can be summarized as follows:
  1383. - Proxy-servers often sent xheaders containing your actual IP-address. The service you are then communication to will receive a header looking like this:
  1385. X-Forwarded-For: client, proxy1, proxy2
  1387. This will tell the server you are connecting to that you are connecting to him via a proxy which is fetching data on behalf of... you!
  1389. - Proxy servers are infested with malware - which will turn your machine into a zombie within a botnet - snooping out all your critical login data for email, banks and you name it.
  1391. - Proxy servers can read - and modify - all your traffic. When skilled enough sometimes even circumventing SSL.
  1393. - Proxy servers can track you.
  1395. - Most proxy servers are run by either criminals or intelligence agencies.
  1397. Seriously. I really recommend watching this (very entertaining) Defcon-talk dealing with this topic. To see how easy e.g. java-script-injections can be done have a look at beef.
  1398. VPN (Virtual Private Network)
  1400. You probably have read the sections on TOR and proxy-servers (do it now - if you haven't) and now you are asking yourself: "&*%$!, what can I use to browse the web safely and anonymously????"
  1402. Well, there is a pretty simple solution. But it will cost you a few nickels. You have to buy a premium-VPN-service with a trustworthy VPN-provider.
  1404. If you don't know what a VPN is or how it works - check out this video.
  1406. Still not convinced? Then read what lifehacker has to say about it.
  1408. Once you've decided that you actually want to use a VPN you need to find a trustworthy provider. Go here to get started with that.
  1410. Only use services that offer OpenVPN. Basically all the other protocols aren't that secure. Or at least they can't compare to OpenVPN.
  1412. Choose the most trustworthy service you find out there and be paranoid about it.
  1414. A trustworthy service doesn't keep logs. If you choose a VPN, read the complete FAQ, their Privacy Policy and the Terms of Service. Check where they're located and check local privacy laws. And: Don't tell people on the internet which service you are using.
  1416. You can get yourself a second VPN account with a different provider you access through a VM. That way VPN#1 only knows your IP-address but not the content of your communication and VPN#2 knows the content but not your IP-address.
  1418. Don't try to use a free VPN. Remember: If you're not paing for it - you are the product.
  1419. The Web
  1421. If for some unimaginable reason you want to use the "real" internet wink - you now are equipped with a configuration which will hopefully make this a much more secure endeavour. But still: Browsing the internet and downloading stuff is the greatest vulnerability to a linux-machine. So use some common sense. wink
  1422. RSS-Feeds
  1424. Please be aware that using RSS-feeds can be used to track you and the information-sources you are using. Often RSS-feeds are managed through 3rd-party providers and not the by the original service you are using.
  1426. Web-bugs are commonly used in RSS-tracking. Also your IP-address and other available browser-info will be recorded.
  1428. Even when you use a text-based desktop-feedreader such as newsbeuter - which mitigates tracking though web-bugs and redirects - you still leave your IP-address.
  1430. To circumvent that you would want to use a VPN or TOR when fetching your RSS-updates.
  1432. If you want to learn more about RSS-tracking read this article.
  1433. Secure Mail-Providers:
  1435. Please consider using a secure email-provider and encourage your friends and contacts to do the same. All your anonymization is worthless when you communicate confidential information in an unencrypted way with someone who is using gmx, gmail or any other crappy provider. (This also applies if you're contemplating setting up your own mail-server.)
  1437. If possible, encrypt everything, but especially confidential stuff, using gpg/enigmail.
  1439. [SSL, SMTP, POP]
  1440. [SSL, SMTP, no POP/IMAP - only in commercial upgrade]
  1441. [SSL, SMTP, POP]
  1443. I found these to be the best. But I may have missed others in the process.
  1444. Hushmail also has the nice feature to encrypt "inhouse"-mails, i.e. mail sent from one hushmail-account to another. So, no need for gpg or other fancy stuff. wink
  1446. The user cyberhood mentioned these mail-providers in the other #! thread on security.
  1448. [SSL, SMTP, IMAP, POP]
  1450. Looks alright. Maybe someone has tested it already?
  1452. [SSL, SMTP, IMAP, POP]
  1454. Although I generally don't trust services that can not present themselves without typos and grammatical errors - I give them
  1455. the benefit of the doubt for they obviously are French. roll Well, you know how the French deal with foreign languages... tongue
  1457. [SSL, SMTP, IMAP, POP]
  1459. See this Review
  1463. You need to prove that you are some kind of activist-type to get an account with them. So I didn't bother to check out their security. This is how they present themselves:
  1464. Riseup wrote:
  1466. The Riseup Collective is an autonomous body based in Seattle with collective members world wide. Our purpose is to aid in the creation of a free society, a world with freedom from want and freedom of expression, a world without oppression or hierarchy, where power is shared equally. We do this by providing communication and computer resources to allies engaged in struggles against capitalism and other forms of oppression.
  1468. Edit: I changed my mind and will not comment on Riseup. It will have its use for some people and as this is a technical manual I edited out my political criticism to keep it that way.
  1469. Disposable Mail-Addresses
  1471. Sometimes you need to register for a service and don't want to hand out your real mail-address. Setting up a new one also is a nuisance. That's where disposable mail-addresses come in. There is a firefox-addon named Bloody Vikings that automatically generates them for you. If you rather want to do that manually you can use some of these providers:
  1473. anonbox
  1474. anonymouse/anonemail
  1475. trash-mail
  1476. 10 Minute Mail
  1477. dispostable
  1478. SilentSender
  1479. Mailinator
  1481. It happens that websites don't allow you to register with certain disposable mail-addresses. In that case you need to test out different ones. I have not yet encountered a site where I could not use one of the many one-time-address out there...
  1482. Secure Instant-Messaging/VoIP
  1484. Using Skype is not advised from a security standpoint. Although Skype communication is encrypted there are a few ways to attack it. Also, you probably don't want to trust Skype to keep all your data safe, do you?
  1486. Instead you can use:
  1487. TorChat
  1489. To install:
  1491. $ sudo apt-get install torchat
  1493. TorChat is generally considered to be really safe - employing end-to-end encryption via the TOR network. It is both anonymous and encrypted.
  1495. Obviously you need TOR for it to function properly.
  1497. Here you find instructions on how to use it.
  1498. OTR [Off-the-Record Messaging]
  1500. OTR is also very secure. Afaik it is encrypted though not anonymous.
  1502. Clients with native OTR support:
  1504. Jitsi
  1505. Climm
  1507. Clients with OTR support through Plugins:
  1509. Pidgin
  1510. Kopete
  1512. XMPP generally supports OTR.
  1514. Here you find a tutorial on how to use OTR with Pidgin.
  1515. Secure and Encrypted VoIP
  1517. As mentioned before - using Skype is not advised. There is a much better solution:
  1519. Jitsi
  1521. Jitsi is a chat/VoIP-client that can be used with different services, most importantly with XMPP. Jitsi doesn't just offer chat, chat with OTR, VoIP-calls over XMPP, VoIP-video-calls via XMPP - but also the ZRTP-protocol, which was developed by the developer of PGP, Phil Zimmerman.
  1523. ZRTP allows you to make fully end-to-end encrypted video-calls. Ain't that sweet? wink
  1525. If you want to know how that technology works, check out these talks by Phil Zimmerman at Defcon. [Defcon 15 | Defcon 16]
  1527. Setting up Jitsi is pretty straightforward.
  1529. Here is a very nice video-tutorial on how get started with Jitsi.
  1530. Social Networking
  1531. Facebook
  1533. Although I actually don't think I need to add this here - I suspect other people coming to this forum from google might need to consider this: Don't use Facebook!
  1535. Apart from security issues, malware and viruses Facebook itself collects every bit of data you hand out: to store it, to sell it, to give it to the authorities. And if that's still not enough for you to cut that crap you might want to watch this video.
  1537. And no: Not using your real name on Facebook isn't helping you anything. Who are your friends on Facebook? Do you always use an IP-anonymization-service to login to Facebook? From where do you login to Facebook? Do you accept cookies? LSO-cookies? Do you use SSL to connect to Facebook? To whom are you writing messages on Facebook? What do you write there? Which favorite [movies | books | bands | places | brands]-lists did you provide to Facebook which only need to be synced with google-, youtube-, and amazon-searches to match your profile? Don't you think such a massive entity as Facebook is able to connect the dots? You might want to check out this vid to find out how much Facebook actually does know about you. Still not convinced? [Those who understand German might want to hear what the head of the German Police Union (GDP), Bernhard Witthaut, says about Facebook on National TV...]
  1539. For all of you who still need more proof regarding the dangers of Facebook and mainstream social media in general - there is a defcon-presentation which I urge you to watch. Seriously. Watch it.
  1541. Well, and then there's of course Wikipedia's collection of criticism of Facebook. I mean, come on.
  1542. Alternatives to Facebook
  1544. Friendica is an alternative to Facebook recommended by the Free Software Foundation
  1546. Lorea seems a bit esoteric to me. Honestly, I haven't wrapped my head around it yet. Check out their description:
  1547. Lorea wrote:
  1549. Lorea is a project to create secure social cybernetic systems, in which a network of humans will become simultaneously represented on a virtual shared world.
  1551. Its aim is to create a distributed and federated nodal organization of entities with no geophysical territory, interlacing their multiple relationships through binary codes and languages.
  1553. Diaspora - but there are some doubts - or I'd better say: questions regarding diasporas security.
  1555. But it is certainly a better choice than Facebook.
  1557. One last thing:
  1558. Passwords
  1560. Always make sure to use good passwords.
  1562. To generate secure passwords you can use:
  1563. pwgen
  1565. Installation:
  1567. $ sudo apt-get install pwgen
  1569. Usage:
  1571. pwgen [ OPTIONS ] [ pw_length ] [ num_pw ]
  1573. Options supported by pwgen:
  1574. -c or --capitalize
  1575. Include at least one capital letter in the password
  1576. -A or --no-capitalize
  1577. Don't include capital letters in the password
  1578. -n or --numerals
  1579. Include at least one number in the password
  1580. -0 or --no-numerals
  1581. Don't include numbers in the password
  1582. -y or --symbols
  1583. Include at least one special symbol in the password
  1584. -s or --secure
  1585. Generate completely random passwords
  1586. -B or --ambiguous
  1587. Don't include ambiguous characters in the password
  1588. -h or --help
  1589. Print a help message
  1590. -H or --sha1=path/to/file[#seed]
  1591. Use sha1 hash of given file as a (not so) random generator
  1592. -C
  1593. Print the generated passwords in columns
  1594. -1
  1595. Don't print the generated passwords in columns
  1596. -v or --no-vowels
  1597. Do not use any vowels so as to avoid accidental nasty words
  1599. Example:
  1601. $ pwgen 24 -y
  1603. Pwgen will now give you a list of password with 24 digits using at least one special character.
  1605. To test the strength of your passwords I recommend using Passfault. But: Since Passfaults' symmetric cypher is rather weak I advise not to use your real password. It is better to substitute each character by another similar one. So you can test the strength of the password without
  1606. transmitting it in an insecure way over the internet.
  1608. If you have reason to assume that the machine you are using is compromised and has a keylogger installed you should generally only use virtual keyboards to submit critical data. They are built in to every OS afaik.
  1610. Another thing you can do is use:
  1611. KeePass
  1613. KeePass stores all kinds of password in an AES/Twofish encrypted database and is thus highly secure and a convenient way to manage your passwords.
  1615. To install:
  1617. $ sudo apt-get install keepass2
  1619. A guide on how to use it can be found here.
  1620. Live-CDs and VM-Images that focus on security and anonymity
  1622. Tails Linux The classic. Debian-based.
  1624. Liberté Linux Similar to Tails. Gentoo-based.
  1626. Privatix Live-System Debian-based.
  1628. Tinhat Gentoo-based.
  1630. Pentoo Gentoo-based. Hardened kernel.
  1632. Janus VM - forces all network traffic through TOR
  1635. Further Info/Tools:
  1637. TOR
  1638. I2P
  1639. Securing Debian Manual
  1640. Electronic Frontier Foundation
  1641. EFF's Surveillance Self-Defense Guide
  1642. Schneier on Security
  1643. Irongeek
  1644. SpywareWarrior
  1645. SecurityFocus
  1646. Wilders Security Forums
  1648. CCC [en]
  1649. Eli the Computer Guy on Security
  1650. Digital Anti-Repression Workshop
  1651. The Hacker News
  1652. Anonymous on the Internets!
  1653. #! Privacy and Security Thread [Attention: There are some dubious addons listed! See my post there for further info.]
  1654. EFF's Panopticlick
  1655. GRC
  1656. Rapid7 UPnP Vulnerability Scan
  1657. HideMyAss! Web interface
  1658. Browserspy
  1660. IP Lookup
  1661. BrowserLeaks
  1662. Whoer
  1663. evercookie
  1664. Sophos Virus DB
  1665. f-secure Virus DB
  1666. Offensive Security Exploit DB
  1667. Passfault
  1668. PwdHash
  1669. Qualys SSL Server Test
  1670. MyShadow
  1671. Security-in-a-Box
  1672. Calyx Institute
  1673. CryptoParty
  1674. Self-D0xing
  1675. Wepawet
  1676. German only:
  1678. awxcnx
  1679. anondat
  1680. SemperVideo
  1681. SemperVideo [youtube]
  1682. Fefes Blog
  1683. heise
  1684. golem
  1685. CCC [de]
  1686. FoeBud
  1687. German Privacy Foundation
  1688. Postscript:
  1690. If you find any error in this guide please don't hesitate to reply with an explanation. Also, if you have anything to add please also use the reply function. Since this is my first "real" post on the #! forums I don't know how long the edit-function is available for regular posts. Should it be usable indefinitely I will edit this original post to include all the additional information you will provide. This way we keep all the required info in one place. Thanks!
  1692. ...and keep sorcering!
  1694. [Edit: Apparently I can edit the hell out of this post. wink So I will be constantly updating this guide in the future. I already scrambled together all the info I found noteworthy from the #! Privacy and Security Thread. So you should in theory find everything you need from there in this manual, too. But you know how personal opinions differ. So please raise your hand if you find I missed something.
  1696. I will also work on migrating this guide into the #!-wiki in the future.]
Add Comment
Please, Sign In to add comment