[Bug 1954639] Re: CVE-2020-4044: Backport for 20.04-LTS
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-4044 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954639 Title: CVE-2020-4044: Backport for 20.04-LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1954639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954639] [NEW] CVE-2020-4044: Backport for 20.04-LTS
Public bug reported: Hello, We are using Ubuntu 20.04 LTS on our Servers with RDP access through XRDP. We found out via vulnurability scanning that the CVE CVE-2020-4044 is still open in the LTS version. In Debian the bug is already fixed in all codestreams: https://security- tracker.debian.org/tracker/CVE-2020-4044 Is there any news when or if the bugfix will be release to the LTS release 20.04 - I can see the same package version is already updated for 21.04. lsb-release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 apt show xrdp Package: xrdp Version: 0.9.12-1 Thank you very much for the great work on Ubuntu and for any information regarding this issue. ** Affects: xrdp (Ubuntu) Importance: Undecided Status: Confirmed ** Description changed: Hello, We are using Ubuntu 20.04 LTS on our Servers with RDP access through XRDP. We found out via vulnurability scanning that the CVE CVE-2020-4044 is still open in the LTS version. In Debian the bug is already fixed in all codestreams: https://security- tracker.debian.org/tracker/CVE-2020-4044 - Is there any news when or if the bugfix will be backported to the LTS - release 20.04. + Is there any news when or if the bugfix will be release to the LTS + release 20.04 - I can see the fix is already in this project. lsb-release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 apt show xrdp Package: xrdp Version: 0.9.12-1 Thank you very much for the great work on Ubuntu and for any information regarding this issue. ** Description changed: Hello, We are using Ubuntu 20.04 LTS on our Servers with RDP access through XRDP. We found out via vulnurability scanning that the CVE CVE-2020-4044 is still open in the LTS version. In Debian the bug is already fixed in all codestreams: https://security- tracker.debian.org/tracker/CVE-2020-4044 Is there any news when or if the bugfix will be release to the LTS - release 20.04 - I can see the fix is already in this project. + release 20.04 - I can see the fix is already in this project ini version + 0.9.12-1.1. lsb-release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 apt show xrdp Package: xrdp Version: 0.9.12-1 Thank you very much for the great work on Ubuntu and for any information regarding this issue. ** Description changed: Hello, We are using Ubuntu 20.04 LTS on our Servers with RDP access through XRDP. We found out via vulnurability scanning that the CVE CVE-2020-4044 is still open in the LTS version. In Debian the bug is already fixed in all codestreams: https://security- tracker.debian.org/tracker/CVE-2020-4044 Is there any news when or if the bugfix will be release to the LTS - release 20.04 - I can see the fix is already in this project ini version - 0.9.12-1.1. + release 20.04 - I can see the same package version is already updated + for 21.04. lsb-release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 apt show xrdp Package: xrdp Version: 0.9.12-1 Thank you very much for the great work on Ubuntu and for any information regarding this issue. ** Summary changed: - CVE-2020-4044 + CVE-2020-4044: Backport for 20.04-LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954639 Title: CVE-2020-4044: Backport for 20.04-LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1954639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
Just as an update - I can confirm that disabling works with 20.10 (which uses an up-to-date enough version of open-vm-tools). I still didn't attach the network automatically, but I have the suspicion that this is because of the ansible collection, because after the machine is booted I can attach the network using govc using: govc device.connect -vm=myvm ethernet-0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
This seems to work to run the user-data part of cloud-init, so that's great. However the problem seems to be that the Customization script must now include the network configuration as well - so either I have to find a way to generate the script dynamically or maybe find a way that *all* customization is done through cloud-init. Is there a way to just completely turn off any customization? I tried to use: vmware-toolbox-cmd config set deployPkg enable-custom-scripts false vmware-toolbox-cmd config set deployPkg enable-customization false But it seems that even with those 2 commands it is still trying to run the customizations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
Exactly so our current workflow looks like this: - We deploy the ova (not using any cloud-init at all - it never gets powered on) - We mark this machine directly as a template for reuse Now in our playbooks we use this template to deploy new machines. For every machine we generate the cloud-init configurations for guest- config and network-config dynamically and create a cloud-init.iso file. The network-config file contains: - static ip address - netmask - nameservers (I think the network config could be done with the guest-customizations now - this apparently was different in the past, when no netplan config was generated by the open-vm-tools. so we might skip this now, if the customizations work) This guest-config file contains: - user accounts (that might differ between VMs) - ssh-keys (that might also differ between VMs) - Some special runcmds depending on the machine This setup is VM specific, so we can not do it during the ova deployment but only for every machine itself. I hope this clears up the situation a bit of how we currently use it. If there is anything blatantly wrong about this workflow I am happy to hear it, we setup this workflow only about 8 months ago, so we are not sure if this is the way it should be used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
In that case I cannot use cloud-init at all though right? The problem is I still want to attach an iso file with guest customization (well I should have pointed that out before - sorry), that sets up the user, ssh-key asf for the machine being booted. That's something I need to configure the ssh-keys that should be allowed to access the machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
As I opened the duplicate (and accidentaly commented there), let me just add the comment here as well: Thanks for the background information - that's really interesting. Yes I also saw that it is fixed in 6.7U3, however maybe that means they have regression, because we are seeing this issue in vSphere 7. The version are: VMware ESXi, 7.0.1, 17551050 vSphere Client version 7.0.1.00200 I am not sure - maybe the workflow I am using is also at fault? Right now I am using the OVA to deploy a initial machine I never power on but immediately turn into a template for further use (cloning a template is just a lot faster for spawning new VMs and we use the template in our ansible playbooks). What I can see concerning the workflows: - vSphere is generating the netplan configuration with the configuration set in ansible, so the data propagates correctly and the file is created. - I tried to strip everything marked as used for guest customization (I only set the network name), but it still fails unfortunately. If there is any more information I can provide just tell me, I'll happily try to get it. I can also say it *used* to work with vSphere 7, but I don't know the versions or the image versions we were using at the time (and now we can't find them out anymore). I attached some logs from a booted VM that show "Executing traditional GOSC workflow." maybe that's the wrong workflow and there is a way to trigger the new one? ** Attachment added: "Log files from a machine that failed to connect the network adapter" https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1793715/+attachment/5481099/+files/vmware-logs.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921116] Re: Booting on vSphere fails the cloud-init guest customization due to missing dbus.service dependency
*** This bug is a duplicate of bug 1793715 *** https://bugs.launchpad.net/bugs/1793715 Hi, Thanks for the background information - that's really interesting. Yes I also saw that it is fixed in 6.7U3, however maybe that means they have regression, because we are seeing this issue in vSphere 7. The version are: VMware ESXi, 7.0.1, 17551050 vSphere Client version 7.0.1.00200 I am not sure - maybe the workflow I am using is also at fault? Right now I am using the OVA to deploy a initial machine I never power on but immediately turn into a template for further use (cloning a template is just a lot faster for spawning new VMs and we use the template in our ansible playbooks). What I can see concerning the workflows: - vSphere is generating the netplan configuration with the configuration set in ansible, so the data propagates correctly and the file is created. - I tried to strip everything marked as used for guest customization (I only set the network name), but it still fails unfortunately. If there is any more information I can provide just tell me, I'll happily try to get it. I can also say it *used* to work with vSphere 7, but I don't know the versions or the image versions we were using at the time (and now we can't find them out anymore) - I assume that maybe it didn't use the cloud-init customization way then, but still the perl way as I understand the linked bugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921116 Title: Booting on vSphere fails the cloud-init guest customization due to missing dbus.service dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1921116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921116] [NEW] Booting on vSphere fails the cloud-init guest customization due to missing dbus.service dependency
Public bug reported: When booting a virtual machine on vSphere there is an error that guest- customizations can not be run. I was using: Ubuntu 20.04.2 LTS release deployed to a template using the ova file. I ran into this problem, when attempting to boot a machine using ansible and ran into this VMWare bug: https://kb.vmware.com/s/article/59687 To summarize: the vmware tools attempt to use dbus before it's available and guest customization fails, which leads to the network adapters of the VM not being attached. It seems all that is missing to make this work is to add the missing: After=dbus.service dependency to the systemd-service for open-vm-tools.service. Once this is added the guest customizations can be used and after booting the network adapters will be attached successfully. ** Affects: open-vm-tools (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/1921116 Title: Booting on vSphere fails the cloud-init guest customization due to missing dbus.service dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1921116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005165] Re: fglrx needed fglrx-amdcccle in order for xorg to work
** Description changed: After upgrading and rebooting the system the graphical environment was replaced by a text-based login. + + Edit: Forgot to add the link to the forum post to the bug: + http://ubuntuforums.org/showthread.php?t=1987636 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fglrx 2:8.960-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: - + ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Sun May 27 15:22:12 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx, 8.960, 3.2.0-24-generic, x86_64: installed GraphicsCard: - Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:21ec] + Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) + Subsystem: Lenovo Device [17aa:21ec] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) JockeyStatus: - xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release updates) (Proprietary, Disabled, Not in use) - xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, Enabled, In use) + xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release updates) (Proprietary, Disabled, Not in use) + xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, Enabled, In use) MachineType: LENOVO 30515YG ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=4f2d6f03-351c-4070-973c-a8b5db23c968 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8RET52WW (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 30515YG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8RET52WW(1.15):bd11/15/2011:svnLENOVO:pn30515YG:pvrThinkPadX121e:rvnLENOVO:rn30515YG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 30515YG dmi.product.version: ThinkPad X121e dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005165 Title: fglrx needed fglrx-amdcccle in order for xorg to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1005165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005165] [NEW] fglrx needed fglrx-amdcccle in order for xorg to work
Public bug reported: After upgrading and rebooting the system the graphical environment was replaced by a text-based login. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fglrx 2:8.960-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Sun May 27 15:22:12 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx, 8.960, 3.2.0-24-generic, x86_64: installed GraphicsCard: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21ec] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) JockeyStatus: xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, Enabled, In use) MachineType: LENOVO 30515YG ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=4f2d6f03-351c-4070-973c-a8b5db23c968 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8RET52WW (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 30515YG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8RET52WW(1.15):bd11/15/2011:svnLENOVO:pn30515YG:pvrThinkPadX121e:rvnLENOVO:rn30515YG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 30515YG dmi.product.version: ThinkPad X121e dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 precise ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005165 Title: fglrx needed fglrx-amdcccle in order for xorg to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1005165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005165] Re: fglrx needed fglrx-amdcccle in order for xorg to work
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005165 Title: fglrx needed fglrx-amdcccle in order for xorg to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1005165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
