I'm not sure. In other clients you can run upscmd -l ups@host and it will list out instant commands available to the client. My NAS doesn't have upscmd but if somehow the NAS become compromised at this point I'm not sure what level of capability would be there apart from being an admin, and again - this would require changing the credentials on every other NUT client to match QNAP. That doesn't seem like a good practice.moody_blue wrote: ↑Sun Jan 29, 2023 11:04 pm I don't consider this to be a security risk. I've never explored NUT extensively but I think that nut clients have restricted priviledges and "harmfull" commands can only be issued by the nut server. It may be a problem if there are other machines imposing their credentials.
Firewalls can probably be used to restrict who can access the nut server if needed.
I just went over NUT's FAQs and found a section about proxying a NUT server using a dummy-ups driver - and also a section on cloning a drive for some clients to use. I'm going to try one of those and see if I can add a "fake" QNAP UPS without modifying any other NUT client.
EDIT: I adjusted the ups.conf file on my NUT server to be:
Code: Select all
[tripplite]
driver = tripplite_usb
port = auto
desc = "Tripp Lite SMART1000RM2U"
vendorid = 90ae
productid = 0001
[qnapups]
driver = dummy-ups
port = tripplite@localhost
desc = "Tripp Lite SMART1000RM2U"