Bug 267390 - Update net-im/signald to 0.23.0
Summary: Update net-im/signald to 0.23.0
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Michael Gmelin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-27 12:56 UTC by Filias Heidt
Modified: 2023-03-02 02:40 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (grembo)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Filias Heidt 2022-10-27 12:56:39 UTC 
Hi,

there has been some progress since 0.15 and I'm getting some errors which might be related and I would like to update. Would it be possible to update the port to 0.23?

Thanks a lot,
Filias
Comment 1 kaltheat 2023-02-28 20:30:24 UTC 
Hi,
I would like to agree that this port needs an update. One issue is that https://chat.signal.org has another certificate / issuer which is not known in 0.15, but in later versions[1]. This leads to a connection error like

20:46:04.642 [OkHttp https://chat.signal.org/...] DEBUG libsignal - [WebSocketConnection] [provisioning:152425623] onFailure()
javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
        at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:131)
        at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:353)
        at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:296)
        at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:291)
        at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(CertificateMessage.java:654)
        at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.onCertificate(CertificateMessage.java:473)
        at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.consume(CertificateMessage.java:369)
        at java.base/sun.security.ssl.SSLHandshake.consume(SSLHandshake.java:392)
...

which is also mentioned here[2]. There might be several other issues which are fixed with a newer version.

Please update.

Kind regards
kaltheat

[1] https://gitlab.com/signald/signald/-/commit/9cce3f6463940269e6695c552f50b43c8d7a3b15
[2] https://gitlab.com/signald/signald/-/issues/343
Comment 2 Michael Gmelin freebsd_committer freebsd_triage 2023-03-01 09:57:22 UTC 
I totally agree, it's just a bit of a cross-dependency issue with net-im/libsignal-client and net-im/signal-cli. Adding 0mp, maybe we can do this in a coordinated effort?
Comment 3 Mateusz Piotrowski freebsd_committer freebsd_triage 2023-03-02 02:40:55 UTC 
(In reply to Michael Gmelin from comment #2)

Hey, unfortunately, I won't be able to work on the patch in the upcoming weeks. Feel free to update all the Signal-related ports I maintain as you see fit.