2 |
|
|
3 |
|
$Id$ |
4 |
|
|
5 |
< |
Copyright (c) 2001-2005 by ircd-hybrid team |
5 |
> |
Copyright (c) 2001-2012 by ircd-hybrid team |
6 |
|
|
7 |
|
---------------------------------------------------------------------- |
8 |
|
|
17 |
|
|
18 |
|
Requirements |
19 |
|
|
20 |
< |
The ircd must be compiled with the --enable-openssl option to configure . |
20 |
> |
The ircd must be compiled with the --enable-openssl option to configure. |
21 |
|
If configure detects a working openssl library, --enable-openssl is |
22 |
|
implicitly enabled. |
23 |
|
|
26 |
|
use both challenge and normal passwords, but this would defeat the purpose |
27 |
|
of the challenge system. |
28 |
|
|
29 |
< |
m_challenge.so must be loaded. |
29 |
> |
m_challenge.la must be loaded. |
30 |
|
|
31 |
|
The oper has their private key file and an implementation of the RSA |
32 |
|
Respond tool available to be run. |
36 |
|
Process |
37 |
|
|
38 |
|
Each oper should have a private key file and a public key file. The keys |
39 |
< |
can be generated with the mkkeypair utility provided in tools/. The keys |
40 |
< |
are compatible with cryptlink keys. |
39 |
> |
can be generated with the mkkeypair utility provided in tools/. |
40 |
|
|
41 |
|
The oper keeps their private key file in a safe place, and gives their |
42 |
|
public key file to their admin(s). |
81 |
|
Using CHALLENGE and respond |
82 |
|
|
83 |
|
Note: All examples assume the use of the stock respond client included |
84 |
< |
with the Hybrid 7 source, run on a UNIX(c) platform. |
84 |
> |
with the ircd-hybrid-8 source, run on a UNIX(c) platform. |
85 |
|
|
86 |
|
The administrator of the server you oper on should remove the password in |
87 |
|
your oper {} block and replace it with an entry for your public key, so |
153 |
|
the respond command, and to copy and paste data to and from the IRC |
154 |
|
client. |
155 |
|
|
156 |
< |
The respond source code is included with the Hybrid 7 source, in the |
157 |
< |
tools/rsa_respond directory. A distributable tar file can easily be |
159 |
< |
created by issuing make rsa_respond in the root of the source tree. The |
160 |
< |
file rsa_respond.tar.gz will be created in the root of the source tree. |
161 |
< |
|
162 |
< |
rsa_respond.tar.gz should compile with little or no modifications[1] on |
163 |
< |
most UNIX(c) and UNIX-like platforms[2]. The README in the tar archive |
164 |
< |
gives more information. |
156 |
> |
The respond source code is included with the ircd-hybrid source, in the |
157 |
> |
tools/rsa_respond directory. |
158 |
|
|
159 |
|
A copy of the source tar file is available on |
160 |
|
http://www.wohmart.com/ircd/pub/irc_tools/rsa/rsa_respond-src-hyb7.tar.gz |
204 |
|
Please note that passphrase protected keys cannot be used in conjunction |
205 |
|
with this script. |
206 |
|
|
207 |
< |
The script is called challange.irc and sits in contrib/. Please review |
207 |
> |
The script is called challenge.irc and sits in contrib/. Please review |
208 |
|
it for more details. |
209 |
|
|
210 |
|
---------------------------------------------------------------------- |