Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[tls] X25519MLKEM enabled as default for all platforms #935

Open
Chilledheart opened this issue May 5, 2024 · 0 comments
Open

[tls] X25519MLKEM enabled as default for all platforms #935

Chilledheart opened this issue May 5, 2024 · 0 comments
Labels
feature

Comments

@Chilledheart
Copy link
Owner

image

https://chromestatus.com/feature/5257822742249472
@Chilledheart Chilledheart mentioned this issue Sep 19, 2024
Closed
@Chilledheart Chilledheart changed the title [tls] X25519Kyber768 enabled as default for android and ios [tls] X25519Kyber768 enabled as default for all platforms Sep 28, 2024
@Chilledheart Chilledheart mentioned this issue Oct 7, 2024
Open
Chilledheart added a commit that referenced this issue Oct 7, 2024
@Chilledheart
tls: Add a flag to use ML-KEM instead of Kyber
23473fc 
The flag is disabled by default for now. We'll enable it by default
after server early adopters have had time to deploy the new codepoint.

ML-KEM and Kyber are very similar, so the compatibility and
performance risks between the two are expected to be identical.
Thus, to minimize interruption to enterprise administrators,
ML-KEM is still gated on the same flags as Kyber was. The new flag
changes the meaning of the old flags to gate Kyber instead.

See https://chromium-review.googlesource.com/c/chromium/src/+/5823718

Related to #935.
@Chilledheart Chilledheart mentioned this issue Oct 7, 2024
Merged
Chilledheart added a commit that referenced this issue Oct 7, 2024
@Chilledheart
tls: Add a flag to use ML-KEM instead of Kyber
ef9fc9d 
The flag is disabled by default for now. We'll enable it by default
after server early adopters have had time to deploy the new codepoint.

ML-KEM and Kyber are very similar, so the compatibility and
performance risks between the two are expected to be identical.
Thus, to minimize interruption to enterprise administrators,
ML-KEM is still gated on the same flags as Kyber was. The new flag
changes the meaning of the old flags to gate Kyber instead.

See https://chromium-review.googlesource.com/c/chromium/src/+/5823718
and https://boringssl-review.googlesource.com/c/boringssl/+/70547.

Related to #935.
Chilledheart added a commit that referenced this issue Oct 7, 2024
@Chilledheart
tls: Add a flag to use ML-KEM instead of Kyber
24ef7b4 
The flag is disabled by default for now. We'll enable it by default
after server early adopters have had time to deploy the new codepoint.

ML-KEM and Kyber are very similar, so the compatibility and
performance risks between the two are expected to be identical.
Thus, to minimize interruption to enterprise administrators,
ML-KEM is still gated on the same flags as Kyber was. The new flag
changes the meaning of the old flags to gate Kyber instead.

See https://chromium-review.googlesource.com/c/chromium/src/+/5823718
and https://boringssl-review.googlesource.com/c/boringssl/+/70547.

Related to #935.
Chilledheart added a commit that referenced this issue Oct 7, 2024
@Chilledheart
tls: Add a flag to use ML-KEM instead of Kyber
99c6715 
The flag is disabled by default for now. We'll enable it by default
after server early adopters have had time to deploy the new codepoint.

ML-KEM and Kyber are very similar, so the compatibility and
performance risks between the two are expected to be identical.
Thus, to minimize interruption to enterprise administrators,
ML-KEM is still gated on the same flags as Kyber was. The new flag
changes the meaning of the old flags to gate Kyber instead.

See https://chromium-review.googlesource.com/c/chromium/src/+/5823718
and https://boringssl-review.googlesource.com/c/boringssl/+/70547.

Related to #935.
@Chilledheart Chilledheart changed the title [tls] X25519Kyber768 enabled as default for all platforms [tls] X25519MLKEM enabled as default for all platforms Oct 8, 2024
Chilledheart added a commit that referenced this issue Oct 15, 2024
@Chilledheart
android: use -O3 instead of -Os for gh releases
fe378be 
Related to #935.
Chilledheart added a commit that referenced this issue Oct 15, 2024
@Chilledheart
android: use -O3 instead of -Os for gh releases
3c7ca06 
according to performance benchmark, some tls ciphers behaves twice
faster with O3 in place of Os.

