Update URLs (->gitlab.com).

The code.google is going to be abandoned.
Thank you you for all the fish.

FAQ

@@ -23,7 +23,7 @@ A. Contributors
   with one master key, anti-forensic features, metadata block at
   start of device, ...). The latest version of this FAQ should
   usually be available at
-  http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions
+  https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions
 
 
  * 1.2 WARNINGS
@@ -173,7 +173,7 @@ A. Contributors
 
  * 1.6 Where is the project website?
 
-  There is the project website at http://code.google.com/p/cryptsetup/
+  There is the project website at https://gitlab.com/cryptsetup/cryptsetup/
   Please do not post questions there, nobody will read them. Use
   the mailing-list instead.
 
@@ -1993,7 +1993,7 @@ A. Contributors
   process, except generating a new LUKS header with the old master
   key (it prints the command for that though):
 
-http://code.google.com/p/cryptsetup/source/browse/misc/luks-header-from-active
+  https://gitlab.com/cryptsetup/cryptsetup/blob/master/misc/luks-header-from-active
 
   You can also do this manually. Here is how:
 
@@ -2091,7 +2091,7 @@ http://code.google.com/p/cryptsetup/source/browse/misc/luks-header-from-active
   bulk data at 0x200000.
 
   The exact specification of the format is here:
-  http://code.google.com/p/cryptsetup/wiki/Specification
+  https://gitlab.com/cryptsetup/cryptsetup/wikis/Specification
 
   For your convenience, here is the LUKS header with hex offsets.
   NOTE: The spec counts key-slots from 1 to 8, but the cryptsetup
@@ -2458,8 +2458,7 @@ offset  length  name                  data type  description
  * Specifications
 
   - LUKS on-disk format spec:
-  http://code.google.com/p/cryptsetup/wiki/Specification
-
+  https://gitlab.com/cryptsetup/cryptsetup/wikis/Specification
 
  * Code Examples