[Bug 1746038] Re: Set all of cipher, hash and size for the plain dm-crypt mapping cryptswap1 in /etc/crypttab.

dino99 1746038 at bugs.launchpad.net
Mon Jan 29 16:54:21 UTC 2018 

** Description changed:

  Upgrading output:
  
  Setting up libcryptsetup12:amd64 (2:2.0.1-0ubuntu1) ...
  Setting up cryptsetup-bin (2:2.0.1-0ubuntu1) ...
  Setting up cryptsetup (2:2.0.1-0ubuntu1) ...
  Installing new version of config file /etc/init.d/cryptdisks-early ...
  update-initramfs: deferring update (trigger activated)
  WARNING: you need to set all of cipher, hash and size for the plain dm-crypt mapping cryptswap1 in /etc/crypttab.
  
- That seems more critical than a simple warning; how do a user can set
- these techy settings ?
+ That seems more critical than a simple warning; how do a user can set these techy settings ?
+ http://manpages.ubuntu.com/manpages/bionic/man5/crypttab.5.html 
+ Should be set by the installer for a OutOfTheBox experience.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cryptsetup 2:2.0.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jan 29 17:43:18 2018
  EcryptfsInUse: Yes
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=<set>
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=<set>
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-30-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro

** Description changed:

  Upgrading output:
  
  Setting up libcryptsetup12:amd64 (2:2.0.1-0ubuntu1) ...
  Setting up cryptsetup-bin (2:2.0.1-0ubuntu1) ...
  Setting up cryptsetup (2:2.0.1-0ubuntu1) ...
  Installing new version of config file /etc/init.d/cryptdisks-early ...
  update-initramfs: deferring update (trigger activated)
  WARNING: you need to set all of cipher, hash and size for the plain dm-crypt mapping cryptswap1 in /etc/crypttab.
  
  That seems more critical than a simple warning; how do a user can set these techy settings ?
- http://manpages.ubuntu.com/manpages/bionic/man5/crypttab.5.html 
- Should be set by the installer for a OutOfTheBox experience.
+ http://manpages.ubuntu.com/manpages/bionic/man5/crypttab.5.html
+ Should be set by the installer for an OutOfTheBox experience.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cryptsetup 2:2.0.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jan 29 17:43:18 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-30-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro

** Description changed:

  Upgrading output:
  
  Setting up libcryptsetup12:amd64 (2:2.0.1-0ubuntu1) ...
  Setting up cryptsetup-bin (2:2.0.1-0ubuntu1) ...
  Setting up cryptsetup (2:2.0.1-0ubuntu1) ...
  Installing new version of config file /etc/init.d/cryptdisks-early ...
  update-initramfs: deferring update (trigger activated)
  WARNING: you need to set all of cipher, hash and size for the plain dm-crypt mapping cryptswap1 in /etc/crypttab.
  
  That seems more critical than a simple warning; how do a user can set these techy settings ?
  http://manpages.ubuntu.com/manpages/bionic/man5/crypttab.5.html
  Should be set by the installer for an OutOfTheBox experience.
+ https://superuser.com/questions/775200/how-do-i-determine-what-ciphers-cipher-modes-i-can-use-in-dm-crypt-luks
+ Really not for the average user.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cryptsetup 2:2.0.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jan 29 17:43:18 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-30-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro

** Description changed:

  Upgrading output:
  
  Setting up libcryptsetup12:amd64 (2:2.0.1-0ubuntu1) ...
  Setting up cryptsetup-bin (2:2.0.1-0ubuntu1) ...
  Setting up cryptsetup (2:2.0.1-0ubuntu1) ...
  Installing new version of config file /etc/init.d/cryptdisks-early ...
  update-initramfs: deferring update (trigger activated)
  WARNING: you need to set all of cipher, hash and size for the plain dm-crypt mapping cryptswap1 in /etc/crypttab.
  
  That seems more critical than a simple warning; how do a user can set these techy settings ?
  http://manpages.ubuntu.com/manpages/bionic/man5/crypttab.5.html
  Should be set by the installer for an OutOfTheBox experience.
  https://superuser.com/questions/775200/how-do-i-determine-what-ciphers-cipher-modes-i-can-use-in-dm-crypt-luks
- Really not for the average user.
+ Really not for the averaged user.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cryptsetup 2:2.0.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jan 29 17:43:18 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-30-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/1746038

Title:
  Set all of cipher, hash and size for the plain dm-crypt mapping
  cryptswap1 in /etc/crypttab.

Status in cryptsetup package in Ubuntu:
  New

Bug description:
  Upgrading output:

  Setting up libcryptsetup12:amd64 (2:2.0.1-0ubuntu1) ...
  Setting up cryptsetup-bin (2:2.0.1-0ubuntu1) ...
  Setting up cryptsetup (2:2.0.1-0ubuntu1) ...
  Installing new version of config file /etc/init.d/cryptdisks-early ...
  update-initramfs: deferring update (trigger activated)
  WARNING: you need to set all of cipher, hash and size for the plain dm-crypt mapping cryptswap1 in /etc/crypttab.

  That seems more critical than a simple warning; how do a user can set these techy settings ?
  http://manpages.ubuntu.com/manpages/bionic/man5/crypttab.5.html
  Should be set by the installer for an OutOfTheBox experience.
  https://superuser.com/questions/775200/how-do-i-determine-what-ciphers-cipher-modes-i-can-use-in-dm-crypt-luks
  Really not for the averaged user.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cryptsetup 2:2.0.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jan 29 17:43:18 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-30-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1746038/+subscriptions

More information about the foundations-bugs mailing list