Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #231995 > unrolled thread
| Started by | Marco Möller <talby@debianlists.mobilxpress.net> |
|---|---|
| First post | 2021-02-23 22:40 +0100 |
| Last post | 2021-02-23 23:10 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.user
authentication bug (or feature?) with multiple encrypted lvm2 volume groups Marco Möller <talby@debianlists.mobilxpress.net> - 2021-02-23 22:40 +0100
Re: authentication bug (or feature?) with multiple encrypted lvm2 volume groups Charles Curley <charlescurley@charlescurley.com> - 2021-02-23 23:10 +0100
| From | Marco Möller <talby@debianlists.mobilxpress.net> |
|---|---|
| Date | 2021-02-23 22:40 +0100 |
| Subject | authentication bug (or feature?) with multiple encrypted lvm2 volume groups |
| Message-ID | <BLNzs-69V-5@gated-at.bofh.it> |
Two volume groups (lvm2) exists, Each of them is encrypted and thus protected by its own password. Lets call the volume groups and their corresponding passwords like this: VG password "A" "pwA" "B" "pwB" "pwA" and "pwB" differ from each other. Step 1: during boot I am asked for the password of "A" Step 2: by accident I enter "pwB" Step 3: consequently an error message is shown and "A" is not opened Step 4: I am asked again for the password of "A" Step 5: I now enter correctly "pwA" Step 6: "A" is opened Step 7: "B" is immediately opened without asking for its password I confirmed, that the opening of "B" does only take place, when having entered in Step 2 the "pwB". If I enter in Step 2 something else, then in Step 7 it is asked for the password of "B", I would enter it in a Step 8 correctly and consequently in a Step 9 the "B" would be opened. Obviously, the in Step 2 entered (wrong) password (for "A") is stored and without further interactive consultation automatically used as the input for the password authentication of "B". Is this a bug or a feature? If it is a bug, where to report it? Thanks in advance for your kind advice, Marco. PS: This is how in the past, more than a year ago, I created this two encrypted volume groups according to my installation notes: When installing a new Debian/testing (bullseye) OS, then I "Create new empty partition table”, then created also these two volume groups by "use as: physical volume for encryption" followed by "Create encrypted volumes".
[toc] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2021-02-23 23:10 +0100 |
| Subject | Re: authentication bug (or feature?) with multiple encrypted lvm2 volume groups |
| Message-ID | <BLO2t-6z0-3@gated-at.bofh.it> |
| In reply to | #231995 |
On Tue, 23 Feb 2021 22:19:03 +0100 Marco Möller <talby@debianlists.mobilxpress.net> wrote: > Obviously, the in Step 2 entered (wrong) password (for "A") is stored > and without further interactive consultation automatically used as > the input for the password authentication of "B". > Is this a bug or a feature? If it is a bug, where to report it? I think it is a feature. Had A and B had the same passphrase, the system would have asked for a passphrase for A, and then applied it to B as well; a nice convenience. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web