YantraStructure

SSL has been around for long enough you'd think that there would be agreed upon container formats. And you're right, there are. Too many standards as it happens. So this is what I know, and I'm sure others will chime in. .csr  This is a Certificate Signing Request. Some applications can generate these for submission to certificate-authorities. The actual format is PKCS10 which is defined in  RFC 2986 . It includes some/all of the key details of the requested certificate such as subject, organization, state, whatnot, as well as the  public key  of the certificate to get signed. These get signed by the CA and a certificate is returned. The returned certificate is the public  certificate  ( not  the key), which itself can be in a couple of formats. .pem  Defined in RFC's  1421  through  1424 , this is a container format that may include just the public certificate (such as with Apache installs, and CA certificate files  /etc/ssl/certs ), or may include an entire certi

After a long wait, finally Java SE Development Kit 8 is available to  download . JDK 8 has been released on  Mar,18 2014  for general availability with the many featured enhancements. You can find all the enhancements in JDK 8  here . This article will help you to Install JAVA 8 (JDK 8u25) or update on your system. Read instruction carefully for  downloading  java from Linux command line. To Install Java 8 in Ubuntu and LinuxMint read  This Article . Step 1: Download JAVA Archive Download latest Java SE Development Kit 8 release from its  official download page  or use following commands to download from shell. For 64Bit # cd /opt/ # wget --no-cookies --no-check-certificate --header "Cookie: gpw_e24=http%3A%2F%2Fwww.oracle.com%2F; oraclelicense=accept-securebackup-cookie" "http://download.oracle.com/otn-pub/java/jdk/8u25-b17/jdk-8u25-linux-x64.tar.gz" # tar xzf jdk-8u25-linux-x64.tar.gz For 32Bit # cd /opt/ # wget --no-cookies --no-check-certificate

While experimenting with  Fedora Atomic , I was looking for an elegant way to automatically deploy Atomic into an OpenStack  environment and then automatically schedule some  Docker  containers on the Atomic host. This post describes my solution. Like many other cloud-targeted distributions, Fedora Atomic runs  cloud-init  when the system boots. We can take advantage of this to configure the system at first boot by providing a  user-data  blob to Nova when we boot the instance. A  user-data  blob can be as simple as a shell script, and while we could arguably mash everything into a single script it wouldn't be particularly maintainable or flexible in the face of different pod/service/etc descriptions. In order to build a more flexible solution, we're going to take advantage of the following features: Support for  multipart MIME archives . Cloud-init allows you to pass in multiple files via  user-data  by encoding them as a multipart MIME archive. Support for a  cu

This article discusses four ways to make a Docker container appear on a local network. These are not suggested as practical solutions, but are meant to illustrate some of the underlying network technology available in Linux. If you were actually going to use one of these solutions as anything other than a technology demonstration, you might look to the  pipework  script, which can automate many of these configurations. Goals and Assumptions In the following examples, we have a host with address 10.12.0.76 on the 10.12.0.0/21 network. We are creating a Docker container that we want to expose as 10.12.0.117. I am running Fedora 20 with Docker 1.1.2. This means, in particular, that my  utils-linux  package is recent enough to include the  nsenter  command. If you don't have that handy, there is a convenient Docker recipe to build it for you at jpetazzo/nsenter  on GitHub. A little help along the way In this article we will often refer to the PID of a docker container. In