Change private openssl/security repository url

Change security repository url in HOWTO-handle-security-issue.md,
HOWTO-make-a-release.md,HOWTO-stage-a-release.md and
HOWTO-publish-a-release.md.

Reviewed-by: Richard Levitte <[email protected]>
Reviewed-by: Tomas Mraz <[email protected]>
(Merged from #219)

Author: quarckster

HOWTO-handle-security-issue.md

@@ -614,7 +614,7 @@ Finish by publishing all the applicable
 [Special handling of vendors]: #special-handling-of-vendors
 
 [private otc/security repository]: https://github.openssl.org/otc/security
-[private openssl/security repository]: https://github.openssl.org/openssl/security
+[private openssl/security repository]: https://github.com/openssl/security
 [private openssl/premium repository]: https://github.openssl.org/openssl/premium
 [private openssl/openssl repository]: https://github.openssl.org/openssl/openssl
 [private omc/data repository]: https://github.openssl.org/omc/data

HOWTO-make-a-release.md

@@ -42,7 +42,7 @@ You must have access to the following repositories:
     a public release, which are those that haven't reached End-Of-Life
     yet.
 
--   `git@github.openssl.org:openssl/security.git`
+-   `git@github.com:openssl/security.git`
 
     This is the security source repository, where security fixes are
     staged before being publically released.  It is used as source
@@ -70,7 +70,7 @@ version released.
     repository, which is one of:
 
     -   `git clone [email protected]:openssl/openssl.git`
-    -   `git clone git@github.openssl.org:openssl/security.git`
+    -   `git clone git@github.com:openssl/security.git`
     -   `git clone [email protected]:openssl/premium.git`
 
 ## Freeze the source repository

HOWTO-publish-a-release.md

@@ -53,7 +53,7 @@ You must have access to the following repositories:
         a public release, which are those that haven't reached End-Of-Life
         yet.
 
-    -   `git@github.openssl.org:openssl/security.git`
+    -   `git@github.com:openssl/security.git`
 
         This is the security source repository, where security fixes are
         staged before being publically released.  It is used as source
@@ -95,7 +95,7 @@ in this section.
 
 *NOTE*  This section should only be performed for public releases, i.e.
 releases made from `[email protected]:openssl/openssl.git` or
-`git@github.openssl.org:openssl/security.git`.
+`git@github.com:openssl/security.git`.
 
 Everything in this section is to be done as the `openssl` user on
 `dev.openssl.org`, so if you haven't done that yet, you now *must* perform
@@ -131,7 +131,7 @@ visiting the release URL that corresponds to the source repository that the
 release was made from, or by using [the Github CLI tool](https://cli.github.com/]:
 
 -   For releases from `[email protected]:openssl/openssl.git` or
-    `git@github.openssl.org:openssl/security.git`:
+    `git@github.com:openssl/security.git`:
 
     URL: https://github.com/openssl/openssl/releases
 

HOWTO-stage-a-release.md

@@ -62,7 +62,7 @@ You must have access to the following repositories:
         a public release, which are those that haven't reached End-Of-Life
         yet.
 
-    -   `git@github.openssl.org:openssl/security.git`
+    -   `git@github.com:openssl/security.git`
 
         This is the security source repository, where security fixes are
         staged before being publically released.  It is used as source
@@ -105,7 +105,7 @@ address, `[email protected]`.  To test this, try to log in with sftp:
     repository, which is one of:
 
     -   `git clone [email protected]:openssl/openssl.git`
-    -   `git clone git@github.openssl.org:openssl/security.git`
+    -   `git clone git@github.com:openssl/security.git`
     -   `git clone [email protected]:openssl/premium.git`
 
 -   If you're staging multiple releases from one repository in one go, there