1. 22 Jan, 2021 1 commit
  2. 12 Jun, 2019 5 commits
  3. 07 Jun, 2019 1 commit
  4. 30 May, 2019 1 commit
  5. 16 May, 2019 1 commit
    • Jiyong Park's avatar
      Change SDK version numbers to 29 · cec808f8
      Jiyong Park authored
      Q is now officially 29. To target the timezone APEX exactly to Q
      devices, the sdk version numbers are all set to 29.
      Bug: 131128233
      Test: m and check the sdk version numbers
      Change-Id: Ic3e2891a26ead3bacf3e8946bdabe3d1a253408f
  6. 05 May, 2019 2 commits
  7. 02 May, 2019 1 commit
  8. 30 Apr, 2019 1 commit
    • Pete Bentley's avatar
      Make libjavacrypto only required for hostdex builds of conscrypt. · 02d06db5
      Pete Bentley authored
      Workaround to prevent libjavacrypto being pulled into /system/lib rather
      than APEX on target builds due to b/124476339.  There is already
      a workaround in apex/Android.bp to ensure libjavacrypto is installed
      in the APEX, which is the only required copy.
      Bug: 123925742
      Test: m && flashall; Manually verify no libjavacrypto in /system
      Test: art/tools/run-libcore-tests.sh --mode=host --variant=X64
      Change-Id: If8ca646755e7f9ca38dc60b67bcdb7540a394523
      Merged-In: If8ca646755e7f9ca38dc60b67bcdb7540a394523
  9. 27 Apr, 2019 1 commit
    • Akshay's avatar
      Update version number to 220000000 · a1776831
      Akshay authored
      Update version number to 220000000. The Beta 3 builds (which are in dogfood and public beta) will receive modules via the Play Store with version numbers 210000000. Hence, we must bump the version in qt-dev and hence beta 4.
      BUG: 131240537
      Change-Id: I829b091f2400fd77c815f6dc452fe87fd16b14c4
  10. 11 Apr, 2019 1 commit
  11. 10 Apr, 2019 2 commits
  12. 09 Apr, 2019 1 commit
  13. 04 Apr, 2019 2 commits
    • Akshay's avatar
      Update version number to 0210000000. · 1b66a708
      Akshay authored
      The Beta 2 builds (which are in dogfood an public beta) will receive modules via the Play Store with version numbers 0200000000. Hence, we must bump the version in qt-dev and hence beta 3. This is so that prebuilts in the beta 3 OTA will be higher than any Play Store pushes on beta 2. We are bumping it by 10000000 so that we have name space to do intermediate cherrypick builds if needed.
      Bug: 129977903
      Change-Id: I023454097f9d2948e68e91ec70dc2ed844075fde
    • android-build-team Robot's avatar
      Snap for 5434517 from b1c569f3 to qt-release · 4a16a1b5
      android-build-team Robot authored
      Change-Id: Ie53dbe3b1279f6ba16269b072bc968e6cce1f71a
  14. 03 Apr, 2019 2 commits
  15. 02 Apr, 2019 7 commits
    • Adam Vartanian's avatar
      Merge upstream master am: 87f65753 am: 30acccc8 · 8f155d74
      Adam Vartanian authored
      am: af20f996
      Change-Id: I735bdea91958b59f0cb1ea8a3853787d20f373a0
    • Adam Vartanian's avatar
      Merge upstream master am: 87f65753 · af20f996
      Adam Vartanian authored
      am: 30acccc8
      Change-Id: I6a0c81c40553ae21dee1a91aca99962e858b3eda
    • Adam Vartanian's avatar
      Merge upstream master · 30acccc8
      Adam Vartanian authored
      am: 87f65753
      Change-Id: Ibdbd53f049563602590b99f6eae5af6802fd2fd0
    • Bill Rassieur's avatar
      Merge master@5428150 into git_qt-dev-plus-aosp. · 99cda942
      Bill Rassieur authored
      Change-Id: I6d05a12e5a5dd1dfca71556d64a36d93b45ec929
      BUG: 129345239
    • Adam Vartanian's avatar
      Merge upstream master · 87f65753
      Adam Vartanian authored
      Relevant changes:
      * Add missing license declarations
      * Omit TLS_FALLBACK_SCSV for TLS 1.2+
      * Add alias for ChaCha20-Poly1305
      Test: cts -m CtsLibcoreTestCases
      Test: cts -m CtsLibcoreOkHttpTestCases
      Change-Id: I321386ca92a58351bc92f8306a575c85a9821400
    • Adam Vartanian's avatar
      Add ChaCha20-Poly1305 as an alias for ChaCha20/Poly1305/NoPadding (#653) · b2c5f501
      Adam Vartanian authored
      Some other providers appear to have used ChaCha20-Poly1305 as the
      identifier for this cipher, so support it for compatibility.
    • Adam Vartanian's avatar
      Don't send TLS_FALLBACK_SCSV if max version is >= 1.2 (#651) · e0e1be74
      Adam Vartanian authored
      TLS_FALLBACK_SCSV protects against downgrade attacks when clients
      implement a version fallback independent of TLS version
      negotiation, but if it's set on a non-fallback connection
      attempt, it will prevent an otherwise-safe connection if the
      server supports a version higher than the client does.  Because
      the default OpenJDK TLS implementation doesn't support
      TLS_FALLBACK_SCSV, some developers mistakenly enable it on every
      connection due to thinking it's a normal cipher suite, which is
      starting to cause issues when servers upgrade to TLS 1.3.
      We can obviously omit it on connections with a max version of 1.3,
      since that's Conscrypt's max version, so it can't be a version
      As far as connections with a max version of 1.2 are concerned, this
      type of fallback is generally not needed any longer, since TLS
      1.3-supporting servers should all perform version negotiation
      properly.  (Chrome and Firefox have both disabled version fallback
      entirely.)  Thus TLS_FALLBACK_SCSV's presence in connections with a
      max version of 1.2 is significantly more likely to be a
      misconfiguration than a true fallback indication.
      We continue to include the cipher suite for connections with a max
      version of 1.1 or lower.  First, flaws in pre-1.2 versions are more
      likely to exist than flaws in 1.2, so the benefit of flagging
      downgrades to those versions are higher.  As well, fallback is most
      likely to be useful when dealing with buggy TLS 1.2 servers.
      Fixes #574
  16. 30 Mar, 2019 1 commit
  17. 29 Mar, 2019 3 commits
  18. 28 Mar, 2019 1 commit
  19. 27 Mar, 2019 6 commits