My setup is exactly like the Ubuntu EncryptedFilesystemHowto:
https://help.ubuntu.com/community/EncryptedFilesystemHowto
I'm using LUKS, and /etc/crypttab with the following line:
safehome /dev/sdb4 none luks,cipher=aes-xts-plain
--
Upgrade to Karmic completely broke password prompt for
Are you 100% sure the correct password is rejected?
Positive. As said, once every n-th time the same password is accepted OK.
I've even checked if my keyboard has bouncy keys etc.
What if you try to mount the disc manually?
Manual mounting (after using cryptsetup luksOpen) works OK as
vbar wrote:
cryptsetup can't have the power to stop - why not?
Because that would interfere with Ubuntu's boot speed ambitions, I
recon. I.e. there might be cases (e.g. with key files, RFID-cards etc.)
where it might make sense to continue booting while cryptsetup does its
work unattendedly.
but the computer does not need other filesystem than root to be mounted
to boot correctly, therefore it makes no sense to depend on
other filesystems then root.
What if any of the essential directories (/var, /home, ...) reside on
other filesystems, are mounted onto the root filesystem,
Same here. This is a serious problem.
Seems like one of us users has to do something about this or the
situation won't change.
Is there any documentation other than guessing which initramfs/init
/upstart-scripts are involved?
--
Upgrade to Karmic completely broke password prompt for cryptdisks
Thanks for the reply and the workarounds, but please consider that there
are systems with custom kernels and without an initramfs.
While I admit that that concerns a smaller number of installations,
using a non-encrypted root partition with encrypted /home, /tmp, /var is
best practice if you run
Hi, Steve,
the current situation is unbearable.
If I set up my encrypted /home exactly like all the HOWTOs say (i.e.
manually after installation), the password prompt is not accessible
unless switching back to the first text console. (And even there the
password prompt is horribly broken and
Patch works well with pdftk-1.41 as of 2009-08-17.
Why not add a command-line option for this non-standards-compliant but
highly useful functionality?
--
pdftk enforces lame pseudo-drm
https://bugs.launchpad.net/bugs/127389
You received this bug notification because you are a member of Ubuntu
What I should add to my description is that I'm using the 64-Bit-version
of Kubuntu.
If other people can reproduce this error, and with only a week until the
scheduled final Jaunty release, maybe we should consider increasing the
importance or blacklisting the package for the release.
--
I've just now compiled and tried the patch.
With the updated package, the active entries in /etc/fstab stay intact
after starting and closing mountmanager again.
This largely fixes the reported bug for me.
However, because mountmanager:
1.: still deletes any comments in /etc/fstab without
Public bug reported:
Binary package hint: mountmanager
Using Kubuntu 9.04 RC for AMD64, latest upgrades, mountmanager
0.2.6-0ubuntu2
With this latest version of mountmanager, I can manage the most common mount
types in /etc/fstab.
But certain entries in /etc/fstab are deleted when applying
Public bug reported:
Binary package hint: mountmanager
Hi,
Kubuntu 9.04 Beta, latest upgrades, mountmanager 0.2.6.
I tried mountmanager without saving any configuration.
After exiting the program, my fstab was empty!
This is _really_ nasty when NFS mounts with various server addresses,
** Changed in: libpam-mount (Ubuntu)
Status: New = Confirmed
--
pam_mount(pam_mount.c:100): unknown pam_mount option use_first_pass
https://bugs.launchpad.net/bugs/332833
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Same for me since recent upgrade in Jaunty Beta.
--
pam_mount(pam_mount.c:100): unknown pam_mount option use_first_pass
https://bugs.launchpad.net/bugs/332833
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Regarding Dimitrios first comment:
Indeed, this might be a problem because the maintainer likely focuses on bugs
in newer Ubuntu releases.
This is understandable.
/But/: 6.06 _is_ supposed to be a LTS distribution! There is still
official support.
/Plus/, AFAIK, the problem still persists
Hello, maintainer...
--
Encrypted SWAP partition not created/mounted
https://bugs.launchpad.net/bugs/316607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
Many thanks for your help Shiv!
I've applied the patch to vol_id and un_vol_id in /lib/cryptsetup/checks/.
Now, the automated creation of the swap device works again.
Looking at the scripts, your explanation seems absolutely plausible to
me.
I've even cross-checked the detection by trying
Public bug reported:
Binary package hint: cryptsetup
Hi,
after updating to Jaunty Alpha, the setup of cryptographic swap on boot fails
with the following message:
* SWAP: the check for '/dev/mapper/SWAP' failed. /dev/mapper/SWAP
contains data: - The device /dev/mapper/SWAP contains a valid
Content of my /etc/ctypttab:
# target name source device key file options
SWAP /dev/sde8 /dev/urandom swap
--
Encrypted SWAP partition not created/mounted
https://bugs.launchpad.net/bugs/316607
You received this bug notification because you are a member of Ubuntu
Bugs, which is
19 matches
Mail list logo
