similar to: 2.7.4 uses deprecated back level of TLS

All; I have a Fedora 26 server that I am trying to compile asterisk-certified-13.13-cert6 on. However, I'm getting the following errors. I'm also having a tough time trying to compile Dahdi. I'm not sure what I'm missing, but if anyone else is running Fedora, I'd really appreciate any help at all. Thanks Much; John V. make[1]: Leaving directory

The init functions are not longer required in OpenSSL 1.1 so I dropped them. TLSv1_client_method() should not be used because it enables only the TLSv1.0 protocol. Better is to use SSLv23_client_method() which enable all the protocols including TLSv1.2. With this functions SSLv2 and SSLv3 is theoretically possible but as of today those protocols are usually build-time disabled. To avoid all this

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

Hi, I need help because I can't install Nut in RedHat EL 6.6 The version of Nut in repository ot RHEL is 2.6.5-2, but doesn't suppor my UPS, Liebert GXT3-200RT. I read that it is supported using Nut version 2.7.2, but I looking all around the web how to install it in my RedHat but I didn't find answers. Follow the guide, I can downlad lasted version stable on web: 2.7.2 Here the

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

OK - trying to migrate to dovecot and I like what I see so far, but having a hard time getting it to work. I decided to go with the 1.0 version because I need to get away from the ~/Mail namespace. I'm trying to port from a Linuxconf virtual WU-IMAP type config. So - I compiled but then decided I wanted mysql so I tried to reconfigure and now getting compile errors. Looks like I'm

On Jun 2, 2014, at 10:25 PM, Stefan Bruda wrote: > Hello, > > At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: >> >> On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> >>>> Don't worry about the battery physical properties for now - the >>>> problem there is that we don't have enough information from the UPS >>>> to do a

Hello, At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: > > On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: > > >> Don't worry about the battery physical properties for now - the > >> problem there is that we don't have enough information from the UPS > >> to do a proper calculation. With the V_interval[] settings, you can > >> tweak

Great, thanks! Two questions: * what is a domain literal? Is this something like 192.168.0.1? In this case, the '[]' are probably unnecessary. * are you sure you want to use fprintf(stderr, ...) in a library? This doesn't seem like a good idea to me. Wouldn't it be more consistent to extend upscli_errlist[] ? -- Peter Arjen de Korte wrote: > > Author:

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'

With the Ipv6 patch (r708), I get: upsclient.c: In function `upscli_connect': upsclient.c:469: `AI_ADDRCONFIG' undeclared (first use in this function) upsclient.c:469: (Each undeclared identifier is reported only once upsclient.c:469: for each function it appears in.) Even if it doesn't break IPv4 support, it may break portability, as IPv6 seems to require specific functions that are

Great, thanks Arjen! Now we need an autoconf test to set HAVE_IPV6 automatically. I will look into what functionality needs to be tested; the test can be refined as problems arise later. -- Peter Arjen de Korte wrote: > > Author: adkorte-guest > Date: Sat Jan 6 19:39:08 2007 > New Revision: 710 > > Modified: > trunk/ChangeLog > trunk/clients/upsc.c >

OpenSSL 1.1.0 has deprecated SSL_load_error_strings and SSL_library_init. Initialization is done automatically, so they're not needed with icecast. Fixes issue #2318 Signed-off-by: Eneas U de Queiroz <cote2004-github at yahoo.com> --- src/tls.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/tls.c b/src/tls.c index 36edd86..e4688c5 100644 --- a/src/tls.c +++ b/src/tls.c

Hi Arjen, in server/upsd.c r731, you moved the call conf_load() from after check_perms() (~ l.1020) to before setupsignals() (~ l.989). The problem is that conf_load() needs to open the ups driver socket, and it assumes that STATEPATH is the current working directory. The directory is only set in l.1016. Therefore, the first attempt to open a socket will always fail. From the user's point of

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

Hello, I was running upsmon some time without UPS connected and noticed significant memory leak. After some debugging I found the leak source. It is in file clients/upsclient.c. Function upscli_connect() allocates memory for ups->pc_ctx and in case of any error, just returns -1 without freeing it. My NUT version is 2.2.0, but I quickly looked through 2.2.1 sources and it seems this bug was not

I was testing some code for listing available UPSes, and when I tried connecting to a machine that didn't have upsd running, upsc went into an infinite loop on OS X (IPv6 enabled). The error code returned by connect is EINVAL, which apparently isn't one of the errors documented in connect(2) here. http://boxster.ghz.cc/projects/nut/changeset/731

I have been trying to get Nut working on a system with Fedora 8 i86_64 installed and an APC Smart-UPS USB. The 2.2.0 rpm does not seem to like the USB on this UPS. I have tried compiling the 2.2.2 version, from source, but am getting warnings. I have tried building it on my i386 system (f8 as well) and I get no warnings also the 2.2.0 works fine on that one with a TrippLite Omni 900 LCD via

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