# Let's Encrypt New Intermediate Certificates

**URL:** <https://community.letsencrypt.org/t/lets-encrypt-new-intermediate-certificates/209498>\
**Category:** Issuance Tech\
**Created:** [December 4, 2023, 7:36pm UTC](https://community.letsencrypt.org/t/lets-encrypt-new-intermediate-certificates/209498 "2023-12-04T19:36:56Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![petercooperjr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/petercooperjr/32/84698_2.png) [@petercooperjr](https://community.letsencrypt.org/u/petercooperjr)\
**Post date:** [December 6, 2023, 1:40am UTC](https://community.letsencrypt.org/t/lets-encrypt-new-intermediate-certificates/209498/28 "2023-12-06T01:40:22Z")

</div>

> [@aarongable](#):
>
> > [@petercooperjr](#):
> >
> > Is there any consideration that there's some specific old version of Android (7.0) that can handle P-256 signatures and not P-384 signatures?
> 
> The existing E1 and E2 keys would run into this already, so this isn't an issue for this upcoming key ceremony to care about, this is an issue for the "ECDSA For All" change to care about.

Perhaps, but I _thought_ that this issue was one of the main reasons people might not want all their ECDSA certs signed by a P-384 ECDSA chain, which is why the current system might still be opt-in-only for now (though I may just be wildly speculating). Some people might want an ECDSA chain that only uses P-256 signatures, which they can get from other CAs (I think) but not with the Let's Encrypt current (or these proposed) intermediates.

---

_[View the full topic](https://community.letsencrypt.org/t/lets-encrypt-new-intermediate-certificates/209498)._