search for: certverify

...scussion in the mailing-list, I have done some tests with nut trunk and - if my config is not too bad - I think ther is a bug with server certificate verification. With a clean trunk checkout, compile and installation; and with the following config : upsmon.conf: CERTPATH /usr/local/ups/etc/cert/ CERTVERIFY 1 FORCESSL 1 Upsd.conf: CERTFILE /usr/local/ups/etc/upsd1.pem And /usr/local/ups/etc/cert/ is empty (no file). When I start upsd and upsmon, there is a valid SSL connection between them. So, do I misunderstand CERTVERIFY directive ? Or is there a bug ? Can you reproduce such behaviour ? BR, Em...

If you don't use 'CERTVERIFY 1', then this will at least make sure that nobody can sniff your sessions without a large effort (...) > So, do I misunderstand CERTVERIFY directive ? Or is there a bug ? >> Can you reproduce such behaviour ? >> > > I'm not sure what is going on. Can you try running...

...smon.conf MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +1" POLLFREQ 10 POLLFREQALERT 10 HOSTSYNC 15 DEADTIME 20 POWERDOWNFLAG /etc/killpower RBWARNTIME 432000 NOCOMMWARNTIME 300 FINALDELAY 4 CERTPATH /etc/letsencrypt/live/REDACTED/ # CERTHOST <hostname> <certificate name> <certverify> <forcessl> # CERTVERIFY 1 # FORCESSL 0 MONITOR 850PRO at localhost 1 admin 1401 master SHUTDOWNCMD "/sbin/shutdown -h now" HOSTSYNC 15 POWERDOWNFLAG /etc/nut/killpower FINALDELAY 5 NOTIFYCMD /sbin/upssched NOTIFYMSG ONBATT "%s is on battery" NOTIFYMSG ONLINE "%s i...

Hello All 2015-03-26 9:03 GMT+01:00 Arnaud Quette <arnaud.quette at gmail.com>: > > > What I will do is to move ssl initializing after usering and forking, > than add key file right checking where ssl was initialized before (before > forking). > > As keys should be owned by nut user, this would not be a problem. > > And moving this code, independently of SSL

...LL+EXEC > NOTIFYFLAG COMMOK   SYSLOG+WALL > NOTIFYFLAG COMMBAD  SYSLOG+WALL > NOTIFYFLAG SHUTDOWN SYSLOG+WALL > NOTIFYFLAG REPLBATT SYSLOG+WALL > NOTIFYFLAG NOCOMM   SYSLOG+WALL > NOTIFYFLAG NOPARENT SYSLOG+WALL > RBWARNTIME 43200 > NOCOMMWARNTIME 300 > FINALDELAY 60 > CERTVERIFY 0 > FORCESSL 0 > > Another thing worth noting, and probably unrelated to this specific > scenario, is somehow I have a "nut" user and a "nutuser" user.  I don't > know how that happened.  On my Debian setup (details in previous > message), user "nu...