** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804408
Title:
[19.04 FEAT] LUKS2 support for pam_mount
To manage
This bug was fixed in the package libpam-mount - 2.16-3ubuntu0.1
---
libpam-mount (2.16-3ubuntu0.1) bionic; urgency=medium
* d/p/0015-Use-crypt_get_type-to-get-type-and-support-CRYPT_LUK.patch:
allow more than just LUKS1 by detecting the type (LP: #1804408)
* d/tests/control,
Test executed fine on the SRU from proposed:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/libp/libpam-mount/20190225_143346_e53d2@/log.gz
The same for all architectures.
And since the test also covers LUKS1 and LUKS2
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804408
Title:
[19.04 FEAT] LUKS2 support for pam_mount
To manage
Hello bugproxy, or anyone else affected,
Accepted libpam-mount into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/libpam-
mount/2.16-3ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
This bug was fixed in the package libpam-mount - 2.16-5ubuntu0.1
---
libpam-mount (2.16-5ubuntu0.1) cosmic; urgency=medium
* d/p/0015-Use-crypt_get_type-to-get-type-and-support-CRYPT_LUK.patch:
allow more than just LUKS1 by detecting the type (LP: #1804408)
* d/tests/control,
Before the update afte rlogin as described in the test steps:
$ ssh alice@localhost
# mount | grep luks
/dev/mapper/_dev_vdc1 on /home/alice/luks1 type ext4 (rw,relatime,helper=crypt)
Upgrading from proposed
ubuntu@cosmic-luks:~$ sudo apt install libpam-mount
Reading package lists... Done
Hi ifranzki, the test you did was the sanity check on my PPA before bringing it
to the eyes of the SRU Team. The one that was called for in comment #16 is now
"the real thing" available in cosmic-proposed and binaries that would be
released.
They are >=99,9% identical, but to be sure a test
FYI - before you go testing this - the builders currently have some issues.
So while the source is in -proposed the package isn't fully built yet.
Be sure when testing to actually have the new code in place.
TL;DR - probably better wait one day to start testing
--
You received this bug
Hello bugproxy, or anyone else affected,
Accepted libpam-mount into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/libpam-
mount/2.16-5ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
I did one more successful test on bionic and LUKS2.
Thanks for the other tests and results results.
I just change the status now to In Progress...
** Changed in: libpam-mount (Ubuntu Cosmic)
Status: Incomplete => In Progress
** Changed in: libpam-mount (Ubuntu Bionic)
Status:
Uploaded to the SRU queue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804408
Title:
[19.04 FEAT] LUKS2 support for pam_mount
To manage notifications about this bug go to:
Thanks ifranzki,
I also added automated tests to the packages on the SRU as well as in Debian
[1].
Test results look good atm and will give the whole thing some more confidence:
Cosmic with fix: http://paste.ubuntu.com/p/nfwBTqBdP9/
Cosmic without: http://paste.ubuntu.com/p/2rzYZJ3RYJ/
Bionic
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libpam-mount/+git/libpam-mount/+merge/362810
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libpam-mount/+git/libpam-mount/+merge/362811
--
You received this bug notification
What I documented in the test steps is clear-key approach as it is what
will work on all platforms.
@ifranzki - could you test the PPA [1] against your setup ?
@jfh - could you test the PPA [1] using a secure key in your setup ?
Once those two are confirmed for the PPA we can upload for review
Waiting for tests by jfh and ifranzki - setting incomplete until I get
those confirmed.
** Changed in: libpam-mount (Ubuntu Bionic)
Status: In Progress => Incomplete
** Changed in: libpam-mount (Ubuntu Cosmic)
Status: In Progress => Incomplete
--
You received this bug
PPA with the builds is available at [1].
Test steps added to the SRU template and tested against:
- disco ok
- cosmic fail
- bionic fail
- cosmic + ppa ok
- bionic + ppa ok
[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3635
** Changed in: libpam-mount (Ubuntu Cosmic)
** Description changed:
+ [Impact]
+
+ * Cryptsetup 2.0 with LUKS2 support was already released back in 2017,
+but plugins exploiting it came sluggish.
+A popular way to automatically make use of LUKS2 (of course while still
+retaining support for LUKS1) is via the pluggable
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804408
Title:
[19.04 FEAT] LUKS2 support for pam_mount
To manage notifications about this bug go to:
Hi Ingo,
we are sorting out the needs for an SRU of this - until I have discussed with
the Team (all others still asleep :-) ) I wanted to ask if you had a test setup
for LUKS1/LUKS2 available that you used to write your patch. If so we could
reuse that for the verifications of PPAs and the
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Server Team (canonical-server)
** Changed in: ubuntu-z-systems
Status: In Progress => Triaged
** Changed in: ubuntu-z-systems
Importance: Undecided => High
--
You received this bug notification because you are a
libpam-mount 2.16-9ubuntu1 is now in disco (release).
** Changed in: libpam-mount (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804408
** Changed in: ubuntu-z-systems
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804408
Title:
[19.04 FEAT] LUKS2 support for pam_mount
To manage
It's not even my patch =) just something that was done by maintainers in
Debian = so obfuscating++
** Also affects: libpam-mount (Ubuntu Disco)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: Fix Committed
** Also affects: libpam-mount
24 matches
Mail list logo
