use HTTPS for URLs

FAQ

@@ -112,7 +112,7 @@ A. Contributors
   characters may have different encoding depending on system configuration
   and your passphrase will not work with a different encoding.  A table of
   the standardized first 128 ASCII characters can, e.g.  be found on
-  http://en.wikipedia.org/wiki/ASCII
+  https://en.wikipedia.org/wiki/ASCII
 
   KEYBOARD NUM-PAD: Apparently some pre-boot authentication environments
   (these are done by the distro, not by cryptsetup, so complain there)
@@ -173,7 +173,7 @@ A. Contributors
   which means distribution is unlimited, you may create derived works, but
   attributions to original authors and this license statement must be
   retained and the derived work must be under the same license.  See
-  http://creativecommons.org/licenses/by-sa/3.0/ for more details of the
+  https://creativecommons.org/licenses/by-sa/3.0/ for more details of the
   license.
 
   Side note: I did text license research some time ago and I think this
@@ -268,7 +268,7 @@ A. Contributors
 
   This can take a while.  To get a progress indicator, you can use the
   tool dd_rescue (->google) instead or use my stream meter "wcs" (source
-  here: http://www.tansi.org/tools/index.html) in the following fashion:
+  here: https://www.tansi.org/tools/index.html) in the following fashion:
 
     cat /dev/zero | wcs > <target device>
 
@@ -677,7 +677,7 @@ A. Contributors
   A bit more information on the process by which transactional guarantees
   are implemented can be found here:
 
-  http://lwn.net/Articles/400541/
+  https://lwn.net/Articles/400541/
 
   Please note that these "guarantees" are weaker than they appear to be. 
   One problem is that quite a few disks lie to the OS about having flushed
@@ -811,7 +811,7 @@ A. Contributors
     dd_rescue -w /dev/zero /dev/mapper/to_be_wiped
 
   Progress-indicator by my "wcs" stream meter (available from
-  http://www.tansi.org/tools/index.html ):
+  https://www.tansi.org/tools/index.html ):
 
     cat /dev/zero | wcs > /dev/mapper/to_be_wiped
 
@@ -1271,7 +1271,7 @@ A. Contributors
   single overwrite could be enough.  If in doubt, use physical destruction
   in addition.  Here is a link to some current research results on erasing
   SSDs and FLASH drives:
-  http://www.usenix.org/events/fast11/tech/full_papers/Wei.pdf
+  https://www.usenix.org/events/fast11/tech/full_papers/Wei.pdf
 
   Keep in mind to also erase all backups.
 
@@ -1701,8 +1701,9 @@ A. Contributors
   can demand encryption keys.
 
   Here is an additional reference for some problems with plausible
-  deniability: http://www.schneier.com/paper-truecrypt-dfs.pdf I strongly
-  suggest you read it.
+  deniability:
+  https://www.schneier.com/academic/paperfiles/paper-truecrypt-dfs.pdf
+  I strongly suggest you read it.
 
   So, no, I will not provide any instructions on how to do it with plain
   dm-crypt or LUKS.  If you insist on shooting yourself in the foot, you
@@ -2994,7 +2995,7 @@ offset  length  name                  data type  description
 
   - http://news.electricalchemy.net/2009/10/password-cracking-in-cloud-part-5.html
 
-  - http://it.slashdot.org/story/12/12/05/0623215/new-25-gpu-monster-devours-strong-passwords-in-minutes
+  - https://it.slashdot.org/story/12/12/05/0623215/new-25-gpu-monster-devours-strong-passwords-in-minutes
 
   * Tools