Skip to main content

Three steps to create a self-signed certificate in Apache for Ubuntu 11.10

It is very simple and quick to create a self-signed certificate on your development machine. Of course you would never use this on a production server because self-signed certificates are vulnerable to man in the middle attacks. 

You will need to make sure that you have the ssl-cert and libapache2-mod-gnutls packages installed.

Step One: Use the ssl-cert package to create a self-signed certificate.  This will create the certificate files in /etc/ssl which is where the Ubuntu default Apache configuration expects to find them.

make-ssl-cert generate-default-snakeoil --force-overwrite

Step Two: Active the SSL module and the default SSL site using the convenience wrappers:



a2enmod ssl


a2ensite default-ssl





Step Three: Restart Apache






service apache2 restart

















Labels:





































Comments









  1. Anonymous17 May 2013 at 14:52
    I will definitely try these steps to create a self signed certificate. I will get back to you if any problem arise. Thanks for sharing.
    digital certificate
    ReplyDelete











Post a Comment



















Popular posts from this blog





















Using Fail2Ban to protect a Varnished site from scrapers




























  I'm using Varnish to cache a fairly busy property site.  Varnish works like a bomb for normal users and has greatly improved our page load speed.   For bots that are scraping the site, presumably to add the property listings to their own site, though the cache is next to useless since the bots are sequentially trawling through the whole site.   I decided to use fail2ban to block IP's who hit the site too often.   The first step in doing so was to enable a disk based access log for Varnish so that fail2ban will have something to work with.   This means setting up varnishncsa.  Add this to your /etc/rc.local file:    varnishncsa -a -w /var/log/varnish/access.log -D -P /var/run/varnishncsa.pid     This starts up varnishncsa in daemon mode and appends Varnish access attempts to /var/log/varnish/access.log   Now edit or create /etc/logrotate.d/varnish and make an entry to rotate this access log:     /var/log/varnish/*log {         create 640 http log         compress        ...




















Post a Comment









Read more






























Translating a bit of the idea behind domain driven design into code architecture




























 I've often participated in arguments  discussions about whether thin models or thin controllers should be preferred.  The wisdom of a thin controller is that if you need to test your controller in isolation then you need to stub the dependencies of your request and response. It also violates the single responsibility principal because the controller could have multiple reasons to change.   Seemingly, the alternative is to settle on having fat models. This results in having domain logic right next to your persistence logic. If you ever want to change your persistence layer you're going to be in for a painful time. That's a bit of a cargo cult argument because honestly who does that, but it's also a violation of the single responsibility principal.   One way to decouple your domain logic from both persistence and controller is to use the "repository pattern".   Here we encapsulate domain logic into a data service. This layer deals exclusively with imple...




















Post a Comment









Read more






























Grokking PHP monolog context into Elastic




























  An indexed and searchable centralized log is one of those tools that once you've had it you'll wonder how you managed without it.      I've experienced a couple of advantages to using a central log - debugging, monitoring performance, and catching unknown problems.    Debugging  Debugging becomes easier because instead of poking around grepping text logs on servers you're able to  use a GUI to contrast and compare values between different time  ranges.   A ticket will often include sparse information about the  problem and observed error, but if you know more or less when a problem  occurred then you can check the logs of all your systems at that time.   Problem behaviour in your application can occur as a result of the  services you depend on.  A database fault will produce errors in your  application, for example.   If you log your database errors and your application errors in the same central platform then it's much more convenient to compare behaviour between...




















Post a Comment









Read more