Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Let's Encrypt gets automation

Unblocking the open CA's client process

Hoping to expand the pool of Let's Encrypt testers, TrueCrypt audit project co-founder Kenneth White has run up a set of scripts to automate the process of installing certificates under the Mozilla-backed open CA.

White, co-director of the Open Crypto Audit Project, has posted the work at Github, here. He explains that the project is quite simple, consisting of Python scripts to “stand up the official Let's Encrypt certificate management ACME client tool” in the target environments.

These include Debian, Amazon's Linux (for AWS), CentOS, RedHat and FreeBSD.

White says while he considers Let's Encrypt to be an important project, at this early stage of development, the official client “can be fragile and error-prone on some systems”.

Having had to batter his own head against the client, White writes, he says he cleaned up the process in his scripts to make Let's Encrypt more accessible to other users.

He notes that Let's Encrypt should still be considered in-development, and warns against running either the Let's Encrypt client or his scripts in production systems:

“LE is still in beta and has some rough edges”, White notes, “including silently invoking sudo and installing quite a few development packages”.

Let's Encrypt was established at the end of 2014 by Mozilla with the backing of Cisco and the Electronic Frontier Foundation. Its aim is to give a push to the encrypt-everything movement, by making certificates available to those who can't afford to buy certificates from commercial CAs.

The group issued its first certificates in July this year, and in October was recognised as a CA by the world's major browser vendors.

Let's Encrypt is currently running as an invitational beta. ®

Similar topics

TIP US OFF

Send us news


Other stories you might like