A cloaked host is generated by a cloaking module (you are required to have one loaded), currently there's only 1 module included:
cloak: This is the official cloaking module since 3.2.1, it is much more secure than the old
algorithm, it uses md5 internally and requires you to have 3 set::cloak-keys:: consisting of mixed lowercase (a-z),
- uppercase (A-Z) and digit (0-9) charachters [eg: "AopAS6WQH2Os6hfosh4SFJHs"]. See example.conf for an example.
+ uppercase (A-Z) and digit (0-9) characters [eg: "AopAS6WQH2Os6hfosh4SFJHs"]. See example.conf for an example.
Cloak keys MUST be the same on ALL SERVERS in a network. Also cloak keys should be kept SECRET because it's possible to decode the original host if you know the keys (which makes umode +x useless).
Hint: If you are on *NIX and have to create new cloak keys, you can run './unreal gencloak' @@ -337,7 +337,7 @@ because otherwise you will not understand concepts such as 'cloaking', 'snomasks If you then connect to 127.0.0.1 port 6667, your traffic will be encrypted and forwarded to irc.myserv.com port 6697 (an SSL port).
You should also validate certificates when you connect to servers and not blindly accept them (like in the stunnel example) - else you are still vulnerable to "active sniffing" attacks (ssl redirects), that's however too offtopic + else you are still vulnerable to "active sniffing" attacks (ssl redirects), that's however too off-topic to explain here (learn about SSL, don't ask us). [mIRC and xchat pop up a window asking you to allow/reject a certificate, so that's good].