![]() And that even if it's because I have the wrong loadkeys or kbd due to a uncommon installation/upgrade path, that's still a symptom of a bug in the update script. ![]() I reasoned that even if the bug doesn't surface in a normal installation, those lines invoking loadkeys are still wrong. L2 can carry out Spectre v2 attacks on L1 due to L1 thinking. A regression exists in the Linux Kernel within KVM: nVMX that allowed for speculative execution attacks. Searching in Novell's OpenSuSE BugZilla database searching for "loadkeys" yielded no results, so I just entered it as bug 813902. The remote SUSE Linux SLED15 / SLES15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2023:2140-1 advisory. This difference in loadkeys was apparently noticed in another distro (?) in 2011. (this kind of code appears in four places in all). So the solution was to modify the /etc/init.d/kbd file, - loadkeys -C "$KBD_TTY". The policy for setting priorities on these public products listed above have been updated. Bugs for packages inherited from SUSE Linux Enterprise should be reported against PUBLIC SUSE Linux Enterprise SP4, server and High Availability. In the /etc/sysconfig/keyboard file, the KBD_TTY variable holds instead KBD_TTY="tty1 tty2 tt圓 tty4 tty5 tty6"Īnd this, in the /etc/init.d/kbd file, causes an error: Couldn't open tty tty2 tt圓. Bugs should be reported on openSUSE’s bugzilla. The loadkeys manpage reports (correctly, it turns out) You can specify console device by the -C (or -console ) optionīut that's device, not devices. Login: Password: Restrict this session to this IP address (using this option improves security. The reason turned out to be a bug in the handling of the -C flag of loadkey. Bugzilla needs a legitimate login and password to continue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |