[Bug 1890198] [NEW] bash rcfile option incorrectly still loads /etc/bash.bashrc
Public bug reported: >From the man bash page: The --rcfile file option will force bash to read and execute commands from file instead of /etc/bash.bashrc and ~/.bashrc. However when I add to /etc/bash.bashrc an echo statement at the top like echo Inside bash.bashrc and then execute: /bin/bash --rcfile /tmp/some_test -i where /tmp/some_test has some simple command like an echo statement I still get the echo statement indicating that /etc/bash.bashrc was loaded and run in addition to /tmp/some_test: Inside bash.bashrc you are in /tmp/some_test right now Expected behavior was that since I used the --rcfile option that /etc/bash.bashrc would be ignored and not referenced. Only /tmp/some_test should have been used. I also tried --noprofile with no change as well as leaving out -i. If I use --norc then /etc/bash.bashrc is correctly not used. When I use the --rcfile option I expect /etc/bash.bashrc to not be used. If this is going to be the behavior then the man page for bash needs to be updated to state such. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 15:45:10 2020 InstallationDate: Installed on 2020-08-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.bash.bashrc: 2020-08-03T15:31:02.839478 ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890198 Title: bash rcfile option incorrectly still loads /etc/bash.bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1890198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports
Can confirm for xenial installing the isc-dhcp-client-ddns also works as expected. This package enables ddns ports. When not using this package no random ddns ports as desired. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports
Verified works on trusty as desired. No more extra ports. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471794] Re: Wifi slow on Intel Corporation Centrino Ultimate-N 6300
Firmware changes did not help, but the following doubled my speed from 20mbps to 40mbps (still 50% lower than what I got in Windows 7): vi /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf Change line to wifi.powersave = 2 echo "options iwlwifi 11n_disable=8" | sudo tee /etc/modprobe.d/iwlwifi11n.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471794 Title: Wifi slow on Intel Corporation Centrino Ultimate-N 6300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471794] Re: Wifi slow on Intel Corporation Centrino Ultimate-N 6300
Went to http://www.intel.com/content/www/us/en/support/network-and-i-o/wireless- networking/05511.html and tried version 9.176 with no luck, same slow speeds. loaded firmware version 9.176.4.1 build 15835 op_mode iwldvm sudo mv -i ~rbeede/Downloads/iwlwifi-6000-4.ucode /lib/firmware sudo modprobe -r iwlwifi; sudo modprobe iwlwifi; dmesg | grep firmware sudo service network-manager restart Will try the git repo latest build next. By chance is there a way to load the Windows firmware/drivers instead? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471794 Title: Wifi slow on Intel Corporation Centrino Ultimate-N 6300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471794] Re: Wifi slow on Intel Corporation Centrino Ultimate-N 6300
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/log/iwlwifi-6000-4.ucode Last activity in master branch was 2011-06-03 so not much hope. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471794 Title: Wifi slow on Intel Corporation Centrino Ultimate-N 6300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471794] Re: Wifi slow on Intel Corporation Centrino Ultimate-N 6300
I just tested and have the same issue. I tried the modprobe options idea with no change. Ubuntu 16.10 64-bit. 4.8.0-41-generic #44-Ubuntu SMP My next approach will be to try the firmware blob from Intel's website to see if pushing a newer one in helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471794 Title: Wifi slow on Intel Corporation Centrino Ultimate-N 6300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471794] Re: Wifi slow on Intel Corporation Centrino Ultimate-N 6300
dmesg | grep firmware 337586.320046] iwlwifi :03:00.0: loaded firmware version 9.221.4.1 build 25532 op_mode iwldvm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471794 Title: Wifi slow on Intel Corporation Centrino Ultimate-N 6300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'
Might be your PMTU discovery is being blocked by a firewall somewhere. http://mccltd.net/blog/?p=1577 -- 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/1254085 Title: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1254085/+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 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'
Might be your PMTU discovery is being blocked by a firewall somewhere. http://mccltd.net/blog/?p=1577 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254085 Title: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1254085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206980] Re: [VMWare] Kernel panic in 3.8.0-26-generic and 3.8.0-27-generic
I have retested using the latest stable kernel and can confirm that this error still occurs. Linux okdev1383 3.11.0-19-generic #33-Ubuntu SMP Tue Mar 11 18:48:34 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux root@okdev1383:~# sudo md5deep -r -c -z /dev/ root@okdev1383:~# cat /etc/os-release NAME=Ubuntu VERSION=13.10, Saucy Salamander ID=ubuntu ID_LIKE=debian PRETTY_NAME=Ubuntu 13.10 VERSION_ID=13.10 HOME_URL=http://www.ubuntu.com/; SUPPORT_URL=http://help.ubuntu.com/; BUG_REPORT_URL=http://bugs.launchpad.net/ubuntu/; Apr 8 14:07:12 okdev1383 kernel: [ 161.705864] [ cut here ] Apr 8 14:07:12 okdev1383 kernel: [ 161.706001] kernel BUG at /build/buildd/linux-3.11.0/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:898! Apr 8 14:07:12 okdev1383 kernel: [ 161.706181] invalid opcode: [#1] SMP Apr 8 14:07:12 okdev1383 kernel: [ 161.706380] Modules linked in: coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ppdev vmw_balloon microcode psmouse serio_raw vmwgfx ttm drm parport_pc shpchp vmw_vmci i2c_piix4 mac_hid lp parport mptspi mptscsih e1000 mptbase vmw_pvscsi vmxnet3 floppy Apr 8 14:07:12 okdev1383 kernel: [ 161.708381] CPU: 3 PID: 1563 Comm: md5deep Not tainted 3.11.0-19-generic #33-Ubuntu Apr 8 14:07:12 okdev1383 kernel: [ 161.708562] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 06/22/2012 Apr 8 14:07:12 okdev1383 kernel: [ 161.708778] task: 880812532ee0 ti: 88081003c000 task.ti: 88081003c000 Apr 8 14:07:12 okdev1383 kernel: [ 161.708939] RIP: 0010:[a014cb77] [a014cb77] vmw_master_set+0x147/0x1c0 [vmwgfx] Apr 8 14:07:12 okdev1383 kernel: [ 161.709183] RSP: 0018:88081003dba8 EFLAGS: 00010212 Apr 8 14:07:12 okdev1383 kernel: [ 161.709310] RAX: 88080f828b18 RBX: 88080f80 RCX: 88081003dfd8 Apr 8 14:07:12 okdev1383 kernel: [ 161.709464] RDX: 10d1 RSI: 88080f800740 RDI: 88080f800740 Apr 8 14:07:12 okdev1383 kernel: [ 161.709621] RBP: 88081003dbe0 R08: 0280 R09: 0023 Apr 8 14:07:12 okdev1383 kernel: [ 161.709792] R10: 01e0 R11: R12: 88081260e800 Apr 8 14:07:12 okdev1383 kernel: [ 161.710057] R13: 880812692e40 R14: 88081009fd00 R15: 880811cc9ec0 Apr 8 14:07:12 okdev1383 kernel: [ 161.710321] FS: 7fa713466700() GS:88081f26() knlGS: Apr 8 14:07:12 okdev1383 kernel: [ 161.710703] CS: 0010 DS: ES: CR0: 80050033 Apr 8 14:07:12 okdev1383 kernel: [ 161.710942] CR2: 7fa712462ff8 CR3: 00080f075000 CR4: 000407e0 Apr 8 14:07:12 okdev1383 kernel: [ 161.711273] Stack: Apr 8 14:07:12 okdev1383 kernel: [ 161.711457] 88080f800740 0001a012d00b 88081260e800 88080fe18fe8 Apr 8 14:07:12 okdev1383 kernel: [ 161.712024] 8808100bbf00 88080f676800 88081260e820 88081003dc40 Apr 8 14:07:12 okdev1383 kernel: [ 161.712594] a00e1539 88080fe193d0 88080fe19138 88080fe22000 Apr 8 14:07:12 okdev1383 kernel: [ 161.713166] Call Trace: Apr 8 14:07:12 okdev1383 kernel: [ 161.713372] [a00e1539] drm_open+0x5f9/0x7d0 [drm] Apr 8 14:07:12 okdev1383 kernel: [ 161.713625] [a00e181a] drm_stub_open+0x10a/0x1a0 [drm] Apr 8 14:07:12 okdev1383 kernel: [ 161.713886] [811acac3] chrdev_open+0xa3/0x1b0 Apr 8 14:07:12 okdev1383 kernel: [ 161.714128] [811a5f3b] do_dentry_open+0x1eb/0x280 Apr 8 14:07:12 okdev1383 kernel: [ 161.714370] [811aca20] ? cdev_put+0x30/0x30 Apr 8 14:07:12 okdev1383 kernel: [ 161.714610] [811a6059] vfs_open+0x49/0x50 Apr 8 14:07:12 okdev1383 kernel: [ 161.714848] [811b6003] do_last+0x1c3/0xe50 Apr 8 14:07:12 okdev1383 kernel: [ 161.715086] [8118e7a8] ? kmem_cache_alloc_trace+0x108/0x130 Apr 8 14:07:12 okdev1383 kernel: [ 161.715349] [811b6d51] path_openat+0xc1/0x630 Apr 8 14:07:12 okdev1383 kernel: [ 161.715594] [811b80ca] do_filp_open+0x3a/0x90 Apr 8 14:07:12 okdev1383 kernel: [ 161.715836] [816efa0e] ? _raw_spin_lock+0xe/0x20 Apr 8 14:07:12 okdev1383 kernel: [ 161.716083] [811c4a37] ? __alloc_fd+0xa7/0x130 Apr 8 14:07:12 okdev1383 kernel: [ 161.716320] [811a723c] do_sys_open+0x12c/0x270 Apr 8 14:07:12 okdev1383 kernel: [ 161.716584] [810c4f41] ? SyS_futex+0x71/0x150 Apr 8 14:07:12 okdev1383 kernel: [ 161.716820] [811a739e] SyS_open+0x1e/0x20 Apr 8 14:07:12 okdev1383 kernel: [ 161.717054] [816f869d] system_call_fastpath+0x1a/0x1f Apr 8 14:07:12 okdev1383 kernel: [ 161.717299] Code: 89 75 c8 e8 2c f2 59 e1 8b 93 f0 06 00 00 b8 2d 00 00 00 ef 83 c2 01 30 c0 ef 48 8b 75 c8 48 89 f7 e8 ae f1 59 e1 e9 02 ff ff ff 0f 0b 48 c7 c6 68 bf 15 a0 48 c7 c7 90 97 15 a0 31 c0 e8 72 91 Apr 8
[Bug 954620] Re: SSH StrictModes does not work correctly
Debian has a Debian specific patch (user-group-modes.patch) that changes the behavior compared to the upstream version of OpenSSH. If a user ssh file or directory has a group write bit set and that group has no other members besides the user then sshd now allows the use of the ssh file or directory. I've confirmed this behavior in Ubuntu 12.04. Upstream the change was not accepted for security reasons and that other distros may not have per-user groups like Debian. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314347 https://bugzilla.mindrot.org/show_bug.cgi?id=1060 ** Bug watch added: Debian Bug tracker #314347 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314347 ** Bug watch added: OpenSSH Portable Bugzilla #1060 https://bugzilla.mindrot.org/show_bug.cgi?id=1060 ** Changed in: openssh (Ubuntu) Status: Confirmed = Fix Released -- 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/954620 Title: SSH StrictModes does not work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/954620/+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 954620] Re: SSH StrictModes does not work correctly
Debian has a Debian specific patch (user-group-modes.patch) that changes the behavior compared to the upstream version of OpenSSH. If a user ssh file or directory has a group write bit set and that group has no other members besides the user then sshd now allows the use of the ssh file or directory. I've confirmed this behavior in Ubuntu 12.04. Upstream the change was not accepted for security reasons and that other distros may not have per-user groups like Debian. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314347 https://bugzilla.mindrot.org/show_bug.cgi?id=1060 ** Bug watch added: Debian Bug tracker #314347 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314347 ** Bug watch added: OpenSSH Portable Bugzilla #1060 https://bugzilla.mindrot.org/show_bug.cgi?id=1060 ** Changed in: openssh (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954620 Title: SSH StrictModes does not work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/954620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 424371] Re: Logins to OpenSSH server slow due to UseDNS yes config
I'd propose submitting a request upstream to make the default setting for UseDNS be No. Additionally add comments in the sshd_config and man page: # UseDNS - Determines whether IP Address to Hostname lookup and comparison is performed # Default value is No which avoids login delays when the remote client's DNS cannot be resolved # Value of No implies that the usage of from= in authorized_keys will not support DNS host names but only IP addresses. # Value of Yes supports host names in from= for authorized_keys. Additionally if the remote client's IP address does not match the resolved DNS host name (or could not be reverse lookup resolved) then a warning is logged. # UseDNS Yes -- 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/424371 Title: Logins to OpenSSH server slow due to UseDNS yes config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/424371/+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 424371] Re: Logins to OpenSSH server slow due to UseDNS yes config
I'd propose submitting a request upstream to make the default setting for UseDNS be No. Additionally add comments in the sshd_config and man page: # UseDNS - Determines whether IP Address to Hostname lookup and comparison is performed # Default value is No which avoids login delays when the remote client's DNS cannot be resolved # Value of No implies that the usage of from= in authorized_keys will not support DNS host names but only IP addresses. # Value of Yes supports host names in from= for authorized_keys. Additionally if the remote client's IP address does not match the resolved DNS host name (or could not be reverse lookup resolved) then a warning is logged. # UseDNS Yes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/424371 Title: Logins to OpenSSH server slow due to UseDNS yes config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/424371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206255] Re: Community Help Wiki Apt-Cacher-Server
I log in, but the page still says Immutable Page. I'm giving up on contributing since the community wiki doesn't work for allowing edits. I've attached my one updated revision I attempted. ** Attachment added: Apt-Cacher-Server wiki update.txt https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1206255/+attachment/3990273/+files/Apt-Cacher-Server%20wiki%20update.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206255 Title: Community Help Wiki Apt-Cacher-Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1206255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276796] Re: bash fails to provide FQDN for PS1 with \H
Rebooted. No change to hostname. No DHCP. Problem still exists. Should see a prompt of: [rbe...@okdev1381.example.org:/home/rbeede] $ but instead I only get: [rbeede@okdev1381:/home/rbeede] $ [rbeede@okdev1383:/home/rbeede] $ echo $PS1 [\u@\H:/home/rbeede] $ [rbeede@okdev1383:/home/rbeede] $ cat /etc/os-release NAME=Ubuntu VERSION=13.10, Saucy Salamander The bash man page states: \h The hostname, up to the first ‘.’. \H The hostname. This would imply that the difference between \h and \H is \h is only the hostname \H is the FQDN The source code however shows: case 'h': case 'H': temp = savestring (current_host_name); if (c == 'h' (t = (char *)strchr (temp, '.'))) *t = '\0'; goto add_string; This shows that \h is always the short form of the hostname while \H may be the FQDN. In most cases, however, \H just resolves so the short form hostname and not the FQDN (aka domain name). This is an ambiguity in the bash man page documentation. The bash man page should be updated to say: \h The hostname, up to the first ‘.’. \H The hostname possibly with the parts after the '.' (domain name or FQDN but usually not) ** Changed in: bash (Ubuntu) Status: Invalid = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276796 Title: bash fails to provide FQDN for PS1 with \H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1276796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276796] Re: bash fails to provide FQDN for PS1 with \H
The default install of Ubuntu fills in /etc/hostname with only the host name and not any of the DNS domain name parts. For Ubuntu 13.10 the following is noted: http://manpages.ubuntu.com/manpages/saucy/man1/hostname.1.html /etc/hostname Historically this file was supposed to only contain the hostname and not the full canonical FQDN. Nowadays most software is able to cope with a full FQDN here. This file is read at boot time by the system initialization scripts to set the hostname. For Ubutnu 12.04 the following is noted: http://manpages.ubuntu.com/manpages/precise/man1/hostname.1.html /etc/hostname This file should only contain the hostname and not the full FQDN. So the issue is how /etc/hostname is treated and that bash uses the value provided by how the distro set it up. Ubuntu 13.10 still leaves out the FQDN in /etc/hostname when you install. It'd be useful if the bash man page stated something like: \h The hostname, up to the first ‘.’. \H The hostname. Depending on the distro this may or may not contain the domain name or FQDN. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276796 Title: bash fails to provide FQDN for PS1 with \H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1276796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276796] Re: bash fails to provide FQDN for PS1 with \H
I've submitted a bug report up-stream. A copy of that bug report is attached. To: bug-b...@gnu.org,b...@packages.debian.org Subject: bash fails to provide FQDN for PS1 with \H Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I../bash -I../bash/include -I../bash/lib -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall uname output: Linux okdev1383 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Machine Type: x86_64-pc-linux-gnu Bash Version: 4.2 Patch Level: 45 Release Status: release Description: The bash man page offers two options for the PS1 prompt: \h and \H. \h is suppose to be for the short form of the host name whereas \H can be the longer form. The text reads: \h The hostname, up to the first ‘.’. \H The hostname. The difference would imply that using \H would give you the FQDN version of the host name, but that is not the case. It is distro specific. See https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1276796 for a discussion thread on this issue in Ubuntu. Repeat-By: Tested on Ubuntu 12.04 and 13.10. Set PS1 with \H. Because Ubuntu's installer creates /etc/hostname without the FQDN (as recommended in their man pages) bash never gets a host name other than the short version. Fix: Option 1: use a function other than gethostname when the \H option is supplied. If the system doesn't have a FQDN this may not change anything, but it has a better chance at avoiding disto specific behavior. Option 2: Update the documentation as follows: \h The hostname, up to the first '.'. \H The hostname. May or may not include the domain name or FQDN. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276796 Title: bash fails to provide FQDN for PS1 with \H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1276796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276796] Re: bash fails to provide FQDN for PS1 with \H
There is no DHCP at all. The OS was installed with a static IP configuration during the install setup. I specified the hostname at that time by typing it into the installer prompt. [rbeede@ubuntu13:/home/rbeede] $ cat /etc/hostname okdev1383 [rbeede@ubuntu13:/home/rbeede] $ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 10.9.156.83 netmask 255.255.252.0 network 10.9.156.0 broadcast 10.9.159.255 gateway 10.9.156.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 10.9.0.25 10.10.0.25 dns-search example.org -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276796 Title: bash fails to provide FQDN for PS1 with \H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1276796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276796] Re: bash fails to provide FQDN for PS1 with \H
apport information ** Tags added: apport-collected saucy ** Description changed: When using \H in the PS1 prompt value bash is not displaying the FQDN but instead only the short form hostname. This is the same as \h. Issue has also been noted at http://serverfault.com/questions/296970/bash-prompt-on-ubuntu-fqdn-h-same-as-hostname-h https://answers.launchpad.net/ubuntu/+source/bash/+question/200900 This appears related to /etc/hostname only having the host and not the FQDN. Bash should obtain the \H value from somewhere other than /etc/hostname. + --- + ApportVersion: 2.12.5-0ubuntu2.2 + Architecture: amd64 + DistroRelease: Ubuntu 13.10 + InstallationDate: Installed on 2014-01-16 (20 days ago) + InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 (20131016) + MarkForUpload: True + Package: bash 4.2-5ubuntu3 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 + Tags: saucy + Uname: Linux 3.11.0-15-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1276796/+attachment/3971415/+files/Dependencies.txt ** Changed in: bash (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276796 Title: bash fails to provide FQDN for PS1 with \H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1276796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239205] Re: bashrc: Please add newline to default PS1 bash prompt
** Changed in: bash (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239205 Title: bashrc: Please add newline to default PS1 bash prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1239205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276796] [NEW] bash fails to provide FQDN for PS1 with \H
Public bug reported: When using \H in the PS1 prompt value bash is not displaying the FQDN but instead only the short form hostname. This is the same as \h. Issue has also been noted at http://serverfault.com/questions/296970/bash-prompt-on-ubuntu-fqdn-h-same-as-hostname-h https://answers.launchpad.net/ubuntu/+source/bash/+question/200900 This appears related to /etc/hostname only having the host and not the FQDN. Bash should obtain the \H value from somewhere other than /etc/hostname. ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: shell -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276796 Title: bash fails to provide FQDN for PS1 with \H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1276796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261861] [NEW] man page for sshd contains error about NP and locked accounts
Public bug reported: man sshd This paragraph: Regardless of the authentication type, the account is checked to ensure that it is accessible. An account is not accessible if it is locked, listed in DenyUsers or its group is listed in DenyGroups . The definition of a locked account is system dependant. Some platforms have their own account database (eg AIX) and some modify the passwd field ( ‘*LK*’ on Solaris and UnixWare, ‘*’ on HP-UX, containing ‘Nologin’ on Tru64, a leading ‘*LOCKED*’ on FreeBSD and a leading ‘!’ on most Linuxes). If there is a requirement to disable password authentication for the account while allowing still public-key, then the passwd field should be set to something other than these values (eg ‘NP’ or ‘*NP*’ ). The recommended use of NP or *NP* causes a conflict as If the encrypted password in /etc/passwd is *NP* (without the quotes), the shadow record should be obtained from an NIS+ server. http://man7.org/linux/man-pages/man5/passwd.5.html The upstream OpenSSH package doesn't have this paragraph in the man page so it was something added by Debian/Ubuntu. How an account is locked and what OpenSSH checks for locked also depends on whether UsePAM is yes or no. When yes an account can still be logged into even when the password entry field has a leading ! When no then OpenSSH's behavior is to treat the account as inaccessible if there is a leading ! in the password. This paragraph should be updated to recommend something else. Perhaps no password login allowed as the recommended value. It'd be nice to have this paragraph submitted upstream as well. Reference also: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=219377 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: manpage -- 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/1261861 Title: man page for sshd contains error about NP and locked accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1261861/+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 1261861] [NEW] man page for sshd contains error about NP and locked accounts
Public bug reported: man sshd This paragraph: Regardless of the authentication type, the account is checked to ensure that it is accessible. An account is not accessible if it is locked, listed in DenyUsers or its group is listed in DenyGroups . The definition of a locked account is system dependant. Some platforms have their own account database (eg AIX) and some modify the passwd field ( ‘*LK*’ on Solaris and UnixWare, ‘*’ on HP-UX, containing ‘Nologin’ on Tru64, a leading ‘*LOCKED*’ on FreeBSD and a leading ‘!’ on most Linuxes). If there is a requirement to disable password authentication for the account while allowing still public-key, then the passwd field should be set to something other than these values (eg ‘NP’ or ‘*NP*’ ). The recommended use of NP or *NP* causes a conflict as If the encrypted password in /etc/passwd is *NP* (without the quotes), the shadow record should be obtained from an NIS+ server. http://man7.org/linux/man-pages/man5/passwd.5.html The upstream OpenSSH package doesn't have this paragraph in the man page so it was something added by Debian/Ubuntu. How an account is locked and what OpenSSH checks for locked also depends on whether UsePAM is yes or no. When yes an account can still be logged into even when the password entry field has a leading ! When no then OpenSSH's behavior is to treat the account as inaccessible if there is a leading ! in the password. This paragraph should be updated to recommend something else. Perhaps no password login allowed as the recommended value. It'd be nice to have this paragraph submitted upstream as well. Reference also: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=219377 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: manpage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261861 Title: man page for sshd contains error about NP and locked accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1261861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222301] [NEW] rsyncd.conf man page on numeric ids has incorrect instructions about chroot
Public bug reported: The man page documention (man rsyncd.conf) states: numeric ids Enabling this parameter disables the mapping of users and groups by name for the current daemon module. This prevents the daemon from trying to load any user/group-related files or libraries. This enabling makes the transfer behave as if the client had passed the --numeric-ids command-line option. By default, this parameter is enabled for chroot modules and disabled for non-chroot modules. A chroot-enabled module should not have this parameter enabled unless you’ve taken steps to ensure that the module has the nec‐ essary resources it needs to translate names, and that it is not possible for a user to change those resources. A chroot-enabled module should not have should read A chroot- enabled module should have (removed the word 'not') as that is the default and expected behavior when chroot is enabled. ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Tags: manpage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222301 Title: rsyncd.conf man page on numeric ids has incorrect instructions about chroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1222301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206980] Re: [VMWare] Kernel panic in 3.8.0-26-generic and 3.8.0-27-generic
Ubuntu 12.04: No kernel bug crash on: 3.5.0-36-generic Kernel crash occurs with: linux-image-3.5.0-37-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206980 Title: [VMWare] Kernel panic in 3.8.0-26-generic and 3.8.0-27-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1206980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206980] Re: [VMWare] Kernel panic in 3.8.0-26-generic and 3.8.0-27-generic
Last worked in Ubuntu 12.04.02 LTS 64-bit Server Edition Kernel 3.5.0-34-generic Broken in Ubuntu 12.04.02 LTS 64-bit Server Edition Kernel 3.5.0-37-generic Broken in Ubuntu 12.10 64-bit Server Edition. Kernel 3.5.0-37-generic Broken in Ubuntu 13.04 64-bit Server Edition. Kernel 3.8.0-19-generic Kernel 3.8.0-27-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206980 Title: [VMWare] Kernel panic in 3.8.0-26-generic and 3.8.0-27-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1206980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206980] Re: [VMWare] Kernel panic in 3.8.0-26-generic and 3.8.0-27-generic
Tested with issue on Vmware workstation 9 on windows 7 64-bit host. No vmware tools. Vmware esxi 5.1 with no vmware tools. Physical hardware Biostar a68i-350 deluxe r2.0 motherboard, 8gb ram. All ubuntu 13.04 lts 64-bit server edition. Works fine on all 3 when using ubuntu 12.04 64-bit server edition. Kernel 3.6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206980 Title: [VMWare] Kernel panic in 3.8.0-26-generic and 3.8.0-27-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1206980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206980] Re: Kernel panic in 3.8.0-26-generic and 3.8.0-27-generic
sudo dpkg -i linux- image-3.11.0-031100rc3-generic_3.11.0-031100rc3.201307290035_amd64.deb uname -a Linux okdev1383 3.11.0-031100rc3-generic #201307290035 SMP Mon Jul 29 04:36:40 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Aug 2 14:57:26 okdev1383 kernel: [ 68.538338] [ cut here ] Aug 2 14:57:26 okdev1383 kernel: [ 68.538388] Kernel BUG at a015bac2 [verbose debug info unavailable] Aug 2 14:57:26 okdev1383 kernel: [ 68.538443] invalid opcode: [#1] SMP Aug 2 14:57:26 okdev1383 kernel: [ 68.538514] Modules linked in: vmw_balloon ppdev psmouse serio_raw parport_pc vmwgfx ttm drm vmw_vmci i2c_piix4 shpchp mac_hid ext2 lp parport floppy mptspi mptscsih e1000 mptbase [last unloaded: ipmi_msghandler] Aug 2 14:57:26 okdev1383 kernel: [ 68.538984] CPU: 3 PID: 1538 Comm: md5deep Not tainted 3.11.0-031100rc3-generic #201307290035 Aug 2 14:57:26 okdev1383 kernel: [ 68.539047] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 06/22/2012 Aug 2 14:57:26 okdev1383 kernel: [ 68.539123] task: 880225cb8000 ti: 880231212000 task.ti: 880231212000 Aug 2 14:57:26 okdev1383 kernel: [ 68.539180] RIP: 0010:[a015bac2] [a015bac2] vmw_master_set+0x162/0x1d0 [vmwgfx] Aug 2 14:57:26 okdev1383 kernel: [ 68.539268] RSP: 0018:880231213ac8 EFLAGS: 00010216 Aug 2 14:57:26 okdev1383 kernel: [ 68.539313] RAX: 880228da8b18 RBX: 880228d8 RCX: Aug 2 14:57:26 okdev1383 kernel: [ 68.539423] RDX: 10d1 RSI: 880225cb8000 RDI: 880228d80740 Aug 2 14:57:26 okdev1383 kernel: [ 68.539478] RBP: 880231213b08 R08: R09: Aug 2 14:57:26 okdev1383 kernel: [ 68.539533] R10: 0001 R11: 0001 R12: 88023157a900 Aug 2 14:57:26 okdev1383 kernel: [ 68.539588] R13: 880228d80740 R14: 8802303db400 R15: 8802327ef900 Aug 2 14:57:26 okdev1383 kernel: [ 68.539644] FS: 7f0ff92e3700() GS:88023fd8() knlGS: Aug 2 14:57:26 okdev1383 kernel: [ 68.539716] CS: 0010 DS: ES: CR0: 80050033 Aug 2 14:57:26 okdev1383 kernel: [ 68.539773] CR2: 7f0ff9e679e0 CR3: 0002319a1000 CR4: 000407e0 Aug 2 14:57:26 okdev1383 kernel: [ 68.539865] Stack: Aug 2 14:57:26 okdev1383 kernel: [ 68.539904] 01ff880231213ae8 880230340e60 88023346d820 88023346d800 Aug 2 14:57:26 okdev1383 kernel: [ 68.540043] 8802303db420 88023094f500 88023346d820 8802303db400 Aug 2 14:57:26 okdev1383 kernel: [ 68.540183] 880231213b58 a00d5719 880231213b68 880230d96000 Aug 2 14:57:26 okdev1383 kernel: [ 68.540322] Call Trace: Aug 2 14:57:26 okdev1383 kernel: [ 68.540369] [a00d5719] drm_open_helper+0x379/0x4a0 [drm] Aug 2 14:57:26 okdev1383 kernel: [ 68.540434] [a00d5934] drm_open+0xf4/0x1c0 [drm] Aug 2 14:57:26 okdev1383 kernel: [ 68.540494] [a00d5b12] drm_stub_open+0x112/0x1b0 [drm] Aug 2 14:57:26 okdev1383 kernel: [ 68.540563] [811b69f2] chrdev_open+0xb2/0x1a0 Aug 2 14:57:26 okdev1383 kernel: [ 68.540624] [811b6940] ? cdev_put+0x30/0x30 Aug 2 14:57:26 okdev1383 kernel: [ 68.540680] [811af866] do_dentry_open+0x226/0x2a0 Aug 2 14:57:26 okdev1383 kernel: [ 68.540739] [811af915] finish_open+0x35/0x50 Aug 2 14:57:26 okdev1383 kernel: [ 68.540795] [811c138e] do_last+0x48e/0x770 Aug 2 14:57:26 okdev1383 kernel: [ 68.540850] [811c1734] path_openat+0xc4/0x4f0 Aug 2 14:57:26 okdev1383 kernel: [ 68.540906] [811c1fb3] do_filp_open+0x43/0xa0 Aug 2 14:57:26 okdev1383 kernel: [ 68.540964] [811ceaf5] ? __alloc_fd+0xd5/0x160 Aug 2 14:57:26 okdev1383 kernel: [ 68.541020] [811b0faf] do_sys_open+0x12f/0x220 Aug 2 14:57:26 okdev1383 kernel: [ 68.541079] [810213ab] ? syscall_trace_leave+0x8b/0x120 Aug 2 14:57:26 okdev1383 kernel: [ 68.541140] [811b10be] SyS_open+0x1e/0x20 Aug 2 14:57:26 okdev1383 kernel: [ 68.541195] [817331af] tracesys+0xe1/0xe6 Aug 2 14:57:26 okdev1383 kernel: [ 68.541248] Code: d5 e0 ff ff 4c 89 ef e8 ad a6 5c e1 8b 93 f0 06 00 00 b8 2d 00 00 00 ef 83 c2 01 30 c0 ef 4c 89 ef e8 b3 a5 5c e1 e9 f6 fe ff ff 0f 0b 48 c7 c6 10 bf 16 a0 48 c7 c7 00 98 16 a0 31 c0 e8 87 e9 Aug 2 14:57:26 okdev1383 kernel: [ 68.542429] RIP [a015bac2] vmw_master_set+0x162/0x1d0 [vmwgfx] Aug 2 14:57:26 okdev1383 kernel: [ 68.542512] RSP 880231213ac8 Aug 2 14:57:26 okdev1383 kernel: [ 68.542571] ---[ end trace 578a4cc2159fbf78 ]--- ** Tags added: kernel-bug-exists-upstream-v3.11 ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.
[Bug 1206980] Re: Kernel panic in 3.8.0-26-generic and 3.8.0-27-generic
sudo dpkg -i linux- image-3.9.0-030900-generic_3.9.0-030900.201304291257_amd64.deb [rbeede@ubuntu13:/home/rbeede] $ uname -a Linux ubuntu13 3.9.0-030900-generic #201304291257 SMP Mon Apr 29 16:58:15 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux sudo md5deep -r -c -z /dev/ Same kernel panic: Aug 1 14:16:31 okdev1383 kernel: [ 63.740605] [ cut here ] Aug 1 14:16:31 okdev1383 kernel: [ 63.740701] Kernel BUG at a01299f2 [verbose debug info unavailable] Aug 1 14:16:31 okdev1383 kernel: [ 63.740805] invalid opcode: [#1] SMP Aug 1 14:16:31 okdev1383 kernel: [ 63.740938] Modules linked in: coretemp ghash_clmulni_intel aesni_intel aes_x86_64 xts lrw gf128mul ablk_helper cryptd ppdev vmw_balloon psmouse microcode serio_raw parport_pc i2c_piix4 shpchp vmwgfx ttm drm ext2 mac_hid lp parport floppy mptspi mptscsih e1000 mptbase [last unloaded: ipmi_msghandler] Aug 1 14:16:31 okdev1383 kernel: [ 63.742181] CPU 2 Aug 1 14:16:31 okdev1383 kernel: [ 63.742237] Pid: 1576, comm: md5deep Not tainted 3.9.0-030900-generic #201304291257 VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform Aug 1 14:16:31 okdev1383 kernel: [ 63.742445] RIP: 0010:[a01299f2] [a01299f2] vmw_master_set+0x162/0x1d0 [vmwgfx] Aug 1 14:16:31 okdev1383 kernel: [ 63.742618] RSP: 0018:880228b67ae8 EFLAGS: 00010216 Aug 1 14:16:31 okdev1383 kernel: [ 63.742704] RAX: 880229be8ab8 RBX: 880229bc RCX: Aug 1 14:16:31 okdev1383 kernel: [ 63.742809] RDX: 10d1 RSI: 88022999dd40 RDI: 880229bc06f8 Aug 1 14:16:31 okdev1383 kernel: [ 63.742915] RBP: 880228b67b28 R08: 880228b66000 R09: 0001 Aug 1 14:16:31 okdev1383 kernel: [ 63.743021] R10: R11: R12: 880231026900 Aug 1 14:16:31 okdev1383 kernel: [ 63.743126] R13: 880229bc06f8 R14: 88023074fc00 R15: 880230ed1cc0 Aug 1 14:16:31 okdev1383 kernel: [ 63.743234] FS: 7fc3bdf5f700() GS:88023fd0() knlGS: Aug 1 14:16:31 okdev1383 kernel: [ 63.743350] CS: 0010 DS: ES: CR0: 80050033 Aug 1 14:16:31 okdev1383 kernel: [ 63.743442] CR2: 7fc3bdf5df50 CR3: 00023121d000 CR4: 000407e0 Aug 1 14:16:31 okdev1383 kernel: [ 63.743629] DR0: DR1: DR2: Aug 1 14:16:31 okdev1383 kernel: [ 63.743781] DR3: DR6: 0ff0 DR7: 0400 Aug 1 14:16:31 okdev1383 kernel: [ 63.743910] Process md5deep (pid: 1576, threadinfo 880228b66000, task 88022999dd40) Aug 1 14:16:31 okdev1383 kernel: [ 63.744070] Stack: Aug 1 14:16:31 okdev1383 kernel: [ 63.744141] 01ff880228b67b08 880228a5bb40 88023074fc00 880230a15000 Aug 1 14:16:31 okdev1383 kernel: [ 63.744411] 880230f29000 88023074fc20 88023074fc00 880230a15020 Aug 1 14:16:31 okdev1383 kernel: [ 63.744692] 880228b67b78 a0088779 880228b67b68 8802305dd000 Aug 1 14:16:31 okdev1383 kernel: [ 63.744964] Call Trace: Aug 1 14:16:31 okdev1383 kernel: [ 63.745058] [a0088779] drm_open_helper+0x349/0x410 [drm] Aug 1 14:16:31 okdev1383 kernel: [ 63.745184] [a0088934] drm_open+0xf4/0x1c0 [drm] Aug 1 14:16:31 okdev1383 kernel: [ 63.745301] [a0088b12] drm_stub_open+0x112/0x1b0 [drm] Aug 1 14:16:31 okdev1383 kernel: [ 63.745420] [811a2eb2] chrdev_open+0xb2/0x1a0 Aug 1 14:16:31 okdev1383 kernel: [ 63.745528] [811a2e00] ? cdev_put+0x30/0x30 Aug 1 14:16:31 okdev1383 kernel: [ 63.745636] [8119c596] do_dentry_open+0x226/0x2a0 Aug 1 14:16:31 okdev1383 kernel: [ 63.745748] [8119c645] finish_open+0x35/0x50 Aug 1 14:16:31 okdev1383 kernel: [ 63.745855] [811ad4a9] do_last+0x509/0x800 Aug 1 14:16:31 okdev1383 kernel: [ 63.745961] [811ad858] path_openat+0xb8/0x4c0 Aug 1 14:16:31 okdev1383 kernel: [ 63.746069] [811ae062] do_filp_open+0x42/0xa0 Aug 1 14:16:31 okdev1383 kernel: [ 63.746180] [811bb455] ? __alloc_fd+0xe5/0x170 Aug 1 14:16:31 okdev1383 kernel: [ 63.746289] [8119dbfe] do_sys_open+0xfe/0x1e0 Aug 1 14:16:31 okdev1383 kernel: [ 63.746397] [8119dd01] sys_open+0x21/0x30 Aug 1 14:16:31 okdev1383 kernel: [ 63.746504] [8170d4dd] system_call_fastpath+0x1a/0x1f Aug 1 14:16:31 okdev1383 kernel: [ 63.746623] Code: 85 e0 ff ff 4c 89 ef e8 dd 7e 5d e1 8b 93 a8 06 00 00 b8 2d 00 00 00 ef 83 c2 01 30 c0 ef 4c 89 ef e8 63 7e 5d e1 e9 f6 fe ff ff 0f 0b 48 c7 c6 a0 9e 13 a0 48 c7 c7 00 78 13 a0 31 c0 e8 57 3b Aug 1 14:16:31 okdev1383 kernel: [ 63.748880] RIP [a01299f2] vmw_master_set+0x162/0x1d0 [vmwgfx] Aug 1 14:16:31 okdev1383 kernel: [ 63.749041] RSP 880228b67ae8 Aug 1 14:16:31 okdev1383 kernel: [ 63.749200] ---[ end trace cd20706a0673f129 ]---
[Bug 1206980] [NEW] Kernel panic in 3.8.0-26-generic and 3.8.0-27-generic
Public bug reported: Reproducable 100% of the time. sudo md5deep -r -c -z /dev/ Other intensive I/O commands such as fsck /dev/Some3TBDrive also cause the panic. /var/log/kern.log shows stack trace. Ubuntu 13.04 64-bit (amd64) Server Edition Tested running under VMWare ESXi 5, VMWare Workstation 9, and on physical machine. Possibly related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1203933 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-26-generic 3.8.0-26.38 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Jul 16 19:29 seq crw-rw---T 1 root audio 116, 33 Jul 16 19:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Wed Jul 31 15:49:15 2013 HibernationDevice: RESUME=UUID=94c0600c-fa67-431a-a43c-ed68d6b13af7 InstallationDate: Installed on 2013-07-16 (14 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: VMware, Inc. VMware Virtual Platform MarkForUpload: True PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-26-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-3.8.0-26-generic N/A linux-backports-modules-3.8.0-26-generic N/A linux-firmware1.106 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2012 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd06/22/2012:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206980 Title: Kernel panic in 3.8.0-26-generic and 3.8.0-27-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1206980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203933] Re: Kernel panic in kernel version 3.8.0-26.38-generic 3.8.13.2
I am encountering this issue as well. Attached is a screenshot. My setup: Ubuntu 13.04 LTS 64-bit Server Edition VMWare Workstation 9 on a Windows 7 64-bit Enterprise Edition host No floppy drive in the VM settings, but I didn't modify the default BIOS either. One good tool to quickly reproduce the issue: sudo apt-get install md5deep sudo md5deep -c -r -z / You get a kernel panic when it starts to hit items in /dev and /vmlinuz.old ** Attachment added: screenshots.tar https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1203933/+attachment/3754870/+files/screenshots.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203933 Title: Kernel panic in kernel version 3.8.0-26.38-generic 3.8.13.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1203933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203933] Re: Kernel panic in kernel version 3.8.0-26.38-generic 3.8.13.2
kern.log from crash with 3.8.0-27-generic ** Attachment added: kern.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1203933/+attachment/3754957/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203933 Title: Kernel panic in kernel version 3.8.0-26.38-generic 3.8.13.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1203933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203933] Re: Kernel panic in kernel version 3.8.0-26.38-generic 3.8.13.2
Pulling the latest updates to 3.8.0-27 results in the same crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203933 Title: Kernel panic in kernel version 3.8.0-26.38-generic 3.8.13.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1203933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203933] Re: Kernel panic in kernel version 3.8.0-26.38-generic 3.8.13.2
My system seems to crash whether doing the md5deep / probe or when doing a large amount of I/O on other mount points. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203933 Title: Kernel panic in kernel version 3.8.0-26.38-generic 3.8.13.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1203933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203933] Re: Kernel panic in kernel version 3.8.0-26.38-generic 3.8.13.2
I am able to reproduce this issue 100% of the time. A quick way to trigger the kernel panic is sudo md5deep -r -c -z /dev ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203933 Title: Kernel panic in kernel version 3.8.0-26.38-generic 3.8.13.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1203933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206255] [NEW] Community Help Wiki Apt-Cacher-Server
Public bug reported: https://help.ubuntu.com/community/Apt-Cacher-Server The page is out-of-date. I tried Edit mode, but it's marked as Immutable Page The line: sudo apt-get install apt-cacher apache2 is out of date as you don't need apache2. I tested the process with Ubuntu 12.04 LTS. ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: New ** Tags: doc wiki -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206255 Title: Community Help Wiki Apt-Cacher-Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1206255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1195009] [NEW] sftp should include seconds in directory listings
Public bug reported: Directory listings from the ls -l command in sftp are only granular for mtime to the minute and not the second. When using sftp clients that support uploading only changed files based on mtime this causes the same file to appear different. sftp should provide the complete timestamp and not just hh:mm. [rbeede@ubuntu:/home/rbeede] $ ssh -V OpenSSH_6.1p1 Debian-4, OpenSSL 1.0.1c 10 May 2012 [rbeede@ubuntu:/home/rbeede] $ uname -a Linux ubuntu 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux This may belong to openssh-server or openssh-client. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: sftp -- 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/1195009 Title: sftp should include seconds in directory listings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1195009/+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 1195009] [NEW] sftp should include seconds in directory listings
Public bug reported: Directory listings from the ls -l command in sftp are only granular for mtime to the minute and not the second. When using sftp clients that support uploading only changed files based on mtime this causes the same file to appear different. sftp should provide the complete timestamp and not just hh:mm. [rbeede@ubuntu:/home/rbeede] $ ssh -V OpenSSH_6.1p1 Debian-4, OpenSSL 1.0.1c 10 May 2012 [rbeede@ubuntu:/home/rbeede] $ uname -a Linux ubuntu 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux This may belong to openssh-server or openssh-client. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: sftp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1195009 Title: sftp should include seconds in directory listings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1195009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1188827] Re: User option (-u or --user) is ignored
Yes, that was the first one I tried. I thought the Ubuntu package may have been compiled without the option support so I tried a recompile to ensure it was enabled. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tftp-hpa in Ubuntu. https://bugs.launchpad.net/bugs/1188827 Title: User option (-u or --user) is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1188827/+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 1188827] Re: User option (-u or --user) is ignored
Yes, that was the first one I tried. I thought the Ubuntu package may have been compiled without the option support so I tried a recompile to ensure it was enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1188827 Title: User option (-u or --user) is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1188827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1188827] [NEW] User option (-u or --user) is ignored
*** This bug is a security vulnerability *** Public security bug reported: Tested in Ubuntu 12.04 and 13.04. The --user, -u, or /etc/default/tftpd-hpa TFTP_USERNAME=tftp options are ignored when running the tftpd-hpa service. I pulled the source with wget https://www.kernel.org/pub/software/network/tftp/tftp-hpa/tftp- hpa-5.2.tar.xz and compiled. Ran with /root/tftp-hpa-5.2/tftpd/tftpd --listen -u nobody --address 0.0.0.0:69 --secure /var Result was root@ubuntu:/var/log# ps -ef | grep tftpd root 7955 1 0 13:55 ?00:00:00 /root/tftp-hpa-5.2/tftpd/tftpd --listen -u nobody --address 0.0.0.0:69 --secure /var I expected the process uid to be that of nobody. Killing the process and trying again I also looked at /proc to see what it thought about it: root@ubuntu:/var/log# cat /proc/8037/task/8037/status Name: tftpd State: S (sleeping) Tgid: 8037 Pid:8037 PPid: 1 TracerPid: 0 Uid:0 0 0 0 Gid:0 0 0 0 FDSize: 64 Groups: 0 VmPeak:13048 kB VmSize:13048 kB VmLck: 0 kB VmPin: 0 kB VmHWM: 140 kB VmRSS: 140 kB VmData: 444 kB VmStk: 136 kB VmExe:32 kB VmLib: 2140 kB VmPTE:44 kB VmSwap:0 kB Threads:1 SigQ: 0/31432 SigPnd: ShdPnd: SigBlk: SigIgn: 0001 SigCgt: 4003 CapInh: CapPrm: 001f CapEff: 001f CapBnd: 001f Seccomp:0 Cpus_allowed: , Cpus_allowed_list: 0-63 Mems_allowed: ,0001 Mems_allowed_list: 0 voluntary_ctxt_switches:1 nonvoluntary_ctxt_switches: 0 ** Affects: tftp-hpa (Ubuntu) Importance: Undecided Status: New ** Tags: tftp ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tftp-hpa in Ubuntu. https://bugs.launchpad.net/bugs/1188827 Title: User option (-u or --user) is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1188827/+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 1188827] [NEW] User option (-u or --user) is ignored
*** This bug is a security vulnerability *** Public security bug reported: Tested in Ubuntu 12.04 and 13.04. The --user, -u, or /etc/default/tftpd-hpa TFTP_USERNAME=tftp options are ignored when running the tftpd-hpa service. I pulled the source with wget https://www.kernel.org/pub/software/network/tftp/tftp-hpa/tftp- hpa-5.2.tar.xz and compiled. Ran with /root/tftp-hpa-5.2/tftpd/tftpd --listen -u nobody --address 0.0.0.0:69 --secure /var Result was root@ubuntu:/var/log# ps -ef | grep tftpd root 7955 1 0 13:55 ?00:00:00 /root/tftp-hpa-5.2/tftpd/tftpd --listen -u nobody --address 0.0.0.0:69 --secure /var I expected the process uid to be that of nobody. Killing the process and trying again I also looked at /proc to see what it thought about it: root@ubuntu:/var/log# cat /proc/8037/task/8037/status Name: tftpd State: S (sleeping) Tgid: 8037 Pid:8037 PPid: 1 TracerPid: 0 Uid:0 0 0 0 Gid:0 0 0 0 FDSize: 64 Groups: 0 VmPeak:13048 kB VmSize:13048 kB VmLck: 0 kB VmPin: 0 kB VmHWM: 140 kB VmRSS: 140 kB VmData: 444 kB VmStk: 136 kB VmExe:32 kB VmLib: 2140 kB VmPTE:44 kB VmSwap:0 kB Threads:1 SigQ: 0/31432 SigPnd: ShdPnd: SigBlk: SigIgn: 0001 SigCgt: 4003 CapInh: CapPrm: 001f CapEff: 001f CapBnd: 001f Seccomp:0 Cpus_allowed: , Cpus_allowed_list: 0-63 Mems_allowed: ,0001 Mems_allowed_list: 0 voluntary_ctxt_switches:1 nonvoluntary_ctxt_switches: 0 ** Affects: tftp-hpa (Ubuntu) Importance: Undecided Status: New ** Tags: tftp ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1188827 Title: User option (-u or --user) is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1188827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180553] [NEW] adduser --disabled-login still allows for SSH RSA keys login
Public bug reported: adduser --disabled-login --gecos --shell /bin/bash testuser I am not prompted for a password as expect, but if I create a .ssh/authorized_keys file (say it was in my /etc/skel/) in the home directory of the new user I can login as that user using SSH keys. The --disabled-password is meant for that. I should not be able to login at all. Ubuntu 13.04 64-bit Server edition. The fix would be to also set the account to be immediately expired in the same manner as doing usermod --expiredate 1 does in addition to marking the password disabled. If this fix cannot be done then the man page for adduser should be updated to warn about this. ** Affects: adduser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180553 Title: adduser --disabled-login still allows for SSH RSA keys login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1180553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180553] Re: adduser --disabled-login still allows for SSH RSA keys login
Corrected package ** Package changed: shadow (Ubuntu) = adduser (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180553 Title: adduser --disabled-login still allows for SSH RSA keys login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1180553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports
I found the cause from a helpful thread at http://forums.debian.net/viewtopic.php?f=10t=95273 The NSUPDATE dns functionality in dhclient automatically causes it to listen on two random UDP ports. This could pose a security issue since the client will accept packets on these ports. The current fix is to modify the source code to disable the functionality as per the thread mentioned above. Doing so stops it from listening on the random ports. I have filed a bug with ISC, bug number [ISC-Bugs #33377] asking for documentation about this feature (none exists currently about why the ports are opened) as well as a run-time configuration option with a default value to disable it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176046] [NEW] isc-dhcp dhclient listens on extra random ports
Public bug reported: Ubuntu 13.04 Server 64-bit. Fresh install. Only one network adapter. dhclient process is listening on two randomly chosen udp ports in addition to the usual port 68. This appears to be a bug in the discovery code for probing information on interfaces in the system. Initial research of the code also suggested omapi, but adding omapi port to /etc/dhcp/dhclient.conf only opened a forth port with the two random udp ports still enabled. Version of included distro dhclient was 4.2.4. I also tested with the latest isc-dhclient-4.2.5-P1 and got the same results. Debian has the same bug: http://forums.debian.net/viewtopic.php?f=10t=95273p=495605#p495605 One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown. Example netstat -lnp output: udp0 0 0.0.0.0:21117 0.0.0.0:* 2659/dhclient udp0 0 0.0.0.0:68 0.0.0.0:* 2659/dhclient udp6 0 0 :::45664:::* 2659/dhclient ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986835] Re: Cursor jumps to left side of screen when moving from right to left monitors
I have this problem whether auto-hide is on or off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986835 Title: Cursor jumps to left side of screen when moving from right to left monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/986835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239069] Re: Can not delete new user which use adduser
I have a similar issue and it seems to be related to duplicate uid in /etc/passwd for the affected account. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/239069 Title: Can not delete new user which use adduser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/239069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 285013] Re: nfs shares are not automounted anymore in intrepid
Modifying /etc/network/interfaces doesn't work for me. If _netdev was supported by nfs4 this probably wouldn't be an issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/285013 Title: nfs shares are not automounted anymore in intrepid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 285013] Re: nfs shares are not automounted anymore in intrepid
A manual work around with the rc script helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/285013 Title: nfs shares are not automounted anymore in intrepid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
