Thank you for taking the time to report this bug. This issue has been
fixed in newer versions of Ubuntu, and Jaunty is EOL. Thus, I am closing
this bugtask.
** Changed in: libpam-mount (Ubuntu Jaunty)
Status: New => Invalid
--
You received this bug notification because you are a member of
As attached:-
http://launchpadlibrarian.net/26008536/LP367577.patch
...is a debdiff.
I've long since moved to karmic (where the issue is fixed) so my
interest in this bug as waned since then.
But, if that debdiff isn't valid for sponsoring I'd very much appreciate
an explanation so I don't make
I unsubscribed ubuntu-sponsors, because there is no debdiff to sponsor.
--
mount.crypt needs to pass -s to cryptsetup
https://bugs.launchpad.net/bugs/367577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
@Steve:
Thanks for taking a look at this bug.
In my opinion the other upstream cherry picks are not needed to pass -s
to cryptsetup (I've been running with the first/original fix for several
months now without issue).
I believe the other cherry picks are a separate but very closely related
bug i
marking 'incomplete' for the open question about whether the other
upstream cherry-picks are needed.
** Changed in: libpam-mount (Ubuntu Jaunty)
Status: New => Incomplete
--
mount.crypt needs to pass -s to cryptsetup
https://bugs.launchpad.net/bugs/367577
You received this bug notificatio
** Also affects: libpam-mount (Ubuntu Jaunty)
Importance: Undecided
Status: New
--
mount.crypt needs to pass -s to cryptsetup
https://bugs.launchpad.net/bugs/367577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
My understanding is that this bug is fixed upstream in the karmic
version. Opening a jaunty task for prospective SRU.
** Changed in: libpam-mount (Ubuntu)
Status: Confirmed => Fix Released
--
mount.crypt needs to pass -s to cryptsetup
https://bugs.launchpad.net/bugs/367577
You received t
Are those latter changes needed as part of this fix? If so, can you
provide them as part of a complete debdiff?
--
mount.crypt needs to pass -s to cryptsetup
https://bugs.launchpad.net/bugs/367577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Discussion for the latter changes:
http://sourceforge.net/tracker/?func=detail&aid=2727353&group_id=41452&atid=430594
** Bug watch added: SourceForge.net Tracker #2727353
http://sourceforge.net/support/tracker.php?aid=2727353
--
mount.crypt needs to pass -s to cryptsetup
https://bugs.launchpa
Worth noting is two other commitdiffs from upstream that re-add support
for overriding the keysize (and then fixing the first patch) - the use-
case for this is given with an example keysize of 448:-
(Re-)Add support for overriding keysize:-
http://pam-mount.git.sourceforge.net/git/gitweb.cgi?p=
Could very well be, upstream used the constant HXSIZEOF_Z32, I merely
used the value of that constant in the created debdiff which was
-4294967296.
If indeed it is flawed here then it's arguably also flawed upstream so
please do consider reporting it there as well.
--
mount.crypt needs to pass -
Your patch is flawed, it makes the key_size array too small.
--
mount.crypt needs to pass -s to cryptsetup
https://bugs.launchpad.net/bugs/367577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
For ages had the following in pam_mount.conf (old non-luks):
volume me crypt - /dev/sdb1 /mnt/massa_crypto-2
cipher=blowfish-cbc-essiv:sha256,keysize=448 - -
Until that didn't work anymore after upgrading to jaunty (crashes reoprted in
syslog, similar to #353935), even when trying manually and a
@jcfp:
Strange, so if you run "mount.crypt" manually from the command line with
the attached patch it (mysteriously) passes through 104 instead of 448?
Can you paste the output of running the mount.crypt command with the -v
parameter? Just curious to see what's going on there since it works
absol
Was hit by this one when updating from intrepid. Apparently went fine
until I discovered that in jaunty only one of my encrypted partitions
was being mounted, namely the one with a 256 bit keysize. None of the
others did, took me well into the night fearing all data on those disks
was lost before f
** Tags added: patch
--
mount.crypt needs to pass -s to cryptsetup
https://bugs.launchpad.net/bugs/367577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/
Jaunty test package with the debdiff applied has now been submitted to
my PPA.
--
mount.crypt needs to pass -s to cryptsetup
https://bugs.launchpad.net/bugs/367577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
** Attachment added: "LP367577.patch"
http://launchpadlibrarian.net/26008536/LP367577.patch
--
mount.crypt needs to pass -s to cryptsetup
https://bugs.launchpad.net/bugs/367577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
18 matches
Mail list logo
