[Bug 1003326] [NEW] IPv6 hosts incorrectly reported down
Public bug reported: When trying to scan an IPv6 host I got this error: Starting Nmap 5.21 ( http://nmap.org ) at 2012-05-23 11:34 CEST Note: Host seems down. If it is really up, but blocking our ping probes, try -PN Nmap done: 1 IP address (0 hosts up) scanned in 3.26 seconds The host is responding to pings, but nmap never send any pings to the host. Nmap only send a few TCP packets to the host, however this particular host did not have a TCP stack and does not reply to TCP packets. I don't know if this bug is fixed by upstream updates, but since nmap 6 has been released and has lots of IPv6 updates it is not unlikely that it has been fixed upstream. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nmap 5.21-1.1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Wed May 23 11:50:16 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nmap UpgradeStatus: Upgraded to precise on 2012-05-08 (14 days ago) ** Affects: nmap (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nmap in Ubuntu. https://bugs.launchpad.net/bugs/1003326 Title: IPv6 hosts incorrectly reported down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nmap/+bug/1003326/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1003326] Re: IPv6 hosts incorrectly reported down
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nmap in Ubuntu. https://bugs.launchpad.net/bugs/1003326 Title: IPv6 hosts incorrectly reported down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nmap/+bug/1003326/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 739297] Re: Please update nmap: stable upstream version is 5.52
What does "Fix Released" mean? Ubutnu 12.04 still only has Nmap 5.21. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nmap in Ubuntu. https://bugs.launchpad.net/bugs/739297 Title: Please update nmap: stable upstream version is 5.52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nmap/+bug/739297/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 967311] Re: Incorrect 6to4 handling
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to whois in Ubuntu. https://bugs.launchpad.net/bugs/967311 Title: Incorrect 6to4 handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whois/+bug/967311/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 967311] [NEW] Incorrect 6to4 handling
Public bug reported: If I run "whois 2002:5634::", it tells me: Querying for the IPv4 endpoint 0.0.0.0 of a 6to4 IPv6 address. However that is not the correct endpoint for the address 2002:5634:: If OTOH I run "2002:5634:0::", it tells me: Querying for the IPv4 endpoint 86.52.0.0 of a 6to4 IPv6 address. Since 2002:5634:: and 2002:5634:0:: are different notations for the same IPv6 address, you'd expect whois to handle both the same, and extract the IPv4 address 86.52.0.0. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: whois 5.0.0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21 Uname: Linux 2.6.32-37-generic i686 Architecture: i386 Date: Wed Mar 28 19:02:46 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) ProcEnviron: PATH=(custom, user) LANG=en_DK.utf8 SHELL=/bin/bash SourcePackage: whois ** Affects: whois (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to whois in Ubuntu. https://bugs.launchpad.net/bugs/967311 Title: Incorrect 6to4 handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whois/+bug/967311/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 989984] [NEW] Lookup for 101/8 reports Please upgrade this program.
Public bug reported: whois lookups for any IP in the 101.0.0.0/8 range results in an error message saying "Please upgrade this program.", but there is no update for whois. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: whois 5.0.0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21 Uname: Linux 2.6.32-37-generic i686 Architecture: i386 Date: Fri Apr 27 20:05:03 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) ProcEnviron: PATH=(custom, user) LANG=en_DK.utf8 SHELL=/bin/bash SourcePackage: whois ** Affects: whois (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to whois in Ubuntu. https://bugs.launchpad.net/bugs/989984 Title: Lookup for 101/8 reports Please upgrade this program. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whois/+bug/989984/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 989984] Re: Lookup for 101/8 reports Please upgrade this program.
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to whois in Ubuntu. https://bugs.launchpad.net/bugs/989984 Title: Lookup for 101/8 reports Please upgrade this program. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whois/+bug/989984/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 989984] Re: Lookup for 101/8 reports Please upgrade this program.
I'm still a bit new to Ubuntu. I'm more experienced with rpm based systems. I haven't figured out the exact steps I need to do in order to build a patched version of an ubuntu package, but if you could point me at instructions that shows me how to build and install a modified deb package, I'll have a patch ready for you in "no time". -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to whois in Ubuntu. https://bugs.launchpad.net/bugs/989984 Title: Lookup for 101/8 reports Please upgrade this program. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whois/+bug/989984/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 815489] [NEW] ssh client should not ask for key passphrase when an unprotected key is available
Public bug reported: When connecting to an ssh server, that will accept two different keys for authentication, and both of them are present in the .ssh directory on the client, the client will prefer to ask the user for a passphrase for a protected keyfile instead of using an unprotected keyfile. Asking for a passphrase when none is needed is bad for user experience and for productivity. More specifically what happens is that the ssh client will contact gnome-keyring-daemon to use a protected keyfile before it looks into the .ssh directory itself. This decision in the ssh client makes more sense with the stock ssh- agent, where a key provided by the agent is unlocked by default. With gnome-keyring-daemon, by default the agent will list all the keys that are currently protected and none of those, that are unprotected. A more appropriate order to test the keys in is: 1. Unprotected keys from ~/.ssh 2. Keys provided by the agent 3. Protected keys from ~/.ssh This will give a reasonable behavior even without knowing if keys provided by the agent are protected or not. The problem is not specific to gnome-keyring-daemon, the same problem is present when using "ssh-add -c" with a standard ssh-agent. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: openssh-client 1:5.3p1-3ubuntu7 ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-generic i686 Architecture: i386 Date: Sun Jul 24 18:54:44 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) ProcEnviron: LANG=en_DK.utf8 SHELL=/bin/bash SourcePackage: openssh ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/815489 Title: ssh client should not ask for key passphrase when an unprotected key is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/815489/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 815489] Re: ssh client should not ask for key passphrase when an unprotected key is available
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/815489 Title: ssh client should not ask for key passphrase when an unprotected key is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/815489/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs