encryptbot 0.1.9 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: dc674c0659d95ae5e92905ecfe91021e6a86764376cd61df579c6554fcbdb16a
-  data.tar.gz: 5073b358fe513028bf63f2de5a13d6bc33b4f94a1dbe4ea78f7250c7bf58bab5
+  metadata.gz: 4d280a6a4a72287178c5b816f7e60ed395f583bce226997f6143f1fd447388d5
+  data.tar.gz: 55187351813cee1b14ea5530276a9ceded41662c945e48ac696699012e589817
 SHA512:
-  metadata.gz: f74db2322ab3a5685d55b8e51cc74d97b6a270e3c9195c707d4105753663073d6fc462993096057fc68208c4d2e9cee5a6ee8178371b351b2091500332f309df
-  data.tar.gz: 5a8d8da57ba2ada3fbad817ca78a49b58bc42a50c1b354bcf1714bfd9acc38dcc95ea39eac0ba458b24f26439af96d4f8b65187a2a14c0bb4f8f55558124531b
+  metadata.gz: fd16ff30f1fe113c1f48ee743bf06623739af349d8fb9d78bc1438469e6683a65dccf1211dff258a48a016c4417122b373f86eb57b2a0b273367c354c04b85f3
+  data.tar.gz: 5e7303718f73dd88e11637e4c57cc59707f9ba1032d0d74696c39467d35ed04ab538da45f8ce6c30a11699607286498af0ea92ac4c7f589e6bd9070a6554dd05

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    encryptbot (0.1.9)
+    encryptbot (0.2.0)
       acme-client
       aws-sdk-route53
       faraday

data/README.md

@@ -1,12 +1,41 @@
 # Encryptbot
 
-Encryptbot creates and renews your Let's Encrypt SSL certificate on Heroku allowing for multiple wildcards.
+Encryptbot create a Let's Encrypt SSL certificate with multiple wildcard domains that is managed in Heroku.
 
 The gem will:
 
-- Create Let's Encrypt
-- Add Let's Encrypt DNS Challenge TXT records to DNS provider Route 53
-- Add certificate to your Heroku SNI endpoint
+- Create a Let's Encrypt Certificate
+- Add Let's Encrypt DNS Challenge TXT records for domains managed in AWS Route 53
+- Add the certificate to a Heroku SNI endpoint
+
+## Pre-setup
+
+1. Using AWS Route 53, create a Hosted Zone
+2. Create an AWS IAM user with the following permissions and get an API access key and secret.
+
+```
+{
+    "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Sid": "VisualEditor0",
+            "Effect": "Allow",
+            "Action": "route53:ChangeResourceRecordSets",
+            "Resource": "arn:aws:route53:::hostedzone/YOUR_ZONE_NAME_ID_HERE"
+        },
+        {
+            "Sid": "VisualEditor1",
+            "Effect": "Allow",
+            "Action": "route53:GetChange",
+            "Resource": "arn:aws:route53:::change/*"
+        }
+    ]
+}
+```
+
+3. Add a CNAME called "_acme-challenege" pointing to your Route 53 name. If you're using Cloudflare, turn off proxying.
+4. You're now ready to go.
+
 
 ## Installation
 
@@ -33,7 +62,7 @@ Add an initializer file to your rails application and all applicable config sett
 Encryptbot.configure do |config|
   config.heroku_app = "heroku_app_name"
   config.heroku_token = "heroku_api_token"
-  config.acme_email = "letsencrypt_account_email"
+  config.acme_email = "letsencrypt_account_email@email.com"
   config.route53_hosted_zone_id = "Z123456"
   config.route53_acme_record_name = "_acme-challenge.acme.domain.com"
   config.route53_access_key_id = "aws_api_key"
@@ -47,11 +76,11 @@ Request initial certificate
 heroku run rails encryptbot:add_cert
 ```
 
-Once the certificate has been initially setup, you can schedule the rake task to run every 60 days.
+Once the certificate has been initially setup, you can schedule the rake task to run every 30 days.
 
 ## Contributing
 
-Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/encryptbot. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+Bug reports and pull requests are welcome on GitHub at https://github.com/danlewis/encryptbot. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
 
 ## License
 
@@ -59,4 +88,4 @@ The gem is available as open source under the terms of the [MIT License](https:/
 
 ## Code of Conduct
 
-Everyone interacting in the encryptbot project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/encryptbot/blob/master/CODE_OF_CONDUCT.md).
+Everyone interacting in the encryptbot project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/danlewis/encryptbot/blob/master/CODE_OF_CONDUCT.md).

data/lib/encryptbot/cert.rb

@@ -37,6 +37,7 @@ module Encryptbot
 
       puts "Start Authorization"
       # authorization of domains
+      failed_domain_authorizations = []
       order.authorizations.each do |authorization|
         dns_challenge = authorization.dns
         domain = authorization.domain
@@ -67,16 +68,22 @@ module Encryptbot
           dns_challenge.reload
         end
         puts "Completed authorization of #{domain}. Status: #{dns_challenge.status}"
-
+        if dns_challenge.status == 'invalid'
+          failed_domain_authorizations << domain
+        end
       end # end auth loop
 
+      if failed_domain_authorizations.any?
+        raise Encryptbot::Error::DomainAuthorizationFailedError, "Domains failed to authorize: #{failed_domain_authorizations.join(', ')}."
+      end
+
       if order.status == "invalid"
         raise Encryptbot::Error::InvalidOrderError, "Certificate order was invalid. DNS Challenge failed."
       end
 
       # Generate certificate
       puts "Generate Certificate"
-      csr = Acme::Client::CertificateRequest.new(names: @domain_names)
+      csr = Acme::Client::CertificateRequest.new(names: @domains)
       order.finalize(csr: csr)
       sleep(1) while order.status == "processing"
 

data/lib/encryptbot/exceptions.rb

@@ -13,15 +13,13 @@ module Encryptbot
     class HerokuCertificateError < EncryptbotError; end
     # Exception raised due to configuration not been setup
     class SetupError < EncryptbotError; end
-    # Exception raised when adding TXT record to Cloudflare
-    class CloudflareDNSError < EncryptbotError; end
-    # Exception raised when adding TXT record to Dyn
-    class DynDNSError < EncryptbotError; end
     # Exception raised when route 53 fails to update
     class Route53DNSError < EncryptbotError; end
     # Exception raised when unknown error
     class UnknownServiceError < EncryptbotError; end
     # Exception raised as order was failed - this happens when the DNS Challenge failed
     class InvalidOrderError < EncryptbotError; end
+    # Exception raised due to a domain failing authorization
+    class DomainAuthorizationFailedError < EncryptbotError; end
   end
 end

data/lib/encryptbot/version.rb

@@ -1,3 +1,3 @@
 module Encryptbot
-  VERSION = "0.1.9"
+  VERSION = "0.2.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: encryptbot
 version: !ruby/object:Gem::Version
-  version: 0.1.9
+  version: 0.2.0
 platform: ruby
 authors:
 - danlewis
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2021-03-10 00:00:00.000000000 Z
+date: 2021-03-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: acme-client