public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Heartbleed fix - question re: replacing self-signed certs with real ones
Date: Wed, 16 Apr 2014 06:52:24 -0400	[thread overview]
Message-ID: <534E60E8.6050502@libertytrek.org> (raw)

Hi all,

I've taken this opportunity to prod the boss to let me buy some real 
certs for our few self-hosted mail services. Until now, we've used 
self-signed certs.

My question is, what exactly is the correct procedure for doing this?

Also, do I still need to do the step I've been seeing:

Step: 2

Delete SSL key set

     Now, make out a list of websites that are equipped with SSL
     certificates.
     After that, delete all SSL keys, private and CSR key
     Finally, create a new private key and CSR key for each of your
     website. However, remember that your keys should be of 2048-bit key
     length.

?

Or will simply replacing my self-signed certs with the new real ones be 
good enough?

Thanks


             reply	other threads:[~2014-04-16 10:53 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 10:52 Tanstaafl [this message]
2014-04-16 11:14 ` [gentoo-user] Heartbleed fix - question re: replacing self-signed certs with real ones Matti Nykyri
2014-04-16 17:56   ` Tanstaafl
2014-04-17  5:59     ` Matti Nykyri
2014-04-17  6:10     ` Mick
2014-04-17 14:40       ` Matti Nykyri
2014-04-17 15:49         ` Mick
2014-04-17 16:54           ` Joe User
2014-04-17 18:43           ` Matti Nykyri
2014-04-17 20:17             ` [gentoo-user] " walt
2014-04-18  5:50               ` Matti Nykyri
2014-04-18 14:27                 ` Dale
2014-04-18 16:45                   ` Mick
2014-04-18 18:08                     ` Dale
2014-04-18 19:01                       ` Mick
2014-04-18 20:27                         ` Dale
2014-04-18 23:33                           ` Mick
2014-04-19 15:29                             ` Dale
2014-04-19 15:43                               ` Matti Nykyri
2014-04-19 19:33                                 ` Dale
2014-04-19 19:43                                   ` Joe User
2014-04-19 21:23                                     ` Dale
2014-04-20  0:18                                 ` Peter Humphrey
2014-04-20  8:49                                   ` Mick
2014-04-20  9:21                                     ` Matti Nykyri
2014-04-20 10:26                                       ` Mick
2014-04-19 16:11                               ` Mick
2014-04-19 18:41                                 ` Dale
2014-04-20  8:27                                   ` Mick
2014-04-20  9:10                                     ` Dale
2014-04-20 12:38                                       ` Mick
2014-04-20 16:40                                         ` Matti Nykyri
2014-04-20 17:20                                           ` Joe User
2014-04-21  6:57                                             ` Matti Nykyri
2014-04-20 18:36                                         ` Dale
2014-04-19 11:51             ` [gentoo-user] " Mick
2014-04-19 13:17               ` Joe User
2014-04-19 15:38                 ` Matti Nykyri
2014-04-19 16:40                   ` Joe User
2014-04-19 17:14                 ` Mick
2014-04-20 23:20                 ` Mick
2014-04-21  7:11                   ` Matti Nykyri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=534E60E8.6050502@libertytrek.org \
    --to=tanstaafl@libertytrek.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox