acme-client | A Ruby client for the letsencrypt 's ACME protocol | Encryption library

by unixcharles Ruby Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | acme-client Summary

acme-client is a Ruby library typically used in Security, Encryption applications. acme-client has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

A Ruby client for the letsencrypt's ACME protocol.

Support

Quality

Security

License

Reuse

Support

acme-client has a low active ecosystem.

It has 444 star(s) with 99 fork(s). There are 18 watchers for this library.

It had no major release in the last 6 months.

There are 5 open issues and 77 have been closed. On average issues are closed in 226 days. There are 6 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of acme-client is current.

Quality

acme-client has 0 bugs and 0 code smells.

Security

acme-client has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

acme-client code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

acme-client is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

acme-client releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

acme-client saves you 905 person hours of effort in developing the same functionality from scratch.

It has 2067 lines of code, 162 functions and 44 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed acme-client and discovered the below as its top functions. This is intended to give you an instant insight into acme-client implemented functionality, and help decide if they suit your requirements.

Generate AES key
Loads the encrypted keychain with the given options .
Return the next key
Generates the EC2 EC2 key
Persist the storage key to disk

Get all kandi verified functions for this library.

acme-client Key Features

No Key Features are available at this moment for acme-client.

acme-client Examples and Code Snippets

No Code Snippets are available at this moment for acme-client.

Community Discussions

Trending Discussions on acme-client

Gitlab : Spawning error : "File is a symlink that does not point to a valid file (RuntimeError)"

RoR - ArgumentError when setup private key for Let's Encrypt API

TimeOut Error while obtaining SSL certificate from Lets Encrypt

Get PrivateKey from X509Certificate

QUESTION

Gitlab : Spawning error : "File is a symlink that does not point to a valid file (RuntimeError)"

Asked 2020-May-14 at 12:23

Having a working gitlab instance on an Ubuntu 18.04 server for abouth 2 months, it now refuse to swpan due to the following 2 errors in /var/log/nginx/error.log

...

ANSWER

Answered 2020-May-14 at 12:23

This is almost certainly a permissions error.

Make sure that whatever file is readable: chmod a+r /opt/gitlab/embedded/service/gitlab-rails/config/database.yml (according to the comments you already did this) AND

Make sure that all the directories are executable, which for directories allows cd'ing into that directory:

Source https://stackoverflow.com/questions/61587787

QUESTION

RoR - ArgumentError when setup private key for Let's Encrypt API

Asked 2018-Jun-20 at 13:45

I'd like to use the gem rails-letsencrypt to generate SSL certificates dynamically, with my RoR application.

I'm following the instructions, and in the step "Setup private key for Let's Encrypt API" I got an error.

after I changed the gemfile and runned install migrations, I am tried to setup private key for Let's Encrypt API. But, after answer the questions like that:

Do you want to use in production environment? [y/N]: y
Where you to save private key [/myapp/config/letsencrypt.key]: [ENTER]
Overwrite /myapp/config/letsencrypt.key? (enter "h" for help) [Ynaqh] y
What email you want to register: myname@mayemail.com

I got this error:

...

ANSWER

Answered 2018-Jun-20 at 13:45

The owner of repository creates a patch to solve. See the reference.

After that, I just updated the gem to version 0.5.5 and works fine.

Source https://stackoverflow.com/questions/50937498

QUESTION

TimeOut Error while obtaining SSL certificate from Lets Encrypt

Asked 2018-Jun-08 at 09:04

I am following rails acme-client to automate the task of obtaining certificates

Code for making CSR request

...

ANSWER

Answered 2018-Jun-07 at 12:20

Refer Last FAQ on the official website of lets encrypt

I hosted the rails app on Heroku and its all fixed.

Error could also be because I was trying to obtain certificate for url of ngrok.io

Source https://stackoverflow.com/questions/50717194

QUESTION

Get PrivateKey from X509Certificate

Asked 2017-Jun-27 at 18:39

Here is my code to generate a SSL certificate using Let's Encrypt (based on https://github.com/zero11it/acme-client):

...

ANSWER

Answered 2017-Jun-27 at 18:39

The solution was to modify the library and expose the certificate storage like this:

public CertificateStorage getCertificateStorage() { return certificateStorage; }

From here the app can get the PrivateKey

Source https://stackoverflow.com/questions/44777774

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install acme-client

Or add it to a Gemfile:.
The client is initialized with a private key and the directory of your ACME provider. LetsEncrypt's directory is https://acme-v02.api.letsencrypt.org/directory. They also have a staging endpoint at https://acme-staging-v02.api.letsencrypt.org/directory. acme-ruby expects OpenSSL::PKey::RSA or OpenSSL::PKey::EC. You can generate one in Ruby using OpenSSL. Or load one from a PEM file. See RSA and EC for documentation. If your account is already registered, you can save some API calls by passing your key ID directly. This will avoid an unnecessary API call to retrieve it from your private key.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: