Re: [Bug 244480] Re: support AES-XTS mode
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 noting the comment in http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=494584 to the effect that XTS' security guarantees deteriorate over 1TB, so the installer would need to have a warning about this. ** Changed in: partman-crypto (Ubuntu) Importance: Undecided = Wishlist Status: Confirmed = Triaged -- support AES-XTS mode https://bugs.launchpad.net/bugs/244480 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/mailman/listinfo/ubuntu-bugs
[Bug 287879] Re: cryptsetup does not understand UUID= in fstab and conf.d/resume
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 encrypted system with AES-XTS, which as of this time is currently unsupported by the alternative installer. After manually creating a LUKS volume, setting up the LVM, and creating the partitions using the 8.10 Live CD, I installed as normal. The installer setup the system as if it was an unencrypted LVM volume. The LVM volumes in /etc/fstab were referenced by their UUID. However, I found that with this setup the system is unbootable, and no warning is displayed when the initrd is created. There simply is no config/config.d/cryptroot and thus the system is unbootable. Modifying /etc/fstab to reference the device name resolves the issue. However, UUIDs may be used in /etc/crypttab. My understanding from reading some other bug reports is that the UUID is inaccessible because it's only available when the volume has been decrypted. However, aren't the partitions mounted by the time fstab is read to mount them? I would assume /etc/crypttab is read first to decrypt the LUKS volume, and then the UUID of the LVM volumes should be accessible to the system. Perhaps I'm wrong about this. Anyway, this is a serious issue as it causes the system to become unbootable with no warning. -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 287879] Re: cryptsetup does not understand UUID= in fstab and conf.d/resume
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 244480] Re: support AES-XTS mode
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 method works, and contrary to the HOWTO, hibernate works great in Ubuntu 8.10 with the Nvidia biinary drivers. Just replace aes-cbc-essiv:sha256 with aes-xts-plain when creating the LUKS volume. -- support AES-XTS mode https://bugs.launchpad.net/bugs/244480 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/mailman/listinfo/ubuntu-bugs
[Bug 244480] Re: support AES-XTS mode
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 /dev/sda5 sda5_crypt Do cryptsetup luksOpen /dev/sda5 pvcrypt Then: pvcreate /dev/mapper/pvcrypt vgcreate vg /dev/mapper/pvcrypt lvcreate -n lvname -L size vg ex. lvcreate -n home -L 35G vg This will create a logical volume named home with a size of 35 GB. You need to create a new logical volume (lvname) for each partition and set the size you want. I created three - root, home, and swap. My setup looks like this: lvdisplay -C home vg -wi-ao 35,00G root vg -wi-ao 20,00G swap vg -wi-ao 2,00G Once you've done that, Ctrl-alt-F1 to return to the setup screen. Choose Finish. You'll get an error stating that sda5_crypt couldn't be found. Select yes to return to the setup screen. Now you'll see the LVM volumes you created. Assign mount points to each volume and continue the install as normal. Jason -- support AES-XTS mode https://bugs.launchpad.net/bugs/244480 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/mailman/listinfo/ubuntu-bugs
[Bug 311860] Re: Auto-hibernate due to inactivity results in a resumed session with hanged gnome-power-manager preventing the system from entering hibernate again
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 sudo apt-get install uswsusp sudo s2disk##Test to see if s2disk works. CAUTION: make sure data is saved for this test! sudo mv /usr/lib/hal/scripts/linux/hal-system-power-hibernate-linux /usr/lib/hal/scripts/linux/hal-system-power-hibernate-linux.backup sudo cp hal-system-* /usr/lib/hal/scripts/linux/ sudo chmod 755 /usr/lib/hal/scripts/linux/* Now, gnome-power-manager should use s2disk to hibernate fixing my reported issue. Note: I found these instructions from http://blog.paulbetts.org/index.php/2007/02/11/fixing-software-suspend- hibernate-with-uswsusp-in-ubuntu-feisty-and-edgy/#comment-17671. The only change I made was to modify the script to reflect the location of the s2disk binary in Ubuntu 8.10. ** Attachment added: hal-system-power-hibernate-linux http://launchpadlibrarian.net/20810875/hal-system-power-hibernate-linux -- Auto-hibernate due to inactivity results in a resumed session with hanged gnome-power-manager preventing the system from entering hibernate again https://bugs.launchpad.net/bugs/311860 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/mailman/listinfo/ubuntu-bugs
[Bug 311860] Re: Auto-hibernate due to inactivity results in a resumed session with hanged gnome-power-manager preventing the system from entering hibernate again
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- suspend-hibernate-with-uswsusp-in-ubuntu-feisty-and-edgy/#comment-17671 (Comment by Robin Battey) -- Auto-hibernate due to inactivity results in a resumed session with hanged gnome-power-manager preventing the system from entering hibernate again https://bugs.launchpad.net/bugs/311860 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/mailman/listinfo/ubuntu-bugs
[Bug 244480] Re: support AES-XTS mode
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 https://bugs.launchpad.net/bugs/244480 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/mailman/listinfo/ubuntu-bugs
[Bug 244480] Re: 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 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/mailman/listinfo/ubuntu-bugs
[Bug 307964] Re: OTR should close a session, if the other chat partner logs out
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 https://bugs.launchpad.net/bugs/307964 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/mailman/listinfo/ubuntu-bugs
[Bug 311860] [NEW] Auto-hibernate due to inactivity results in a resumed session with hanged gnome-power-manager preventing the system from going into hibernate again
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 menu and resume without issue. However, if the system hibernates automatically after a period of inactivity, when the system is resumed I see the below error message. In addition, it appears that gnome-power-manager has hanged because selecting hibernate from the GNOME menu does nothing. In addition, when I attempt to shut down I am warned that gnome-power- manager is not responding. Killing gnome-power-manager and restarting it restores hibernate functionality. Error Message: http://img48.imageshack.us/img48/495/hibernatewarningpq2.png ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- Auto-hibernate due to inactivity results in a resumed session with hanged gnome-power-manager preventing the system from going into hibernate again https://bugs.launchpad.net/bugs/311860 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/mailman/listinfo/ubuntu-bugs
[Bug 311860] Re: Auto-hibernate due to inactivity results in a resumed session with hanged gnome-power-manager preventing the system from going into hibernate again
** 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 messages or hanging gnome-power-manager. 4) I am able to manually hibernate the system from the GNOME menu and resume without issue. However, if the system hibernates automatically after a period of inactivity, when the system is resumed I see the below error message. In addition, it appears that gnome-power-manager has hanged because selecting hibernate from the GNOME menu does nothing. In addition, when I attempt to shut down I am warned that gnome-power- manager is not responding. Killing gnome-power-manager and restarting it restores hibernate functionality. - [URL=http://img48.imageshack.us/my.php?image=hibernatewarningpq2.png][IMG]http://img48.imageshack.us/img48/495/hibernatewarningpq2.png[/IMG][/URL] - [URL=http://g.imageshack.us/img48/hibernatewarningpq2.png/1/][IMG]http://img48.imageshack.us/img48/hibernatewarningpq2.png/1/w312.png[/IMG][/URL] + a target='_blank' title='ImageShack - Image And Video Hosting' + href='http://img48.imageshack.us/my.php?image=hibernatewarningpq2.png'img + src='http://img48.imageshack.us/img48/495/hibernatewarningpq2.png' + border='0'//abr/a + href=http://g.imageshack.us/img48/hibernatewarningpq2.png/1/;img + src=http://img48.imageshack.us/img48/hibernatewarningpq2.png/1/w312.png; + border=0/a ** 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 messages or hanging gnome-power-manager. 4) I am able to manually hibernate the system from the GNOME menu and resume without issue. However, if the system hibernates automatically after a period of inactivity, when the system is resumed I see the below error message. In addition, it appears that gnome-power-manager has hanged because selecting hibernate from the GNOME menu does nothing. In addition, when I attempt to shut down I am warned that gnome-power- manager is not responding. Killing gnome-power-manager and restarting it restores hibernate functionality. - a target='_blank' title='ImageShack - Image And Video Hosting' - href='http://img48.imageshack.us/my.php?image=hibernatewarningpq2.png'img - src='http://img48.imageshack.us/img48/495/hibernatewarningpq2.png' - border='0'//abr/a - href=http://g.imageshack.us/img48/hibernatewarningpq2.png/1/;img - src=http://img48.imageshack.us/img48/hibernatewarningpq2.png/1/w312.png; - border=0/a + a + href=http://img48.imageshack.us/my.php?image=hibernatewarningpq2.png; + target=_blankimg + src=http://img48.imageshack.us/img48/495/hibernatewarningpq2.th.png; + border=0 alt=Free Image Hosting at www.ImageShack.us //abr /br + /a + href=http://img604.imageshack.us/content.php?page=blogpostfiles=img48/495/hibernatewarningpq2.png; + title=QuickPostimg src=http://imageshack.us/img/butansn.png; + alt=QuickPost border=0/a ** 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 messages or hanging gnome-power-manager. 4) I am able to manually hibernate the system from the GNOME menu and resume without issue. However, if the system hibernates automatically after a period of inactivity, when the system is resumed I see the below error message. In addition, it appears that gnome-power-manager has hanged because selecting hibernate from the GNOME menu does nothing. In addition, when I attempt to shut down I am warned that gnome-power- manager is not responding. Killing gnome-power-manager and restarting it restores hibernate functionality. - a - href=http://img48.imageshack.us/my.php?image=hibernatewarningpq2.png; - target=_blankimg - src=http://img48.imageshack.us/img48/495/hibernatewarningpq2.th.png; - border=0 alt=Free Image Hosting at www.ImageShack.us //abr /br - /a - href=http://img604.imageshack.us/content.php?page=blogpostfiles=img48/495/hibernatewarningpq2.png; - title=QuickPostimg src=http://imageshack.us/img/butansn.png; - alt=QuickPost border=0/a + Error Message: + http://img48.imageshack.us/my.php?image=hibernatewarningpq2.png ** 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 messages or hanging gnome-power-manager. 4) I am able to manually hibernate the system from the GNOME menu and resume without issue. However, if the system hibernates automatically after a period of inactivity, when the system is resumed I see the below error message. In
[Bug 311860] Re: Auto-hibernate due to inactivity results in a resumed session with hanged gnome-power-manager preventing the system from entering hibernate again
** 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 entering hibernate again -- Auto-hibernate due to inactivity results in a resumed session with hanged gnome-power-manager preventing the system from entering hibernate again https://bugs.launchpad.net/bugs/311860 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/mailman/listinfo/ubuntu-bugs
[Bug 302123] Re: Network Manager does not connect VPN on startup even with Autoconnect option enabled.
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 309629] [NEW] EAP-TLS network fails to connect with timeout message
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 increases the time allowed for connections to 60 seconds) I can reliably connect to my network when I use PEAP or EAP-TTLS. However, I have never been able to successfully connect to my network using EAP-TLS in Ubuntu 8.10 despite the fact that each connection attempt shows a successful login in my RADIUS server log. The exact same setup worked in Ubuntu 8.04 and works in Windows XP with 3 different supplicants (XP supplicant, Juniper Access Client, Intel PROSet). I've even tried using the Hardy network- manager, wpasupplicant, and kernel packages yet EAP-TLS still doesn't work in Ubuntu 8.10. I am currently using the latest version of all above-mentioned packages. Syslog: Dec 19 04:14:46 jason-laptop NetworkManager: info (ath0): bringing up device. Dec 19 04:14:46 jason-laptop NetworkManager: info (ath0): preparing device. Dec 19 04:14:46 jason-laptop NetworkManager: info (ath0): deactivating device (reason: 2). Dec 19 04:14:46 jason-laptop NetworkManager: info (eth0): carrier now ON (device state 2) Dec 19 04:14:46 jason-laptop NetworkManager: info (eth0): device state change: 2 - 3 Dec 19 04:14:46 jason-laptop NetworkManager: info (eth0): carrier now OFF (device state 3) Dec 19 04:14:46 jason-laptop NetworkManager: info (eth0): device state change: 3 - 2 Dec 19 04:14:46 jason-laptop NetworkManager: info (eth0): deactivating device (reason: 0). Dec 19 04:14:46 jason-laptop NetworkManager: info (ath0): device state change: 2 - 3 Dec 19 04:14:46 jason-laptop NetworkManager: info (ath0): supplicant interface state change: 1 - 2. Dec 19 04:15:17 jason-laptop NetworkManager: info Activation (ath0) starting connection 'Auto Wireless 9568392' Dec 19 04:15:17 jason-laptop NetworkManager: info (ath0): device state change: 3 - 4 Dec 19 04:15:17 jason-laptop NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... Dec 19 04:15:17 jason-laptop NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) started... Dec 19 04:15:17 jason-laptop NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... Dec 19 04:15:17 jason-laptop NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) complete. Dec 19 04:15:17 jason-laptop NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) starting... Dec 19 04:15:17 jason-laptop NetworkManager: info (ath0): device state change: 4 - 5 Dec 19 04:15:17 jason-laptop NetworkManager: info Activation (ath0/wireless): access point 'Auto Wireless 9568392' has security, but secrets are required. Dec 19 04:15:17 jason-laptop NetworkManager: info (ath0): device state change: 5 - 6 Dec 19 04:15:17 jason-laptop NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) complete. Dec 19 04:15:18 jason-laptop NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... Dec 19 04:15:18 jason-laptop NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) started... Dec 19 04:15:18 jason-laptop NetworkManager: info (ath0): device state change: 6 - 4 Dec 19 04:15:18 jason-laptop NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... Dec 19 04:15:18 jason-laptop NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) complete. Dec 19 04:15:18 jason-laptop NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) starting... Dec 19 04:15:18 jason-laptop NetworkManager: info (ath0): device state change: 4 - 5 Dec 19 04:15:18 jason-laptop NetworkManager: info Activation (ath0/wireless): connection 'Auto Wireless 9568392' has security, and secrets exist. No new secrets needed. Dec 19 04:15:18 jason-laptop NetworkManager: info Config: added 'ssid' value 'Wireless 9568392' Dec 19 04:15:18 jason-laptop NetworkManager: info Config: added 'scan_ssid' value '1' Dec 19 04:15:18 jason-laptop NetworkManager: info Config: added 'key_mgmt' value 'WPA-EAP' Dec 19 04:15:18 jason-laptop NetworkManager: info Config: added 'proto' value 'WPA RSN' Dec 19 04:15:18 jason-laptop NetworkManager: info Config: added 'pairwise' value 'TKIP CCMP' Dec 19 04:15:18 jason-laptop NetworkManager: info Config: added 'group' value 'WEP40 WEP104 TKIP CCMP' Dec 19 04:15:18 jason-laptop NetworkManager: info Config: added 'eap' value 'TLS' Dec 19 04:15:18 jason-laptop NetworkManager: info Config: added 'fragment_size' value '1300' Dec 19 04:15:18 jason-laptop NetworkManager: info Config: added 'ca_cert' value 'blob://-org-freedesktop-NetworkManagerSettings-0-ca_cert' Dec 19 04:15:18 jason-laptop NetworkManager: info Config: added 'client_cert'
[Bug 307622] Re: Ubuntu fails to reliably associate with WPA2-Enterprise networks using either the WG511T (AR5212) or Intel 4965AGN wireless chipsets with 2.6.27 kernel.
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 chipsets with 2.6.27 kernel. https://bugs.launchpad.net/bugs/307622 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/mailman/listinfo/ubuntu-bugs
[Bug 292054] Re: Some drivers take too long to associate (Was: network-manager 0.7 always asks for WPA passphrase)
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 kernel (tested WG511T and Intel 4965AGN chipsets). This delay is NOT present in the 2.6.24 kernel from Hardy. 2.EAP-TLS does not work under any configuration (tested with 2.6.24, 2.6.27, NM 0.6 and 0.7, wpasupplicant from hardy and intrepid, and every combination of kernel, network-manager, and wpasupplicant). With the latest patch, the server shows a successful authentication each time I try to connect, but the connection always fails with a timeout message on the client side. I reported these issues in Bug # 35836 but I think #1 should be reported as a kernel problem, and #2 separated. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292054] Re: Some drivers take too long to associate (Was: network-manager 0.7 always asks for WPA passphrase)
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 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292054] Re: Some drivers take too long to associate (Was: network-manager 0.7 always asks for WPA passphrase)
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292054] Re: Some drivers take too long to associate (Was: network-manager 0.7 always asks for WPA passphrase)
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 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 307622] Re: Ubuntu fails to reliably associate with WPA2-Enterprise networks using either the WG511T (AR5212) or Intel 4965AGN wireless chipsets with 2.6.27 kernel.
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 (AR5212) or Intel 4965AGN wireless chipsets with 2.6.27 kernel. https://bugs.launchpad.net/bugs/307622 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/mailman/listinfo/ubuntu-bugs
[Bug 307622] Re: Ubuntu fails to reliably associate with WPA2-Enterprise networks using either the WG511T (AR5212) or Intel 4965AGN wireless chipsets with 2.6.27 kernel.
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 the WG511T (AR5212) or Intel 4965AGN wireless chipsets with 2.6.27 kernel. https://bugs.launchpad.net/bugs/307622 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/mailman/listinfo/ubuntu-bugs
[Bug 307622] Re: Ubuntu fails to reliably associate with WPA2-Enterprise networks using either the WG511T (AR5212) or Intel 4965AGN wireless chipsets.
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 hasn't gone away. I've tested using Hardy's wpasupplicant, network-manager, network-manager-gnome, and Hardy's network-manager libraries. In every case, each connection attempt led to a successful authentication on the RADIUS server, but Ubuntu failed to connect with the same timeout message. Upgrading to the latest version of wpasupplicant and network-manager packages hasn't helped. Status: EAP-TLS never works. PEAP and EAP-TTLS work consistently. Fix: Use 2.6.24 kernel from Hardy packages So any idea what could cause EAP-TLS networks to fail when the RADIUS server authenticates the user properly and does so promptly? What other packages could be involved? ** Summary changed: - Ubuntu fails to reliably associate with WPA2-Enterprise networks using either the WG511T (AR5212) or Intel 4965AGN wireless chipsets. + Ubuntu fails to reliably associate with WPA2-Enterprise networks using either the WG511T (AR5212) or Intel 4965AGN wireless chipsets with 2.6.27 kernel. ** Description changed: 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 attempts to connect using EAP-TTLS or PEAP and EAP-TLS doesn't work at all, despite showing a successful authentication message in my FreeRADIUS logs. In each case, it takes 4 or 5 connection attempts before my FreeRADIUS logs show any activity. In Ubuntu 8.04, I can reliably connect on the first try. My server logs show a successful authentication within 2-3 seconds of clicking the connect button in Ubuntu 8.04. I have tested using my own WPA2-Enterprise wireless network using EAP- TLS, PEAPv0/MSCHAPv2 and EAP-TTLS/MSCHAPv2 in both Ubuntu 8.04 and 8.10. I am able to reliably and quickly connect using Ubuntu 8.04 but no setup works reliably in Ubuntu 8.10. Under Ubuntu 8.04, within 2-3 seconds of clicking on my network, my FreeRADIUS server logs show a successful connection using any of the above mentioned EAP types. However, in Ubuntu 8.10 (with the latest network-manager package), I see absolutely no ATTEMPT to connect to my RADIUS server . Even when running the server in debugging mode, in 5 out of 6 connection attempts, the server shows no activity at all. With PEAP and EAP-TLS, when the server shows a successful authentication, Ubuntu connects properly. However, even when the server shows a successful authentication attempt with EAP-TLS, Ubuntu still fails to connect. WPA2-PSK, WEP, and open networks work fine in Ubuntu 8.10. In addition, I have tested my network on Windows XP SP3 with Juniper's Odyssey Access Client, Intel's PROSet client, and XP's included supplicant. PEAP and EAP-TLS work in all three (XP's supplicant doesn't support EAP-TTLS). - If this is indeed a driver issue as suggested, why is it affecting two - different wireless chipsets, manufactured by different companies, which - use different drivers, in precisely the same way? Both chipsets work - with EAP-TLS, PEAP, and EAP-TTLS in 8.04. Neither work at all with EAP- - TLS, and both work intermittently with PEAP and EAP-TTLS. I am able to - reproduce this issue consistently on either a fresh install of 8.10 - (with or without updates) or with the Live CD (with or without updates) - on both an old Dell Inspiron 8200 laptop with a 1.2 ghz CPU and 1 GB of - RAM with the WG511T and on the 1 year-old HP dv9500t 2 Ghz Core 2 Duo, 2 - GB RAM laptop with the Intel 4945AGN chip. Completely different - hardware, different wireless chipsets, both exhibiting the same behavior - off a freshly updated install of Ubuntu 8.10. + PARTIAL SOLUTION: PEAP and EAP-TTLS work reliably while using the 2.6.24 + kernel. EAP-TLS still doesn't work despite showing a successful + authentication on the RADIUS server. Attempted connection to WPA2-Enterprise network using EAP-TLS authentication in Ubuntu 8.10: Dec 12 23:02:49 jason-laptop NetworkManager: info (ath0): device state change: 5 - 6 Dec 12 23:02:49 jason-laptop NetworkManager: info Activation (ath0/wireless): asking for new secrets Dec 12 23:02:49 jason-laptop NetworkManager: info (ath0): supplicant connection state change: 4 - 0 Dec 12 23:02:52 jason-laptop NetworkManager: WARN get_secrets_cb(): Couldn't get connection secrets: applet-device-wifi.c.1512 (get_secrets_dialog_response_cb): canceled. Dec 12 23:02:52 jason-laptop NetworkManager: info (ath0): device state change: 6 - 9 Dec 12 23:02:52 jason-laptop NetworkManager: info Activation (ath0) failed
[Bug 307622] Re: Ubuntu fails to reliably associate with WPA2-Enterprise networks using either the WG511T (AR5212) or Intel 4965AGN wireless chipsets with 2.6.27 kernel.
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. https://bugs.launchpad.net/bugs/307622 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/mailman/listinfo/ubuntu-bugs
[Bug 307622] [NEW] Ubuntu fails to reliably associate with WPA2-Enterprise networks using either the WG511T (AR5212) or Intel 4965AGN wireless chipsets.
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 attempts to connect using EAP-TTLS or PEAP and EAP-TLS doesn't work at all, despite showing a successful authentication message in my FreeRADIUS logs. In each case, it takes 4 or 5 connection attempts before my FreeRADIUS logs show any activity. In Ubuntu 8.04, I can reliably connect on the first try. My server logs show a successful authentication within 2-3 seconds of clicking the connect button in Ubuntu 8.04. I have tested using my own WPA2-Enterprise wireless network using EAP- TLS, PEAPv0/MSCHAPv2 and EAP-TTLS/MSCHAPv2 in both Ubuntu 8.04 and 8.10. I am able to reliably and quickly connect using Ubuntu 8.04 but no setup works reliably in Ubuntu 8.10. Under Ubuntu 8.04, within 2-3 seconds of clicking on my network, my FreeRADIUS server logs show a successful connection using any of the above mentioned EAP types. However, in Ubuntu 8.10 (with the latest network-manager package), I see absolutely no ATTEMPT to connect to my RADIUS server . Even when running the server in debugging mode, in 5 out of 6 connection attempts, the server shows no activity at all. With PEAP and EAP-TLS, when the server shows a successful authentication, Ubuntu connects properly. However, even when the server shows a successful authentication attempt with EAP-TLS, Ubuntu still fails to connect. WPA2-PSK, WEP, and open networks work fine in Ubuntu 8.10. In addition, I have tested my network on Windows XP SP3 with Juniper's Odyssey Access Client, Intel's PROSet client, and XP's included supplicant. PEAP and EAP-TLS work in all three (XP's supplicant doesn't support EAP-TTLS). If this is indeed a driver issue as suggested, why is it affecting two different wireless chipsets, manufactured by different companies, which use different drivers, in precisely the same way? Both chipsets work with EAP-TLS, PEAP, and EAP-TTLS in 8.04. Neither work at all with EAP- TLS, and both work intermittently with PEAP and EAP-TTLS. I am able to reproduce this issue consistently on either a fresh install of 8.10 (with or without updates) or with the Live CD (with or without updates) on both an old Dell Inspiron 8200 laptop with a 1.2 ghz CPU and 1 GB of RAM with the WG511T and on the 1 year-old HP dv9500t 2 Ghz Core 2 Duo, 2 GB RAM laptop with the Intel 4945AGN chip. Completely different hardware, different wireless chipsets, both exhibiting the same behavior off a freshly updated install of Ubuntu 8.10. Attempted connection to WPA2-Enterprise network using EAP-TLS authentication in Ubuntu 8.10: Dec 12 23:02:49 jason-laptop NetworkManager: info (ath0): device state change: 5 - 6 Dec 12 23:02:49 jason-laptop NetworkManager: info Activation (ath0/wireless): asking for new secrets Dec 12 23:02:49 jason-laptop NetworkManager: info (ath0): supplicant connection state change: 4 - 0 Dec 12 23:02:52 jason-laptop NetworkManager: WARN get_secrets_cb(): Couldn't get connection secrets: applet-device-wifi.c.1512 (get_secrets_dialog_response_cb): canceled. Dec 12 23:02:52 jason-laptop NetworkManager: info (ath0): device state change: 6 - 9 Dec 12 23:02:52 jason-laptop NetworkManager: info Activation (ath0) failed for access point (Wireless 9568392) Dec 12 23:02:52 jason-laptop NetworkManager: info Marking connection 'Auto Wireless 9568392' invalid. Dec 12 23:02:52 jason-laptop NetworkManager: info Activation (ath0) failed. Dec 12 23:02:52 jason-laptop NetworkManager: info (ath0): device state change: 9 - 3 Dec 12 23:02:52 jason-laptop NetworkManager: info (ath0): deactivating device (reason: 0). Dec 12 23:05:24 jason-laptop NetworkManager: info Activation (ath0) starting connection 'Auto Wireless 9568392' Dec 12 23:05:24 jason-laptop NetworkManager: info (ath0): device state change: 3 - 4 Dec 12 23:05:24 jason-laptop NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... Dec 12 23:05:24 jason-laptop NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) started... Dec 12 23:05:24 jason-laptop NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... Dec 12 23:05:24 jason-laptop NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) complete. Dec 12 23:05:24 jason-laptop NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) starting... Dec 12 23:05:24 jason-laptop NetworkManager: info (ath0): device state change: 4 - 5 Dec 12 23:05:24 jason-laptop NetworkManager: info Activation (ath0/wireless): access point 'Auto Wireless 9568392' has security, but secrets are required. Dec 12 23:05:24 jason-laptop NetworkManager: info (ath0): device state change: 5 - 6 Dec 12 23:05:24 jason-laptop NetworkManager: info
[Bug 262152] Re: brings up both wired and wireless interfaces; hard to pick just one through the UI
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292054] Re: Some drivers take too long to associate (Was: network-manager 0.7 always asks for WPA passphrase)
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 user is authenticated properly, yet the connection still fails. I know there is no issue with the RADIUS server because with Juniper or Intel's supplicant, authentication takes 1-3 seconds, at most. I have also noticed that after a successful connection, I can reconnect without re-authenticating with the RADIUS server despite the fact that my RADIUS server does not have pre-authentication or session resumption enabled. All three windows supplicants (Juniper Access Client, Intel ProSet Wireless Client, and XP's supplicant) re-authenticate upon a new connection attempt. However, there is absolutely no activity in the FreeRadius debug output when network-manager reconnects. In addition, 75% of connection attempts do not lead to an authentication attempt with the RADIUS server. Of those that do, authentication is always successful, but network-manager doesn't always connect properly. As I mentioned earlier, I have yet to connect once successfully with EAP-TLS. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 290285] Re: Grayed out Connect button when using WPA2 Entreprise+TLS authentication
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 is largely useless for 802.1x. With PEAPv0/MSCHAPv2 I was able to connect about 50% of the time. The rest of the time, the freeradius debug log showed that no attempt was even made to connect. With EAP-TLS, I see the same behavior, but even when the freeradius log shows a successful connection, network manager refuses to connect and doesn't output any errors! I am able to connect 100% of the time with either the Windows XP supplicant or Juniper's Odyssey Access client. This is clearly a network-manager issue. Hopefully, wpa-supplicant will be more reliable. -- Grayed out Connect button when using WPA2 Entreprise+TLS authentication https://bugs.launchpad.net/bugs/290285 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/mailman/listinfo/ubuntu-bugs
[Bug 35836] Re: Hold packages
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303862] [NEW] Pidgin freezes when generating new OTR private key
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 Ubuntu 8.10 LiveCD When I enable the pidgin-otr plugin and attempt to generate a new private key, Pidgin pops up a dialog box telling me that a new private key is being generated. However, key generation never completes and eventually I receive a notification that Pidgin or Generating Private Key is not responding. I have attempted to generate keys for both a XMPP (GMail Account) and an AIM account with the same result, and have repeated the process on both systems multiple times. I have successfully generated keys using the same version of OTR on Windows XP SP3 on the HP dv9500t laptop. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/pidgin Package: pidgin 1:2.5.2-0ubuntu1 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pidgin Uname: Linux 2.6.27-9-generic i686 ** Affects: pidgin-otr Importance: Undecided Status: Invalid ** Affects: pidgin (Ubuntu) Importance: Undecided Status: Invalid ** Tags: apport-bug -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303862] Re: Pidgin freezes when generating new private key
** 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 affects: pidgin-otr Importance: Undecided Status: New ** Changed in: pidgin (Ubuntu) Status: New = Invalid ** Summary changed: - Pidgin freezes when generating new private key + Pidgin freezes when generating new OTR private key -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303862] Re: Pidgin freezes when generating new OTR private key
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303866] [NEW] Pidgin freezes when generating new OTR private key
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 of Ubuntu 8.10 LiveCD When I enable the pidgin-otr plugin and attempt to generate a new private key, Pidgin pops up a dialog box telling me that a new private key is being generated. However, key generation never completes and eventually I receive a notification that Pidgin or Generating Private Key is not responding. I have attempted to generate keys for both a XMPP (GMail Account) and an AIM account with the same result, and have repeated the process on both systems multiple times. I have successfully generated keys using the same version of OTR on Windows XP SP3 on the HP dv9500t laptop. ** Affects: pidgin-otr (Ubuntu) Importance: Undecided Status: New -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303866] Re: Pidgin freezes when generating new OTR private key
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303866] Re: Pidgin freezes when generating new OTR private key
** 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 GB HDD running of Ubuntu 8.10 LiveCD When I enable the pidgin-otr plugin and attempt to generate a new private key, Pidgin pops up a dialog box telling me that a new private key is being generated. However, key generation never completes and eventually I receive a notification that Pidgin or Generating Private Key is not responding. I have attempted to generate keys for both a XMPP (GMail Account) and an AIM account with the same result, and have repeated the process on both systems multiple times. I have successfully generated keys using the same version of OTR on Windows XP SP3 on the HP dv9500t laptop. + + I'm unsure if this is relevant but I did the key creation on the AMD + machine while connected via RealVNC. The connection was made over an + OpenVPN tunnel. However, key creation was done on the live system on my + HP laptop while using the live CD. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303866] Re: Pidgin freezes when generating new OTR private key
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303866] Re: Pidgin freezes when generating new OTR private key
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
