diff --git a/navbar.html b/navbar.html index b093c01..58d24a4 100644 --- a/navbar.html +++ b/navbar.html @@ -23,6 +23,7 @@ Navigation bar * Off-topic sites (Social Media) --> +

Not directly related to me * Auto-identifying on IRC

diff --git a/navbar.html.md b/navbar.html.md index 0dd0d4f..95fa9a3 100644 --- a/navbar.html.md +++ b/navbar.html.md @@ -26,6 +26,9 @@ Where to find me? * Off-topic sites (Social Media) --> +Not directly related to me +* Auto-identifying on IRC + diff --git a/pages/external/identifying.html b/pages/external/identifying.html index 01f3688..e1fcce0 100644 --- a/pages/external/identifying.html +++ b/pages/external/identifying.html @@ -42,6 +42,46 @@ XX:XX:XX < *sasl> +-------------+-----------------------------------------
  • This won't help you if services go down.

    • CertFP

    +

    CertFP identifies you using SSL certificate which you must generate and add to your NickServ account.

    +

    You can use this command at IRC to check if the network supports certfp.

    +
    /msg NickServ help cert
    +

    I am not sure how this happens on Windows, so you might need to look for that information elsewhere unless someone decides to help me and tell how does it happen. I am going to tell about OpenSSL.

    +

    Generating the certificate

    +

    Open terminal and run this command and replae YOURNICKNAMEHERE.pem with your nickname or something else which makes you know what it is (DO NOT SET PASSWORD FOR IT OR YOUR CLIENT MIGHT NOT BE ABLE TO USE IT):

    +
    openssl req -nodes -newkey rsa:4096 -keyout YOURNICKNAMEHERE.pem -x509 -days 365 -out YOURNICKNAMEHERE.pem
    +

    This gives us file YOURNICKNAMEHERE.pem which you must give to your IRC client. I am sorry, but that depends on your IRC client too, so I cannot say anything about it.

    +

    Telling NickServ about your key

    +

    NickServ wants to know the fingerprint which you can get with the following command:

    +
    openssl x509 -sha1 -noout -fingerprint -in YOURNICKNAMEHERE.pem | sed -e 's/^.*=//;s/://g;y/ABCDEF/abcdef/'
    +

    which returns your fingerprint (WHICH YOU MUST NOT SHARE WITH ANYONE)

    +
    05dd01fedc1b821b796d0d785160f03e32f53fa8
    +

    Now you can tell to NickServ about it.

    +
    /msg NickServ CERT ADD 05dd01fedc1b821b796d0d785160f03e32f53fa8
    +

    (replace that with your own fingerprint!) And nickerv replies to you

    +
    14:13:39 -- NickServ: Added fingerprint 05dd01fedc1b821b796d0d785160f03e32f53fa8 to your fingerprint list.
    +

    Testing

    +

    Now when you connect to freenode and have configured your IRC client to use your new certificate, you should get identified automatically and you should see your certificate by whoising yourself and running cert list with NickServ.

    +
    /WHOIS YOURNICK YOURNICK
+/MSG NickServ CERT LIST
    +

    replies

    +
    <...>
