daily pastebin goal
24%
SHARE
TWEET

Untitled

a guest Oct 27th, 2015 146 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1.                                                                                                                                                                                                                                                                
  2. Delivered-To: blakelapierre@gmail.com
  3. Received: by 10.129.41.146 with SMTP id p140csp267022ywp;
  4.         Tue, 27 Oct 2015 08:15:00 -0700 (PDT)
  5. X-Received: by 10.202.231.79 with SMTP id e76mr18356231oih.129.1445958900357;
  6.         Tue, 27 Oct 2015 08:15:00 -0700 (PDT)
  7. Return-Path: <betaprogram@letsencrypt.org>
  8. Received: from mail.letsencrypt.org ([66.133.109.36])
  9.         by mx.google.com with ESMTP id x2si3501585obg.88.2015.10.27.08.15.00
  10.         for <blakelapierre@gmail.com>;
  11.         Tue, 27 Oct 2015 08:15:00 -0700 (PDT)
  12. Received-SPF: pass (google.com: domain of betaprogram@letsencrypt.org designates 66.133.109.36 as permitted sender) client-ip=66.133.109.36;
  13. Authentication-Results: mx.google.com;
  14.        spf=pass (google.com: domain of betaprogram@letsencrypt.org designates 66.133.109.36 as permitted sender) smtp.mailfrom=betaprogram@letsencrypt.org;
  15.        dkim=pass header.i=@letsencrypt.org
  16. Date: Tue, 27 Oct 2015 08:15:00 -0700 (PDT)
  17. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=letsencrypt.org;
  18.         s=gondor; t=1445958899;
  19.         bh=zyYpN1J7c4MJQonWekJLZg1+5B8mKg7MAryo+1qJzpk=; h=Subject:From:To;
  20.         b=uZUnisFjFMy9mttR4eR+uyfHbsHXQ3uPwYn/PiTfm2SS2yVPDyDyxhQIjjVvA9j0X
  21.          IKAxk+EPr8Uo3y7U4fwioDYWtGjJ2OsXlDLdFlvt9T6IKXUH41CgX/J5khDJyvVb5M
  22.          aV3/r6hYtVtHsxiSxroLsYP/5aklLwhNLE6lORlE=
  23. Content-Type: multipart/mixed; boundary="===============9144345536937131119=="
  24. MIME-Version: 1.0
  25. Subject: Let's Encrypt Closed Beta Invite
  26. From: Let's Encrypt Beta <betaprogram@letsencrypt.org>
  27. To: blakelapierre@gmail.com
  28. Message-Id: <20151027151459.26501.79670.betaprogram@letsencrypt.org>
  29.  
  30. This is a multi-part message in MIME format.
  31. --===============9144345536937131119==
  32. Content-Type: multipart/alternative;
  33.  boundary="===============2612887529607284251=="
  34. MIME-Version: 1.0
  35.  
  36. --===============2612887529607284251==
  37. Content-Type: text/plain; charset="us-ascii"
  38. MIME-Version: 1.0
  39. Content-Transfer-Encoding: 7bit
  40.  
  41. Greetings from Let's Encrypt, blakelapierre@gmail.com.
  42.  
  43. Thank you for your interest in our beta program! We're excited to let you know that your domains (below) have been whitelisted, and you can now utilize an ACME client to obtain a certificate for them.
  44.  
  45. # Quick Start
  46.  
  47. To use Let's Encrypt's official client to obtain your real certificates, you will need to provide the production API URL on the command line:
  48.  
  49.   https://acme-v01.api.letsencrypt.org/directory.
  50.  
  51. When running the Python client (installation directions [1]), be sure to specify the --server argument with the production URL:
  52.  
  53.   git clone https://github.com/letsencrypt/letsencrypt
  54.   cd letsencrypt
  55.   ./letsencrypt-auto --agree-dev-preview --server \
  56.       https://acme-v01.api.letsencrypt.org/directory auth
  57.  
  58. If you are using a different ACME client, be sure to configure it to use the production URL in order to get valid certificates. Many clients will default to the staging URL.
  59.  
  60. ## Known Issues
  61.  
  62. There are some known issues with the official Python client posted here: https://github.com/letsencrypt/letsencrypt/wiki/Known-issues
  63.  
  64. # Renewals and Lifetimes
  65.  
  66. Certificates from Let's Encrypt are valid for 90 days. We recommend renewing them every 60 days to provide a nice margin of error. As a beta participant, you should be prepared to manually renew your certificates at that time. As we get closer to General Availability, we hope to have automatic renewal tested and working on more platforms, but for now, please play it safe and keep track.
  67.  
  68. # Rate Limiting
  69.  
  70. During this beta test we have very tight rate-limiting in place. We plan to loosen these limits as the beta proceeds.
  71.  
  72. There are two rate limits in play: Registrations/IP address, and Certificates/Domain.
  73.  
  74. Registrations/IP address limits the number of registrations you can make in a given day; currently 10. This means you should avoid deleting the /etc/letsencrypt/accounts folder, or you may not be able to re-register.
  75.  
  76. Certificates/Domain you could run into through repeated re-issuance. This limit measures certificates issued for a given combination of Top Level Domain + Domain. This means if you issue certificates for the following domains, at the end you would have what we consider 4 certificates for the domain example.com.
  77.  
  78.   1. www.example.com
  79.   2. example.com www.example.com
  80.   3. webmail.example.com ldap.example.com
  81.   4. example.com www.example.com
  82.  
  83. The limit on Certificates/Domain has a window of 60 days, to give 30 days for renewals. We know it's restrictive at present; thank you for your patience in helping us ensure Let's Encrypt is ready for the whole world.
  84.  
  85. # Certificate Transparency
  86.  
  87. Part of our transparency mission includes publicly disclosing the certificates we issue via Certificate Transparency. Your email address is not publicly disclosed.
  88.  
  89. # Helpful Information
  90.  
  91. Let's Encrypt maintainence events are posted on https://letsencrypt.status.io/ and Twitter (@letsencrypt_ops). If you need help, both the Let's Encrypt community at https://community.letsencrypt.org/ and #letsencrypt on irc.freenode.org are excellent sources of assistance.
  92.  
  93. If there are updates for Beta program participants, they will be posted at the community site at https://community.letsencrypt.org/t/beta-program-announcements/1631.
  94.  
  95. Your whitelisted domains are:
  96.  
  97.  
  98.  - instachat.io
  99.  - www.instachat.io
  100.  - 2016fan.com
  101.  - 2016fantasy.com
  102.  - www.2016fan.com
  103.  - www.2016fantasy.com
  104.  
  105. On behalf of everyone involved in Let's Encrypt, welcome to the future of the encrypted web.
  106.  
  107. # Like What We're Doing?
  108.  
  109. If you like what we're doing please consider donating to Let's Encrypt. Individual donors are critical to keeping the free certs rolling. If you can, please consider making it a recurring donation; that'd be cool of you.
  110.  
  111.   https://letsencrypt.org
  112.  
  113. # Finally
  114.  
  115. On behalf of everyone involved in Let's Encrypt, welcome to the future of the encrypted web.
  116.  
  117. Note: Please do not respond to this email. This is a one-time notification about your acceptance into the Beta Program. You will not receive further emails about our Beta Program unless you send in another application.
  118.  
  119. [1] https://letsencrypt.readthedocs.org/en/latest/using.html#installation-and-usage
  120. --===============2612887529607284251==
  121. Content-Type: text/html; charset="us-ascii"
  122. MIME-Version: 1.0
  123. Content-Transfer-Encoding: 7bit
  124.  
  125. <p>Greetings from Let's Encrypt, blakelapierre@gmail.com.</p>
  126.  
  127. <p>Thank you for your interest in our beta program! We're excited to let you know that your domains (below) have been whitelisted, and you can now utilize an ACME client to obtain a certificate for them.</p>
  128.  
  129. <h2>Quick Start</h2>
  130.  
  131. <p>To use Let's Encrypt's official client to obtain your real certificates, you will need to provide the production API URL on the command line:</p>
  132.  
  133. <pre>
  134.   <a href="https://acme-v01.api.letsencrypt.org/directory">https://acme-v01.api.letsencrypt.org/directory</a>
  135. </pre>
  136.  
  137. <p>When running the Python client (installation directions [<a href="https://letsencrypt.readthedocs.org/en/latest/using.html">1</a>]), be sure to specify the <tt>--server</tt> argument with the production URL:</p>
  138.  
  139. <pre>
  140.   git clone https://github.com/letsencrypt/letsencrypt
  141.   cd letsencrypt
  142.   ./letsencrypt-auto --agree-dev-preview <span style="background-color: yellow; font-weight: bold;">--server \
  143.       https://acme-v01.api.letsencrypt.org/directory</span> auth
  144. </pre>
  145.  
  146. <p>If you are using a different ACME client, be sure to configure it to use the production URL in order to get valid certificates. Many clients will default to the staging URL.</p>
  147.  
  148. <h3>Known Issues</h3>
  149.  
  150. <p>There are some known issues with the official Python client posted here: <a href="https://github.com/letsencrypt/letsencrypt/wiki/Known-issues">https://github.com/letsencrypt/letsencrypt/wiki/Known-issues</a></p>
  151.  
  152. <h2>Renewals and Lifetimes</h2>
  153.  
  154. <p>Certificates from Let's Encrypt are valid for 90 days. We recommend renewing them every 60 days to provide a nice margin of error. As a beta participant, you should be prepared to manually renew your certificates at that time. As we get closer to General Availability, we hope to have automatic renewal tested and working on more platforms, but for now, please play it safe and keep track.</p>
  155.  
  156. <h2>Rate Limiting</h2>
  157.  
  158. <p>During this beta test we have very tight rate-limiting in place. We plan to loosen these limits as the beta proceeds.</p>
  159.  
  160. <p>There are two rate limits in play: <tt>Registrations/IP address</tt>, and <tt>Certificates/Domain</tt>.</p>
  161.  
  162. <p><tt>Registrations/IP address</tt> limits the number of registrations you can make in a given day; currently 10. This means you <strong>should avoid deleting the <tt>/etc/letsencrypt/accounts</tt> folder</strong>, or you may not be able to re-register.</p>
  163.  
  164. <p><tt>Certificates/Domain</tt> you could run into through repeated re-issuance. This limit measures certificates issued for a given combination of <tt>Top Level Domain + Domain</tt>. This means if you issue certificates for the following domains, at the end you would have what we consider 4 certificates for the domain <tt>example.com</tt>.
  165.  
  166. <ol>
  167.   <li>www.example.com</li>
  168.   <li>example.com www.example.com</li>
  169.   <li>webmail.example.com ldap.example.com</li>
  170.   <li>example.com www.example.com</li>
  171. </ol>
  172.  
  173. The limit on <tt>Certificates/Domain</tt> has a window of 60 days, to give 30 days for renewals. We know it's restrictive at present; thank you for your patience in helping us ensure Let's Encrypt is ready for the whole world.</p>
  174.  
  175. <h2>Certificate Transparency</h2>
  176.  
  177. <p>Part of our transparency mission includes publicly disclosing the certificates <a href="https://crt.sh/?caid=7395">we issue</a> via <a href="https://www.certificate-transparency.org/">Certificate Transparency</a>. Your email address is not publicly disclosed.</p>
  178.  
  179. <h2>Helpful Information</h2>
  180.  
  181. <p>Let's Encrypt maintainence events are posted on <a href="https://letsencrypt.status.io/">https://letsencrypt.status.io/</a> and Twitter (<a href="https://twitter.com/letsencrypt_ops">@letsencrypt_ops</a>). If you need help, both the Let's Encrypt community at <a href="https://community.letsencrypt.org/">https://community.letsencrypt.org/</a> and #letsencrypt on irc.freenode.org are excellent sources of assistance.</p>
  182.  
  183. <p>If there are updates for Beta program participants, they will be posted at the community site at <a href="https://community.letsencrypt.org/t/beta-program-announcements/1631">https://community.letsencrypt.org/t/beta-program-announcements/1631</a>.</p>
  184.  
  185. <p>Your whitelisted domains are:
  186. <ul>
  187.  
  188.   <li>instachat.io</li>
  189.   <li>www.instachat.io</li>
  190.   <li>2016fan.com</li>
  191.   <li>2016fantasy.com</li>
  192.   <li>www.2016fan.com</li>
  193.   <li>www.2016fantasy.com</li>
  194. </ul>
  195. </p>
  196.  
  197. <h2>Like What We're Doing?</h2>
  198. <p>If you like what we're doing please consider donating to Let's Encrypt. Individual donors are critical to keeping the free certs rolling. If you can, please consider making it a recurring donation; that'd be cool of you.</p>
  199.  
  200. <ol>
  201. <form action="https://www.paypal.com/cgi-bin/webscr" method="post" target="_top">
  202.   <input type="hidden" name="cmd" value="_s-xclick">
  203.   <input type="hidden" name="hosted_button_id" value="AF6VLVH49A3QN">
  204.   <input type="image" src="https://www.paypal.com/en_US/i/btn/btn_donateCC_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
  205.   <img alt="" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
  206. </form>
  207. </ol>
  208.  
  209. <h2>Finally</h2>
  210.  
  211. <p>On behalf of everyone involved in Let's Encrypt, welcome to the future of the encrypted web.</p>
  212.  
  213. <p><strong>Note:</strong> Please do not respond to this email. This is a one-time notification about your acceptance into the Beta Program. You will not receive further emails about our Beta Program unless you send in another application.</p>
  214.  
  215. <dd>
  216. [1] <a href="https://letsencrypt.readthedocs.org/en/latest/using.html#installation-and-usage">https://letsencrypt.readthedocs.org/en/latest/using.html#installation-and-usage</a>
  217. </dd>
  218. --===============2612887529607284251==--
  219.  
  220. --===============9144345536937131119==--
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
 
Top