similar to: NSS branch testing.

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

Citeren Emilien Kia <emilienkia-guest op alioth.debian.org>: > Modified: branches/ssl-nss-port/server/conf.c > ============================================================================== > --- branches/ssl-nss-port/server/conf.c Wed Jan 5 21:12:03 2011 (r2803) > +++ branches/ssl-nss-port/server/conf.c Thu Jan 6 10:27:55 2011 (r2804) > @@ -178,6 +178,22 @@ > return

Hi all, I am pleased to announce that NSS port of NUT is finished. Port is fully functionnal (same functionnalities as openssl, and a not-activated-by-default client certificate validation function) and successfully tested by myself (external tests are pending, Frederic Bohe is planned for) with a test matrix which will be uploaded to the web site soon (by Arnaud), tested functionnality by

Hi, Thanks to some older discussions on this list I found it quite easy to eventually track down problem with using USB cable with some more of Megatec/Q1 UPSes. The trick (which is done in megatec_usb, but not in blazer_usb) is to read in the junk that somehow gets into read buffers before sending any commands. (I inserted debug statements so it's easy to see that the data read is really

On 02/29/2016 05:33 AM, C. L. Martinez wrote: > More info in my ssl_error.log: > > Mon Feb 29 14:32:06 2016] [info] [client 10.64.118.59] SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page > [Mon Feb 29 14:32:06 2016] [info] SSL Library Error: 336027804 error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request speaking HTTP to HTTPS port!? Well, that

Hi all, I am trying to setup an apache virtualhost under CentOS 6.7 that needs to redirects requests from port 444 to port 5100 in its local ip. But I am doing some mistakes because every time I'm receiving a loop error. My actual httpd's config for this virtualhost is: NameVirtualHost 192.168.1.5:444 <VirtualHost 192.168.1.5:444> ServerName myweb01.local.domain ErrorLog

Citeren Frederic BOHE <fbohe-guest op alioth.debian.org>: > --- branches/windows_port/scripts/Windows/wininit.c Tue Jan 18 > 08:57:03 2011 (r2838) > +++ branches/windows_port/scripts/Windows/wininit.c Tue Jan 18 > 10:05:01 2011 (r2839) > @@ -285,8 +285,11 @@ > char fn[SMALLBUF]; > FILE *nutf; > char buf[SMALLBUF]; > + const char * conf_path; > > -

I am (belatedly) updating pkgsrc to 2.8.1 (+ bugfix). (FWIW, I think a 2.8.1.1 or 2.8.2 immediately with the fix is in order. >From a packaging viewpoint, the effort to update for a release is about 3 minutes plus time to adapt anythhing that has changed. So I'd much rather have releases more often.) In the pkgsrc build, nut finds tcp wrappers because they are part of the base system.

As Charles mentioned in a mail today, we have a branch merge underway for NSS. This branch has been staging for a year, since it's development completion. So time has come to move on, and complete the work there, to switch to other topics. Charles has already sync'ed a git branch with the latest trunk (master) there: https://github.com/clepple/nut/tree/ssl-nss-port-CFL To ensure that

I''m having a problem but don''t know what is causing it so I don''t know exactly where to post, please bear with me. I''m trying to set up https access however whenever I go to https://url_for_site the root route renders but the url is rewritten to http://url_for_site. The ssl request shows in the apache logs but obviously no further ssl requests show up.

On Tue, 19 Jun 2018, tech wrote: > Jun 19 16:34:55 REDACTED upsmon[7389]: Can not initialize SSL context > I am lost. Comments and Help welcome. It's only a comment, but, this message comes from NUT program netssl.c status = NSS_NoDB_Init(NULL); if (status != SECSuccess) { upslogx(LOG_ERR, "Can not initialize SSL context"); nss_error("upscli_init /

I am unable to get 2.7.4 to work with NSS support as provided by libnss3 2:3.26.2 on Debian stretch. Currently NSS supports two database formats identified by prefixes "sql:" for the new database and "dbm:" for the legacy database. I created the NSS database in directory /etc/nut with command certutil -N -d dbm:NSS_db --empty-password I copied over public key and

Hello, the code below the failing part mentions this flavor of protocol, drivers/blazer_ser.c:463 /* * If a command is invalid, it will be echoed back. * As an exception, Best UPS units will report "ACK" in case of success! */ I prepared a patch, it adds a similar check and also checks (in both occurencies) for blazer_command()<0, the latter

Hello all. Thx for the log-tip. It was a access right violation on /etc.../letsencrypt/....cert . The folder was own by root:root Had to create a group nutusers including root and my nut users. After that, had to change the chmod for the folder from 755 to 775 Now, running upsc -l Init SSL without certificate database 850PRO Witch is better. But still problématic wuth the init ssl

...it was almost midnight, Cinderella became a pumpkin, and NUT was released!.. Trick or treat?! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20231031/f3590340/attachment.htm>

...it was almost midnight, Cinderella became a pumpkin, and NUT was released!.. Trick or treat?! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20231031/f3590340/attachment.htm>

I want to use upsdebugx, upslogx in 'clients/upsclient.c', however this fails with the following error messages (I trimmed the path to the build directory to <path> in order to prevent line wrapping): <path>/clients/upsclient.c:941: undefined reference to `upsdebugx' <path>/clients/upsclient.c:910: undefined reference to `upslogx'

I recently upgraded from nut-2.4.1 to 2.4.3 and my UPS stopped working. usbhid-ups now fails two communicate with the UPS: With 2.4.1: # /sbin/usbhid-ups -D -a auto Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 debug level is '1' upsdrv_initups... Using subdriver: Belkin HID 0.12 Path: UPS.BELKINConfig.BELKINConfigVoltage, Type: Feature, ReportID: 0x01,

Hi, I successfully managed to use SSL on a local webserver for testing purposes, following the section "Using SSL" in the Chapter "Using Apache" of the "Definitive Guide to CentOS". Now I wonder: how can I use SSL with virtual hosts? I have several virtual hosts defined. Let's say I want to use SSL with this one: <VirtualHost *:80> ServerAdmin info

After a power interruption, asterisk doesn't seem to be routing calls and there seems to be a premature timeout and hangups occurring. I am clueless where to look. Can someone in the know, look at the following log and enlighten me if there's a problem, or if it looks normal. From the calling phone, it keeps ringing as if never picked up. Thanks soo much. -braman