Fix build when hamlib is installed.
Put /usr/local/include at end of AM_CPPFLAGS instead of at beginning,
ensures the included header files are used.
Link included hamlib using ${libdir}/libhamlib.a rather than -lhamlib to
ensure the included static hamlib is used instead of a dynamic one in the
library path.
Approved by: ports-secteam (miwi)
Add missing run dependency to security/ca_root_nss
Caddy has a feature for automatic Certification installation
from let's encrypt for HTTPS.
Without security/ca_root_nss certificates are impossible to
install, because root certificate is missing.
Bump PORTREVISION.
PR: 237293
Submitted by: Pwny Tail <pwnytail@bsd.services>
Approved by: Fabian Freyer <fabian.freyer@physik.tu-berlin.de> (maintainer)
Approved by: ports-secteam
net-mgmt/mk-livestatus: Restore fix from r485075
mk-livestatus always builds with Nagios 4 support again and
--without-nagios4 is still broken.
PR: 232716
Reported by: Leonid Vasiliev <leo9641@yandex.ru>
Approved by: egypcio (maintainer)
Approved by: ports-secteam blanket
Mark BROKEN: fails to configure
checking for NETTLE... no
configure: error: Package requirements (nettle >= 2.4) were not met:
Package 'nettle', required by 'virtual:world', not found
Reported by: pkg-fallout
Fix build of www/squid and www/squid-devel with clang 8
This fixes an error with a defaulted copy constructor:
../../src/security/ServerOptions.h:38:5: error: explicitly defaulted copy constructor is implicitly deleted [-Werror,-Wdefaulted-function-deleted]
ServerOptions(const ServerOptions &) = default;
^
../../src/security/ServerOptions.h:110:29: note: copy constructor of 'ServerOptions' is implicitly deleted because field 'clientCaStack' has a deleted copy constructor
X509_NAME_STACK_Pointer clientCaStack;
^
/usr/include/c++/v1/memory:2494:3: note: copy constructor is implicitly deleted because 'unique_ptr<stack_st_X509_NAME, Security::ServerOptions::sk_X509_NAME_free_wrapper>' has a user-declared move constructor
unique_ptr(unique_ptr&& __u) noexcept
^
The copy constructor can instead be deleted.
Approved by: portmgr (joneum)
PR: 236210
net/remotebox: Update dependency after net/tigervnc separation
- vncviewer is now installed as net/tigervnc-viewer
- Bump PORTREISION due to dependency change
- Pet portlint (extra item in USES section)
PR: 236928
Submitted by: myself
Approved by: kai (maintainer)
Approved by: portmgr (antonie)
databases/pgpool-II-40: Upgrade from 4.0.3 to 4.0.4
Changelog:
Enhancements
* Add new configuration option ssl_prefer_server_ciphers. (Muhammad Usama)
Add the new setting ssl_prefer_server_ciphers to let users configure if they want client's or server's cipher order to take preference.
The default for this parameter is off, which prioritize the client's cipher order as usual. However this is just for keeping backward compatibility, and it is possible that a malicious client uses weak ciphers. For this reason we recommend to set this parameter to on at all times.
* Allow to set a client cipher list. (Tatsuo Ishii, Yugo Nagata)
For this purpose new parameter ssl_ciphers, which specifies the cipher list to be accepted by Pgpool-II, is added. This is already implemented in PostgreSQL and useful to enhance security when SSL is enabled.
Bug fixes
* Fix unnecessary fsync() to pgpool_status file. (Tatsuo Ishii)
Whenever new connections are created to PostgreSQL backend, fsync() was issued to pgpool_status file, which could generate excessive I/O in certain conditions. So reduce the chance of issuing fsync() so that it is issued only when backend status is changed.
* Doc: add more explanation to follow_master_command. (Tatsuo Ishii)
Add description how follow_master_command is executed etc.
* Doc: add note to detach_false_primary configuration parameter. (bug 469) (Tatsuo Ishii)
To use this feature, sr_check_user must be super user or in pg_monitor group.
Changelog taken from: http://www.pgpool.net/docs/latest/en/html/release-4-0-4.html
Approved by: ports-secteam (joneum)
databases/pgpool-II-37: Upgrade from 3.7.8 to 3.7.9
Changelog:
Enhancements
* Add new configuration option ssl_prefer_server_ciphers. (Muhammad Usama)
Add the new setting ssl_prefer_server_ciphers to let users configure if they want client's or server's cipher order to take preference.
The default for this parameter is off, which prioritize the client's cipher order as usual. However this is just for keeping backward compatibility, and it is possible that a malicious client uses weak ciphers. For this reason we recommend to set this parameter to on at all times.
* Allow to set a client cipher list. (Tatsuo Ishii, Yugo Nagata)
For this purpose new parameter ssl_ciphers, which specifies the cipher list to be accepted by Pgpool-II, is added. This is already implemented in PostgreSQL and useful to enhance security when SSL is enabled.
Bug fixes
* Fix unnecessary fsync() to pgpool_status file. (Tatsuo Ishii)
Whenever new connections are created to PostgreSQL backend, fsync() was issued to pgpool_status file, which could generate excessive I/O in certain conditions. So reduce the chance of issuing fsync() so that it is issued only when backend status is changed.
Changelog taken from: http://www.pgpool.net/docs/latest/en/html/release-3-7-9.html
Approved by: ports-secteam (joneum)
databases/pgpool-II-36: Upgrade from 3.6.15 to 3.6.16
Changelog:
Enhancements
* Add new configuration option ssl_prefer_server_ciphers. (Muhammad Usama)
Add the new setting ssl_prefer_server_ciphers to let users configure if they want client's or server's cipher order to take preference.
The default for this parameter is off, which prioritize the client's cipher order as usual. However this is just for keeping backward compatibility, and it is possible that a malicious client uses weak ciphers. For this reason we recommend to set this parameter to on at all times.
* Allow to set a client cipher list. (Tatsuo Ishii, Yugo Nagata)
For this purpose new parameter ssl_ciphers, which specifies the cipher list to be accepted by Pgpool-II, is added. This is already implemented in PostgreSQL and useful to enhance security when SSL is enabled.
Bug fixes
* Fix unnecessary fsync() to pgpool_status file. (Tatsuo Ishii)
Whenever new connections are created to PostgreSQL backend, fsync() was issued to pgpool_status file, which could generate excessive I/O in certain conditions. So reduce the chance of issuing fsync() so that it is issued only when backend status is changed.
Changelog taken from: http://www.pgpool.net/docs/latest/en/html/release-3-6-16.html
Approved by: ports-secteam (joneum)
databases/pgpool: Upgrade from 3.5.19 to 3.5.20
Changelog:
Enhancements
* Add new configuration option ssl_prefer_server_ciphers. (Muhammad Usama)
Add the new setting ssl_prefer_server_ciphers to let users configure if they want client's or server's cipher order to take preference.
The default for this parameter is off, which prioritize the client's cipher order as usual. However this is just for keeping backward compatibility, and it is possible that a malicious client uses weak ciphers. For this reason we recommend to set this parameter to on at all times.
* Allow to set a client cipher list. (Tatsuo Ishii)
For this purpose new parameter ssl_ciphers, which specifies the cipher list to be accepted by Pgpool-II, is added. This is already implemented in PostgreSQL and useful to enhance security when SSL is enabled.
Bug fixes
* Fix unnecessary fsync() to pgpool_status file. (Tatsuo Ishii)
Whenever new connections are created to PostgreSQL backend, fsync() was issued to pgpool_status file, which could generate excessive I/O in certain conditions. So reduce the chance of issuing fsync() so that it is issued only when backend status is changed.
Changelog taken from: http://www.pgpool.net/docs/latest/en/html/release-3-5-20.html
Approved by: ports-secteam (joneum)
databases/pgpool: Update from 3.4.22 to 3.4.23
Changelog:
Enhancements
* Add new configuration option ssl_prefer_server_ciphers. (Muhammad Usama)
Add the new setting ssl_prefer_server_ciphers to let users configure if they want client's or server's cipher order to take preference.
The default for this parameter is off, which prioritize the client's cipher order as usual. However this is just for keeping backward compatibility, and it is possible that a malicious client uses weak ciphers. For this reason we recommend to set this parameter to on at all times.
* Allow to set a client cipher list. (Tatsuo Ishii)
For this purpose new parameter ssl_ciphers, which specifies the cipher list to be accepted by Pgpool-II, is added. This is already implemented in PostgreSQL and useful to enhance security when SSL is enabled.
Bug fixes
* Fix unnecessary fsync() to pgpool_status file. (Tatsuo Ishii)
Whenever new connections are created to PostgreSQL backend, fsync() was issued to pgpool_status file, which could generate excessive I/O in certain conditions. So reduce the chance of issuing fsync() so that it is issued only when backend status is changed.
Changelog taken from: http://www.pgpool.net/docs/latest/en/html/release-3-4-23.html
Approved by: ports-secteam (joneum)
This port requires a C++11-compatible compiler, so add USES=compiler:c++11-lang
to fix build on GCC-based architectures.
While here, add USES=sdl.
PR: 237100
Submitted by: Piotr Kubaj
Approved by: portmgr (tier-2 blanket)
