DareNET Wiki - User contributions [en]

User:Vicarious

2010-02-15T22:28:35Z

Vicarious: added #Macintosh

{{Infobox_userpage
| image = Vicarious.jpg|center
| account = Vicarious
| real_name = Vicarious
| age = Born in the scary year 1984.
| located_in = Planet Earth
| common_nick = Vicarious
| common_chan = #DareNET,#Macintosh,#mIRC,#Support
| website_url = [http://www.darenet.org/ www.darenet.org] <br /><html><img src="http://www.darenet.org/static/userstatus.php?img=1&nick=Vicarious"></html>
}}
[[Image:Vicarious.png|My nickname]]

* Languages: dutch, english, german

{{Userboxes
|align =|toptext = User Badges{{Userbadge/irc nick|Vicarious}}
{{Userbadge/irssi}}
{{Userbadge/osx}}}}

mIRC v6.0 Tips

2010-02-11T16:47:18Z

Vicarious: typo fixed

== Connect to a second network, while remaining connected to the first ==

* /server -m irc.server2.net

== You want mIRC to connect to 2 Different Servers ==

Put this into your remotes (Alt + r)

<pre>on *:start: server irc.server1.name | server -m irc.server2.name </pre>

== You want mIRC to join multiple channels, depending on network ==

<pre>on 1:connect: {
if ($network == DareNET) { join #Channel,#channel2,#channel3 }
if ($network == Efnet) { /nick MyNick }
if ($network == DALnet) join #Channel4
if ($network == Undernet) /msg Nick Message
}</pre>

OR, you can add something similar to your perform section

File - Options - IRC - Perform
<pre>
/if ($network == DareNET) { /join #DareNET }
/if ($network == Undernet) { /nick MyNick }
/if ($network == DALnet) { /join #hideout }
/if ($network == EFnet) { /join #Chat }</pre>

== Globally send an /amsg ==

<pre>/scid -a /amsg Your text here</pre>

== How does mIRC get the $network info it displays on the switchbar button? ==

mIRC first looks to the server for a message to be sent (Raw) if nothing comes,
it looks in your own server settings (file - options- connect) and checks the name of the server you are connecting to, to see what information you have filled in under the "Group" section. If no information is filled in, mIRC uses the server name itself.

= Tips, Tricks and FYI =

'''2nd Input Box'''

(Alt + - ) choose Edit Box - you can now specify specific input commands for this new, second input box. Some suggestions are /onotice or /msg NickName Alt + Q adds the edit box to any channel. Single line edit box :Shift & Tab cycles between channel & custom input boxes. Multi line edit box: Tab

Test it out - Alt + Q - Box Appears - Right click in box- choose options
Command editbox opens
Under Command type: /me

Ok out of menu - Type in that new edit box on right: says Hi !

----

'''Status Window kept in focus, based on active channel/window.'''

(Alt + W) - choose Status on top - this will allow the status window to come 'forward' for the network you have in focus (note: this does not work in tiled windows)

Test it out - Open 2 servers. Join channels on each. Be able to see both channels and both status boxes. Now click between the 2 channels on the 2 different networks. You'll notice the Status Window focus comes 'front'.

----

'''How to simply open a 2nd server after you connect to the first'''

(ALT + O) - Connect - [x]New Server Window - will create an additional connection, to the server shown above this option. An additional connection can also be made by typing /server -m server.name.com into any edit box.

----

'''FYI (For your information)'''

If you currently use the /aop (auto Op) command, be SURE to go to your settings to specify by network. New names added will automatically grab the network.

[[Category:All]] [[Category:Documentation|Mirc]]

Using SSL

2010-01-26T06:55:51Z

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

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.mirc.com mIRC] (6.14 and above)
* [http://www.xchat.org/ Xchat]
* [http://www.scrollz.com/ Scrollz]
* [http://www.irssi.org/ irssi]
* [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.

== Servers Supporting SSL ==

* irc.darenet.org

== 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.

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.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).

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:

<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:

<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].

== 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.

== Why the need for secure connections? ==

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:All]] [[Category:New Users]]

Using SSL

2010-01-26T06:16:44Z

Vicarious: fixed minor typo's

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.mirc.com mIRC] (6.14 and above)
* [http://www.xchat.org/ Xchat]
* [http://www.scrollz.com/ Scrollz]
* [http://www.irssi.org/ irssi]
* [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.

== Servers Supporting SSL ==

* irc.darenet.org

== 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.

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.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).

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:

<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:

<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].

== 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.

== Why the need for secure connections? ==

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:All]] [[Category:New Users]]

Extended Bans

2009-12-03T20:13:24Z

Vicarious: /* Quiet and Nick Change */

We have recently added support for extended bans to ircd-darenet, our server software. Extended bans gives channel operators more flexibility and control over their channel's ban list. The proper syntax for extended bans is as follows:

'''<code>/mode #channel +b $type:mask</code>'''

The following types of extended bans are currently supported:

{| class="wikitable" width="100%" style="font-size: 85%;"
! style="text-align: center;" | Type
! style="text-align: center;" | Name
! style="text-align: left;" | Purpose
|-
| style="text-align: center;" | $a
| style="text-align: center;" | Account
| If a user's account name matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $c
| style="text-align: center;" | Channel
| If a user is in a channel that matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $j
| style="text-align: center;" | Shared Bans
| If a user matches a ban on the channel who's ban list is being shared, (s)he will be unable to join.
|-
| style="text-align: center;" | $n
| style="text-align: center;" | Nick Change
| If a user matches this ban, (s)he will be unable to change their nickname while in the channel.
|-
| style="text-align: center;" | $q
| style="text-align: center;" | Quiet
| If a user matches this ban, (s)he will be unable to send messages to the channel.
|-
| style="text-align: center;" | $r
| style="text-align: center;" | Realname
| If a user's realname (gecos) matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $t
| style="text-align: center;" | Text
| Allows you to specify text that will be blocked if a user's privmsg or notice to the channel contains it. * and ? wildcards supported.
|-
|}

== Quiet and Nick Change ==

$q (quiet) and $n (nick change) are similar to normal bans, except that they allow you to control what a user can do without preventing them from joining the channel. $q prevents users matching the ban from sending messages/notices to the channel, while $n prevents them from changing their nickname.

'''Syntax:'''

<code>/mode #channel +b $q:nick!ident@host<br>
/mode #channel +b $n:nick!ident@host</code>

'''Examples:'''

Let's say that we wanted to allow AOL users to join the channel, but prevent them from speaking. This could be achieved by setting the following $q (quiet) extended ban:

<code>/mode #channel +b $q:*!*@*.aol.com</code>

If we wanted to also prevent AOL users from changing their nickname while their in our channel, we could also set the following $n (nick change) extended ban to achieve that:

<code>/mode #channel +b $n:*!*@*.aol.com</code>

== Channel and Realname ==

$c and $r are channel and realname (gecos) bans, respectively.

When $c is used, it will prevent users who are currently in the channel specified from joining your channel. When $r is used, it will prevent users who's realname (gecos) matches the ban from joining your channel. Note, $r treats '_' as both the underscore character and a space.

'''Syntax:'''

<code>/mode #channel +b $c:#channel<br>
/mode #channel +b $r:realname</code>

'''Examples:'''

Let's say we wanted to prevent all users who are inchannels with the word ''warez'' in their name from joining our channel. We could achieve this by setting the following $c (channel) extended ban:

<code>/mode #channel +b $c:#*warez*</code>

Let's say we also want to prevent all users with the word ''bot'' in their realname (gecos) from joining the channel, as well. To do this, we could set the following $r (realname) extended ban:

<code>/mode #channel +b $r:*bot*</code>

== Account Bans ==

The $a (account) extended ban type allows you to ban (logged in) users who's account matches the specified ban mask. Note, these types of bans can only ever match users logged into their NickServ account.

'''Syntax:'''

<code>/mode #channel +b $a:mask</code>

'''Examples:'''

If we wanted to ban all users who's account names contained the word ''joe'' in them, we could set the following $a (account) extended ban to achieve this:

<code>/mode #channel +b $a:*joe*</code>

NOTE: Extended account bans act identical to the previous method of banning user's based on their account name (e.g. <code>/mode #channel +b *!*@accountname.*</code>); however, the reverse logic function can also be used with extended account bans, which cannot presently do with the old method. We discuss the reverse logic function a little later in this guide.

== Shared Bans ==

The $j (shared bans) extended ban type allows you to use another channel's ban list.

'''Syntax:'''

<code>/mode #channel +b $j:mask</code>

'''Examples:'''

Okay, for this example, our channel is ''#channel'' and we want to use ''#shared''<nowiki>'</nowiki>s channel ban list along with our own. To do this, we would set the following $c (shared bans) extended ban on ''#channel'':

<code>/mode #channel +b $j:#shared</code>

Now, whenever a user tries to join ''#channel'', they will be checked against ''#shared''<nowiki>'</nowiki>s channel ban list, in addition to ''#channel''<nowiki>'</nowiki>s channel ban list. If a match is found in either ban list, they will be prevented from joining.

== Text Bans ==

The $t (text ban) extended ban type allows channel operators to specify text that will blocked if a user's message or notice to the channel contains it. The * and ? wildcards are supported. Note, this currently affects channel operators, half operators and voices as well.

'''Syntax:'''

<code>/mode #channel +b $t:mask</code>

'''Examples:'''

Let's say we wanted to block all channel messages and notices that contained the word ''damn''. To do this, we would set the following:

<code>/mode #channel +b $t:damn</code>

== Reverse Logic ==

If "!" is specified in an extended ban, then it will have a reverse effect. Please note this does not work with quiets. Instead, use excepts.

'''Syntax:'''

<code>/mode #channel +b $!<type>:mask</code>

'''Example:'''

Let's say we wanted to an extended channel ban on #darenet with the "!" (reverse) flag, we'd use:

<code>/mode #channel +b $!c:#darenet</code>

This would prevent anyone from joining #channel if they are not already in #darenet as well.

== Assistance ==

Should you need assistance using the new extended bans feature, feel free to stop by #Support

[[Category:Documentation]]

User:Vicarious

2009-07-28T23:36:43Z

Vicarious: created my own userpage

{{Infobox_userpage
| image = Vicarious.jpg|center
| account = Vicarious
| real_name = Vicarious
| age = Born in the scary year 1984.
| located_in = Planet Earth
| common_nick = Vicarious
| common_chan = #DareNET,#mIRC,#Support
| website_url = [http://www.darenet.org/ www.darenet.org] <br /><html><img src="http://www.darenet.org/static/userstatus.php?img=1&nick=Vicarious"></html>
}}
[[Image:Vicarious.png|My nickname]]

* Languages: dutch, english, german

{{Userboxes
|align =|toptext = User Badges{{Userbadge/irc nick|Vicarious}}
{{Userbadge/irssi}}
{{Userbadge/osx}}}}

File:Vicarious.jpg

2009-07-28T18:55:28Z

Vicarious: My avatar

My avatar

File:Vicarious.png

2009-07-28T17:49:14Z

Vicarious: My nickname

My nickname