https

Author: mbax

docs/advanced/ecdsa.md

@@ -94,23 +94,23 @@ server sends an `CAP ACK`, authentication can begin.
 The mechanism makes use of the NIST P-256 curve (`NID_X9_62_prime256v1` in OpenSSL) which
 (per the name) is defined over a 256 bit prime finite field. The parameters for this curve
 are available [from the NSA](https://www.nsa.gov/ia/_files/nist-routines.pdf) in section 4.3.
-The curve itself doesn't fit the [SafeCurves requirements](http://safecurves.cr.yp.to/).
+The curve itself doesn't fit the [SafeCurves requirements](https://safecurves.cr.yp.to/).
 
 Atheme is the only IRC services software that appears to implement this authentication method.
  Atheme's implementation requires that:
 
 * Users make use of the `/msg NickServ SET PUBKEY <pubkey>` command to tell the services
 package their public key
     * `<pubkey>` in this case is the **point compressed** X9.62 representation of the public
-     key which is then base64 encoded. Please see section 2.3.3 of the [SEC1](http://www.secg.org/sec1-v2.pdf)
+     key which is then base64 encoded. Please see section 2.3.3 of the [SEC1](https://www.secg.org/sec1-v2.pdf)
      spec for more information. Public keys making use of the uncompressed or hybrid forms will
      **not work**. Java users may wish to implement their own method for applying point compression
      since it is unavailable in the standard library. See the implementation in [KICL](https://github.com/KittehOrg/KittehIRCClientLib/commit/448ae6bf18956b5a38e0da8f87486c5db85db880).
 
 #### Step 1 - Begin authentication
 
 The client sends `AUTHENTICATE ECDSA-NIST256P-CHALLENGE` to request that the authentication
-process be started. See the [SASL documentation](http://ircv3.net/specs/extensions/sasl-3.1.html)
+process be started. See the [SASL documentation](https://ircv3.net/specs/extensions/sasl-3.1.html)
 for more information on the SASL process.
 
 #### Step 2 - Wait for server acknowledgement

docs/advanced/sasl.md

@@ -1,12 +1,12 @@
 KICL supports using SASL to authenticate with an IRC server. As described in the
-[IRCv3.1 spec](http://ircv3.net/specs/extensions/sasl-3.1.html), SASL allows the client to authenticate using a SASL
+[IRCv3.1 spec](https://ircv3.net/specs/extensions/sasl-3.1.html), SASL allows the client to authenticate using a SASL
 mechanism and the `AUTHENTICATE` command. The client must have requested the `sasl` capability to be able to use the
 AUTHENTICATE command.
 
 KICL's SASL support can be configured by calling the `Client#getAuthManager` method which returns an
-[AuthManager](http://kittehorg.github.io/KittehIRCClientLib/org/kitteh/irc/client/library/auth/AuthManager.html). The
+[AuthManager](https://kittehorg.github.io/KittehIRCClientLib/org/kitteh/irc/client/library/auth/AuthManager.html). The
 manager can be used to manage authentication protocols. For SASL, there are currently three available authentication
-protocols which [extend](http://kittehorg.github.io/KittehIRCClientLib/org/kitteh/irc/client/library/auth/protocol/class-use/AbstractSaslProtocol.html)
+protocols which [extend](https://kittehorg.github.io/KittehIRCClientLib/org/kitteh/irc/client/library/auth/protocol/class-use/AbstractSaslProtocol.html)
 the `AbstractSaslProtocol` class. It's also possible to add [non-SASL](alt_auth.md) authentication protocols.
 
 Protocols can be added by calling the `AuthManager#addProtocol` method, for example:

docs/advanced/sts.md

@@ -23,7 +23,7 @@ a secure connection if they haven't yet rolled out TLS.
 
 To use STS, the client needs some way to persist information about the policies it encounters during the connection
 process. Within the codebase, an interface
-[org.kitteh.irc.client.library.feature.sts.StsStorageManager](http://kittehorg.github.io/KittehIRCClientLib/org/kitteh/irc/client/library/feature/sts/StsStorageManager.html)
+[org.kitteh.irc.client.library.feature.sts.StsStorageManager](https://kittehorg.github.io/KittehIRCClientLib/org/kitteh/irc/client/library/feature/sts/StsStorageManager.html)
 is available which you can implement yourself for complete control over policy storage.
 
 Alternatively, a default class (currently `StsPropertiesStorageManager`) which stores the STS policies in a properties

docs/events.md

@@ -37,7 +37,7 @@ listen to the exact class, utilize the annotation's `rejectSubtypes` value.
 
 ## KICL Events
 KICL events cover nearly all common IRC interactions. See the
-[JavaDocs](http://kittehorg.github.io/KittehIRCClientLib/) for the complete listing.
+[JavaDocs](https://kittehorg.github.io/KittehIRCClientLib/) for the complete listing.
 
 For all situations where KICL doesn't provide the event you need, you can listen to the server's
 messages. The `ClientReceiveCommandEvent` and `ClientReceiveNumericEvent` classes let you listen

docs/index.md

@@ -107,7 +107,7 @@ public class FriendlyBot {
 
 ## More information
 
-Consult the [JavaDocs](http://kittehorg.github.io/KittehIRCClientLib/) to answer most questions.
+Consult the [JavaDocs](https://kittehorg.github.io/KittehIRCClientLib/) to answer most questions.
 
 Visit us in `#kitteh.org` on `irc.esper.net` for a chat (click
 [here](https://webchat.esper.net/?nick=kicl_...&channels=%23kitteh.org) to join), or check out the

src/main/java/org/kitteh/irc/client/library/feature/auth/SaslEcdsaNist256PChallenge.java

@@ -206,7 +206,7 @@ protected void toString(final ToStringer stringer) {
      * Applies point compression to a public key and returns the result,
      * encoded with base64.
      *
-     * See http://www.secg.org/sec1-v2.pdf section 2.3.3 for more info.
+     * See https://www.secg.org/sec1-v2.pdf section 2.3.3 for more info.
      *
      * @param publicKey the public key to get the compressed X9.62
      * representation for