Bastian Blank wrote:
On Wed, Sep 30, 2009 at 12:01:05PM +0200, Milan Broz wrote:
That's the story. What's the real problem now in this bug?
What you've shown is the theory. It does not look this way on my system
nor in the 1.0.7 code.
Of course it is not theory but real implementation.
hey bastian, hey milan,
On 01/10/2009 Bastian Blank wrote:
On Wed, Sep 30, 2009 at 12:01:05PM +0200, Milan Broz wrote:
That's the story. What's the real problem now in this bug?
What you've shown is the theory. It does not look this way on my system
nor in the 1.0.7 code.
i can verify
Bastian Blank wrote:
I'm not sure, where this informations comes from, but LVM upstream
decided to use the UUID of CRYPT-TEMP-* to detect the temporary luks
devices. Also in the examples, they use CRYPT-PLAIN-* and CRYPT-LUKS1-*,
which is not set this way by the current version of cryptsetup.
On 30/09/2009 Milan Broz wrote:
Bastian Blank wrote:
I'm not sure, where this informations comes from, but LVM upstream
decided to use the UUID of CRYPT-TEMP-* to detect the temporary luks
devices. Also in the examples, they use CRYPT-PLAIN-* and CRYPT-LUKS1-*,
which is not set this way
On Wed, Sep 30, 2009 at 12:01:05PM +0200, Milan Broz wrote:
That's the story. What's the real problem now in this bug?
What you've shown is the theory. It does not look this way on my system
nor in the 1.0.7 code.
Bastian
--
Insufficient facts always invite danger.
-- Spock,
Package: cryptsetup
Version: 2:1.0.7-2
I'm not sure, where this informations comes from, but LVM upstream
decided to use the UUID of CRYPT-TEMP-* to detect the temporary luks
devices. Also in the examples, they use CRYPT-PLAIN-* and CRYPT-LUKS1-*,
which is not set this way by the current version
6 matches
Mail list logo
