On 05/28/10 11:36, Jonas Meurer wrote:
can you give the packages at http://people.debian.org/~mejo/cryptsetup/
a try?
they contain a new upstream patch regarding stdin and key-file=- from
http://code.google.com/p/cryptsetup/source/detail?r=237 which should fix
the bug you discovered.
This se
Hi Jonas,
if I understand it correctly, the testing package is basically upstream svn
snapshot?
If it solves this regression, please let me know and I release new upstream
version,
I think more people have the same problem.
Just need to verify that current snapshot really fixes this issue.
Tha
Hello!
Yes, I can confirm the same things, harald told about. I do have exactly the
same problem. Well, my key is als on an usb-stick, and mine is nearly one year
old.
I tried the packages from mejos site. (version 1.1.1.-2-amd64), which are
working on my system.
The key is now reconized, an
hey harald,
On 28/05/2010 Harald Dunkel wrote:
> On 05/28/10 01:16, Jonas Meurer wrote:
> >
> >do you still know which cryptsetup version was used to set up your
> >environment?
>
> The partitions were encrypted several years ago. The oldest key
> file is from November 2007.
>
> >and do you use
On 05/28/10 01:16, Jonas Meurer wrote:
do you still know which cryptsetup version was used to set up your
environment?
The partitions were encrypted several years ago. The oldest key
file is from November 2007.
and do you use a keyscript like passdev? in this case i
guess that you set up the
hey Harald,
On 27/05/2010 Harald Dunkel wrote:
> Package: cryptsetup
> Version: 2:1.1.1-1
>
>
> Using the new version I cannot unlock the encrypted partitions
> anymore. Sample:
> [...]
> The keys are stored on an usb stick that is supposed to be
> mounted on the fly, as usual.
>
> Moving back
6 matches
Mail list logo
