Using SSL - Revision history

Admin at 14:24, 14 November 2011

2011-11-14T14:24:50Z

← Older revision		Revision as of 14:24, 14 November 2011
Line 1:		Line 1:
-	~~All~~ DareNET ~~client~~ servers ~~utilize~~ SSL ~~for encryption. Those servers supporting such listen~~ on ~~port~~ 6697 and~~/or~~ 9999 ~~for incoming SSL connections~~. There are several methods you can utilize to connect using ~~SSL~~. The method chosen depends ~~entirely~~ on the client and any additional tunnel software, if needed. Currently, the following clients offer native or ~~builtin~~ SSL support for connections:	+	DareNET's servers support TLS/SSL-enabled connections on ports 6697 and 9999. There are several methods you can utilize to connect to DareNET using an encrypted connection. The method chosen depends on the IRC client being used and any additional tunnel software, if needed. Currently, the following clients offer native or built-in TLS/SSL support for connections:

	* [http://www.bitchx.org/ BitchX]		* [http://www.bitchx.org/ BitchX]
Line 8:		Line 8:
	* [http://www.kvirc.net/ KVirc]		* [http://www.kvirc.net/ KVirc]

-	For clients ~~that do not have~~ built-in SSL support such as mIRC versions prior to 6.14 you will need to use an SSL tunnel program. There are ~~two~~ popular SSL tunnels in use now for IRC clients~~. A unix/linux/windows version that can be used is stunnel and a windows only version is winsslwrap or~~ [http://www.~~bovine~~.~~net~~/~~~jlawson~~/~~coding~~/~~stuntour~~/ ~~StunTour]~~. ~~SSL connections are established by connecting through a tunnel~~. ~~The tunnel opens an SSL connection to an SSL enabled server~~, and ~~then opens a local connection on your computer~~. ~~The local connection is usually opened on port 6667, the default IRC port, or can be customised by the user~~. ~~The client then only needs to connect to localhost~~ (~~127.0.0.1~~), or basically to the local computer on the port that the SSL tunnel is listening on. An example command one might use in mIRC with an SSL tunnel program would be: /server localhost . If a port is not specified, the client will usually use the default port, 6667.	+	For clients without built-in TLS/SSL support, such as mIRC versions prior to 6.14, you will need to use an TLS/SSL tunnel program. There are three popular TLS/SSL tunnels in use now for IRC clients: [http://www.stunnel.org/ Stunnel] (Unix/Linux/Windows), [http://oifan.xf.cz/WinSSLWrap/ WinSSLWrap] (Windows), and [http://jeff.bovine.net/Stuntour StunTour] (Windows).

-	~~== Servers Supporting~~ SSL ==	+	This method establishes a TLS/SSL connection by connecting through a tunnel. The tunnel opens a TLS/SSL connection to the IRC server, and then opens a local connection your computer. The local connection is usually opened on port 6667, the default IRC port, though this can be customized by the user. The client then only needs to connect to localhost (127.0.0.1), using the port the TLS/SSL tunnel is listening on.

-	* irc.darenet.org	+	==Servers supporting TLS/SSL==

-	~~== Using~~ SSL ~~with mIRC 6~~.~~14+ ==~~	+	All DareNET IRC servers presently support TLS/SSL-enabled connections on ports 6697 and 9999; therefore, you may still specify ''irc.darenet.org'' as the server to use (which will connect you to a server geographically closest to you).

-	~~Since the majority of our users use~~ mIRC~~, we'll explain how to connect to DareNET using it. We assume you're using version~~ 6.14 ~~or newer, which all have built-in support for connecting to SSL servers, using the [http://www.openssl.org/ OpenSSL] libraries.~~	+	==Using SSL with mIRC 6.14+ ==

-	The OpenSSL libraries are not included with mIRC ~~for licensing reasons~~, but you can download them pre-compiled for win32 (~~windows~~ 9x, 2000, 2003, XP) from [http://archives.darenet.org/archives.php?dir=misc/openssl-bin/&file=Win32OpenSSL_Light-0_9_8l.exe here]. After you download that file, extract the included libraries (libeay32.dll and ssleay32.dll) into your mIRC directory, or you can extract them to your windows/system directory if you prefer.	+	The majority of our users use mIRC, so we'll explain how to connect to DareNET using it. We assume you're using version 6.14 or newer, which all have built-in support for connecting to TLS/SSL-enabled servers, using the [http://www.openssl.org/ OpenSSL] libraries.
		+
		+	Due to licensing reasons, the OpenSSL libraries are not included with mIRC, but you can download them pre-compiled for win32 (Windows 9x, 2000, 2003, XP) from [http://archives.darenet.org/archives.php?dir=misc/openssl-bin/&file=Win32OpenSSL_Light-0_9_8l.exe here]. After you download that file, extract the included libraries (libeay32.dll and ssleay32.dll) into your mIRC directory, or you can extract them to your windows/system directory if you prefer.

	''NOTE: The library files provided above were compiled from the OpenSSL 0.9.8I sources. If you know how to and prefer to compile your own, you can do that as well.''		''NOTE: The library files provided above were compiled from the OpenSSL 0.9.8I sources. If you know how to and prefer to compile your own, you can do that as well.''
Line 24:		Line 26:
	After you have placed libeay32.dll and ssleay32.dll in your mIRC directory, shutdown mIRC and restart it, then it should automatically find the library files and load them. To make sure your copy of mIRC will now work with SSL, you can check the '''$sslready''' variable (type '''''//echo $sslready''''' in your status window, and mIRC should return '''$true''' if the OpenSSL libraries are properly loaded).		After you have placed libeay32.dll and ssleay32.dll in your mIRC directory, shutdown mIRC and restart it, then it should automatically find the library files and load them. To make sure your copy of mIRC will now work with SSL, you can check the '''$sslready''' variable (type '''''//echo $sslready''''' in your status window, and mIRC should return '''$true''' if the OpenSSL libraries are properly loaded).

-	We use ~~port~~ 6697 or 9999 for all incoming SSL connections ~~to leafs~~, so to connect using SSL just use /server irc.darenet.org +6697 (the plus sign is required for SSL connections)~~. For a list of available servers, please see the list above~~.	+	We use ports 6697 and 9999 for all incoming TLS/SSL client connections, so to connect using SSL just use /server irc.darenet.org +6697 (the plus sign is required for SSL connections).

	An example:		An example:

-	<~~pre~~>/server irc.darenet.org +6697</~~pre~~>	+	<code>/server irc.darenet.org +6697</code>

-	After you have connected, you can verify that you are connected with SSL using the '''$ssl''' variable in mIRC (type '''''//echo $ssl''''' in your status window, and mIRC should return '''$true'''). Another way to see if you are connected with SSL is to /WHOIS yourself by typing /WHOIS YourNick, and in your WHOIS output you will see a line like this:	+	After you have connected, you can verify that you are connected with SSL using the '''$ssl''' variable in mIRC (type '''''//echo $ssl''''' in your status window, and mIRC should return '''$true''').Another way to see if you are connected with SSL is to /WHOIS yourself by typing /WHOIS YourNick, and in your WHOIS output you will see a line like this:

-	<pre>YourNick is using a secure connection ~~(SSL)~~</pre>	+	<pre>YourNick is using a secure connection</pre>

-	If you are using an mIRC version older than 6.14, then the above instructions do not apply to you. You should upgrade to the latest mIRC version. If for some reason you want to keep your current version of mIRC, then you will have to use an SSL tunnel, like [http://~~www~~.bovine.net/~~~jlawson/coding/stuntour/~~ StunTour].	+	If you are using an mIRC version older than 6.14, then the above instructions do not apply to you. You should upgrade to the latest mIRC version. If for some reason you want to keep your current version of mIRC, then you will have to use an SSL tunnel, like [http://jeff.bovine.net/Stuntour StunTour].

-	== SSL-only channels ==	+	== TLS/SSL-only channels ==

-	DareNET's servers support channel mode +Z, which means only users connected using ~~SSL~~ will be allowed to join the channel. This is useful for those who want to ensure that their communications on the channel are entirely secure.	+	DareNET's servers support channel mode +Z, which means only users connected using an encrypted connection will be allowed to join the channel. This is useful for those who want to ensure that their communications on the channel are entirely secure.

	== Why the need for secure connections? ==		== Why the need for secure connections? ==

Vicarious: SSL-only channel mode is +Z, not +S

2010-01-26T06:55:51Z

SSL-only channel mode is +Z, not +S

← Older revision		Revision as of 06:55, 26 January 2010
Line 38:		Line 38:
	== SSL-only channels ==		== SSL-only channels ==

-	DareNET's servers support channel mode +S, which means only users connected using SSL will be allowed to join the channel. This is useful for those who want to ensure that their communications on the channel are entirely secure.	+	DareNET's servers support channel mode +Z, which means only users connected using SSL will be allowed to join the channel. This is useful for those who want to ensure that their communications on the channel are entirely secure.

	== Why the need for secure connections? ==		== Why the need for secure connections? ==

Vicarious: fixed minor typo's

2010-01-26T06:16:44Z

fixed minor typo's

Nitemare at 01:25, 31 December 2009

2009-12-31T01:25:14Z

← Older revision		Revision as of 01:25, 31 December 2009
Line 1:		Line 1:
-	~~{{Adminbacklog\|id=1}}~~
-
-	The information given here will hopefully assist you in connecting to DareNET using an encrypted connection. This is a work in progress and will become more complete in the near future so please check back often.
-
	All DareNET client servers utilize SSL for encryption. Those servers supporting such listen on port 6697 and/or 9999 for incoming SSL connections. There are several methods you can utilize to connect using SSL. The method chosen depends entirely on the client and any additional tunnel software, if needed. Currently, the following clients offer native or builtin SSL support for connections:		All DareNET client servers utilize SSL for encryption. Those servers supporting such listen on port 6697 and/or 9999 for incoming SSL connections. There are several methods you can utilize to connect using SSL. The method chosen depends entirely on the client and any additional tunnel software, if needed. Currently, the following clients offer native or builtin SSL support for connections:

Line 48:		Line 44:
	DareNET/IRC is used by many organizations that need to communicate over secure connections, everything from corporate to governmental. Various educational organizations that provide online teaching also require communications to be secure for privacy purposes. Apart from that, many individuals around the world also depend on secure communications, whether for political, business, or other reasons. At the end of the day, it really depends on your own personal needs. If it's not something that you think you need, then you probably don't!		DareNET/IRC is used by many organizations that need to communicate over secure connections, everything from corporate to governmental. Various educational organizations that provide online teaching also require communications to be secure for privacy purposes. Apart from that, many individuals around the world also depend on secure communications, whether for political, business, or other reasons. At the end of the day, it really depends on your own personal needs. If it's not something that you think you need, then you probably don't!

-	[[Category:~~Old~~]]	+	[[Category:All]] [[Category:New Users]]

Nitemare at 01:09, 31 December 2009

2009-12-31T01:09:53Z

← Older revision		Revision as of 01:09, 31 December 2009
Line 3:		Line 3:
	The information given here will hopefully assist you in connecting to DareNET using an encrypted connection. This is a work in progress and will become more complete in the near future so please check back often.		The information given here will hopefully assist you in connecting to DareNET using an encrypted connection. This is a work in progress and will become more complete in the near future so please check back often.

-	~~Some~~ DareNET servers ~~have recently started to~~ utilize SSL ~~encryption~~ for ~~client connections~~. Those servers supporting such listen on port 6697 and/or 9999 for incoming SSL connections. There are several methods you can utilize to connect using SSL. The method chosen depends entirely on the client and any additional tunnel software, if needed. Currently, the following clients offer native or builtin SSL support for connections:	+	All DareNET client servers utilize SSL for encryption. Those servers supporting such listen on port 6697 and/or 9999 for incoming SSL connections. There are several methods you can utilize to connect using SSL. The method chosen depends entirely on the client and any additional tunnel software, if needed. Currently, the following clients offer native or builtin SSL support for connections:

	* [http://www.bitchx.org/ BitchX]		* [http://www.bitchx.org/ BitchX]
Line 16:		Line 16:
	== Servers Supporting SSL ==		== Servers Supporting SSL ==

-	* ~~quake.ca.us~~.darenet.org	+	* irc.darenet.org

	== Using SSL with mIRC 6.14+ ==		== Using SSL with mIRC 6.14+ ==
Line 22:		Line 22:
	Since the majority of our users use mIRC, we'll explain how to connect to DareNET using it. We assume you're using version 6.14 or newer, which all have built-in support for connecting to ssl servers, using the [http://www.openssl.org/ OpenSSL] libraries.		Since the majority of our users use mIRC, we'll explain how to connect to DareNET using it. We assume you're using version 6.14 or newer, which all have built-in support for connecting to ssl servers, using the [http://www.openssl.org/ OpenSSL] libraries.

-	The OpenSSL libraries are not included with mIRC for licensing reasons, but you can download them pre-compiled for win32 (windows 9x, 2000, 2003, XP) from [http://~~www~~.darenet.org/~~downloads/openssl_0~~.~~9.8_win32~~.~~zip~~ here]. After you download that file, extract the included libraries (libeay32.dll and ssleay32.dll) into your mIRC directory, or you can extract them to your windows/system directory if you prefer.	+	The OpenSSL libraries are not included with mIRC for licensing reasons, but you can download them pre-compiled for win32 (windows 9x, 2000, 2003, XP) from [http://archives.darenet.org/archives.php?dir=misc/openssl-bin/&file=Win32OpenSSL_Light-0_9_8l.exe here]. After you download that file, extract the included libraries (libeay32.dll and ssleay32.dll) into your mIRC directory, or you can extract them to your windows/system directory if you prefer.

-	''NOTE: The library files provided above were compiled from the OpenSSL 0.9.8 sources. If you know how to and prefer to compile your own, you can do that as well.''	+	''NOTE: The library files provided above were compiled from the OpenSSL 0.9.8I sources. If you know how to and prefer to compile your own, you can do that as well.''

	After you have placed libeay32.dll and ssleay32.dll in your mIRC directory, shutdown mIRC and restart it, then it should automatically find the library files and load them. To make sure your copy of mIRC will now work with ssl, you can check the '''$sslready''' variable (type '''''//echo $sslready''''' in your status window, and mIRC should return '''$true''' if the OpenSSL libraries are properly loaded).		After you have placed libeay32.dll and ssleay32.dll in your mIRC directory, shutdown mIRC and restart it, then it should automatically find the library files and load them. To make sure your copy of mIRC will now work with ssl, you can check the '''$sslready''' variable (type '''''//echo $sslready''''' in your status window, and mIRC should return '''$true''' if the OpenSSL libraries are properly loaded).

-	We use port 9999 for all incoming ssl connections to leafs, so to connect using ssl just use /server ~~servername~~ +~~9999~~ (the plus sign is required for ssl connections). For a list of available servers, please see the list above.	+	We use port 6697 or 9999 for all incoming ssl connections to leafs, so to connect using ssl just use /server irc.darenet.org +6697 (the plus sign is required for ssl connections). For a list of available servers, please see the list above.

	An example:		An example:

-	<pre>/server ~~quake.ca.us~~.darenet.org +~~9999~~</pre>	+	<pre>/server irc.darenet.org +6697</pre>

	After you have connected, you can verify that you are connected with ssl using the '''$ssl''' variable in mIRC (type '''''//echo $ssl''''' in your status window, and mIRC should return '''$true'''). Another way to see if you are connected with ssl is to /WHOIS yourself by typing /WHOIS YourNick, and in your WHOIS output you will see a line like this:		After you have connected, you can verify that you are connected with ssl using the '''$ssl''' variable in mIRC (type '''''//echo $ssl''''' in your status window, and mIRC should return '''$true'''). Another way to see if you are connected with ssl is to /WHOIS yourself by typing /WHOIS YourNick, and in your WHOIS output you will see a line like this:

Admin at 00:37, 31 December 2009

2009-12-31T00:37:38Z

← Older revision		Revision as of 00:37, 31 December 2009
Line 1:		Line 1:
-	{{Adminbacklog}}	+	{{Adminbacklog\|id=1}}

	The information given here will hopefully assist you in connecting to DareNET using an encrypted connection. This is a work in progress and will become more complete in the near future so please check back often.		The information given here will hopefully assist you in connecting to DareNET using an encrypted connection. This is a work in progress and will become more complete in the near future so please check back often.

Admin at 00:12, 30 December 2009

2009-12-30T00:12:37Z

← Older revision		Revision as of 00:12, 30 December 2009
Line 1:		Line 1:
		+	{{Adminbacklog}}
		+
	The information given here will hopefully assist you in connecting to DareNET using an encrypted connection. This is a work in progress and will become more complete in the near future so please check back often.		The information given here will hopefully assist you in connecting to DareNET using an encrypted connection. This is a work in progress and will become more complete in the near future so please check back often.

Secretagent: Updated, but probably needs further updates

2008-07-22T05:26:17Z

Updated, but probably needs further updates

← Older revision		Revision as of 05:26, 22 July 2008
Line 1:		Line 1:
-	The information given here will hopefully assist you in connecting to ~~ChatX~~ using an encrypted connection. This is a work in progress and will become more complete in the near future so please check back often.	+	The information given here will hopefully assist you in connecting to DareNET using an encrypted connection. This is a work in progress and will become more complete in the near future so please check back often.

-	Some ~~ChatX~~ servers have recently started to utilize SSL encryption for client connections. Those servers supporting such listen on port ~~7070~~ for incoming SSL connections. There are several methods you can utilize to connect using SSL. The method chosen depends entirely on the client and any additional tunnel software, if needed. Currently, the following clients offer native or builtin SSL support for connections:	+	Some DareNET servers have recently started to utilize SSL encryption for client connections. Those servers supporting such listen on port 6697 and/or 9999 for incoming SSL connections. There are several methods you can utilize to connect using SSL. The method chosen depends entirely on the client and any additional tunnel software, if needed. Currently, the following clients offer native or builtin SSL support for connections:

	* [http://www.bitchx.org/ BitchX]		* [http://www.bitchx.org/ BitchX]
Line 14:		Line 14:
	== Servers Supporting SSL ==		== Servers Supporting SSL ==

-	* ~~queen~~.il.us.~~chatx~~.~~net port 7070~~	+	* quake.ca.us.darenet.org

	== Using SSL with mIRC 6.14+ ==		== Using SSL with mIRC 6.14+ ==

-	Since the majority of our users use mIRC, we'll explain how to connect to ~~ChatX~~ using it. We assume you're using version 6.14 or newer, which all have built-in support for connecting to ssl servers, using the [http://www.openssl.org/ OpenSSL] libraries.	+	Since the majority of our users use mIRC, we'll explain how to connect to DareNET using it. We assume you're using version 6.14 or newer, which all have built-in support for connecting to ssl servers, using the [http://www.openssl.org/ OpenSSL] libraries.

-	The OpenSSL libraries are not included with mIRC for licensing reasons, but you can download them pre-compiled for win32 (windows 9x, 2000, 2003, XP) from [http://www.~~chatx~~.~~net~~/downloads/openssl_0.9.8_win32.zip here]. After you download that file, extract the included libraries (libeay32.dll and ssleay32.dll) into your mIRC directory, or you can extract them to your windows/system directory if you prefer.	+	The OpenSSL libraries are not included with mIRC for licensing reasons, but you can download them pre-compiled for win32 (windows 9x, 2000, 2003, XP) from [http://www.darenet.org/downloads/openssl_0.9.8_win32.zip here]. After you download that file, extract the included libraries (libeay32.dll and ssleay32.dll) into your mIRC directory, or you can extract them to your windows/system directory if you prefer.

	''NOTE: The library files provided above were compiled from the OpenSSL 0.9.8 sources. If you know how to and prefer to compile your own, you can do that as well.''		''NOTE: The library files provided above were compiled from the OpenSSL 0.9.8 sources. If you know how to and prefer to compile your own, you can do that as well.''
Line 26:		Line 26:
	After you have placed libeay32.dll and ssleay32.dll in your mIRC directory, shutdown mIRC and restart it, then it should automatically find the library files and load them. To make sure your copy of mIRC will now work with ssl, you can check the '''$sslready''' variable (type '''''//echo $sslready''''' in your status window, and mIRC should return '''$true''' if the OpenSSL libraries are properly loaded).		After you have placed libeay32.dll and ssleay32.dll in your mIRC directory, shutdown mIRC and restart it, then it should automatically find the library files and load them. To make sure your copy of mIRC will now work with ssl, you can check the '''$sslready''' variable (type '''''//echo $sslready''''' in your status window, and mIRC should return '''$true''' if the OpenSSL libraries are properly loaded).

-	We use port ~~7070~~ for all incoming ssl connections to leafs, so to connect using ssl just use /server servername +~~7070~~ (the plus sign is required for ssl connections). For a list of available servers, please see the list above.	+	We use port 9999 for all incoming ssl connections to leafs, so to connect using ssl just use /server servername +9999 (the plus sign is required for ssl connections). For a list of available servers, please see the list above.

	An example:		An example:

-	<pre>/server ~~queen~~.il.us.~~chatx~~.~~net~~ +~~7070~~</pre>	+	<pre>/server quake.ca.us.darenet.org +9999</pre>

	After you have connected, you can verify that you are connected with ssl using the '''$ssl''' variable in mIRC (type '''''//echo $ssl''''' in your status window, and mIRC should return '''$true'''). Another way to see if you are connected with ssl is to /WHOIS yourself by typing /WHOIS YourNick, and in your WHOIS output you will see a line like this:		After you have connected, you can verify that you are connected with ssl using the '''$ssl''' variable in mIRC (type '''''//echo $ssl''''' in your status window, and mIRC should return '''$true'''). Another way to see if you are connected with ssl is to /WHOIS yourself by typing /WHOIS YourNick, and in your WHOIS output you will see a line like this:
Line 40:		Line 40:
	== SSL-only channels ==		== SSL-only channels ==

-	~~ChatX~~'s servers support channel mode +S, which means only users connected using SSL will be allowed to join the channel. This is useful for those who want to ensure that their communications on the channel are entirely secure.	+	DareNET's servers support channel mode +S, which means only users connected using SSL will be allowed to join the channel. This is useful for those who want to ensure that their communications on the channel are entirely secure.

	== Why the need for secure connections? ==		== Why the need for secure connections? ==

-	~~ChatX~~/IRC is used by many organizations that need to communicate over secure connections, everything from corporate to governmental. Various educational organizations that provide online teaching also require communications to be secure for privacy purposes. Apart from that, many individuals around the world also depend on secure communications, whether for political, business, or other reasons. At the end of the day, it really depends on your own personal needs. If it's not something that you think you need, then you probably don't!	+	DareNET/IRC is used by many organizations that need to communicate over secure connections, everything from corporate to governmental. Various educational organizations that provide online teaching also require communications to be secure for privacy purposes. Apart from that, many individuals around the world also depend on secure communications, whether for political, business, or other reasons. At the end of the day, it really depends on your own personal needs. If it's not something that you think you need, then you probably don't!

	[[Category:Old]]		[[Category:Old]]

Admin at 03:01, 29 February 2008

2008-02-29T03:01:32Z

← Older revision		Revision as of 03:01, 29 February 2008
Line 46:		Line 46:
	ChatX/IRC is used by many organizations that need to communicate over secure connections, everything from corporate to governmental. Various educational organizations that provide online teaching also require communications to be secure for privacy purposes. Apart from that, many individuals around the world also depend on secure communications, whether for political, business, or other reasons. At the end of the day, it really depends on your own personal needs. If it's not something that you think you need, then you probably don't!		ChatX/IRC is used by many organizations that need to communicate over secure connections, everything from corporate to governmental. Various educational organizations that provide online teaching also require communications to be secure for privacy purposes. Apart from that, many individuals around the world also depend on secure communications, whether for political, business, or other reasons. At the end of the day, it really depends on your own personal needs. If it's not something that you think you need, then you probably don't!

-	[[Category:~~Documentation~~]]	+	[[Category:Old]]

Secretagent: /* Using SSL with mIRC 6.14+ */

2007-10-02T00:28:21Z

Using SSL with mIRC 6.14+

← Older revision		Revision as of 00:28, 2 October 2007
Line 24:		Line 24:
	''NOTE: The library files provided above were compiled from the OpenSSL 0.9.8 sources. If you know how to and prefer to compile your own, you can do that as well.''		''NOTE: The library files provided above were compiled from the OpenSSL 0.9.8 sources. If you know how to and prefer to compile your own, you can do that as well.''

-	After you have placed libeay32.dll and ssleay32.dll in your mIRC directory, shutdown mIRC and restart it, then it should automatically find the library files and load them. To make sure your copy of mIRC will now work with ssl, you can check the '''$sslready''' variable (type '''''//echo $sslready''''' in your status window, and mIRC should return $true if the OpenSSL libraries are properly loaded).	+	After you have placed libeay32.dll and ssleay32.dll in your mIRC directory, shutdown mIRC and restart it, then it should automatically find the library files and load them. To make sure your copy of mIRC will now work with ssl, you can check the '''$sslready''' variable (type '''''//echo $sslready''''' in your status window, and mIRC should return '''$true''' if the OpenSSL libraries are properly loaded).

	We use port 7070 for all incoming ssl connections to leafs, so to connect using ssl just use /server servername +7070 (the plus sign is required for ssl connections). For a list of available servers, please see the list above.		We use port 7070 for all incoming ssl connections to leafs, so to connect using ssl just use /server servername +7070 (the plus sign is required for ssl connections). For a list of available servers, please see the list above.

← Older revision		Revision as of 06:16, 26 January 2010
Line 8:		Line 8:
	* [http://www.kvirc.net/ KVirc]		* [http://www.kvirc.net/ KVirc]

-	For clients that do not have built-in SSL support such as mIRC versions ~~priot~~ to 6.14 you will need to use an SSL tunnel program. There are two popular SSL tunnels in use now for IRC clients. A unix/linux/windows version that can be used is stunnel and a windows only version is winsslwrap or [http://www.bovine.net/~jlawson/coding/stuntour/ StunTour]. SSL connections are established by connecting through a tunnel. The tunnel opens an SSL connection to an SSL enabled server, and then opens a local connection on your computer. The local connection is usually opened on port 6667, the default IRC port, or can be customised by the user. The client then only needs to connect to localhost (127.0.0.1), or basically to the local computer on the port that the SSL tunnel is listening on. An example command one might use in mIRC with an SSL tunnel program would be: /server localhost . If a port is not specified, the client will usually use the default port, 6667.	+	For clients that do not have built-in SSL support such as mIRC versions prior to 6.14 you will need to use an SSL tunnel program. There are two popular SSL tunnels in use now for IRC clients. A unix/linux/windows version that can be used is stunnel and a windows only version is winsslwrap or [http://www.bovine.net/~jlawson/coding/stuntour/ StunTour]. SSL connections are established by connecting through a tunnel. The tunnel opens an SSL connection to an SSL enabled server, and then opens a local connection on your computer. The local connection is usually opened on port 6667, the default IRC port, or can be customised by the user. The client then only needs to connect to localhost (127.0.0.1), or basically to the local computer on the port that the SSL tunnel is listening on. An example command one might use in mIRC with an SSL tunnel program would be: /server localhost . If a port is not specified, the client will usually use the default port, 6667.

	== Servers Supporting SSL ==		== Servers Supporting SSL ==
Line 16:		Line 16:
	== Using SSL with mIRC 6.14+ ==		== Using SSL with mIRC 6.14+ ==

-	Since the majority of our users use mIRC, we'll explain how to connect to DareNET using it. We assume you're using version 6.14 or newer, which all have built-in support for connecting to ~~ssl~~ servers, using the [http://www.openssl.org/ OpenSSL] libraries.	+	Since the majority of our users use mIRC, we'll explain how to connect to DareNET using it. We assume you're using version 6.14 or newer, which all have built-in support for connecting to SSL servers, using the [http://www.openssl.org/ OpenSSL] libraries.

	The OpenSSL libraries are not included with mIRC for licensing reasons, but you can download them pre-compiled for win32 (windows 9x, 2000, 2003, XP) from [http://archives.darenet.org/archives.php?dir=misc/openssl-bin/&file=Win32OpenSSL_Light-0_9_8l.exe here]. After you download that file, extract the included libraries (libeay32.dll and ssleay32.dll) into your mIRC directory, or you can extract them to your windows/system directory if you prefer.		The OpenSSL libraries are not included with mIRC for licensing reasons, but you can download them pre-compiled for win32 (windows 9x, 2000, 2003, XP) from [http://archives.darenet.org/archives.php?dir=misc/openssl-bin/&file=Win32OpenSSL_Light-0_9_8l.exe here]. After you download that file, extract the included libraries (libeay32.dll and ssleay32.dll) into your mIRC directory, or you can extract them to your windows/system directory if you prefer.
Line 22:		Line 22:
	''NOTE: The library files provided above were compiled from the OpenSSL 0.9.8I sources. If you know how to and prefer to compile your own, you can do that as well.''		''NOTE: The library files provided above were compiled from the OpenSSL 0.9.8I sources. If you know how to and prefer to compile your own, you can do that as well.''

-	After you have placed libeay32.dll and ssleay32.dll in your mIRC directory, shutdown mIRC and restart it, then it should automatically find the library files and load them. To make sure your copy of mIRC will now work with ~~ssl~~, you can check the '''$sslready''' variable (type '''''//echo $sslready''''' in your status window, and mIRC should return '''$true''' if the OpenSSL libraries are properly loaded).	+	After you have placed libeay32.dll and ssleay32.dll in your mIRC directory, shutdown mIRC and restart it, then it should automatically find the library files and load them. To make sure your copy of mIRC will now work with SSL, you can check the '''$sslready''' variable (type '''''//echo $sslready''''' in your status window, and mIRC should return '''$true''' if the OpenSSL libraries are properly loaded).

-	We use port 6697 or 9999 for all incoming ~~ssl~~ connections to leafs, so to connect using ~~ssl~~ just use /server irc.darenet.org +6697 (the plus sign is required for ~~ssl~~ connections). For a list of available servers, please see the list above.	+	We use port 6697 or 9999 for all incoming SSL connections to leafs, so to connect using SSL just use /server irc.darenet.org +6697 (the plus sign is required for SSL connections). For a list of available servers, please see the list above.

	An example:		An example:
Line 30:		Line 30:
	<pre>/server irc.darenet.org +6697</pre>		<pre>/server irc.darenet.org +6697</pre>

-	After you have connected, you can verify that you are connected with ~~ssl~~ using the '''$ssl''' variable in mIRC (type '''''//echo $ssl''''' in your status window, and mIRC should return '''$true'''). Another way to see if you are connected with ~~ssl~~ is to /WHOIS yourself by typing /WHOIS YourNick, and in your WHOIS output you will see a line like this:	+	After you have connected, you can verify that you are connected with SSL using the '''$ssl''' variable in mIRC (type '''''//echo $ssl''''' in your status window, and mIRC should return '''$true'''). Another way to see if you are connected with SSL is to /WHOIS yourself by typing /WHOIS YourNick, and in your WHOIS output you will see a line like this:

	<pre>YourNick is using a secure connection (SSL)</pre>		<pre>YourNick is using a secure connection (SSL)</pre>

-	If you are using an mIRC version older than 6.14, then the above instructions do not apply to you. You should upgrade to the latest mIRC version. If for some reason you want to keep your current version of mIRC, then you will have to use an ~~ssl~~ tunnel, like [http://www.bovine.net/~jlawson/coding/stuntour/ StunTour].	+	If you are using an mIRC version older than 6.14, then the above instructions do not apply to you. You should upgrade to the latest mIRC version. If for some reason you want to keep your current version of mIRC, then you will have to use an SSL tunnel, like [http://www.bovine.net/~jlawson/coding/stuntour/ StunTour].

	== SSL-only channels ==		== SSL-only channels ==