openwrt 19.07.3, stubby version 0.3.0-1 OpenSSL does not support configuring cipher suites ERROR #257
Comments
|
This is #240 |
This was referenced Jan 27, 2021
har-riz
added a commit
to har-riz/packages
that referenced
this issue
Feb 1, 2021
Description : Fix typo in CMAKE getdns included files, so Stubby can use TLS v1.3 with chipersuites options ON. This solve issue that's written in here : getdnsapi/stubby#240 getdnsapi/stubby#257 Signed-off-by: Harris K Kusuma <igharris.kk@gmail.com>
har-riz
added a commit
to har-riz/packages
that referenced
this issue
Feb 1, 2021
Description : Fix typo in CMAKE getdns included files, so Stubby can use TLS v1.3 with chipersuites options ON. This solve issue that's written in here : getdnsapi/stubby#240 getdnsapi/stubby#257 Signed-off-by: Harris K Kusuma <igharris.kk@gmail.com>
har-riz
added a commit
to har-riz/packages
that referenced
this issue
Feb 1, 2021
Description : Fix typo in CMAKE getdns included files, so Stubby can use TLS v1.3 with chipersuites options ON. This solve issue that's written in here : getdnsapi/stubby#240 getdnsapi/stubby#257 Signed-off-by: Harris K Kusuma <igharris.kk@gmail.com>
har-riz
added a commit
to har-riz/packages
that referenced
this issue
Feb 1, 2021
Description : Fix typo in CMAKE getdns included files, so Stubby can use TLS v1.3 with chipersuites options ON. This solve issue that's written in here : getdnsapi/stubby#240 getdnsapi/stubby#257 Signed-off-by: Harris K Kusuma <igharris.kk@gmail.com>
har-riz
pushed a commit
to har-riz/packages
that referenced
this issue
Feb 1, 2021
Description : Fix typo in CMAKE getdns included files, so Stubby can use TLS v1.3 with chipersuites options ON. This solve issue that's written in here : getdnsapi/stubby#240 getdnsapi/stubby#257 Signed-off-by: Harris K Kusuma <igharris.kk@gmail.com>
1715173329
pushed a commit
to immortalwrt/packages
that referenced
this issue
Feb 2, 2021
Description : Fix typo in CMAKE getdns included files, so Stubby can use TLS v1.3 with chipersuites options ON. This solve issue that's written in here : getdnsapi/stubby#240 getdnsapi/stubby#257 Signed-off-by: Harris K Kusuma <igharris.kk@gmail.com> Signed-off-by: CN_SZTL <cnsztl@project-openwrt.eu.org>
jonathanunderwood
pushed a commit
to jonathanunderwood/openwrt-packages
that referenced
this issue
Feb 6, 2021
Description : Fix typo in CMAKE getdns included files, so Stubby can use TLS v1.3 with chipersuites options ON. This solve issue that's written in here : getdnsapi/stubby#240 getdnsapi/stubby#257 Signed-off-by: Harris K Kusuma <igharris.kk@gmail.com>
|
I believe this can be closed. |
Grommish
pushed a commit
to Itus-Shield/packages
that referenced
this issue
Feb 15, 2021
Description : Fix typo in CMAKE getdns included files, so Stubby can use TLS v1.3 with chipersuites options ON. This solve issue that's written in here : getdnsapi/stubby#240 getdnsapi/stubby#257 Signed-off-by: Harris K Kusuma <igharris.kk@gmail.com>
codingdie
pushed a commit
to codingdie/packages
that referenced
this issue
Oct 1, 2022
Description : Fix typo in CMAKE getdns included files, so Stubby can use TLS v1.3 with chipersuites options ON. This solve issue that's written in here : getdnsapi/stubby#240 getdnsapi/stubby#257 Signed-off-by: Harris K Kusuma <igharris.kk@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi all, I am using openwrt 19.07.3 on my linksys acs 1900 (shelby) custom build from imagebuilder and I configured my dnsmasq to work with stubby according to the privacy dns guide (I set minimum TLS version 1.3 and I set cloudflare servers). The point is that during the latest packages upgrades I got the stubby updated on version 0.3.0-1 and I can't get it working anymore. I receive this error "This version of OpenSSL does not support configuring cipher suites" and the daemon doesn't start. I reviewed my config files and everything seems okay to me (no changes). The funny part is that everything seems to work fine with a previous stubby version (eg. 0.2.6). Any hints suggestion to how to fix that?
The text was updated successfully, but these errors were encountered: