For context, kernel panics seem to sometimes be encoded as a URL in the QR code by distros. The panic text is encoded as a numeric parameter. For example:
https://jexposit.fedorapeople.org/drm-panic/#?a=x86_64&v=6.17.0-rc2+&z=64016708045408584681305161836175901065787789727173061004041671633088591186286363786562987653814347942450168430510852681524688435157911241621365859153819732690406649525043247774110913752991389170560320455163781439079986337356710273501164645667555084821480237326301207073831710176482850121513079951455217310046422632328303510474264780788030301611164774573122018172510304672562667379831349924441560360997679573341401750485619388375493[... many more digits]
It's a possibility, but it's not how these kernel panic viewer websites are currently implemented. They do the decoding on the clientside, with the data stored in the URL fragment, which is not sent to the server by default.
Still good to have alternative implementations, though. The Javascript could be silently stealing the URL fragment on only specific requests, so there's no real way to audit it to be sure.
https://discussion.fedoraproject.org/t/f45-change-proposal-d...
This script is to decode such kernel panics without needing to provide it to an external service.
In the particular URL example, the panic is not necessarily sent to a server, because it's in a URL fragment (`#`), but still.
This script is to decode such kernel panics without needing to provide it to an external service.
WTF. A solution for an entirely self-inflicted problem.
Distro developers and user are separate people. Also, a person viewing the QR code is not necessarily the owner of the panicked system.
Still good to have alternative implementations, though. The Javascript could be silently stealing the URL fragment on only specific requests, so there's no real way to audit it to be sure.
Qr -> URL -> Panic Log