+XX:XX:XX -- [YOURNICK] has client certificate fingerprint 05dd01fedc1b821b796d0d785160f03e32f53fa8
+<...>
+XX:XX:XX -- NickServ: Fingerprint list for YOURNICK:
+XX:XX:XX -- NickServ: - 05dd01fedc1b821b796d0d785160f03e32f53fa8$$
+XX:XX:XX -- NickServ: End of YOURNICK fingerprint list.
    +

    Notes

    +

    Server password

    This might not work with some networks, but this works with freenode. All IRC clients should support settng password which to use while connecting to server. Set it as username:password for freenode and you are automatically identified when you connect.

    Some notes:

    @@ -60,6 +100,7 @@ XX:XX:XX < *sasl> +-------------+-----------------------------------------
  • Your client might send that command too late to prevent you from getting to redirect channels for unidentified users and show your real host to everyone.
  • You might annoy people by joining twice and quitting once with "Changing host".
    • +
    For corrections above this line, please contact me at IRC or fix them by yourself here. What is below that line is embedded GitHub gist which reads where to contact with issues with it.
    diff --git a/pages/external/identifying.html.md b/pages/external/identifying.html.md index 3812849..beb9655 100644 --- a/pages/external/identifying.html.md +++ b/pages/external/identifying.html.md @@ -69,6 +69,95 @@ work with most of networks. ## CertFP +CertFP identifies you using SSL certificate which you must generate and +add to your NickServ account. + +You can use this command at IRC to check if the network supports certfp. + +``` +/msg NickServ help cert +``` + +I am not sure how this happens on Windows, so you might need to look for +that information elsewhere unless someone decides to help me and tell +how does it happen. I am going to tell about OpenSSL. + +### Generating the certificate + +Open terminal and run this command and replae YOURNICKNAMEHERE.pem with +your nickname or something else which makes you know what it is +(**DO NOT SET PASSWORD FOR IT OR YOUR CLIENT MIGHT NOT BE ABLE TO USE IT**): + +``` +openssl req -nodes -newkey rsa:4096 -keyout YOURNICKNAMEHERE.pem -x509 -days 365 -out YOURNICKNAMEHERE.pem +``` + +This gives us file `YOURNICKNAMEHERE.pem` which you must give to your IRC +client. I am sorry, but that depends on your IRC client too, so I cannot +say anything about it. + +### Telling NickServ about your key + +NickServ wants to know the fingerprint which you can get with the following +command: + +``` +openssl x509 -sha1 -noout -fingerprint -in YOURNICKNAMEHERE.pem | sed -e 's/^.*=//;s/://g;y/ABCDEF/abcdef/' +``` + +which returns your fingerprint (**WHICH YOU MUST NOT SHARE WITH ANYONE**) + +``` +05dd01fedc1b821b796d0d785160f03e32f53fa8 +``` + +Now you can tell to NickServ about it. + +``` +/msg NickServ CERT ADD 05dd01fedc1b821b796d0d785160f03e32f53fa8 +``` + +(replace that with your own fingerprint!) And nickerv replies to you + +``` +14:13:39 -- NickServ: Added fingerprint 05dd01fedc1b821b796d0d785160f03e32f53fa8 to your fingerprint list. +``` + +### Testing + +Now when you connect to freenode and have configured your IRC client to +use your new certificate, you should get identified automatically and +you should see your certificate by whoising yourself and running cert list +with NickServ. + +``` +/WHOIS YOURNICK YOURNICK +/MSG NickServ CERT LIST +``` + +replies + +``` +<...> +XX:XX:XX -- [YOURNICK] has client certificate fingerprint 05dd01fedc1b821b796d0d785160f03e32f53fa8 +<...> +XX:XX:XX -- NickServ: Fingerprint list for YOURNICK: +XX:XX:XX -- NickServ: - 05dd01fedc1b821b796d0d785160f03e32f53fa8$$ +XX:XX:XX -- NickServ: End of YOURNICK fingerprint list. +``` + +### Notes + +* You must recreate your certificate yearly. +* This will identify you with immediately so you are still visible to +/monitor. +* This will identify you after services return unlike other methods if you +happen to be on splitted server without services. +* Supported networks which I am on: + * freenode + * oftc + * piratenet + ## Server password This might not work with some networks, but this works with freenode. @@ -103,6 +192,7 @@ everyone. * You might annoy people by joining twice and quitting once with "Changing host". +
    For corrections above this line, please contact [me at IRC](../irc.html) or fix them by yourself [here](https://github.com/Mkaysi/mkaysi.github.io/blob/master/pages/external/identifying.html.md). What is below that line is embedded GitHub gist which reads where to contact with issues with it.