Created
April 3, 2017 20:59
-
-
Save hyper3xpl0iter/f2bf95f5b279b9baa04df869e0671c24 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
################################################################################ | |
# | |
# filename: irc-sasl.conf | |
# description: Gist to show to setup SASL connections to IRC | |
# author: Andre Mattie | |
# email: devel@introsec.ca | |
# GPG: 5620 A200 6534 B779 08A8 B22B 0FA6 CD54 93EA 430D | |
# bitcoin: 1LHsfZrES8DksJ41JAXULimLJjUZJf7Qns | |
# date: 04/03/2017 | |
# | |
################################################################################ | |
### Creating Certificates | |
openssl req -x509 -new -newkey rsa:4096 -sha256 -days 1000 -nodes -out <YOUR-NICK>.pem -keyout <YOUR-NICK>.pem | |
#You will be prompted for various pieces of information about the certificate. The contents do not matter for our purposes, but #openssl needs at least one of them to be non-empty. | |
# | |
#The .pem file will have the same access to your NickServ account as your password does, so take appropriate care in securing it. | |
# Display your certificates fingerprint | |
openssl x509 -in <YOUR-NICK>.pem -outform der | sha1sum -b | cut -d' ' -f1 | |
# Now lookup the documentation of your IRC client program for examples on how to setup/configure the client to use your newly #created certificate and enable SASL |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment