lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2d6a68c7-cad7-4a0d-9c73-03d3c217bfce@lunn.ch>
Date: Tue, 2 Dec 2025 16:52:42 +0100
From: Andrew Lunn <andrew@...n.ch>
To: René Rebe <rene@...ctco.de>
Cc: Heiner Kallweit <hkallweit1@...il.com>, netdev@...r.kernel.org,
	nic_swsd@...ltek.com
Subject: Re: [PATCH] r8169: fix RTL8117 Wake-on-Lan in DASH mode

> Well, the argument is for wakeup to “just work”. There also
> should be some consistency in Linux. Either all drivers should
> enable it or disable it by default. That is why I have thrown in
> the idea of a new kconfig options for downstream distros to
> make a conscious global choice. E.g. we would ship it it
> enabled.

You might need to separate out, what is Linux doing, and what is the
bootloader doing before Linux takes over the machine.

Linux drivers sometimes don't reset WoL back to nothing enabled. They
just take over how the hardware was configured. So if the bootloader
has enabled Magic packet, Linux might inherit that.

I _think_ Linux enabling Magic packet by default does not
happen. Which is why it would be good if you give links to 5 to 10
drivers, from the over 200 in the kernel, which do enable WoL by
default.

	Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