As side effect, binary increases slightly (aka 0.4Mib).

  $ 7z l yass-android-release-arm64-1.15.0-3-d164f433.apk|grep '\.so'
  1981-01-01 01:01:02 .....      1454640       442424  lib/arm64-v8a/libcrashpad_handler.so
  1981-01-01 01:01:02 .....      6381040      2517657  lib/arm64-v8a/libyass.so
  $ 7z l yass-android-release-arm64-1.15.0-3-fe378beb.apk|grep '\.so'
  1981-01-01 01:01:02 .....      1454640       442424  lib/arm64-v8a/libcrashpad_handler.so
  1981-01-01 01:01:02 .....      6786760      2731654  lib/arm64-v8a/libyass.so

No change when compressed as apk format.

  -rw-r--r--@ 1 hky  staff    11M Oct 16 05:20 yass-android-release-arm64-1.15.0-3-d164f433.apk
  -rw-r--r--@ 1 hky  staff    11M Oct 16 05:21 yass-android-release-arm64-1.15.0-3-fe378beb.apk

Related to #935.
Chilledheart added a commit that referenced this issue Oct 15, 2024
@Chilledheart
android: use -O3 instead of -Os for gh releases
f4f09f9 
according to performance benchmark, some tls ciphers behaves twice
faster with O3 in place of Os.

As side effect, binary increases slightly (aka 0.4Mib).

    $ 7z l yass-android-release-arm64-1.15.0-3-d164f433.apk|grep '\.so'
    1981-01-01 01:01:02 .....      1454640       442424  lib/arm64-v8a/libcrashpad_handler.so
    1981-01-01 01:01:02 .....      6381040      2517657  lib/arm64-v8a/libyass.so
    $ 7z l yass-android-release-arm64-1.15.0-3-fe378beb.apk|grep '\.so'
    1981-01-01 01:01:02 .....      1454640       442424  lib/arm64-v8a/libcrashpad_handler.so
    1981-01-01 01:01:02 .....      6786760      2731654  lib/arm64-v8a/libyass.so

No change when compressed as apk format.

    -rw-r--r--@ 1 hky  staff    11M Oct 16 05:20 yass-android-release-arm64-1.15.0-3-d164f433.apk
    -rw-r--r--@ 1 hky  staff    11M Oct 16 05:21 yass-android-release-arm64-1.15.0-3-fe378beb.apk

Related to #935.
@Chilledheart Chilledheart mentioned this issue Oct 15, 2024
Merged
Chilledheart added a commit that referenced this issue Oct 16, 2024
@Chilledheart
android: use -O3 instead of -Os for gh releases
3109078 
according to performance benchmark, some tls ciphers behaves twice
faster with O3 in place of Os.

As side effect, binary increases slightly (aka 0.4Mib).

    $ 7z l yass-android-release-arm64-1.15.0-3-d164f433.apk|grep '\.so'
    1981-01-01 01:01:02 .....      1454640       442424  lib/arm64-v8a/libcrashpad_handler.so
    1981-01-01 01:01:02 .....      6381040      2517657  lib/arm64-v8a/libyass.so
    $ 7z l yass-android-release-arm64-1.15.0-3-fe378beb.apk|grep '\.so'
    1981-01-01 01:01:02 .....      1454640       442424  lib/arm64-v8a/libcrashpad_handler.so
    1981-01-01 01:01:02 .....      6786760      2731654  lib/arm64-v8a/libyass.so

No change when compressed as apk format.

    -rw-r--r--@ 1 hky  staff    11M Oct 16 05:20 yass-android-release-arm64-1.15.0-3-d164f433.apk
    -rw-r--r--@ 1 hky  staff    11M Oct 16 05:21 yass-android-release-arm64-1.15.0-3-fe378beb.apk

Related to #935.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Chilledheart