Bug#928469: ITP: uacme -- lightweight client for the RFC8555 ACMEv2 protocol

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#928469: ITP: uacme -- lightweight client for the RFC8555 ACMEv2 protocol

Nicola Di Lieto-2
Package: wnpp
Severity: wishlist
Owner: 'Nicola Di Lieto' <[hidden email]>

*Package Name    : uacme
  Version         : 1.0.8
  Upstream Author : Nicola Di Lieto
*URL             : https://github.com/ndilieto/uacme
*License         : GPL-3.0+
  Description     : lightweight client for the RFC8555 ACMEv2 protocol

  uacme is a lightweight client for the RFC8555 ACMEv2 protocol, written
  in plain C code with minimal dependencies (libcurl and one of GnuTLS,
  OpenSSL or mbedTLS). The ACMEv2 protocol allows a Certificate
  Authority (https://letsencrypt.org is a popular one) and an applicant
  to automate the process of verification and certificate issuance. The
  protocol also provides facilities for other certificate management
  functions, such as certificate revocation.
  .
  I have tentatively packaged this already in the git repository, using
  the DEP-14 branch layout at http://dep.debian.net/deps/dep14 - look at
  the debian/master branch. Not sure what to do now to get it into
  debian.

Greetings,
Nicola
 

Reply | Threaded
Open this post in threaded view
|

Bug#928469: Bug #928469: ITP: uacme -- lightweight client for the RFC8555 ACMEv2 protocol

Nicola Di Lieto-2
Package: wnpp
Severity: wishlist
Owner: 'Nicola Di Lieto' <[hidden email]>

*Package Name    : uacme
 Version         : 1.0.14
 Upstream Author : Nicola Di Lieto
*URL             : https://github.com/ndilieto/uacme
*License         : GPL-3.0+
 Description     : lightweight client for the RFC8555 ACMEv2 protocol

 uacme is a lightweight client for the RFC8555 ACMEv2 protocol, written
 in plain C code with minimal dependencies (libcurl and one of GnuTLS,
 OpenSSL or mbedTLS). The ACMEv2 protocol allows a Certificate
 Authority (https://letsencrypt.org is a popular one) and an applicant
 to automate the process of verification and certificate issuance. The
 protocol also provides facilities for other certificate management
 functions, such as certificate revocation.
 .
 I have tentatively packaged this already in the git repository, using
 the DEP-14 branch layout at http://dep.debian.net/deps/dep14 - look at
 the debian/master branch. Not sure what to do now to get it into
 debian.

Reply | Threaded
Open this post in threaded view
|

Bug#928469: Bug #928469: ITP: uacme -- lightweight client for the RFC8555 ACMEv2 protocol

Vincent Bernat-3
 ❦ 15 juin 2019 07:14 +02, Nicola Di Lieto <[hidden email]>:

> I have tentatively packaged this already in the git repository, using
> the DEP-14 branch layout at http://dep.debian.net/deps/dep14 - look at
> the debian/master branch. Not sure what to do now to get it into
> debian.

Look at https://mentors.debian.net/sponsors. Notably, there is a "Let's
Encrypt" team ([hidden email]....).
--
Use the "telephone test" for readability.
            - The Elements of Programming Style (Kernighan & Plauger)

signature.asc (847 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#928469: Bug #928469: ITP: uacme -- lightweight client for the RFC8555 ACMEv2 protocol

Nicola Di Lieto-2
On Sat, Jun 15, 2019 at 07:42:12AM +0200, Vincent Bernat wrote:
>Look at https://mentors.debian.net/sponsors. Notably, there is a "Let's
>Encrypt" team ([hidden email]....).

Hello Vincent,

many thanks for your reply. I already emailed
[hidden email] at the end of April and have so far
received no reply. What else can I do?

Thanks
Nicola

Reply | Threaded
Open this post in threaded view
|

Bug#928469: Bug #928469: ITP: uacme -- lightweight client for the RFC8555 ACMEv2 protocol

Vincent Bernat-3
 ❦ 15 juin 2019 20:39 +02, Nicola Di Lieto <[hidden email]>:

>>Look at https://mentors.debian.net/sponsors. Notably, there is a "Let's
>>Encrypt" team ([hidden email]....).
>
> Hello Vincent,
>
> many thanks for your reply. I already emailed
> [hidden email] at the end of April and have so
> far received no reply. What else can I do?

Then, you can do create a "Request For Sponsor" (RFS).
--
Keep it simple to make it faster.
            - The Elements of Programming Style (Kernighan & Plauger)

signature.asc (847 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#928469: Bug #928469: ITP: uacme -- lightweight client for the RFC8555 ACMEv2 protocol

Nicola Di Lieto-2
On Sat, Jun 15, 2019 at 08:48:09PM +0200, Vincent Bernat wrote:
>Then, you can do create a "Request For Sponsor" (RFS).

Hi Vincent, thanks again. Here is the RFS:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930595