<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lacme/tests/cert-extensions, branch v0.8.3</title>
<subtitle>Small ACME client written with process isolation and minimal privileges in mind</subtitle>
<id>http://git.guilhem.org/lacme/atom?h=v0.8.3</id>
<link rel='self' href='http://git.guilhem.org/lacme/atom?h=v0.8.3'/>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/'/>
<updated>2024-06-13T13:41:12Z</updated>
<entry>
<title>Pass `-in /dev/stdin` option to openssl(1) to avoid warning with recent versions.</title>
<updated>2024-06-13T13:41:12Z</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2024-06-13T01:33:20Z</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=bf4d2d13ffcd894c6e7765dbd366f1163c69c9e1'/>
<id>urn:sha1:bf4d2d13ffcd894c6e7765dbd366f1163c69c9e1</id>
<content type='text'>
OpenSSL 3.2 from Debian sid spews

    Warning: Reading certificate from stdin since no -in or -new option is given

without an explicit `-in /dev/stdin`.
</content>
</entry>
<entry>
<title>t/cert-extensions: Fix tr(1) range syntax.</title>
<updated>2024-06-13T13:41:12Z</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2024-06-13T12:30:30Z</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=568656b1fcb60d451b4a5313876ef0b96ae8bbfd'/>
<id>urn:sha1:568656b1fcb60d451b4a5313876ef0b96ae8bbfd</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add test suite against Let's Encrypt's staging environment.</title>
<updated>2021-02-20T19:16:29Z</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2021-02-19T22:22:15Z</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=11d971bc07ceb4359565e6611ae03a0c0134d153'/>
<id>urn:sha1:11d971bc07ceb4359565e6611ae03a0c0134d153</id>
<content type='text'>
https://letsencrypt.org/docs/staging-environment/
</content>
</entry>
</feed>
