-= Feature Request =-
And let me know if I need to start a new thread for this, but it seems to be the most appropriate place for a VHR ISO request. I'm also unsure how this will be situated in the v13 release as well, but can we please modify the usbguard configuration to allow all keyboards and mice and probably KVM devices as well? As it stands, when the VHR is deployed, only the plugged in keyboard and mouse (or virtually plugged in when using iDRAC/iLO, etc) are added to the authorized list. Last night I discovered even using the same model of keyboard (abeit a different version - Dell Entry Keyboard A00 vs A01 in this case) does not match the one plugged in when deployed), and the keyboard has to be plugged into the same USB port - using the "correct" keyboard but in the wrong port will also generate an unauthorized device error. I get that this is a hardened repository, but this seems pretty extreme that I would need to keep a specific keyboard and plugged into a specific port in order to use it at the console. My understanding is that the configuration file can be modified to allow additional devices, but if I SSH into the repo, I can't sudo to modify the config file - granted I'm no linux wiz, but so far I don't even see an option to add additional devices. Let me know if I'm missing something though.
And let me know if I need to start a new thread for this, but it seems to be the most appropriate place for a VHR ISO request. I'm also unsure how this will be situated in the v13 release as well, but can we please modify the usbguard configuration to allow all keyboards and mice and probably KVM devices as well? As it stands, when the VHR is deployed, only the plugged in keyboard and mouse (or virtually plugged in when using iDRAC/iLO, etc) are added to the authorized list. Last night I discovered even using the same model of keyboard (abeit a different version - Dell Entry Keyboard A00 vs A01 in this case) does not match the one plugged in when deployed), and the keyboard has to be plugged into the same USB port - using the "correct" keyboard but in the wrong port will also generate an unauthorized device error. I get that this is a hardened repository, but this seems pretty extreme that I would need to keep a specific keyboard and plugged into a specific port in order to use it at the console. My understanding is that the configuration file can be modified to allow additional devices, but if I SSH into the repo, I can't sudo to modify the config file - granted I'm no linux wiz, but so far I don't even see an option to add additional devices. Let me know if I'm missing something though.
Statistics: Posted by dloseke — Jun 25, 2025 1:51 pm
