…systems, and internal infrastructure.
Some of the most exciting features for our initial launch include:
signing of repositories
All repositories are served over HTTPS
Support for multiplein a single repository
Install scripts to get your repositories up and running quickly and easily
sign up and stay tuned
Sign up today and stay tuned for more to come soon
…IP addresses and then to specific ports. For example, HTTP traffic usually goes to port 80, and HTTPS traffic usually goes to port 443. While developing the AJAX requests feature, we found some requests were sent to localhost port 0. That's a rather odd place to send a request to, because not only is the browser sending a request to the computer it is running on, it is sending it to port 0, which is a reserved TCP port. However, at the time we didn't have a way to figure out what …
…across the network over a secure connection. In this case, that secure connection was provided by HTTPS using the OpenSSL library. Just like any other sensitive information in your Chef infrastructure, it is possible that this data was compromised by the Heartbleed bug. Since the private key is only transferred once, the chances of this information leaking is much lower than other objects, but that chance is still non-zero.
Another scenario in which the Heartbleed…
External Bookshelf Traffic Over HTTPS
11.1.1 defaults to the header set by the incoming , ensuring that bookshelf generated from requests to the front-end will be directed back to that front-end and be correctly proxied to the back-end service. This also ensures that all external bookshelf traffic travels over HTTPS.
Updated documentation on these changes, including the new configuration settings, is available at: http://docs.opscode.com/release/oec_11-1/config_rb_chef_server_enterprise.html …
Assuming you've followed everything above, and assuming it's all worked, you should now be able to login to the admin interface using the username 'admin' and the password you chose above. Beyond this, all that should be left is to setup necessary port access in your security group - i'm also not sure if there is any benefit to using an Elastic…
…, and 380ms for the and (instant) response. For HTTPS, we would add another two to negotiate all the required parameters: 1140ms + 760ms, or ~1900ms (5 RTTs) in total. Well, that's the theory, let's now try the theory in practice!
[ issue #401 .] The ` HTTPS` variable is now set correctly for HTTPS connections, even without setting `ssl on`. Fixes
 It is now possible to listen on both a normal and an HTTPS port.
 The `passenger-status` tool now displays rolling restart status.
's core is open source. …
…web API . Taking advantage of New Relic webhooks and the OpsGenie web , we were able to implement the integration pretty quickly.sends to a URL, and has a ( / HTTPS)
On the OpsGenie side, we've implemented an endpoint that receives the webhook requests from New Relic, and creates/closes alerts in OpsGenie. For mutual customers, using this integration , sending New Relic alerts to OpsGenie is straightforward: create …
…certificate is valid and signed by a trusted authority, the browsers indicate a successfully secured HTTPS connection.
Organization Validated SSL Certificates
The Organization Validated SSL Certificate (OV certificate) validates the domain ownership, plus organization information included in the certificate such as name, city, state and country.
The validation process is similar to the domain validated certificate, but it requires additional documentation to certify the company identity. …
Our APT repository is stored on an HTTPS server so you may need to add HTTPS support for APT: sudo apt-get install apt-transport-https
Next, create a file /etc/apt/sources.list.d/passenger.list and insert one of the following lines, depending on your distribution.
Phusion Passenger open source: deb https://oss-binaries.phusionpassenger.com/apt/passenger lucid main deb https://oss-binaries.phusionpassenger.com/apt/passenger precise main deb https://oss-binaries.phusionpassenger.com/apt/passenger …