Mutt has a really good autocrypt documentation:
Mutt: http://www.mutt.org/doc/manual/#autocryptdoc
NeoMutt: https://neomutt.org/guide/autocryptdoc.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
Dear package maintainers,
due to the fact that WoT (Web of Trust) for OpenPGP is broken [0] since
June 2019 [1] (Daniel Kahn Gillmor (dkg)) it's a needed feature to
simplify key exchange and enabling encryption on basis of OpenPGP.
Please consider my patch.
cheers,
Arsen
[0] https://lwn.net/Art
Public bug reported:
autocrypt is a cryptographic protocol for email clients aiming to simplify key
exchange and enabling encryption on basis of OpenPGP. These emails clients have
implemented it:
Thunderbird, Mailpile, Delta Chat Messenger, K-9 Mail and Mutt.
In order to activate autocrypt in M
This version has also multiple CVEs: CVE-2018-103, CVE-2017-15120,
CVE-2017-15094, CVE-2017-15090, CVE-2016-7068
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-7068
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15090
** CVE added: https://cve.mitre.org/
#10 worked for me too! I was also affected since upgrading to 15.04
32bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432271
Title:
[vivid] Abiword always starts after logging in
To manage noti
This is quite interesting although
cryptswap1 should be on /dev/dm-6 it's mounted at dm-8
grep cryptswap1 /etc/crypttab
cryptswap1 /dev/dm-6 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
ls -l /dev/mapper/cryptswap1
lrwxrwxrwx 1 root root 7 Apr 17 09:17 /dev/mapper/cryptswap1 -> ../dm-8
swapon
That did the trick!
I booted now with systemd without any issues!
Thanks
cat /etc/crypttab
#
#vg-swap /dev/dm-6 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
cryptswap1 /dev/dm-6 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
grep cryptswap1 /etc/fstab
/dev/mapper/cryptswap1 n
** Attachment added: "strace of /lib/systemd/systemd-cryptsetup attach vg-swap
/dev/dm-6 /dev/urandom swap,cipher=aes-cbc-essiv:sha256"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1443413/+attachment/4377259/+files/tt
--
You received this bug notification because you are a member
I have now booted with upstart as init, because I've forgotten to commentout
/etc/crypttab.
I hope that the attached /tmp/t still makes sense even if booted with upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
SYSTEMD_LOG_LEVEL=debug strace -fvvs1024 -o /tmp/t /lib/systemd/systemd-
cryptsetup attach vg-swap dev/dm-6 /dev/urandom swap,cipher=aes-cbc-
essiv:sha256
crypt_init() failed: Block device required
if I put a / in front of /dev/dm-6 I'm getting the flowing:
SYSTEMD_LOG_LEVEL=debug strace -fvvs102
Hi Martin,
Thanks, if I disable vg-swap it works!
Is there already a fix for this?
Can I try any updated software which fixes this?
cat /etc/crypttab
#
vg-swap /dev/dm-6 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
blkid
/dev/sda1: UUID="ojI1MN-U1rH-rsCw-HeS8-y1wj-fr0T-g0QCz
@Martin Pitti: As you requested I have filed this systemd bug. What
would you suggest to debug this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1443413
Title:
can't boot with systemd
To ma
Public bug reported:
Booting with systemd fails always at same stage.
Using upstart just works.
grep GRUB_CMDLINE_LINUX /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX="systemd.log_target=kmsg systemd.log_level=debug"
grep debug /boot/grub/grub.cfg
linux /vmlinuz-3.19.0-13-g
Public bug reported:
-D (O_DIRECT) is not working. (without -D everything runs fine)
/usr/sbin/bonnie++ -n 1024 -D >> ~/squeeze-mpath-ext4d.csv
Writing a byte at a time...Can't write() - disk full?
echo $?
1
I think its an issue with O_DIRECT.
man 2 open (notes section):
--- snip ---
O_DIRECT
Paul,
due to the fact that natty is quite old and even quantal's
lcl-utils-0.9.30.2 differ from raring's lcl-utils-0.9.30.4 at this
particular postinst-file I don't think, that this patch could be applied
to natty's lcl-utils-package.
But there is a high chance, that a modified patch could fix nat
I had a similar issue with latest version lcl-utils-0.9.30.4 in raring.
During the upgrade process from quantal (lcl-utils-0.9.30.2) to raring
(lcl-utils-0.9.30.4) lcl failed with errorcode 2.
I fixed the broken installation at lcl-utils-0.9.30.4.postinst by removing
single-quotes at ${CFG_DIR} and
** Patch added: "lcl-utils-0.9.30.4.postinst patch"
https://bugs.launchpad.net/ubuntu/+source/lazarus/+bug/771467/+attachment/3679006/+files/lcl.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
@Nathaniel
proposed is only for advanced users:
https://wiki.ubuntu.com/Testing/EnableProposed
OR
cd /etc/apt/sources.list.d/
sudo echo -n 'deb http://archive.ubuntu.com/ubuntu/ ' > proposed.list
sudo echo -n 'quantal-proposed main restricted ' >> proposed.list
sudo echo 'universe multiverse' >
Bard,
could you explain what the regression was? I am just curios.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1167114
Title:
Ubuntu Kernel 3.5.0-27 does not boot
To manage notifications about t
@kristian you are absolutely right! But as log we are waiting for an
upstream fix bumblebee fixes the problem with NVIDIA and the latest
(3.5.0-27) kernel and nobody is forced to remove the latest kernel or to
change grub to boot 3.5.0-26.
--
You received this bug notification because you are a m
@alec @Yngve and all of you who are using NVIDIA try to install bumblebee from
#30
It works for me with 3.5.0-27
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1167114
Title:
Ubuntu Kernel 3.5.0-27
Solution by memilanuk in #30 seems to work for me too. After installing
bumblebee I have not experienced the bug anymore.
lspci |grep VGA
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated
Graphics Controller (rev 02)
01:00.0 VGA compatible controller: NVIDIA Corporati
Luis I have tried your kernel but I wasn't successful.
But I have to admit, I have this issue with Nvidia:
lspci |grep VGA
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated
Graphics Controller (rev 02)
01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [NVS 3
23 matches
Mail list logo
