]>
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. | |
fbb9b6df DP |
47 | - Accepting a DCC chat/file transfer session, or clicking a link someone sends |
48 | you could reveal your IP to them | |
a4cef4d4 DP |
49 | |
50 | For these reasons, we advise you to consider cloaks very basic protection from | |
51 | casual observers, and a way to stop your IP/hostname being passively logged in | |
52 | most cases, but caution that they cannot be relied upon to hide your IP/hostname | |
53 | robustly - if you want that, you should consider an IRC bouncer, VPN or Tor. | |
54 | ||
fbb9b6df DP |
55 | Do consider, however, just how much you need to hide your IP address; it's |
56 | disclosed routinely during normal Internet usage - for instance, every website | |
57 | you visit will necessarily see your IP address, unless you are using a VPN or | |
58 | Tor. Many, many users happily use IRC for decades, never hiding their IP | |
59 | address, and do not have any problems. | |
60 | ||
a4cef4d4 DP |
61 | Requesting a cloak |
62 | ================== | |
63 | Once you've read and understood the above, if you would like an unaffiliated | |
64 | cloak, please drop in to #freenode or speak to a member of the staff team and | |
65 | we'll be happy to set one up for you. | |
66 | ||
67 | For project cloaks, a registered GC for the project needs to contact staff to | |
68 | request the cloak be added to the desired user. | |
69 |