projects / irc / freenode / web-7.0.git / blame
| Commit | Line | Data |
|---|---|---|
| a4cef4d4 DP |
1 | Title: User and project cloaks |
| 2 | --- | |
| 3 | There are two types of "cloak" available on freenode; both replace the | |
| 4 | hostname/IP displayed when you are connected (but only when you're identified to | |
| 5 | NickServ - see below). | |
| 6 | ||
| 7 | Project cloaks | |
| 8 | ============== | |
| 9 | Project cloaks typically take the form `project/role/user`, for instance | |
| 10 | `freenode/staff/bigpresh`, and are designed to demonstrate that the user is | |
| 11 | connected to the project in some way. Different projects use cloaks for various | |
| 12 | roles - some only use them for their "core" team, some will assign "user" cloaks | |
| 13 | as well. | |
| 14 | ||
| 15 | Project cloaks can only be requested by a registered group contact of an | |
| 16 | already [registered group](pages/groupreg) - they should contact a member of | |
| 17 | freenode staff to request that a user be given a project cloak. | |
| 18 | ||
| 19 | ||
| 20 | Unaffiliated cloaks | |
| 21 | =================== | |
| 22 | Unaffiliated cloaks take the form `unaffiliated/accountname`. They obscure your | |
| 23 | IP from casual observers, to a degree - but see the weaknesses section below. | |
| 24 | ||
| 25 | ||
| 26 | Gateway cloaks | |
| 27 | ============== | |
| 28 | If you are connected via a gateway which sets a gateway cloak (for instance, our | |
| 29 | webchat, or KiwiIRC, or some bouncer/shell providers) then you will receive an | |
| 30 | automatic gateway cloak - for instance `gateway/web/freenode/ip.1.2.3.4` - these | |
| 31 | gateway cloaks override unaffiliated cloaks, but do not override project cloaks. | |
| 32 | ||
| 33 | ||
| 34 | Cloaks do not effectively hide your IP | |
| 35 | ====================================== | |
| 36 | Cloaks can help obscure your IP address/hostname from casual observers, but | |
| 37 | should *not* be relied upon for that purpose, as they are not reliable: | |
| 38 | ||
| 39 | - Connecting before identifying to NickServ (or whilst services are unavailable | |
| 40 | due to a netsplit or maintenance) will show your uncloaked IP/hostname | |
| 41 | connecting via SASL can help a little here, as authentication is done much | |
| 42 | earlier in the connection) | |
| 43 | - Connecting via a gateway (for instance, the webchat) will override | |
| 44 | unaffiliated cloaks (see the "gateway cloaks" section above) | |
| 45 | - Due to the nature of IRC services, there are some tricks which can cause | |
| 46 | services to reveal a cloaked user's IP/hostname. | |
| 47 | ||
| 48 | For these reasons, we advise you to consider cloaks very basic protection from | |
| 49 | casual observers, and a way to stop your IP/hostname being passively logged in | |
| 50 | most cases, but caution that they cannot be relied upon to hide your IP/hostname | |
| 51 | robustly - if you want that, you should consider an IRC bouncer, VPN or Tor. | |
| 52 | ||
| 53 | Requesting a cloak | |
| 54 | ================== | |
| 55 | Once you've read and understood the above, if you would like an unaffiliated | |
| 56 | cloak, please drop in to #freenode or speak to a member of the staff team and | |
| 57 | we'll be happy to set one up for you. | |
| 58 | ||
| 59 | For project cloaks, a registered GC for the project needs to contact staff to | |
| 60 | request the cloak be added to the desired user. | |
| 61 |