Cloaking/zh-tw

This feature is useful to prevent users from flooding/attacking each other, they can't flood the other party without knowing their real host/IP. The host is not just cloaked in JOIN's, it's also hidden in PART, WHOIS, etc.. every command that would otherwise have exposed your real host or IP to another user.

Cloaking 是一個隱藏 IRC 使用者的 Hostname 的方法. 舉例來說，如果你的 host 是 d5142341.cable.wanadoo.nl，當你未使用 Cloaking 時加入會看起來如下： *** User (~none@d5142341.cable.wanadoo.nl) has joined #test 而使用 Cloaking 時看起來如下: *** User (~none@rox-2DCA3201.cable.wanadoo.nl) has joined #test 如你所見，host 會被掩蓋、隱藏，其他使用者將不會看到你真實的 hostname 或 IP. 這是一個很有用的功能來避免使用者遇到 flooding/attacking. 有心人士無法在不知道你 host 與 IP 下攻擊你. Host 不僅僅是在 JOIN 時隱藏，於 PART、WHOIS 與其他會暴露你 Host 或 IP 的指令下都會隱藏.

Cloaking is controlled by usermode +x (like: /mode yournick +x). Normally admins force +x to be enabled by default (through set::modes-on-connect).

A cloaked host is generated by a cloaking module. You must load at least one cloaking module, but don't worry about it too much as the default modules.default.conf (that almost everyone uses) will load the default cloaking module shipped with UnrealIRCd. It's also possible to use another cloaking algorithm created by a 3rd party.

The cloaking algorithm requires (secret) cloaking keys to be set, see set::cloak-keys for more information.

Cloak keys MUST be the same on ALL SERVERS in a network. Also cloak keys must be kept secret because it's possible to decode (or rather: brute force) the original host when you know the keys, doing so would make the whole point of cloaking useless.

Note that while cloaking protects the individual from having the IRC server expose the IP/hostname of the user, there are still plenty of other ways for a user to expose his/her IP. For example, if you ask a user to surf to a website under your own control, and the user does this, you could then check the log file of your web server to see the users' IP.