Skip to main content

Self-signed SSL certificates for private servers

Self-signed SSL certificates aren't substitutes for commercial certificates for your publicly available servers, but they will prevent intruders from eavesdropping on or breaking into your services while you're using your service's configuration management application.

 OpenSSL comes installed in almost all Linux and BSD operating systems, except for source-based operating systems. Here's a template for making your own certificates:

 1. Generate a RSA private key of 1024 bits encrypted using triple DES:
openssl genrsa -des3 -out server.key 1024

 2. Generate a new certificate signing request (CSR) using your RSA private key:
openssl req -new -key server.key -out server.csr

Country Name (2 letter code) [default country code]: <country code>
State or Province Name (full name) [default state]: <state>
Locality Name (e.g. city) [default city]: <city>
Organization Name (e.g. company) [default company name]: <company name>
Organization Unit Name (e.g. section) [default department]: <department>
Common Name (e.g. your name) []: <hostname or domain name or fqdn>
Email Address []: <webmaster email address>

3. Generate a self-signed certificate that expires in 365 days:
openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt

Do you have a suggestion about how to improve this blog? Let's talk about it. Contact me at David.Brenner.Jr@Gmail.com or 720-584-5229.

Comments

Post a Comment

Comments to this blog will be reviewed within 72 hours. No trolling please

Popular posts from this blog

OpenStack+Ceph as Software-Defined Storage

SDS reduces the costs of the management of growing data stores by decoupling storage management from its hardware to allow for centralized management of cheaper, popular commodity hardware. The example SDS ecosystem uses open source software like OpenStack as a front-end interface on top of Ceph as the resource provider of a RADOS cluster of commodity solid-state drives. OpenStack provides user-friendly wrappers for accessing and modifying underlying Ceph storage. OpenStack comes in the form of distributed microservices with RESTful API's: Block (Cinder), File (Manila), Image (Glance), and Object (Swift). Each microservice can scale-out as a cluster of stand-alone services to accommodate the varying demands of high-growth storage. With OpenStack the underlying Ceph storage can address the block storage needs, file storage needs, image storage needs, and object storage needs of datacenters adopting open source as their new norm in an industry trend for high performace and high a
1 comment
Read more

Network traffic monitoring in Linux with Python

You can investigate suspicious activity in your network traffic by collecting relevant machine data from your endpoint. You can use the machine data to create your own analysis. Before you start your investigation you will need to determine normal activity on your endpoint. Normal activity is the scope of functionality of the software on your endpoint during periods of low activity and high activity. You will need some kind of software that periodically collects specific machine data from your endpoint like my software developed in Python that's available for free download at https://github.com/davidbrennerjr/server-stats-collector Ingest one or more of the following machine data: Application specific logs from /var/log Raw dumps from sniffing at Layers 2-3 Raw dumps from /proc of kernel data structures Raw dumps of kernel routing tables General system-wide error messages from /var/log/syslog Do you
Post a Comment
Read more

Continuous Integration (CI) Best Practices

Continuous Integration (CI) automates the building and testing of software in a test environment whenever a change is committed to a revision control system. CI performs QA testing of a change before adding it to the current working version. CI makes sure all development can be integrated into a build. CI Best Practices 1. Maintain a test environment that's a clone of the production environment. 2. Maintain a revision control system such as CVS, SVN or Git. 3. Automate the building of software and the documenting of code in the test environment. 4. Automate QA testing of a change then report that change to developers. 5. Commit changes regularly to avoid integration conflicts. 6. Monitor the revision control system for a commit then build the software before replacing the current working version. Do you have a suggestion about how to improve this blog? Let's talk about it. Contact me at David.Brenner.Jr@Gmail.com or 720-584-5229.
Post a Comment
Read more