Isn't 1 TB an overly conservative estimate? The probability of a
successful attack on 1 PB of data is only eight in a trillion. See
http://en.wikipedia.org/wiki/XTS#XTS. Truecrypt sets its maximum volume
size at 1 PB for this reason.
On 1/27/2009 8:37 PM, Colin Watson wrote:
It may be worth
I can confirm this bug on Ubuntu 8.10. Nikolaus is correct. Not only may
UUIDs be used to reference LVM volumes in /etc/fstab, this is the
default configuration in 8.10. I followed the instructions here
(https://help.ubuntu.com/community/EncryptedFilesystemLVMHowto) in order
to create a LUKS+LVM
That should read - isn't the partition decrypted by the time fstab is
read to mount the LVM volumes?
--
cryptsetup does not understand UUID= in fstab and conf.d/resume
https://bugs.launchpad.net/bugs/287879
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Note that following installation you'll need to use a live CD to modify
/etc/crypttab, /etc/fstab, load the necessary modules and rebuild
initrd. It may be easier to just follow this howto if you want LVM+LUKS
(https://help.ubuntu.com/community/EncryptedFilesystemLVMHowto). I can
confirm that this
Nevermind, I figured out how to create an LUKS+LVM encrypted Ubuntu
install using the
https://help.ubuntu.com/community/EncryptedFilesystemLVMHowto
instructions.
The last step must be slightly modified, and a few more steps are
necessary to create the LVM.
Instead of cryptsetup luksOpen
WORKAROUND:
This issue doesn't arise if the system uses uswsusp rather than the
kernel's method of hibernation. So, the fix is to force gnome-power-
management to use s2disk rather than the kernel method. This is fairly
simple to do:
Download the attached script hal-system-power-hibernate-linux
BETTER WORKAROUND:
sudo apt-get install uswsusp
sudo dpkg-divert --rename --divert /usr/sbin/pmi-disabled /usr/sbin/pmi
To undo:
sudo dpkg-divert --rename --remove /usr/sbin/pmi
See http://blog.paulbetts.org/index.php/2007/02/11/fixing-software-
Marc,
Your instructions don't appear to work when using LVM as the installer
fails to format the LVM volumes. Any idea how to modify your
instructions to create an LUKS+LVM encrypted partition so that I can
have separate /home, /, and swap?
Jason
--
support AES-XTS mode
Thank you for the guide. I was just in the process of installing Ubuntu
8.10 on my laptop via the alternative CD when I realized that XTS wasn't
supported. I will be following your instructions to encrypt my system
with AES-XTS.
--
support AES-XTS mode
https://bugs.launchpad.net/bugs/244480
You
I can confirm this behavior on both Ubuntu Intrepid and Windows XP SP3
using pidgin 2.5.2/3 and pidgin-otr 3.2.0. I describe OTR's handling
here: http://lists.cypherpunks.ca/pipermail/otr-
users/2008-December/001562.html
--
OTR should close a session, if the other chat partner logs out
Public bug reported:
Binary package hint: gnome-power-manager
1) Ubuntu 8.10 (Intrepid)
2) 2.24.0-0ubuntu8.1
3) I expected the system to resume from hibernate properly without outputting
error messages or hanging gnome-power-manager.
4) I am able to manually hibernate the system from the GNOME
** Attachment added: syslog.txt
http://launchpadlibrarian.net/20771946/syslog.txt
** Description changed:
Binary package hint: gnome-power-manager
1) Ubuntu 8.10 (Intrepid)
2) 2.24.0-0ubuntu8.1
3) I expected the system to resume from hibernate properly without outputting
error
** Summary changed:
- Auto-hibernate due to inactivity results in a resumed session with hanged
gnome-power-manager preventing the system from going into hibernate again
+ Auto-hibernate due to inactivity results in a resumed session with hanged
gnome-power-manager preventing the system from
I can confirm this issue with the OpenVPN network-manger plugin on
Intrepid.
--
Network Manager does not connect VPN on startup even with Autoconnect option
enabled.
https://bugs.launchpad.net/bugs/302123
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: network-manager
1) Ubuntu 8.10 (Intrepid)
2) network-manager_0.7~~svn20081018t105859-0ubuntu1.8.10.1
Kernel 2.6.27-9-generic
3) I expected to be able to connect to an WPA2-Enterprise EAP-TLS
network.
4) With the new version of network-manager (which
Network-Manager 0.7~~svn20081018t105859-0ubuntu1.8.10.1 fixes the
reliability problem.
** Changed in: network-manager (Ubuntu)
Status: New = Fix Released
--
Ubuntu fails to reliably associate with WPA2-Enterprise networks using either
the WG511T (AR5212) or Intel 4965AGN wireless
Alexander,
I can confirm that the 0.7~~svn20081018t105859-0ubuntu1.8.10.1 update
waits 60 seconds before giving a timeout error. Through my testing I
have discovered two separate bugs, the first of which is mitigated by
this package.
1. Some drivers take too long to associate with the 2.6.27
PEAPv0/EAP-MSCHAPv2 and EAP-TTLS/MSCHAPv2 both connect every time under
kernel 2.6.27. It just takes longer than 2.6.24. If you would like me to
test any other configurations I have a FreeRADIUS at my disposal.
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for
That should read FreeRADIUS server.
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I gave the wrong bug # earlier. The bug I reported was Bug #307622
(Ubuntu fails to reliably associate with WPA2-Enterprise networks using
either the WG511T (AR5212) or Intel 4965AGN wireless chipsets with
2.6.27 kernel).
--
Some drivers take too long to associate (Was: network-manager 0.7
Network-Manager 0.7~~svn20081018t105859-0ubuntu1.8.10.1 allows Ubuntu
8.10 to reliably associate to PEAP and EAP-TTLS networks. I still have
not found a configuration that allows EAP-TLS to function.
--
Ubuntu fails to reliably associate with WPA2-Enterprise networks using either
the WG511T
I should have said Network-Manager
0.7~~svn20081018t105859-0ubuntu1.8.10.1 allows Ubuntu 8.10 to reliably
associate to PEAP and EAP-TTLS networks with kernel 2.6.27 on my
hardware (WG511T or Intel 4965AGN chispet).
--
Ubuntu fails to reliably associate with WPA2-Enterprise networks using either
PARTIAL SOLUTION:
Apparently I was wrong. The failure to reliably authenticate issue was
in fact a driver problem. I am now able to connect to PEAP and EAP-TTLS
networks reliably using the 2.6.24-22-386 kernel. Now I can connect
every time rather than every sixth time.
However, the EAP-TLS issue
So, it appears this is not a network-manager bug after all. Should it be
re-tagged as a kernel issue?
--
Ubuntu fails to reliably associate with WPA2-Enterprise networks using either
the WG511T (AR5212) or Intel 4965AGN wireless chipsets with 2.6.27 kernel.
Public bug reported:
Binary package hint: network-manager
1) Ubuntu 8.10 (Intrepid)
2) network-manager (0.7~~svn20081018t105859-0ubuntu1)
3) I expected to be able to use a WPA2-Enterprise network reliably and connect
within a reasonable period of time (e.g. 30 seconds).
4) It takes 5 to 6
William,
There's a simpler solution.
apt-get install wajig
wajig hold package
--
brings up both wired and wireless interfaces; hard to pick just one through the
UI
https://bugs.launchpad.net/bugs/262152
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm still having timeout problems with the new package. PEAPv0/MSCHAPv2
will occasionally connect whereas EAP-TLS consistently fails to connect.
The bizarre part is that the majority of the time the RADIUS server
doesn't even get a request for authentication, and when it does get a
request, the
I can confirm that encrypting the key fixes the problem. It doesn't
matter whether the certificates/key are in PEM or DER format. If the key
is encrypted, and the correct password is inputted, the connect button
lights up and becomes usable.
However, that doesn't fix the fact that network-manager
I can confirm that this bug affects Intrepid as well. wajig fixed the
problem, though.
--
Hold packages
https://bugs.launchpad.net/bugs/35836
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: pidgin
Package: pidgin-otr (Intrepid) 3.2.0-1
Version of Ubuntu: Ubuntu 8.10 (Intrepid)
Systems used: AMD XP 3200+, 1 GB DDR, 160 GB HDD running Ubuntu 8.10
HP dv9500t laptop, 2.0 Ghz Core 2 Duo, 2 GB DDR, 160
GB HDD running of
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/20086211/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/20086212/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/20086213/ProcStatus.txt
** Also
** Changed in: pidgin-otr
Status: New = Invalid
--
Pidgin freezes when generating new OTR private key
https://bugs.launchpad.net/bugs/303862
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: pidgin-otr
Package: pidgin-otr (Intrepid) 3.2.0-1
Version of Ubuntu: Ubuntu 8.10 (Intrepid)
Systems used: AMD XP 3200+, 1 GB DDR, 160 GB HDD running Ubuntu 8.10
HP dv9500t laptop, 2.0 Ghz Core 2 Duo, 2 GB DDR, 160 GB
HDD running
** Attachment added: pidgin.log
http://launchpadlibrarian.net/20086497/pidgin.log
--
Pidgin freezes when generating new OTR private key
https://bugs.launchpad.net/bugs/303866
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Description changed:
Binary package hint: pidgin-otr
Package: pidgin-otr (Intrepid) 3.2.0-1
Version of Ubuntu: Ubuntu 8.10 (Intrepid)
Systems used: AMD XP 3200+, 1 GB DDR, 160 GB HDD running Ubuntu 8.10
HP dv9500t laptop, 2.0 Ghz Core 2 Duo, 2 GB DDR, 160
In addition, while Pidgin was frozen, CPU usage remained near 0%.
--
Pidgin freezes when generating new OTR private key
https://bugs.launchpad.net/bugs/303866
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Key creation did not succeed here even after 45 minutes elapsed.
--
Pidgin freezes when generating new OTR private key
https://bugs.launchpad.net/bugs/303866
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
37 matches
Mail list logo
