| 2020-08-03 17:26:33 |
Eric Desrochers |
bug |
|
|
added bug |
| 2020-08-03 17:28:07 |
Eric Desrochers |
tags |
|
seg sts |
|
| 2020-08-03 17:29:34 |
Eric Desrochers |
nominated for series |
|
Ubuntu Focal |
|
| 2020-08-03 17:29:34 |
Eric Desrochers |
bug task added |
|
rsyslog (Ubuntu Focal) |
|
| 2020-08-03 17:32:05 |
Eric Desrochers |
description |
The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following:
syslog:Aug 3 15:16:58 <HOSTNAME> rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2]
[1] - Bionic/18.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root syslog 5, 1 Aug 3 15:17 /dev/console
[2] - Focal/20.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root tty 5, 1 Aug 3 17:19 /dev/console
# /etc/rsyslog.conf
$PrivDropToUser syslog
$PrivDropToGroup syslog
** As a debug exercise I did the following:
- Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options.
- Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group.
Other bug:
https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 |
The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following:
syslog:Aug 3 15:16:58 <HOSTNAME> rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2]
[1] - Bionic/18.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root syslog 5, 1 Aug 3 15:17 /dev/console
[2] - Focal/20.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root tty 5, 1 Aug 3 17:19 /dev/console
# /etc/rsyslog.conf
$PrivDropToUser syslog
$PrivDropToGroup syslog
** As a debug exercise I did the following:
- Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options.
- Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group.
Meaning that it's pretty obvious with the above statement that the permission denied is caused by the permission/ownership mismatch between '/dev/console' 's ownership permission & syslog user (PrivDropTo[User|Group]).
Other bug:
https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 |
|
| 2020-08-04 16:02:20 |
Eric Desrochers |
rsyslog (Ubuntu Focal): status |
New |
In Progress |
|
| 2020-08-04 16:02:24 |
Eric Desrochers |
rsyslog (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2020-08-04 16:02:26 |
Eric Desrochers |
rsyslog (Ubuntu Focal): assignee |
|
Eric Desrochers (slashd) |
|
| 2020-08-04 16:12:12 |
Eric Desrochers |
description |
The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following:
syslog:Aug 3 15:16:58 <HOSTNAME> rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2]
[1] - Bionic/18.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root syslog 5, 1 Aug 3 15:17 /dev/console
[2] - Focal/20.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root tty 5, 1 Aug 3 17:19 /dev/console
# /etc/rsyslog.conf
$PrivDropToUser syslog
$PrivDropToGroup syslog
** As a debug exercise I did the following:
- Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options.
- Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group.
Meaning that it's pretty obvious with the above statement that the permission denied is caused by the permission/ownership mismatch between '/dev/console' 's ownership permission & syslog user (PrivDropTo[User|Group]).
Other bug:
https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 |
[Impact]
At the moment rsyslog cannot have access /dev/console due to a mismatch permission/ownership between '/dev/console' and the Privilege Drop User and Group 'syslog' in rsyslog.
[Test Case]
* Deploy focal/20.04LTS
* Install rsyslog
* systemctl restart rsyslog OR systemctl restart rsyslog
* Inspect /var/log/syslog for the following error:
syslog:Aug 4 14:37:56 <HOSTNAME> rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
[Regression potential]
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/comments/4
[Other information]
[Original description]
The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following:
syslog:Aug 3 15:16:58 <HOSTNAME> rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2]
[1] - Bionic/18.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root syslog 5, 1 Aug 3 15:17 /dev/console
[2] - Focal/20.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root tty 5, 1 Aug 3 17:19 /dev/console
# /etc/rsyslog.conf
$PrivDropToUser syslog
$PrivDropToGroup syslog
** As a debug exercise I did the following:
- Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options.
- Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group.
Meaning that it's pretty obvious with the above statement that the permission denied is caused by the permission/ownership mismatch between '/dev/console' 's ownership permission & syslog user (PrivDropTo[User|Group]).
Other bug:
https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 |
|
| 2020-08-04 16:15:02 |
Eric Desrochers |
description |
[Impact]
At the moment rsyslog cannot have access /dev/console due to a mismatch permission/ownership between '/dev/console' and the Privilege Drop User and Group 'syslog' in rsyslog.
[Test Case]
* Deploy focal/20.04LTS
* Install rsyslog
* systemctl restart rsyslog OR systemctl restart rsyslog
* Inspect /var/log/syslog for the following error:
syslog:Aug 4 14:37:56 <HOSTNAME> rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
[Regression potential]
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/comments/4
[Other information]
[Original description]
The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following:
syslog:Aug 3 15:16:58 <HOSTNAME> rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2]
[1] - Bionic/18.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root syslog 5, 1 Aug 3 15:17 /dev/console
[2] - Focal/20.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root tty 5, 1 Aug 3 17:19 /dev/console
# /etc/rsyslog.conf
$PrivDropToUser syslog
$PrivDropToGroup syslog
** As a debug exercise I did the following:
- Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options.
- Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group.
Meaning that it's pretty obvious with the above statement that the permission denied is caused by the permission/ownership mismatch between '/dev/console' 's ownership permission & syslog user (PrivDropTo[User|Group]).
Other bug:
https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 |
[Impact]
At the moment rsyslog cannot have access /dev/console due to a mismatch permission/ownership between '/dev/console' and the Privilege Drop User and Group 'syslog' in rsyslog.
[Test Case]
* Deploy focal/20.04LTS
* Install rsyslog
* systemctl restart rsyslog OR systemctl restart rsyslog
* Inspect /var/log/syslog for the following error:
syslog:Aug 4 14:37:56 <HOSTNAME> rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
[Regression potential]
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/comments/4
[Other information]
Other bug:
https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889
[Original description]
The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following:
syslog:Aug 3 15:16:58 <HOSTNAME> rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2]
[1] - Bionic/18.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root syslog 5, 1 Aug 3 15:17 /dev/console
[2] - Focal/20.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root tty 5, 1 Aug 3 17:19 /dev/console
# /etc/rsyslog.conf
$PrivDropToUser syslog
$PrivDropToGroup syslog
** As a debug exercise I did the following:
- Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options.
- Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group.
Meaning that it's pretty obvious with the above statement that the permission denied is caused by the permission/ownership mismatch between '/dev/console' 's ownership permission & syslog user (PrivDropTo[User|Group]).
Other bug:
https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 |
|
| 2020-08-04 16:38:38 |
Eric Desrochers |
description |
[Impact]
At the moment rsyslog cannot have access /dev/console due to a mismatch permission/ownership between '/dev/console' and the Privilege Drop User and Group 'syslog' in rsyslog.
[Test Case]
* Deploy focal/20.04LTS
* Install rsyslog
* systemctl restart rsyslog OR systemctl restart rsyslog
* Inspect /var/log/syslog for the following error:
syslog:Aug 4 14:37:56 <HOSTNAME> rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
[Regression potential]
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/comments/4
[Other information]
Other bug:
https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889
[Original description]
The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following:
syslog:Aug 3 15:16:58 <HOSTNAME> rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2]
[1] - Bionic/18.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root syslog 5, 1 Aug 3 15:17 /dev/console
[2] - Focal/20.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root tty 5, 1 Aug 3 17:19 /dev/console
# /etc/rsyslog.conf
$PrivDropToUser syslog
$PrivDropToGroup syslog
** As a debug exercise I did the following:
- Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options.
- Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group.
Meaning that it's pretty obvious with the above statement that the permission denied is caused by the permission/ownership mismatch between '/dev/console' 's ownership permission & syslog user (PrivDropTo[User|Group]).
Other bug:
https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 |
[Impact]
At the moment rsyslog cannot have access /dev/console due to a mismatch permission/ownership between '/dev/console' and the Privilege Drop User and Group 'syslog' in rsyslog.
[Test Case]
* Deploy focal/20.04LTS (tested in gcloud instance)
* Install rsyslog
* systemctl restart rsyslog OR systemctl restart rsyslog
* Inspect /var/log/syslog for the following error:
syslog:Aug 4 14:37:56 <HOSTNAME> rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
[Regression potential]
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/comments/4
[Other information]
Other bug:
https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889
[Original description]
The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following:
syslog:Aug 3 15:16:58 <HOSTNAME> rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2]
[1] - Bionic/18.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root syslog 5, 1 Aug 3 15:17 /dev/console
[2] - Focal/20.04LTS (Gcloud instance)
# ls -l /dev/console
crw--w---- 1 root tty 5, 1 Aug 3 17:19 /dev/console
# /etc/rsyslog.conf
$PrivDropToUser syslog
$PrivDropToGroup syslog
** As a debug exercise I did the following:
- Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options.
- Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group.
Meaning that it's pretty obvious with the above statement that the permission denied is caused by the permission/ownership mismatch between '/dev/console' 's ownership permission & syslog user (PrivDropTo[User|Group]).
Other bug:
https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 |
|
| 2020-08-07 08:54:13 |
Timo Aaltonen |
rsyslog (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2020-08-07 08:54:15 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-08-07 08:54:17 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2020-08-07 08:54:21 |
Timo Aaltonen |
tags |
seg sts |
seg sts verification-needed verification-needed-focal |
|
| 2020-08-07 21:40:27 |
Zach Bjornson |
bug |
|
|
added subscriber Zach Bjornson |
| 2020-08-10 19:03:47 |
Eric Desrochers |
tags |
seg sts verification-needed verification-needed-focal |
seg sts verification-done verification-done-focal |
|
| 2020-08-18 18:16:59 |
Mauricio Faria de Oliveira |
bug |
|
|
added subscriber Mauricio Faria de Oliveira |
| 2020-08-20 08:49:55 |
Launchpad Janitor |
rsyslog (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-08-20 08:50:01 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2023-03-12 13:28:10 |
Launchpad Janitor |
rsyslog (Ubuntu): status |
New |
Confirmed |
|
