-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
conscrypt throws java.lang.IllegalArgumentException: Unknown cipher suite supported by native code: DH-DSS-AES256-GCM-SHA384 #20
Comments
Conscrypt only works with BoringSSL. When we make a release, we will note the BoringSSL commit-ish that Conscrypt works with. |
I know. So why does AOSP pull in OpenSSL when building conscrypt instead of
BoringSSL?
…On Wed, 28 Dec 2016 at 02:34 Kenny Root ***@***.***> wrote:
Closed #20 <#20>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB2crF3azRQSs0r5KCwwWmnqUdP_w0kKks5rMT4QgaJpZM4LWCIh>
.
|
Maybe you have changed your manifest with a |
Nope, I haven't. I know it *should* be using BoringSSL, but somehow the
build seems to be prioritising OpenSSL over BoringSSL.
…On Wed, 28 Dec 2016 at 15:13 Kenny Root ***@***.***> wrote:
Maybe you have changed your manifest with a local_manifests entry. It
definitely uses BoringSSL
<https://android.googlesource.com/platform/manifest/+/master/default.xml#94>
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB2crBsy5_sKtykHaOLQ7yAJOYs6V3Vuks5rMfARgaJpZM4LWCIh>
.
|
Maybe it's picking up your host This is a conversation is more suited for a mailing list than an issue tracker, though. |
how could it possibly be the case? Is there any way I can see what it's loading? |
So I used jdb to check if org.conscrypt.NativeCrypto.isBoringSSL was true. It was indeed true - and yet get_cipher_names somehow uses OpenSSL.
|
ah, it's a result of nixos fucking with the procedure linkage table! after looking around with gdb, I got to this point:
which in assembly is
the debugging info says that it points to the one included in libconscrypt_openjdk_jni.so, but nixos modifies ELFs to take into account the different directory layout. so it presumably scans the ELF for symbols and then fails to recognise the various BoringSSL functions are statically linked, and rewrites their addresses to point to OpenSSL's methods. |
conscrypt fails while building AOSP under NixOS.
OS: NixOS
AOSP version: Copperhead 7.1.1r6 aosp_marlin
OpenJDK versions tried: 112b15, 122b3
Installed OpenSSL versions tried: OpenSSL 1.0.2j, OpenSSL 1.1.0, LibreSSL 2.5.0
make showcommands -j4
The text was updated successfully, but these errors were encountered: