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
MFH: 2019Q2
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
MFH: 2019Q2
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
MFH: 2019Q2
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
MFH: 2019Q2
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
MFH: 2019Q2
- Upgrade sip to 4.19.15
- Upgrade qscintilla2 to 2.11.1
- Upgrade PyQt to 5.12.1
- From this version on www/py-qt5-webengine is unbundled and ships its own distfile
PR: 236894
Exp-run by: antoine
2019-03-25 chinese/reciteword: depends on audio/esound
2019-03-31 comms/conserver: Superseeded by comms/conserver-com
2019-03-24 databases/flamerobin: Abandonware since 2009, does not work with newer version of wxGTK
2019-04-01 databases/mariadb100-client: Upstream End-of-Life March 2019 (https://mariadb.org/about/maintenance-policy/)
2019-04-01 databases/mariadb100-server: Upstream End-of-Life March 2019 (https://mariadb.org/about/maintenance-policy/)
2019-03-12 devel/physfs-devel: is the same as devel/physfs, serving no purpose
2019-03-20 devel/py-construct28: Latest upstream version is in ports tree devel/py-construct
2019-03-31 devel/xtoolchain-llvm40: No supported release uses this version
2019-03-31 devel/xtoolchain-llvm50: No supported release uses this version
2019-03-31 finance/aqmoney: no longer maintained upstream
2019-03-31 finance/openhbci: no longer maintained upstream
2019-03-31 graphics/py-exiv2: py-exiv2 has been deprecated in favour of GExiv2
2019-04-04 mail/dbmail22: Please use mail/dbmail which uses latest version of 3.X
2019-03-31 net/rubygem-fog-google17: Use net/rubygem-fog-google instead
2019-03-31 ports-mgmt/bsdadminscripts: Upstream stale nearly 10 years, no longer works properly, use ports-mgmt/bsdadminscripts2 instead
2019-03-24 www/mod_md-devel: Use the module that is shipped with Apache 2.4
2019-03-25 x11/xbelld: Depends on audio/esound
Summary of the most important changes since version 1.2.14:
- Removed ability to manage sorted arrays as key values due
to performance issues; replaced with two-part compound keys
+ Added support of variable-length encoded integer keys
+ Added atomic in-place integer key value increments
+ Added new utility functions and flags
* Fixed incorrect key handling in iwkv_del()
* Fixed iwkv_cursor_copy_key() which was not aware of the
compound keys mode
* Fixed iwkv_puth() was called with incorrect previous value
* Fixed deadlocks in iwkv_del() by not escalating exclusive
lock on the storage
* Fixed iwxstr_new2() with zero size argument caused illegal
memory write
* Fixed memory leak in iwkv_cursor_open() on error
* Fixed high CPU usage in WAL mode
Requested by: upstream
since gdbm is gemified in upstream after Ruby 2.5 [1]. Ruby 2.4 can also
use the gdbm gem because it is a gem!
- Add MOVED entry
- Bump PORTEPOCH because PORTVERSION goes barwards
- Update pkg-descr and WWW
- Remove unnecessary pkg-message
[1] https://bugs.ruby-lang.org/issues/5481
Update lang/ruby* ports:
- Do not build gdbm together with Ruby interpreter, but build as a rubygem
- Remove ${BUILD_WRKSRC}/ext/gdbm instead of moving it to ${WRKDIR}
- Update pkg-message to mention rubygem-gdbm instead of ruby-gdbm
Also following changes are made to ruby-gdbm consumers:
- Updade dependency to depend on rubygem-gdbm
- Bump PORTREVISION due to dependency change
PR: 230436
Submitted by: Yasuhiro KIMURA <yasu@utahime.org>
Sponsored by: HAW International, Inc.
2019-03-31 archivers/go-compress: Go libraries should not be packaged
2019-03-31 textproc/go.text: Go libraries should not be packaged
2019-03-31 devel/go-hashicorp-logutils: Go libraries should not be packaged
2019-03-31 devel/go-cpuid: Go libraries should not be packaged
2019-03-31 devel/go-nuid: Go libraries should not be packaged
2019-03-31 devel/go-yaml: Go libraries should not be packaged
2019-03-31 devel/go-raw: Go libraries should not be packaged
2019-03-31 devel/go-go.uuid: Go libraries should not be packaged
2019-03-31 devel/go-goregen: Go libraries should not be packaged
2019-03-31 devel/go-runewidth: Go libraries should not be packaged
2019-03-31 devel/go-cobra: Go libraries should not be packaged
2019-03-31 devel/go-pflag: Go libraries should not be packaged
2019-03-31 devel/go-slices: Go libraries should not be packaged
2019-03-31 devel/go-form: Go libraries should not be packaged
2019-03-31 devel/go-bayesian: Go libraries should not be packaged
2019-03-31 devel/go-uuid: Go libraries should not be packaged
2019-03-31 devel/go-logrus: Go libraries should not be packaged
2019-03-31 devel/go-metrics: Go libraries should not be packaged
2019-03-31 devel/go-codec: Go libraries should not be packaged
2019-03-31 devel/go-faker: Go libraries should not be packaged
2019-03-31 devel/go-crc32: Go libraries should not be packaged
2019-03-31 security/goptlib: Go libraries should not be packaged
2019-03-31 security/go.crypto: Go libraries should not be packaged
2019-03-31 net/go-httppath: Go libraries should not be packaged
2019-03-31 net/go-amqp: Go libraries should not be packaged
2019-03-31 net/go.net: Go libraries should not be packaged
2019-03-31 net/go-nats: Go libraries should not be packaged
2019-03-31 net/go-httptreemux: Go libraries should not be packaged
2019-03-31 databases/gosqlite3: Go libraries should not be packaged
2019-03-31 databases/redigo: Go libraries should not be packaged
2019-03-31 databases/gomdb: Go libraries should not be packaged
2019-03-31 databases/radix.v2: Go libraries should not be packaged
2019-03-31 databases/levigo: Go libraries should not be packaged
2019-03-31 www/unit-go: Go libraries should not be packaged
2019-03-31 www/webgo: Go libraries should not be packaged
2019-03-31 www/go-fasthttp: Go libraries should not be packaged
- explicitly depend on OTP>=21.3 to skip BEAM coredumps observed in the wild
- drop OTP<20 option per above
- tweak rc.d script to ensure coredumps can be retrieved if needed
Approved by: jrm (mentor)
Differential Revision: https://reviews.freebsd.org/D19621
Ports for Haskell *libraries* are going to be removed from the ports tree.
Haskell *applications* are going to be statically linked with all dependencies
( https://reviews.freebsd.org/D19730 ), so there is no reason to keep
Haskell libraries in tree.
If you think a port is wrongly marked and should stay, please contact haskell@
Submitted by: arrowd
Differential Revision: https://reviews.freebsd.org/D19244
Rene Ladan
Steve Wills
Torsten Zuehlsdorff
Tobias Kortkamp
Yuri Victorovich
Sunpoet Po-Chuan Hsieh
Antoine Brodin
Tobias C. Berner
Matthew Seaman
Craig Leres
Muhammad Moinur Rahman
Dave Cottlehuber
Romain Tartière
Alexey Dokuchaev
Koichiro Iwao
Mark Linimon
Thomas Zander