├── .github └── ISSUE_TEMPLATE │ ├── new-link-request.md │ └── report-a-dead-link.md ├── LICENSE.md ├── README.md ├── _config.yml ├── articles ├── README.md ├── browser-config │ ├── WhonixBrowser.md │ └── WindowsTestingBrowser.md └── i2p-docker-services │ ├── BasicStaticeepSite.md │ ├── FreecivServerClient.md │ ├── GithubPagesMirror.md │ ├── README.md │ └── i2pd.example.conf ├── getting-started.md ├── security-considerations.md └── sidebar.md /.github/ISSUE_TEMPLATE/new-link-request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: New link request 3 | about: Do you think a link should be on the sidebar? 4 | 5 | --- 6 | 7 | ## What is the link: 8 | 9 | ## What is it's purpose/content: 10 | 11 | ## Why do you think it should be on the sidebar: 12 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/report-a-dead-link.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Report a dead link 3 | about: Is a link consistently unreachable? 4 | 5 | --- 6 | 7 | - [ ] this is an incomplete item 8 | 9 | It is located in: 10 | 11 | A good substitute for it is: 12 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | Attribution-ShareAlike 4.0 International 2 | 3 | ======================================================================= 4 | 5 | Creative Commons Corporation ("Creative Commons") is not a law firm and 6 | does not provide legal services or legal advice. Distribution of 7 | Creative Commons public licenses does not create a lawyer-client or 8 | other relationship. Creative Commons makes its licenses and related 9 | information available on an "as-is" basis. Creative Commons gives no 10 | warranties regarding its licenses, any material licensed under their 11 | terms and conditions, or any related information. Creative Commons 12 | disclaims all liability for damages resulting from their use to the 13 | fullest extent possible. 14 | 15 | Using Creative Commons Public Licenses 16 | 17 | Creative Commons public licenses provide a standard set of terms and 18 | conditions that creators and other rights holders may use to share 19 | original works of authorship and other material subject to copyright 20 | and certain other rights specified in the public license below. The 21 | following considerations are for informational purposes only, are not 22 | exhaustive, and do not form part of our licenses. 23 | 24 | Considerations for licensors: Our public licenses are 25 | intended for use by those authorized to give the public 26 | permission to use material in ways otherwise restricted by 27 | copyright and certain other rights. Our licenses are 28 | irrevocable. Licensors should read and understand the terms 29 | and conditions of the license they choose before applying it. 30 | Licensors should also secure all rights necessary before 31 | applying our licenses so that the public can reuse the 32 | material as expected. Licensors should clearly mark any 33 | material not subject to the license. This includes other CC- 34 | licensed material, or material used under an exception or 35 | limitation to copyright. More considerations for licensors: 36 | wiki.creativecommons.org/Considerations_for_licensors 37 | 38 | Considerations for the public: By using one of our public 39 | licenses, a licensor grants the public permission to use the 40 | licensed material under specified terms and conditions. If 41 | the licensor's permission is not necessary for any reason--for 42 | example, because of any applicable exception or limitation to 43 | copyright--then that use is not regulated by the license. Our 44 | licenses grant only permissions under copyright and certain 45 | other rights that a licensor has authority to grant. Use of 46 | the licensed material may still be restricted for other 47 | reasons, including because others have copyright or other 48 | rights in the material. A licensor may make special requests, 49 | such as asking that all changes be marked or described. 50 | Although not required by our licenses, you are encouraged to 51 | respect those requests where reasonable. More_considerations 52 | for the public: 53 | wiki.creativecommons.org/Considerations_for_licensees 54 | 55 | ======================================================================= 56 | 57 | Creative Commons Attribution-ShareAlike 4.0 International Public 58 | License 59 | 60 | By exercising the Licensed Rights (defined below), You accept and agree 61 | to be bound by the terms and conditions of this Creative Commons 62 | Attribution-ShareAlike 4.0 International Public License ("Public 63 | License"). To the extent this Public License may be interpreted as a 64 | contract, You are granted the Licensed Rights in consideration of Your 65 | acceptance of these terms and conditions, and the Licensor grants You 66 | such rights in consideration of benefits the Licensor receives from 67 | making the Licensed Material available under these terms and 68 | conditions. 69 | 70 | 71 | Section 1 -- Definitions. 72 | 73 | a. Adapted Material means material subject to Copyright and Similar 74 | Rights that is derived from or based upon the Licensed Material 75 | and in which the Licensed Material is translated, altered, 76 | arranged, transformed, or otherwise modified in a manner requiring 77 | permission under the Copyright and Similar Rights held by the 78 | Licensor. For purposes of this Public License, where the Licensed 79 | Material is a musical work, performance, or sound recording, 80 | Adapted Material is always produced where the Licensed Material is 81 | synched in timed relation with a moving image. 82 | 83 | b. Adapter's License means the license You apply to Your Copyright 84 | and Similar Rights in Your contributions to Adapted Material in 85 | accordance with the terms and conditions of this Public License. 86 | 87 | c. BY-SA Compatible License means a license listed at 88 | creativecommons.org/compatiblelicenses, approved by Creative 89 | Commons as essentially the equivalent of this Public License. 90 | 91 | d. Copyright and Similar Rights means copyright and/or similar rights 92 | closely related to copyright including, without limitation, 93 | performance, broadcast, sound recording, and Sui Generis Database 94 | Rights, without regard to how the rights are labeled or 95 | categorized. For purposes of this Public License, the rights 96 | specified in Section 2(b)(1)-(2) are not Copyright and Similar 97 | Rights. 98 | 99 | e. Effective Technological Measures means those measures that, in the 100 | absence of proper authority, may not be circumvented under laws 101 | fulfilling obligations under Article 11 of the WIPO Copyright 102 | Treaty adopted on December 20, 1996, and/or similar international 103 | agreements. 104 | 105 | f. Exceptions and Limitations means fair use, fair dealing, and/or 106 | any other exception or limitation to Copyright and Similar Rights 107 | that applies to Your use of the Licensed Material. 108 | 109 | g. License Elements means the license attributes listed in the name 110 | of a Creative Commons Public License. The License Elements of this 111 | Public License are Attribution and ShareAlike. 112 | 113 | h. Licensed Material means the artistic or literary work, database, 114 | or other material to which the Licensor applied this Public 115 | License. 116 | 117 | i. Licensed Rights means the rights granted to You subject to the 118 | terms and conditions of this Public License, which are limited to 119 | all Copyright and Similar Rights that apply to Your use of the 120 | Licensed Material and that the Licensor has authority to license. 121 | 122 | j. Licensor means the individual(s) or entity(ies) granting rights 123 | under this Public License. 124 | 125 | k. Share means to provide material to the public by any means or 126 | process that requires permission under the Licensed Rights, such 127 | as reproduction, public display, public performance, distribution, 128 | dissemination, communication, or importation, and to make material 129 | available to the public including in ways that members of the 130 | public may access the material from a place and at a time 131 | individually chosen by them. 132 | 133 | l. Sui Generis Database Rights means rights other than copyright 134 | resulting from Directive 96/9/EC of the European Parliament and of 135 | the Council of 11 March 1996 on the legal protection of databases, 136 | as amended and/or succeeded, as well as other essentially 137 | equivalent rights anywhere in the world. 138 | 139 | m. You means the individual or entity exercising the Licensed Rights 140 | under this Public License. Your has a corresponding meaning. 141 | 142 | 143 | Section 2 -- Scope. 144 | 145 | a. License grant. 146 | 147 | 1. Subject to the terms and conditions of this Public License, 148 | the Licensor hereby grants You a worldwide, royalty-free, 149 | non-sublicensable, non-exclusive, irrevocable license to 150 | exercise the Licensed Rights in the Licensed Material to: 151 | 152 | a. reproduce and Share the Licensed Material, in whole or 153 | in part; and 154 | 155 | b. produce, reproduce, and Share Adapted Material. 156 | 157 | 2. Exceptions and Limitations. For the avoidance of doubt, where 158 | Exceptions and Limitations apply to Your use, this Public 159 | License does not apply, and You do not need to comply with 160 | its terms and conditions. 161 | 162 | 3. Term. The term of this Public License is specified in Section 163 | 6(a). 164 | 165 | 4. Media and formats; technical modifications allowed. The 166 | Licensor authorizes You to exercise the Licensed Rights in 167 | all media and formats whether now known or hereafter created, 168 | and to make technical modifications necessary to do so. The 169 | Licensor waives and/or agrees not to assert any right or 170 | authority to forbid You from making technical modifications 171 | necessary to exercise the Licensed Rights, including 172 | technical modifications necessary to circumvent Effective 173 | Technological Measures. For purposes of this Public License, 174 | simply making modifications authorized by this Section 2(a) 175 | (4) never produces Adapted Material. 176 | 177 | 5. Downstream recipients. 178 | 179 | a. Offer from the Licensor -- Licensed Material. Every 180 | recipient of the Licensed Material automatically 181 | receives an offer from the Licensor to exercise the 182 | Licensed Rights under the terms and conditions of this 183 | Public License. 184 | 185 | b. Additional offer from the Licensor -- Adapted Material. 186 | Every recipient of Adapted Material from You 187 | automatically receives an offer from the Licensor to 188 | exercise the Licensed Rights in the Adapted Material 189 | under the conditions of the Adapter's License You apply. 190 | 191 | c. No downstream restrictions. You may not offer or impose 192 | any additional or different terms or conditions on, or 193 | apply any Effective Technological Measures to, the 194 | Licensed Material if doing so restricts exercise of the 195 | Licensed Rights by any recipient of the Licensed 196 | Material. 197 | 198 | 6. No endorsement. Nothing in this Public License constitutes or 199 | may be construed as permission to assert or imply that You 200 | are, or that Your use of the Licensed Material is, connected 201 | with, or sponsored, endorsed, or granted official status by, 202 | the Licensor or others designated to receive attribution as 203 | provided in Section 3(a)(1)(A)(i). 204 | 205 | b. Other rights. 206 | 207 | 1. Moral rights, such as the right of integrity, are not 208 | licensed under this Public License, nor are publicity, 209 | privacy, and/or other similar personality rights; however, to 210 | the extent possible, the Licensor waives and/or agrees not to 211 | assert any such rights held by the Licensor to the limited 212 | extent necessary to allow You to exercise the Licensed 213 | Rights, but not otherwise. 214 | 215 | 2. Patent and trademark rights are not licensed under this 216 | Public License. 217 | 218 | 3. To the extent possible, the Licensor waives any right to 219 | collect royalties from You for the exercise of the Licensed 220 | Rights, whether directly or through a collecting society 221 | under any voluntary or waivable statutory or compulsory 222 | licensing scheme. In all other cases the Licensor expressly 223 | reserves any right to collect such royalties. 224 | 225 | 226 | Section 3 -- License Conditions. 227 | 228 | Your exercise of the Licensed Rights is expressly made subject to the 229 | following conditions. 230 | 231 | a. Attribution. 232 | 233 | 1. If You Share the Licensed Material (including in modified 234 | form), You must: 235 | 236 | a. retain the following if it is supplied by the Licensor 237 | with the Licensed Material: 238 | 239 | i. identification of the creator(s) of the Licensed 240 | Material and any others designated to receive 241 | attribution, in any reasonable manner requested by 242 | the Licensor (including by pseudonym if 243 | designated); 244 | 245 | ii. a copyright notice; 246 | 247 | iii. a notice that refers to this Public License; 248 | 249 | iv. a notice that refers to the disclaimer of 250 | warranties; 251 | 252 | v. a URI or hyperlink to the Licensed Material to the 253 | extent reasonably practicable; 254 | 255 | b. indicate if You modified the Licensed Material and 256 | retain an indication of any previous modifications; and 257 | 258 | c. indicate the Licensed Material is licensed under this 259 | Public License, and include the text of, or the URI or 260 | hyperlink to, this Public License. 261 | 262 | 2. You may satisfy the conditions in Section 3(a)(1) in any 263 | reasonable manner based on the medium, means, and context in 264 | which You Share the Licensed Material. For example, it may be 265 | reasonable to satisfy the conditions by providing a URI or 266 | hyperlink to a resource that includes the required 267 | information. 268 | 269 | 3. If requested by the Licensor, You must remove any of the 270 | information required by Section 3(a)(1)(A) to the extent 271 | reasonably practicable. 272 | 273 | b. ShareAlike. 274 | 275 | In addition to the conditions in Section 3(a), if You Share 276 | Adapted Material You produce, the following conditions also apply. 277 | 278 | 1. The Adapter's License You apply must be a Creative Commons 279 | license with the same License Elements, this version or 280 | later, or a BY-SA Compatible License. 281 | 282 | 2. You must include the text of, or the URI or hyperlink to, the 283 | Adapter's License You apply. You may satisfy this condition 284 | in any reasonable manner based on the medium, means, and 285 | context in which You Share Adapted Material. 286 | 287 | 3. You may not offer or impose any additional or different terms 288 | or conditions on, or apply any Effective Technological 289 | Measures to, Adapted Material that restrict exercise of the 290 | rights granted under the Adapter's License You apply. 291 | 292 | 293 | Section 4 -- Sui Generis Database Rights. 294 | 295 | Where the Licensed Rights include Sui Generis Database Rights that 296 | apply to Your use of the Licensed Material: 297 | 298 | a. for the avoidance of doubt, Section 2(a)(1) grants You the right 299 | to extract, reuse, reproduce, and Share all or a substantial 300 | portion of the contents of the database; 301 | 302 | b. if You include all or a substantial portion of the database 303 | contents in a database in which You have Sui Generis Database 304 | Rights, then the database in which You have Sui Generis Database 305 | Rights (but not its individual contents) is Adapted Material, 306 | 307 | including for purposes of Section 3(b); and 308 | c. You must comply with the conditions in Section 3(a) if You Share 309 | all or a substantial portion of the contents of the database. 310 | 311 | For the avoidance of doubt, this Section 4 supplements and does not 312 | replace Your obligations under this Public License where the Licensed 313 | Rights include other Copyright and Similar Rights. 314 | 315 | 316 | Section 5 -- Disclaimer of Warranties and Limitation of Liability. 317 | 318 | a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE 319 | EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS 320 | AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF 321 | ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, 322 | IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, 323 | WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR 324 | PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, 325 | ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT 326 | KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT 327 | ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. 328 | 329 | b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE 330 | TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, 331 | NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, 332 | INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, 333 | COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR 334 | USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN 335 | ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR 336 | DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR 337 | IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. 338 | 339 | c. The disclaimer of warranties and limitation of liability provided 340 | above shall be interpreted in a manner that, to the extent 341 | possible, most closely approximates an absolute disclaimer and 342 | waiver of all liability. 343 | 344 | 345 | Section 6 -- Term and Termination. 346 | 347 | a. This Public License applies for the term of the Copyright and 348 | Similar Rights licensed here. However, if You fail to comply with 349 | this Public License, then Your rights under this Public License 350 | terminate automatically. 351 | 352 | b. Where Your right to use the Licensed Material has terminated under 353 | Section 6(a), it reinstates: 354 | 355 | 1. automatically as of the date the violation is cured, provided 356 | it is cured within 30 days of Your discovery of the 357 | violation; or 358 | 359 | 2. upon express reinstatement by the Licensor. 360 | 361 | For the avoidance of doubt, this Section 6(b) does not affect any 362 | right the Licensor may have to seek remedies for Your violations 363 | of this Public License. 364 | 365 | c. For the avoidance of doubt, the Licensor may also offer the 366 | Licensed Material under separate terms or conditions or stop 367 | distributing the Licensed Material at any time; however, doing so 368 | will not terminate this Public License. 369 | 370 | d. Sections 1, 5, 6, 7, and 8 survive termination of this Public 371 | License. 372 | 373 | 374 | Section 7 -- Other Terms and Conditions. 375 | 376 | a. The Licensor shall not be bound by any additional or different 377 | terms or conditions communicated by You unless expressly agreed. 378 | 379 | b. Any arrangements, understandings, or agreements regarding the 380 | Licensed Material not stated herein are separate from and 381 | independent of the terms and conditions of this Public License. 382 | 383 | 384 | Section 8 -- Interpretation. 385 | 386 | a. For the avoidance of doubt, this Public License does not, and 387 | shall not be interpreted to, reduce, limit, restrict, or impose 388 | conditions on any use of the Licensed Material that could lawfully 389 | be made without permission under this Public License. 390 | 391 | b. To the extent possible, if any provision of this Public License is 392 | deemed unenforceable, it shall be automatically reformed to the 393 | minimum extent necessary to make it enforceable. If the provision 394 | cannot be reformed, it shall be severed from this Public License 395 | without affecting the enforceability of the remaining terms and 396 | conditions. 397 | 398 | c. No term or condition of this Public License will be waived and no 399 | failure to comply consented to unless expressly agreed to by the 400 | Licensor. 401 | 402 | d. Nothing in this Public License constitutes or may be interpreted 403 | as a limitation upon, or waiver of, any privileges and immunities 404 | that apply to the Licensor or You, including from the legal 405 | processes of any jurisdiction or authority. 406 | 407 | 408 | ======================================================================= 409 | 410 | Creative Commons is not a party to its public 411 | licenses. Notwithstanding, Creative Commons may elect to apply one of 412 | its public licenses to material it publishes and in those instances 413 | will be considered the “Licensor.” The text of the Creative Commons 414 | public licenses is dedicated to the public domain under the CC0 Public 415 | Domain Dedication. Except for the limited purpose of indicating that 416 | material is shared under a Creative Commons public license or as 417 | otherwise permitted by the Creative Commons policies published at 418 | creativecommons.org/policies, Creative Commons does not authorize the 419 | use of the trademark "Creative Commons" or any other trademark or logo 420 | of Creative Commons without its prior written consent including, 421 | without limitation, in connection with any unauthorized modifications 422 | to any of its public licenses or any other arrangements, 423 | understandings, or agreements concerning use of licensed material. For 424 | the avoidance of doubt, this paragraph does not form part of the 425 | public licenses. 426 | 427 | Creative Commons may be contacted at creativecommons.org. 428 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # r-i2p-wiki 2 | The community wiki for /r/i2p 3 | 4 | [Getting Started](getting-started.md) 5 | 6 | [Security Considerations](security-considerations.md) 7 | 8 | [Articles](articles/README.md) 9 | 10 | -------------------------------------------------------------------------------- /_config.yml: -------------------------------------------------------------------------------- 1 | theme: jekyll-theme-minimal -------------------------------------------------------------------------------- /articles/README.md: -------------------------------------------------------------------------------- 1 | Articles: 2 | ========= 3 | 4 | Configuring an i2p browser 5 | -------------------------- 6 | 7 | * **[Easy configuration of an i2p browser for Windows](browser-config/WindowsTestingBrowser.md)** Set up a dedicated 8 | i2p browsing profile with Firefox for Windows automatically. By @eyedeekay 9 | * **[Configuration of Whonix i2pbrowser profile on Debian-Based GNU/Linux](browser-config/WhonixBrowser.md)** Use 10 | Whonix-based Tor/i2p Browser Management Tools with i2p. By @eyedeekay 11 | 12 | 13 | Configuring services with Docker and i2pd ([index](i2p-docker-services/README.md)) 14 | ----------------------------------------------------- 15 | 16 | * **[Configuring a Simple Static eepSite](i2p-docker-services/BasicStaticeepSite.md):** Host simple static content on 17 | i2p in minutes. By @eyedeekay 18 | * **[Mirroring a Github Pages site as an eepSite](i2p-docker-services/GithubPagesMirror.md):** Expand on the static 19 | eepsite tutorial by enabling a Github Pages mirror. By @eyedeekay 20 | * **[Gaming on i2p with Freeciv and Docker](i2p-docker-services/FreecivServerClient.md):** Set up 21 | a Freeciv client and server, using i2p. By @eyedeekay 22 | -------------------------------------------------------------------------------- /articles/browser-config/WhonixBrowser.md: -------------------------------------------------------------------------------- 1 | Using Whonix's i2p Browser Launching Scripts on Debian-Based GNU/Linux 2 | ====================================================================== 3 | 4 | **This guide is intended for users who are aware of the implications of using** 5 | **third-party repositories on their Debian-based Linux PC's.** In particular, 6 | Whonix is designed to pro-actively prevent certain kinds of attacks from 7 | affecting the user, and their packages sometimes overwrite things like hosts 8 | files and such with versions suitable for the Whonix threat model. While I 9 | currently use the following packages successfully on both Debian and Ubuntu 10 | Linux at this time, I cannot guarantee that they will work for everyone's 11 | specific configuration. 12 | 13 | Installation/Use: 14 | ----------------- 15 | 16 | First, you will need to install the Whonix package signing key with apt-key add. 17 | This will allow apt to vet the source of the new packages to confirm that they 18 | are indeed from the Whonix project. 19 | 20 | ```sh 21 | sudo apt-key --keyring /etc/apt/trusted.gpg.d/whonix.gpg adv --keyserver hkp://ipv4.pool.sks-keyservers.net:80 --recv-keys 916B8D99C38EAF5E8ADC7A2A8D66066A2EEACCDA 22 | ``` 23 | 24 | Next, you will need to add the Whonix stretch-testers repository to your package 25 | sources. 26 | 27 | ```sh 28 | echo 'deb http://deb.whonix.org stretch-testers main' | tee /etc/apt/sources.list.d/whonix-testing.list # apt-transport-* season to taste 29 | ``` 30 | 31 | Update your packages to see what is available from the new package source. 32 | 33 | ```sh 34 | sudo apt-get update 35 | ``` 36 | 37 | Install the tb-starter package and it's dependencies. 38 | 39 | ```sh 40 | sudo apt-get install tb-starter 41 | ``` 42 | 43 | Once you have tb-starter installed, you can launch your new Tor Browser for i2p 44 | by running 45 | 46 | ```sh 47 | i2pbrowser 48 | ``` 49 | 50 | In a terminal. 51 | -------------------------------------------------------------------------------- /articles/browser-config/WindowsTestingBrowser.md: -------------------------------------------------------------------------------- 1 | Using the Self-Installing i2p Browser Profile for Windows 2 | ========================================================= 3 | 4 | In order to make i2p simpler to use and to encourage safer practices with web 5 | browsers, I've created a browser profile for use with i2p and Firefox, coupled 6 | with an easy and reliable installer and launcher that will be familiar to 7 | Windows users. This profile endeavors to make everyday browsing with i2p safer 8 | and to automatically separate your clearnet browser use and your i2p browser 9 | user, while also disabling features of Firefox which are irrelevant or risky 10 | in the context of browsing i2p. 11 | 12 | Installation/Use: 13 | ----------------- 14 | 15 | First, in order to use this browser profile, you will need to install Firefox if 16 | you have not already. You can get the latest version from [Mozilla's web site](https://www.mozilla.org/en-US/firefox/new/). 17 | 18 | Next, you should download this [this .exe installer](https://github.com/eyedeekay/firefox.profile.i2p/releases/download/current/install-i2pbrowser.exe)(URL: https://github.com/eyedeekay/firefox.profile.i2p/releases/download/current/install-i2pbrowser.exe) 19 | and run it. It should detect your Firefox application automatically and 20 | configure the profile and launcher scripts. 21 | 22 | You're done! Now you can launch the i2p browser profile with the short-cuts that 23 | have been made on your Start Menu and Desktop. 24 | 25 | Notes: 26 | ------ 27 | 28 | With the standard launcher, which is labeled "I2PBrowser-Launcher" the profile 29 | is used in regular browsing mode, and some information like logins can persist 30 | between sessions. By launching "Private Browsing-I2PBrowser-Launcher" Firefox 31 | will automatically delete session information when you close the browser. 32 | 33 | For more information on it's development, see [the development repository](https://github.com/eyedeekay/firefox.profile.i2p/). 34 | 35 | In the next major release of i2p, this profile/installer will be integrated with 36 | java i2p automatically, with it's relevant launchers. 37 | -------------------------------------------------------------------------------- /articles/i2p-docker-services/BasicStaticeepSite.md: -------------------------------------------------------------------------------- 1 | Creating a simple static eepSite using Docker, Alpine, and i2pd 2 | =============================================================== 3 | 4 | One of the most common things I hear people say about i2p is that they have 5 | trouble finding interesting content on the existing eepSites. It's true, to an 6 | extent, as well. Most of the interesting eepSite content is, in fact, about i2p 7 | and i2p-related projects. That's not a bad thing, but it's a little unfortunate 8 | because it's actually very easy to host your own content on the i2p network. In 9 | this, the first of many guides to hosting web-like services within the i2p 10 | network using i2pd and Docker. 11 | 12 | Prerequisites 13 | ------------- 14 | 15 | The tutorial here assumes that you've already got a GNU/Linux machine with 16 | Docker installed and have at least a passing familiarity with using Docker from 17 | the terminal. If you need to install Docker, go [here for Debian-based Distros](https://docs.docker.com/install/linux/docker-ce/debian/), 18 | [here for Ubuntu-based distros](https://docs.docker.com/install/linux/docker-ce/ubuntu/), 19 | and go [here for Redhat based distros](https://docs.docker.com/install/linux/docker-ce/fedora/). 20 | On Alpine Linux, run "apk add docker" as root. 21 | 22 | ### Create a Docker network off the host 23 | 24 | In order to provide static IP addresses for the containers you generate, you'll 25 | need to create a separate Docker network with an explicitly defined, limited 26 | subnet. 27 | 28 | ``` 29 | docker network create --subnet 172.81.81.0/29 eepsite 30 | ``` 31 | 32 | ### Configuring an i2p router with a single HTTP service tunnel 33 | 34 | There are a number of Docker containers that can be used to run i2pd, but for 35 | the purposes of building services that run on i2pd, I like to make my own. I 36 | prefer this approach because I like to use the defaults that are used by the 37 | Debian package, and the easiest way to do that is to just use the Debian 38 | package. The trade-off, of course, is a somewhat larger container. 39 | 40 | #### The Dockerfile 41 | 42 | ```Dockerfile 43 | FROM debian:sid 44 | RUN apt-get update && apt-get dist-upgrade -y 45 | RUN apt-get install -y gpg ca-certificates 46 | RUN echo "deb http://repo.lngserv.ru/debian stretch main" | tee /etc/apt/sources.list.d/i2pd.list 47 | RUN echo "deb-src http://repo.lngserv.ru/debian stretch main" | tee -a /etc/apt/sources.list.d/i2pd.list 48 | RUN apt-key adv --keyserver ha.pool.sks-keyservers.net --recv 66F6C87B98EBCFE2 49 | RUN apt-get update && apt-get install -y i2pd 50 | COPY i2pd.conf tunnels.conf /etc/i2pd/ 51 | CMD chown -R i2pd:i2pd /var/lib/i2pd; \ 52 | ln -sf /usr/share/i2pd/certificates /var/lib/i2pd/certificates; \ 53 | ln -sf /etc/i2pd/subscriptions.txt /var/lib/i2pd/subscriptions.txt; \ 54 | su - -c "i2pd i2pd --service --loglevel=info \ 55 | --conf=/etc/i2pd/i2pd.conf \ 56 | --tunconf=/etc/i2pd/tunnels.conf \ 57 | --log=/var/log/i2pd/log"; \ 58 | sleep 5; \ 59 | tail -f /var/log/i2pd/log 60 | ``` 61 | 62 | 63 | Before we build, we'll need to create a configuration files to use for our 64 | Dockerized i2pd container. In the i2pd.conf file, you should disable the HTTP 65 | and SOCKS proxies and set the bandwidth to unlimited("X" in the configuration 66 | file). [An example i2pd.conf can be found here](i2pd.conf), it can be used for 67 | *all* of the forthcoming eepSite tutorials I will be writing. The other, 68 | slightly more interesting file is the tunnels.conf file. 69 | 70 | #### The tunnels.conf file 71 | 72 | ``` 73 | [DARKHTTPD] 74 | type = http 75 | host = eepsite-darkhttpd 76 | port = 8080 77 | inbound.length = 3 78 | outbound.length = 3 79 | keys = darkhttpd.dat 80 | ``` 81 | 82 | Note that the inbound.length and outbound.length are both set to three. This is 83 | optimized to make web sites anonymous, but it will cost some speed. Selecting 84 | a different length may be an acceptable trade-off to achieve higher speed and 85 | lower latency. 86 | 87 | #### Build and Run the container: 88 | 89 | Once you've got your configuration files and your Dockerfile created, run the 90 | following command to build the container (Where Dockerfile.i2pd is the newly 91 | created Dockerfile): 92 | 93 | ``` 94 | docker build --rm -f Dockerfile.i2pd -t dockerhub_username/eepsite . 95 | ``` 96 | 97 | And this command to run the container: 98 | 99 | ``` 100 | docker run --restart=always -i -t \ 101 | --name eepsite-i2pd \ 102 | --network eepsite \ 103 | --network-alias eepsite-i2pd \ 104 | --hostname eepsite-i2pd \ 105 | --link eepsite-darkhttpd \ 106 | --ip 172.81.81.2 \ 107 | -p :4567 \ 108 | -p 127.0.0.1:7070:7070 \ 109 | -v eepsite:/var/lib/i2pd \ 110 | dockerhub_username/eepsite-i2pd 111 | ``` 112 | 113 | ### Configuring DarkHTTPD with your content 114 | 115 | Now that your i2pd container is up and bootstrapping it's connection to the i2p 116 | network, you can start configuring your static eepSite container. To do this, 117 | you'll need a static web site to host. Either plain files or those generated by 118 | a static site generator like Jekyll will do. 119 | 120 | #### The Dockerfile 121 | 122 | ```Dockerfile 123 | FROM alpine:3.7 124 | ARG WEBSITE=website 125 | ENV WEBSITE=$WEBSITE 126 | RUN apk update 127 | RUN apk add darkhttpd 128 | COPY $WEBSITE /var/www/localhost/htdocs/$WEBSITE 129 | USER darkhttpd 130 | CMD darkhttpd /var/www/localhost/htdocs/$WEBSITE --port 8080 --log stdout --no-server-id 131 | ``` 132 | 133 | I keep my eepSite files in the same folder as the Dockefiles, under their own 134 | directory named "website" to make things easier when passing the website's files 135 | into the Docker build context. As you can see, the path used can be changed by 136 | passing an argument to the "docker build" command or the argument can be omitted 137 | for a default value of "website." The Dockerfile copies the contents of 138 | "website" into a folder owned by darkhttpd, changes to the darkhttpd user, and 139 | starts the server in the directory where we copied the files for our static 140 | site. 141 | 142 | #### Build and Run the container: 143 | 144 | The full command to build the image for your static eepsite is: 145 | 146 | ``` 147 | docker build --rm \ 148 | --build-arg WEBSITE=website \ 149 | -f Dockerfile.darkhttpd -t dockerhub_username/eepsite-darkhttpd . 150 | ``` 151 | 152 | with the argument included. Make sure to change the argument if your website 153 | is in a different directory than "website." 154 | 155 | Lastly, to run the container and serve the darkhttpd static website over i2p, 156 | run the command: 157 | 158 | ``` 159 | docker run --restart=always -i -t -d \ 160 | --name eepsite-darkhttpd \ 161 | --network eepsite \ 162 | --network-alias eepsite-darkhttpd \ 163 | --hostname eepsite-darkhttpd \ 164 | --ip 172.81.81.3 \ 165 | dockerhub_username/eepsite-darkhttpd 166 | ``` 167 | -------------------------------------------------------------------------------- /articles/i2p-docker-services/FreecivServerClient.md: -------------------------------------------------------------------------------- 1 | Gaming on i2p with Freeciv and Docker 2 | ===================================== 3 | 4 | It may surprise you, but it's actually possible to play games across anonymous 5 | networks under the right circumstances. While it's not especially likely that 6 | you'll be able to play real-time, demanding games while also having a high 7 | degree of anonymity anytime soon, it's entirely possible to play turn-oriented 8 | games, or to turn down the anonymity(and use i2p as a peer-to-peer network) and 9 | take advantage of the higher speed. This guide builds incrementally on the 10 | previous two guides by doing slightly more advanced configuration of i2pd's 11 | server tunnel, and adding in a client tunnel with a fixed destination. 12 | 13 | In this tutorial: 14 | ----------------- 15 | 16 | * We use single-hop tunnels. This is a bit like a VPN, but where you would use a random VPN server every time. *The intermediate node will know your IP address, but not what you are transmitting. The endpoints will not be able to discern eachother's IP addresses. If you desire greater anonymity, Freeciv can be played successfully with as many as 3 hops for both clients and servers*, but is sometimes less reliable. 17 | 18 | Freeciv over i2p: The Server 19 | ---------------------------- 20 | 21 | ### Preparation 22 | 23 | Like the previous tutorials, this tutorial requres a docker network for 24 | configuring the hosts and i2pd running in a docker container. For convenience's 25 | sake, we can use the existing container and network on 172.81.81.0, or we can 26 | create new ones. Hopefully by now this process is familiar, and readers have 27 | realized that configuring services to run across eepSites is very similar across 28 | the board. 29 | 30 | Alter your tunnels.conf file to contain this section: 31 | 32 | ``` 33 | [FREECIV-SERVER] 34 | type = server 35 | host = i2p-freeciv 36 | port = 5555 37 | inbound.length = 1 38 | inbound.quantity = 15 39 | outbound.length = 1 40 | outbound.quantity = 15 41 | keys = freeciv.dat 42 | ``` 43 | 44 | You'll see that we have some new details in this one compared to our old, 45 | http-based tunnels. While the options are pretty self explanatory, I'll go over 46 | them here too. 47 | 48 | * inbound.length: This is the length of the tunnel that the client connects to to send messages to the server. A shorter length corresponds to more speed, but it's easier to conduct traffic analysis against users who are using fewer hops. 49 | * outbound.length: This is the length of the tunnel that the server uses to reply to clients. The same basic rules apply to it as to inbound tunnels. 50 | * inbound.quantity: This is the number of tunnels that will be created to deal with inbound connections. In this case we're using alot of them, because we're trying to game. 51 | * outbound.quantity: This is the number of tunnels that will be created to deal with outbound connections. 52 | 53 | Now that you've customized your i2pd container, you can docker build/docker run 54 | it. 55 | 56 | ### Setting up Freeciv 57 | 58 | In order to make Freeciv run across i2p, it helps to make a few adjustments to 59 | Freeciv. 60 | 61 | #### Adjust the timeouts for connecting to the Freeciv Server 62 | 63 | Now that you've got your server tunnel, it's time to configure the Freeciv 64 | server. Freeciv server on Debian uses the folder /usr/share/games/freeciv/ 65 | to store it's ruleset configurations. I happen to like playing the Civ2/Civ3 66 | ruleset: /usr/share/games/freeciv/civ2civ3.serv. Copy that file to the 67 | directory where you're configuring your Freeciv server container. In order to 68 | make it work reliably with i2p, turn up the timeout options a bit by copying 69 | the following lines to the bottom: 70 | 71 | ``` 72 | set nettimeout=120 73 | set netwait=20 74 | set pingtime=60 75 | set pingtimeout=600 76 | ``` 77 | 78 | Of course, you can add these lines to any freeciv ruleset. I'd just make sure 79 | to add them at the end, to ensure that they are applied last. 80 | 81 | #### Install the Freeciv Server in a container 82 | 83 | A common mistake in Docker containers is to run applications as root in the 84 | container unnecessarily. In our Dockerfile, we create a user 'freeciv' to run 85 | our freeciv service. Besides that, we'll have to ensure that our server doesn't 86 | connect to the clearnet Freeciv metaserver. We can do this by explicitly 87 | defining the command to be run to start the server. 88 | 89 | #### The Dockerfile 90 | 91 | So, to create a container which uses your modified ruleset, you can use this 92 | Dockerfile: 93 | 94 | ```Dockerfile 95 | FROM debian:sid 96 | ARG file=civ2civ3.serv 97 | ENV file=$file 98 | RUN apt-get update 99 | RUN apt-get install -y freeciv-server 100 | RUN adduser --disabled-password --gecos ',,,,' freeciv 101 | WORKDIR /usr/share/games/freeciv/ 102 | COPY $file /usr/share/games/freeciv/$file 103 | WORKDIR /home/freeciv 104 | USER freeciv 105 | CMD /usr/games/freeciv-server \ 106 | --bind 0.0.0.0 \ 107 | --port 5555 \ 108 | --identity "i2p-freeciv" \ 109 | -r /usr/share/games/freeciv/$file \ 110 | --exit-on-end 111 | ``` 112 | 113 | And build it like this: 114 | 115 | ``` 116 | docker build --rm \ 117 | --build-arg "file"="civ2civ3.serv" \ 118 | -f Dockerfile -t eyedeekay/i2p-freeciv . 119 | ``` 120 | 121 | And finally, run it like this: 122 | 123 | ``` 124 | docker run --restart=always -i -t -d \ 125 | --name i2p-freeciv \ 126 | --network eepsite \ 127 | --network-alias i2p-freeciv \ 128 | --hostname i2p-freeciv \ 129 | --ip 172.81.81.3 \ 130 | eyedeekay/i2p-freeciv 131 | ``` 132 | 133 | Freeciv over i2p: The Client 134 | ---------------------------- 135 | 136 | ### Prerequisites 137 | 138 | Similar to the previous tutorials, except in this case it is intended to be run 139 | on a computer other than the computer running the server. You still need an i2p 140 | router running on the client computer. 141 | 142 | Particularly, you will need the destination(either the base32 or the 143 | addresshelper address) of an existing i2p-based Freeciv server. Intermittently, 144 | there will be one available at the following b32: 145 | 4q7zxgr27pwybbqizpv6nhmriidgwj3owqt33jvuijmro57l7jdq.b32.i2p, but it's not going 146 | to be up all the time (it's the one I used to test this on my laptop). I'm going 147 | to use it in the example. 148 | 149 | ### Setting up i2pd 150 | 151 | We haven't configured a client tunnel in this series of guides yet. Let's do 152 | that now. 153 | 154 | #### Client tunnel configuration 155 | 156 | Clients will need a destination to connect to, corresponding to a server like 157 | the one we already set up. In this case, the client tunnel should also listen on 158 | all addresses so other containers on the docker network can use it to connect to 159 | the Freeciv server. 160 | 161 | ``` 162 | [FREECIV-CLIENT] 163 | type = client 164 | address = 0.0.0.0 165 | port = 5555 166 | destination = 4q7zxgr27pwybbqizpv6nhmriidgwj3owqt33jvuijmro57l7jdq.b32.i2p 167 | inbound.length = 1 168 | inbound.quantity = 15 169 | outbound.length = 1 170 | outbound.quantity = 15 171 | keys = freeciv-client.dat 172 | ``` 173 | 174 | You'll notice that most of the options are the same between the server and 175 | client. The big difference, the destination option, is set to the base32 of a 176 | freeciv server running on i2p. 177 | 178 | ### Setting up Freeciv 179 | 180 | In this example, we're using the freeciv-client-gtk3 client to connect to the 181 | Freeciv server. The instructions below can at least be adapted to the SDL and 182 | QT versions, possibly all versions of the Freeciv client. 183 | 184 | #### Freeciv Client Configuration 185 | 186 | In order to successfully connect to the Freeciv server through i2p, use the 187 | newly created client tunnel host:port with the --autoconnect option in your 188 | final CMD in your Dockerfile. 189 | 190 | ``` 191 | /usr/games/freeciv-gtk3 \ 192 | --autoconnect \ 193 | --server 172.81.81.2 \ 194 | --port 5555 195 | ``` 196 | 197 | #### The Dockerfile 198 | 199 | Is extremely self-explanatory. 200 | 201 | ```Dockerfile 202 | FROM debian:sid 203 | RUN apt-get update 204 | RUN apt-get install -y freeciv-client-gtk3 205 | RUN adduser --disabled-password --gecos ',,,,' freeciv 206 | USER freeciv 207 | CMD /usr/games/freeciv-gtk3 \ 208 | --autoconnect \ 209 | --server 172.81.81.2 \ 210 | --port 5555 211 | ``` 212 | 213 | You can build it with: 214 | 215 | ``` 216 | docker build --rm \ 217 | -f Dockerfile.client -t eyedeekay/i2p-freeciv-client . 218 | ``` 219 | 220 | and run it by forwarding to your local X server with: 221 | 222 | ``` 223 | docker run -i -t --rm \ 224 | -e DISPLAY=:0 \ 225 | --name i2p-freeciv-client \ 226 | --network eepsite \ 227 | --network-alias i2p-freeciv-client \ 228 | --hostname i2p-freeciv-client \ 229 | --ip 172.81.81.4 \ 230 | --link freeciv-i2pd \ 231 | --volume freeciv-client:/home/freeciv \ 232 | --volume /tmp/.X11-unix:/tmp/.X11-unix:ro \ 233 | eyedeekay/i2p-freeciv-client 234 | ``` 235 | 236 | Find some players! 237 | ------------------ 238 | 239 | Lastly, you'll need to find some players! Head on over to a public forum for i2p 240 | users like [r/i2p](https://reddit.com/r/i2p), [i2pforums](https://i2pforum.net), 241 | or visit i2prc, and find some other i2p users to play with. If they use i2pd, 242 | you can re-use the same tunnels.conf for clients on their routers without 243 | needing to change it at all. Enjoy! 244 | -------------------------------------------------------------------------------- /articles/i2p-docker-services/GithubPagesMirror.md: -------------------------------------------------------------------------------- 1 | Mirroring an existing Github Pages site using Jekyll and i2p, with Tor for location obfuscation 2 | =============================================================================================== 3 | 4 | This is kind of a softball tutorial, it's almost the same as the **[Previous tutorial](BasicStaticeepSite.md):** 5 | but it's intended specifically to allow you to mirror a Github Pages based site 6 | using Jekyll to i2p using i2pd and Tor. Of course, this means that the 7 | eepSite is by definition linked to your identity on Github, but this might be 8 | desirable, for instance for i2p applications that collaborate primarily by way 9 | of Github, but who wish to have a presence on i2p as well. Probably other cases 10 | where long-term pseudonymity is desirable. 11 | 12 | So, just to be clear 13 | -------------------- 14 | 15 | * *For this tutorial to be unlinkable to your real identity, your github must be unlinkable to your real identity.* 16 | * *It does not conceal your identity on github(username, repository) from visitors, but it does conceal your IP address from github.* 17 | * *This is pseudonymous, location-obfuscated mirroring of a github pages site.* 18 | 19 | Now with that out of the way, let's get down to mirroring a Github Pages site, 20 | for example this exact wiki, to your own i2p eepSite. 21 | 22 | Preparation 23 | ----------- 24 | 25 | To get started, you'll need an i2pd docker container with an http server tunnel 26 | prepared. For convenience's sake, you can just use the one from the previous 27 | tutorial. First, make sure you've created your network and specified a subnet, 28 | as in the first tutorial: 29 | 30 | ``` 31 | docker network create --subnet 172.81.81.0/29 eepsite 32 | ``` 33 | 34 | And alter the tunnels.conf in your tunnels.conf to look like this: 35 | 36 | ``` 37 | [DARKHTTPD] 38 | type = http 39 | host = eepsite-darkhttpd 40 | port = 8080 41 | inbound.length = 3 42 | outbound.length = 3 43 | keys = darkhttpd.dat 44 | 45 | [GITHUB] 46 | type = http 47 | host = eepsite-github 48 | port = 8090 49 | inbound.length = 3 50 | outbound.length = 3 51 | keys = github.dat 52 | ``` 53 | 54 | Once you've done that, you can `docker build` the new container and your 55 | original, darkhttpd tunnel will continue to exist at the same destination but a 56 | new unique destination will be generated for your forthcoming Github mirror. 57 | From the perspective of someone browsing the i2p network, and the other routers 58 | in the i2p network, there will be no good reason to believe that either of those 59 | tunnels are running on the same i2p router. If you no longer want the original 60 | darkhttpd tunnel, then you can just delete the [DARKHTTPD] section from your 61 | tunnels.conf. 62 | 63 | Obfuscating the IP address of your container host 64 | ------------------------------------------------- 65 | 66 | In order to fetch your repositories from git pseudonymously, or in order to 67 | obfuscate your location as a git user, you will need to ensure that git is 68 | configured to fetch clearnet resources via Tor. In order to do this, we'll add a 69 | container running Tor to our docker network, with an exposed SocksPort. 70 | Additionally, we will do no actual building or generation of the Github Pages 71 | mirror until the containers are running and present on the network. In order to 72 | safely host any site that requests resources from the clearnet, you will need to 73 | do a similar procedure to route it through Tor. For git, this procedure is 74 | simple to do so it makes a good example. 75 | 76 | For the purposes of this demonstration, we're going to assume that the pertinent 77 | adversaries do not have sufficient power to link your fetching of packages via 78 | the rubygems package manager to your eepsite activity. If that's an issue for 79 | you, I kinda hope you don't need this tutorial. It also assumes that you are 80 | not concerned about separating contextual identities *because* you are only 81 | going to use this Tor SocksProxy to fetch git repositories associated with one 82 | account anyway. So here's our Tor container Dockerfile: 83 | 84 | ### Tor container Dockerfile 85 | 86 | ```Dockerfile 87 | FROM alpine:3.7 88 | ARG TOR_CONTROL_HOST=172.81.81.6 89 | ARG TOR_CONTROL_PORT=9151 90 | ARG TOR_SOCKS_HOST=172.81.81.6 91 | ARG TOR_SOCKS_PORT=9150 92 | RUN apk update && apk add tor 93 | COPY torrc /etc/tor/torrc 94 | RUN sed -i "s|172.81.81.6|$TOR_CONTROL_HOST|g" /etc/tor/torrc 95 | RUN sed -i "s|9151|$TOR_CONTROL_PORT|g" /etc/tor/torrc 96 | RUN sed -i "s|172.81.81.6|$TOR_SOCKS_HOST|g" /etc/tor/torrc 97 | RUN sed -i "s|9150|$TOR_SOCKS_PORT|g" /etc/tor/torrc 98 | RUN mkdir -p /var/lib/tor 99 | RUN chown -R tor /var/lib/tor 100 | RUN chmod -R 2700 /var/lib/tor 101 | RUN chmod -R o+rw /var/lib/tor 102 | EXPOSE $TOR_CONTROL_PORT 103 | EXPOSE $TOR_SOCKS_PORT 104 | USER tor 105 | CMD tor -f /etc/tor/torrc 106 | ``` 107 | 108 | Of course, you'll need a minimal .torrc to configure your Tor service with. 109 | 110 | ### minimal torrc 111 | 112 | ``` 113 | SOCKSPort 172.81.81.6:9150 114 | SOCKSPolicy accept 172.81.81.0/24 115 | DataDirectory /var/lib/tor 116 | ControlPort 172.81.81.6:9151 117 | CookieAuthentication 1 118 | ``` 119 | 120 | Keep it in your docker build context. If you have the resources, consider making 121 | it a relay or hosting a Snowflake service. 122 | 123 | ### Building and Running the Tor container 124 | 125 | Finally, build the Tor container using the following command: 126 | 127 | ``` 128 | docker build --force-rm \ 129 | --build-arg TOR_SOCKS_PORT=9150 \ 130 | --build-arg TOR_SOCKS_HOST=172.81.81.6 \ 131 | --build-arg TOR_CONTROL_PORT=9151 \ 132 | --build-arg TOR_CONTROL_HOST=172.81.81.6 \ 133 | --network eepsite \ 134 | -f Dockerfile.torhost -t eyedeekay/tor-host . 135 | ``` 136 | 137 | And run it using the following command: 138 | 139 | ``` 140 | docker run --rm -i -t -d \ 141 | --net tbb \ 142 | --name eepsite-tor \ 143 | --network eepsite \ 144 | --network-alias eepsite-tor \ 145 | --hostname eepsite-tor \ 146 | --link eepsite-github \ 147 | --expose 9150 \ 148 | --ip 172.81.81.6 \ 149 | eyedeekay/tor-host; true 150 | ``` 151 | 152 | Mirroring your github page 153 | -------------------------- 154 | 155 | Once your Tor service is up, you're ready to start mirroring your github page. 156 | To do this, while only fetching git repositories over Tor, you can use an Alpine 157 | Linux container with ruby, ruby-bundler, and some libraries. We're also going to 158 | configure our tools, git and bundle, but not use them to fetch any resources 159 | yet. 160 | 161 | ### Github Pages Mirror Dockerfile 162 | 163 | ```Dockerfile 164 | FROM alpine:3.7 165 | ARG PAGES_REPO_NWO=j-tt/r-i2p-wiki 166 | ARG proxy=socks5://172.81.81.6:9150 167 | ENV PAGES_REPO_NWO=$PAGES_REPO_NWO JEKYLL_ENV=production proxy=$proxy 168 | RUN apk update && apk add git ruby ruby-dev make gcc g++ musl musl-dev ruby-rdoc ruby-irb ruby-xmlrpc libxml2 zlib zlib-dev markdown ruby-bundler 169 | RUN adduser -h /var/www/ -D user 170 | RUN git config --global http.proxy $proxy 171 | WORKDIR /var/www/ 172 | RUN chown -R user . 173 | USER user 174 | RUN bundle config --local path /var/www/.bundle 175 | COPY loop.sh /usr/bin/loop.sh 176 | CMD loop.sh 177 | ``` 178 | 179 | Finally, we need to create a launcher script. This script will create the site 180 | folder, populate it, guarantee the contents of the Gemfile and serve the site. 181 | 182 | ### Github Pages Mirror Congigurator 183 | 184 | ```Shell 185 | #! /usr/bin/env /bin/sh 186 | git config --global http.proxy $proxy 187 | git clone https://github.com/$PAGES_REPO_NWO /var/www/site 188 | cd /var/www/site || exit 189 | touch Gemfile 190 | grep "source 'https://rubygems.org'" Gemfile || \ 191 | echo "source 'https://rubygems.org'" | tee -a Gemfile 192 | grep "gem 'github-pages', group: :jekyll_plugins" Gemfile || \ 193 | echo "gem 'github-pages', group: :jekyll_plugins" | tee -a Gemfile 194 | grep "gem '$theme', group: :jekyll_plugins" Gemfile || \ 195 | echo "gem '$theme', group: :jekyll_plugins" | tee -a Gemfile 196 | bundle install 197 | bundle exec jekyll serve --port 8090 --host 0.0.0.0 --baseurl "" 198 | ``` 199 | 200 | Now you've got a container ready to build and run, which will host a github 201 | page mirror on i2p, but only fetch the repo from github over Tor. Every time you 202 | run the container, you'll get the most up-to-date version of the ruby packages 203 | you need. 204 | 205 | ### Build the container 206 | 207 | This container can generically mirror any github page passed to it using the 208 | --build-arg PAGES\_REPO\_NWO option. For example, in order to mirror this wiki, 209 | you can pass j-tt/r-i2p-wiki: 210 | 211 | ``` 212 | docker build --rm \ 213 | --build-arg PAGES_REPO_NWO="j-tt/r-i2p-wiki" \ 214 | --build-arg proxy=socks5://172.81.81.6:9150 \ 215 | --build-arg theme=jekyll-theme-minimal \ 216 | -f Dockerfile.github -t eyedeekay/eepsite-github . 217 | ``` 218 | Now it's ready to run. 219 | 220 | ``` 221 | docker run --restart=always -i -t -d \ 222 | --name eepsite-github \ 223 | --network eepsite \ 224 | --network-alias eepsite-github \ 225 | --hostname eepsite-github \ 226 | --link eepsite-tor \ 227 | --ip 172.81.81.5 \ 228 | eyedeekay/eepsite-github 229 | ``` 230 | 231 | It will take quite a while to bootstrap the github pages environment, but soon 232 | you will have a githhub pages mirror as an eepSite. 233 | -------------------------------------------------------------------------------- /articles/i2p-docker-services/README.md: -------------------------------------------------------------------------------- 1 | Configuring services with Docker and i2pd ([articles](../README.md)) 2 | ======================================================== 3 | 4 | This is a series of guides to setting up various services within the i2p network. 5 | They're sorted from simplest to most difficult, and intended to illustrate 6 | basic tasks one might carry out using i2pd and docker. 7 | 8 | * **[Configuring a Simple Static eepSite](BasicStaticeepSite.md):** Host 9 | simple static content on i2p in minutes. By @eyedeekay [source](https://github.com/eyedeekay/basic-eepsite) 10 | * **[Mirroring a Github Pages site as an eepSite](GithubPagesMirror.md):** Expand 11 | on the static eepsite tutorial by enabling a Github Pages mirror. By @eyedeekay [source](https://github.com/eyedeekay/github-eepsite) 12 | * **[Gaming on i2p with Freeciv and Docker](FreecivServerClient.md):** Set up 13 | a Freeciv client and server, using i2p. By @eyedeekay [source](https://github.com/eyedeekay/freeciv-tunnels) 14 | -------------------------------------------------------------------------------- /articles/i2p-docker-services/i2pd.example.conf: -------------------------------------------------------------------------------- 1 | ## Configuration file for a simple i2p eepSite 2 | port = 4567 3 | ## Enable communication through ipv4 4 | ipv4 = true 5 | ## Enable communication through ipv6 6 | ipv6 = true 7 | nat = true 8 | bandwidth = X 9 | 10 | [upnp] 11 | enabled = true 12 | 13 | [reseed] 14 | verify = true 15 | 16 | [http] 17 | enabled = true 18 | address = 0.0.0.0 19 | port = 7070 20 | 21 | [httpproxy] 22 | enabled = false 23 | 24 | [socksproxy] 25 | enabled = false 26 | 27 | [i2pcontrol] 28 | ## Uncomment and set to 'true' to enable I2PControl protocol 29 | enabled = false 30 | ## Address and port service will listen on 31 | #address = 0.0.0.0 32 | #port = 7650 33 | ## Set password 34 | #password = default 35 | -------------------------------------------------------------------------------- /getting-started.md: -------------------------------------------------------------------------------- 1 | # TODO 2 | 3 | ==== 4 | [HOME](README.md) | [Subreddit](https://www.reddit.com/r/i2p/) 5 | ---- | ---- 6 | -------------------------------------------------------------------------------- /security-considerations.md: -------------------------------------------------------------------------------- 1 | # I2P Security Considerations 2 | 3 | I2P is a great tool for online privacy & security, but like any software, it is not perfect. There are issues one needs to consider before and during use of I2P. 4 | 5 | This is in no way a comprehensive guide to I2P security, and there may be some mistakes. 6 | 7 | ## Traffic Correlation 8 | 9 | Traffic correlation is a problem with all anonymity networks, especially in low-latency networks like I2P. 10 | 11 | Assuming one is not using a VPN, a user's Internet provider will know that they are using I2P, how much traffic they are relaying, and even potentially who/what they are communicating with if they can combine this information with other nodes in the I2P network, or with other ISPs data. 12 | 13 | I2P-Bote, a sub-network inside I2P for anonymous mail exchange protects against this to some extent by obscuring the recipent of a message and by being high-latency. 14 | 15 | ### VPNs 16 | 17 | VPNs can be used before connecting to the I2P network, but all this will do is obscure the fact that a user is using I2P from their ISP. If one lives in a country with decent human rights, this is not generally necessary, and [in some cases can even harm one's privacy](https://matt.traudt.xyz/posts/vpn-tor-not-mRikAa4h.html) (Related to Tor, but applies mostly the same to I2P) 18 | 19 | ## Browser Fingerprinting 20 | 21 | Eepsites are a popular feature of I2P, however these websites posses the ability to potentially fingerprint and track a user's web browser. Having JavaScript enabled is especially risky, however [CSS alone can be used to track someone too](https://matt.traudt.xyz/posts/how-css-alone-YF4ciVY6.html) (Related to Tor, but applies the same to I2P). 22 | 23 | If a user's browser is sufficiently unique enough, this will greatly increase the ability for an adversary to track them, especially if they use the same/similar configuration on the clearnet. 24 | 25 | It is recommended to configure the Tor Browser Bundle for I2P and to not resize the browser window. 26 | 27 | ## User Profiling 28 | 29 | Besides browsers & traffic, a user can also be profiled based on their behavior. For example, if one uses a particular style of writing, posts at certain times of the day, reuses usernames & passwords, contact information, personal information, etc, this can be used to track a user cross-services, and even potentially to a clearnet identity. 30 | 31 | For example, [language patterns were used to track down a pedophile in 2016](https://www.deepdotweb.com/2016/07/20/police-infiltrated-darknet-forum-hunt-pedophiles/). 32 | 33 | One should be careful with the language they use and information they reveal. 34 | 35 | ## Malware 36 | 37 | If a user's device is already compromised with malware, no software including I2P can effectively defend against it. This includes any malicious design in a user's OS or hardware. 38 | 39 | Users should consider booting into a Live OS on trusted hardware to use I2P, if preexisting malware is a concern. 40 | 41 | ## Quantum Security & Future Exploits 42 | 43 | If one's communications must stay secret forever, then they should worry about future exploits of cryptography, particularly with quantum computers. Most public key cryptography is vulnerable to quantum computers, however this is likely out of most user's threat model currently, and I2P has forward secrecy which would require an adversary to intercept & store **complete** streams until a suitable computer exists, which would be very difficult to do. 44 | 45 | 46 | ## Legal Considerations 47 | 48 | As stated earlier, internet providers can see that a user is using I2P, which may be problematic if a user is in a location where encryption or online anonymity would draw suspicion. Remember, no encryption can protect against [a $5 wrench](https://xkcd.com/538/) 49 | 50 | ![XKCD 538](https://imgs.xkcd.com/comics/security.png) 51 | -------------------------------------------------------------------------------- /sidebar.md: -------------------------------------------------------------------------------- 1 | # The Invisible Internet Project 2 | *"Cousin of R2D2"* 3 | 4 | 5 | # New to I2P? Use these! 6 | 7 | * [A text-only tutorial on eepsites and I2P torrenting](https://rebuildingalexandria.wordpress.com/2012/02/21/secure-and-anonymous-file-sharing-using-torrents-on-the-i2p-network-library-nu-exiles-take-a-look/) 8 | 9 | * [Basic video tutorials (installation, tweaks, browser configuration, irc, torrents)](https://www.youtube.com/user/i2ptutorials) 10 | 11 | * [r/i2p Wiki](https://j-tt.github.io/r-i2p-wiki/) 12 | 13 | I2P can be downloaded [here](http://www.i2p2.de) 14 | 15 | # FAQ: 16 | 17 | * I found a bug! 18 | 19 | Check [this thread](https://pay.reddit.com/r/i2p/comments/1bnhb3/official_report_bugs_here_thread/) on how to report it. 20 | 21 | * Can I use I2P as a proxy to the internet? 22 | 23 | It's not recommended as that is not the main use of I2P, but you can. See information on [outproxies](http://www.i2p2.de/faq.html#exit) for more. 24 | 25 | # I2P links of interest: 26 | 27 | For a more complete list of interesting I2P services, read the [Guide to I2P services](http://pastebin.com/xWzw10wW). 28 | 29 | ## General 30 | * [Main project site](http://i2p-projekt.i2p) 31 | * [I2P Forum](http://i2pforum.i2p) ([clearnet](https://i2pforum.net/)) Official I2P community and development forum 32 | * [zzz](http://zzz.i2p) zzz's personal website, old developers forum 33 | * [planet.i2p](http://planet.i2p) RSS aggregator 34 | * [I2P-Bote](http://bote.i2p) Serverless, encrypted e-mail plugin for I2P 35 | 36 | ## File Hosting and Pastebins 37 | * [i2push](http://i2push.i2p) File hosting 38 | * [Zerobin](http://zerobin.i2p) Encrypted Pastebin 39 | * [FS](http://fs.i2p) Filesharing service 40 | * [PrivateBin](http://paste.r4sas.i2p/) Other encrypted pastebin 41 | * [Pasta NoJS](http://pasta-nojs.i2p/) Basic pastebin (JavaScript-free) 42 | 43 | ## Torrents 44 | * [PaTracker](http://tracker2.postman.i2p) Main torrent tracker 45 | * [DifTracker](http://diftracker.i2p) (French) torrent tracker 46 | * [Anodex](http://anodex.i2p) Torrents index 47 | 48 | ## Social Networks and Microblogging 49 | * [Visibility](http://visibility.i2p) Social Publishing 50 | * [Decentralized social network](http://em763732l4b7b7zhaolctpt6wewwr7zw3nsxfchr6qmceizzmgpa.b32.i2p) ([clearnet](https://social.i2p.rocks)) 51 | 52 | ## Exploring I2P 53 | * [Identiguy](http://identiguy.i2p) List online .i2p sites 54 | * [I2P Name Registry](http://inr.i2p) 55 | 56 | ## IRC 57 | *Irc2P comes pre-configured with I2P. To connect with other networks, please follow [this tutorial](http://i.imgur.com/PxZLa.png).* 58 | 59 | * [Irc2P](irc://127.0.0.1/6668/#i2p-chat) (works out of the box) 60 | 61 | ## Syndie 62 | An open source system for operating distributed forums in anonymous networks 63 | 64 | * [Syndie Project](http://syndie-project.i2p) Syndie Project Website 65 | * [Syndie Documentation Project](http://fomjl7cori4juycw55kdlczpgzzhme6nox6zykokuiov6t5lxhvq.b32.i2p) 66 | * syndie.darrob.i2p 67 | * syndie.echelon.i2p 68 | * syndie.inscrutable.i2p 69 | * syndie.killyourtv.i2p 70 | * syndie.meeh.i2p 71 | * syndie.welterde.i2p 72 | 73 | ## Inproxies 74 | *Don't have I2P? You can still access .i2p sites using an inproxy! Just add .xyz after .i2p in your URL.* 75 | 76 | 77 | # Sister Subreddits 78 | * /r/onions 79 | * /r/Torrents 80 | * /r/Anoncoin 81 | * /r/Bitcoin 82 | * /r/Darknetplan 83 | * /r/Privacy 84 | * /r/Crypto 85 | * /r/CryptoAnarchy 86 | * /r/P2P 87 | * /r/Filesharing 88 | * /r/evolutionReddit 89 | * /r/NSALeaks 90 | 91 | Follow us on [](https://twitter.com/r_i2p) 92 | 93 | If you have made a submission to this subreddit and it isn't showing up, PM the moderators! It might be stuck in the spam filter. 94 | --------------------------------------------------------------------------------