Re: Errors in DMESG After System Update

2025-04-05 Thread Tim via users
Tim: >> Supposedly, it could show an ordinary user something they shouldn't >> know, hence the increased security, now. Barry: > As I understand the risk it is the presences of addresses in dmesg > output of kernel internals that are required for attacking the > kernel. > I couldn't remember wha

Re: Errors in DMESG After System Update

2025-04-05 Thread Stephen Morris
On 17/3/25 17:42, Samuel Sieb wrote: On 2025-03-16 15:23, Stephen Morris wrote: Is the nvidia API mismatch because the Xorg nvidia drivers were updated with the update I did and I haven't rebooted yet? [ 3055.581655] NVRM: API mismatch: the client has the version 570.124.04, but

Re: Errors in DMESG After System Update

2025-03-18 Thread Tim via users
Tim: > > Supposedly, it could show an ordinary user something they shouldn't > > know, hence the increased security, now. Stephen Morris: > It depends on what environment you are in, if you are in an > organisational environment then it is possible that it may show > something that is sensitive

Re: Errors in DMESG After System Update

2025-03-18 Thread Barry
> On 18 Mar 2025, at 07:29, Tim via users wrote: > > Supposedly, it could show an ordinary user something they shouldn't > know, hence the increased security, now. As I understand the risk it is the presences of addresses in dmesg output of kernel internals that are required for attacking the

Re: Errors in DMESG After System Update

2025-03-18 Thread Stephen Morris
On 18/3/25 18:28, Tim via users wrote: On Tue, 2025-03-18 at 08:43 +1100, Stephen Morris wrote: Thanks Todd, it's been quite a while since I've used DMESG, but I don't remember ever having to use sudo with it, nor do I remember ever seeing the message about kernel buffer access being denied, but

Re: Errors in DMESG After System Update

2025-03-18 Thread Tim via users
On Tue, 2025-03-18 at 08:43 +1100, Stephen Morris wrote: > Thanks Todd, it's been quite a while since I've used DMESG, but I don't > remember ever having to use sudo with it, nor do I remember ever seeing > the message about kernel buffer access being denied, but it just means I > will now have

Re: Errors in DMESG After System Update

2025-03-17 Thread Stephen Morris
On 17/3/25 09:38, Todd Zullinger wrote: Stephen Morris wrote:     Just a query first off, why do I need to run dmesg under sudo for it to produce its output? In Fedora 39 (or there about), the CONFIG_SECURITY_DMESG_RESTRICT kernel config was changed. The commit in the Fedora kernel source tre

Re: Errors in DMESG After System Update

2025-03-16 Thread Samuel Sieb
On 2025-03-16 15:23, Stephen Morris wrote:     Is the nvidia API mismatch because the Xorg nvidia drivers were updated with the update I did and I haven't rebooted yet? [ 3055.581655] NVRM: API mismatch: the client has the version 570.124.04, but   NVRM: this kernel module has t

Re: Errors in DMESG After System Update

2025-03-16 Thread Todd Zullinger
Stephen Morris wrote: >     Just a query first off, why do I need to run dmesg under sudo for it to > produce its output? In Fedora 39 (or there about), the CONFIG_SECURITY_DMESG_RESTRICT kernel config was changed. The commit in the Fedora kernel source tree provides some useful details¹: Tu

Errors in DMESG After System Update

2025-03-16 Thread Stephen Morris
Hi,     Just a query first off, why do I need to run dmesg under sudo for it to produce its output?     Could someone explain the systemd message below as to why they are coming out rather than the package being updated as specified in the message. The device non-existant errors and the lockd