plugins
plugins copied to clipboard
Shadowsocks uses deprecated pcre-8.45_4.
Important notices Before you add a new report, we ask you kindly to acknowledge the following:
- [x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
- [x] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
- [x] The title contains the plugin to which this issue belongs
Describe the bug When installing the Shadowsocks plugin I get notified about using the wrong version of pcre. pcre-8.45-4 gets installed instead of the recommended devel/pcre2.
To Reproduce Steps to reproduce the behavior:
- Install Shadowsocks plugin through the gui.
Expected behavior I do not receive a warning about using the deprecated version of pcre.
Environment OPNsense 24.1.7_4 (amd64).
The upstream port of FreeBSD needs to be updated, maybe you can open an issue over there to get in touch with the maintainer?
upstream project with problem is at https://github.com/shadowsocks/shadowsocks-libev. The latest commit to shadowsocks-libev is 2 years ago. The description of shadowsocks-libev github repository states that further development is in https://github.com/shadowsocks/shadowsocks-rust.
I searched for 5 minutes if pcre2 can be used as an API compatible drop in replacement for pcre but found no information.
So sooner or later https://github.com/opnsense/plugins/blob/a01fd048ae6d5db323473d9fd8c574da18c45388/net/shadowsocks/Makefile#L4 should be replaced by PLUGIN_DEPENDS= shadowsocks-rust. Again I do not know if shadowsocks-rust is API compatible with shadowsocks-libev.
Not going to touch this. We could pivot to another dependency but not without maintainer ok and testing. All library related changes are FreeBSD ports territory.
This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository, please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue, just let us know, so we can reopen the issue and assign an owner to it.