# Trust of sslforfree.com to generate private keys

**URL:** <https://community.letsencrypt.org/t/trust-of-sslforfree-com-to-generate-private-keys/72779>\
**Category:** Client dev\
**Created:** [September 20, 2018, 8:39pm UTC](https://community.letsencrypt.org/t/trust-of-sslforfree-com-to-generate-private-keys/72779 "2018-09-20T20:39:55Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [September 20, 2018, 9:29pm UTC](https://community.letsencrypt.org/t/trust-of-sslforfree-com-to-generate-private-keys/72779/2 "2018-09-20T21:29:56Z")

</div>

> [@tdelmas](#):
>
> **Although it should be safe to use to generate a certificate if you already have a CSR**

This isn't really safe either. Due to the fact that authorizations are re-usable (currently for 30 days), it opens the opportunity for [sslforfree.com](http://sslforfree.com) to just silently\* issue an identical certificate under an alternate private key. This is because they control the ACME account key at all times.

(\* mitigated by CT logs but most users are not savvy to that)

---

_[View the full topic](https://community.letsencrypt.org/t/trust-of-sslforfree-com-to-generate-private-keys/72779)._