[Bug 1870818] Re: apache2 security fix in 2.4.43

2020-08-11 Thread Chris Samaritoni
As this security issue seems to have not progressed afaik since may, I
wanted to make sure whoever is involved in triaging this know that this
CVE has been considered a high priority for PCI compliancy checks even
though it appears to be marked "Low" by Canonical.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870818

Title:
  apache2 security fix in 2.4.43

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1870818/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1586473] Re: 16.04 regression bug lshw -C memory does not display module info

2016-06-08 Thread Chris Samaritoni
I'm experiencing the same issue but it seems to be a general issue with
all classes in lshw.

I have two identical systems with the same hardware and on my 14.04
server I can run

# lshw -C system
host01   
description: Rack Mount Chassis
product: PowerEdge 1950 ()
vendor: Dell Inc.
serial: XXX
width: 64 bits
capabilities: smbios-2.5 dmi-2.5 vsyscall32
configuration: boot=normal chassis=rackmount 
uuid=23454B4D-4800-1200-2323-C8A04E4C4832

and on the 16.04 server it only returns

# lshw -C system
host02 
description: Computer
width: 64 bits
capabilities: smbios-2.5 vsyscall32

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586473

Title:
  16.04 regression bug lshw -C memory does not display module info

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1586473/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1586473] Re: 16.04 regression bug lshw -C memory does not display module info

2016-06-10 Thread Chris Samaritoni
I just noticed a new version of lshw ( 02.17-1.1ubuntu3.1 ) seems to
have fixed this issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586473

Title:
  16.04 regression bug lshw -C memory does not display module info

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1586473/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 994199] [NEW] vmbuilder and /etc/sudoers template missing "sudo" group support

2012-05-03 Thread Chris Samaritoni
Public bug reported:

I noticed when creating a 12.04 VM with vmbuilder, the template file
/etc/vmbuilder/ubuntu/sudoers.tmpl that is used to generate the
/etc/sudoers appears to be quite outdated. From my understanding on
12.04 you are supposed to use the "sudo" group for putting users in, to
allow sudo access and "admin" was just hanging around for backward
compatibility. The template file does not include a "sudo" entry in the
/etc/sudoers

Current template:

# /etc/sudoers
#
# This file MUST be edited with the 'visudo' command as root.
#
# See the man page for details on how to write a sudoers file.
# Defaults

Defaults!lecture,tty_tickets,!fqdn

# Uncomment to allow members of group sudo to not need a password
# %sudo ALL=NOPASSWD: ALL

# Host alias specification

# User alias specification

# Cmnd alias specification

# User privilege specification
rootALL=(ALL) ALL

# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL


I modified the /etc/vmbuilder/ubuntu/sudoers.tmpl to match a typical
phyical install (ie, from CD) and my issue was solved.

Modified template file:

#
# This file MUST be edited with the 'visudo' command as root.
#
# Please consider adding local content in /etc/sudoers.d/ instead of
# directly modifying this file.
#
# See the man page for details on how to write a sudoers file.
#
Defaultsenv_reset
Defaults
secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"

# Host alias specification

# User alias specification

# Cmnd alias specification

# User privilege specification
rootALL=(ALL:ALL) ALL

# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL

# Allow members of group sudo to execute any command
%sudo   ALL=(ALL:ALL) ALL

# See sudoers(5) for more information on "\#include" directives:

#includedir /etc/sudoers.d


** Affects: vm-builder (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  I noticed when creating a 12.04 VM with vmbuilder, the template file
  /etc/vmbuilder/ubuntu/sudoers.tmpl that is used to generate the
  /etc/sudoers appears to be quite outdated. From my understanding on
  12.04 you are supposed to use the "sudo" group for putting users in, to
  allow sudo access and "admin" was just hanging around for backward
- compatibility. The templates file does not include a "sudo" entry in the
+ compatibility. The template file does not include a "sudo" entry in the
  /etc/sudoers
  
- Currently template:
+ Current template:
  
  # /etc/sudoers
  #
  # This file MUST be edited with the 'visudo' command as root.
  #
  # See the man page for details on how to write a sudoers file.
  # Defaults
  
  Defaults!lecture,tty_tickets,!fqdn
  
  # Uncomment to allow members of group sudo to not need a password
  # %sudo ALL=NOPASSWD: ALL
  
  # Host alias specification
  
  # User alias specification
  
  # Cmnd alias specification
  
  # User privilege specification
  rootALL=(ALL) ALL
  
  # Members of the admin group may gain root privileges
  %admin ALL=(ALL) ALL
  
  
  I modified the /etc/vmbuilder/ubuntu/sudoers.tmpl to match a typical
  phyical install (ie, from CD) and my issue was solved.
  
  Modified template file:
  
  #
  # This file MUST be edited with the 'visudo' command as root.
  #
  # Please consider adding local content in /etc/sudoers.d/ instead of
  # directly modifying this file.
  #
  # See the man page for details on how to write a sudoers file.
  #
  Defaultsenv_reset
  Defaults
secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
  
  # Host alias specification
  
  # User alias specification
  
  # Cmnd alias specification
  
  # User privilege specification
  rootALL=(ALL:ALL) ALL
  
  # Members of the admin group may gain root privileges
  %admin ALL=(ALL) ALL
  
  # Allow members of group sudo to execute any command
  %sudo   ALL=(ALL:ALL) ALL
  
  # See sudoers(5) for more information on "\#include" directives:
  
  #includedir /etc/sudoers.d
  

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994199

Title:
  vmbuilder and /etc/sudoers template missing "sudo" group support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/994199/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 994199] Re: vmbuilder and /etc/sudoers template missing "sudo" group support

2012-05-03 Thread Chris Samaritoni
If and when the template is updated, when you supply the default user to
add to the system when you build the VM, they should be added to "sudo"
group and not the "admin" group.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994199

Title:
  vmbuilder and /etc/sudoers template missing "sudo" group support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/994199/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs