Skip to content

Conversation

@aparcar
Copy link
Member

@aparcar aparcar commented Oct 30, 2025

📦 Package Details

Maintainer: @fededim

Description:

By using --cert-warn this silently ignores certificate warnings. Removing it so the connection is properly terminated.


🧪 Run Testing Details

  • OpenWrt Version: CI
  • OpenWrt Target/Subtarget: CI
  • OpenWrt Device: CI

✅ Formalities

  • I have reviewed the CONTRIBUTING.md file for detailed contributing guidelines.

If your PR contains a patch:

  • It can be applied using git am
  • It has been refreshed to avoid offsets, fuzzes, etc., using
    make package/<your-package>/refresh V=s
  • It is structured in a way that it is potentially upstreamable
    (e.g., subject line, commit description, etc.)
    We must try to upstream patches to reduce maintenance burden.

By using `--cert-warn` this silently ignores certificate warnings.
Removing it so the connection is properly terminated.

Reported-by: Alexander Patrakov <[email protected]>
Signed-off-by: Paul Spooren <[email protected]>
@patrakov
Copy link
Contributor

Does not work - sstp-client needs an explicit path to certificates. You need:

--ca-cert /etc/ssl/cert.pem

And still doesn't work because of #27318.

@patrakov
Copy link
Contributor

And I think there is a significant user base that connects to SSTP servers by IP with invalid or self-signed certificates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants