search for: certverifi

Hi all, After client's certificate verifications discussion 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

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 'upsmon' with debugging > enabled? The following are

those mails list are from last century but i give it a try ! created : https://github.com/networkupstools/nut/issues/563 Hello all, Trying to run an EATON 850pro via USB on a Debian Stretch Stable. I have letsencrypt certificate installed and working. When trying to manage the EATON device, i got: upsmon Can not initialize SSL context When 850pro is connected via USB, i can: lsusb Bus 009

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

Was /etc/nut/upssched-cmd automatically installed? I don't have it on my raspberry pi. :-( On 2019-04-03 1:54 p.m., Mike wrote: > I figured this out and it is working now.  This fix seems strange to me > and is possibly a bug.  I'm sharing in case it might help others. > > I had to uncomment all of the NOTIFYFLAG statements whether I was > changing them or not.