Hello,
I wanted to ask what the default Debian configuration of the NUT package
is in their repo with regards to openssl.? As I have read the NUT
website, and at times it states to custom compile ./configure
--with-openssl and in other instances it doesn't reference this.? I
could not determine if I have to custom compile to have openssl
functionality available, or if this is included by default in some
versions.
The "./compile --help" shows some functionality as "auto",
some "yes"
and this is why I ask.? As also, I would think these days ssl would be
almost default.
I also thought it was included by default as when running systemctl
status nut-monitor, we see "Init SSL without certificate database."
My questions are:
1. Is custom compile is required?
2. If so, would the default configure settings with exception of
--with-openssl be the same as Debian repo?
Thank you in advance for your wisdom in this!
Vyasa
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20250702/dd2b1ab8/attachment.htm>
Vyasa via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes:> I wanted to ask what the default Debian configuration of the NUT > package is in their repo with regards to openssl.? As I have read the > NUT website, and at times it states to custom compile ./configure > --with-openssl and in other instances it doesn't reference this.? I > could not determine if I have to custom compile to have openssl > functionality available, or if this is included by default in some > versions. > > The "./compile --help" shows some functionality as "auto", some "yes" > and this is why I ask.? As also, I would think these days ssl would be > almost default.Really you have to ask Debian. While it's a fair question to ask what happens if you build nut yourself, packagers set options on and off and make dependencies visible or not, as decisions.> My questions are: > > 1. Is custom compile is required? > 2. If so, would the default configure settings with exception of > --with-openssl be the same as Debian repo?Read the Debian packaging control files. In the pkgsrc build, there is a choice of openssl or nss. Not really sure why anybody would want nss. With openssl, the configure args are CONFIGURE_ARGS+= --with-ssl=openssl --without-nss --with-openssl and $ ldd /usr/pkg/bin/upsc /usr/pkg/bin/upsc: -lupsclient.7 => /usr/pkg/lib/libupsclient.so.7 -lssl.15 => /usr/lib/libssl.so.15 -lcrypto.15 => /usr/lib/libcrypto.so.15 -lcrypt.1 => /lib/libcrypt.so.1 -lc.12 => /usr/lib/libc.so.12 -lpthread.1 => /usr/lib/libpthread.so.1 also if you ./configure yourself, save the output and read it.
> ?Hello, > > I wanted to ask what the default Debian configuration of the NUT package is > in their repo with regards to openssl.This is something that you can figure out yourself. Simply ask dpkg for the dependencies of the nut package. If it was compiled with openssl, then it will have a dependency on openssl. $ dpkg -s nut ? Depends: nut-client, nut-server Ok, the nut package depends on nut-client and nut-server packages. And then you investigate these dependencies, recursvely, until you get your answer. I see that my nut-server depends on libnss3, apparently an alternative to openssl. Your mileage may vary. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20250703/46eeefe8/attachment.sig>