224 Commits

Author SHA1 Message Date
be2e3225e3 Update bundle news
Some checks failed
Sync Primary Repository to GitHub Mirror / sync (push) Has been cancelled
2025-06-07 23:13:15 -04:00
797b5f11e5 fix url in update file
Some checks failed
Sync Primary Repository to GitHub Mirror / sync (push) Has been cancelled
2025-06-02 18:36:24 -04:00
2e71ac306e update torrent version 2025-06-02 17:37:13 -04:00
3a37ab6b2c update torrent
Some checks failed
Sync Primary Repository to GitHub Mirror / sync (push) Has been cancelled
2025-06-02 16:33:48 -04:00
idk
07774d90a7 Update data/entries.html
Some checks failed
Sync Primary Repository to GitHub Mirror / sync (push) Has been cancelled
2025-05-30 14:03:00 -04:00
idk
551f895b8e Update data/entries.html
Some checks failed
Sync Primary Repository to GitHub Mirror / sync (push) Has been cancelled
2025-05-30 12:02:50 -04:00
idk
2ce99a843f Update data/entries.html
Some checks failed
Sync Primary Repository to GitHub Mirror / sync (push) Has been cancelled
2025-05-30 12:02:08 -04:00
b0c3682586 Draft release notes 2.9.0
Some checks failed
Sync Primary Repository to GitHub Mirror / sync (push) Has been cancelled
2025-05-29 20:03:33 -04:00
f621c5634a Add test.sh script
Some checks failed
Sync Primary Repository to GitHub Mirror / sync (push) Has been cancelled
2025-05-12 21:37:09 -04:00
zzz
3ff7257620 blocklist update
All checks were successful
Sync Primary Repository to GitHub Mirror / sync (push) Successful in 6s
2025-05-11 18:06:01 -04:00
90f10fc7e1 Add github sync for i2p.newsxml
All checks were successful
Sync Primary Repository to GitHub Mirror / sync (push) Successful in 5s
2025-05-10 18:53:58 -04:00
zzz
92db73685a blocklist update 2025-05-03 10:10:11 -04:00
5a4976aeff update bundle news 2025-04-02 14:55:55 -04:00
9973cad50c check in data/translations 2025-03-29 16:58:29 -04:00
31dc6ce7ad Merge branch 'master' of 127.0.0.1:i2p-hackers/i2p.newsxml 2025-03-29 16:43:06 -04:00
412c12e701 check in new translations from tx 2025-03-29 10:33:06 -04:00
zzz
f38e4fd894 2.8.2 metadata
Fix blog post URL
2025-03-29 09:18:08 -04:00
zzz
228dd41681 2.8.2 news 2025-03-26 10:57:22 -04:00
d76d5ad371 Fix summary 2025-03-21 17:19:43 -04:00
2b8d2d0abf Easy-Install news 2025-03-21 13:35:04 -04:00
e0214aaa36 check in new translations 2025-03-17 19:03:46 -04:00
zzz
f933d9c9b4 2.8.1 2025-03-17 13:06:39 -04:00
199f495445 Merge branch 'master' of i2pgit.org:i2p-hackers/i2p.newsxml 2025-03-14 14:44:15 -04:00
zzz
6761d53403 2.8.1 news 2025-03-14 14:29:03 -04:00
52f4fcdd14 update easy-install news 2025-02-12 12:23:14 -05:00
10bf10704a update easy-install torrent 2025-02-12 12:22:22 -05:00
zzz
b2f327611c new entry about 2.8.0 bug 2025-02-08 11:24:25 -05:00
ac563bb2c4 update versions in update feed 2025-02-04 18:08:44 -05:00
87f9116b35 add new translations 2025-02-04 17:29:07 -05:00
a1df0a513c update releases.json 2025-02-04 17:20:30 -05:00
4a7e83e845 update translations 2025-02-04 16:43:03 -05:00
769c24708b one more 2.8.0 revision 2025-01-31 14:20:54 -05:00
5b7c482cc4 More revisions to 2.8.0 entry 2025-01-31 13:58:13 -05:00
03dbdc811b Revisions to 2.8.0 entry 2025-01-31 13:54:36 -05:00
c9c84f03aa Merge branch 'master' of i2pgit.org:i2p-hackers/i2p.newsxml 2025-01-31 13:35:58 -05:00
9cc4c22612 Update entries.html 2025-01-31 13:35:03 -05:00
zzz
880e071ace blocklist update 2025-01-21 09:48:44 -05:00
8328a5f386 Easy-Install news and torrent 2024-10-20 16:11:35 -04:00
e2da9e4836 Merge branch 'master' of i2pgit.org:i2p-hackers/i2p.newsxml 2024-10-08 12:48:35 -04:00
79284631dd Update the torrent 2024-10-08 12:48:04 -04:00
f14b8a3883 Release: update dates for core news torrent 2024-10-08 12:26:41 -04:00
zzz
ca2c435230 blocklist update 2024-10-05 09:29:18 -04:00
d90239bd0b Move date ahead 4 days 2024-10-04 14:39:01 -04:00
e7b5599714 Merge branch 'master' of i2pgit.org:i2p-hackers/i2p.newsxml 2024-10-04 12:38:49 -04:00
ab0df485e3 Check in 2.7.0 news 2024-10-04 12:34:39 -04:00
zzz
b27a4cb0d3 blocklist update 2024-10-02 09:06:59 -04:00
zzz
ec6700cb52 blocklist update 2024-09-28 09:36:16 -04:00
ce20007f20 update translations and rebuild news 2024-08-26 20:24:15 -04:00
29e4d76349 Copy news for Easy-Install 2024-08-26 18:44:53 -04:00
b376832715 Update news for easy-install 2024-08-26 18:43:38 -04:00
eb0930bf78 Remove malformed whitespace 2024-08-08 13:01:44 -04:00
7f6ac69821 update torrent in releases.json 2024-08-06 22:37:22 -04:00
fa90fe82d1 Set blog date to release date 2024-08-02 13:41:47 -04:00
0e3d5d2dd0 Fix title and link
Signed-off-by: eyedeekay <hankhill19580@gmail.com>
2024-08-02 13:40:45 -04:00
ed8e38da8c Release 2.6.1 2024-08-02 13:40:11 -04:00
d88b19b683 update news for Easy-Install Windows
Signed-off-by: eyedeekay <hankhill19580@gmail.com>
2024-07-21 00:02:16 -04:00
b94f7592da update translations 2024-07-20 23:55:45 -04:00
8e44fc8bae update torrent in newsfeed 2024-07-19 13:59:22 -04:00
02a9eefdf2 Make the blog post match up when author presupplies a DATE to the create_new_entry.sh script 2024-07-16 14:42:58 -04:00
zzz
21f29bff94 spelling fix, date fix 2024-07-16 05:48:57 -04:00
ad1d921a87 Don't indent 2024-07-16 01:28:12 -04:00
4070661a61 Say IP addresses instead of IPs 2024-07-16 00:39:34 -04:00
e75a026971 Make the Tor announcement more firm 2024-07-16 00:38:26 -04:00
a7e89f4873 Update script, add new news 2024-07-16 00:36:55 -04:00
91ada8b553 point at the release blog post 2024-05-15 23:23:58 -04:00
a10dd55f30 check in translations, update the windows bundle torrents 2024-05-15 23:12:11 -04:00
zzz
f19a7f53ac 2.5.2 metadata 2024-05-15 09:35:03 -04:00
zzz
64acb1c69e Force leading zeros in blog entry paths 2024-05-14 14:10:58 -04:00
zzz
0c4b6184b3 2.5.2 news entry 2024-05-14 14:08:38 -04:00
8d1097c8ca Fix date 2024-05-06 18:58:49 -04:00
ac67ae3423 Update translations 2024-05-06 18:25:07 -04:00
734dda86b3 Fix static su3 download URLs 2024-05-06 17:56:10 -04:00
ef2da63636 Update version, update torrent 2024-05-06 17:05:29 -04:00
d35d987659 Fix href in stormy weather post 2024-05-05 09:50:54 -04:00
b44ca0d261 Fix href 2024-05-05 09:48:36 -04:00
4eda689238 Fix blog post dates, capitalize 'Sybil', fix typos 2024-05-05 09:39:04 -04:00
b861221715 Fix date on blog post 2024-05-04 10:47:11 -04:00
59f8ba9f42 Write entry for release 2.5.1 2024-05-04 10:27:15 -04:00
dfd84da9db Add attack news 2024-04-25 22:45:47 -04:00
d7edf9a06a update easy-install news 2024-04-09 00:08:45 -04:00
66d9426623 update torrent 2024-04-08 13:15:59 -04:00
zzz
4134129656 grammar fix, change dates, remove whitespace 2024-04-06 11:41:08 -04:00
163233ba1c Update: 2.5.0 news entry 2024-04-06 11:01:12 -04:00
198dbf9a1d update Easy-Install for Windows release 2024-03-20 15:57:20 -04:00
401a21568c give more options for pre-configuring content of news entry in create_new_entry.sh 2024-03-19 23:40:27 -04:00
zzz
304040328b blocklist update 2024-03-16 09:11:31 -04:00
c09da4ae1d Update torrents for Easy-Install Bundle 2023-12-31 04:59:26 -05:00
440bc4f7d0 Fix json formatting in releases.json 2023-12-20 13:37:31 -05:00
1841ecfb81 Re-add stats as update source, fix version 2023-12-19 12:21:34 -05:00
5043e46a65 fix version in backup URL 2023-12-19 08:16:06 -05:00
eeb33d7b9b Update the torrent 2023-12-18 18:31:58 -05:00
04a7589fcd Update translations 2023-12-18 17:49:27 -05:00
af9c347e0e Update title, summary, blog URL 2023-12-15 13:20:17 -05:00
ac6ce3baea Use release dates in blog post href 2023-12-15 11:53:00 -05:00
2f077991ea Fixup line breaks and leading whitespace for translations in previous news entry 2023-12-15 11:46:56 -05:00
1fd912a107 Fixup line breaks and leading whitespace for translations 2023-12-15 11:46:09 -05:00
5cc6534076 Remove Welcome, Cap, and Metrics from news 2023-12-15 11:26:55 -05:00
9e9ea397de Check in already updated translations 2023-12-15 11:05:26 -05:00
67ed6cfc9f Fix start of paragraph 3 2023-12-15 10:54:16 -05:00
0de1fd7543 Update entries.html for 2.4.0 2023-12-15 10:53:01 -05:00
zzz
8de71d84f6 blocklist update 2023-11-10 12:38:26 -05:00
zzz
1b68c27eae Migrate tx config to v3 2023-11-10 09:15:43 -05:00
e08a3bc185 Merge branch 'master' of i2pgit.org:i2p-hackers/i2p.newsxml 2023-07-11 17:45:41 -04:00
1829ed012e fix version numbers and blog post URLS 2023-07-11 17:27:23 -04:00
idk
71be75bc07 switch signing docker to oldstable, update version and magnet link 2023-06-30 12:46:23 -04:00
idk
09dff7c407 Merge branch 'master' of i2pgit.org:i2p-hackers/i2p.newsxml 2023-06-30 12:39:07 -04:00
idk
60f3fc117e update signing container 2023-06-30 12:38:44 -04:00
idk
bfc38cecec Merge branch 'i2p.i2p.2.3.0' into 'master'
add 2.3.0 news

See merge request i2p-hackers/i2p.newsxml!1
2023-06-30 15:14:46 +00:00
idk
2c27b2985f add 2.3.0 news 2023-06-28 17:14:28 -04:00
idk
cb4f65a58b update magnet link 2023-04-29 15:22:31 +00:00
idk
44ac34f89b update releases.json 2023-04-29 15:10:57 +00:00
idk
e57bcbe9b9 add new translation, add important dirs to gitignore 2023-04-28 19:49:55 +00:00
idk
70f643fcbf update torrent 2023-04-13 05:19:10 +00:00
idk
3caa12a7ff 2.2.1 news 2023-04-12 04:55:12 +00:00
idk
9c0b3b0604 update feed entries for Easy-Install Windows 2023-03-20 18:33:53 +00:00
idk
b2b785286c update torrent for windows 2023-03-20 18:26:32 +00:00
idk
355d700f3c fix HTTP fallback URL pattern 2023-03-13 23:23:36 +00:00
idk
7eba4d4b91 update the torrent for 2.2.0 2023-03-13 21:05:10 +00:00
idk
fa6af8e763 write the news for 2.2.0 2023-03-13 18:27:58 +00:00
idk
9dd303a061 Merge branch 'master' of i2pgit.org:i2p-hackers/i2p.newsxml 2023-02-14 23:18:22 +00:00
zzz
463ef16205 new news entry 2023-02-14 14:23:47 -05:00
idk
82af99a92f pull in translations and sign news 2023-02-11 16:33:49 +00:00
idk
00fb6242aa add newsfeed entry about ddos attack 2023-02-09 23:59:52 +00:00
idk
971ff00074 add newsfeed entry about ddos attack 2023-02-09 23:59:41 +00:00
idk
7d342cdb5c check in translations 2023-02-09 23:58:35 +00:00
zzz
11323544d9 blocklist update 2023-01-28 15:39:39 -05:00
zzz
33cc654b48 Add script to validate all entries.html files 2023-01-15 18:12:43 -05:00
zzz
c7c9f5d44b Fix HTML escaping issues in ast and zh translations 2023-01-15 17:29:11 -05:00
zzz
083c5350e9 blocklist update 2023-01-15 17:11:16 -05:00
idk
c2098757b3 fix date in link in newsfeed 2023-01-13 07:39:22 +00:00
idk
0a950e769d fix metadata extraction issue which was keeping windows newsfeed from building correctly 2023-01-13 07:37:02 +00:00
idk
6e921d2eaf fix omitted text in news entry 2023-01-13 04:33:12 +00:00
idk
dcb5683fb4 add news entries for 2.1.0, add news entries for both testing and beta, TODO get rid of one or both of those for the next release, ideally in favor of stable 2023-01-13 02:03:51 +00:00
idk
7c441697ce update the torrent 2023-01-13 00:55:59 +00:00
idk
0a25c6d01e check in translations 2023-01-13 00:55:31 +00:00
zzz
0bcf4004e2 2.1.0 metadata 2023-01-10 11:02:24 -05:00
zzz
ec6b155d11 OSX Bundle news 2023-01-06 07:05:25 -05:00
zzz
54e5800eb4 2.1.0 news 2023-01-05 11:59:13 -05:00
zzz
b0b0266cf3 update blocklist 2022-12-15 14:46:19 -05:00
idk
307ab473ad pull updated translations and check in Windows newsfeeds, git log --stat -p data/win 2022-11-26 09:15:36 -05:00
zzz
55eca8418b 2.0.0 metadata 2022-11-21 13:54:09 -05:00
zzz
7157fa5342 2.0.0 news entries 2022-11-18 10:23:22 -05:00
zzz
436a9d437f News entry with links to blog posts 2022-10-11 19:08:42 -04:00
idk
e0523f162a switch torrent link 2022-09-07 18:13:16 -04:00
idk
fafe1bfbcb switch torrent link 2022-09-07 18:12:40 -04:00
idk
1e1b15d9bc fix blog link 2022-09-07 18:10:51 -04:00
idk
d319ad0fa4 update Windows Easy-Install news 2022-09-07 18:07:24 -04:00
idk
4076f8c244 update easy-install bundle torrent 2022-08-29 09:55:26 -04:00
idk
464dbf90c7 update Windows easy-install news entry 2022-08-28 23:42:06 -04:00
idk
d53ae7217e update translations 2022-08-28 23:40:55 -04:00
00aea5404d mac bundles 1.9 metadata 2022-08-22 17:31:34 +01:00
zzz
9aab5e35b0 1.9.0 metadata 2022-08-22 12:15:03 -04:00
zzz
8da7b3a94c Fix atom links 2022-08-21 12:16:06 -04:00
zzz
358d84d1e6 1.9.0 news 2022-08-19 09:46:30 -04:00
zzz
5f97182865 outproxy news 2022-08-05 11:45:24 -04:00
ee64eec8d5 welcome news entry for arm64 macs 2022-08-03 20:06:57 +01:00
zzz
8f75cdb1e2 Ban router building huge number of tunnels 2022-07-13 15:18:45 -04:00
idk
0a7641d8f0 also remove leading zeroes from days when generating blog URL for feed 2022-07-05 18:55:13 -04:00
idk
ba83efc0aa remove leading zeroes from months when generating blog URL for feed 2022-07-05 18:53:10 -04:00
idk
30cf8619a8 fix URL in Windows news entry 2022-07-05 18:33:52 -04:00
592fec5cdb add mac-arm64 as a separate platform 2022-07-04 01:13:33 +01:00
idk
34cb65493d update windows easy-install release.json 2022-05-24 15:13:03 -04:00
idk
a998c4d5df update windows easy-install release.json 2022-05-24 15:13:03 -04:00
idk
2e56ccac02 check in new translations 2022-05-24 15:13:03 -04:00
e4f606403c mac 1.8.0 metadata 2022-05-24 13:14:13 +01:00
idk
6a29f0e065 add DEBIAN_FRONTEND noninteractive to Dockerfile.signing, change title in create_new_entry.sh example, and add a news entry for i2p.firefox beta 2022-05-23 14:33:44 -04:00
zzz
781486f1a6 1.8.0 metadata 2022-05-23 11:57:18 -04:00
zzz
7135cbb225 Add more changeme fields in create_news_entry.sh 2022-05-20 09:54:50 -04:00
zzz
23fd0a754c 1.8.0 release notes 2022-05-20 09:48:44 -04:00
idk
5e06fac77c Fix torrent 2022-05-08 23:33:17 -04:00
idk
81d083fb69 Do another Windows release 2022-05-08 22:54:50 -04:00
idk
026ff94863 Do another Windows release 2022-05-08 22:51:28 -04:00
idk
abe8e6d238 update Windows release, torrent 2022-05-05 19:20:26 -04:00
idk
87409b1188 Switch paragraphs and clarify response in Psychic Signatures entry in main news feed. Remove redundant text. 2022-04-25 12:09:03 -04:00
idk
58df45083a fix mispelling in news feed 2022-04-24 12:05:06 -04:00
idk
db5dce3f1b Add a Psychic Signatures announcement to the main feed 2022-04-22 11:49:32 -04:00
idk
afb0b2327f Add a Psychic Signatures announcement to the main feed 2022-04-22 11:38:21 -04:00
idk
126273fee4 update the torrent for the Windows bundle 2022-04-22 10:15:52 -04:00
idk
ab80e2a945 fix blog URL in my newsfeed 2022-04-21 13:18:27 -04:00
idk
1ba5f12b64 Add a news entry for 1.7.4 2022-04-21 11:44:38 -04:00
021eae6a04 news for Mac bundle 1.7.1 2022-04-20 14:53:57 +01:00
1d91d3181c update mac releases.json for 1.7.1 2022-04-20 14:20:46 +01:00
idk
680843bd85 allow passing additional OSS, BRANCHES to newsfeed 2022-03-21 12:34:47 -04:00
idk
5385475559 Update releases.json for windows beta build 2022-02-25 21:45:09 -05:00
idk
9ac80042f4 don't reverse sort order 2022-02-22 17:47:22 -05:00
09e47645c0 fix mac releases.json 2022-02-22 21:03:56 +00:00
zzz
7029e7945a Add note about validating the XHTML 2022-02-22 07:22:35 -05:00
141fae7628 Mac 1.7.0 2022-02-21 15:57:39 +00:00
zzz
737634f418 1.7.0 metadata 2022-02-21 10:35:35 -05:00
zzz
57f57b7861 1.7.0 news 2022-02-16 08:45:43 -05:00
idk
9095bee45c Make it possible to run multiple containers on different names/ports using docker. Gonna do some dev builds. 2022-02-04 16:48:22 -05:00
idk
4fd9b3b730 Docker script-based setup 2022-02-04 16:07:08 -05:00
idk
49c700f820 fix the escaped tracker URL's in my magnet link 2021-12-20 16:18:37 -05:00
idk
3bbc062a88 fix the torrent for the exe release 2021-12-09 21:43:47 -05:00
idk
c612be9af8 fix the torrent for the exe release 2021-12-09 21:32:49 -05:00
idk
ab07ea6c34 update some docs, update translations, windows release.json 2021-12-08 23:06:32 -05:00
621d244c33 Mac DMG 1.6.1 2021-12-06 07:21:50 +00:00
zzz
ba66e7f724 1.6.1 metadata 2021-11-29 12:54:12 -05:00
zzz
71bf2348f6 1.6.0 metadata 2021-11-29 11:53:38 -05:00
zzz
e6fe3a6e59 1.6.0 news 2021-11-25 10:17:01 -05:00
zzz
ebfba93ee2 Blocklist update 2021-11-21 05:46:15 -05:00
idk
10bd3d6851 make entries.html in win/beta the same as in mac/stable 2021-11-03 00:08:34 -04:00
b98c83d66e files for mac jpackage 1.5.1 2021-11-03 02:06:43 +00:00
idk
08701aa62c sort feed entries by date 2021-11-02 20:35:05 -04:00
idk
d102455321 Add support for platform-specific news entries.html files in data/I2P_OS/I2P_BRANCH/entries.html 2021-11-02 19:39:00 -04:00
idk
86fb5066a2 use mac instead of osx 2021-10-20 16:41:03 -04:00
idk
3f2e4c50be Make it so that the workflow doesn't have to change for newsfeed maintainers 2021-10-20 16:37:52 -04:00
idk
36db30f33d give each updater it's own section in ./build 2021-10-20 15:31:03 -04:00
idk
c840f1cb6a Merge branch 'master' of i2pgit.org:i2p-hackers/i2p.newsxml 2021-10-20 00:48:50 -04:00
idk
363a5ed5ec Add support for Easy-Install Bundle updates from torrents 2021-10-20 00:48:26 -04:00
zzz
2858c69dc0 Add download server URL
Add help about URLs to README
The backup news URLs will be supported in I2P 1.6.0
2021-09-05 10:22:49 -04:00
idk
7667abd7a8 update docker image for python3 2021-09-04 15:27:41 -04:00
idk
2f56ed3fe4 Fix remaining python2/python3 issue, decode('utf8') is no longer required for strings in python3 2021-09-04 14:23:26 -04:00
idk
e0d7635700 Make it ready to work with python3 with zlatinb's help 2021-09-04 14:12:26 -04:00
idk
3c2585cb47 Fix broken timestamp on second MuWire news entry 2021-08-23 18:26:56 -04:00
zzz
cffce539e0 1.5.0 metadata 2021-08-23 12:17:57 -04:00
zzz
6dcf326de8 1.5.0 news 2021-08-19 07:51:12 -04:00
zzz
8c43fe8a86 muwire news 2021-07-09 11:46:09 -04:00
zzz
23a2f78436 muwire news 2021-07-07 06:56:41 -04:00
zzz
8e9dec3e3d pull translations 2021-05-19 12:10:10 -04:00
zzz
98a93e2aaa 0.9.50 metadata 2021-05-18 10:37:39 -04:00
zzz
afb72174af fix 2021-05-13 16:37:46 -04:00
zzz
fcaab5b823 release news 2021-05-13 08:30:48 -04:00
idk
70f39aa2e7 Instructions for hosting newsfeeds with docker 2021-05-08 09:30:35 -04:00
65 changed files with 19264 additions and 997 deletions

1
.dockerignore Normal file
View File

@ -0,0 +1 @@
env

66
.github/workflows/sync.yaml vendored Normal file
View File

@ -0,0 +1,66 @@
# GitHub Actions workflow file to sync an external repository to this GitHub mirror.
# This file was automatically generated by go-github-sync.
#
# The workflow does the following:
# - Runs on a scheduled basis (and can also be triggered manually)
# - Clones the GitHub mirror repository
# - Fetches changes from the primary external repository
# - Applies those changes to the mirror repository
# - Pushes the updated content back to the GitHub mirror
#
# Authentication is handled by the GITHUB_TOKEN secret provided by GitHub Actions.
jobs:
sync:
runs-on: ubuntu-latest
steps:
- name: Validate Github Actions Environment
run: if [ "$GITHUB_ACTIONS" != "true" ]; then echo 'This script must be run in a GitHub Actions environment.'; exit 1; fi
- name: Checkout GitHub Mirror
uses: actions/checkout@v3
with:
fetch-depth: 0
- name: Configure Git
run: |-
git config user.name 'GitHub Actions'
git config user.email 'actions@github.com'
- env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
name: Sync Primary Repository
run: |-
# Add the primary repository as a remote
git remote add primary https://i2pgit.org/I2P_Developers/i2p.newsxml.git
# Fetch the latest changes from the primary repository
git fetch primary
# Check if the primary branch exists in the primary repository
if git ls-remote --heads primary master | grep -q master; then
echo "Primary branch master found in primary repository"
else
echo "Error: Primary branch master not found in primary repository"
exit 1
fi
# Check if we're already on the mirror branch
if git rev-parse --verify --quiet master; then
git checkout master
else
# Create the mirror branch if it doesn't exist
git checkout -b master
fi
# Force-apply all changes from primary, overriding any conflicts
echo "Performing force sync from primary/master to master"
git reset --hard primary/master
# Push changes back to the mirror repository
git push origin master
name: Sync Primary Repository to GitHub Mirror
"on":
push: {}
schedule:
- cron: 0 * * * *
workflow_dispatch: {}

8
.gitignore vendored
View File

@ -4,3 +4,11 @@
# Accidentally checking in a working transifexrc would be extremely bad!
.transifexrc
^logs
build
logs
etc/*custom*
build.old
/certificates
/blocklist.txt
news.su3
news.xml

448
.gitleaks.toml Executable file
View File

@ -0,0 +1,448 @@
title = "gitleaks config"
# Gitleaks rules are defined by regular expressions and entropy ranges.
# Some secrets have unique signatures which make detecting those secrets easy.
# Examples of those secrets would be Gitlab Personal Access Tokens, AWS keys, and Github Access Tokens.
# All these examples have defined prefixes like `glpat`, `AKIA`, `ghp_`, etc.
#
# Other secrets might just be a hash which means we need to write more complex rules to verify
# that what we are matching is a secret.
#
# Here is an example of a semi-generic secret
#
# discord_client_secret = "8dyfuiRyq=vVc3RRr_edRk-fK__JItpZ"
#
# We can write a regular expression to capture the variable name (identifier),
# the assignment symbol (like '=' or ':='), and finally the actual secret.
# The structure of a rule to match this example secret is below:
#
# Beginning string
# quotation
# │ End string quotation
# │ │
# ▼ ▼
# (?i)(discord[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9=_\-]{32})['\"]
#
# ▲ ▲ ▲
# │ │ │
# │ │ │
# identifier assignment symbol
# Secret
#
[[rules]]
id = "gitlab-pat"
description = "GitLab Personal Access Token"
regex = '''glpat-[0-9a-zA-Z\-]{20}'''
[[rules]]
id = "aws-access-token"
description = "AWS"
regex = '''AKIA[0-9A-Z]{16}'''
# Cryptographic keys
[[rules]]
id = "PKCS8-PK"
description = "PKCS8 private key"
regex = '''-----BEGIN PRIVATE KEY-----'''
[[rules]]
id = "RSA-PK"
description = "RSA private key"
regex = '''-----BEGIN RSA PRIVATE KEY-----'''
[[rules]]
id = "OPENSSH-PK"
description = "SSH private key"
regex = '''-----BEGIN OPENSSH PRIVATE KEY-----'''
[[rules]]
id = "PGP-PK"
description = "PGP private key"
regex = '''-----BEGIN PGP PRIVATE KEY BLOCK-----'''
[[rules]]
id = "github-pat"
description = "Github Personal Access Token"
regex = '''ghp_[0-9a-zA-Z]{36}'''
[[rules]]
id = "github-oauth"
description = "Github OAuth Access Token"
regex = '''gho_[0-9a-zA-Z]{36}'''
[[rules]]
id = "SSH-DSA-PK"
description = "SSH (DSA) private key"
regex = '''-----BEGIN DSA PRIVATE KEY-----'''
[[rules]]
id = "SSH-EC-PK"
description = "SSH (EC) private key"
regex = '''-----BEGIN EC PRIVATE KEY-----'''
[[rules]]
id = "github-app-token"
description = "Github App Token"
regex = '''(ghu|ghs)_[0-9a-zA-Z]{36}'''
[[rules]]
id = "github-refresh-token"
description = "Github Refresh Token"
regex = '''ghr_[0-9a-zA-Z]{76}'''
[[rules]]
id = "shopify-shared-secret"
description = "Shopify shared secret"
regex = '''shpss_[a-fA-F0-9]{32}'''
[[rules]]
id = "shopify-access-token"
description = "Shopify access token"
regex = '''shpat_[a-fA-F0-9]{32}'''
[[rules]]
id = "shopify-custom-access-token"
description = "Shopify custom app access token"
regex = '''shpca_[a-fA-F0-9]{32}'''
[[rules]]
id = "shopify-private-app-access-token"
description = "Shopify private app access token"
regex = '''shppa_[a-fA-F0-9]{32}'''
[[rules]]
id = "slack-access-token"
description = "Slack token"
regex = '''xox[baprs]-([0-9a-zA-Z]{10,48})?'''
[[rules]]
id = "stripe-access-token"
description = "Stripe"
regex = '''(?i)(sk|pk)_(test|live)_[0-9a-z]{10,32}'''
[[rules]]
id = "pypi-upload-token"
description = "PyPI upload token"
regex = '''pypi-AgEIcHlwaS5vcmc[A-Za-z0-9-_]{50,1000}'''
[[rules]]
id = "generic-api-key"
description = "Generic API Key"
regex = '''(?i)((key|api|token|secret|password)[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([0-9a-zA-Z\-_=]{8,64})['\"]'''
entropy = 3.7
entropyGroup = 4
# ➜ ~/code/gitleaks (v8) git show ec2fc9d6cb0954fb3b57201cf6133c48d8ca0d29 -- checks_test.go
[[rules]]
id = "gcp-service-account"
description = "Google (GCP) Service-account"
regex = '''\"type\": \"service_account\"'''
[[rules]]
id = "heroku-api-key"
description = "Heroku API Key"
regex = ''' (?i)(heroku[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([0-9A-F]{8}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{12})['\"]'''
[[rules]]
id = "slack-web-hook"
description = "Slack Webhook"
regex = '''https://hooks.slack.com/services/T[a-zA-Z0-9_]{8}/B[a-zA-Z0-9_]{8}/[a-zA-Z0-9_]{24}'''
[[rules]]
id = "twilio-api-key"
description = "Twilio API Key"
regex = '''SK[0-9a-fA-F]{32}'''
[[rules]]
id = "age-secret-key"
description = "Age secret key"
regex = '''AGE-SECRET-KEY-1[QPZRY9X8GF2TVDW0S3JN54KHCE6MUA7L]{58}'''
[[rules]]
id = "facebook-token"
description = "Facebook token"
regex = '''(?i)(facebook[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-f0-9]{32})['\"]'''
[[rules]]
id = "twitter-token"
description = "Twitter token"
regex = '''(?i)(twitter[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-f0-9]{35,44})['\"]'''
[[rules]]
id = "adobe-client-id"
description = "Adobe Client ID (Oauth Web)"
regex = '''(?i)(adobe[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-f0-9]{32})['\"]'''
[[rules]]
id = "adobe-client-secret"
description = "Adobe Client Secret"
regex = '''(p8e-)(?i)[a-z0-9]{32}'''
[[rules]]
id = "alibaba-access-key-id"
description = "Alibaba AccessKey ID"
regex = '''(LTAI)(?i)[a-z0-9]{20}'''
[[rules]]
id = "alibaba-secret-key"
description = "Alibaba Secret Key"
regex = '''(?i)(alibaba[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9]{30})['\"]'''
[[rules]]
id = "asana-client-id"
description = "Asana Client ID"
regex = '''(?i)(asana[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([0-9]{16})['\"]'''
[[rules]]
id = "asana-client-secret"
description = "Asana Client Secret"
regex = '''(?i)(asana[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9]{32})['\"]'''
[[rules]]
id = "atlassian-api-token"
description = "Atlassian API token"
regex = '''(?i)(atlassian[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9]{24})['\"]'''
[[rules]]
id = "bitbucket-client-id"
description = "Bitbucket client ID"
regex = '''(?i)(bitbucket[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9]{32})['\"]'''
[[rules]]
description = "Bitbucket client secret"
regex = '''(?i)(bitbucket[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9_\-]{64})['\"]'''
[[rules]]
description = "Beamer API token"
regex = '''(?i)(beamer[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"](b_[a-z0-9=_\-]{44})['\"]'''
[[rules]]
description = "Clojars API token"
regex = '''(CLOJARS_)(?i)[a-z0-9]{60}'''
[[rules]]
description = "Contentful delivery API token"
regex = '''(?i)(contentful[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9\-=_]{43})['\"]'''
[[rules]]
description = "Contentful preview API token"
regex = '''(?i)(contentful[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9\-=_]{43})['\"]'''
[[rules]]
description = "Databricks API token"
regex = '''dapi[a-h0-9]{32}'''
[[rules]]
description = "Discord API key"
regex = '''(?i)(discord[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-h0-9]{64})['\"]'''
[[rules]]
description = "Discord client ID"
regex = '''(?i)(discord[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([0-9]{18})['\"]'''
[[rules]]
description = "Discord client secret"
regex = '''(?i)(discord[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9=_\-]{32})['\"]'''
[[rules]]
description = "Doppler API token"
regex = '''['\"](dp\.pt\.)(?i)[a-z0-9]{43}['\"]'''
[[rules]]
description = "Dropbox API secret/key"
regex = '''(?i)(dropbox[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9]{15})['\"]'''
[[rules]]
description = "Dropbox short lived API token"
regex = '''(?i)(dropbox[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"](sl\.[a-z0-9\-=_]{135})['\"]'''
[[rules]]
description = "Dropbox long lived API token"
regex = '''(?i)(dropbox)(.{0,20})['\"](?i)[a-z0-9]{11}(AAAAAAAAAA)[a-z0-9-_=]{43}['\"]'''
[[rules]]
description = "Duffel API token"
regex = '''['\"]duffel_(test|live)_(?i)[a-z0-9_-]{43}['\"]'''
[[rules]]
description = "Dynatrace API token"
regex = '''['\"]dt0c01\.(?i)[a-z0-9]{24}\.[a-z0-9]{64}['\"]'''
[[rules]]
description = "EasyPost API token"
regex = '''['\"]EZAK(?i)[a-z0-9]{54}['\"]'''
[[rules]]
description = "EasyPost test API token"
regex = '''['\"]EZTK(?i)[a-z0-9]{54}['\"]'''
[[rules]]
description = "Fastly API token"
regex = '''(?i)(fastly[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9\-=_]{32})['\"]'''
[[rules]]
description = "Finicity client secret"
regex = '''(?i)(finicity[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9]{20})['\"]'''
[[rules]]
description = "Finicity API token"
regex = '''(?i)(finicity[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-f0-9]{32})['\"]'''
[[rules]]
description = "Flutterweave public key"
regex = '''FLWPUBK_TEST-(?i)[a-h0-9]{32}-X'''
[[rules]]
description = "Flutterweave secret key"
regex = '''FLWSECK_TEST-(?i)[a-h0-9]{32}-X'''
[[rules]]
description = "Flutterweave encrypted key"
regex = '''FLWSECK_TEST[a-h0-9]{12}'''
[[rules]]
description = "Frame.io API token"
regex = '''fio-u-(?i)[a-z0-9-_=]{64}'''
[[rules]]
description = "GoCardless API token"
regex = '''['\"]live_(?i)[a-z0-9-_=]{40}['\"]'''
[[rules]]
description = "Grafana API token"
regex = '''['\"]eyJrIjoi(?i)[a-z0-9-_=]{72,92}['\"]'''
[[rules]]
description = "Hashicorp Terraform user/org API token"
regex = '''['\"](?i)[a-z0-9]{14}\.atlasv1\.[a-z0-9-_=]{60,70}['\"]'''
[[rules]]
description = "Hubspot API token"
regex = '''(?i)(hubspot[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-h0-9]{8}-[a-h0-9]{4}-[a-h0-9]{4}-[a-h0-9]{4}-[a-h0-9]{12})['\"]'''
[[rules]]
description = "Intercom API token"
regex = '''(?i)(intercom[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9=_]{60})['\"]'''
[[rules]]
description = "Intercom client secret/ID"
regex = '''(?i)(intercom[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-h0-9]{8}-[a-h0-9]{4}-[a-h0-9]{4}-[a-h0-9]{4}-[a-h0-9]{12})['\"]'''
[[rules]]
description = "Ionic API token"
regex = '''ion_(?i)[a-z0-9]{42}'''
[[rules]]
description = "Linear API token"
regex = '''lin_api_(?i)[a-z0-9]{40}'''
[[rules]]
description = "Linear client secret/ID"
regex = '''(?i)(linear[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-f0-9]{32})['\"]'''
[[rules]]
description = "Lob API Key"
regex = '''(?i)(lob[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]((live|test)_[a-f0-9]{35})['\"]'''
[[rules]]
description = "Lob Publishable API Key"
regex = '''(?i)(lob[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]((test|live)_pub_[a-f0-9]{31})['\"]'''
[[rules]]
description = "Mailchimp API key"
regex = '''(?i)(mailchimp[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-f0-9]{32}-us20)['\"]'''
[[rules]]
description = "Mailgun private API token"
regex = '''(?i)(mailgun[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"](key-[a-f0-9]{32})['\"]'''
[[rules]]
description = "Mailgun public validation key"
regex = '''(?i)(mailgun[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"](pubkey-[a-f0-9]{32})['\"]'''
[[rules]]
description = "Mailgun webhook signing key"
regex = '''(?i)(mailgun[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-h0-9]{32}-[a-h0-9]{8}-[a-h0-9]{8})['\"]'''
[[rules]]
description = "Mapbox API token"
regex = '''(?i)(pk\.[a-z0-9]{60}\.[a-z0-9]{22})'''
[[rules]]
description = "MessageBird API token"
regex = '''(?i)(messagebird[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9]{25})['\"]'''
[[rules]]
description = "MessageBird API client ID"
regex = '''(?i)(messagebird[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-h0-9]{8}-[a-h0-9]{4}-[a-h0-9]{4}-[a-h0-9]{4}-[a-h0-9]{12})['\"]'''
[[rules]]
description = "New Relic user API Key"
regex = '''['\"](NRAK-[A-Z0-9]{27})['\"]'''
[[rules]]
description = "New Relic user API ID"
regex = '''(?i)(newrelic[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([A-Z0-9]{64})['\"]'''
[[rules]]
description = "New Relic ingest browser API token"
regex = '''['\"](NRJS-[a-f0-9]{19})['\"]'''
[[rules]]
description = "npm access token"
regex = '''['\"](npm_(?i)[a-z0-9]{36})['\"]'''
[[rules]]
description = "Planetscale password"
regex = '''pscale_pw_(?i)[a-z0-9\-_\.]{43}'''
[[rules]]
description = "Planetscale API token"
regex = '''pscale_tkn_(?i)[a-z0-9\-_\.]{43}'''
[[rules]]
description = "Postman API token"
regex = '''PMAK-(?i)[a-f0-9]{24}\-[a-f0-9]{34}'''
[[rules]]
description = "Pulumi API token"
regex = '''pul-[a-f0-9]{40}'''
[[rules]]
description = "Rubygem API token"
regex = '''rubygems_[a-f0-9]{48}'''
[[rules]]
description = "Sendgrid API token"
regex = '''SG\.(?i)[a-z0-9_\-\.]{66}'''
[[rules]]
description = "Sendinblue API token"
regex = '''xkeysib-[a-f0-9]{64}\-(?i)[a-z0-9]{16}'''
[[rules]]
description = "Shippo API token"
regex = '''shippo_(live|test)_[a-f0-9]{40}'''
[[rules]]
description = "Linkedin Client secret"
regex = '''(?i)(linkedin[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z]{16})['\"]'''
[[rules]]
description = "Linkedin Client ID"
regex = '''(?i)(linkedin[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9]{14})['\"]'''
[[rules]]
description = "Twitch API token"
regex = '''(?i)(twitch[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}['\"]([a-z0-9]{30})['\"]'''
[[rules]]
description = "Typeform API token"
regex = '''(?i)(typeform[a-z0-9_ .\-,]{0,25})(=|>|:=|\|\|:|<=|=>|:).{0,5}(tfp_[a-z0-9\-_\.=]{59})'''
[allowlist]
description = "global allow lists"
regexes = ['''219-09-9999''', '''078-05-1120''', '''(9[0-9]{2}|666)-\d{2}-\d{4}''']
files = ['''(.*?)(jpg|gif|doc|pdf|bin|svg|socket)$''']

View File

@ -2,7 +2,7 @@
host = https://www.transifex.com
lang_map = ru_RU: ru, sv_SE: sv, tr_TR: tr, uk_UA: uk, zh_CN: zh
[I2P.newsxml]
[o:otf:p:I2P:r:newsxml]
file_filter = data/translations/entries.<lang>.html
source_file = data/entries.html
source_lang = en

65
DOCKER.md Normal file
View File

@ -0,0 +1,65 @@
Signing News and Hosting a News Server with Docker
==================================================
i2p.newsxml has two containers, one for hosting the news itself, and one which
is used for running `news.sh` and `generate_news.py` in a container on Linux
distributions where Python2 support is limited or unavailable. It's also useful
if you simply prefer to manage Docker containers using Docker's or related
project's tooling(Portainer or sen for instance).
## To build the signing container, use:
``` sh
docker build --no-cache -t i2p.newsxml.signing -f Dockerfile.signing .
```
To run news.sh in the container, prepare your etc/su3.vars.custom.docker file as
if your signing keys directory were mounted at `/.i2p-plugin-keys`. No other
differences should be required between a Docker and non-docker `news.sh` run
``` sh
docker run -it \
-u $(id -u):$(id -g) \
--name i2p.newsxml.signing \
-v $HOME/.i2p-plugin-keys/:/.i2p-plugin-keys/:ro \
-v $HOME/i2p/:/i2p/:ro \
i2p.newsxml.signing
```
Then, extract the built feeds from the container:
``` sh
docker cp i2p.newsxml.signing:/opt/i2p.newsxml/build build
```
``` sh
docker build --no-cache -t i2p.newsxml.signing -f Dockerfile.signing .
docker rm -f i2p.newsxml.signing
docker run -it \
-u $(id -u):$(id -g) \
--name i2p.newsxml.signing \
-v $HOME/.i2p-plugin-keys/:/.i2p-plugin-keys/:ro \
-v $HOME/i2p/:/i2p/:ro \
i2p.newsxml.signing
docker cp i2p.newsxml.signing:/opt/i2p.newsxml/build build
```
## Now, you're ready to build the hosting container:
With the feeds in `build` from the previous step, run:
``` sh
docker build -t i2p.newsxml .
```
then, to serve the files on a local port:
``` sh
docker run -d --restart=always --name newsxml -p 127.0.0.1:3000:3000 i2p.newsxml
```
``` sh
docker build -t i2p.newsxml .
docker rm -f newsxml
docker run -d --restart=always --name newsxml -p 127.0.0.1:3000:3000 i2p.newsxml
```

29
Dockerfile.signing Normal file
View File

@ -0,0 +1,29 @@
FROM debian:oldstable
ENV PATH=/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ENV PYTHONPATH=/opt/newsxml
ENV LANG en_US.UTF-8
ENV LANGUAGE en_US:en
ENV LC_ALL en_US.UTF-8
ENV DEBIAN_FRONTEND noninteractive
RUN apt-get update
RUN apt-get install -y python \
python-dev \
virtualenv \
pip \
libxml2-dev \
libxslt1-dev \
default-jdk \
locales
RUN sed -i '/en_US.UTF-8/s/^# //g' /etc/locale.gen && \
locale-gen
COPY . /opt/i2p.newsxml
COPY etc/su3.vars.custom.docker /opt/i2p.newsxml/etc/su3.vars.custom
RUN mkdir -p /.local /.cache/pip/
RUN chown -R 1000:1000 /opt/i2p.newsxml /.local /.cache/pip/
RUN chmod -R o+rw /opt/i2p.newsxml /.local /.cache/pip/
WORKDIR /opt/i2p.newsxml
RUN ./setup_venv.sh && \
. env/bin/activate && \
pip install .
CMD . env/bin/activate && \
./news.sh

19
README
View File

@ -32,6 +32,13 @@ The highest-level heading that can be used is <h4>, but it looks bad in CSS, so
for now use <p><b>.
If it's an I2P release, edit data/releases.json as well.
Valid su3 map entries in releases.json are:
torrent: A single magnet link
url: A list of in-i2p http URLs, supported in I2P as of 1.6.0
clearnet: A list of non-i2p http URLs, not currently supported in I2P
clearnetssl: A list of non-i2p https URLs, not currently supported in I2P
NOTE: Only the following XHTML entities are allowed in news entries.
Strict XHTML is required. This is enforced in NewsXMLParser.
@ -44,7 +51,8 @@ Strict XHTML is required. This is enforced in NewsXMLParser.
Please use .i2p links instead of clearnet links in news entries if possible.
**Important:** Validate your XHTML with
$ xmllint data/entries.html > /dev/null || echo FAIL
**WARNING:** *NEVER* push translations from here (tx push -t)! The strings will
*NOT* match, and *ALL* translations will get out-of-sync!
@ -52,12 +60,12 @@ Please use .i2p links instead of clearnet links in news entries if possible.
To push the new entry into translations:
$ tx push -s
$ tx pull -a
$ tx pull --use-git-timestamps -a
To pull translations:
$ tx pull -a
$ tx pull --use-git-timestamps -a
To build the feeds:
@ -116,6 +124,11 @@ for routers to verify the signature. If you do not have privileges, ask somebody
does to generate it and check it in.
Generation requires I2P 0.9.27-12 or higher.
Before signing, create a symlink to the certificates directory in the
directory you are signing from, usually this will be the `i2p.newsxml` checkout.
ln -s $HOME/i2p/certificates
Input file is blocklist.txt. Format:
One IPv4 or IPv6 address or base 64 router hash per line.
No host names or netmasks (e.g. /24) are allowed.

View File

@ -1,8 +1,46 @@
#!/bin/sh
ENTRIES=data/entries.html
UUIDGEN="`which uuidgen || which uuid`"
sed -i "3i <article\n id=\"urn:uuid:`$UUIDGEN`\"\n title=\"\"\n href=\"\"\n author=\"\"\n published=\"\"\n updated=\"\">\n<details>\n<summary></summary>\n</details>\n<p>\n\n</p>\n</article>\n\n\n" $ENTRIES
# this script creates a new news entry
# it's a little smarter than it used to be to account for per-platform, per-branch updates
# You can still run it with just ./create_new_entry.sh but it will fill in some
# of the necessary fields for you and. You can also now pass it environment variables TITLE,
# HREF, and AUTHOR to set the title, href, and author of the entry.
#
# Example usage:
# TITLE="Title Here" AUTHOR=idk EDITOR=mousepad I2P_OS=win I2P_BRANCH=beta ./create_new_entry.sh
ENTRIES=data/$I2P_OS/$I2P_BRANCH/entries.html
UUIDGEN="`which uuidgen || which uuid`"
if [ -z "$DATE" ]; then
DATE=$(date +%Y-%m-%dT%H:00:00Z)
YEAR=$(date +%Y)
MONTH=$(date +%m)
DAY=$(date +%d)
else
DATE2=$(echo "$DATE" | sed 's/T.*//')
YEAR=$(echo "$DATE2" | cut -d - -f 1)
MONTH=$(echo "$DATE2" | cut -d - -f 2)
DAY=$(echo "$DATE2" | cut -d - -f 3)
fi
if [ -z "$HREF" ]; then
if [ ! -z "$CHANGEME_URL_HERE" ]; then
CHANGEME_URL_HERE=CHANGEME_URL_HERE
else
CHANGEME_URL_HERE=$(echo "$TITLE" | tr "[:upper:]" "[:lower:]" | sed 's| |_|g')
fi
HREF="http://i2p-projekt.i2p/en/blog/post/$YEAR/$MONTH/$DAY/$CHANGEME_URL_HERE"
fi
TITLE=${TITLE:-TITLE_HERE}
AUTHOR=${AUTHOR:-AUTHOR_HERE}
if [ -z "$SUMMARY_HERE" ]; then
SUMMARY_HERE="SUMMARY_HERE"
fi
if [ -z "$CONTENT_HERE" ]; then
CONTENT_HERE="<p>\n\n</p>"
fi
sed -i "3i <article\n id=\"urn:uuid:`$UUIDGEN`\"\n title=\"$TITLE\"\n href=\"$HREF\"\n author=\"$AUTHOR\"\n published=\"$DATE\"\n updated=\"$DATE\">\n<details>\n<summary>$SUMMARY_HERE</summary>\n</details>\n$CONTENT_HERE\n</article>\n\n\n" $ENTRIES
if [ ! -z "$EDITOR" ]; then
case "$EDITOR" in
@ -14,3 +52,4 @@ if [ ! -z "$EDITOR" ]; then
;;
esac
fi

View File

@ -1,175 +1,125 @@
<i2p:blocklist signer="zzz@mail.i2p" sig="6:FN0kFHzL7icjysU5zLbLovcc62uN9BjQW0NvZntMkxdrNLAyYmKT6radAfJQfxKzuwKyU6eSTprRNn0XHc1m~UV-6oM4bkWxxNHjWJRyaBomXeTdfw8b29aT5dsf5FIZhlLE48HkBryYl88rdgLz5r0ZAFOx5ofDJMeV1KT-YHiUxTUMBgSTc5K0CrHMnrthsijBsjlwD0mygscA9d50B1HkDx~nX24Hj0NKrXZ2DVD8x518eS9IPradfsx3zJURQT~eqqonF5nkSjqMAO4Sg8gETNoO-dRdQfdRQbhYupJR4LU~OuJSbG5HyjgPjrxA2TFDzE0PJLim5qduySvxzjj1I5tCnkoCiUMWyuMqZyUXuxqbn7xXQoQdWCtzklJPHKNz7OoUQwLrTA5wrtC8Des2Ij1~jhhZ5iMr0Quvhglzsk9Ta3sHHqqfvwECDt5xDO9mCdR88H7CkqbJjHvtf8pckgBPqeEBvrF5J65WSarF668YgM38oTQTP5M-svu6MRPEhbkW~27Hvb4XMVrbISP~ihZQijsw2oEIo~69pb3LaR9U4KXHsW6kvdCvkINCwpolJuJvS2Ezk3xBDx7r9GaYJtd11FC7zbD6KmrbmuyEplE15h3plwzp~H4NXTuXdcFFvPqIpVuX2s2Hnw38edzTVPfcq66avUor53hLHM0=">
<updated>2019-10-30T15:44:29Z</updated>
<i2p:block>45.32.62.37</i2p:block>
<i2p:block>45.32.125.149</i2p:block>
<i2p:block>45.32.152.247</i2p:block>
<i2p:block>45.63.50.207</i2p:block>
<i2p:block>45.63.76.128</i2p:block>
<i2p:block>45.76.47.3</i2p:block>
<i2p:block>45.76.98.64</i2p:block>
<i2p:block>45.76.112.208</i2p:block>
<i2p:block>45.76.152.150</i2p:block>
<i2p:block>45.77.29.172</i2p:block>
<i2p:block>45.77.132.75</i2p:block>
<i2p:block>47.88.159.58</i2p:block>
<i2p:block>47.88.169.149</i2p:block>
<i2p:block>47.90.120.30</i2p:block>
<i2p:block>47.208.97.112</i2p:block>
<i2p:block>104.156.254.54</i2p:block>
<i2p:block>104.207.153.96</i2p:block>
<i2p:block>108.61.251.143</i2p:block>
<i2p:block>133.130.124.185</i2p:block>
<i2p:block>150.95.134.159</i2p:block>
<i2p:block>150.95.144.95</i2p:block>
<i2p:block>150.95.147.89</i2p:block>
<i2p:block>150.95.153.220</i2p:block>
<i2p:block>160.36.130.86</i2p:block>
<i2p:block>160.36.130.87</i2p:block>
<i2p:block>160.36.130.88</i2p:block>
<i2p:block>160.36.130.89</i2p:block>
<i2p:block>160.36.130.90</i2p:block>
<i2p:block>160.36.130.91</i2p:block>
<i2p:block>160.36.130.92</i2p:block>
<i2p:block>160.36.130.93</i2p:block>
<i2p:block>160.36.130.94</i2p:block>
<i2p:block>160.36.130.95</i2p:block>
<i2p:block>160.36.130.96</i2p:block>
<i2p:block>160.36.130.97</i2p:block>
<i2p:block>160.36.130.98</i2p:block>
<i2p:block>160.36.130.99</i2p:block>
<i2p:block>160.36.130.100</i2p:block>
<i2p:block>160.36.130.101</i2p:block>
<i2p:block>160.36.130.102</i2p:block>
<i2p:block>160.36.130.103</i2p:block>
<i2p:block>160.36.130.104</i2p:block>
<i2p:block>160.36.130.105</i2p:block>
<i2p:block>160.36.130.106</i2p:block>
<i2p:block>160.36.130.107</i2p:block>
<i2p:block>160.36.130.108</i2p:block>
<i2p:block>160.36.130.109</i2p:block>
<i2p:block>160.36.130.110</i2p:block>
<i2p:block>160.36.130.111</i2p:block>
<i2p:block>160.36.130.112</i2p:block>
<i2p:block>160.36.130.113</i2p:block>
<i2p:block>160.36.130.114</i2p:block>
<i2p:block>160.36.130.115</i2p:block>
<i2p:block>160.36.130.116</i2p:block>
<i2p:block>160.36.130.117</i2p:block>
<i2p:block>160.36.130.118</i2p:block>
<i2p:block>160.36.130.119</i2p:block>
<i2p:block>160.36.130.120</i2p:block>
<i2p:block>160.36.130.121</i2p:block>
<i2p:block>160.36.130.122</i2p:block>
<i2p:block>160.36.130.123</i2p:block>
<i2p:block>160.36.130.124</i2p:block>
<i2p:block>160.36.130.125</i2p:block>
<i2p:block>160.36.130.126</i2p:block>
<i2p:block>160.36.130.127</i2p:block>
<i2p:block>160.36.130.128</i2p:block>
<i2p:block>160.36.130.129</i2p:block>
<i2p:block>160.36.130.130</i2p:block>
<i2p:block>160.36.130.131</i2p:block>
<i2p:block>160.36.130.132</i2p:block>
<i2p:block>160.36.130.133</i2p:block>
<i2p:block>160.36.130.134</i2p:block>
<i2p:block>160.36.130.135</i2p:block>
<i2p:block>160.36.130.136</i2p:block>
<i2p:block>160.36.130.137</i2p:block>
<i2p:block>160.36.130.138</i2p:block>
<i2p:block>160.36.130.139</i2p:block>
<i2p:block>160.36.130.140</i2p:block>
<i2p:block>160.36.130.141</i2p:block>
<i2p:block>160.36.130.142</i2p:block>
<i2p:block>160.36.130.143</i2p:block>
<i2p:block>160.36.130.144</i2p:block>
<i2p:block>160.36.130.145</i2p:block>
<i2p:block>160.36.130.146</i2p:block>
<i2p:block>160.36.130.147</i2p:block>
<i2p:block>160.36.130.148</i2p:block>
<i2p:block>160.36.130.149</i2p:block>
<i2p:block>160.36.130.150</i2p:block>
<i2p:block>160.36.130.151</i2p:block>
<i2p:block>160.36.130.152</i2p:block>
<i2p:block>160.36.130.153</i2p:block>
<i2p:block>160.36.130.154</i2p:block>
<i2p:block>160.36.130.155</i2p:block>
<i2p:block>160.36.130.156</i2p:block>
<i2p:block>160.36.130.157</i2p:block>
<i2p:block>160.36.130.158</i2p:block>
<i2p:block>160.36.130.159</i2p:block>
<i2p:block>160.36.130.160</i2p:block>
<i2p:block>160.36.130.161</i2p:block>
<i2p:block>160.36.130.162</i2p:block>
<i2p:block>160.36.130.163</i2p:block>
<i2p:block>160.36.130.164</i2p:block>
<i2p:block>160.36.130.165</i2p:block>
<i2p:block>160.36.130.166</i2p:block>
<i2p:block>160.36.130.167</i2p:block>
<i2p:block>160.36.130.168</i2p:block>
<i2p:block>160.36.130.169</i2p:block>
<i2p:block>160.36.130.170</i2p:block>
<i2p:block>160.36.130.171</i2p:block>
<i2p:block>160.36.130.172</i2p:block>
<i2p:block>160.36.130.173</i2p:block>
<i2p:block>160.36.130.174</i2p:block>
<i2p:block>160.36.130.175</i2p:block>
<i2p:block>160.36.130.176</i2p:block>
<i2p:block>160.36.130.177</i2p:block>
<i2p:block>160.36.130.178</i2p:block>
<i2p:block>160.36.130.179</i2p:block>
<i2p:block>160.36.130.180</i2p:block>
<i2p:block>160.36.130.181</i2p:block>
<i2p:block>160.36.130.182</i2p:block>
<i2p:block>160.36.130.183</i2p:block>
<i2p:block>160.36.130.184</i2p:block>
<i2p:block>160.36.130.185</i2p:block>
<i2p:block>160.36.130.186</i2p:block>
<i2p:block>160.36.130.187</i2p:block>
<i2p:block>160.36.130.188</i2p:block>
<i2p:block>160.36.130.189</i2p:block>
<i2p:block>160.36.130.190</i2p:block>
<i2p:block>160.36.130.191</i2p:block>
<i2p:block>160.36.130.192</i2p:block>
<i2p:block>160.36.130.193</i2p:block>
<i2p:block>160.36.130.194</i2p:block>
<i2p:block>160.36.130.195</i2p:block>
<i2p:block>160.36.130.196</i2p:block>
<i2p:block>160.36.130.197</i2p:block>
<i2p:block>160.36.130.198</i2p:block>
<i2p:block>160.36.130.199</i2p:block>
<i2p:block>160.36.130.200</i2p:block>
<i2p:block>160.36.130.201</i2p:block>
<i2p:block>160.36.130.202</i2p:block>
<i2p:block>160.36.130.203</i2p:block>
<i2p:block>160.36.130.204</i2p:block>
<i2p:block>160.36.130.205</i2p:block>
<i2p:block>160.36.130.206</i2p:block>
<i2p:block>160.36.130.207</i2p:block>
<i2p:block>160.36.130.208</i2p:block>
<i2p:block>160.36.130.209</i2p:block>
<i2p:block>160.36.130.210</i2p:block>
<i2p:block>160.36.130.211</i2p:block>
<i2p:block>160.36.130.212</i2p:block>
<i2p:block>160.36.130.213</i2p:block>
<i2p:block>160.36.130.214</i2p:block>
<i2p:block>160.36.130.215</i2p:block>
<i2p:block>160.36.130.216</i2p:block>
<i2p:block>160.36.130.217</i2p:block>
<i2p:block>160.36.130.218</i2p:block>
<i2p:block>160.36.130.219</i2p:block>
<i2p:block>160.36.130.220</i2p:block>
<i2p:block>160.36.130.221</i2p:block>
<i2p:block>160.36.130.222</i2p:block>
<i2p:block>163.44.149.31</i2p:block>
<i2p:block>2001:df6:b800:1128:a163:44:149:310</i2p:block>
<i2p:block>2001:19f0:4400:4376:5400:ff:fe47:bcbd</i2p:block>
<i2p:block>2001:19f0:5801:1d4:5400:ff:fe38:a26e</i2p:block>
<i2p:block>2001:19f0:5c01:1df:5400:ff:fe3e:ba8f</i2p:block>
<i2p:block>2001:19f0:7001:cb:5400:ff:fe47:c952</i2p:block>
<i2p:block>2400:8500:1302:816:a150:95:128:1656</i2p:block>
<i2p:block>2400:8500:1302:802:a133:130:124:1855</i2p:block>
<i2p:block>2400:8500:1302:819:a150:95:134:1590</i2p:block>
<i2p:block>2400:8500:1302:824:a150:95:144:951</i2p:block>
<i2p:block>2400:8500:1302:825:150:95:147:89</i2p:block>
<i2p:block>2400:8500:1302:828:a150:95:153:2202</i2p:block>
<i2p:blocklist signer="zzz@mail.i2p" sig="6:NUAbQZOcQOlRUAnLxjFsrxNfia6ckgqJ-164bLe7lVI8GfaKT61CjXb22DEFnDXri8buGVAOTs0PN-R-J2i4fRUp5qoW2JfZkRafWc~YAuwyMjoytx6aTKOkjJA-OZYFiLHA0sbodDagUajOsBVpwdF97GtNH2f9FyRy9f9j68jV-cGqPh4VEXbk50jFfL4v~ABhuj2xUbNmdJseKP2bQkC21kd0qMqeNfd0Wxpy9Ij-IODHV0tzd-JqgMntXBshMPWE5ywOfuCIpqMCvjvHIYlKKxOmi0e1Khx5wsJ0BnP-JdXB9xbLh0PUeFpZCDuxweOYPb~kihON85xLttRmcSXQ6wGfXechWzqx8bcWqhs501pUBvakEwPFgkkHG-tMHBfJPfLY~xCHGXOOOT0xNtEDuGyDbc-dA1D38a5O6ImKUW4xZUvv~NbQFG8zKfEIVJ5PHg1Ch2sqNB0NMNOP8DxZw311D-vR~yZndk11W~j8S7WLN7tor4t4FTGnPO1gdoMSW-NXR8wlnrkbEFrt6m-HVKZsf18mL~9T~dqaihWBuWi8mcX9ZfseuXdou-ip~FK4ktXVUNBKOADUseykp2GTgQYhZK~QCjppEILmVcf1LyIULqIFvOUhC6JZUX62xsM8jpCuBw3t2o7CjxzZYqRH55zeDDVrfGMAMR~IjKw=">
<updated>2025-05-11T22:04:43Z</updated>
<i2p:block>93.157.12.248</i2p:block>
<i2p:block>185.213.155.252</i2p:block>
<i2p:block>223.167.199.60</i2p:block>
<i2p:block>2a03:1b20:6:f011:0:0:0:a02e</i2p:block>
<i2p:block>JbifzqZZqeTXtxK6KDqNUPWaW-phKqeS~tfJT82SIYI=</i2p:block>
<i2p:block>QPUV1bW6arN2zp3gTBMvOEvgSuKbXUqk2oqHkb~UoSw=</i2p:block>
<i2p:block>CyLg6w8lypk1gnAX-CdG8O4NCR86hq8ifge6QKXAoJg=</i2p:block>
<i2p:block>DtQsGzkbeR3nilr6ZvywR2O7-f0XaaV~YfHXohqwjgI=</i2p:block>
<i2p:block>lam824jtkYq4qTiZHT~TkdHoVTVRwnLghgFheZbgDhU=</i2p:block>
<i2p:block>Qqj3p9F0Y~qXAkSz3FYo~e~OfSgaM5qZ2OYUrzOtrgM=</i2p:block>
<i2p:block>NUo2wncm49XY8f~dzdxII5fnVopL9oT92KC9JC3IOFY=</i2p:block>
<i2p:block>GEpq15rG0XjIvP7oZCW9cmL8Dhb8eLSweTU3hZuT2fE=</i2p:block>
<i2p:block>aNBK4IQwYCejjMnD31hapWQvova~u1OINPnHCqceljw=</i2p:block>
<i2p:block>6lWUeurYBX4w6lsfPdkAxbFKXoGEXKxofXwlWOC3RQA=</i2p:block>
<i2p:block>xKAdoKJUvrSEGS0gREC4lEUawa4IKsVnQU189X~QQhk=</i2p:block>
<i2p:block>2EJgHsXnjQo8gHt-jmS-GlhXjqtHnNgWiK~QyQ0Rsh4=</i2p:block>
<i2p:block>o-atVIIK0N2Eu6r2Nq42cAVqlK6wJGrXqU0Ps3x0HmY=</i2p:block>
<i2p:block>2C-fFbGjOJks1mDYxlQ~~M3Q-tX9Dx~tyAUHPzfct~E=</i2p:block>
<i2p:block>Qc5rvLavMYNhzQBQfBgFkZbesEvGW~3nz1ZwllR1MoM=</i2p:block>
<i2p:block>0bLUiXtgYCzAy3533C~wjaUxUkH63JGSRlx2huH-6Bo=</i2p:block>
<i2p:block>3~ZOYyQFJAJXxuynetnoijOFjliGGmN9kZ5BkiSupy0=</i2p:block>
<i2p:block>4V3EsOGTWrIXJDNaGpOLZrnSGWgSxwgZ7Tsxb0txFtE=</i2p:block>
<i2p:block>4yr5497JpDG-K7s1unMbvWBPPfds72Qw27DNH9FpcKQ=</i2p:block>
<i2p:block>5MAAvwKgnG7hYbi93q0Luro~-AyIjO5xvUbABc2T3IU=</i2p:block>
<i2p:block>5SI8wX-KUefASp0KbjuQ2KaCyZboFHcsXsgwaONVqzc=</i2p:block>
<i2p:block>6lKXyJfzTrrt2B7R-p24FSMQQHmyPBb1JSp1N49wdrM=</i2p:block>
<i2p:block>6yUKWdxJKF0wtxd3Ro0VfkSlLe74gvM2b0IJbzm~mT0=</i2p:block>
<i2p:block>7NzcMy-ty6WICyPHbYBuGQlbcMs7dV-5lN2HIZ-PvuY=</i2p:block>
<i2p:block>9ELLjPmb9PBMTOeXqMsRmRfLRlctQMELTZFrkDBOiVA=</i2p:block>
<i2p:block>AQ2Wq8Guob3CI1jve~W5wErlaaSF-iZz9mhzKsFmWeo=</i2p:block>
<i2p:block>BhqgIK5aTiL8UosUjmBMsCl5NtNCFCZTu0wUSFt0Mkg=</i2p:block>
<i2p:block>cC8PmCV4AehT0hKPAfp3yP1DYJKFxmWBk8JWSVZT8Oo=</i2p:block>
<i2p:block>cfhT8b5PNxSIFhmg-6ZvP78W5eD9jtGBLjM~oIRRqoE=</i2p:block>
<i2p:block>fGe1bjAyj-V0kRJmbXbCGp9y0ZVkYDZksdvfBwo2nME=</i2p:block>
<i2p:block>G7d8g3yIjMTG1M6ui1zWf-YYYe0K3Pz8dCg~gRHM-KI=</i2p:block>
<i2p:block>Giy8ehFNw~RyB5KV5BCMzgMUMxVI2hiWFS3gdWPthCA=</i2p:block>
<i2p:block>HPDYhgrDNJK0STyIJM-A3Q~aMU9D63P-7Bw-Qs15Bmk=</i2p:block>
<i2p:block>I5rpywP3dJsP1bfKzp-QUsRCNgT2sO7sTqxuH8~AjmQ=</i2p:block>
<i2p:block>ioBAP6QWbWpzkUbmpKn2eWe~XlNmFuIsTJxvstMt2hU=</i2p:block>
<i2p:block>jizbTEmYpthOrW2louGRyR057W9G4vcOKtvk~lPqvYg=</i2p:block>
<i2p:block>JtgxUY6P7VcgJV3HQUzAaUSVInTR20PT8E34xvwkEck=</i2p:block>
<i2p:block>kISWAKZmX0n9C~vQ19oTdL9iWdLs1BfDrssNiZunubw=</i2p:block>
<i2p:block>krZK4oqwsee2Qsevb9b9n5jGuNrVaTJlt-nE8G8ft5w=</i2p:block>
<i2p:block>lj1A58-iv9W4V9r-jrHZISKncWlSYaQCYvQcBvZppEg=</i2p:block>
<i2p:block>N9GkaK294wlSRKaUicSimnxDwebUWKggFlrBUpe00KA=</i2p:block>
<i2p:block>Oy4ZaiVxxel1XAWW1p23JlekMGEFvWbWuizQMRnG~tc=</i2p:block>
<i2p:block>q1rjeEo0hB61qIcER59aEdQWsX8-gpW-K862deAJkp0=</i2p:block>
<i2p:block>QYkhWCudqWhty-TvJ-sFd0z5uLYBXHW5t61L-I6ltJU=</i2p:block>
<i2p:block>RDX~26d6ugO1C-DEhkEzPQaGHurvfgKL0cXZlqr4C6Y=</i2p:block>
<i2p:block>RjBVJtLfMhLgaSNDpv-D4UqybO5GWSgtcJqAqqd6L~Q=</i2p:block>
<i2p:block>S7-xKQ1wSqiqmjODZrTWprTD1L0dtiZlwT055DArGFw=</i2p:block>
<i2p:block>SdXmd046uxhAvscEM7ogR6HtH2eWBiyo4~XOnj3dr7c=</i2p:block>
<i2p:block>Sm6IkscEdA0vBy9Cx~VQcgB2f5e0fvQ2CEu8fkceL1s=</i2p:block>
<i2p:block>tFv6N4kwPdOlMXo8VqoOO3UrSsWAg~-5nadozzBm2Tc=</i2p:block>
<i2p:block>TJwtpwSS7yANCDPDfbGdx3f4lDQNYcfA-0X75jHbbNU=</i2p:block>
<i2p:block>w~1a6nvIBJfFHGur0mPJmjlwjSBOrWGTC-INPEesPJ0=</i2p:block>
<i2p:block>wMIJ9Ax~4kW-jkFQLTHfzSSBqaMSy3EKiBH8YUQjAVA=</i2p:block>
<i2p:block>wPorvAjMYj6FipnUHruA0dF2K-Xm~GngCY3QDIVlZyU=</i2p:block>
<i2p:block>wWP~J-g-e8Fok7NpTURpJJfeNTGB5S7F15QshyRn9n0=</i2p:block>
<i2p:block>X52PGfb8TysUDO7pvQIKGeoPcmWx4jwQJjoHLDD7A5Y=</i2p:block>
<i2p:block>xirj-SFuNcYapYv7vnkfa2peqqCzuWeKeUB937Odl3s=</i2p:block>
<i2p:block>xXvAxpq~FFyNx9bm6XlPVXNQ7vYfGkjC7nj0xWvNjwE=</i2p:block>
<i2p:block>YbIKZpPSqdohVjzi8s~N-D0t~bbayKM4hHcBk-fcJvY=</i2p:block>
<i2p:block>ynL10zIHBslFPSf1cmAONogYvNm1WrZ9bgE0txHzOr4=</i2p:block>
<i2p:block>YSfLfZVPUvvyQtAltBSJ2RHcU~uTiV0x0H4y~QIPczc=</i2p:block>
<i2p:block>ZTOVAP9GJYEKu8CjCQBmOigw79oyTVpQQguTDqwv2EU=</i2p:block>
<i2p:block>-xH2G0zblY4mRQxeb1WtXAJwyy8hlsrqpY3~fgPBnoU=</i2p:block>
<i2p:block>~CrJVoN00MNvEjZIWudnWFzjqDPDsZxKuFq1Y~Sh8fo=</i2p:block>
<i2p:block>8ej3XrMgI2IMIwP4X6~h9Nw4vtDV~2yX1nI7u-nOidg=</i2p:block>
<i2p:block>o0N6orDrgfMY29G4Z8Q7CRwhSnvw4LuuKhvadrtDsSE=</i2p:block>
<i2p:block>tATb9Xe-Tj5QqTm1u1zY1CZlqK0X6Ygn6LjnQBjb55w=</i2p:block>
<i2p:block>xnMzPiEhGe2mFuoN8PiB5voV-H2JLk4g5a054mVmFds=</i2p:block>
<i2p:block>yb2KWHXrtLdSGG4G53GXjVRilYXFDj7KzsHMLYCNK3o=</i2p:block>
<i2p:block>yQN8Qt0K0yi89DrMaMa0LhHpQkxj2X3zS0SATe5QAXI=</i2p:block>
<i2p:block>F~UzS1mTN3XYlnOfidMBv5Z4lHI7dsCZ8N5mxpyc-OU=</i2p:block>
<i2p:block>6NMfknVMawT~baK0VanEkbXvO2hJCLJ5rreieysRrNE=</i2p:block>
<i2p:block>MogB-V71uOsLBu5z9gW5sa3zzUfI5GD43selaYiOy4U=</i2p:block>
<i2p:block>~SN8k6Hid107ighTnxRSiwTwwPMjEpPbDEyEY--zD~U=</i2p:block>
<i2p:block>ixpaFrLz3C-Fo~6~TOKtQIsHRvmdC~hOFtmJenNz3-Y=</i2p:block>
<i2p:block>2l9Eg2BKOmu8hixe~UyElpu~~2RXkhBOM5j8rSqjsKs=</i2p:block>
<i2p:block>i1Viub4WK3l-6KbZHifQCY9aGwhU8JG3u5gg5fVJWlM=</i2p:block>
<i2p:block>nA-DRzbe33yVHcvITENBWKJ~yVVie6hngoQbB~MoYH0=</i2p:block>
<i2p:block>jDFMFtR3wmtuixX0LajCoW1Ko-fSU8sWTtkuqKM9ti8=</i2p:block>
<i2p:block>nRTKhTmfXEmpLGe7QmpEPOZr6C3SpX0ke~sgqcX8axA=</i2p:block>
<i2p:block>3lgHIOIADdUIoyJjWymzE1Xikx7RojrEBfYT6P7eLzk=</i2p:block>
<i2p:block>jhyiaB9Nd2RRVInrmSi0rquBwJaLhhiPemlqj7HGo7k=</i2p:block>
<i2p:block>1jhJoqpi5oFB6yvObMwAiiTi7DT8~WTIAd1zh1XSNEM=</i2p:block>
<i2p:block>y8q2xWGfKdUzGVkapSZ~wJbqGWJ1vTaPUz0oChBp99M=</i2p:block>
<i2p:block>3.225.127.222</i2p:block>
<i2p:block>3.234.89.179</i2p:block>
<i2p:block>5.250.198.133</i2p:block>
<i2p:block>18.210.78.199</i2p:block>
<i2p:block>31.155.206.27</i2p:block>
<i2p:block>38.242.206.110</i2p:block>
<i2p:block>44.210.192.47</i2p:block>
<i2p:block>46.53.244.68</i2p:block>
<i2p:block>52.60.61.249</i2p:block>
<i2p:block>52.70.234.81</i2p:block>
<i2p:block>59.56.69.164</i2p:block>
<i2p:block>77.165.6.8</i2p:block>
<i2p:block>91.138.224.31</i2p:block>
<i2p:block>93.235.73.128</i2p:block>
<i2p:block>98.15.244.49</i2p:block>
<i2p:block>109.197.204.101</i2p:block>
<i2p:block>109.197.205.47</i2p:block>
<i2p:block>110.137.220.12</i2p:block>
<i2p:block>139.59.133.151</i2p:block>
<i2p:block>145.239.83.230</i2p:block>
<i2p:block>162.55.230.167</i2p:block>
<i2p:block>162.218.65.219</i2p:block>
<i2p:block>172.6.174.68</i2p:block>
<i2p:block>174.27.149.30</i2p:block>
<i2p:block>176.88.62.2</i2p:block>
<i2p:block>185.209.196.140</i2p:block>
<i2p:block>185.209.196.150</i2p:block>
<i2p:block>185.209.196.180</i2p:block>
<i2p:block>185.65.134.232</i2p:block>
<i2p:block>185.65.134.233</i2p:block>
<i2p:block>185.65.134.253</i2p:block>
<i2p:block>186.166.142.51</i2p:block>
<i2p:block>193.32.249.139</i2p:block>
<i2p:block>2a03:1b20:6:f011:0:0:0:a07e</i2p:block>
</i2p:blocklist>

View File

@ -1,5 +1,908 @@
<div>
<header title="I2P News">News feed, and router updates</header>
<article
id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a"
title="2.9.0 Released"
href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released"
author="idk"
published="2025-06-02T19:00:00Z"
updated="2025-06-02T19:00:00Z">
<details>
<summary>I2P 2.9.0 Release</summary>
</details>
<p>
I2P 2.9.0 is a maintenance release that includes bug fixes and work on new features.
</p>
<p>
Thread usage has been improved to improve the performance of the i2ptunnel system.
NTCP2 has been improved to resist probing attacks.
The notification system has been integrated into more applications to provide better feedback to users from I2PSnark and the other applications.
Automatic floodfill enrollment has been fixed.
Users may observe increased resource usage when acting as floodfill.
If this is not desired, floodfill mode can be disabled on the /config page.
</p>
<p>
A new global map feature is available in the console which shows the locations of routers in your view of the netDb.
These are the peers that help your router build tunnels and provide services anonymously.
</p>
<p>
Work continues on implementing automatic bandwidth management for tunnels, the Datagram2 protocol, and Post-Quantum cryptography.
In two releases, at 2.11.0, I2P will require Java 17.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe"
title="2.8.2 Released"
href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release"
author="zzz"
published="2025-03-29T12:00:00Z"
updated="2025-03-29T12:00:00Z">
<details>
<summary>I2P 2.8.2 Release</summary>
</details>
<p>
2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce"
title="2.8.1 Released"
href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release"
author="zzz"
published="2025-03-17T14:00:00Z"
updated="2025-03-17T14:00:00Z">
<details>
<summary>I2P 2.8.1 Release</summary>
</details>
<p>
2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.
</p>
<p>
We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e"
title="Local site access fails in 2.8.0"
href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release"
author="zzz"
published="2025-02-08T16:00:00Z"
updated="2025-02-08T16:00:00Z">
<details>
<summary>2.8.0 Local Access Bug</summary>
</details>
<p>
In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.
</p>
</article>
<article
id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994"
title="I2P 2.8.0 Release"
href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release"
author="idk"
published="2025-02-03T13:00:00Z"
updated="2025-02-03T13:00:00Z">
<details>
<summary>I2P 2.8.0 Release</summary>
</details>
<p>
This release improves I2P by fixing bugs, removing unused code, and improving network stability.
</p>
<p>
We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0"
title="I2P 2.7.0 Release"
href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release"
author="idk"
published="2024-10-08T10:00:00Z"
updated="2024-10-08T10:00:00Z">
<details>
<summary>I2P 2.7.0 Release</summary>
</details>
<p>
This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.
</p>
<p>
Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.
</p>
<p>
Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632"
title="I2P 2.6.1 Released"
href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released"
author="idk"
published="2024-08-06T13:00:00Z"
updated="2024-08-06T13:00:00Z">
<details>
<summary>I2P 2.6.1 Release</summary>
</details>
<p>
I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e"
title="I2P 2.6.0 Released"
href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released"
author="idk"
published="2024-07-19T22:00:00Z"
updated="2024-07-19T22:00:00Z">
<details>
<summary>I2P 2.6.0 Release</summary>
</details>
<p>
This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.
</p>
<p>
Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.
</p>
<p>
I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf"
title="2.5.2 Released"
href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release"
author="zzz"
published="2024-05-15T12:00:00Z"
updated="2024-05-15T12:00:00Z">
<details>
<summary>2.5.2 with HTTP fix</summary>
</details>
<p>
I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a"
title="I2P 2.5.1 Released"
href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released"
author="idk"
published="2024-05-06T10:00:00Z"
updated="2024-05-06T10:00:00Z">
<details>
<summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary>
</details>
<p>
I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d"
title="Stormy Weather"
href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather"
author="idk"
published="2024-04-25T22:00:00Z"
updated="2024-04-25T22:00:00Z">
<details>
<summary>Network Weather: Stormy. I2P is under attack.</summary>
</details>
<p>
The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.
</p>
<p>
If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.
</p>
</article>
<article
id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3"
title="New Release I2P 2.5.0"
href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0"
author="idk"
published="2024-04-08T10:00:00Z"
updated="2024-04-08T10:00:00Z">
<details>
<summary>More Application Improvements, Audit of NetDB Isolation strategy</summary>
</details>
<p>
This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.
</p>
<p>
New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>
During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.
</p>
<p>
During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7"
title="I2P 2.4.0 Release with Congestion and NetDB Security improvements"
href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0"
author="idk"
published="2023-12-18T20:00:00Z"
updated="2023-12-18T20:00:00Z">
<details>
<summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary>
</details>
<p>
This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.
</p>
<p>
The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.
</p>
<p>
The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.
</p>
<p>
Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:"
title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API"
href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0"
author="idk"
published="2023-06-25T12:00:00Z"
updated="2023-06-25T12:00:00Z">
<details>
<summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary>
</details>
<p>
This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.
</p>
<p>
In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.
</p>
<p>
This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.
</p>
<p>
This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.
</p>
<p>
This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5"
title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid"
href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1"
author="idk"
published="2023-04-12T03:00:00Z"
updated="2023-04-12T03:00:00Z">
<details>
<summary>I2P 2.2.1 - maintenance release for 2.2.0</summary>
</details>
<p>
After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.
</p>
<p>
This release syncs translations with transifex and updates the GeoIP database.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362"
title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem"
href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0"
author="idk"
published="2023-03-13T17:00:00Z"
updated="2023-03-13T17:00:00Z">
<details>
<summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary>
</details>
<p>
We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.
</p>
<p>
This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.
</p>
<p>
As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7"
title="DDoS Update"
href="http://zzz.i2p/topics/3593"
author="zzz"
published="2023-02-14T19:00:00Z"
updated="2023-02-14T19:00:00Z">
<details>
<summary>DDoS Update</summary>
</details>
<p>
We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.
</p><p>
This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.
</p><p>
We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.
</p>
</article>
<article
id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d"
title="About the recent Denial of Service attacks"
href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks"
author="sadie,idk"
published="2023-02-09T23:00:00Z"
updated="2023-02-09T23:00:00Z">
<details>
<summary>I2P remains intact with impaired performance</summary>
</details>
<p>
The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.
</p>
<p>
While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.
</p>
</article>
<article
id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007"
title="2.1.0 Released"
href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release"
author="zzz"
published="2023-01-09T12:00:00Z"
updated="2023-01-09T12:00:00Z">
<details>
<summary>2.1.0 with numerous SSU2 fixes</summary>
</details>
<p>
We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.
</p><p>
Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.
</p><p>
Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.
</p><p>
As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2"
title="2.0.0 Released"
href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release"
author="zzz"
published="2022-11-21T12:00:00Z"
updated="2022-11-21T12:00:00Z">
<details>
<summary>SSU2 Transport Enabled</summary>
</details>
<p>
I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.
</p><p>
We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.
</p><p>
As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341"
title="Recent Blog Posts"
href="http://i2p-projekt.i2p/en/blog/"
author="zzz"
published="2022-10-12T12:00:00Z"
updated="2022-10-12T12:00:00Z">
<details>
<summary>A few recent blog posts</summary>
</details>
<p>
Here's links to several recent blog posts on our website:
</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul>
</article>
<article
id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5"
title="1.9.0 Released"
href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release"
author="zzz"
published="2022-08-22T12:00:00Z"
updated="2022-08-22T12:00:00Z">
<details>
<summary>1.9.0 with SSU2 for testing</summary>
</details>
<p>
We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.
</p><p>
Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.
</p><p>
As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7"
title="New Outproxy exit.stormycloud.i2p"
href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud"
author="zzz"
published="2022-08-05T11:00:00Z"
updated="2022-08-05T11:00:00Z">
<details>
<summary>New Outproxy</summary>
</details>
<p>
I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.
</p><p>
We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.
</p><p>
Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.
</p>
</article>
<article
id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73"
title="1.8.0 Released"
href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release"
author="zzz"
published="2022-05-23T12:00:00Z"
updated="2022-05-23T12:00:00Z">
<details>
<summary>1.8.0 with bug fixes</summary>
</details>
<p>
This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.
</p><p>
Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.
</p><p>
As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71"
title="Install essential Java/Jpackage updates"
href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates"
author="idk"
published="2022-04-22T11:00:00Z"
updated="2022-04-22T11:00:00Z">
<details>
<summary></summary>
</details>
<p>
The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.
</p>
<p>
New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.
</p>
</article>
<article
id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228"
title="1.7.0 Released"
href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release"
author="zzz"
published="2022-02-21T12:00:00Z"
updated="2022-02-21T12:00:00Z">
<details>
<summary>1.7.0 with reliability and performance improvements</summary>
</details>
<p>
The 1.7.0 release contains several performance and reliability improvements.
</p><p>
There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.
</p><p>
The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.
</p><p>
We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.
</p><p>
In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.
</p><p>
As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf"
title="1.6.0 Released"
href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release"
author="zzz"
published="2021-11-29T12:00:00Z"
updated="2021-11-29T12:00:00Z">
<details>
<summary>1.6.0 enables new tunnel build messages</summary>
</details>
<p>
This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.
</p><p>
We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.
</p><p>
In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.
</p><p>
As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9"
title="1.5.0 Released"
href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release"
author="zzz"
published="2021-08-23T12:00:00Z"
updated="2021-08-23T12:00:00Z">
<details>
<summary>1.5.0 with new tunnel build messages</summary>
</details>
<p>
Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.
</p><p>
This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.
</p><p>
As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560"
title="MuWire Desktop Vulnerability"
href="http://muwire.i2p/security.html"
author="zlatinb"
published="2021-07-09T15:00:00Z"
updated="2021-07-09T15:00:00Z">
<details>
<summary>Muwire Desktop Vulnerability</summary>
</details>
<p>
A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.
</p><p>
Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.
</p>
</article>
<article
id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387"
title="MuWire Plugin Vulnerability"
href="http://muwire.i2p/security.html"
author="zlatinb"
published="2021-07-07T11:00:00Z"
updated="2021-07-07T11:00:00Z">
<details>
<summary>Muwire Plugin Vulnerability</summary>
</details>
<p>
A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.
</p><p>
See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.
</p>
</article>
<article
id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48"
title="0.9.50 Released"
href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release"
author="zzz"
published="2021-05-17T12:00:00Z"
updated="2021-05-17T12:00:00Z">
<details>
<summary>0.9.50 with IPv6 fixes</summary>
</details>
<p>
0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.
</p><p>
We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.
</p><p>
As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3"
title="0.9.49 Released"

View File

@ -0,0 +1,16 @@
[
{
"date": "2021-08-23",
"version": "1.5.0",
"minVersion": "0.9.9",
"minJavaVersion": "1.8",
"updates": {
"su3": {
"torrent": "magnet:?xt=urn:btih:4ec75754158779b5b74909a1768e6ab385d61e3b&dn=i2pupdate-1.5.0.su3&tr=http://tracker2.postman.i2p/announce.php",
"url": [
"http://stats.i2p/i2p/1.5.0/i2pupdate.su3"
]
}
}
}
]

View File

@ -0,0 +1,68 @@
<div>
<header title="I2P News">News feed, and router updates</header>
<article
id="urn:uuid:59d8a3ea-aa97-4770-965e-c0ab4e61307b"
title="OSX Release Status"
href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release"
author="zzz"
published="2023-01-09T13:00:00Z"
updated="2023-01-09T13:00:00Z">
<details>
<summary>OSX Support Update</summary>
</details>
<p>
Unfortunately we were unable to release a 2.0.0 OSX Easy-Install Bundle in December as promised.
As the 2.1.0 release was accelerated by six weeks, we will not be releasing 2.0.0.
We are now focused on the build and release for the 2.1.0 Bundle.
</p><p>
We will make an annoucement here in the news feed when it is ready.
You may check our <a href="http://zzz.i2p/">development forum</a> for the latest status.
Thanks for your patience.
</p>
</article>
<article
id="urn:uuid:593f667a-4260-4042-b32d-360f4c4455c9"
title="2.0.0 OSX Release Delayed"
href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release"
author="zzz"
published="2022-11-21T13:00:00Z"
updated="2022-11-21T13:00:00Z">
<details>
<summary>OSX Support Update</summary>
</details>
<p>
The 2.0.0 update for the I2P OSX Easy-Install Bundle will be delayed,
because our OSX maintainer zlatinb recently resigned his position.
We are working to replace the expertise, hardware, and credentials required to build and release updates.
</p><p>
Our current estimate is that the update will be available in about a month.
We will make an annoucement here in the news feed when it is ready.
You may check our <a href="http://zzz.i2p/">development forum</a> for the latest status.
Thanks for your patience.
</p>
</article>
<article
id="urn:uuid:30a1c425-c23e-4a24-b24a-d6bf34cf725f"
title="Apple Silicon Easy Install Bundle"
href="http://i2p-projekt.i2p/en/blog//post/2022/8/3/Apple-Silicon-Easy-Install"
author="zlatinb"
published="2022-08-03T18:00:00Z"
updated="2022-08-03T18:00:00Z">
<details>
<summary>Apple Silicon Easy Install Bundle</summary>
</details>
<p>
If you see this message your Apple Silicon Easy Install bundle is configured correctly. Thanks for testing!
</p>
</article>
</div>

View File

@ -0,0 +1,16 @@
[
{
"date": "2022-08-22",
"version": "1.9.0",
"minVersion": "0.9.9",
"minJavaVersion": "1.8",
"updates": {
"su3": {
"torrent": "magnet:?xt=urn:btih:fefc6532a1c2b7391ad7e2354ae4246580de0c3a&dn=I2P-1.9.0+Mac+DMG+update+%28arm64%29&tr=http://tracker2.postman.i2p/announce.php",
"url": [
"http://n4xen5sohufgjhv327ex4qra77f4tpqohlcyoa3atoboknzqazeq.b32.i2p/i2pmacupdate-arm64-1.9.0.su3"
]
}
}
}
]

View File

@ -0,0 +1,16 @@
[
{
"date": "2021-08-23",
"version": "1.5.0",
"minVersion": "0.9.9",
"minJavaVersion": "1.8",
"updates": {
"su3": {
"torrent": "magnet:?xt=urn:btih:4ec75754158779b5b74909a1768e6ab385d61e3b&dn=i2pupdate-1.5.0.su3&tr=http://tracker2.postman.i2p/announce.php",
"url": [
"http://stats.i2p/i2p/1.5.0/i2pupdate.su3"
]
}
}
}
]

View File

@ -0,0 +1,86 @@
<div>
<header title="I2P News">News feed, and router updates</header>
<article
id="urn:uuid:59d8a3ea-aa97-4770-965e-c0ab4e61307b"
title="OSX Release Status"
href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release"
author="zzz"
published="2023-01-09T13:00:00Z"
updated="2023-01-09T13:00:00Z">
<details>
<summary>OSX Support Update</summary>
</details>
<p>
Unfortunately we were unable to release a 2.0.0 OSX Easy-Install Bundle in December as promised.
As the 2.1.0 release was accelerated by six weeks, we will not be releasing 2.0.0.
We are now focused on the build and release for the 2.1.0 Bundle.
</p><p>
We will make an annoucement here in the news feed when it is ready.
You may check our <a href="http://zzz.i2p/">development forum</a> for the latest status.
Thanks for your patience.
</p>
</article>
<article
id="urn:uuid:49bc001e-4b3b-46a4-a255-9efd2104282b"
title="2.0.0 OSX Release Delayed"
href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release"
author="zzz"
published="2022-11-21T13:00:00Z"
updated="2022-11-21T13:00:00Z">
<details>
<summary>OSX Support Update</summary>
</details>
<p>
The 2.0.0 update for the I2P OSX Easy-Install Bundle will be delayed,
because our OSX maintainer zlatinb recently resigned his position.
We are working to replace the expertise, hardware, and credentials required to build and release updates.
</p><p>
Our current estimate is that the update will be available in about a month.
We will make an annoucement here in the news feed when it is ready.
You may check our <a href="http://zzz.i2p/">development forum</a> for the latest status.
Thanks for your patience.
</p>
</article>
<article
id="urn:uuid:938f15bb-7371-407f-9697-2bf60e593bbb"
title="Security Update for I2P 1.7.1"
href="http://zzz.i2p/topics/3296-java-15-18-ecdsa-vulnerability"
author="zlatinb"
published="2022-04-20T14:00:00Z"
updated="2022-04-20T14:00:00Z">
<details>
<summary>I2P Mac Bundle with Java 18.0.1 Security Update</summary>
</details>
<p>
A security vulnerability affecting the Java Runtime Environment used by I2P has been disclosed.
Please update your Mac bundle to I2P 1.7.1 as soon as you can.
</p>
</article>
<article
id="urn:uuid:f3f4304f-68c1-485c-b759-a63a8cb26a76"
title="Update for Mac JPackage 1.5.1"
href="http://i2p-projekt.i2p/en/blog/post/2021/11/02/i2p-jpackage-1.5.1"
author="zlatinb"
published="2021-11-02T18:00:00Z"
updated="2021-11-02T18:00:00Z">
<details>
<summary>I2P Mac Bundle with Java 17.0.1</summary>
</details>
<p>
Version 1.5.1 of the I2P Mac DMG bundle is now available. It features the latest JDK 17.0.1.
Please update.
</p>
</article>
</div>

View File

@ -0,0 +1,16 @@
[
{
"date": "2022-08-22",
"version": "1.9.0",
"minVersion": "0.9.9",
"minJavaVersion": "1.8",
"updates": {
"su3": {
"torrent": "magnet:?xt=urn:btih:6b3a14d6482583ca97ae9fe5203cd41f0526da5b&dn=I2P-1.9.0+Mac+DMG+update&tr=http://tracker2.postman.i2p/announce.php",
"url": [
"http://n4xen5sohufgjhv327ex4qra77f4tpqohlcyoa3atoboknzqazeq.b32.i2p/i2pmacupdate-1.9.0.su3"
]
}
}
}
]

View File

@ -1,14 +1,15 @@
[
{
"date": "2021-02-17",
"version": "0.9.49",
"date": "2025-03-29",
"version": "2.9.0",
"minVersion": "0.9.9",
"minJavaVersion": "1.8",
"updates": {
"su3": {
"torrent": "magnet:?xt=urn:btih:08449226a35104968f3d6f38f6cbfc9bb0b3c66a&dn=i2pupdate-0.9.49.su3&tr=http://tracker2.postman.i2p/announce.php",
"torrent": "magnet:?xt=urn:btih:78d9f15e58a405f32be7b6ee50f30aeaa5c98460&dn=i2pupdate-2.9.0.su3&tr=http://tracker2.postman.i2p/announce.php",
"url": [
"http://stats.i2p/i2p/0.9.49/i2pupdate.su3"
"http://mgp6yzdxeoqds3wucnbhfrdgpjjyqbiqjdwcfezpul3or7bzm4ga.b32.i2p/2.9.0/i2pupdate.su3",
"http://stats.i2p/i2p/2.9.0/i2pupdate.su3"
]
}
}

View File

@ -1,8 +1,410 @@
<div>
<header title="أخبار I2P">الخلاصة الإخبارية، وتحديثات التوجيه</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<header title="أخبار I2P">الخلاصة الإخبارية، وتحديثات التوجيه</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 الاصدار" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="الإصدار 0.9.37" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 إصدار" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 مع NTCP2 وإصلاحات الأخطاء</summary></details><p>يحتوي الإصدار 0.9.36 على بروتوكول نقل جديد أكثر أمانًا يسمى NTCP2.
هو معطل افتراضيًا، ولكن يمكنك تمكينه للاختبار عن طريق إضافة <a href="/configadvanced"> التهيئة المتقدمة </a><tt> i2np.ntcp2.enable = true </tt>وإعادة التشغيل.
سيتم تمكين NTCP2 في الإصدار التالي. </p>
<p>يحتوي هذا الإصدار أيضًا على العديد من تحسينات الأداء وإصلاحات الأخطاء.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 إصدار" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 مع مجلدات SusiMail و معالج SSL</summary></details><p>يضيف 0.9.35 دعمًا للمجلدات في SusiMail ، ومعالج SSL جديد لإعداد HTTPS على موقع الويب المخفي الخاص بك.</p>
<p>نحن نعمل بجد على عدة أشياء لـ 0.9.36 ، بما في ذلك مثبت OSX جديد وبروتوكول نقل أسرع وأكثر أمانًا يسمى NTCP2.</p>
<p>سيكون I2P في HOPE في مدينة نيويورك ، 20-22 تموز. اعثر علينا وقل مرحبا!</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="أُصدر 0.9.34" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 مع إصلاحات الأخطاء</summary></details><p>0.9.34 يحتوي على الكثير من إصلاحات الأخطاء!
@ -51,51 +453,51 @@ We also have the usual collection of bug fixes, especially in SusiMail.</p>
مساهم! الرجاء مراجعة
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">دليل المترجم الجديد</a>
للحصول على معلومات حول كيفية البدء.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="أُصدر 0.9.30" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
<p>Several plugins are not compatible with Jetty 9 and must be updated.
The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="أُصدر 0.9.30" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 تحديثات لـ Jetty 9</summary></details><p>0.9.30 يحتوي على ترقية لـ Jetty 9 و Tomcat 8.
اﻹصدارات السابقة لن تكون مدعومةً بعد اﻵن، وهي غير متوفرة في إصدارات Debian Stretch و Ubuntu Zesty القادمة.
سيقوم جهاز التوجيه بنقل ملف تهيئة jetty.xml لكل موقع Jetty إلى الإعداد Jetty 9 الجديد.
يجب أن يعمل هذا مع التهيئات الحديثة، أو الغير معدلة، ولكن قد لا يعمل هذا مع الإعدادات القديمة أو المعدلة.
تحقق من أن موقع Jetty الخاص بك يعمل بعد الترقية، واتصل بنا على IRC إذا كنت بحاجة إلى المساعدة.</p>
<p>عدة ملحقات غير متوافقة مع Jetty 9 ويجب تحديثها.
تم تحديث الملحقات التالية للعمل مع 0.9.30 ، ويجب أن يقوم جهاز التوجيه الخاص بك بتحديثها بعد إعادة التشغيل:
i2pbote 0.4.6; zzzot 0.15.0.
The following plugins (with current versions listed) will not work with 0.9.30.
Contact the appropriate plugin developer for the status of new versions:
لن تعمل الإضافات التالية (مع الإصدارات الحالية المدرجة) مع 0.9.30.
تواصل مع مطور الملحق المناسب للاستعلام عن حالة اﻹصدارات الجديدة:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>يدعم هذا الإصدار أيضًا نقل خدمات DSA-SHA1 القديمة (2014 والإصدارات السابقة) إلى نوع توقيع EdDSA الأكثر أمانًا.
راجع <a href="http://zzz.i2p/topics/2271"> zzz.i2p </a> لمزيد من المعلومات ، بما في ذلك دليل والأسئلة الشائعة.</p>
<p>ملاحظة: على اﻷنظمة المختلفة عن Android ARM مثل Raspberry Pi، فسيتم ترقية قاعدة بيانات blockfile بعد إعادة التشغيل ، والتي قد تستغرق عدة دقائق.
يرجى التحلي بالصبر.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="أُصدر 0.9.29" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="أُصدر 0.9.29" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 يحتوي على إصلاحات الأخطاء</summary></details><p>يحتوي 0.9.29 على إصلاحات للعديد من تذاكر تراك، بما في ذلك الحلول البديلة للرسائل المضغوطة الفاسدة.
نحن الآن ندعم NTP عبر IPv6.
لقد أضفنا دعمًا تمهيديًّا لـ Docker.
لقد ترجمنا الآن الـ man pages.
نمرر الآن من نفس المصدر الرؤوس التحويلية عبر وكيل HTTP.
هناك المزيد من الإصلاحات على جافا 9، على الرغم من أننا لا نوصي بعد بـ Java 9 للاستخدام العام.</p>
<p>كالعادة ، نوصي جميع المستخدمين بالتحديث لهذا الإصدار.
أفضل طريقة لمساعدة الشبكة والحفاظ على الأمان هي بتشغيل الإصدار الأخير.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote ثغرة أمنية" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote ثغرة أمنية</summary></details><p>I2P-Bote 0.4.5 تم إصلاح الثغرة الأمنية الموجودة في جميع الإصدارات السابقة من الملحق اﻹضافي لـ I2P-Bote.
لم يتأثر تطبيق Android.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="أُصدر 0.9.28" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 يحتوي على إصلاحات للأخطاء</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>سيتم ترقية جميع مستخدمي I2P-Bote تلقائيًا في المرة الأولى التي يقومون فيها بإعادة تشغيل جهاز التوجيه الخاص بهم
بعد إصدار I2P 0.9.29 في منتصف فبراير. ومع ذلك ، للسلامة نوصيك بأن
<a href="http://bote.i2p/install/">تتبع التعليمات على صفحة التثبيت </a>لـلـ
ترقية اليدويّة إذا كنت تخطط في استخدام I2P أو I2P-Bote في الوقت الحالي.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="أُصدر 0.9.28" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 يحتوي على إصلاحات للأخطاء</summary></details><p>0.9.28 يحتوي على إصلاحات لأكثر من 25 تذكرة تتبع، وتحديثات لعدد من حزم البرامج المجمعة بما في ذلك Jetty.
هناك إصلاحات لميزة اختبار اﻷقران في IPv6 الّتي قدمت في اﻹصدار السابق.
ما زلنا نواصل التحسينات لاكتشاف ومنع الأقران الذين يحتمل أن يكونوا مضرين.
هناك إصلاحات تمهيدية لـ Java 9 ، على الرغم من أننا لم نوصي بعد بالاستخدام العام لـ Java 9.</p>
<p>سيكون I2P في 33C3 ، يرجى زيارتنا هناك وإعطاؤنا أفكارك حول كيفية تحسين الشبكة.
سنراجع خريطة عام 2017 وأولويات 2017 في المؤتمر.</p>
<p>كالعادة ، نوصي جميع المستخدمين بالتحديث لهذا الإصدار.
أفضل طريقة لمساعدة الشبكة والحفاظ على الأمان هي بتشغيل الإصدار الأخير.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote ثغرة أمنية" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote ثغرة أمنية</summary></details><p>يقوم I2P-Bote 0.4.4 بإصلاح ثغرة أمنية موجودة في جميع الإصدارات السابقة من
ملحق I2P-Bote. لم يتأثر تطبيق الـ Android بهذا.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
@ -111,8 +513,8 @@ JavaScript enabled while running I2P-Bote.</p>
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
<p>كالعادة ، نوصي جميع المستخدمين بالتحديث لهذا الإصدار.
أفضل طريقة لمساعدة الشبكة والحفاظ على الأمان هي بتشغيل الإصدار الأخير.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="أُصدر 0.9.26" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
@ -135,8 +537,8 @@ and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
to make it easier to declare that your group of routers is run by a single person.
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
<p>كالعادة ، نوصي جميع المستخدمين بالتحديث لهذا الإصدار.
أفضل طريقة لمساعدة الشبكة والحفاظ على الأمان هي بتشغيل الإصدار الأخير.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="أُصدر 0.9.24" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 يحتوي على العديد من إصلاحات الأخطاء وتسريعات</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
@ -149,8 +551,8 @@ For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration,
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
<p>كالعادة ، نوصي جميع المستخدمين بالتحديث لهذا الإصدار.
أفضل طريقة لمساعدة الشبكة والحفاظ على الأمان هي بتشغيل الإصدار الأخير.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="أُصدر 0.9.23" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 يحتوي على مجموعة متنوعة من إصلاحات الأخطاء، وبعض التحسينات الطفيفة على I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
@ -176,19 +578,19 @@ reintegrates into the network with its new identity.</p>
<p>Note that this will be the last release to support Java 6. Please update to
Java 7 or 8 as soon as possible. We are already working to make I2P compatible
with the upcoming Java 9, and some of that work is in this release.</p>
<p>We have also made some minor improvements in I2PSnark, and added a new page in
the routerconsole for viewing older news items.</p>
<p>لقد أجرينا أيضًا بعض التحسينات الطفيفة في I2PSnark ، وأضفنا صفحة جديدة في
وحدة تحكم الموجه لعرض الأخبار القديمة.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="أُصدر 0.9.22" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 مع إصلاحات الأخطاء وبدأ نزوح Ed25519</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
<p>كان I2PCon تورونتو نجاحا كبيرا!
جميع العروض ومقاطع الفيديو مدرجة على <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">صفحة I2PCon</a>.</p>
<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="أُصدر 0.9.21" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="أُصدر 0.9.21" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>تم إصدار 0.9.21 مع تحسينات في الأداء وإصلاحات للأخطاء.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
and use bandwidth more effectively.
We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
using the new "multisession" capability for those sites that don't support ECDSA.</p>

View File

@ -0,0 +1,605 @@
<div>
<header title="Noticies de I2P">Cahal (feed) de noticies, y anovamientos del router</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="Espublizáu 0.9.36" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 con NTCP2 y igua de fallos</summary></details><p>0.9.36 contien un protocolu de tresporte nuevu, más seguru llamáu NTCP2.
ta desactiváu de mou predetermináu, pero puedes activalu pa pruebes añadiendo en configuración avanzada i2np.ntcp2.enable=true y reaniciado.
NTCP2 tará activáu nel siguiente llanzamientu.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
it if you could set aside a little more time than usual during this release cycle
in order to bring the translations up to speed. We have pushed the strings early
to give you three weeks to work on them.</p>
<p>If you're not currently an I2P translator, now would be a great time to get
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
<p>Several plugins are not compatible with Jetty 9 and must be updated.
The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
i2pbote 0.4.6; zzzot 0.15.0.
The following plugins (with current versions listed) will not work with 0.9.30.
Contact the appropriate plugin developer for the status of new versions:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contains bug fixes</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
for this.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
which will speed up crypto operations considerably.
Also, we are now using constant-time GMP functions to prevent side-channel attacks.
For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
we will include them for in-net updates in the 0.9.27 release.</p>
<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
<p>There's a collection of bug fixes also, including a fix for a timer bug
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contains SAM 3.3, QR codes, and bug fixes</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
It adds QR codes for sharing hidden service addresses with others,
and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
to make it easier to declare that your group of routers is run by a single person.
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
Your router will not automatically update if you are using Java 6.</p>
<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration,
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
<p><b>Housekeeping</b></p>
<p>My signing key has been in router updates for over two years (since 0.9.9), so
if you are on a recent version of I2P this update should be just as easy as
every other update. However, if you are running an older version than 0.9.9, you
will first need to manually update to a recent version. Update files for recent
versions can be downloaded
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
and instructions on how to manually update are provided
<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
updated, your router will then find and download the 0.9.23 update as usual.</p>
<p>If you installed I2P via a package manager, you are not affected by the change,
and can update as usual.</p>
<p><b>Update details</b></p>
<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
with at least half of the network already estimated to have rekeyed. This
release accelerates the rekeying process. To reduce network churn, your router
will have a small probability of converting to Ed25519 at each restart. When it
does rekey, expect to see lower bandwidth usage for a couple of days as it
reintegrates into the network with its new identity.</p>
<p>Note that this will be the last release to support Java 6. Please update to
Java 7 or 8 as soon as possible. We are already working to make I2P compatible
with the upcoming Java 9, and some of that work is in this release.</p>
<p>We have also made some minor improvements in I2PSnark, and added a new page in
the routerconsole for viewing older news items.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
and use bandwidth more effectively.
We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
using the new "multisession" capability for those sites that don't support ECDSA.</p>
<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto speakers and schedule announced" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 speakers and schedule announced</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -1,10 +1,391 @@
<div>
<header title="I2P Xəbərlər">Xəbər axını və istiqamətləndiricinin yenilənməsi</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<header title="I2P Xəbərlər">Xəbər axını və istiqamətləndiricinin yenilənməsi</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Buraxılış" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 xəta düzəlişləri ilə</summary></details><p>0.9.34 xeyli xəta düzəlişləri var!
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Buraxıldı" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>SusiMail qovluqları və SSL Vizardı ilə 0.9.35</summary></details><p>SusiMail-də qovluqlar üçün dəstək və Gizli Xidmət saytında HTTPS-i qurmaq üçün 0.9.35 yeni SSL Vizardı əlavə edir.
Bizim xüsusilə SusiMail-də adi xəta düzəlişləri kolleksiyamız var.</p>
<p>Yeni OSX quraşdırıcısı və daha sürətli, daha təhlükəsiz nəqliyyat protokolu olan NTCP2 də daxil olmaqla, 0.9.36 üçün bir neçə məsələ üzərində çalışırıq.</p>
<p>I2P 20-22 iyul tarixlərində Nyu-York şəhərində HOPE-da olacaq. Bizi tapıb, salamlayın!</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Buraxıldı" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 xəta düzəlişləri ilə</summary></details><p>0.9.34 xeyli xəta düzəlişləri var!
SusiMail, IPv6 ilə işdə və tunel bənzərlərinin seçimində təkmilləşdirmələr var.
Biz UPnP-də IGD2-ə dəstək sxemləri əlavə etdik.
Gələcək buraxılışlarda görəcəyiniz əlavə təkmilləşmələrə hazırlıq gedir.</p>
@ -52,7 +433,7 @@ Daha ətraflı məlumat üçün <a href="http://zzz.i2p/topics/2271">zzz.i2p-ə<
<p>Qeyd: Raspberry Pi kimi qeyri-Android ARM platformalarında blok verilənlər bazası yenidən başladılanda, bu, bir neçə dəqiqə çəkə bilər.
Səbrli olun.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Başladıldı" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 xəta düzəlişləri var</summary></details><p>0.9.29 çoxsaylı Trac biletlərinə, təhrif olunmuş sıxılmış mesajlar üçün həllər də daxil olmaqla, düzəlişləri ehtiva edir.
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Buraxıldı" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 xəta düzəlişləri var</summary></details><p>0.9.29 çoxsaylı Trac biletlərinə, təhrif olunmuş sıxılmış mesajlar üçün həllər də daxil olmaqla, düzəlişləri ehtiva edir.
Biz artıq IPv6 üzərindən NTP-ni dəstəkləyirik.
İlkin Docker dəstəyini əlavə etdik.
İndi soraq səhifələrini tərcümə etdik.
@ -62,124 +443,104 @@ Java 9 üçün daha çox düzəliş var, baxmayaraq ki, biz hələ də ümumi is
Şəbəkəyə kömək etmək və təhlükəsiz qalmağn ən yaxşı yolu ən son buraxılışı yükləməkdir. </p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote təhlükəsizlik zəifliyi" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote təhlükəsizlik zəifliyi</summary></details><p>I2P-Bote 0.4.5, I2P-Bote qoşmalarının əvvəlki versiyalarındakı təhlükəsizlik zəifliyini düzəldir.
Android tətbiqinə təsir etmədi.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p> Fevralın ortalarında I2P-nin 0.9.29 versiyası buraxıldıqdan sonra, İ2P-Bote istifadəçilərinin hamısı
<p>İstifadəçiyə email-ləri göstərərkən, əksər sahələr çıxarılmayıb. Bununla belə qoşmaların adları
çıxarılmayıb və JavaScript ilə aktivləşdirilmiş brauzerdə ziyanverici kod məqsədilə istifadə edilə
bilər. Onlar artıq çıxarıldı və əlavə olaraq bütün səhifələr üçün Məzmun Təhlükəsizlik Siyasəti tətbiq
edilib.</p>
<p>Fevralın ortalarında I2P-nin 0.9.29 versiyası buraxıldıqdan sonra, İ2P-Bote istifadəçilərinin hamısı
istiqamətləndiricini yenidən başladan zaman avtomatik yenilənəcəklər. Əgər 0.9.29-dan İ2P və ya İ
Bununla belə, təhlükəsizlik səbəbilə 0.9.29-un buraxılışından əvvəl I2P və ya I2P-Bote-dan istifadə etməyi planlaşdırırsınızsa, yeniləmə üçün <a href="http://bote.i2p/install/">quraşdırma səhifəsindəki </a>təlimatları
izləməyi məsləhət görürük. </p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Buraxıldı" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 xəta düzəlişləri var</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Buraxıldı" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 xəta düzəlişləri var</summary></details><p>0.9.28 25-dən artıq Trac biletinə düzəlişlərdən və Jetty də daxil olmaqla, bir sıra paket proqram üçün yeniliklərdən ibarətdir.
Son buraxılışda IPv6 peer testi xüsusiyyətləri üçün düzəlişlər var.
Biz potensial zərərli peer-lərin aşkarlanaraq, bloklanması üçün təkmilləşdirmələrə davam edirik.
Java 9 üçün ilkin düzəlişlər var, hərçənd onu hələlik ümumi istifadə üçün məsləhət görmürük. </p>
<p>I2P 33C3-də iştirak edəcək, xahiş edirik masamızdan yan keçməyin və şəbəkənin inkişafı ilə əlaqədar fikirlərinizi bölüşün.
Konqresdə 2017-ci ilin yol xəritəsini və prioritetləri nəzərdən keçirəcəyik.</p>
<p>Hər zamanki kimi bütün istifadəçilərə bu buraxılışı yeniləməyi məsləhət görürük.
Şəbəkəyə kömək etmək və təhlükəsiz qalmağn ən yaxşı yolu ən son buraxılışı yükləməkdir. </p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote təhlükəsizlik zəifliyi" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote təhlükəsizlik zəifliyi</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
for this.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote təhlükəsizlik zəifliyi" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote təhlükəsizlik zəifliyi</summary></details><p>I2P-Bote-da 0.4.4 I2P-Bote qoşmalarının əvvəlki versiyalarında mövcud olan təhlükəsizlik zəifliyini düzəldir. Android tətbiqinə təsiri olmadı.</p>
<p>CSRF müdafiəsinin çatışmazlığı o demək olardı ki, istifadəçi I2P-Bote-u işə salsın, daha sonra
JavaScript ilə aktivləşdirilmiş brauzerə ziyanverici kodu yükləsin, rəqib I2P-Bote-da istifadəçinin
adından hərəkətə səbəb olsun, məsələn, məlumat göndərsin. Bu, I2P-Bote ünvanları üçün məxfi
açarların çıxarılmasını aktivləşdirə bilərdi, hərçənd bununla əlaqədar sınaq aparılmayıb.</p>
<p>İ2P 0.9.28 dekabr ayının ortalarında buraxıldıqdan sonra I2P-Bote istifadəçilərinin hamısı istiqamətləndircilərini ilk dəfə yenidən başlandanda avtomatik olaraq yenilənəcəklər. Lakin təhlükəsizlik səbəbindən biz <a href="http://bote.i2p/install/">quraşdırma səhifəsindəki təlimatları izləməyi</a>, bu müddətdə İ2P və ya İ2P-Bote-dan istifadəni planlaşdırırsınızsa, yeniləməni əl ilə aparmağı məsləhət görürük.
I2P-Bote-dan istifadə zamanı müntəzəm olaraq JavaScript-i aktiv olan saytlara baxırsınızsa, yeni I2P-Bote ünvanlarının yaradılmasını da düşünməlisiniz.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Buraxıldı" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 xəta düzəlişləri var</summary></details><p>0.9.27 buraxılışında müxtəlif xəta düzəlişləri var.
Şifrələməni sürətləndirmək üçün yenilənən və 0.9.26 buraxılışında yalnız yeni Debian quruluşları üçün əlavə olunan GMP kitapxanası indi şəbəkə yenilənmələrinə əlavə edildi.
IPv6 nəqliyyatı, SSU peer sınağı və gizli rejim məsələlərində yaxşılaşma var. </p>
<p><a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> zamanı bir sıra qoşmaları yenilədik və yenidən başladıqdan sonra istiqamətləndiriciniz avtomatik olaraq onları yeniləyəcək.</p>
<p>Hər zamanki kimi bütün istifadəçilərə bu buraxılışı yeniləməyi məsləhət görürük.
Şəbəkəyə kömək etmək və təhlükəsiz qalmağn ən yaxşı yolu ən son buraxılışı yükləməkdir. </p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
which will speed up crypto operations considerably.
Also, we are now using constant-time GMP functions to prevent side-channel attacks.
For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
we will include them for in-net updates in the 0.9.27 release.</p>
<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
<p>There's a collection of bug fixes also, including a fix for a timer bug
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contains SAM 3.3, QR codes, and bug fixes</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
It adds QR codes for sharing hidden service addresses with others,
and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
to make it easier to declare that your group of routers is run by a single person.
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange təklifi" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>İndi I2P Stack Exchange üzərində təklif olunan saytdır!</summary></details><p>İndi I2P Stack Exchange üzərində təklif olunan saytdır!
Zəhmət olmasa sınaq fazasının başlaması üçün <a href="https://area51.stackexchange.com/proposals/99297/i2p">istifadə edin</a>.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Buraxıldı" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 buraxılışında kripto yeniliklər, Debian paketi yaxşılaşmaları və xəta düzəlişləri var.</summary></details><p>0.9.26 buraxılışında doğma kripto kitabxanaya böyük yeniləmələr,
imzalarla birgə yeni ünvan kitabına abunəlik protokolu,
Debian/Ubuntu paketləri üçün böyük dəyişikliklər yer alıb.</p>
<p>Kriptoqrafiya GMP 6.0.0 buraxılışına yüksəldildi və kriptoqrafiya sürətini əhəmiyyətli dərəcədə artıracaq daha yeni prosessorlara dəstəyi əlavə etdik.
Bundan əlavə yan kanal hücumlarının qarşısını almaq üçün sabit zamanlı GMP funksiyalarından istifadə edirik.
Diqqətli olun, GMP dəyişiklikləri yeni quraşdırmalar və Debian / Ubuntu quruluşları üçün aktivdir;
biz bunları 0.9.27 buraxılışının şəbəkəiçi yeniləmələrinə əlavə edəcəyik.</p>
<p>Debian/Ubuntu qurumları üçün Jetty 8 ve geoip kimi bəzi paket asılılıqları əlavə olundu və
ekvivalent kodlar aradan qaldırıldı. </p>
<p>Burada həmçinin zamanla qeyri-sabitlik və performansın azalmasına səbəb olmuş taymer xətası da daxil, bir sıra xəta düzəlişləri var.
Hər zamanki kimi bütün istifadəçilərə buraxılışı yeniləməyi məsləhət görürük.
Şəbəkəyə kömək etmək və təhlükəsiz qalmağın ən yaxşı üsulu ən son buraxılışdan istifadə etməkdir.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Buraxıldı" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 buraxılışında SAM 3.3, QR kodları və xəta düzəlişləri yer alıb</summary></details><p>0.9.25 mürəkkəb çox protokollu tətbiqləri dəstəkləyən yeni SAM, v3.3 buraxılışından ibarətdir.
Gizli xidmət ünvanlarını paylaşmaq üçün QR kodları və ünvanları gözlə ayırd edə bilmək üçün
"identicon" təsvirləri əlavə olundu. </p>
<p>Təkcə bir adam tərəfindən işlədilən istiqamələndirici qrupunu daha asan müəyyən etmək üçün
konsola yeni "istiqamətləndirici ailə" quraşdırma səhifəsi əlavə olundu. Şəbəkə həcmini və tunel
quruluş uğurunu artıran bəzi dəyişikliklər edildi. </p>
<p>Hər zamanki kimi bütün istifadəçilərə bu buraxılışı yeniləməyi məsləhət görürük.
Şəbəkəyə kömək etmək və təhlükəsiz qalmağn ən yaxşı yolu ən son buraxılışı yükləməkdir. </p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
Your router will not automatically update if you are using Java 6.</p>
<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration,
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Buraxıldı" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 buraxılışında bəzi xəta düzəlişləri və sürətləndirmələr yer alıb</summary></details><p>0.9.24 yeni SAM (v3.2) buraxılışı və çeşidli xəta və sürətləndirmə düzəlişlərindən ibarətdir..
Bu buraxılışın işləməsi üçün Java 7 tələb olunur.
Ən qısa zamanda Java 7 və ya 8-ə yeniləyin.
Java 6-dan istifadə etdiyiniz halda istiqamətləndiriciniz avtomatik olaraq yenilənməyəcək.</p>
<p>Qədim commons-logging kitabxanasından qaynaqlanan problemləri əngəlləmək üçün aradan qaldırdıq.
Çox qədim I2P-Bote qoşmaları (HungryHobo tərəfindən imzalanmış 0.2.10 və aşağı) IMAP-ı aktivləşdirsələr zədələnə bilərlər.
Düzəltmək üçün qədim I2P-Bote qoşmanızı str4d. tərəfindən imzalanan cari ilə dəyişdirməyiniz tövsiyə olunur.
Daha ətraflı məlumat üçün bu <a href="http://bote.i2p/news/0.4.3">yazıya</a> baxın.</p>
<p><a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Konqresi</a> böyük idi və 2016 layihə planlarımız da yaxşı irəliləyir.
Echelon-un I2P-nin keçmiş və indiki statusu ilə bağlı çıxışına və slaydına <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">buradan</a> baxmaq olar (pdf).
Str4d <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto-ya</a> qatılaraq, kripto miqrasiya haqqında çıxış edib, onun slaydı ilə <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">buradan</a> tanış ola bilərsiniz (pdf). </p>
<p>Hər zamanki kimi bütün istifadəçilərə bu buraxılışı yeniləməyi məsləhət görürük.
Şəbəkəyə kömək etmək və təhlükəsiz qalmağn ən yaxşı yolu ən son buraxılışı yükləməkdir. </p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
<p><b>Housekeeping</b></p>
<p>My signing key has been in router updates for over two years (since 0.9.9), so
if you are on a recent version of I2P this update should be just as easy as
every other update. However, if you are running an older version than 0.9.9, you
will first need to manually update to a recent version. Update files for recent
versions can be downloaded
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
and instructions on how to manually update are provided
<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
updated, your router will then find and download the 0.9.23 update as usual.</p>
<p>If you installed I2P via a package manager, you are not affected by the change,
and can update as usual.</p>
<p><b>Update details</b></p>
<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
with at least half of the network already estimated to have rekeyed. This
release accelerates the rekeying process. To reduce network churn, your router
will have a small probability of converting to Ed25519 at each restart. When it
does rekey, expect to see lower bandwidth usage for a couple of days as it
reintegrates into the network with its new identity.</p>
<p>Note that this will be the last release to support Java 6. Please update to
Java 7 or 8 as soon as possible. We are already working to make I2P compatible
with the upcoming Java 9, and some of that work is in this release.</p>
<p>We have also made some minor improvements in I2PSnark, and added a new page in
the routerconsole for viewing older news items.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Buraxıldı" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 buraxılışında çeşidli xəta düzəlişləri və I2PSnark irəliləyişləri yer alıb</summary></details><p>Salam I2P! Bu buraxılış zzz tərəfindən imzalanan 49 buraxılışdan sonra mənim imzaladığım (str4d) ilk buraxılışdır.
Layihənin müxtəlif hissələrinin, o cümlədən, iştirakçılarının dəyişməsinin yoxlanılması.</p>
<p><b>Təmizlik</b></p>
<p>İmza açarım iki ildən çoxdur istiqamətləndirici yeniləmələrində yer alırdı (0.9.9-dan bəri). I2P-nin son buraxılışlarından birindən istifadə edirsinizsə, yeniləmə işi digər yeniləmələr qədər asan olur.
0.9.9-dan əvvəlki buraxılışı istifadə edirsinizsə, öncə əl ilə daha yeni buraxılışa yeniləməniz lazımdır.
Son buraxılışların fayllarını <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">burdan</a> tapmaq olar.
<a href="http://i2p-projekt.i2p/en/download#update">Əl ilə yeniləməni</a> tamamladığınızda, istiqamətləndirici 0.9.23 buraxılışını tapıb endirə bilər. </p>
<p>I2P-ni paket idarəçisi tərəfindən quraşdırmısınızsa, dəyişikliklərdən təsirlənməyəcək və normal şəkildə yeniləyə biləcəksiniz. </p>
<p><b>Yeniləmə detalları</b></p>
<p>Routerinfos üçün yeni və daha güclü Ed25519 imzalarına keçmə işi yaxşı gedir.
Şəbəkənin ən az yarısı yenilənib. Bu buraxılışda açar dəyişdirmə prosesi sürətləndirildi. Şəbəkə qarışıqlığı olmasın deyə, istiqmətləndiriciniz hər dəfə yenidən başlayanda kiçik ehtimalla Ed25519 çevrilməsi edəcək. Əgər bu baş verərsə, yaxın iki gündə yeni ünvan şəbəkəyə
uyğunlaşana qədər trafikin azalması müşahidə olunacaq.</p>
<p>Bu, Java 6-nı dəstəkləyən son buraxılışdır. Java 7 və ya 8 buraxılışına mümkün qədər tez
yeniləməyi unutmayın. I2P buraxılışını tezliklə buraxılacaq Java 9 ilə uyumlu şəkildə inkişaf
etdirməyə başladıq və artıq bəzi dəyişikliklər edilib. </p>
<p>I2PSnark-da bəzi kiçik yeniləmələr edərək, routerconsole üçün keçmiş xəbərlərin görüntülənə biləcəyi yeni səhifə əlavə etdik.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Buraxıldı" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 buraxılışında xəta düzəlişləri və Ed25519 keçid başlanması </summary></details><p>Əvvəlcə 0.9.22 buraxılışında ilişməyə səbəb olan i2psnark problemi həll olundu və istiqamətləndirici məlumatlarının yeni və daha güclü Ed25519 imzalarına keçirilməsi təmin olundu.
Şəbəkə qarışıqlığı olmasın deyə, istiqmətləndiriciniz hər dəfə yenidən başlayanda kiçik ehtimalla Ed25519 çevrilməsi edəcək.
Əgər bu baş verərsə, yaxın iki gündə yeni ünvan şəbəkəyə uyğunlaşana qədər trafikin azalması müşahidə olunacaq.
Hər şey yolunda getsə, sonrakı buraxılışda yenidən açar yaratmaq prosesini sürətləndirəcəyik. </p>
<p>I2PCon Toronto görüşü çox uğurlu idi!
Bütün təqdimat və videolara <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon səhifəsindən</a> baxa bilərsiniz. </p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
and use bandwidth more effectively.
We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
using the new "multisession" capability for those sites that don't support ECDSA.</p>
<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Buraxıldı" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 buraxılışında məhsuldarlıq təkmilləşdirməsi və səhv düzəlişləri ilə</summary></details><p>0.9.21 buraxılışı şəbəkə həcmini artıran fərqli dəyişikliklər,
floodfill
səmərəliliyini artıran və ötürmə qabiliyyətindən daha məhsuldar istifadə edən xüsusiyyətlər ilə buraxıldı.
Paylaşılan müştəri tunellərini ECDSA imzaları ilə birləşdirdik və ECDSA dəstəkləməyən saytlar üçün yeni "çoxseanslı" qabiliyyətini qiymətləndirən DSA əlavə etdik.</p>
<p>2015-ci il Torontoda keçiriləcək I2PCon konfransının məruzəçiləri və təqvimi elan olunub.
Əlavə məlumat üçün <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon səhifəsinə</a> baxın.
<a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a> üçün yerinizi bronlayın.</p>
<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı yükləməkdir.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto speakers and schedule announced" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 speakers and schedule announced</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto məruzəçiləri və təqvimi elan olundu" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto məruzəçiləri və təqvimi elan olundu</summary></details><p>2015-ci il Torontoda keçiriləcək I2PCon konfransının məruzəçiləri və təqvimi elan olunub.
Əlavə məlumat üçün <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon səhifəsinə</a> baxın.
<a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a> üçün yerinizi bronlayın.</p>
</article>
</div>

View File

@ -0,0 +1,605 @@
<div>
<header title="I2P Novinky">News feed, and router updates</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Vydána" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 s IPv6 opravami</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Vydána" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Vydána" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Vydána" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Vydána" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Vydána" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Vydána" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Vydána" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Vydána" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
it if you could set aside a little more time than usual during this release cycle
in order to bring the translations up to speed. We have pushed the strings early
to give you three weeks to work on them.</p>
<p>If you're not currently an I2P translator, now would be a great time to get
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
<p>Several plugins are not compatible with Jetty 9 and must be updated.
The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
i2pbote 0.4.6; zzzot 0.15.0.
The following plugins (with current versions listed) will not work with 0.9.30.
Contact the appropriate plugin developer for the status of new versions:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contains bug fixes</summary></details><p>0.9.28 obsahuje opravy více než 25 Trac problémů a aktualizací vestavěných balíčků software, včetně Jetty.
Jsou zde opravy funkce testování IPv6 peera, která byla představena v minulém vydání.
Pokračujeme s vylepšeními rozpoznání a blokování peerů, kteří jsou potenciálně nebezpeční.
Jsou zde předběžné opravy pro Java 9, avšak ještě nedoporučujeme Java 9 pro obecné použití.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
for this.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
which will speed up crypto operations considerably.
Also, we are now using constant-time GMP functions to prevent side-channel attacks.
For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
we will include them for in-net updates in the 0.9.27 release.</p>
<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
<p>There's a collection of bug fixes also, including a fix for a timer bug
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contains SAM 3.3, QR codes, and bug fixes</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
It adds QR codes for sharing hidden service addresses with others,
and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
to make it easier to declare that your group of routers is run by a single person.
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
Your router will not automatically update if you are using Java 6.</p>
<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration,
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
<p><b>Housekeeping</b></p>
<p>My signing key has been in router updates for over two years (since 0.9.9), so
if you are on a recent version of I2P this update should be just as easy as
every other update. However, if you are running an older version than 0.9.9, you
will first need to manually update to a recent version. Update files for recent
versions can be downloaded
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
and instructions on how to manually update are provided
<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
updated, your router will then find and download the 0.9.23 update as usual.</p>
<p>If you installed I2P via a package manager, you are not affected by the change,
and can update as usual.</p>
<p><b>Update details</b></p>
<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
with at least half of the network already estimated to have rekeyed. This
release accelerates the rekeying process. To reduce network churn, your router
will have a small probability of converting to Ed25519 at each restart. When it
does rekey, expect to see lower bandwidth usage for a couple of days as it
reintegrates into the network with its new identity.</p>
<p>Note that this will be the last release to support Java 6. Please update to
Java 7 or 8 as soon as possible. We are already working to make I2P compatible
with the upcoming Java 9, and some of that work is in this release.</p>
<p>We have also made some minor improvements in I2PSnark, and added a new page in
the routerconsole for viewing older news items.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
and use bandwidth more effectively.
We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
using the new "multisession" capability for those sites that don't support ECDSA.</p>
<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto speakers and schedule announced" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 speakers and schedule announced</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -0,0 +1,605 @@
<div>
<header title="I2P nyheder">Nyhedsfeed og router-opdateringer</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Frigivet" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 frigivet" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 med SSU2 til test</summary></details><p>Vi har de tre seneste måneder arbejdet på vores nye UDP transport protokol SSU2
med et lille antal frivillige testere.
Denne release færdiggør implementeringen, inklusiv relay og peer testing.
Vi aktiverer det pr. default for Androud og ARM platforme, og en mindre andel øvrige, tilfældige routere
Dette muliggør, at vi kan foretage meget mere testning i de næste tre måneder, færdiggøre forbindelsesmigrationsfeaturen,
samt rette øvrige tilbageværende problemer.
Vi planlægger at aktivere det for alle i den næste frigivelse, som er planlagt til november.
Manuel konfiguration er ikke nødvendig.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
it if you could set aside a little more time than usual during this release cycle
in order to bring the translations up to speed. We have pushed the strings early
to give you three weeks to work on them.</p>
<p>If you're not currently an I2P translator, now would be a great time to get
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
<p>Several plugins are not compatible with Jetty 9 and must be updated.
The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
i2pbote 0.4.6; zzzot 0.15.0.
The following plugins (with current versions listed) will not work with 0.9.30.
Contact the appropriate plugin developer for the status of new versions:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contains bug fixes</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
for this.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
which will speed up crypto operations considerably.
Also, we are now using constant-time GMP functions to prevent side-channel attacks.
For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
we will include them for in-net updates in the 0.9.27 release.</p>
<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
<p>There's a collection of bug fixes also, including a fix for a timer bug
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contains SAM 3.3, QR codes, and bug fixes</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
It adds QR codes for sharing hidden service addresses with others,
and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
to make it easier to declare that your group of routers is run by a single person.
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
Your router will not automatically update if you are using Java 6.</p>
<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration,
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
<p><b>Housekeeping</b></p>
<p>My signing key has been in router updates for over two years (since 0.9.9), so
if you are on a recent version of I2P this update should be just as easy as
every other update. However, if you are running an older version than 0.9.9, you
will first need to manually update to a recent version. Update files for recent
versions can be downloaded
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
and instructions on how to manually update are provided
<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
updated, your router will then find and download the 0.9.23 update as usual.</p>
<p>If you installed I2P via a package manager, you are not affected by the change,
and can update as usual.</p>
<p><b>Update details</b></p>
<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
with at least half of the network already estimated to have rekeyed. This
release accelerates the rekeying process. To reduce network churn, your router
will have a small probability of converting to Ed25519 at each restart. When it
does rekey, expect to see lower bandwidth usage for a couple of days as it
reintegrates into the network with its new identity.</p>
<p>Note that this will be the last release to support Java 6. Please update to
Java 7 or 8 as soon as possible. We are already working to make I2P compatible
with the upcoming Java 9, and some of that work is in this release.</p>
<p>We have also made some minor improvements in I2PSnark, and added a new page in
the routerconsole for viewing older news items.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
and use bandwidth more effectively.
We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
using the new "multisession" capability for those sites that don't support ECDSA.</p>
<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto speakers and schedule announced" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 speakers and schedule announced</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -1,20 +1,374 @@
<div>
<header title="I2P - Nachrichten">Neuigkeiten und Router-Aktualisierungen</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 enthält jetzt SusiMail Verzeichnisse und einen SSL Wizzard</summary></details><p>0.9.35 fügt nun Support für EMail Verzeichnisse in SusiMail hinzu und einen neuen SSL Wizzard zum aktivieren von HTTPS auf ihren Versteckten Services Webseite.
Desweiteren wurden wie üblich jede Menge Fehler, besonders in SusiMail, behoben.</p>
<header title="I2P - Nachrichten">Neuigkeiten und Router-Aktualisierungen</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 mit zahlreichen SSU2-Korrekturen</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2-Übertragung aktiviert</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Neueste Blog-Beiträge" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 mit SSU2 zum Testen</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>Neuer Ausgangsproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 enthält Fehlerkorrekturen</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 mit Zuverlässigkeits- und Leistungsverbesserungen</summary></details><p>Das 1.7.0 Update enthält verschiedenen Zuverlässigkeits- und Leistungsverbesserungen. </p>
<p>Es gibt nun Popup-Benachrichtigungen für die Plattformen, die sie unterstützen.
i2psnark hat einen neuen Torrent Editor.
Der NTCP2 Transport lastet den CPU weniger aus. </p>
<p>Die völlig veraltete BOB Schnittstelle ist bei einer Neuinstallation nicht mehr dabei sein.
Es wird aber weiterhin in bereits bestehenden Installation funktionieren, mit Ausnahme von Debian-Paketen.
Alle verbleibenden Nurten der BOB Anwendung sollten die Entwickler bitten, auf das SAMv3 Protokoll umzustellen. </p>
<p>Wir wissen, dass sich die Netzwerkleistung seit dem 1.6.1 Update immer weiter verschlechtert hat.
Wir waren uns den Problems gleich nach der Veröffentlichung bewusst, aber es dauerte fast zwei Monate, bis wir die Ursache fanden.
Wir haben es schließlich als Fehler i2pd 2.40.0 identifiziert,
und der Fix wird in der der Version 2.41.0 verfügbar sein, welche ungefähr zur gleichen Zeit wie diese Version erscheinen wird.
Außerdem haben wird mehrere Änderungen auf der Java I2P-Seite vorgenommen, um die
Robustheit von Netzwerkdatenbanksuchen und -speichern und die Vermeidung schlechter Ergebnisse bei der Auswahl von Tunnel Peers zu verbessern.
Dies soll die Robustheit auch bei der Gegenwart von fehlerhaften oder bösartigen Routern sicherstellen.
Darüber hinaus starten wir ein gemeinsames Programm zum Testen von Vorabversionen der i2pd- und Java i2P-Routern zusammen in einem isolierten Testnetzwerk, so dass wir mehr Probleme vor der Veröffentlichung finden können, nicht danach. </p>
<p>Außerdem machen wir weiterhin große Fortschritte, was die Gestaltung unseres neuen UDP-Transports "SSU2" (Vorschlag Nr. 159) angeht uns haben mit der Implementierung begonnen.
SSU2 wird erhebliche Leistungs- und Sicherheitsverbesserungen bringen.
Es wird uns auch die Möglichkeit schaffen, die sehr langsamen ElGamal-Verschlüsslung endlich zu ersetzten, damit wir den Abschluss eines vollständigen Kryptographie-Upgrade, das vor etwa 9 Jahren begann erreichen können.
Wir gehen davon aus, dass wir bald mit gemeinsamen Tests mit i2pd beginnen können und Änderungen später in diesem Jahr auf das Netzwerk ausweiten können. </p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 aktiviert neue Tunnelaufbau-Nachrichten</summary></details><p>Diese Version komplementiert den Rollout von 2 großen Protokoll Aktualisierungen, die in 2021 entwickelt wurden.
Die Migration zur X25519 Verschlüsselung wird beschleunigt und wir erwarten bis zum Ende des Jahres die Schlüssel-Umstellung nahezu aller Router.
Kurze Tunnelaufbau-Nachrichten werden aktiviert und bieten eine erhebliche Reduzierung der Bandbreitennutzung jener.</p>
<p>Wir haben ein Panel zur Auswahl eines Themes im Neue-Installation Wizzard inkludiert.
Wir haben die Performance von SSU verbessert und einen Fehler in den SSP Peer Test Nachrichten behoben.
Der Tunnelaufbau Bloom-Filter wurde auch adaptiert um weniger Speicher zu nutzen.
Wir haben den Support von Nicht-Java-Erweiterungen verbessert.</p>
<p>In weiteren Neueigkeiten: we machen sehr gute Fortschritte beim Design unseres neuen UDP Transports SSU2 und erwarten den Start der Implementierung im nächsten Jahr.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 mit neuen Tunnelaufbau Nachrichten</summary></details><p>Ja, richtig gelesen, nach 9 Jahren von 0.9.x Versionen wechseln wir direkt von 0.9.50 zu Version 1.5.0.
Dieses impliziert jedoch keine große Änderung an der API or eine Behauptung, die Entwicklung sei jetzt fertig.
Es ist nur eine Feststellung von 20 Jahren Arbeit um Anonymität uind Sicherheit unseren Nutzenden anzubieten.</p>
<p>Diese Version komplementiert die Implementierung von kleinere Tunnelaufbau Nachrichten um die Bandbreitennutzung jener zu reduzieren.
Wir verfolgen weiter die Umstellung der Netzwerk-Router zur X25519 Verschlüsselung.
Natürlich gibt es diverse Fehlerverbesserungen und Performance Verbesserungen.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Schwachstelle" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>MuWire Desktop Schwachstelle</summary></details><p>Eine Sicherheits Schwachstelle wurde im Muwire Standalone Desktop Klienten entdeckt.
Diese betrifft nicht das Konsolen-Plugin und steht nicht in Verbindung mit der kürzlich veröffentlichten Plugin Schwachstelle.
Falls Sie die Muwire Desktop Anwendung nutzen, sollten Sie sofort <a href="http://muwire.i2p/">auf Version 0.8.8</a> aktualisieren.</p>
<p>Details zu diesem Problem wird auf <a href="http://muwire.i2p/security.html">muwire.i2p</a> zum 15.July 2021 veröffentlicht.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Schwachstelle" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>MuWire Plugin Schwachstelle</summary></details><p>Eine Sicherheits Schwachstelle wurde im MuWire Plugin entdeckt.
Diese betrifft nicht den Standalone Desktop Klienten.
Falls Sie das MuWire Plugin nutzeen, sollten Sie sofott auf <a href="/configplugins">Version 0.8.7-b1 aktualisieren.</a> </p>
<p>Schaue auf<a href="http://muwire.i2p/security.html">muwire.i2p</a>
für mehr Informationen zu dieser Schwachstelle und aktualisierte Sicherheits Empfehlungen.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 enthält Korrekturen für IPv6</summary></details><p>0.9.50 führt die Transition fort hinr zu ECIES-X25519 Router Verschlüsselung.
DNS über HTTPS wurde für das Reseeding aktiviert, dieses schützt BenutzerInnen vor passivem DNS Snooping.
Neben einem neuen UPnP Support wurden zahlreiche Korrekturen und Verbesserungen für IPv6 Adressen inkludiert.</p>
<p>Endlich wurden auch einige lang ausstehende SusiMail Korruptionsfehler behoben.
Änderungen an den Bandbreitenlimitern sollte die Netzwerk Tunnel Performance verbessern.
Es gibt diverse Verbesserungen für die Docker Container.
Diverse Abwehrmaßnahemen gegenüber möglichen feindseeligen und gefährlichen Router im I2P Netzwerk wurden verbessert.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 mit SSU Korrekturen und schnelleren Kryptographieoperationen</summary></details><p>0.9.49 führt die Arbeiten zum Beschleuningen und besseren Absicherung von I2P fort.
Es gibt diverse Verbesserungen und Korrekturen für den SSU (UDP) Transport, aus denen höhere Geschwindigkeiten resultieren sollten.
Diese Version startet auch die Migration zur neuen, schnelleren ECIES-X25519 Verschlüsselung für die Router.
(Destinationen nutzen diese Verschlüsselung schon seit einigen Versionen)
Wir haben seit einigen Jahren an den Spezifikationen und Implementationen für die neue Verschlüsselung gearbeitet und kommen dem Abschluß dieser Arbeiten nahe! Diese Migration wird einige Versionen bis zum Abschluß benötigen.</p>
<p>Zur Vermeidung von großen Unterbrechungen werden mit dieser Version nur neue Installationen und ein kleiner Teil der bestehenden Installationen (beim Neustart zufällig ausgewählt) die neue Verschlüsselung nutzen.
Falls Ihr Router auf die neue Verschlüsselung umstellt, wird dieser wahrscheinlich einige Tage nach dem Neustart weniger stabil sein und weniger Bandbreite nutzen.
Dieses ist normal, da ihr Router eine neue Identifikation bekommt. Ihre Router-Performance wird nach einer Weile wieder erholt sein.</p>
<p>Wir haben das I2P Netzwerk schon 2 mal dieser Prozdeur unterzogen, beim Ändern des Stanardsignatur Typus, aber dieses ist das erste Mal, das wir den Standard Verschlüsselung Typus ändern-
Es sollte problemfrei funktionieren, zur Sicherheit starten wir mit einer kleiner Anzahl an Migrationen.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 mit Performanceerbesserungen</summary></details><p>0.9.48 aktiviert das neue Ende-zu-Ende Verschlüsselungsprotokoll (Vorschlag 144) fur fast alle Services.
Vorläufige Unterstützung für die neue Verschlüsselung der Tunnelaufbaunachrichten (Vorschlag 152) wurde auch hinzugefügt.
Es gibt signifikante Verbesserung der Perforamnce im gesamten Routerr.</p>
<p>Pakete für Ubuntu Xenial (16.04 LTS) werden nicht mehr unterstützt und zur Verfügung gestellt.
BenutzerInnen dieser Plattform sollten diese aktualisieren um die letzten I2P Aktualisierungen bekommen zu können. </p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 aktiviert die neue Verschlüsselung</summary></details><p>0.9.47 aktiviert das neue Ende-zu-Ende Verschlüsselungsprotokoll (Vorschalg 144) als Standard für einige Services.
Das Sybil Analyse- und Blockierungsprogramm ist nun standardmässig aktiviert.</p>
<p>Java 8 oder höher ist nun notwendig.
Debian Pakete für Wheezy und Stretch, als auch Pakete für Ubuntu Trusty und Precise werden nicht mehr unterstützt oder zur Verfügung gestellt.
BenutzerInnen dieser Plattformen sollten diese aktualisieren um die letzten I2P Aktualisierungen zu bekommen</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 enthält Fehlerkorrekturen</summary></details><p>0.9.46 enthält signifikante Performanceverbesserungen in der Streaming Bibliothek
Wir haben die Entwicklung der ECIES Verschlüsselung (Proposal 144) vervollständigt und es gibt jetzt eine Möglichkeit zur Aktivierung und testen dieser.</p>
<p>Nur für Windows AnwenderInnen:
Diese Version behebt eine lokale Privilegieneskalation welche von einem lokalen Nutzer ausgenutzt werden konnte.
Bitte spielen Sie dieses Update so schnell wie möglich ein.
Vielen Dank an Blaze Infosec fürs verantwortungsbewusste Melden der Schwachstelle.</p>
<p>Dieses ist die letzt Version mit Java 7 Support, Distributionspakete für Debian Wheezy und Stretch, Ubuntu Precise und Trusty.
AnwenderInnen dieser Plattformen sollten diese Upgraden um zukünftige I2P Versionen zu erhalten.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 enthält Fehlerkorrekturen</summary></details><p>0.9.45 enthält wichtige Korrekturen für den "Versteckten Modus" und dem Bandbreitentester.
Es gibt eine Aktualisierung für das dunkle Konsolenthema.
Auch wurden die Arbeiten an Performanceverbesserungen weitergeführt und die Entwicklung der neuen Ende-zu-Ende Verschlüsselung (Proposal 144).</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 mit Bug Fixes</summary></details><p>0.9.44 beinhaltet ein wichtiges Fix für eine Denialof Service Problem innerhalb der internen Dienste, bei denen neue Verschlüsselungsalgorythmen eingesetzt werden. Alle User sollten so schnell wie möglich updaten! </p>
<p>Die Veröffentlichung beinhaltet initialen Support für neue Ende-zu-Ende Verschlüsselung (proposal 144). Die Arbeit an diesem Projekt geht weiter und es ist noch nicht einsatzbereit. Es gibt Änderung an der Homepage der Konsole und neue eingebettete HTML5 Media Player in i2psnark. Darüber hinaus gehende Korrekturen an firewalled IPv6 Netzwerken sind eingeschlossen. Korrekturen beim Aufbau der Tunnel sollten sich für einige User in einem schnelleren Aufbau bemerkbar machen. </p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 mit Fehlerkorrekturen</summary></details><p>In der 0.9.43 Version wird die Arbeit an starker Verschlüsselung, Privacy Funktionen und Performance Verbesserungen. weitergeführt.
Unsere Implementation der neuen LeaseSet Spezifikation (LS2) ist jetzt komplett.
Wir beginnen somit unsere Implementierung der schnelleren und stärkeren Ende-zu-Ende Verschlüsselung (Proposal 144) für eine zukünftige Version.
Diverse IPv6 Adressen Detektierungen wurden Fehlerbereinigt und natürlich wurden weitere Fehler behoben.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 mit Fehlerkorrekturen</summary></details><p>Version 0.9.42 ist ein weiterer Schritt auf dem Weg, I2P schneller und zuverlässiger zu machen.
Es gab mehrere Änderungen, um UDP-Übertragungen zu beschleunigen.
Wir haben die Konfigurationsdateien aufgeteilt, um in Zukunft die Paketierung modularer gestalten zu können.
Wir arbeiten weiterhin daran, neue Ansätze für schnellere und sicherere Verschlüsselung einzubauen.
Selbstverständlich gibt es auch viele Fehlerkorrekturen.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 mit Fehlerkorrekturen</summary></details><p>Mit der 0.9.41 setzen wir die Arbeit an an Vorschlag 123 fort,
mit Authentifizierung pro Client bei verschlüsselten Leasesets.
Die Konsole hat ein aktuelles I2P-Logo und mehrere neue Icons.
Wir haben das Linux-Installationsprogramm aktualisiert.</p>
<p>Der Start sollte auf Platformen wie dem Raspberry Pi schneller sein.
Wir haben mehrere Fehler behoben, darunter einige sehr gravierende, die Low-Level-Netzwerkmeldungen betrafen.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 mit neuen Icons</summary></details><p>0.9.40 bringt Unterstützung für das neue, verschlüsselte Leaseset-Format.
Wir haben das alte Transportprotokoll NTCP 1 deaktiviert.
Bei SusiDNS gibt es eine neue Import-Funktion und einen neuen, Skript-basierten Filtermechanismus für eingehende Verbindungen.</p>
<p>Wir haben große Fortschritte bei der nativen OSX-Installation gemacht, und wir haben die IzPack-Installation ebenfalls aktualisiert.
Weiterhin wird die Konsole durch neue Icons aufgefrischt.
Wie üblich haben wir auch viele Fehler behoben!</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 mit Performanceverbesserungen</summary></details><p>0.9.39 enthält weitreichende Veränderungen für die neuen Typen der Netzwerkdatenbank (Proposal 123).
Wir bündeln das I2PControl Plugin als eine WebApplikation zur Unterstützung der Entwicklung von RPC Anwendungen.
Desweiteren gibt es zahlreiche Performanceverbesserungen und Fehlerbehebungen. </p>
<p>Die Midnight und Classic Themen wurden zur Verbesserung der Wartungsfreundlichkeit entfernt;
Nutzer dieser Themes werden nun das dark oder light Theme sehen.
Auch gibt es neue Homepage Icons als ersten Schritt zur Aktualisierung der Konsole.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 mit neuem Installationsassistenten</summary></details><p>0.9.38 enthält einen neuen Assistenten zur Erstinstallation und mit Bandbreiten-Tester.
Wir haben Unterstützung für das neueste GeoIP-Datenbankformat eingebaut.
Es gibt ein neues Installationsprogramm für Firefox-Profile und ein neues, natives Installationsprogramm für Mac OSX auf unserer Webseite.
Die Arbeiten zur Unterstützung des neuen NetDB-Format "LS2" dauern an.</p>
<p>Diese Version behebt auch viele Fehler, darunter mehrere Probleme mit Susimail-Anhängen und eines mit Nur-IPv6-Routern.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="Bericht vom 35C3-Besuch" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P beim 35C3</summary></details><p>Die meisten Mitglieder des I2P-Teams waren beim 35C3 in Leipzig anwesend.
Bei täglichen Treffen wurden das vergangene Jahr sowie unsere Entwicklungs- und Designziele für 2019 besprochen.</p>
<p>Die Projektübersicht und der neue Entwicklungsplan können <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">hier</a> begutachtet werden.</p>
<p>Wir arbeiten weiter an LS2, dem Testnet und an Benutzbarkeitsverbesserungen für unsere Website und die Konsole.
Es ist geplant, in Tails, Debian und Ubuntu Disco zu sein. Wir brauchen noch Leute, die Fehler an Android und I2P_Bote beheben.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 mit aktiviertem NTCP2</summary></details><p>0.9.37 aktiviert das schnellere, sicherere Transportprotokoll namens NTCP2.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 mit NTCP2 und Fehlerkorrekturen</summary></details><p>0.9.36 führt ein neues, sichereres Transportprotokoll namens NTCP2 ein.
Es ist standardmäßig deaktiviert, kann aber zum Testen eingeschaltet werden, indem man in der <a href="/configadvanced">erweiterten Konfiguration</a> <tt>i2np.ntcp2.enable=true</tt> setzt und neu startet.
NTCP2 wird in der kommenden Version standardmäßig aktiv sein.</p>
<p>Diese Version enthält auch mehrere Geschwindigkeitsverbesserungen und Fehlerkorrekturen.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 mit Ordnern in SusiMail und einem SSL-Assistenten</summary></details><p>0.9.35 fügt Unterstützung für E-Mail-Ordner in SusiMail hinzu sowie einen neuen SSL-Assistenten zum Einrichten von HTTPS für deine versteckte Website.
Ansonsten wurden wie üblich jede Menge Fehler, besonders in SusiMail, behoben.</p>
<p>Wir arbeiten weiter hart an diversen Verbesserungen für 0.9.36, inklusiv einem neuem OSX Installer und einem schnelleren, sichreren Transportprotokoll, welches sich NTCP2 nennt.</p>
<p>I2P wird auf der HOPE Konferenz in New York City, vom 20. bis zum 22. July, sein. Finden Sie und und sagen Sie uns Hallo!</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 enthält Fehlerkorrekturen</summary></details><p>0.9.34 enthält viele Fehlekorrekturen!
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 enthält Fehlerkorrekturen</summary></details><p>0.9.34 enthält viele Fehlerkorrekturen!
Diese Version verbessert ausserdem SusiMail, das Arbeiten mit IPv6 und die Auswahl der Tunnelteilnehmer.
In UPnP wurde Unterstützung für IGD2 implementiert.
Desweiteren wurden Vorbereitungen für weitere Verbesserungen implementiert, die in den nächsten Versionen aufscheinenwerden.</p>
Für UPnP wurde Unterstützung von IGD2 implementiert.
Außerdem wurden Vorbereitungen für weitere Verbesserungen implementiert, die in die nächsten Versionen einfließen werden.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 mit Fehlerkorrekturen</summary></details><p>0.9.33 enthält eine große Anzahl an Fehlerkorrekturen, unter anderen für I2PSnark, I2PTunnel, Streaming und SusiMail.
Für diejenigen, die die Reseed Server nicht direkt erreichen können, unterstützen wir jetzt diverse Arten von Proxies zum reseeden.
Jetzt setzen wir auch standardmässig die Zugriffslimits im Hidden Service Manager.
Falls Sie einen Server mit hoher Bandbreite betreiben, kontrollieren Sie bitte diese Limits und passen Sie diese ggf. an.</p>
<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown und Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Sicherheits Probleme in nahezu jedem System gefunden</summary></details><p>Ein sehr gravierendes Problem wurde in modernen CPUS gefunden, welches nahezu alle verkauften Computer und Mobilgeräte betrifft.
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown und Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Sicherheitsprobleme in nahezu jedem System gefunden</summary></details><p>Ein sehr gravierendes Problem wurde in modernen CPUS gefunden, welches nahezu alle verkauften Computer und Mobilgeräte betrifft.
Diese Probleme wurden "Kaiser", "Meltdown" und "Spectre" benannt.</p>
<p>Das Whitepaper zu KAISER/KPTI kann under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a> gelesen werden, Meltdown unter <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, und SPECTRE unter <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels erste Reaktion ist auf <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels Anwort</a>zu finden.</p>
<p>Für unsere I2P Nutzer ist es wichtig, aktuelle Updates einzuspielen und das System aktuell zu halten. Patches für Windows 10 existieren bereits, Windows 7 und 8 werden rasch folgen. Ebenso gibt es schon Patches für MacOS. Für viele Linux Systeme existieren schon aktuelle Kernel Pakete mit den nötigen Fixes, ebenso für Android, der Security Fix vom 2. Januar 2018 enthält den nötigen Fix.

View File

@ -0,0 +1,574 @@
<div>
<header title="Νέα I2P">Ροή νέων, και ενημέρωσης δρομολογητών </header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="Η έκλδοση 0.9.50 Κυκλοφόρησε " href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>Έκδοση 0.9.50 και βελτιώσεις σχετικά με IPv6</summary></details><p>Η έκδοση 0.9.50 συνεχίζει με την μετάβαση σε ECIES-X25519 για τα κλειδιά κρυπτογράφησης των δρομολογητών.
Ενεργοποιήσαμε την δυνατότητα DNS μέσω HTTPS για επαναδιασπορά προκειμένου να προστατεύσουμε τους χρήστες απο παθητηκή κατασκοπεία DNS.
Υπάρχουν πολλές διορθώσεις και βελτιώσεις για τις IPv6 διευθύνσεις, συμπεριλαμβανομένης της νέας υποστήριξης UPnP.</p>
<p>Φιάξαμε επιτέλους κάποια επίμονα σφάλματα διαφθοράς του SusiMail.
Ευελπιστούμε οι αλλαγές στον περιοριστή του bandwidth βελτιώσουν την απόδωση της σήραγγας δυκτίου.
Πραγματοποιήθηκαν μερικές βελτιώσεις στους Docker containers μας.
Βελτιώσαμε τις άμυνές μας για πιθανούς κακόβουλους και προβληματικούς δρομολογητές εντός του δικτύου</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="Η έκδοση 0.9.49 Κυκλοφόρησε " href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>Έκδοση 0.9.49 και βελτιώσεις SSU για γρηορότερη κρυπτογράφηση</summary></details><p>Στην έκδοση 0.9.49 συνεχίζουμε την δουλειά προκειμένου να κάνουμε το I2P γρηγορότερο και ασφαλέστερο
Έχουμε κάνει μερικές βελτιώσεις και διορθώσεις για την SSU (UDP) μεταφορά οι οποίες ευελπιστούμε να οδηγήσουν σε μεγαλύτερες ταχύτητες.
Σε αυτή την έκδοση ξεκινήσαμε την ενσωμάτωση της καινούριας, γρηγορότερης ECIES-X25519 κρυπτογράφησης για τους δρομολογητές.
(Προορισμοί χρησιμοποιούν την συγκεκριμένη κρυπρογράφηση εδώ και μερικές εκδώσεις)
Δουλεύουμε τις προδιαγραφές και τα προτόκολα για την νέα κρυπτογράφηση εδώ και μερικά χρόνια,
και βρισκόμαστε κοντά στην τελειοποίησή τους. Αυτή ενσωμάτωση θα χρειαστεί μερικές εκδώσεις προκειμένου να ολοκληρωθεί.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Κυκλοφόρησε " href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 με διορθώσεις δυσλειτουργιών </summary></details><p>0.9.44 περιέχει μια σημαντική διόρθωση για ένα θέμα άρνησης υπηρεσίας στις κρυφές υπηρεσίες που χειρίζονται νέους τύπους κρυπτογράφησης.
Όλοι οι χρήστες πρέπει να κάνουν ενημέρωση το συντομότερο δυνατό. </p>
<p>Η κυκλοφορία περιέχει βασική υποστήριξη στην νέα κρυπτογράφηση από άκρο σε άκρο (πρόταση 144).
Η δουλειά συνεχίζεται στο έργο,και δεν είναι ακόμα έτοιμο για χρήση.
Υπάρχουν αλλαγές στην κονσόλα αρχικής σελίδας, και νέα ενσωματωμένα HTML5 media players στο i2psnark.
Πρόσθετες διορθώσεις για δίκτυα IPv6 μέσα από τοίχοι ασφαλείας συμπεριλαμβάνονται.
Διορθώσεις στον σχηματισμό τούνελ πρέπει να αποτελέσουνε σε γρηγορότερη εκκίνηση για κάποιος χρήστες.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
it if you could set aside a little more time than usual during this release cycle
in order to bring the translations up to speed. We have pushed the strings early
to give you three weeks to work on them.</p>
<p>If you're not currently an I2P translator, now would be a great time to get
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
<p>Several plugins are not compatible with Jetty 9 and must be updated.
The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
i2pbote 0.4.6; zzzot 0.15.0.
The following plugins (with current versions listed) will not work with 0.9.30.
Contact the appropriate plugin developer for the status of new versions:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contains bug fixes</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
for this.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
which will speed up crypto operations considerably.
Also, we are now using constant-time GMP functions to prevent side-channel attacks.
For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
we will include them for in-net updates in the 0.9.27 release.</p>
<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
<p>There's a collection of bug fixes also, including a fix for a timer bug
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contains SAM 3.3, QR codes, and bug fixes</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
It adds QR codes for sharing hidden service addresses with others,
and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
to make it easier to declare that your group of routers is run by a single person.
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
Your router will not automatically update if you are using Java 6.</p>
<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration,
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
<p><b>Housekeeping</b></p>
<p>My signing key has been in router updates for over two years (since 0.9.9), so
if you are on a recent version of I2P this update should be just as easy as
every other update. However, if you are running an older version than 0.9.9, you
will first need to manually update to a recent version. Update files for recent
versions can be downloaded
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
and instructions on how to manually update are provided
<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
updated, your router will then find and download the 0.9.23 update as usual.</p>
<p>If you installed I2P via a package manager, you are not affected by the change,
and can update as usual.</p>
<p><b>Update details</b></p>
<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
with at least half of the network already estimated to have rekeyed. This
release accelerates the rekeying process. To reduce network churn, your router
will have a small probability of converting to Ed25519 at each restart. When it
does rekey, expect to see lower bandwidth usage for a couple of days as it
reintegrates into the network with its new identity.</p>
<p>Note that this will be the last release to support Java 6. Please update to
Java 7 or 8 as soon as possible. We are already working to make I2P compatible
with the upcoming Java 9, and some of that work is in this release.</p>
<p>We have also made some minor improvements in I2PSnark, and added a new page in
the routerconsole for viewing older news items.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
and use bandwidth more effectively.
We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
using the new "multisession" capability for those sites that don't support ECDSA.</p>
<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto speakers and schedule announced" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 speakers and schedule announced</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -1,8 +1,390 @@
<div>
<header title="Noticias de I2P">Suscripción (feed) de noticias, y actualizaciones del router I2P</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<header title="Noticias de I2P">Suscripción (feed) de noticias, y actualizaciones del router I2P</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="Versión 2.8.2 Disponible" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>Versión 2.8.2 Disponible</summary></details><p>La versión 2.8.2 corrige un error que causaba fallos de SHA256 que se introdujo en la versión 2.8.1.
El error afectaba principalmente a los enrutadores de alto ancho de banda.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="Versión 2.8.1 Disponible" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>Lanzamiento de I2P 2.8.1</summary></details><p>La versión 2.8.1 corrige los accesos a sitios locales que se rompieron en 2.8.0.
Hemos añadido burbujas de notificación a varias aplicaciones en la consola para destacar los mensajes de la aplicación.
Hemos corregido un error en la prueba del túnel que podría haber estado afectando a la fiabilidad del túnel.
La libreta de direcciones ahora tiene una nueva pestaña "última" que muestra los nombres de host más recientes añadidos de tus suscripciones.
Hay varias correcciones y mejoras en el tema oscuro.</p>
<p>Arreglamos el instalador que antes fallaba en Java 21 o superior.
También arreglamos la instalación en rutas de directorio que contienen espacios en Linux.
Para los que usáis Docker, actualizamos el contenedor de Docker y las librerías de contenedor que estaban desactualizadas.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="El acceso al sitio local falla en 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Error de acceso local</summary></details><p>En la versión 2.8.0, navegar a un sitio local (ya sea por nombre de host o b32) fallará.
La solución alternativa es usar localhost y el puerto del servidor, generalmente 7658, para evitar I2P.
Por ejemplo, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
Pedimos disculpas por el problema y estamos trabajando en una solución.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="Lanzamiento de I2P 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>Lanzamiento de I2P 2.8.0</summary></details><p>Esta versión mejora I2P al corregir errores, eliminar código no utilizado y mejorar la estabilidad de la red.</p>
<p>Hemos mejorado el manejo de routers congestionados en la red.
Se abordaron problemas en UPnP y la transversalidad NAT para mejorar la conectividad y la notificación de errores.
Ahora tenemos una estrategia más agresiva para la eliminación de leasesets del NetDb con el fin de mejorar el rendimiento del router y mitigar la sobrecarga.
Se implementaron otros cambios para reducir la observabilidad de eventos como el reinicio o apagado de un router.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="Publicada la versión 2.7.0 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>Publicada la versión 2.7.0 de I2P</summary></details><p>Esta versión, I2P 2.7.0, continúa nuestro trabajo corrigiendo errores, mejorando el rendimiento y añadiendo funciones.</p>
<p>Se ha mejorado el acceso a la información desde la consola y las aplicaciones.
Se han solucionado problemas en I2PSnark y la búsqueda de SusiMail.
La búsqueda de netDB integrada en la consola del router ahora funciona de una manera más intuitiva y útil.
Se han realizado pequeñas mejoras en las pantallas de diagnóstico en modo avanzado.</p>
<p>También se han corregido errores para mejorar la compatibilidad dentro de la red.
Se resolvió un problema con la publicación de leaseSets, lo que mejora la fiabilidad de los servicios ocultos principales.
I2PSnark ya no cambia el infohash cuando un usuario solo modifica los trackers en un torrent existente.
Esto evita que los torrents se vean innecesariamente interrumpidos por estos cambios.
Damos la bienvenida a esta contribución de un nuevo colaborador.
Se resolvió un conflicto en el manejo de una opción de la biblioteca de streaming para mejorar la compatibilidad con otras implementaciones de I2P.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="Publicada la versión 2.6.1 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>Publicada la versión 2.6.1 de I2P</summary></details><p>I2P 2.6.1 se lanza para corregir un error en la interfaz de usuario de la aplicación Hidden Services Manager.
Este error deshabilitaba el desplazamiento, haciendo que algunas configuraciones fueran inaccesibles.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="Publicada la versión 2.6.0 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>Publicada la versión 2.6.0 de I2P</summary></details><p>Esta versión, I2P 2.6.0, continúa nuestro trabajo al corregir errores, agregar funciones y mejorar la fiabilidad de la red.</p>
<p>Se favorecerán los routers más nuevos al seleccionar routers floodfill.
I2PSnark recibió funciones que mejoran el rendimiento de PeX (Intercambio de Pares), además de correcciones de errores.
Se están eliminando los protocolos de transporte heredados, simplificando el código en los transportes UDP.
Los destinos alojados localmente serán accesibles para los clientes locales sin solicitar su LeaseSet, mejorando el rendimiento y la capacidad de prueba.
Se realizaron ajustes adicionales en las estrategias de selección de pares.</p>
<p>I2P ya no permite I2P-sobre-Tor, las conexiones desde direcciones IP de salida de Tor ahora están bloqueadas.
Desalentamos esto porque degrada el rendimiento de I2P y consume los recursos de las salidas de Tor sin ningún beneficio.
Si eres una persona solidaria que opera tanto una salida de Tor como I2P, te animamos a continuar haciéndolo, utilizando direcciones IP diferentes para cada uno.
Los relés no de salida y los clientes de Tor no se ven afectados por esto y no necesitan cambiar nada.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="Publicada la versión 2.5.2 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 con corrección de HTTP</summary></details><p>Se publica I2P 2.5.2 para corregir un error introducido en 2.5.0 que provocaba el truncamiento de algunos contenidos HTTP.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="Publicada la versión 2.5.1 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>Lanzamiento de la versión 2.5.1 de I2P para hacer frente a los ataques de denegación de servicio</summary></details><p>"I2P 2.5.1 se ha lanzado para abordar los ataques de Denegación de Servicio que afectan a la red y los servicios de I2P.
Con este lanzamiento, deshabilitamos las partes basadas en IP de la herramienta de detección de ataques Sybil, que estaban dirigidas a amplificar el efecto y la duración del ataque.
Esto debería ayudar a que la red vuelva a la operación normal.
Aquellos de ustedes que han deshabilitado la herramienta de detección de ataques Sybil pueden volver a habilitarla de forma segura.
También se han realizado ajustes en otros subsistemas para mejorar la validación de RouterInfo y la selección de pares."</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Clima tormentoso." href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Clima de la red: Tormentoso. I2P está bajo ataque.</summary></details><p>La red I2P está actualmente bajo un ataque de Denegación de Servicio.
Este ataque afecta a I2P e i2pd, pero de diferentes maneras, y está teniendo un efecto grave en la salud de la red.
La accesibilidad de los sitios de I2P está gravemente degradada.</p>
<p>Si estás alojando un servicio dentro de I2P y está alojado en un router Floodfill, deberías considerar alojar el servicio también en un router con Floodfill deshabilitado para mejorar la accesibilidad.
Se están discutiendo otras mitigaciones, pero todavía se está trabajando en una solución a largo plazo y compatible con versiones anteriores.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="Nueva versión I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>Más mejoras de aplicaciones, auditoría de la estrategia de aislamiento de NetDB.</summary></details><p>Esta versión, I2P 2.5.0, ofrece más mejoras orientadas al usuario que la versión 2.4.0, que se centró en implementar la estrategia de aislamiento de NetDB.</p>
<p>Se han añadido nuevas funciones a I2PSnark, como la capacidad de buscar a través de torrents.
Se han corregido errores para mejorar la compatibilidad con otros clientes de torrents de I2P, como BiglyBT y qBittorrent.
Nos gustaría agradecer a todos los desarrolladores que han trabajado con libtorrent y qBittorrent para habilitar y mejorar su soporte para I2P.
También se han añadido nuevas funciones a SusiMail, incluyendo soporte para el formato Markdown en correos electrónicos y la capacidad de arrastrar y soltar archivos adjuntos en correos electrónicos.
Los túneles creados con el administrador de Servicios Ocultos ahora soportan "Keepalive", lo que mejora el rendimiento y la compatibilidad con tecnologías web, permitiendo sitios I2P más sofisticados.</p>
<p>Durante esta versión también realizamos varios ajustes en la NetDB para mejorar su resistencia al spam y la capacidad del router para rechazar mensajes sospechosos.
Esto fue parte de un esfuerzo por "auditar" la implementación de las defensas de "aislamiento de Sub-DB" de la versión 2.4.0.
Esta investigación descubrió un evento menor que rompía el aislamiento, el cual reparamos.
Este problema fue descubierto y solucionado internamente por el equipo de I2P.</p>
<p>Durante esta versión se realizaron varias mejoras en el proceso de lanzamiento de nuestras distribuciones downstream para Android y Windows.
Esto debería resultar en una mejor entrega y disponibilidad de estos productos downstream.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="Lanzamiento de I2P 2.4.0 con mejoras en la congestión y la seguridad de NetDB." href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>Lanzamiento de I2P 2.4.0 con mejoras en la congestión y la seguridad de NetDB.</summary></details><p>Esta versión, I2P 2.4.0, continúa nuestro esfuerzo por mejorar la seguridad y estabilidad de la red I2P.
Contiene mejoras significativas en la Base de Datos de la Red, una estructura esencial dentro de la red I2P utilizada para descubrir a tus pares.</p>
<p>Los cambios en la gestión de la congestión mejorarán la estabilidad de la red al dar a los enrutadores la capacidad de aliviar a los pares congestionados evitándolos.
Esto ayudará a la red a limitar el efecto del spam de túneles.
También ayudará a la red a recuperarse durante y después de los ataques DDOS.</p>
<p>Los cambios en NetDb también ayudan a proteger los routers individuales y las aplicaciones que los utilizan.
Los routers ahora pueden defenderse contra atacantes separando el NetDB en múltiples "Sub-DB's", que usamos para prevenir fugas de información entre las aplicaciones y el router.
Esto también mejora la información disponible para los routers Java sobre su actividad en NetDB y simplifica nuestro soporte para aplicaciones multihoming.</p>
<p>También se incluyen una serie de correcciones de errores y mejoras en las aplicaciones I2PSnark y SusiMail.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:" title="Nuevo lanzamiento I2P 2.3.0 - Correcciones de seguridad, listas de bloqueo ajustables, API DTG." href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Correcciones de seguridad, listas de bloqueo ajustables, API DTG</summary></details><p>Esta versión contiene correcciones para CVE-2023-36325.
CVE-2023-36325 es un error de confusión de contexto que ocurrió en el filtro de Bloom.
Un atacante elabora un mensaje I2NP que contiene un messageID único y envía ese messageID a un cliente.
El mensaje, después de pasar por el filtro de Bloom, no se permite reutilizar en un segundo mensaje.
El atacante luego envía el mismo mensaje directamente al enrutador.
El enrutador pasa el mensaje al filtro de Bloom y se descarta.
Esto filtra la información de que el messageID se ha visto antes, dando al atacante una fuerte razón para creer que el enrutador está alojando al cliente.
Esto se ha solucionado separando la funcionalidad del filtro de Bloom en diferentes contextos según si un mensaje provino de un túnel de cliente, un túnel exploratorio o se envió directamente al enrutador.
Bajo circunstancias normales, este ataque tarda varios días en realizarse con éxito y puede verse afectado por varios factores, como el reinicio de enrutadores durante la fase de ataque y la sensibilidad a falsos positivos.
Se recomienda a los usuarios de Java I2P que actualicen de inmediato para evitar el ataque.</p>
<p>En el proceso de solucionar este error de confusión de contexto, hemos revisado algunas de nuestras estrategias para programar de manera defensiva contra este tipo de fugas.
Esto incluye ajustes en el netDb, los mecanismos de limitación de velocidad y el comportamiento de los routers floodfill.</p>
<p>Esta versión añade not_bob como un segundo proveedor de hosts predeterminado, y añade <a href="http://notbob.i2p">notbob.i2p</a> y <a href="http://ramble.i2p">ramble.i2p</a> a la página de inicio de la consola.</p>
<p>Esta versión también contiene una lista de bloqueo ajustable.
El bloqueo es semipermanente, cada dirección IP bloqueada normalmente permanece bloqueada hasta que se reinicia el router.
Los usuarios que observen un crecimiento explosivo de la lista de bloqueo durante ataques Sybil pueden optar por tiempos de espera más cortos configurando la lista de bloqueo para que las entradas expiren en un intervalo.
Esta función está desactivada por defecto y solo se recomienda para usuarios avanzados en este momento.</p>
<p>Esta versión también incluye una API para que los complementos se modifiquen con la interfaz gráfica de escritorio (DTG).
Ahora es posible agregar elementos al menú de la bandeja del sistema, lo que permite un lanzamiento más intuitivo de los complementos que utilizan interfaces de aplicaciones nativas.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="Nueva versión 2.2.1, correcciones de empaquetado para Docker, Ubuntu Lunar y Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - versión de mantenimiento para 2.2.0</summary></details><p>Después del lanzamiento de I2P 2.2.0, que se adelantó para acelerar las mitigaciones de los ataques DDOS, nos enteramos de algunos problemas en desarrollo que hicieron necesario construir y lanzar nuevos paquetes.
Esta versión soluciona un problema en Ubuntu Lunar y Debian Sid por el que no se podía acceder a la consola del router utilizando una versión actualizada del paquete jakarta.
Los paquetes Docker no leían los argumentos correctamente, lo que resultaba en archivos de configuración inaccesibles.
Este problema también se ha resuelto.
El contenedor Docker ahora también es compatible con Podman.</p>
<p>Esta versión sincroniza las traducciones con transifex y actualiza la base de datos GeoIP.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="Nueva versión 2.2.0. Mitigación de los ataques DDoS y ajustes del subsistema de streaming." href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigación de ataques DDoS y ajustes del subsistema de streaming</summary></details><p>Hemos decidido adelantar la fecha de lanzamiento de la versión 2.2.0, que tendrá lugar hoy, 13 de marzo de 2023.Esta versión incluye cambios en los componentes NetDB, Floodfill y Peer-Selection que mejoran la capacidad del router para sobrevivir a ataques DDOS.Es probable que los ataques continúen, pero las mejoras en estos sistemas ayudarán a mitigar el riesgo de ataques DDOS al ayudar al router a identificar y quitar prioridad a los routers que parezcan maliciosos.</p>
<p>Esta versión también añade protección contra repeticiones al subsistema de streaming, lo que impide que un atacante que pueda capturar un paquete cifrado pueda reutilizarlo enviándolo a destinatarios no deseados.Se trata de un cambio compatible con versiones anteriores, por lo que los routers más antiguos podrán seguir utilizando las funciones de streaming de los routers más recientes.Este problema fue descubierto y solucionado internamente por el equipo de desarrollo de I2P y no está relacionado con los ataques DDoS.Nunca hemos encontrado un paquete de streaming reproducido en la naturaleza y no creemos que un ataque de repetición de streaming haya tenido lugar contra la red I2P en este momento.</p>
<p>Como habréis notado, estas notas de publicación y la propia publicación han sido firmadas por idk, y no por zzz.zzz ha decidido alejarse del proyecto y sus responsabilidades están siendo asumidas por otros miembros del equipo.Por ello, el proyecto está trabajando en la sustitución de la infraestructura de estadísticas de red y en el traslado del foro de desarrollo a i2pforum.i2p.Agradecemos a zzz que haya prestado estos servicios durante tanto tiempo.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="Actualización DDoS" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>Actualización DDoS</summary></details><p>Hemos confirmado que el atacante controla un gran número de routers.Nuestras investigaciones y mitigaciones continúan.</p>
<p>Es un buen momento para recordar que, incluso después de 20 años, la red I2P es relativamente pequeña.No tenemos pruebas de que el atacante esté intentando desanonimizar a ningún usuario en particular o servicio oculto.Sin embargo, si usted tiene un modelo de amenaza de alto riesgo, debería considerar cuidadosamente si I2P le proporciona actualmente la protección que necesita.La mejor solución, a largo plazo, es correr la voz y hacer crecer la red I2P para aumentar la seguridad de nuestros usuarios.</p>
<p>Proporcionaremos información adicional aquí en el feed de noticias y en <a href="http://zzz.i2p">zzz.i2p</a> según sea necesario.Le pedimos paciencia mientras trabajamos para mejorar I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="Acerca de los recientes ataques de denegación de servicio" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>La I2P permanece intacta con el rendimiento mermado</summary></details><p>La red I2P está siendo afectada por un ataque de denegación de servicio.La función floodfill de la red se ha visto afectada, lo que ha provocado la interrupción de las respuestas y el descenso de los índices de éxito en la construcción de túneles.Los participantes en la red han experimentado dificultades para conectarse a los sitios I2P y utilizar los servicios I2P.Se están investigando y aplicando gradualmente estrategias de mitigación.</p>
<p>Aunque el ataque ha degradado el rendimiento, la red sigue intacta y utilizable.Los enrutadores Java I2P parecen manejar los problemas mejor que los enrutadores i2pd por ahora.En la próxima semana deberían empezar a aparecer varias mitigaciones en las versiones de desarrollo de los routers Java y C++.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="Publicada la 2.1.0" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 con varias correcciones de SSU2</summary></details><p>Hemos aprendido muchas cosas desde el lanzamiento de la versión 2.0.0 en noviembre. A medida que los routers se han actualizad, la red ha pasado de aproximadamente el 1% a más del 60% a usar el nuevo protocolo de transporte SSU2. Primero, hemos confirmado que el protocolo SSU2 es sólido y seguro. En segundo lugar, sin embargo, hemos encontrado y corregido numerosos errores menores o raramente activados en la implementación del protocolo. Los efectos de estos errores se han acumulado, reducido el rendimiento de la red.</p>
<p>Además, somos conscientes del aumento del número de túneles y la reducción de la tasa de éxito en la construcción de túneles en la red,
posiblemente provocados por la nueva función de dirección transitoria I2P de Bitcoin,
pero empeorados por nuestros errores en SSU2 y otros problemas de control de congestión.
Estamos trabajando con Bitcoin y otros proyectos que no son de Bitcoin para reducir las demandas de la red I2P.
Hemos mejorado nuestros algoritmos para reducir la carga de la red durante tiempos de congestión.
También estamos colaborando con i2pd para desarrollar estrategias comunes de control de la congestión.</p>
<p>Por lo tanto, hemos acelerado este lanzamiento en unas seis semanas, para hacer llegar las correcciones a todo el mundo.
i2pd lanzó su versión 2.45.0 la semana pasada y los primeros resultados son alentadores.
Los nuevos protocolos y las redes distribuidas son difíciles de desarrollar.
La congestión puede llegar con poca advertencia y con pocas pistas de la causa.
Gracias por su paciencia, ya que hemos diagnosticado y, con suerte, solucionado los problemas.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="Lanzamiento de la versión 2.0.0" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>Transporte SSU2 habilitado</summary></details><p>La versión 2.0.0 de I2P habilita nuestro nuevo transporte UDP SSU2 para todos los usuarios, después de completar funciones menores, pruebas y numerosas correcciones de errores.</p>
<p>También tenemos correcciones en todas partes, incluso para el instalador, la base de datos de la red, la adición a la libreta de direcciones privada, el iniciador del navegador de Windows y UPnP IPv6.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Entradas recientes del blog" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Algunas publicaciones de blog recientes</summary></details><p>Aquí hay enlaces a varias publicaciones de blog recientes en nuestra web:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Descripción general sobre nuestro nuevo transporte SSU2</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">Advertencia sobre monedas I2P y otras estafas</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">Una entrevista con Konrad de diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">Una entrevista con Dustin de StormyCloud1</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="Lanzamiento de la versión 1.9.0" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 con SSU2 para pruebas</summary></details><p>Hemos pasado los últimos tres meses trabajando en nuestro nuevo protocolo de transporte UDP "SSU2"
con un pequeño número de probadores voluntarios.
Esta versión completa la implementación, incluyendo pruebas de retransmisión y de pares.
Lo estamos habilitando por defecto para las plataformas Android y ARM, y un pequeño porcentaje de otros routers al azar.
Esto nos permitirá hacer muchas más pruebas en los próximos tres meses, terminar la función de migración de conexiones
y solucionar cualquier problema restante.
Tenemos previsto habilitarla para todo el mundo en la próxima versión prevista para noviembre.
No es necesaria ninguna configuración manual.</p>
<p>Por supuesto, también hay la habitual colección de correcciones de errores en esta versión.
También hemos añadido un detector automático de bloqueos que ya ha encontrado un raro bloqueo que ya está solucionado.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="Nuevo Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>Nuevo Outproxy</summary></details><p>Los "outproxies" (nodos de salida) de I2P pueden utilizarse para acceder a Internet a través de
su túnel proxy HTTP.
Como se aprobó en nuestra <a href="http://i2p-projekt.i2p/en/meetings/314">reunión mensual</a>,
<b>exit.stormycloud.i2p</b> es ahora nuestro outproxy oficial y recomendado, sustituyendo al ya desaparecido <b>false.i2p</b>.
Para más información sobre la <a href="http://stormycloud.i2p/">organización</a> de StormyCloud
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
y los <a href="http://stormycloud.i2p/tos.html">términos del servicio</a>,
consulte el <a href="http://stormycloud.i2p/">sitio web de StormyCloud</a>.</p>
<p>Le sugerimos que cambie la configuración de su <a href="/i2ptunnel/edit?tunnel=0">Administrador de Servicios Ocultos</a>
para especificar <b>exit.stormycloud.i2p</b>
en dos lugares: <b>Outproxies</b> y <b>SSL Outproxies</b>.
Después de editar, <b>desplácese hacia abajo y haga clic en Guardar</b>.
Ver nuestra <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">entrada de blog para una captura de pantalla</a>.
Para las instrucciones de Android y capturas de pantalla ver el <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">blog de notbob</a>.</p>
<p>Las actualizaciones del router no actualizarán su configuración, deberá editarla manualmente.
Gracias a StormyCloud por su apoyo, y por favor considere una <a href="http://stormycloud.i2p/donate.html">donación</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 con correcciones de errores</summary></details><p>Esta versión incluye correcciones de errores en i2psnark
el router, I2CP, y UPnP.
Las correcciones del router abordan errores en el reinicio suave, IPv6, pruebas de pares SSU
los almacenes de la base de datos de la red, y la construcción de túneles.
El manejo de la familia del router y la clasificación Sybil también han sido
mejorado significativamente.</p>
<p>Junto con i2pd, estamos desarrollando nuestro nuevo transporte UDP, SSU2.
SSU2 aportará mejoras sustanciales de rendimiento y seguridad.
También nos permitirá reemplazar finalmente nuestro último uso de la lentísima encriptación ElGamal,
completando la actualización completa de la criptografía que comenzamos hace unos 9 años.
Esta versión contiene una implementación preliminar que está desactivada por defecto.
Si desea participar en las pruebas, por favor busque la información actual
en zzz.i2p.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Instalar las actualizaciones esenciales de Java/Jpackage" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>La reciente vulnerabilidad de Java "Psychic Signatues" afecta a I2P. Los usuarios actuales de
I2P en Linux, o cualquier usuario de I2P que esté utilizando una JVM no empaquetada debería actualizar
su JVM o cambiar a una versión que no contenga la vulnerabilidad, por debajo de Java 15.</p>
<p>Se han generado nuevos paquetes I2P Easy-Install utilizando la última versión de la
máquina virtual Java. Se han publicado más detalles en las respectivas
fuentes de noticias de los paquetes.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 con mejoras de fiabilidad y rendimiento</summary></details><p>La versión 1.7.0 contiene varias mejoras de rendimiento y fiabilidad.</p>
<p>Ahora hay mensajes emergentes en la bandeja del sistema, para aquellas plataformas que lo soportan.
i2psnark tiene un nuevo editor de torrents.
El transporte NTCP2 ahora usa mucho menos CPU.</p>
<p>La interfaz BOB, obsoleta desde hace tiempo, se elimina para las nuevas instalaciones.
Seguirá funcionando en las instalaciones existentes, excepto en los paquetes de Debian.
Los usuarios que sigan utilizando las aplicaciones BOB deberían pedir a los desarrolladores que se conviertan al protocolo SAMv3.</p>
<p>Sabemos que desde nuestro lanzamiento de la versión 1.6.1, la fiabilidad de la red se ha deteriorado constantemente.
Nos dimos cuenta del problema poco después del lanzamiento, pero tardamos casi dos meses en encontrar la causa.
Finalmente lo identificamos como un error en i2pd 2.40.0,
y la solución estará en su versión 2.41.0 que saldrá aproximadamente al mismo tiempo que esta versión.
En el camino, hemos hecho varios cambios en el lado de Java I2P para mejorar la
robustez de las búsquedas y almacenes de la base de datos de la red, y evitar los pares de bajo rendimiento en la selección de pares del túnel.
Esto debería ayudar a que la red sea más robusta incluso en presencia de routers con errores o maliciosos.
Además, estamos iniciando un programa conjunto para probar los routers i2pd y Java I2P
juntos en una red de prueba aislada, para que podamos encontrar más problemas antes de los lanzamientos, no después.</p>
<p>En otras noticias, seguimos avanzando mucho en el diseño de nuestro nuevo transporte UDP "SSU2" (propuesta 159)
y hemos empezado a implementarlo.
SSU2 aportará mejoras sustanciales de rendimiento y seguridad.
También nos permitirá reemplazar finalmente nuestro último uso del lentísimo cifrado ElGamal,
completando una actualización completa de la criptografía que comenzó hace unos 9 años.
Esperamos comenzar pronto las pruebas conjuntas con i2pd, y extenderlo a la red a finales de este año.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 habilita nuevos mensajes de construcción de túneles</summary></details><p>Esta versión completa el despliegue de dos importantes actualizaciones de protocolo desarrolladas en 2021.
Se acelera la transición al cifrado X25519 para los enrutadores, y esperamos que casi todos los enrutadores se vuelvan a cifrar a finales de año.
Se habilitan los mensajes de construcción de túneles cortos para una importante reducción del ancho de banda.</p>
<p>Hemos añadido un panel de selección de temas al nuevo asistente de instalación.
Hemos mejorado el rendimiento de SSU y solucionado un problema con los mensajes de prueba de pares de SSU.
Se ajustó el filtro Bloom de construcción de túneles para reducir el uso de memoria.
Hemos mejorado la compatibilidad con los plugins que no son de Java.</p>
<p>En otras noticias, estamos avanzando de forma excelente en el diseño de nuestro nuevo transporte UDP SSU2 y esperamos empezar a implementarlo a principios del año que viene.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 con nuevos mensajes de construcción de túneles</summary></details><p>Sí, así es, después de 9 años de versiones 0.9.x, vamos a pasar directamente de 0.9.50 a 1.5.0.
Esto no significa un cambio importante en la API, ni una afirmación de que el desarrollo haya terminado.
Es simplemente un reconocimiento a casi 20 años de trabajo para proporcionar anonimato y seguridad a nuestros usuarios.</p>
<p>Esta versión finaliza la implementación de mensajes de construcción de túneles más pequeños para reducir el ancho de banda.
Continuamos la transición de los routers de la red al cifrado X25519.
Por supuesto, también hay numerosas correcciones de errores y mejoras de rendimiento.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Vulnerabilidad en MuWire Desktop" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Vulnerabilidad de Muwire Desktop</summary></details><p>Se ha descubierto una vulnerabilidad de seguridad en la aplicación de escritorio independiente de MuWire.
No afecta al plugin de la consola, y no está relacionado con el problema del plugin anunciado anteriormente.
Si está ejecutando la aplicación de escritorio de MuWire debe <a href="http://muwire.i2p/">actualizar a la versión 0.8.8</a> inmediatamente.</p>
<p>Los detalles de la emisión se publicarán en <a href="http://muwire.i2p/security.html">muwire.i2p</a>
el 15 de julio de 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Vulnerabilidad del plugin MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Vulnerabilidad del plugin Muwire</summary></details><p>Se ha descubierto una vulnerabilidad de seguridad en el plugin MuWire.
No afecta al cliente de escritorio independiente.
Si está ejecutando el plugin MuWire debe <a href="/configplugins">actualizar a la versión 0.8.7-b1</a> inmediatamente.</p>
<p>Consulte <a href="http://muwire.i2p/security.html">muwire.i2p</a>
para obtener más información sobre la vulnerabilidad y las recomendaciones de seguridad actualizadas.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="Lanzamiento de la versión 0.9.50" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 con correcciones de IPv6</summary></details><p>0.9.50 continúa la transición a ECIES-X25519 para las claves de cifrado del router.
Hemos habilitado el DNS sobre HTTPS para la resiembra con el fin de proteger a los usuarios del snooping pasivo de DNS.
Hay numerosas correcciones y mejoras para las direcciones IPv6, incluida la nueva compatibilidad con UPnP.</p>
<p>Por fin hemos corregido algunos errores de corrupción de SusiMail que se producían desde hace tiempo.
Los cambios en el limitador de ancho de banda deberían mejorar el rendimiento del túnel de red.
Hay varias mejoras en nuestros contenedores Docker.
Hemos mejorado nuestras defensas para posibles routers maliciosos y con errores en la red.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 con correcciones de SSU y criptografía más rápida</summary></details><p>La versión 0.9.49 continúa el trabajo para hacer que I2P sea más rápido y seguro.
Tenemos varias mejoras y correcciones para el transporte SSU (UDP) que deberían resultar en velocidades más rápidas.
Esta versión también inicia la migración al nuevo y más rápido cifrado ECIES-X25519 para los routers.
(Los destinos llevan utilizando este cifrado desde hace varias versiones)
Llevamos varios años trabajando en las especificaciones y protocolos del nuevo cifrado
y nos estamos acercando al final. La migración tardará varias versiones en completarse.</p>
<p>En esta versión, para minimizar las interrupciones, sólo las nuevas instalaciones y un pequeño porcentaje de las existentes
(seleccionadas aleatoriamente al reiniciar) utilizarán el nuevo cifrado.
Si tu router se "reconfigura" para usar el nuevo cifrado, puede tener un tráfico más bajo o menos fiable de lo habitual durante varios días después de reiniciar.
Esto es normal, porque tu router ha generado una nueva identidad.
Su rendimiento debería recuperarse después de un tiempo.</p>
<p>Ya hemos "re-claveado" la red dos veces, al cambiar el tipo de firma por defecto,
pero esta es la primera vez que cambiamos el tipo de cifrado por defecto.
Esperemos que todo vaya bien, pero estamos empezando poco a poco para estar seguros.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 con mejoras de rendimiento</summary></details><p>0.9.48 habilita nuestro nuevo protocolo de cifrado de extremo a extremo (propuesta 144) para la mayoría de los servicios.
Hemos añadido soporte preliminar para el nuevo cifrado de mensajes de construcción de túneles (propuesta 152).
Hay importantes mejoras de rendimiento en todo el router.</p>
<p>Los paquetes para Ubuntu Xenial (16.04 LTS) ya no están soportados.
Los usuarios de esa plataforma deben actualizar para poder seguir recibiendo las actualizaciones de I2P.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>La versión 0.9.47 permite una nueva codificación</summary></details><p>La versión 0.9.47 habilita por defecto nuestro nuevo protocolo de cifrado de extremo a extremo (propuesta 144) para algunos servicios.
La herramienta de análisis y bloqueo de Sybil está ahora habilitada por defecto.</p>
<p>Ahora se requiere Java 8 o superior.
Los paquetes de Debian para Wheezy y Stretch, y para Ubuntu Trusty y Precise, ya no están soportados.
Los usuarios de esas plataformas deberían actualizar para poder seguir recibiendo las actualizaciones de I2P</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="Se ha lanzado la versión 0.9.46" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 con correcciones de errores</summary></details><p>La versión 0.9.46 contiene importantes mejoras de rendimiento en la biblioteca de streaming.
Hemos completado el desarrollo del cifrado ECIES (propuesta 144) y ahora hay una opción para habilitarlo para las pruebas.</p>
<p>Sólo para usuarios de Windows:
Esta versión corrige una vulnerabilidad de escalada de privilegios local
que podría ser explotada por un usuario local.
Por favor, aplique la actualización lo antes posible.
Gracias a Blaze Infosec por la divulgación responsable del problema.</p>
<p>Esta es la última versión compatible con Java 7, los paquetes Debian Wheezy y Stretch, y los paquetes Ubuntu Precise y Trusty.
Los usuarios de esas plataformas se deben actualizar para recibir futuras actualizaciones de I2P.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 con correcciones de errores</summary></details><p>La versión 0.9.45 contiene correcciones importantes para el modo oculto y el probador de ancho de banda.
Hay una actualización del tema oscuro de la consola.
Seguimos trabajando en la mejora del rendimiento y en el desarrollo de un nuevo cifrado de extremo a extremo (propuesta 144).</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="Versión 0.9.44" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 con corrección de errores</summary></details><p>0.9.44 contiene una solución importante para un problema de denegación de servicio en la gestión de servicios ocultos de nuevos tipos de cifrado.
Todos los usuarios deben actualizar lo antes posible.</p>
<p>La versión incluye el soporte inicial para la nueva encriptación de extremo a extremo (propuesta 144).
Se sigue trabajando en este proyecto y aún no está listo para su uso.
Hay cambios en la página de inicio de la consola y nuevos reproductores multimedia HTML5 incrustados en i2psnark.
Se incluyen correcciones adicionales para redes IPv6 con cortafuegos.
Las correcciones en la construcción del túnel deberían resultar en un inicio más rápido para algunos usuarios.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="Versión 0.9.43" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 con corrección de errores</summary></details><p>En la versión 0.9.43, continuamos trabajando para mejorar la seguridad, la privacidad y el rendimiento.
Nuestra implementación de la nueva especificación del conjunto de contratos de arrendamiento (LS2) ha finalizado.
Estamos comenzando la implementación de una encriptación de extremo a extremo más fuerte y rápida (propuesta 144) para una futura versión.
Varios problemas de detección de direcciones IPv6 han sido corregidos, y por supuesto hay otros errores corregidos.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 con corrección de errores</summary></details><p>0.9.42 sigue trabajando para que el I2P sea más rápido y fiable.
Incluye varios cambios para acelerar nuestro transporte UDP.
Hemos dividido los archivos de configuración para poder trabajar en el futuro con embalajes más modulares.
Continuamos trabajando para implementar nuevas propuestas para una encriptación más rápida y segura.
Hay, por supuesto, un montón de correcciones de errores también.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 con corrección de errores</summary></details><p>0.9.41 prosigue la labor de aplicación de las nuevas características de la propuesta 123,
incluyendo la autenticación por cliente para conjuntos de contratos de arrendamiento encriptados.
La consola tiene un logotipo I2P actualizado y varios iconos nuevos.
Hemos actualizado el instalador de Linux.</p>
<p>El inicio debería ser más rápido en plataformas como Raspberry Pi.
Hemos corregido varios errores, incluidos algunos graves que afectan a los mensajes de red de bajo nivel.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 con nuevos iconos</summary></details><p>0.9.40 incluye soporte para el nuevo formato cifrado de leaseset.
Desactivamos el antiguo protocolo de transporte NTCP 1.
Hay una nueva característica de importación de SusiDNS y un nuevo mecanismo de filtrado de scripts para las conexiones entrantes.</p>
<p>Hemos hecho muchas mejoras al instalador nativo de OSX, y también hemos actualizado el instalador de IzPack.
El trabajo continúa en la actualización de la consola con nuevos iconos.
Como de costumbre, ¡también hemos arreglado muchos errores!</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 con mejoras en el rendimiento</summary></details><p>0.9.39 incluye amplios cambios para los nuevos tipos de bases de datos de red (propuesta 123).
Hemos incluido el plugin i2pcontrol como webapp para soportar el desarrollo de aplicaciones RPC.
Hay numerosas mejoras de rendimiento y correcciones de errores.</p>
<p>Hemos eliminado los temas de medianoche y clásicos para reducir la carga de mantenimiento;
los usuarios anteriores de esos temas verán ahora el tema oscuro o claro.
También hay nuevos iconos en la página de inicio, un primer paso para actualizar la consola.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 con el nuevo asistente de configuración</summary></details><p>0.9.38 incluye un nuevo asistente de primera instalación con un probador de ancho de banda.
Hemos añadido soporte para el último formato de base de datos GeoIP.
Hay un nuevo instalador de perfiles de Firefox y un nuevo instalador nativo de Mac OSX en nuestro sitio web.
Se sigue trabajando en el soporte del nuevo formato netdb "LS2".</p>
<p>Esta versión también contiene un montón de correcciones de errores, incluyendo varios problemas con los adjuntos susimail, y una solución para enrutadores sólo IPv6.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Informe de Viaje" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P en el 35C3</summary></details><p>El equipo I2P estuvo presente en su mayoría en el 35C3 de Leipzig.
Se celebraron reuniones diarias para revisar el año pasado y cubrir nuestras metas de desarrollo y diseño para 2019.</p>
<p>La Visión del Proyecto y la nueva Hoja de Ruta pueden ser <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">revisadas aquí</a>.</p>
<p>El trabajo continuará en LS2, la Testnet y las mejoras de usabilidad de nuestro sitio web y consola.
Existe un plan para estar en Tails, Debian y Ubuntu Disco. Todavía necesitamos gente que trabaje en las correcciones de Android e I2P_Bote.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 con NTCP2 activado</summary></details><p>Versión 0.9.37 usa un protocolo de transporte más rápido, más seguro que se llama NTCP2. </p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 lanzada" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 con NTCP2 y reparación de errores</summary></details><p>0.9.36 contiene un nuevo protocolo de transporte más seguro llamado NTCP2.
Está desactivado por defecto, pero puede habilitarlo para realizar pruebas añadiendo la <a href="/configadvanced">configuración avanzada</a> <tt>i2np.ntcp2.enable=true</tt> y reiniciando.
NTCP2 se activará en la próxima versión.</p>
<p>Esta versión también contiene varias mejoras de rendimiento y correcciones de errores.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 lanzada" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 con carpetas de SusiMail y asistente de instalación de SSL</summary></details><p>0.9.35 añade soporte para carpetas en SusiMail, y un nuevo Asistente SSL para configurar HTTPS en su sitio web de Servicio Oculto.
También tenemos la habitual colección de correcciones de errores, especialmente en SusiMail.</p>
<p>Estamos trabajando duro en varias cosas para 0.9.36, incluyendo un nuevo instalador de OSX y un protocolo de transporte más rápido y seguro llamado NTCP2.</p>
<p>I2P estará en HOPE en la ciudad de Nueva York, del 20-22 de julio. Encuéntranos y dinos hola!</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="Versión 0.9.34" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 con correcciones de fallos</summary></details><p>¡La 0.9.34 contiene muchas correcciones de fallos!

View File

@ -0,0 +1,567 @@
<div>
<header title="Noticias de I2P">Suscripción (feed) de noticias, y actualizaciones del router I2P</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="Versión 2.8.2 Disponible" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>Versión 2.8.2 Disponible</summary></details><p>La versión 2.8.2 corrige un error que causaba fallos de SHA256 que se introdujo en la versión 2.8.1.
El error afectaba principalmente a los enrutadores de alto ancho de banda.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="Versión 2.8.1 Disponible" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>Lanzamiento de I2P 2.8.1</summary></details><p>La versión 2.8.1 corrige los accesos a sitios locales que se rompieron en 2.8.0.
Hemos añadido burbujas de notificación a varias aplicaciones en la consola para destacar los mensajes de la aplicación.
Hemos corregido un error en la prueba del túnel que podría haber estado afectando a la fiabilidad del túnel.
La libreta de direcciones ahora tiene una nueva pestaña "última" que muestra los nombres de host más recientes añadidos de tus suscripciones.
Hay varias correcciones y mejoras en el tema oscuro.
</p>
<p>Arreglamos el instalador que antes fallaba en Java 21 o superior.
También arreglamos la instalación en rutas de directorio que contienen espacios en Linux.
Para los que usáis Docker, actualizamos el contenedor de Docker y las librerías de contenedor que estaban desactualizadas.
</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="El acceso al sitio local falla en 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Error de acceso local</summary></details><p>En la versión 2.8.0, navegar a un sitio local (ya sea por nombre de host o b32) fallará.
La solución alternativa es usar localhost y el puerto del servidor, generalmente 7658, para evitar I2P.
Por ejemplo, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
Pedimos disculpas por el problema y estamos trabajando en una solución.
</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="Lanzamiento de I2P 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>Lanzamiento de I2P 2.8.0</summary></details><p>Esta versión mejora I2P al corregir errores, eliminar código no utilizado y mejorar la estabilidad de la red.</p>
<p>Hemos mejorado el manejo de routers congestionados en la red.
Se abordaron problemas en UPnP y la transversalidad NAT para mejorar la conectividad y la notificación de errores.
Ahora tenemos una estrategia más agresiva para la eliminación de leasesets del NetDb con el fin de mejorar el rendimiento del router y mitigar la sobrecarga.
Se implementaron otros cambios para reducir la observabilidad de eventos como el reinicio o apagado de un router.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="Publicada la versión 2.7.0 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>Publicada la versión 2.7.0 de I2P</summary></details><p>Esta versión, I2P 2.7.0, continúa nuestro trabajo corrigiendo errores, mejorando el rendimiento y añadiendo funciones.</p>
<p>Se ha mejorado el acceso a la información desde la consola y las aplicaciones.
Se han solucionado problemas en I2PSnark y la búsqueda de SusiMail.
La búsqueda de netDB integrada en la consola del router ahora funciona de una manera más intuitiva y útil.
Se han realizado pequeñas mejoras en las pantallas de diagnóstico en modo avanzado.</p>
<p>También se han corregido errores para mejorar la compatibilidad dentro de la red.
Se resolvió un problema con la publicación de leaseSets, lo que mejora la fiabilidad de los servicios ocultos principales.
I2PSnark ya no cambia el infohash cuando un usuario solo modifica los trackers en un torrent existente.
Esto evita que los torrents se vean innecesariamente interrumpidos por estos cambios.
Damos la bienvenida a esta contribución de un nuevo colaborador.
Se resolvió un conflicto en el manejo de una opción de la biblioteca de streaming para mejorar la compatibilidad con otras implementaciones de I2P.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="Publicada la versión 2.6.1 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>Publicada la versión 2.6.1 de I2P</summary></details><p>I2P 2.6.1 se lanza para corregir un error en la interfaz de usuario de la aplicación Hidden Services Manager.
Este error deshabilitaba el desplazamiento, haciendo que algunas configuraciones fueran inaccesibles.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="Publicada la versión 2.6.0 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>Publicada la versión 2.6.0 de I2P</summary></details><p>Esta versión, I2P 2.6.0, continúa nuestro trabajo al corregir errores, agregar funciones y mejorar la fiabilidad de la red.</p>
<p>Se favorecerán los routers más nuevos al seleccionar routers floodfill.
I2PSnark recibió funciones que mejoran el rendimiento de PeX (Intercambio de Pares), además de correcciones de errores.
Se están eliminando los protocolos de transporte heredados, simplificando el código en los transportes UDP.
Los destinos alojados localmente serán accesibles para los clientes locales sin solicitar su LeaseSet, mejorando el rendimiento y la capacidad de prueba.
Se realizaron ajustes adicionales en las estrategias de selección de pares.</p>
<p>I2P ya no permite I2P-sobre-Tor, las conexiones desde direcciones IP de salida de Tor ahora están bloqueadas.
Desalentamos esto porque degrada el rendimiento de I2P y consume los recursos de las salidas de Tor sin ningún beneficio.
Si eres una persona solidaria que opera tanto una salida de Tor como I2P, te animamos a continuar haciéndolo, utilizando direcciones IP diferentes para cada uno.
Los relés no de salida y los clientes de Tor no se ven afectados por esto y no necesitan cambiar nada.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="Publicada la versión 2.5.2 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 con corrección de HTTP</summary></details><p>Se publica I2P 2.5.2 para corregir un error introducido en 2.5.0 que provocaba el truncamiento de algunos contenidos HTTP.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="Publicada la versión 2.5.1 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>Lanzamiento de la versión 2.5.1 de I2P para hacer frente a los ataques de denegación de servicio</summary></details><p>"I2P 2.5.1 se ha lanzado para abordar los ataques de Denegación de Servicio que afectan a la red y los servicios de I2P.
Con este lanzamiento, deshabilitamos las partes basadas en IP de la herramienta de detección de ataques Sybil, que estaban dirigidas a amplificar el efecto y la duración del ataque.
Esto debería ayudar a que la red vuelva a la operación normal.
Aquellos de ustedes que han deshabilitado la herramienta de detección de ataques Sybil pueden volver a habilitarla de forma segura.
También se han realizado ajustes en otros subsistemas para mejorar la validación de RouterInfo y la selección de pares."</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Clima tormentoso." href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Clima de la red: Tormentoso. I2P está bajo ataque.</summary></details><p>La red I2P está actualmente bajo un ataque de Denegación de Servicio.
Este ataque afecta a I2P e i2pd, pero de diferentes maneras, y está teniendo un efecto grave en la salud de la red.
La accesibilidad de los sitios de I2P está gravemente degradada.</p>
<p>Si estás alojando un servicio dentro de I2P y está alojado en un router Floodfill, deberías considerar alojar el servicio también en un router con Floodfill deshabilitado para mejorar la accesibilidad.
Se están discutiendo otras mitigaciones, pero todavía se está trabajando en una solución a largo plazo y compatible con versiones anteriores.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="Nueva versión I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>Más mejoras de aplicaciones, auditoría de la estrategia de aislamiento de NetDB.</summary></details><p>Esta versión, I2P 2.5.0, ofrece más mejoras orientadas al usuario que la versión 2.4.0, que se centró en implementar la estrategia de aislamiento de NetDB.</p>
<p>Se han añadido nuevas funciones a I2PSnark, como la capacidad de buscar a través de torrents.
Se han corregido errores para mejorar la compatibilidad con otros clientes de torrents de I2P, como BiglyBT y qBittorrent.
Nos gustaría agradecer a todos los desarrolladores que han trabajado con libtorrent y qBittorrent para habilitar y mejorar su soporte para I2P.
También se han añadido nuevas funciones a SusiMail, incluyendo soporte para el formato Markdown en correos electrónicos y la capacidad de arrastrar y soltar archivos adjuntos en correos electrónicos.
Los túneles creados con el administrador de Servicios Ocultos ahora soportan "Keepalive", lo que mejora el rendimiento y la compatibilidad con tecnologías web, permitiendo sitios I2P más sofisticados.</p>
<p>Durante esta versión también realizamos varios ajustes en la NetDB para mejorar su resistencia al spam y la capacidad del router para rechazar mensajes sospechosos.
Esto fue parte de un esfuerzo por "auditar" la implementación de las defensas de "aislamiento de Sub-DB" de la versión 2.4.0.
Esta investigación descubrió un evento menor que rompía el aislamiento, el cual reparamos.
Este problema fue descubierto y solucionado internamente por el equipo de I2P.</p>
<p>Durante esta versión se realizaron varias mejoras en el proceso de lanzamiento de nuestras distribuciones downstream para Android y Windows.
Esto debería resultar en una mejor entrega y disponibilidad de estos productos downstream.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="Lanzamiento de I2P 2.4.0 con mejoras en la congestión y la seguridad de NetDB." href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>Lanzamiento de I2P 2.4.0 con mejoras en la congestión y la seguridad de NetDB.</summary></details><p>Esta versión, I2P 2.4.0, continúa nuestro esfuerzo por mejorar la seguridad y estabilidad de la red I2P.
Contiene mejoras significativas en la Base de Datos de la Red, una estructura esencial dentro de la red I2P utilizada para descubrir a tus pares.</p>
<p>Los cambios en la gestión de la congestión mejorarán la estabilidad de la red al dar a los enrutadores la capacidad de aliviar a los pares congestionados evitándolos.
Esto ayudará a la red a limitar el efecto del spam de túneles.
También ayudará a la red a recuperarse durante y después de los ataques DDOS.</p>
<p>Los cambios en NetDb también ayudan a proteger los routers individuales y las aplicaciones que los utilizan.
Los routers ahora pueden defenderse contra atacantes separando el NetDB en múltiples "Sub-DB's", que usamos para prevenir fugas de información entre las aplicaciones y el router.
Esto también mejora la información disponible para los routers Java sobre su actividad en NetDB y simplifica nuestro soporte para aplicaciones multihoming.</p>
<p>También se incluyen una serie de correcciones de errores y mejoras en las aplicaciones I2PSnark y SusiMail.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:" title="Nuevo lanzamiento I2P 2.3.0 - Correcciones de seguridad, listas de bloqueo ajustables, API DTG." href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Correcciones de seguridad, listas de bloqueo ajustables, API DTG</summary></details><p>Esta versión contiene correcciones para CVE-2023-36325.
CVE-2023-36325 es un error de confusión de contexto que ocurrió en el filtro de Bloom.
Un atacante elabora un mensaje I2NP que contiene un messageID único y envía ese messageID a un cliente.
El mensaje, después de pasar por el filtro de Bloom, no se permite reutilizar en un segundo mensaje.
El atacante luego envía el mismo mensaje directamente al enrutador.
El enrutador pasa el mensaje al filtro de Bloom y se descarta.
Esto filtra la información de que el messageID se ha visto antes, dando al atacante una fuerte razón para creer que el enrutador está alojando al cliente.
Esto se ha solucionado separando la funcionalidad del filtro de Bloom en diferentes contextos según si un mensaje provino de un túnel de cliente, un túnel exploratorio o se envió directamente al enrutador.
Bajo circunstancias normales, este ataque tarda varios días en realizarse con éxito y puede verse afectado por varios factores, como el reinicio de enrutadores durante la fase de ataque y la sensibilidad a falsos positivos.
Se recomienda a los usuarios de Java I2P que actualicen de inmediato para evitar el ataque.</p>
<p>En el proceso de solucionar este error de confusión de contexto, hemos revisado algunas de nuestras estrategias para programar de manera defensiva contra este tipo de fugas.
Esto incluye ajustes en el netDb, los mecanismos de limitación de velocidad y el comportamiento de los routers floodfill.</p>
<p>Esta versión añade not_bob como un segundo proveedor de hosts predeterminado, y añade <a href="http://notbob.i2p">notbob.i2p</a> y <a href="http://ramble.i2p">ramble.i2p</a> a la página de inicio de la consola.</p>
<p>Esta versión también contiene una lista de bloqueo ajustable.
El bloqueo es semipermanente, cada dirección IP bloqueada normalmente permanece bloqueada hasta que se reinicia el router.
Los usuarios que observen un crecimiento explosivo de la lista de bloqueo durante ataques Sybil pueden optar por tiempos de espera más cortos configurando la lista de bloqueo para que las entradas expiren en un intervalo.
Esta función está desactivada por defecto y solo se recomienda para usuarios avanzados en este momento.</p>
<p>Esta versión también incluye una API para que los complementos se modifiquen con la interfaz gráfica de escritorio (DTG).
Ahora es posible agregar elementos al menú de la bandeja del sistema, lo que permite un lanzamiento más intuitivo de los complementos que utilizan interfaces de aplicaciones nativas.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="Nueva versión 2.2.1, correcciones de empaquetado para Docker, Ubuntu Lunar y Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - versión de mantenimiento para 2.2.0</summary></details><p>Después del lanzamiento de I2P 2.2.0, que se adelantó para acelerar las mitigaciones de los ataques DDOS, nos enteramos de algunos problemas en desarrollo que hicieron necesario construir y lanzar nuevos paquetes.
Esta versión soluciona un problema en Ubuntu Lunar y Debian Sid por el que no se podía acceder a la consola del router utilizando una versión actualizada del paquete jakarta.
Los paquetes Docker no leían los argumentos correctamente, lo que resultaba en archivos de configuración inaccesibles.
Este problema también se ha resuelto.
El contenedor Docker ahora también es compatible con Podman.</p>
<p>Esta versión sincroniza las traducciones con transifex y actualiza la base de datos GeoIP.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="Nueva versión 2.2.0. Mitigación de los ataques DDoS y ajustes del subsistema de streaming." href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigación de ataques DDoS y ajustes del subsistema de streaming</summary></details><p>Hemos decidido adelantar la fecha de lanzamiento de la versión 2.2.0, que tendrá lugar hoy, 13 de marzo de 2023.Esta versión incluye cambios en los componentes NetDB, Floodfill y Peer-Selection que mejoran la capacidad del router para sobrevivir a ataques DDOS.Es probable que los ataques continúen, pero las mejoras en estos sistemas ayudarán a mitigar el riesgo de ataques DDOS al ayudar al router a identificar y quitar prioridad a los routers que parezcan maliciosos.</p>
<p>Esta versión también añade protección contra repeticiones al subsistema de streaming, lo que impide que un atacante que pueda capturar un paquete cifrado pueda reutilizarlo enviándolo a destinatarios no deseados.Se trata de un cambio compatible con versiones anteriores, por lo que los routers más antiguos podrán seguir utilizando las funciones de streaming de los routers más recientes.Este problema fue descubierto y solucionado internamente por el equipo de desarrollo de I2P y no está relacionado con los ataques DDoS.Nunca hemos encontrado un paquete de streaming reproducido en la naturaleza y no creemos que un ataque de repetición de streaming haya tenido lugar contra la red I2P en este momento.</p>
<p>Como habréis notado, estas notas de publicación y la propia publicación han sido firmadas por idk, y no por zzz.zzz ha decidido alejarse del proyecto y sus responsabilidades están siendo asumidas por otros miembros del equipo.Por ello, el proyecto está trabajando en la sustitución de la infraestructura de estadísticas de red y en el traslado del foro de desarrollo a i2pforum.i2p.Agradecemos a zzz que haya prestado estos servicios durante tanto tiempo.</p>
<p>Como es habitual, le recomendamos que actualice a esta versión.
La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="Actualización DDoS" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>Actualización DDoS</summary></details><p>Hemos confirmado que el atacante controla un gran número de routers.Nuestras investigaciones y mitigaciones continúan.</p>
<p>Es un buen momento para recordar que, incluso después de 20 años, la red I2P es relativamente pequeña.No tenemos pruebas de que el atacante esté intentando desanonimizar a ningún usuario en particular o servicio oculto.Sin embargo, si usted tiene un modelo de amenaza de alto riesgo, debería considerar cuidadosamente si I2P le proporciona actualmente la protección que necesita.La mejor solución, a largo plazo, es correr la voz y hacer crecer la red I2P para aumentar la seguridad de nuestros usuarios.</p>
<p>Proporcionaremos información adicional aquí en el feed de noticias y en <a href="http://zzz.i2p">zzz.i2p</a> según sea necesario.Le pedimos paciencia mientras trabajamos para mejorar I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="Acerca de los recientes ataques de denegación de servicio" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>La I2P permanece intacta con el rendimiento mermado</summary></details><p>La red I2P está siendo afectada por un ataque de denegación de servicio.La función floodfill de la red se ha visto afectada, lo que ha provocado la interrupción de las respuestas y el descenso de los índices de éxito en la construcción de túneles.Los participantes en la red han experimentado dificultades para conectarse a los sitios I2P y utilizar los servicios I2P.Se están investigando y aplicando gradualmente estrategias de mitigación.</p>
<p>Aunque el ataque ha degradado el rendimiento, la red sigue intacta y utilizable.Los enrutadores Java I2P parecen manejar los problemas mejor que los enrutadores i2pd por ahora.En la próxima semana deberían empezar a aparecer varias mitigaciones en las versiones de desarrollo de los routers Java y C++.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="Publicada la 2.1.0" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 con varias correcciones de SSU2</summary></details><p>Hemos aprendido muchas cosas desde el lanzamiento de la versión 2.0.0 en noviembre. A medida que los routers se han actualizad, la red ha pasado de aproximadamente el 1% a más del 60% a usar el nuevo protocolo de transporte SSU2. Primero, hemos confirmado que el protocolo SSU2 es sólido y seguro. En segundo lugar, sin embargo, hemos encontrado y corregido numerosos errores menores o raramente activados en la implementación del protocolo. Los efectos de estos errores se han acumulado, reducido el rendimiento de la red.</p>
<p>Además, somos conscientes del aumento del número de túneles y la reducción de la tasa de éxito en la construcción de túneles en la red,
posiblemente provocados por la nueva función de dirección transitoria I2P de Bitcoin,
pero empeorados por nuestros errores en SSU2 y otros problemas de control de congestión.
Estamos trabajando con Bitcoin y otros proyectos que no son de Bitcoin para reducir las demandas de la red I2P.
Hemos mejorado nuestros algoritmos para reducir la carga de la red durante tiempos de congestión.
También estamos colaborando con i2pd para desarrollar estrategias comunes de control de la congestión.</p>
<p>Por lo tanto, hemos acelerado este lanzamiento en unas seis semanas, para hacer llegar las correcciones a todo el mundo.
i2pd lanzó su versión 2.45.0 la semana pasada y los primeros resultados son alentadores.
Los nuevos protocolos y las redes distribuidas son difíciles de desarrollar.
La congestión puede llegar con poca advertencia y con pocas pistas de la causa.
Gracias por su paciencia, ya que hemos diagnosticado y, con suerte, solucionado los problemas.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="Lanzamiento de la versión 2.0.0" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>Transporte SSU2 habilitado</summary></details><p>La versión 2.0.0 de I2P habilita nuestro nuevo transporte UDP SSU2 para todos los usuarios, después de completar funciones menores, pruebas y numerosas correcciones de errores.</p>
<p>También tenemos correcciones en todas partes, incluso para el instalador, la base de datos de la red, la adición a la libreta de direcciones privada, el iniciador del navegador de Windows y UPnP IPv6.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Entradas recientes del blog" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Algunas publicaciones de blog recientes</summary></details><p>Aquí hay enlaces a varias publicaciones de blog recientes en nuestra web:</p>
<ul>
<li>Descripción general sobre nuestro nuevo transporte SSU2</li>
<li>Advertencia sobre monedas I2P y otras estafas</li>
<li>Una entrevista con Konrad de diva.exchange</li>
<li>Una entrevista con Dustin de StormyCloud1</li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="Lanzamiento de la versión 1.9.0" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 con SSU2 para pruebas</summary></details><p>Hemos pasado los últimos tres meses trabajando en nuestro nuevo protocolo de transporte UDP "SSU2"
con un pequeño número de probadores voluntarios.
Esta versión completa la implementación, incluyendo pruebas de retransmisión y de pares.
Lo estamos habilitando por defecto para las plataformas Android y ARM, y un pequeño porcentaje de otros routers al azar.
Esto nos permitirá hacer muchas más pruebas en los próximos tres meses, terminar la función de migración de conexiones
y solucionar cualquier problema restante.
Tenemos previsto habilitarla para todo el mundo en la próxima versión prevista para noviembre.
No es necesaria ninguna configuración manual.</p>
<p>Por supuesto, también hay la habitual colección de correcciones de errores en esta versión.
También hemos añadido un detector automático de bloqueos que ya ha encontrado un raro bloqueo que ya está solucionado.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="Nuevo Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>Nuevo Outproxy</summary></details><p>Los "outproxies" (nodos de salida) de I2P pueden utilizarse para acceder a Internet a través de
su túnel proxy HTTP.
Como se aprobó en nuestra <a href="http://i2p-projekt.i2p/en/meetings/314">reunión mensual</a>,
<b>exit.stormycloud.i2p</b> es ahora nuestro outproxy oficial y recomendado, sustituyendo al ya desaparecido <b>false.i2p</b>.
Para más información sobre la <a href="http://stormycloud.i2p/">organización</a> de StormyCloud
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
y los <a href="http://stormycloud.i2p/tos.html">términos del servicio</a>,
consulte el <a href="http://stormycloud.i2p/">sitio web de StormyCloud</a>.</p>
<p>Le sugerimos que cambie la configuración de su <a href="/i2ptunnel/edit?tunnel=0">Administrador de Servicios Ocultos</a>
para especificar <b>exit.stormycloud.i2p</b>
en dos lugares: <b>Outproxies</b> y <b>SSL Outproxies</b>.
Después de editar, <b>desplácese hacia abajo y haga clic en Guardar</b>.
Ver nuestra <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">entrada de blog para una captura de pantalla</a>.
Para las instrucciones de Android y capturas de pantalla ver el <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">blog de notbob</a>.</p>
<p>Las actualizaciones del router no actualizarán su configuración, deberá editarla manualmente.
Gracias a StormyCloud por su apoyo, y por favor considere una <a href="http://stormycloud.i2p/donate.html">donación</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 con correcciones de errores</summary></details><p>Esta versión incluye correcciones de errores en i2psnark
el router, I2CP, y UPnP.
Las correcciones del router abordan errores en el reinicio suave, IPv6, pruebas de pares SSU
los almacenes de la base de datos de la red, y la construcción de túneles.
El manejo de la familia del router y la clasificación Sybil también han sido
mejorado significativamente.</p>
<p>Junto con i2pd, estamos desarrollando nuestro nuevo transporte UDP, SSU2.
SSU2 aportará mejoras sustanciales de rendimiento y seguridad.
También nos permitirá reemplazar finalmente nuestro último uso de la lentísima encriptación ElGamal,
completando la actualización completa de la criptografía que comenzamos hace unos 9 años.
Esta versión contiene una implementación preliminar que está desactivada por defecto.
Si desea participar en las pruebas, por favor busque la información actual
en zzz.i2p.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Instalar las actualizaciones esenciales de Java/Jpackage" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>La reciente vulnerabilidad de Java "Psychic Signatues" afecta a I2P. Los usuarios actuales de
I2P en Linux, o cualquier usuario de I2P que esté utilizando una JVM no empaquetada debería actualizar
su JVM o cambiar a una versión que no contenga la vulnerabilidad, por debajo de Java 15.</p>
<p>Se han generado nuevos paquetes I2P Easy-Install utilizando la última versión de la
máquina virtual Java. Se han publicado más detalles en las respectivas
fuentes de noticias de los paquetes.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 con mejoras de fiabilidad y rendimiento</summary></details><p>La versión 1.7.0 contiene varias mejoras de rendimiento y fiabilidad.</p>
<p>Ahora hay mensajes emergentes en la bandeja del sistema, para aquellas plataformas que lo soportan.
i2psnark tiene un nuevo editor de torrents.
El transporte NTCP2 ahora usa mucho menos CPU.</p>
<p>La interfaz BOB, obsoleta desde hace tiempo, se elimina para las nuevas instalaciones.
Seguirá funcionando en las instalaciones existentes, excepto en los paquetes de Debian.
Los usuarios que sigan utilizando las aplicaciones BOB deberían pedir a los desarrolladores que se conviertan al protocolo SAMv3.</p>
<p>Sabemos que desde nuestro lanzamiento de la versión 1.6.1, la fiabilidad de la red se ha deteriorado constantemente.
Nos dimos cuenta del problema poco después del lanzamiento, pero tardamos casi dos meses en encontrar la causa.
Finalmente lo identificamos como un error en i2pd 2.40.0,
y la solución estará en su versión 2.41.0 que saldrá aproximadamente al mismo tiempo que esta versión.
En el camino, hemos hecho varios cambios en el lado de Java I2P para mejorar la
robustez de las búsquedas y almacenes de la base de datos de la red, y evitar los pares de bajo rendimiento en la selección de pares del túnel.
Esto debería ayudar a que la red sea más robusta incluso en presencia de routers con errores o maliciosos.
Además, estamos iniciando un programa conjunto para probar los routers i2pd y Java I2P
juntos en una red de prueba aislada, para que podamos encontrar más problemas antes de los lanzamientos, no después.</p>
<p>En otras noticias, seguimos avanzando mucho en el diseño de nuestro nuevo transporte UDP "SSU2" (propuesta 159)
y hemos empezado a implementarlo.
SSU2 aportará mejoras sustanciales de rendimiento y seguridad.
También nos permitirá reemplazar finalmente nuestro último uso del lentísimo cifrado ElGamal,
completando una actualización completa de la criptografía que comenzó hace unos 9 años.
Esperamos comenzar pronto las pruebas conjuntas con i2pd, y extenderlo a la red a finales de este año.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 habilita nuevos mensajes de construcción de túneles</summary></details><p>Esta versión completa el despliegue de dos importantes actualizaciones de protocolo desarrolladas en 2021.
Se acelera la transición al cifrado X25519 para los enrutadores, y esperamos que casi todos los enrutadores se vuelvan a cifrar a finales de año.
Se habilitan los mensajes de construcción de túneles cortos para una importante reducción del ancho de banda.</p>
<p>Hemos añadido un panel de selección de temas al nuevo asistente de instalación.
Hemos mejorado el rendimiento de SSU y solucionado un problema con los mensajes de prueba de pares de SSU.
Se ajustó el filtro Bloom de construcción de túneles para reducir el uso de memoria.
Hemos mejorado la compatibilidad con los plugins que no son de Java.</p>
<p>En otras noticias, estamos avanzando de forma excelente en el diseño de nuestro nuevo transporte UDP SSU2 y esperamos empezar a implementarlo a principios del año que viene.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 con nuevos mensajes de construcción de túneles</summary></details><p>Sí, así es, después de 9 años de versiones 0.9.x, vamos a pasar directamente de 0.9.50 a 1.5.0.
Esto no significa un cambio importante en la API, ni una afirmación de que el desarrollo haya terminado.
Es simplemente un reconocimiento a casi 20 años de trabajo para proporcionar anonimato y seguridad a nuestros usuarios.</p>
<p>Esta versión finaliza la implementación de mensajes de construcción de túneles más pequeños para reducir el ancho de banda.
Continuamos la transición de los routers de la red al cifrado X25519.
Por supuesto, también hay numerosas correcciones de errores y mejoras de rendimiento.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Vulnerabilidad en MuWire Desktop" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Vulnerabilidad de Muwire Desktop</summary></details><p>Se ha descubierto una vulnerabilidad de seguridad en la aplicación de escritorio independiente de MuWire.
No afecta al plugin de la consola, y no está relacionado con el problema del plugin anunciado anteriormente.
Si está ejecutando la aplicación de escritorio de MuWire debe <a href="http://muwire.i2p/">actualizar a la versión 0.8.8</a> inmediatamente.</p>
<p>Los detalles de la emisión se publicarán en <a href="http://muwire.i2p/security.html">muwire.i2p</a>
el 15 de julio de 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Vulnerabilidad del plugin MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Vulnerabilidad del plugin Muwire</summary></details><p>Se ha descubierto una vulnerabilidad de seguridad en el plugin MuWire.
No afecta al cliente de escritorio independiente.
Si está ejecutando el plugin MuWire debe <a href="/configplugins">actualizar a la versión 0.8.7-b1</a> inmediatamente.</p>
<p>Consulte <a href="http://muwire.i2p/security.html">muwire.i2p</a>
para obtener más información sobre la vulnerabilidad y las recomendaciones de seguridad actualizadas.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="Lanzamiento de la versión 0.9.50" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 con correcciones de IPv6</summary></details><p>0.9.50 continúa la transición a ECIES-X25519 para las claves de cifrado del router.
Hemos habilitado el DNS sobre HTTPS para la resiembra con el fin de proteger a los usuarios del snooping pasivo de DNS.
Hay numerosas correcciones y mejoras para las direcciones IPv6, incluida la nueva compatibilidad con UPnP.</p>
<p>Por fin hemos corregido algunos errores de corrupción de SusiMail que se producían desde hace tiempo.
Los cambios en el limitador de ancho de banda deberían mejorar el rendimiento del túnel de red.
Hay varias mejoras en nuestros contenedores Docker.
Hemos mejorado nuestras defensas para posibles routers maliciosos y con errores en la red.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 con correcciones de SSU y criptografía más rápida</summary></details><p>La versión 0.9.49 continúa el trabajo para hacer que I2P sea más rápido y seguro.
Tenemos varias mejoras y correcciones para el transporte SSU (UDP) que deberían resultar en velocidades más rápidas.
Esta versión también inicia la migración al nuevo y más rápido cifrado ECIES-X25519 para los routers.
(Los destinos llevan utilizando este cifrado desde hace varias versiones)
Llevamos varios años trabajando en las especificaciones y protocolos del nuevo cifrado
y nos estamos acercando al final. La migración tardará varias versiones en completarse.</p>
<p>En esta versión, para minimizar las interrupciones, sólo las nuevas instalaciones y un pequeño porcentaje de las existentes
(seleccionadas aleatoriamente al reiniciar) utilizarán el nuevo cifrado.
Si tu router se "reconfigura" para usar el nuevo cifrado, puede tener un tráfico más bajo o menos fiable de lo habitual durante varios días después de reiniciar.
Esto es normal, porque tu router ha generado una nueva identidad.
Su rendimiento debería recuperarse después de un tiempo.</p>
<p>Ya hemos "re-claveado" la red dos veces, al cambiar el tipo de firma por defecto,
pero esta es la primera vez que cambiamos el tipo de cifrado por defecto.
Esperemos que todo vaya bien, pero estamos empezando poco a poco para estar seguros.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 con mejoras de rendimiento</summary></details><p>0.9.48 habilita nuestro nuevo protocolo de cifrado de extremo a extremo (propuesta 144) para la mayoría de los servicios.
Hemos añadido soporte preliminar para el nuevo cifrado de mensajes de construcción de túneles (propuesta 152).
Hay importantes mejoras de rendimiento en todo el router.</p>
<p>Los paquetes para Ubuntu Xenial (16.04 LTS) ya no están soportados.
Los usuarios de esa plataforma deben actualizar para poder seguir recibiendo las actualizaciones de I2P.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>La versión 0.9.47 permite una nueva codificación</summary></details><p>La versión 0.9.47 habilita por defecto nuestro nuevo protocolo de cifrado de extremo a extremo (propuesta 144) para algunos servicios.
La herramienta de análisis y bloqueo de Sybil está ahora habilitada por defecto.</p>
<p>Ahora se requiere Java 8 o superior.
Los paquetes de Debian para Wheezy y Stretch, y para Ubuntu Trusty y Precise, ya no están soportados.
Los usuarios de esas plataformas deberían actualizar para poder seguir recibiendo las actualizaciones de I2P</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="Se ha lanzado la versión 0.9.46" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 con correcciones de errores</summary></details><p>La versión 0.9.46 contiene importantes mejoras de rendimiento en la biblioteca de streaming.
Hemos completado el desarrollo del cifrado ECIES (propuesta 144) y ahora hay una opción para habilitarlo para las pruebas.</p>
<p>Sólo para usuarios de Windows:
Esta versión corrige una vulnerabilidad de escalada de privilegios local
que podría ser explotada por un usuario local.
Por favor, aplique la actualización lo antes posible.
Gracias a Blaze Infosec por la divulgación responsable del problema.</p>
<p>Esta es la última versión compatible con Java 7, los paquetes Debian Wheezy y Stretch, y los paquetes Ubuntu Precise y Trusty.
Los usuarios de esas plataformas se deben actualizar para recibir futuras actualizaciones de I2P.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 con correcciones de errores</summary></details><p>La versión 0.9.45 contiene correcciones importantes para el modo oculto y el probador de ancho de banda.
Hay una actualización del tema oscuro de la consola.
Seguimos trabajando en la mejora del rendimiento y en el desarrollo de un nuevo cifrado de extremo a extremo (propuesta 144).</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="Versión 0.9.44" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 con corrección de errores</summary></details><p>0.9.44 contiene una solución importante para un problema de denegación de servicio en la gestión de servicios ocultos de nuevos tipos de cifrado.
Todos los usuarios deben actualizar lo antes posible.</p>
<p>La versión incluye el soporte inicial para la nueva encriptación de extremo a extremo (propuesta 144).
Se sigue trabajando en este proyecto y aún no está listo para su uso.
Hay cambios en la página de inicio de la consola y nuevos reproductores multimedia HTML5 incrustados en i2psnark.
Se incluyen correcciones adicionales para redes IPv6 con cortafuegos.
Las correcciones en la construcción del túnel deberían resultar en un inicio más rápido para algunos usuarios.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="Versión 0.9.43" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 con corrección de errores</summary></details><p>En la versión 0.9.43, continuamos trabajando para mejorar la seguridad, la privacidad y el rendimiento.
Nuestra implementación de la nueva especificación del conjunto de contratos de arrendamiento (LS2) ha finalizado.
Estamos comenzando la implementación de una encriptación de extremo a extremo más fuerte y rápida (propuesta 144) para una futura versión.
Varios problemas de detección de direcciones IPv6 han sido corregidos, y por supuesto hay otros errores corregidos.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 con corrección de errores</summary></details><p>0.9.42 sigue trabajando para que el I2P sea más rápido y fiable.
Incluye varios cambios para acelerar nuestro transporte UDP.
Hemos dividido los archivos de configuración para poder trabajar en el futuro con embalajes más modulares.
Continuamos trabajando para implementar nuevas propuestas para una encriptación más rápida y segura.
Hay, por supuesto, un montón de correcciones de errores también.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 con corrección de errores</summary></details><p>0.9.41 prosigue la labor de aplicación de las nuevas características de la propuesta 123,
incluyendo la autenticación por cliente para conjuntos de contratos de arrendamiento encriptados.
La consola tiene un logotipo I2P actualizado y varios iconos nuevos.
Hemos actualizado el instalador de Linux.</p>
<p>El inicio debería ser más rápido en plataformas como Raspberry Pi.
Hemos corregido varios errores, incluidos algunos graves que afectan a los mensajes de red de bajo nivel.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 con nuevos iconos</summary></details><p>0.9.40 incluye soporte para el nuevo formato cifrado de leaseset.
Desactivamos el antiguo protocolo de transporte NTCP 1.
Hay una nueva característica de importación de SusiDNS y un nuevo mecanismo de filtrado de scripts para las conexiones entrantes.</p>
<p>Hemos hecho muchas mejoras al instalador nativo de OSX, y también hemos actualizado el instalador de IzPack.
El trabajo continúa en la actualización de la consola con nuevos iconos.
Como de costumbre, ¡también hemos arreglado muchos errores!</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 con mejoras en el rendimiento</summary></details><p>0.9.39 incluye amplios cambios para los nuevos tipos de bases de datos de red (propuesta 123).
Hemos incluido el plugin i2pcontrol como webapp para soportar el desarrollo de aplicaciones RPC.
Hay numerosas mejoras de rendimiento y correcciones de errores.</p>
<p>Hemos eliminado los temas de medianoche y clásicos para reducir la carga de mantenimiento;
los usuarios anteriores de esos temas verán ahora el tema oscuro o claro.
También hay nuevos iconos en la página de inicio, un primer paso para actualizar la consola.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 con el nuevo asistente de configuración</summary></details><p>0.9.38 incluye un nuevo asistente de primera instalación con un probador de ancho de banda.
Hemos añadido soporte para el último formato de base de datos GeoIP.
Hay un nuevo instalador de perfiles de Firefox y un nuevo instalador nativo de Mac OSX en nuestro sitio web.
Se sigue trabajando en el soporte del nuevo formato netdb "LS2".</p>
<p>Esta versión también contiene un montón de correcciones de errores, incluyendo varios problemas con los adjuntos susimail, y una solución para enrutadores sólo IPv6.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Informe de Viaje" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P en el 35C3</summary></details><p>El equipo I2P estuvo presente en su mayoría en el 35C3 de Leipzig.
Se celebraron reuniones diarias para revisar el año pasado y cubrir nuestras metas de desarrollo y diseño para 2019.</p>
<p>La Visión del Proyecto y la nueva Hoja de Ruta pueden ser <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">revisadas aquí</a>.</p>
<p>El trabajo continuará en LS2, la Testnet y las mejoras de usabilidad de nuestro sitio web y consola.
Existe un plan para estar en Tails, Debian y Ubuntu Disco. Todavía necesitamos gente que trabaje en las correcciones de Android e I2P_Bote.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Liberado" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 con NTCP2 activado</summary></details><p>Versión 0.9.37 usa un protocolo de transporte más rápido, más seguro que se llama NTCP2. </p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 lanzada" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 con NTCP2 y reparación de errores</summary></details><p>0.9.36 contiene un nuevo protocolo de transporte más seguro llamado NTCP2.
Está desactivado por defecto, pero puede habilitarlo para realizar pruebas añadiendo la <a href="/configadvanced">configuración avanzada</a> <tt>i2np.ntcp2.enable=true</tt> y reiniciando.
NTCP2 se activará en la próxima versión.</p>
<p>Esta versión también contiene varias mejoras de rendimiento y correcciones de errores.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 lanzada" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 con carpetas de SusiMail y asistente de instalación de SSL</summary></details><p>0.9.35 añade soporte para carpetas en SusiMail, y un nuevo Asistente SSL para configurar HTTPS en su sitio web de Servicio Oculto.
También tenemos la habitual colección de correcciones de errores, especialmente en SusiMail.</p>
<p>Estamos trabajando duro en varias cosas para 0.9.36, incluyendo un nuevo instalador de OSX y un protocolo de transporte más rápido y seguro llamado NTCP2.</p>
<p>I2P estará en HOPE en la ciudad de Nueva York, del 20-22 de julio. Encuéntranos y dinos hola!</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="Versión 0.9.34" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 con correcciones de fallos</summary></details><p>¡La 0.9.34 contiene muchas correcciones de fallos!
También tiene mejoras en SusiMail, manejo de IPv6, y selecciòn de contraparte de túnel.
Añadimos soporte para esquemas IGD2 en UPnP.
También hay preparación para más mejoras que verá en futuras versiones.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="Versión 0.9.33" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 con correcciones de fallos</summary></details><p>La 0.9.33 contiene un gran número de correcciones de fallos, incluyendo i2psnark, i2ptunnel, streaming, y SusiMail.
Para aquellos que no pueden acceder a los sitios de resembrado directamente, ahora soportamos varios tipos de proxys para resembrado.
Ahora establecemos límites de tasa de transferencia en el administrador de servicios ocultos.
Para aquellos que ejecutan servidores con alto tráfico, por favor, revisen y ajusten los límites según sea necesario.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown y Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Problemas de seguridad encontrados en casi cualquier sistema</summary></details><p>Se ha encontrado un problema muy serio en CPUs modernas que están instaladas en casi todas las computadoras vendidas por todo el mundo, incluyendo móviles. Esos problemas de seguridad se llaman "Kaiser", "Meltdown", y "Spectre".</p>
<p>El documento técnico (whitepaper) para KAISER/KPTI puede encontrarse bajo <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, el de Meltdown bajo <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, y el de SPECTRE bajo<a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. La primera respuesta de Intel está listada bajo <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>Es importante para nuestros usuarios de I2P actualizar su sistema, en tanto las actualizaciones estén disponibles. Los parches para Windows 10 ya están disponibles, los de Windows 7 y 8 les seguirán pronto. Los parches para MacOS también están ya disponibles. Muchos sistemas Linux también tienen disponible un Kernel más reciente con una corrección incluida. Lo mismo se aplica a Android, cuya reparación de seguridad de 2 enero de 2018 incluye un parche para estos problemas. Por favor, actualice sus sistemas tan pronto como estén disponibles y sea posible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="¡Feliz año nuevo! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Nuevo año e I2P en el 34C3</summary></details><p>¡Feliz año nuevo del equjpo de I2P para todos!</p>
<p>No menos de 7 miembros del equipo de I2P se reuniron en el 34C3 en Leipzig del 27 al 30 de diciembre de 2017. Además de las <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">reuniones</a> en nuestra mesa, nos reunimos con montones de amigos de I2P por todo el lugar. Los resultados de las reuniones ya está publicados en <a href="http://zzz.i2p" target="_blank">zzz.i2p</a>.</p>
<p>También entregamos montones de pegatinas y dimos información acerca de nuestro proyecto a cualquiera que preguntase. Nuestra cena anual de I2P en agradecimiento a todos los asistentes por su continuo apoyo a I2P fue todo un éxito.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="Versión 0.9.32" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 con actualizaciones de consola</summary></details><p>La 0.9.32 contiene varias correcciones en la consola del router I2P y las aplicaciones web asociadas (addressbook, i2psnark, y susimail).
También hemos cambiado la forma en la que manejamos los nombres de servidor configurados para las 'router infos' publicadas, para eliminar algunos ataques de enumeración de red vía DNS.
Hemos añadido algunas comprobaciones en la consola para resistir ataques de reasociación (rebinding).</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="Versión 0.9.31" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 con actualizaciones de consola</summary></details><p>¡Los cambios en esta versión son mucho más advertibles que habitualmente!
Hemos dado un aire fresco a la consola del router I2P para hacerla más fácil de comprender,
hemos mejorado la accesibilidad y el soporte entre distintos navegadores,
y hemos ordenado en general las cosas.
Este es el primer paso en un plan a largo plazo para hacer que la consola del router I2P sea más amable para el usuario.
También hemos añadido valoraciones de torrents y soporte para comentarios a i2psnark.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Llamada para traductores" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>La proxima versión 0.9.31 tiene más cadenas sin traducir de lo que es habitual</summary></details><p>En preparación para la versión 0.9.31, que trae actualizaciones significativas
para la interfaz de usuario, tenemos una colección más grande de lo normal
de cadenas sin traducir que precisan atención. Si es usted un traductor,
apreciaríamos enormemente si pudiera dedicarnos un poco más de tiempo
del habitual durante este ciclo de publicación para nutrir las traducciones con
celeridad. Hemos subido las cadenas pronto para dar tres semanas para
trabajar sobre ellas.</p>
<p>¡Si actualmente no es un traductor de I2P, ahora sería un momento
estupendo para involucrarse! Por favor, vea la
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">Nueva Guía del Traductor</a>
para obtener información sobre cómo empezar a funcionar.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="Versión 0.9.30" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>La versión 0.9.30 actualiza a Jetty 9</summary></details><p>La 0.9.30 contiene una actualización a Jetty 9 y Tomcat 8.
Las versiones anteriores ya no están soportadas, y no están disponibles en las próximas versiones Debian Stretch y Ubuntu Zesty.
El router I2P migrará el fichero de configuración jetty.xml para cada sitio web Jetty a la nueva instalación de Jetty 9.
Esto debe funcionar para configuraciones recientes inalteradas, pero puede no funcionar para instalaciones modificadas o muy antiguas.
Verifique que su sitio web Jetty funciona tras actualizar, y contacte con nosotros en el IRC si necesita asistencia.</p>
<p>Varios complementos no son compatibles con Jetty 9 y deben ser actualizados.
Los siguientes complementos se han puesto al día para funcionar con la 0.9.30, y su router I2P debe actualizarlos tras reiniciar:
i2pbote 0.4.6; zzzot 0.15.0.
Los siguientes complementos (versiones actuales listadas) no funcionarán con la 0.9.30.
Contacte con el desarrollador de complementos correspondiente para conocer el estado de nuevas versiones:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>Esta versión también soporta la migración de los antiguos (2014 y anteriores) servicios ocultos DSA-SHA1 al tipo de firma EdDSA más seguro.
Vea <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> para más información, incluyendo una guía y preguntas frecuentes (FAQ).</p>
<p>Nota: En plataformas ARM no-Android como la Raspberry Pi, la base de datos del blockfile (sistema de nombres) se actualizará al reiniciar, lo que puede tardar varios minutos.
Por favor, tenga paciencia.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="Se ha publicado la 0.9.29" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>La 0.9.29 contiene correcciones de fallos</summary></details><p>La 0.9.29 contiene correcciones para numerosos tickets de Trac, incluyendo soluciones auxiliares para mensajes comprimidos corruptos.
Ahora soportamos NTP sobre IPv6.
Hemos añadido soporte preliminar para Docker.
Ahora tenemos páginas man traducidas.
Ahora pasamos las cabeceras Referer con 'same-origin' (mismo origen) a través del proxy HTTP.
Hay más correcciones para Java 9, aunque aún no recomendamos Java 9 para uso general. </p>
<p>Como es usual, recomendamos que todos los usuarios actualicen a esta versión.
La mejor manera de ayudar a la red y permanecer seguro es ejecutar la última versión.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="Vulnerabilidad de seguridad de I2P-Bote" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>Vulnerabilidad de seguridad de I2P-Bote</summary></details><p>I2P-Bote 0.4.5 corrige una vulnerabilidad de seguridad presente en todas las versiones antiguas del complemento I2P-Bote. La aplicación Android no resultó afectada.</p>
<p>Al mostrar correos electrónicos al usuario, se estaban evitando la mayoría de los campos. Sin embargo, no se evitaban los nombres de fichero de los adjuntos, y se podían usar para
ejecutar código malicioso en un navegador con JavaScript habilitado. Ahora estos nombres se
evitan, y además se ha implementado una Política de Seguridad de Contenidos para todas las páginas.</p>
<p>Todos los usuarios de I2P-Bote serán actualizados automáticamente la primera vez que
reinicien su router I2P después de que I2P 0.9.29 sea publicado a mediados de febrero.
Sin embargo, por seguridad, le recomendamos que <a href="http://bote.i2p/install/">siga las instrucciones de la
página de instalación</a> para actualizar manualmente si planea usar I2P o I2P-Bote antes de esa fecha.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="Se ha publicado la 0.9.28" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>La 0.9.28 contiene correcciones de fallos</summary></details><p>La 0.9.28 contiene correcciones para más de 25 tickets de Trac, y actualizaciones para varios de los paquetes de software integrados, incluido Jetty.
Hay correcciones para la característica de testeado del par IPv6 introducida en la última versión.
Continuamos las mejoras para detectar y bloquear pares que son potencialmente maliciosos.
Hay correcciones preliminares para Java 9, sin embargo aún no recomendamos Java 9 para uso general.</p>
<p>I2P estará en el 33C3, por favor, haga una parada en nuestro puesto y cuéntenos sus ideas sobre cómo mejorar la red.
Revisaremos nuestra hoja de ruta y prioridades para 2017 en este congreso.</p>
<p>Como es usual, recomendamos que todos los usuarios actualicen a esta versión.
La mejor manera de ayudar a la red y permanecer seguro es ejecutar la última versión.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="Vulnerabilidad de seguridad de I2P-Bote" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>Vulnerabilidad de seguridad de I2P-Bote</summary></details><p>I2P-Bote 0.4.4 corrige una vulnerabilidad de seguridad presente en todas las versiones antiguas del
plugin I2P-Bote. La aplicación Android fo estaba afectada.</p>
<p>Una falta de protección contra CSRF (falsificación de petición cruzada de sitio) significaba
que si un usuario estaba ejecutando I2P-Bote y luego cargaba un sitio malicioso en el un
navegador con JavaScript habilitado, el adversario podía desencadenar acciones en
I2P-Bote en nombre del usuario, como enviar mensajes. Esto también podría haber habilitado la extracción de claves privadas para direcciones I2P-Bote, sin embargo no se ha probado ninguna prueba-de-concepto del fallo explotable (exploit) para esto.</p>
<p>Todos los usuarios de I2P-Bote se actualizarán automáticamente la primera vez que
reinicien su router I2P después de que se haya publicado I2P 0.9.28 a mediados de
diciembre. Sin embargo, por seguridad, le recomendamos que <a href="http://bote.i2p/install/">siga las instrucciones
en la página de instalación</a> para actualizar manualmente si planea usar I2P o I2P-Bote
durante el periodo intermedio. También debe considerar generar nuevas direcciones
I2P-Bote si navega regularmente por sitios con JavaScript habilitado mientras ejecuta
I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="Se ha publicado la 0.9.27" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>La 0.9.27 contiene correcciones de fallos</summary></details><p>0.9.27 contiene varias correcciones de fallos.
La librería GMP actualizada para aceleración de la criptografía, que fue empaquetada en la versión 0.9.26 sólo para nuevas instalaciones y versiones (builds) de Debian, ahora está incluida en la actualización desde el interior de la red para la 0.9.27.
Hay mejoras en transportes IPv6, testeo de pares SSU, y modo oculto.</p>
<p>Hemos actualizado varios complementos durante el <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> y su router I2P los actualizará automáticamente tras reiniciar.</p>
<p>Como es usual, recomendamos que todos los usuarios actualicen a esta versión.
La mejor manera de ayudar a la red y permanecer seguro es ejecutar la última versión.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="Propuesta I2P de Stack Exchange" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>¡I2P tiene ahora propuesto un sitio en Stack Exchange!</summary></details><p>¡I2P tiene ahora un sitio propuesto en Stack Exchange! Por favor, <a href="https://area51.stackexchange.com/proposals/99297/i2p">comprométase (commit) a usarlo</a> para que la fase beta pueda comenzar.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="Se ha publicado la 0.9.26" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>La versión 0.9.26 contiene actualizaciones de criptografía, mejoras del empaquetado Debian, y correciones de fallos</summary></details><p>La 0.9.26 contiene una actualización importante de nuestra
librería de criptografía nativa, un nuevo protocolo de
suscripción de libreta de direcciones con firmas, y mejoras
importantes para el empaquetado Debian/Ubuntu.</p>
<p>Para criptografía, hemos actualizado a GMP 6.0.0, y añadido soporte para nuevos procesadores, que acelerarán las operaciones de criptografía considerablemente.
Además, ahora estamos usando funciones GMP de tiempo-constante para prevenir ataques de canal-lateral.
Por precaución, los cambios de GMP sólo están habilitados para nuevas instalaciones
y versiones (builds) Debian/Ubuntu; las incluiremos para actualizaciones
dentro-de-la-red en la versión 0.9.27.</p>
<p>Para versiones (builds) para Debian/Ubuntu, hemos añadido dependencias en varios paquetes, incluyendo Jetty 8 y geoip, y hemos eliminado el código empaquetado equivalente.</p>
<p>Hay también una colección de correcciones de fallos, incluyendo una
corrección para un fallo de cronometrado que causaba inestabilidad
y degradación del rendimiento con el tiempo. Como es habitual,
recomendamos que todos los usuarios se actualicen a esta versión.
La mejor forma de ayudar a la red y permanecer seguro es ejecutar
la última versión.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="Se ha publicado la 0.9.25" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>La versión 0.9.25 contiene SAM 3.3, códigos QR, y correcciones de fallos</summary></details><p>La versión 0.9.25 contiene una nueva versión principal de SAM, v3.3, para soportar aplicaciones multiprotocolo sofisticadas.
Añade códigos QR para compartir direcciones de servicio oculto con otros,
e imágenes "identicon" para distinguir visualmente las direcciones.</p>
<p>Hemos añadido una nueva página de configuración de "familia de router I2P" en la consola,
para facilitar declarar que su grupo de routers I2P está ejecutado por una sola persona.
Hay varios cambios para incrementar la capacidad de la red y con suerte mejorar el establecimiento exitoso de túneles.</p>
<p>Como es usual, recomendamos que todos los usuarios actualicen a esta versión.
La mejor manera de ayudar a la red y permanecer seguro es ejecutar la última versión.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="Se ha publicado la 0.9.24" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>La versión 0.9.24 contiene correcciones para varios errores y mejoras de velocidad</summary></details><p>La versión 0.9.24 contiene una nueva versión de SAM (v3.2), numerosos errores corregidos y mejoras en la eficiencia.
Tenga en cuenta que esta versión es la primera en requerir Java 7.
Por favor, actualice a Java 7 u 8 tan pronto como sea posible.
Su router I2P no actualizará automáticamente si está utilizando Java 6.</p>
<p>Para prevenir los problemas causados por la anciana librería commons-logging, la hemos eliminado.
Esto provocará que los complementos I2P-Bote muy antiguos (0.2.10 y anteriores, firmados por HungryHobo) fallen si tienen habilitado IMAP.
La solución recomendada es reemplazar el complemento I2P-Bote por el actual firmado por str4d.
Para más detalles, vea <a href="http://bote.i2p/news/0.4.3">esta nota</a>.</p>
<p>Tuvimos un gran <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">Congreso 32C3</a> y se están haciendo buenos progresos en nuestros planes para el proyecto de 2016.
Echelon (desarrollador) dio una charla sobre la historia de I2P y su estado actual, y sus presentaciones están <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">aquí</a> (pdf).
Str4d participó en la <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> y dio una charla sobre nuestra cripto-migración, sus presentaciones están <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">aquí</a> (pdf).</p>
<p>Como es usual, recomendamos que todos los usuarios actualicen a esta versión.
La mejor manera de ayudar a la red y permanecer seguro es ejecutar la última versión.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="Se ha publicado la 0.9.23" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>La versión 0.9.23 contiene varias correcciones de errores, y algunas mejoras menores en I2PSnark</summary></details><p>¡Hola, I2P! Esta es la primera versión firmada por mi (str4d) después de 49 versiones firmadas por zzz. Esta es una prueba importante de nuestra redundancia en todos los aspectos, incluyendo el del personal.</p>
<p><b>Mantenimiento interno</b></p>
<p>Mi clave firmante ha estado incluida en las actualizaciones del router I2P desde hace más de dos años (desde la versión 0.9.9), así que si está utilizando una versión reciente de I2P, esta actualización debería ser tan fácil como cualquier otra. Sin embargo, si está utilizando una versión más antigua que la 0.9.9, primero tendrá que actualizar manualmente a una versión más reciente. Los archivos de actualización para las versiones recientes se pueden descargar de <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">aquí</a>, y las instrucciones para actualizar manualmente están <a href="http://i2p-projekt.i2p/es/download#update">aquí</a>. En cuanto haya actualizado manualmente, su router I2P encontrará y descargará la actualización 0.9.23 del modo habitual.</p>
<p>Si instaló I2P por medio de un administrador de paquetes, este cambio no le
afecta, y puede actualizar del modo habitual.</p>
<p><b>Detalles de la actualización</b></p>
<p>La migración de las RouterInfos (datos del router I2P) a unas nuevas, y más
seguras, firmas Ed25519 está yendo bien, se estima que al menos la mitad de
la red ya ha realizado la conversión a estas nuevas firmas. Esta versión
acelera el proceso de renovación de claves. Para reducir la volatilidad de la
red, su router I2P sólo tendrá una pequeña probabilidad de realizar la
conversión a Ed25519 en cada reinicio. Cuando al fin se realice la renovación
de las claves, es probable que vea un menor uso de ancho de banda durante
algunos días, mientras se reintegra a la red con su nueva identidad.</p>
<p>Tenga en cuenta que esta será la última versión que soporte Java 6. Por favor, actualice a Java 7 u 8 lo antes posible. Ya estamos trabajando en hacer I2P compatible con la próxima versión Java 9, y parte de ese trabajo ya viene incluido en esta versión.</p>
<p>También hemos hecho algunos pequeños cambios en I2PSnark, y hemos añadido una nueva página en la consola del router I2P para que muestre los elementos de novedades de consola antiguos.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="Se ha publicado la 0.9.22" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>La versión 0.9.22 corrige fallos e inicia la migración a Ed25519</summary></details><p>La versión 0.9.22 contiene correcciones para i2psnark, que solía quedarse atascado antes de finalizar, y comienza la migración de las RouterInfos (datos del router I2P) a las nuevas y más robustas firmas Ed25519.
Para reducir la volatilidad de la red, su router I2P tendrá sólo una pequeña probabilidad de realizar la conversión a Ed25519 en cada reinicio.
Cuando al fin se realice la renovación de las claves, espere ver un menor uso del ancho de banda durante algunos días hasta que su router I2P se reintegre a la red con su nueva identidad.
Si todo va bien, aceleraremos el proceso de renovación de claves en la próxima versión.</p>
<p>¡La I2PCon de Toronto fue un gran éxito! Todas las presentaciones y vídeos están disponibles en la <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">página de la I2PCon</a>.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="Se ha publicado la 0.9.21" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>Se ha publicado la versión 0.9.21 con mejoras de rendimiento y correcciones de fallos.</summary></details><p>La versión 0.9.21 contiene varios cambios para añadir capacidad a la red, incrementar la eficiencia de los
routers I2P de inundación (floodfills), y usar el ancho de banda con mayor efectividad.
Hemos migrado los túneles de clientes compartidos a firmas ECDSA y hemos añadido un recurso de
contingencia DSA que usa la nueva capacidad "multisession" para aquellos sitios que no soportan ECDSA.</p>
<p>Se han anunciado los oradores y el programa de la I2PCon 2015 de Toronto. Eche un vistazo a la <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">página de la I2PCon</a> para ver los detalles. Reserve su localidad en <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="Se han anunciado los oradores y el programa de la I2PCon de Toronto" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>Se han anunciado los oradores y el programa de la I2PCon 2015 de Toronto</summary></details><p>Se han anunciado los oradores y el programa de la I2PCon 2015 de Toronto. Eche un vistazo a la <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">página de la I2PCon</a> para ver los detalles. Reserve su localidad en <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -1,39 +1,420 @@
<div>
<header title="اخبار I2P">خوراک خبری و به روز رسانی های مسیریاب</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
<header title="اخبار I2P">خوراک خبری و به روز رسانیهای مسیریاب</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 منتشر شد" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 اشکال‌زدایی شد</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 ریلیز شد" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 با اصلاحات باگ ها</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 انتشار یافت" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 با آیکون های جدید</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 انتشار یافت" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 با بهبود عملکرد</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="نسخه 0.9.38 منتشر شد" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 با ویزارد نصب جدید</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P در 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 منتشر شد" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 با NTCP2 فعال شد</summary></details><p>0.9.37 یک پروتکل انتقال امن تر، سریع تر به نام NTCP2 را فراهم می کند.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 ریلیز شد" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 با NTCP2 و اصلاحات باگ ها</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 ریلیز شد" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 با پوشه های SusiMail و ویزارد SSL</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید که بهترین روش برای تامین امنیت و کمک به ارتقا شبکه به آخرین نسخه است.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 ریلیز شد" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 با اصلاحات باگ ها</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید که بهترین روش برای تامین امنیت و کمک به ارتقا شبکه به آخرین نسخه است.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 ریلیز شد" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 با اصلاحات باگ ها</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید که بهترین روش برای تامین امنیت و کمک به ارتقا شبکه به آخرین نسخه است.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER ،Meltdown و Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>مشکلات امنیتی یافت شده تقریبا در هر سیستم</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="سال نو مبارک! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>سال جدید و I2P در 34C3</summary></details><p>تبریک سال نو از تیم I2P به همه!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 ریلیز شد" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 همراه به روز رسانی های کنسول</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید که بهترین روش برای تامین امنیت و کمک به ارتقا شبکه به آخرین نسخه است.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 ریلیز شد" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 همراه به روز رسانی های کنسول</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید که بهترین روش برای تامین امنیت و کمک به ارتقا شبکه به آخرین نسخه است.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
@ -44,7 +425,7 @@ to give you three weeks to work on them.</p>
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 ریلیز شد" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
@ -59,8 +440,8 @@ BwSchedule 0.0.36; i2pcontrol 0.11.</p>
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید که بهترین روش برای تامین امنیت و کمک به ارتقا شبکه به آخرین نسخه است.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 ریلیز شد" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 حاوی اصلاحات باگ ها</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
@ -78,7 +459,7 @@ has been implemented for all pages.</p>
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contains bug fixes</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 ریلیز شد" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 حاوی اصلاحات باگ ها</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
@ -99,7 +480,7 @@ after I2P 0.9.28 is released in mid-December. However, for safety we recommend t
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 ریلیز شد" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 حاوی اصلاحات باگ ها</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
@ -107,7 +488,7 @@ There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p
بهترین روش برای کمک به شبکه و امن ماندن این است که به آخرین نسخه به روز رسانی کنید.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 ریلیز شد" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
@ -164,11 +545,11 @@ does rekey, expect to see lower bandwidth usage for a couple of days as it
reintegrates into the network with its new identity.</p>
<p>توجه داشته باشید که این آخرین نسخه ما است که از جاوا 6 پشتیبانی می‌کند. لطفا هر چه سریع تر به جاوا 7 یا 8 به روز رسانی کنید. ما همچنین در حال کار بر روی I2P برای هماهنگ سازی با نسخه پیش رو جاوا 9 هستیم. برخی از فعالیت‌ها در همین نسخه منتشر شده.</p>
<p>ما همچنین چندین بهینه سازی کوچک در I2PSnark انجام داده ایم و همچنین صفحه جدیدی برای دیدن اخبار قبلی ایجاد کرده ایم.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید که بهترین روش برای تامین امنیت و کمک به ارتقا شبکه به آخرین نسخه است.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 منتشر شد!" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 با اصلاح باگ و شروع مهاجرت از ED25519 اتفاق افتاده.</summary></details><p>0.9.22 شامل اصلاح باگ برای i2psnark است که قبل از اتمام کار از کار می افتد، و همچنین شروع به مهاجرت router infos به نسخه جدید و قوی تر امضا ED25519</p>
<p>I2PCon تورتنو یک موفقیت بزرگ بود!
تمامی ارائه ها و ویدیو ها در <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon صفحه</a> نمایش داده شده اند.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید که بهترین روش برای تامین امنیت و کمک به ارتقا شبکه به آخرین نسخه است.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 منتشر شد!" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 با اصلاح باگ و بهبود عملکرد منتشر شد!</summary></details><p>0.9.21 شامل چندین تغییر به منظور اضافه شدن ظرفیت به شبکه و همچنین بهبود عملکرد روش سیل آسا بوده است.
که از بهنای باند استفاده بهتری نماید.
ما به استفاده از امضا ECDSA برای تونل های مشترک روی آوردیم و همچنین روش بازگشت DSA اضافه شد.
@ -176,7 +557,7 @@ reintegrates into the network with its new identity.</p>
<p>سخنرانان و برنامه زمانی I2PCon 2015 در تورنتو اعلام شد.
برای اطلاعات بیشتر به <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon صفخه</a> نگاهی بیندازید.
برای رزو صندلی <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">رویداد I2PCon</a> مراجعه کنید.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید که بهترین روش برای تامین امنیت و کمک به ارتقا شبکه به آخرین نسخه است.</p>
<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon تورنتو، سخنرانان و برنامه زمانی اعلام شد." href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon تورینتو سال 2015، سخنرانان و برنامه زمانی اعلام شد.</summary></details><p>سخنرانان و برنامه زمانی I2PCon 2015 در تورنتو اعلام شد.
برای اطلاعات بیشتر به <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon صفخه</a> نگاهی بیندازید.
برای رزو صندلی <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">رویداد I2PCon</a> مراجعه کنید.</p>

View File

@ -0,0 +1,605 @@
<div>
<header title="I2P-uutiset">Uutissyöte ja reititinpäivitykset</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="Versio 1.7.0 julkaistu" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>1.7.0-versio sisältää useita suorituskyky- ja luotettavuusparannuksia.</p>
<p>Tehtäväpalkissa näytetään nyt ponnahdusviestejä niillä alustoilla, jotka niitä tukevat.
i2psnark sisältää uuden torrent-muokkaimen.
NTCP2-kuljetus käyttää nyt paljon vähemmän prosessoritehoa.</p>
<p>Pitkään käytöstä poistettuna ollut BOB-rajapinta on poistettu uusista asennuksista.
Se toimii edelleen olemassa olevissa asennuksissa, lukuun ottamatta Debian-paketteja.
Kaikkien jäljellä olevien BOB-sovellusten käyttäjien olisi pyydettävä kehittäjiä siirtymään SAMv3-protokollaan.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
it if you could set aside a little more time than usual during this release cycle
in order to bring the translations up to speed. We have pushed the strings early
to give you three weeks to work on them.</p>
<p>If you're not currently an I2P translator, now would be a great time to get
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
<p>Several plugins are not compatible with Jetty 9 and must be updated.
The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
i2pbote 0.4.6; zzzot 0.15.0.
The following plugins (with current versions listed) will not work with 0.9.30.
Contact the appropriate plugin developer for the status of new versions:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contains bug fixes</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
for this.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
which will speed up crypto operations considerably.
Also, we are now using constant-time GMP functions to prevent side-channel attacks.
For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
we will include them for in-net updates in the 0.9.27 release.</p>
<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
<p>There's a collection of bug fixes also, including a fix for a timer bug
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contains SAM 3.3, QR codes, and bug fixes</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
It adds QR codes for sharing hidden service addresses with others,
and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
to make it easier to declare that your group of routers is run by a single person.
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
Your router will not automatically update if you are using Java 6.</p>
<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration,
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
<p><b>Housekeeping</b></p>
<p>My signing key has been in router updates for over two years (since 0.9.9), so
if you are on a recent version of I2P this update should be just as easy as
every other update. However, if you are running an older version than 0.9.9, you
will first need to manually update to a recent version. Update files for recent
versions can be downloaded
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
and instructions on how to manually update are provided
<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
updated, your router will then find and download the 0.9.23 update as usual.</p>
<p>If you installed I2P via a package manager, you are not affected by the change,
and can update as usual.</p>
<p><b>Update details</b></p>
<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
with at least half of the network already estimated to have rekeyed. This
release accelerates the rekeying process. To reduce network churn, your router
will have a small probability of converting to Ed25519 at each restart. When it
does rekey, expect to see lower bandwidth usage for a couple of days as it
reintegrates into the network with its new identity.</p>
<p>Note that this will be the last release to support Java 6. Please update to
Java 7 or 8 as soon as possible. We are already working to make I2P compatible
with the upcoming Java 9, and some of that work is in this release.</p>
<p>We have also made some minor improvements in I2PSnark, and added a new page in
the routerconsole for viewing older news items.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
and use bandwidth more effectively.
We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
using the new "multisession" capability for those sites that don't support ECDSA.</p>
<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto speakers and schedule announced" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 speakers and schedule announced</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -1,6 +1,336 @@
<div>
<header title="Nouvelles dI2P">Fil de nouvelles et mises à jour du routeur</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="Parution de la version 0.9.35" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 avec des dossiers dans SusiMail et un assistant SSL</summary></details><p>0.9.35 ajoute la prise en charge de dossiers dans SusiMail ainsi qu'un nouvel assistant SSL pour la mise en place de HTTPS pour votre site Web de service caché.
Cette version offre la suite habituelle de correctif de bogues, particulièrement dans SusiMail.</p>
<header title="Nouvelles dI2P">Fil de nouvelles et mises à jour du routeur</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version.
La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version.
La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P version 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P version 2.8.0</summary></details><p>Cette version améliore I2P en corrigeant des bogues, en retirant du code inutilisé, et en améliorant la stabilité du réseau.</p>
<p>Nous avons amélioré la gestion de congestion des routeurs sur le réseau.
Les problèmes avec l'UPnPet le passage de NATont été adressés afin d'améliorer la connectivité et l'envoi d'erreurs.
Nous avons maintenant une stratégie plus agressive pour le retrait des jeux de baux de la BDréseau pour améliorer les performances des routeurs et atténuer leur surcharge.
D'autres changements ont été implémentés pour réduire la visibilité d'évènements comme un routeur redémarrant ou s'éteignant</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version.
La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P version 2.7.0" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P version 2.7.0</summary></details><p>Avec cette version, I2P 2.7.0 continue notre travail sur le réglage de bugs, l'amélioration des performances, et en rajoutant de nouvelles fonctionnalités. </p>
<p>L'accès aux informations depuis le tableau de bord et les applications à été amélioré.
Des erreurs ont été réglé dans la barre de recherche de I2PSnark et SusiMail.
Le netDB embarqué dans le tableau de bord opère fonctionne d'une manière plus utile et plus intuitive.
Plusieures améliorations mineures ont été effectuées dans les écrans de diagnostics dans le mode avancé. </p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version.
La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version.
La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version.
La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version.
La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version.
La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version.
La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version.
La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version.
La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version.
La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version.
La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 sortie" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>Transport SSU2 activé</summary></details><p>La version 2.0.0 d'I2P active nos nouveaux transports UDP SSU2 pour tout les utilisateurs, après la finalisation de petites fonctionnalités, d'essais et de plusieurs correctifs de bug.</p>
<p>Nous avons aussi des correctifs de partout y compris le programme d'installation, la base de données de réseau, ajouts au carnet d'adresse privé, le lanceur de navigateur Windows et IPv6 UPnP.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Billets de blogue récents" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Quelques billets de blogue récents</summary></details><p>Voici des liens vers plusieurs billets de blogue récents sur notre site web :</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Aperçu de notre nouveau transport SSU2</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">Un avertissement sur les jetons I2P et d'autres arnaques</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">Une interview avec Konrad de diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">Une interview avec Dustin de StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 sortie" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 avec SSU2 à tester</summary></details><p>Nous avons passé les trois dernier mois à travailler sur notre nouveau protocole de transport UDP "SSU2"
avec un petit nombre de testeurs bénévole.
Cette sortie complète l'implémentation du relai et le test de pair.
Nous l'activerons par défaut pour les plateformes Android et ARM et aléatoirement sur un petit pourcentage d'autres réseaux.
Cela nous permettra de faire beaucoup plus de tests dans les trois prochain mois, finaliser la fonction de migration de connexion et corriger les problèmes restants.
Nous prévoyons de l'activer pour tout le monde dans la prochaine version prévue pour novembre.
Une configuration manuelle n'est pas nécessaire.</p>
<p>Naturellement, il y a aussi la suite habituelle de correctifs de bogue dans cette version.
Nous avons aussi ajouté un détecteur d'impasse automatique qui a déjà trouvé une impasse rare qui est maintenant corrigée.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="Nouveau mandataire sortant exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>Nouveau mandataire sortant</summary></details><p>Des "mandataires sortants" I2P (nœuds de sortie) peuvent être utilisés pour accéder à Internet à travers
votre tunnel mandataire HTML.
Tel qu'approuvé dans notre <a href="http://i2p-projekt.i2p/en/meetings/314">rendez-vous mensuel</a>,
<b>exit.stormycloud.i2p</b> est désormais notre mandataire sortant officiel et recommandé, remplaçant le <b>false.i2p</b> mort depuis longtemps.
Pour plus d'information sur <a href="http://stormycloud.i2p/">l'organisation</a> StormyCloud,
<a href="http://stormycloud.i2p/outproxy.html">le mandataire sortant</a>,
et les <a href="http://stormycloud.i2p/tos.html">conditions générales d'utilisation</a>,
voir le <a href="http://stormycloud.i2p/">site web StormyCloud</a>.</p>
<p>Nous suggérons que vous changiez votre <a href="/i2ptunnel/edit?tunnel=0">configuration du Gestionnaire de Services Cachés</a>
pour spécifier <b>exit.stormycloud.i2p</b>
en 2 endroits : <b>mandataires sortant</b> et <b>mandataire sortant SSL</b>.
Après modification, <b>défilez vers le bas et cliquer Enregistrer</b>.
Voir notre <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">billet de blogue pour une capture d'écran</a>.
Pour les instructions Android et les capture d'écrans, voir <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">le blogue de notbob</a>.</p>
<p>Les mises à jour de routeur ne se mettront pas à jour votre configuration, vous devez la modifier manuellement.
Merci à StormyCloud pour leur soutien, et s'il-vous plaît, veuillez penser à faire un <a href="http://stormycloud.i2p/donate.html">don</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 sortie" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 avec des correctifs de bogue</summary></details><p>Cette version inclut des correctifs de bogue dans i2psnark,
le routeur, I2CP et UPnP.
Les correctifs de routeur adresse les bogues des redémarrages rapides, IPv6, test de pair SSU,
marchés de base de données de réseau et de construction de tunnel.
Le traitement de la famille de routeur et la classification Sybil ont aussi été
significativement améliorés.</p>
<p>Ensemble avec i2pd, nous sommes en train de développer notre nouveau transport UDP, SSU2.
SSU2 amènera des améliorations substantielles à la performance et la sécurité.
Il nous permettra aussi de remplacer enfin notre dernière utilisation du chiffrement extrêmement lent de ElGamal,
finalisant la mise à niveau de la cryptographie que nous avions commencé il y a maintenant 9 ans.
Cette version contient aussi une implémentation préliminaire qui est désactivé par défaut.
Si vous souhaitez participer au test, veuillez voir nos informations actuelles
sur zzz.i2p.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Installer les mises à jour indispensable Java/Jpackage" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>La vulnérabilité récente des "Signatures Psychiques" Java ont affecté I2P. Les utilisateurs actuels de
I2P sur Linux, ou n'importe quel utilisateur d'I2P qui utilise un MVJ non groupé devrait mettre à jour
leur MVJ ou basculer vers une version qui ne contient pas la vulnérabilité, en dessous de
Java 15.</p>
<p>Les nouveaux paquets I2P facile d'installation ont été générés en utilisant la dernière version de la
Machine Java Virtuelle. Plus d'informations ont été publiés dans les fils de nouveautés des paquets
respectifs</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 sorti" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 avec améliorations de performance et de fiabilité</summary></details><p>La version 1.7.0 contient plusieurs améliorations de performance et de fiabilité.</p>
<p>Il y a désormais des messages contextuels dans la zone de notification, pour les plateformes qui ne les prenait pas en charge.
i2psnarka un nouvel éditeur torrent.
Le transport NTCP2 utilise maintenant beaucoup moins d'UCT.</p>
<p>L'interface BOB depuis longtemps obsolète a été retirée pour de nouvelles installations.
Elle continuera de fonctionner sur les installations existantes, à part les paquets Debian.
Les utilisateurs des applications BOB restants devrait demander aux développeurs de convertir au protocole SAMv3.</p>
<p>Nous savons que depuis notre version 1.6.1, la fiabilité du réseau s'est régulièrement détérioré.
Nous étions conscient du problème peu après la sortie mais cela nous a pris presque deux mois pour trouver la cause.
Nous l'avons éventuellement identifié comme un bogue dans i2pd 2.40.0,
et le correctif sera dans la version 2.41.0 qui sortira à peu près en même temps que cette sortie.
Sur le chemin, nous avons fait plusieurs changement du côté du I2P Java pour améliorer la
robustesse des marchés et des recherches de base de donnée réseau et éviter les pairs peu performants dans la sélection du tunnel de pair.
Cela devrait aider le réseau à être plus robuste même en présence de routeurs boghei ou malicieux.
De plus, nous commençons un programme joint pour tester une version préliminaire des routeurs i2pd et Java I2P
dans un test réseau isolé pour que nous trouvions plus de problèmes avant les sorties et non après.</p>
<p>Dans d'autres nouvelles, nous continuons à progresser sur le design de notre nouveau transport UDP "SSU2 (suggestion 159)
et avons commencer l'implémentation.
SSU2 amènera des améliorations substantielles à la performance et la sécurité.
Cela nous permettra aussi de remplacer enfin notre dernière utilisation du chiffrement extrêmement lent ElGamal,
finalisant la mise à niveau de la cryptographie que nous avions commencé il y a maintenant 9 ans.
Nous nous attendons a commencer les tests joints avec i2pd bientôt, et le sortir sur le réseau plus tard cette année.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 sortie" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 permet de nouveaux messages de construction de tunnel</summary></details><p>Cette version finalise la sortie de deux protocoles majeurs développés en 2021.
La transition au chiffrage X25519 pour les routeurs est accélérée et nous nous attendons à ce que presque tout les routeurs soit ressaisis d'ici la fin de l'année.
Les messages de construction de tunnel courts sont activés pour une réduction de bande passante considérable.</p>
<p>Nous avons ajouté une sélection de panneau de thème au nouveau sorcier d'installation.
Nous avons amélioré la performance SSU et corrigé un problème avec les messages de test pair SSU.
Le filtre de construction de tunnel Bloom a été ajusté pour réduire l'utilisation de la mémoire.
Nous avons amélioré la prise en charge pour les greffons non Java.</p>
<p>Par ailleurs, nous progressons très bien sur le design de notre nouveau transport UDP "SSU2" et son implémentation devrait débuter tôt dans l'année prochaine.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 sortie" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 avec des nouveaux messages de construction de tunnel</summary></details><p>Et oui, après 9 ans de versions 0.9.x, nous allons directement de 0.9.50 à 1.5.0.
Cela ne signifiera pas de changement majeur d'API ou une affirmation que le développement est terminé.
C'est simplement la reconnaissance de presque 20 ans de travail pour fournir de l'anonymat et de la sécurité à nos utilisateurs.</p>
<p>Cette version finalise enfin l'implémentation de plus petits messages de construction de tunnel pour réduire la bande passante.
Nous continuons de transitionner les routeurs réseaux au chiffrement X25519.
Bien sûr il y a aussi de nombreux correctifs de bogues et améliorations de performance.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Vulnérabilité de MuWire pour ordinateur" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Vulnérabilité de MuWire pour ordinateur</summary></details><p>Une faille de sécurité a été découverte dans lapplication MuWire pour ordinateur.
Elle naffecte pas le greffon de la console et nest pas liée au problème de greffon annoncé précédemment.
Si vous utilisez lapplication MuWire pour ordinateur, vous devriez immédiatement <a href="http://muwire.i2p/">la mettre à jour vers la version 0.8.8</a>.</p>
<p>Les détails du problème seront publiés sur <a href="http://muwire.i2p/security.html">muwire.i2p</a>
le 15 juillet 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Vulnérabilité du greffon MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Vulnérabilité du greffon MuWire</summary></details><p>Une faille de sécurité a été découverte dans le greffon MuWire. Elle naffecte pas le client autonome pour ordinateur. Si vous utilisez le greffon MuWire, vous devriez immédiatement <a href="/configplugins">le mettre à jour vers la version 0.8.7-b1</a>.</p>
<p>Consultez <a href="http://muwire.i2p/security.html">muwire.i2p</a>
pour plus de renseignements à propos de cette vulnérabilité, ainsi que des recommandations à jour sur la sécurité.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="Parution de la version 0.9.50" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 avec des correctifs IPv6</summary></details><p>0.9.50 poursuit la transition vers ECIES-X25519 pour les clés de chiffrement du routeur. Nous avons activé le DNS par HTTPS pour le réensemencement afin de protéger les utilisateurs contre la surveillance passive du trafic DNS. Nous trouvons aussi de nombreux correctifs et améliorations pour les adresses IPv6, dont la nouvelle prise en charge dUPnP.</p>
<p>Nous avons enfin corrigé danciens bogues de corruption dans SusiMail. Les changements apportés au limiteur de bande passante devraient améliorer les performances des tunnels réseau. Nous trouvons plusieurs améliorations dans nos conteneurs Docker. Nous avons aussi amélioré nos défenses contre la présence possible de routeurs malveillants ou bogués dans le réseau.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="Parution de la version 0.9.49" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 avec des correctifs SSU et une cryptographie plus rapide</summary></details><p>0.9.49 poursuit le travail afin de rendre I2P plus rapide et plus sûr. Nous avons plusieurs améliorations et correctifs pour le transport SSU (UDP), qui devraient donner des vitesses plus rapides. Cette version commence aussi la migration vers le nouveau chiffrement ECIES-X25519 pour les routeurs (les destinations utilisent déjà ce nouveau chiffrement depuis quelques versions). Nous travaillons depuis plusieurs années sur les spécifications et les protocoles de ce nouveau chiffrement, et nous approchons de la fin du tunnel. Plusieurs versions seront nécessaires pour achever la migration.</p>
<p>Pour cette version, afin de réduire les perturbations au minimum, seuls les nouvelles installations et un très faible pourcentage des installations existantes (sélectionnées au hasard au redémarrage) utiliseront le nouveau chiffrement. Si votre routeur régénère une clé afin dutiliser le nouveau chiffrement, il pourrait avoir moins de trafic et être moins fiable que dhabitude pendant plusieurs jours après redémarrage. Cela est normal, car votre routeur a généré une nouvelle identité. Vos performances devraient se rétablir après un certain temps.</p>
<p>Nous avons régénéré une clé pour le réseau deux fois auparavant, lors du changement de type de signature par défaut, mais cest la première fois que nous avons changé le type de chiffrement par défaut. Nous espérons que tout ira bien, mais nous commençons lentement, par prudence.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="Parution de la version 0.9.48" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 avec amélioration des performances</summary></details><p>0.9.48 met en œuvre notre nouveau protocole de chiffrement de bout en bout (proposition 144) pour la plupart des services. Nous avons ajouté la prise en charge préliminaire du chiffrement des messages de construction de nouveaux tunnels (proposition 152). Le routeur reçoit dimportantes améliorations des performances.</p>
<p>Les paquets pour Ubuntu Xenial (16.04 LTS) ne sont plus pris en charge. Les utilisateurs de cette plateforme devraient la mettre à niveau afin de recevoir les futures mises à jour dI2P.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="Parution de la version 0.9.47" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 permet un nouveau chiffrement</summary></details><p>0.9.47 Notre nouveau protocole de chiffrement de bout en bout est activé par défaut (proposition 144) pour certains services. Loutil danalyse et de blocage Sybil est désormais activé par défaut.</p>
<p>Java 8 ou version ultérieure est maintenant exigée. Les paquets Debian pour Wheezy et Stretch, ainsi que les paquets Ubuntu Precise et Trusty ne sont plus pris en charge. Les utilisateurs de ces plateformes devraient les mettre à niveau afin de recevoir les futures mises à jour dI2P.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="Parution de la version 0.9.46" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 avec des correctifs de bogues</summary></details><p>0.9.46 présente des améliorations significatives des performances de la bibliothèque de diffusion en continu.
Nous avons mené à bien le développement du chiffrement ECIES (proposition 144) et une option est maintenant offerte afin de lactiver à des fins de test.</p>
<p>Pour les utilisateurs de Windows seulement : cette version corrige une vulnérabilité descalade des privilèges locaux, qui pourrait être exploitée par un utilisateur local.
Veuillez appliquer la mise à jour dès que possible.
Nos remerciements à Blaze Infosec pour la divulgation responsable de ce problème.</p>
<p>Cette version est la dernière à prendre en charge Java 7, les paquets Debian Wheezy et Stretch, ainsi que les paquets Ubuntu Precise et Trusty. Les utilisateurs de ces plateformes doivent les mettre à niveau afin de recevoir les futures mises à jour dI2P.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="Parution de la version 0.9.45" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 avec des correctifs de bogues</summary></details><p>La version 0.9.45 comprend des correctifs importants pour le mode caché et le testeur de bande passante. Le thème sombre de la console a été mis à jour. Nos efforts continus ciblent lamélioration des performances et le développement du nouveau chiffrement de bout en bout (proposition 144).</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="Parution de la version 0.9.44" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 avec des correctifs de bogues</summary></details><p>0.9.44 comprend un correctif important dun problème de déni de service dans la gestion des services cachés de nouveaux types de chiffrement. Tous les utilisateurs devraient effectuer une mise à jour dès que possible.</p>
<p>Cette version comprend la prise en charge initiale dun nouveau chiffrement de bout en bout (proposition 144).
Le travail sur ce projet se poursuit et il nest pas encore prêt à être utilisé. La page daccueil de la console reçoit des changements et i2psnark des lecteurs multimédias HTML5 intégrés. Nous avons aussi des correctifs supplémentaires pour les réseaux IPv6 qui se trouvent derrière des pare-feu. Des correctifs apportés à la construction de tunnels devraient entraîner des démarrages plus rapides pour certains utilisateurs.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="Parution de la version 0.9.43" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 avec des correctifs de bogues</summary></details><p>Dans la version 0.9 43, nous poursuivons nos efforts pour livrer une sécurité et des options de confidentialité et de protection des données personnelles plus robustes, ainsi que des améliorations des performances. Notre mise en œuvre de la nouvelle spécification de jeu de baux (LS2) est maintenant achevée. Nous commençons la mise en œuvre dun chiffrement de bout en bout plus robuste et plus rapide (proposition 144) pour une version à venir. Plusieurs problèmes de détection des adresses IPv6 ont été corrigés, et bien sûr, de nombreux bogues ont été corrigés.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="Parution de la version 0.9.42" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 avec des correctifs de bogues</summary></details><p>0.9.42 poursuit le travail pour rendre I2P plus rapide et plus fiable. Elle comprend plusieurs changements pour accélérer notre transport UDP. Nous avons séparé les fichiers de configuration afin de permettre à lavenir des paquets plus modulaires. Nous poursuivons nos efforts afin de mettre en œuvre de nouvelles propositions de chiffrement plus rapide et plus sécurisé. Et bien sûr, il y a de nombreux correctifs de bogues.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="Parution de la version 0.9.41" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 avec des correctifs de bogues</summary></details><p>0.9.41 poursuit leffort de mise en place de nouvelles fonctions pour la proposition 123, dont une authentification par client pour les jeux de baux chiffrés. La console offre un logo dI2P mis à jour et plusieurs nouvelles icônes. Nous avons mis à jour le programme dinstallation pour Linux.</p>
<p>Le démarrage devrait être plus rapide sur les plateformes telles que le Raspberry Pi. Nous avons corrigé plusieurs bogues, dont certains importants qui affectaient les messages de bas niveau du réseau.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="Parution de la version 0.9.40" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 avec de nouvelles icônes</summary></details><p>0.9.40 comprend la prise en charge du nouveau format chiffré de jeux de baux. Nous avons désactivé lancien protocole de transport NTCP 1. SusiDNS offre une nouvelle fonction dimportation et un nouveau mécanisme de filtrage par script pour les connexions entrantes.</p>
<p>Nous avons apporté de nombreuses améliorations au programme dinstallation natif OS X et nous avons aussi mis à jour le programme dinstallation IzPack. Leffort dactualisation de la console continue avec de nouvelles icônes. Comme dhabitude, nous avons aussi corrigé de nombreux bogues.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="Parution de la version 0.9.39" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 avec amélioration des performances</summary></details><p>0.9.39 comprend des changements profonds pour les nouveaux types de base de données de réseau (proposition 123).
Nous avons intégré le greffon i2pcontrol en tant quappli Web pour soutenir le développement des applications RPC.
Il y a de nombreuses améliorations des performances et des correctifs de bogues.</p>
<p>Nous avons supprimé les thèmes minuit et classique afin de réduire la charge de maintenance; ceux qui les utilisaient verront maintenant le thème sombre ou clair.
De nouvelles icônes voient le jour pour la page daccueil, une première étape vers la mise à jour de la console.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="Parution de la version 0.9.38" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 avec un nouvel assistant de configuration</summary></details><p>0.9.38 comprend un nouvel assistant de première installation avec un testeur de bande passante.
Nous avons ajouté la prise en charge du format de base de données GeoIP le plus récent.
Un nouveau programme dinstallation de profil Firefox est proposé, ainsi quun nouveau programme dinstallation natif macOS sur notre site Web.
Nous continuons de travailler sur la prise en charge du nouveau format de BDréseau « LS2 ».</p>
<p>Cette version comprend aussi une multitude de correctifs de bogues, dont de nombreux problèmes avec les fichiers joints dans SusiMail, ainsi quun correctif pour les routeurs IPv6-seulement.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="Compte-rendu de notre visite au 35C3" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P au 35C3</summary></details><p>Presque toute léquipe dI2P était présente au 35C3 de Leipzig.
Des rencontres quotidiennes ont eu lieu pour examiner lannée passée et discuter de nos objectifs de développement et de conception pour 2019.</p>
<p>La vision et la feuille de route du projet peuvent être <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">examinées ici</a>.</p>
<p>Le travail continuera sur LS2, sur le réseau de test et sur les améliorations apportées à la convivialité de notre site Web et de la console.
Il est prévu que nous soyons présents dans Tails, Debian et Ubuntu Disco. Nous avons encore besoin de contributeurs pour travailler sur les correctifs pour Android et I2P_Bote.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="Parution de la version 0.9.37" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 avec activation de NTCP2</summary></details><p>0.9.37 active un protocole de transport plus rapide et plus sécurisé appelé NTCP2.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="Parution de la version 0.9.36" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 avec NTCP2 et des correctifs de bogues</summary></details><p>0.9.36 présente un nouveau protocole de transport plus sécurisé appelé NTCP2. Il est désactivé par défaut, mais vous pouvez l'activer pour le tester en ajoutant la <a href="/configadvanced">configuration avancée</a> <tt>2np.ntcp2.enable=true</tt> et en redémarrant.
NTCP2 sera activé dans la prochaine version.</p>
<p>Cette version présente aussi plusieurs améliorations des performances et des correctifs de bogues.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="Parution de la version 0.9.35" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 avec des dossiers dans SusiMail et un assistant SSL</summary></details><p>0.9.35 ajoute la prise en charge de dossiers dans SusiMail ainsi qu'un nouvel assistant SSL pour la mise en place de HTTPS pour votre site Web de service caché.
Cette version offre aussi la suite habituelle de correctif de bogues, particulièrement dans SusiMail.</p>
<p>Nous travaillons très fort sur plusieurs choses pour 0.9.36, dont un nouveau programme dinstallation pour macOS et un protocole de transport plus rapide et plus sécurisé appelé NTCP2.</p>
<p>I2P sera présent à HOPE à New York du 20 au 22 juillet. Trouvez-nous y et dites-nous bonjour!</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
@ -16,13 +346,12 @@ Pour ceux qui exploitent des serveurs à trafic élevé, veuillez réviser et r
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown et Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Failles de sécurité se trouvant dans presque tous les systèmes</summary></details><p>Des failles très graves ont été découvertes dans les UCT modernes qui se trouvent dans presque tous les ordinateurs vendus dans le monde entier, dont les appareils mobiles. Ces failles de sécurité se nomment « Kaiser », « Meltdown » et « Spectre ».</p>
<p>Les documents de présentation technique (en anglais) peuvent être consultés ici :
<a href="https://gruss.cc/files/kaiser.pdf" target="_blank">Kaiser.pdf</a> pour KAISER/KPTI, <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a> pour Meltdown et <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a> pour Spectre. La première réaction dIntel se trouve href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank"&gt;ici.
</p>
<a href="https://gruss.cc/files/kaiser.pdf" target="_blank">Kaiser.pdf</a> pour KAISER/KPTI, <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a> pour Meltdown et <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a> pour Spectre. La première réaction dIntel se trouve <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">ici</a>.</p>
<p>Il est important pour les utilisateurs dI2P de mettre leur système à jour tant que des mises à jour seront proposées. Des correctifs pour Windows 10 sont dores et déjà proposés, ceux pour Windows 7 et 8 suivront bientôt. Des correctifs pour macOS sont déjà proposés aussi. De nombreux systèmes Linux proposent à leur tour un nouveau noyau incluant un correctif. Il en est de même pour Android dont le correctif de sécurité du 2 janvier 2018 corrige ces problèmes.
Veuillez mettre vos système à jour dès que possible et au fur et à mesure.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Bonne année! 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Nouvelle année et I2P au 34C3</summary></details><p>Bonne année à tous, de la part de léquipe dI2P!</p>
<p>Pas moins de sept membres de léquipe dI2P se sont rencontrés au 34C3 à Leipzig du 27 au 30 décembre 2017. En plus des <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3%C2%A0%C2%BB%20target=" _blank>réunions</a> à notre table, nous avons rencontré un peu partout de nombreux amis dI2P.
Les résultats de ces réunions sont déjà publiés sur <a href="http://zzz.i2p%C2%A0%C2%BB%20target=" _blank>zzz.i2p</a>.</p>
<p>Pas moins de sept membres de léquipe dI2P se sont rencontrés au 34C3 à Leipzig du 27 au 30 décembre 2017. En plus des <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">réunions</a> à notre table, nous avons rencontré un peu partout de nombreux amis dI2P.
Les résultats de ces réunions sont déjà publiés sur <a href="http://zzz.i2p" target="_blank">zzz.i2p</a>.</p>
<p>Nous avons aussi distribué de nombreux autocollants et donné des informations sur notre projet à tous ceux qui en demandaient.
Notre dîner annuel I2P connut un franc succès, en remerciement à tous les participants pour leur soutien continu.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="Parution de la version 0.9.32" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 avec des mises à jour de la console</summary></details><p>0.9.32 contient plusieurs correctifs dans la console du routeur et les applis Web connexes (carnet dadresses, 2psnark et susimail).
@ -35,7 +364,7 @@ Cest la première étape dun plan à long terme visant à rendre la consol
Nous avons aussi ajouté à i2psnark la prise en charge de lévaluation des torrents et des commentaires.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Recherche de traducteurs" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>La version 0.9.31 à venir a plus de chaînes non traduites que dhabitude</summary></details><p>En préparation à la version 0.9.31 qui comporte des mises à jour importantes de linterface utilisateur, un plus grand nombre de chaînes non traduites a besoin dattention. Si vous êtes un traducteur, nous apprécierions grandement si vous pouviez consacrer un peu plus de temps que dhabitude à ce cycle de parution afin de compléter les traductions. Les chaînes ont été poussées tôt afin de vous donner trois semaines pour y travailler.</p>
<p>Si vous nêtes pas actuellement un traducteur dI2P, cest le moment de vous impliquer ! Veuillez consulter le <a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">guide du nouveau traducteur</a> qui vous expliquera comment débuter.</p>
<p>Si vous nêtes pas actuellement un traducteur dI2P, cest le moment de vous impliquer! Veuillez consulter le <a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">guide du nouveau traducteur</a> qui vous expliquera comment débuter.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="Parution de la version 0.9.30" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>Mise à niveau de 0.9.30 vers Jetty 9</summary></details><p>0.9.30 contient une mise à niveau vers Jetty 9 et Tomcat 8.
Les versions précédentes ne sont plus prises en charge et ne sont pas proposées dans les prochaines versions de Debian Stretch ni dUbuntu Zesty.
Le routeur migrera le fichier de configuration jetty.xml de chaque site Web Jetty vers la nouvelle configuration Jetty 9.
@ -48,7 +377,7 @@ Contactez le développeur de greffon compétent pour connaître létat des no
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>Cette version prend aussi en charge la migration des anciens (2014 et antérieurs) services cachés DSA-SHA1 vers le type de signature plus sécurisé EdDSA.
Voir <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> pour de plus amples informations, incluant guide et FAQ.</p>
<p>Notez : sur les plateformes ARM non Android telles que le Raspberry Pi, la base de données blockfile se mettra à jour lors du redémarrage, ce qui pourrait prendre quelques minutes.
<p>Notez : sur les plateformes ARM non Android telles que le Raspberry Pi, la base de données blockfile se mettra à jour lors du redémarrage, ce qui pourrait prendre quelques minutes.
Soyez patient.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="Parution de la version 0.9.29" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contient des correctifs de bogues</summary></details><p>v0.9.29 contient des correctifs pour de nombreux billets de Trac, y compris des solutions de contournement pour les messages compressés corrompus.
@ -60,7 +389,7 @@ Il y a dautres correctifs pour Java 9, bien que nous ne recommandions pas enc
<p>Comme dhabitude, nous recommandons que tous les utilisateurs mettent à jour I2P vers cette version.
La meilleure façon daider le réseau et de maintenir la sécurité est dexécuter la dernière version.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="Faille de sécurité dI2P-Bote" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>Faille de sécurité dI2P-Bote</summary></details><p>I2P-Bote 0.4.5 corrige une faille de sécurité présente dans toutes les versions précédentes du greffon I2P-Bote. Lappli pour Android nétait été affectée.</p>
<p>Lors de laffichage de courriels à lutilisateur, la plupart des champs étaient échappés. Cependant, les noms de fichier des pièces jointes nétaient pas échappés et pouvaient être utilisés pour exécuter du code malveillant dans un navigateur où JavaScript était activé. Ils sont maintenant échappés et une politique de sécurité du contenu a en plus été mise en œuvre pour toutes les pages.</p>
<p>Lors de laffichage de courriels à lutilisateur, la plupart des champs étaient échappés. Cependant, les noms de fichier des fichiers joints nétaient pas échappés et pouvaient être utilisés pour exécuter du code malveillant dans un navigateur où JavaScript était activé. Ils sont maintenant échappés et une politique de sécurité du contenu a en plus été mise en œuvre pour toutes les pages.</p>
<p>Tous les utilisateurs dI2P-Bote seront automatiquement mis à niveau la première fois quils redémarreront leur routeur après parution dI2P 0.9.29 à la mi-février. Cependant, pour des raisons de sécurité, nous recommandons que vous <a href="http://bote.i2p/install/">suiviez les instructions sur la page dinstallation</a> afin de la mettre à niveau manuellement si vous prévoyez utiliser I2P ou I2P-Bote entre temps.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="Parution de la version 0.9.28" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contient des correctifs de bogues</summary></details><p>0.9.28 contient des correctifs pour plus de 25 billets Trac et des mises à jour pour un certain nombre de logiciels intégrés y compris Jetty.
Il y a des correctifs pour la fonction de test de pairs en IPv6 présentée dans la dernière version.
@ -79,20 +408,20 @@ Il y a des améliorations des transports IPv6, du test de pairs SSU et du mode c
<p>Nous avons mis à jour plusieurs greffons durant l<a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">été I2P</a> et votre routeur les mettra à jour automatiquement après redémarrage.</p>
<p>Comme dhabitude, nous recommandons que tous les utilisateurs mettent à jour I2P vers cette version.
La meilleure façon daider le réseau et de maintenir la sécurité est dexécuter la dernière version.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="Proposition dI2P sur « Stack Exchange »" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P est maintenant un site proposé sur « Stack Exchange » !</summary></details><p>I2P est maintenant un site proposé sur « Stack Exchange » !
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="Proposition dI2P sur « Stack Exchange »" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P est maintenant un site proposé sur « Stack Exchange » !</summary></details><p>I2P est maintenant un site proposé sur « Stack Exchange » !
Veuillez <a href="https://area51.stackexchange.com/proposals/99297/i2p">vous engager à lutiliser</a> afin que la phase bêta puisse commencer.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="Parution de la version 0.9.26" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contient des mises à jour cryptographiques, des améliorations de lempaquetage pour Debian et des correctifs de bogues</summary></details><p>0.9.26 contient une mise à niveau importante de notre bibliothèque cryptographique native, un nouveau protocole dabonnement de carnet dadresses avec signatures et des améliorations importantes de lempaquetage Debian et Ubuntu.</p>
<p>Concernant la cryptographie, nous sommes passé à GMP 6.0.0 et nous avons ajouté la prise en charge de processeurs plus récents ce qui accélérera considérablement les opérations cryptographiques.
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="Parution de la version 0.9.26" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contient des mises à jour cryptographiques, des améliorations de lempaquetage pour Debian et des correctifs de bogues</summary></details><p>0.9.26 contient une mise à niveau importante de notre bibliothèque cryptographique native, un nouveau protocole dabonnement à des carnets dadresses avec signatures et des améliorations importantes de lempaquetage Debian et Ubuntu.</p>
<p>Concernant la cryptographie, nous sommes passés à GMP 6.0.0 et nous avons ajouté la prise en charge de processeurs plus récents ce qui accélérera considérablement les opérations cryptographiques.
De plus, nous utilisons maintenant des fonctions GMP en temps constant afin dempêcher les attaques par canal auxiliaire.
Par précaution, les changements dans GMP seront seulement activés pour les nouvelles installations et les versions Debian ou Ubuntu ;
nous les inclurons avec les mises à jour intraréseau dans la version 0.9.27.</p>
Par précaution, les changements dans GMP seront seulement activés pour les nouvelles installations et les versions Debian ou Ubuntu;
nous les inclurons avec les mises à jour intraréseau dans la version 0.9.27.</p>
<p>Pour les versions Debian ou Ubuntu, nous avons ajouté des dépendances vers plusieurs paquets, dont Jetty 8 et geoip et nous avons supprimé le code intégré équivalent.</p>
<p>Il y a aussi une collection de correctifs de bogues, y compris un correctif de bogue de minuteur qui causait de linstabilité et une dégradation des performances au fil du temps.
Comme dhabitude, nous recommandons que tous les utilisateurs mettent à jour I2P vers cette version.
La meilleure façon daider le réseau et de maintenir la sécurité est dexécuter la dernière version.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="Parution de la version 0.9.25" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contient SAM 3.3, les codes QR et des correctifs de bogues</summary></details><p>0.9.25 contient une nouvelle version majeure de SAM, la v3.3, pour prendre en charge les applications multiprocotoles sophistiquées.
Elle ajoute des codes QR pour partager les adresses des services cachés avec dautres et des images « identicône » afin de distinguer les adresses visuellement.</p>
<p>Nous avons ajouté une nouvelle page de configuration «&nbsp;famille de routeurs&nbsp;» à la console, afin quil soit plus facile de déclarer que votre groupe de routeurs est exploité par une seule personne.
Elle ajoute des codes QR pour partager les adresses des services cachés avec dautres et des images « identicône » afin de distinguer les adresses visuellement.</p>
<p>Nous avons ajouté une nouvelle page de configuration « famille de routeurs » à la console, afin quil soit plus facile de déclarer que votre groupe de routeurs est exploité par une seule personne.
Il y a plusieurs changements afin daugmenter la capacité du réseau et avec un peu de chance améliorer le taux de réussite des constructions de tunnels.</p>
<p>Comme dhabitude, nous recommandons que tous les utilisateurs mettent à jour I2P vers cette version.
La meilleure façon daider le réseau et de maintenir la sécurité est dexécuter la dernière version.</p>
@ -103,34 +432,34 @@ Votre routeur ne se mettra pas automatiquement à jour si vous utilisez Java 6.<
<p>Pour empêcher les problèmes causés par la très ancienne bibliothèque commons-logging, nous lavons enlevée.
Cela causera le plantage des très anciens greffons I2P-Bote (0.2.10 et antérieur, signés par HungryHobo) sils ont activé IMAP.
Le correctif recommandé consiste à remplacer votre ancien greffon I2P-Bote par lactuel signé par str4d.
Pour plus de détails, consulter <a href="http://bote.i2p/news/0.4.3">ce article</a>.</p>
Pour plus de précisions, consulter <a href="http://bote.i2p/news/0.4.3">ce article</a>.</p>
<p>Nous avons eu un très bon <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">congrès 32C3</a> et nous progressons avec nos projets pour 2016.
Echelon a donné une conférence concernant lhistoire dI2P et son état actuel et ses diapos sont <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">ici</a> (pdf).
Str4d a participé à <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> et a donné une conférence sur notre migration cryptographique,
ses diapos sont <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">ici</a> (pdf).</p>
<p>Comme dhabitude, nous recommandons que tous les utilisateurs mettent à jour I2P vers cette version.
La meilleure façon daider le réseau et de maintenir la sécurité est dexécuter la dernière version.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="Parution de la version 0.9.23" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contient divers correctifs de bogues et des améliorations mineures dans I2PSnark</summary></details><p>Bonjour I2P ! Ceci est la première version signée par moi (str4d), après 49 versions signées par zzz. Cest un test important de notre redondance pour tout, y compris les personnes.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="Parution de la version 0.9.23" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contient divers correctifs de bogues et des améliorations mineures dans I2PSnark</summary></details><p>Bonjour I2P! Ceci est la première version signée par moi (str4d), après 49 versions signées par zzz. Cest un test important de notre redondance pour tout, y compris les personnes.</p>
<p><b>Gestion interne</b></p>
<p>Ma clé de signature est présente dans les mises à jour du routeur depuis plus de deux ans (depuis 0.9.9), donc si vous utilisez une version récente dI2P, cette mise à jour devrait être aussi facile que nimporte quelle autre mise à jour. Cependant, si vous exécutez une version antérieure à 0.9.9, vous devrez dabord passer manuellement à une version récente. Les fichiers de mise à jour des versions récentes peuvent être téléchargés
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">ici</a> et les instructions de mise à jour manuelle se trouvent <a href="http://i2p-projekt.i2p/fr/download#update">ici</a>. Une fois que vous aurez mis votre version à jour manuellement, votre routeur trouvera et téléchargera alors la mise à jour 0.9.23 comme dhabitude.</p>
<p>Si vous avez installé I2P grâce à un gestionnaire de paquets, vous nêtes pas affectés par le changement et pouvez mettre votre version à jour comme dhabitude.</p>
<p><b>Détails sur la mise à jour</b></p>
<p>La migration dInfosRouteur vers de nouvelles signatures Ed25519 plus robustes se passe bien et il est estimé quau moins la moitié du réseau utilise déjà les nouvelles signatures. Cette version accélère ce processus. Afin de réduire le taux de désabonnement du réseau, votre routeur aura une faible probabilité de conversion à Ed25519 lors de chaque redémarrage. Lorsquil utilisera les nouvelles signatures, attendez-vous à voir une utilisation moindre de la bande passante pendant quelques jours alors quil réintègre le réseau avec sa nouvelle identité.</p>
<p>La migration dInfosRouteur vers de nouvelles signatures Ed25519 plus robustes se passe bien et il est estimé quau moins la moitié du réseau utilise déjà les nouvelles signatures. Cette version accélère ce processus. Afin de réduire le taux de désabonnement du réseau, votre routeur aura une faible probabilité de conversion à Ed25519 lors de chaque redémarrage. Une fois que les clés seront régénérées, attendez-vous à voir une utilisation moindre de la bande passante pendant quelques jours alors quil réintègre le réseau avec sa nouvelle identité.</p>
<p>Noter que cette version sera la dernière à prendre Java 6 en charge. Veuillez mettre votre Java à jour vers Java 7 ou 8 dès que possible. Nous nous efforçons déjà de rendre I2P compatible avec le futur Java 9 et une partie de ce travail est présente dans cette version.</p>
<p>Nous avons aussi effectué quelques améliorations mineures dans I2PSnark et avons ajouté une nouvelle page dans la console du routeur afin de visualiser les anciennes nouvelles.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="Parution de la version 0.9.22" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 avec des correctifs de bogues et le début de la migration vers Ed25519</summary></details><p>0.9.22 contient des correctifs pour I2PSnark qui se bloquait avant la fin des téléchargements et débute la migration des infos du routeur vers des signatures Ed25519 nouvelles et plus robustes. Afin de réduire le taux de désabonnement du réseau, votre routeur aura une faible probabilité de conversion à Ed25519 lors de chaque redémarrage. Lorsquil utilisera les nouvelles signatures, attendez-vous à voir une utilisation moindre de la bande passante pendant quelques jours alors quil réintègre le réseau avec sa nouvelle identité. Si tout se passe bien, nous accélérerons le processus de régénération de clés lors de la prochaine version.</p>
<p>I2PCon Toronto a été un grand succès ! Toutes les présentations et vidéos sont listées sur la <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">page dI2PCon</a>.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="Parution de la version 0.9.22" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 avec des correctifs de bogues et le début de la migration vers Ed25519</summary></details><p>0.9.22 contient des correctifs pour I2PSnark qui se bloquait avant la fin, et commence la migration des renseignements du routeur vers des signatures Ed25519 nouvelles et plus robustes. Afin de réduire le taux de désabonnement du réseau, votre routeur aura une faible probabilité de conversion à Ed25519 lors de chaque redémarrage. Une fois que les clés seront régénérées, attendez-vous à voir une utilisation moindre de la bande passante pendant quelques jours alors quil réintègre le réseau avec sa nouvelle identité. Si tout se passe bien, nous accélérerons le processus de régénération de clés lors de la prochaine version.</p>
<p>I2PCon Toronto a été un grand succès! Toutes les présentations et vidéos sont listées sur la <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">page dI2PCon</a>.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="Parution de la version 0.9.21" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 est parue avec des améliorations des performances et des correctifs de bogues.</summary></details><p>0.9.21 contient plusieurs changements pour ajouter de la capacité au réseau, augmenter lefficacité du remplissage par diffusion et utiliser la bande passante plus efficacement.
Nous avons migré les tunnels client partagés vers des signatures ECDSA et avons ajouté un repli DSA utilisant la nouvelle capacité « multisession » pour les sites qui ne prennent pas ECDSA en charge.</p>
Nous avons migré les tunnels client partagés vers des signatures ECDSA et avons ajouté un repli DSA utilisant la nouvelle capacité « multisession » pour les sites qui ne prennent pas ECDSA en charge.</p>
<p>Les orateurs et le calendrier dI2PCon Toronto 2015 ont été annoncés.
Consulter la <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">page dI2PCon</a> pour plus de détails.
Consulter la <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">page dI2PCon</a> pour plus de précisions.
Réservez votre siège sur <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>Comme dhabitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et daider le réseau est dexécuter la dernière version.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="Les orateurs et le calendrier dI2PCon Toronto ont été annoncés" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>Les orateurs et le calendrier dI2PCon Toronto 2015 ont été annoncés</summary></details><p>Les orateurs et le calendrier dI2PCon Toronto 2015 ont été annoncés.
Consulter la <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">page dI2PCon</a> pour plus de détails.
Consulter la <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">page dI2PCon</a> pour plus de précisions.
Réservez votre siège sur <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -0,0 +1,522 @@
<div>
<header title="I2P 新聞">新闻订阅和软件更新</header><article id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a" title="2.9.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released" author="idk" published="2025-06-02T19:00:00Z" updated="2025-06-02T19:00:00Z"><details><summary>I2P 2.9.0 版本</summary></details><p>I2P 2.9.0 是一个维护版本,包括错误修复和新功能开发。</p>
<p>改进了线程使用以提高 i2ptunnel 系统的性能。改进了 NTCP2 以抵御探测攻击。通知系统已集成到更多应用程序中,以便从 I2PSnark 和其他应用程序向用户提供更好的反馈。修复了自动播种注册问题。用户在充当播种时可能会观察到更多的资源使用情况。如果不希望出现这种情况,可在 /config 页面上禁用播种模式。</p>
<p>控制台中新增了全局地图功能,可在网络数据库视图中显示路由器位置。这些都是帮助路由器建立隧道和匿名提供服务的对等节点。</p>
<p>关于隧道的自动带宽管理、数据报 2 协议和后量子密码学的实现工作仍在继续。在两个版本后,即 2.11.0I2P 将需要 Java 17。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 版本</summary></details><p>2.8.2 修复了在 2.8.1 版本中引入的导致 SHA256 失败的错误。
该错误主要影响高带宽路由器。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 版本</summary></details><p>2.8.1 修复了 2.8.0 中出现问题的本地站点访问问题。
我们在控制台中为多个应用程序添加了通知气泡,以突出显示应用的消息。
我们修复了可能影响隧道可靠性的隧道测试错误。
地址簿现在有一个新的“最新”选项卡,显示从您的订阅中添加的最新主机名。
对暗色主题进行了若干处修复和改进。</p>
<p>我们修复了之前在 Java 21 或更高版本上失败的安装程序。
我们还修复了在 Linux 上安装到包含空格的目录路径出现的问题。
对于使用 Docker 的用户,我们更新了过时的 Docker 容器和容器库。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="2.8.0 访问本地站点失败" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 本地访问错误</summary></details><p>在 2.8.0 中,浏览本地站点(通过主机名或 b32将失败。
解决方法是使用 localhost 和服务器端口(通常为 7658来绕过 I2P。
例如,<a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>
我们对此问题深表歉意并努力修复中。</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 发布</summary></details><p>此版本通过修复错误、删除未使用的代码以及提高网络稳定性以改进 I2P。</p>
<p>我们改进了网络中拥堵的路由器的处理。
UPnP 和 NAT 遍历中的问题已解决,以改善连接性和错误回报。
我们现在有一个更激进的策略来从 NetDb 中删除赁集,以提高路由器性能并减轻过载。
另外有一些降低事件可观察性的更改,如路由器重启或关闭等。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 发布</summary></details><p>本次发布I2P 2.7.0 继续修复错误,提高性能以及添加功能。</p>
<p>从控制台和应用程序的信息访问已得到改进。
I2PSnark 和 SusiMail 搜索中的问题已得到修复。
路由器控制台中嵌入的 netDB 搜索的使用方式现在更直观、更实用。
高级模式下的诊断显示亦有少量改进。</p>
<p>另外修复了一些错误以提高网络内的兼容性。
一个赁集发布的问题已解决,提高了主要隐藏服务的可靠性。
当用户仅更改现有种子上的跟踪器时I2PSnark 不再更改信息哈希。
这可以防止种子因这些更改而受到不必要的干扰。
我们欢迎这份来自新贡献者的工作。
在处理流媒体库选项时的冲突已被解决以提高与其他 I2P 实现的兼容性。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 版本</summary></details><p>I2P 2.6.1 的发布是为了修复隐藏服务管理器应用程序中的用户界面错误。
此错误导致滚动被禁用,从而使某些配置无法访问。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 版本</summary></details><p>本次发布的I2P 2.6.0版本继续致力于修复漏洞、添加新功能并提升网络的可靠性。</p>
<p>当选择洪泛路由时,较新的路由将受到青睐。
I2PSnark 除了修复漏洞之外还获得了一些功能这些功能可以提高PeX对等节点交换的性能。
遗留的旧传输协议正在被移除因此简化了UDP传输代码。
本地主机上的目标节点将可以直接被本地客户端访问,而不需要请求它们的赁集,这可以提高性能和可测试性。
另外对对等节点的选择策略进行了一些额外的调整。</p>
<p>I2P 不再允许通过 Tor 建立 I2P 连接,从 Tor 出口IP地址建立的连接现在已被阻止。
我们不鼓励这样做因为它会降低I2P的性能并浪费Tor出口节点的资源而无任何益处。
如果您既运行Tor出口路由又运行I2P我们鼓励您继续这样做为两者使用不同的IP地址。
非出口节点和Tor客户端不受此影响无需任何更改。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 发布" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 包含 HTTP 修复</summary></details><p>I2P 2.5.2 版本是为了修复在 2.5.0 中引入的导致某些 HTTP 内容被截断的错误。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P 版本 2.5.1 已发布以解决拒绝服务攻击</summary></details><p>I2P 2.5.1 的发布是为了解决影响 I2P 网络和服务的拒绝服务攻击。
在此版本中,我们禁用了 Sybil 攻击检测工具的基于 IP 的部分,这些部分旨在放大攻击的影响和持续时间。
这应该有助于网络恢复正常运行。
那些已禁用 Sybil 攻击检测工具的人可以安全地重新启用它。
其他子系统也进行了调整,以改进路由信息验证和对等节点选择。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="暴风雨天气" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>网络天气:暴风雨。 I2P 正在遭受攻击。</summary></details><p>I2P 网络目前正遭受拒绝服务攻击。
此攻击以不同的方式影响 I2P 和 i2pd并对网络健康状况造成严重影响。
I2P 站点可达性严重下降。</p>
<p>如果您在 I2P 内部托管服务,并且该服务托管在洪泛路由上,则应考虑在禁用 Floodfill 的路由器上对该服务采用多宿主形式,以提高可达性。
其他缓解措施正在讨论中,但长期的、可向后兼容的解决方案仍需进一步研究。</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="新版本 I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>更多应用改善NetDB隔离策略审计</summary></details><p>该版本 I2P 2.5.0 比 2.4.0 版本提供了更多面向用户的改进,后者侧重于实施 NetDB 隔离策略。</p>
<p>I2PSnark增加了一些新功能比如搜索种子。
若干错误已经修复以提高与其他I2P种子客户端如 BiglyBT 和 qBittorrent 的兼容性。
我们要感谢所有与libtorrent和qBittorrent合作的开发人员他们支持并改进了I2P支持。
SusiMail还增加了一些新功能包括支持邮件中的Markdown格式和将附件拖放到邮件中的功能。
使用隐藏服务管理器创建的隧道现在支持“Keepalive”这提高了性能和与网络技术的兼容性使更复杂的I2P站点成为可能。</p>
<p>在此版本中,我们还对 NetDB 进行了一些调整,以增强其对垃圾信息的韧性,并提高路由器阻挡可疑消息的能力。
这是“审计” 2.4.0 版本中“子数据库隔离”防御实现的一部分。
此次调查发现了一个小的隔离穿透事件并修复之。
这个问题是 I2P 团队在内部发现并修复的。</p>
<p>在这个版本中我们对发布Android和Windows下游发行版的过程进行了一些改进。
这将改善这些下游产品的交付和可用性。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 发布包含 Congestion 和 NetDB 安全提升" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 发布包含 Congestion 和 NetDB 安全提升</summary></details><p>此版本 I2P 2.4.0 持续努力提高 I2P 网络的安全性和稳定性。
其中包含对网络数据库的大幅改进,网络数据库是 I2P 网络中用于发现对等节点的基本结构。</p>
<p>拥塞控制的改进将使路由器能够通过避开拥堵的对等节点从而提高网络稳定性。
这将有助于网络限制隧道垃圾信息造成的影响。
它还将有助于在 DDOS 攻击期间和之后修复网络。</p>
<p>NetDb 的更改还有助于保护各个路由器以及使用它们的应用程序的安全。
路由器现在可以通过将 NetDB 分成多个“子DB”来防御攻击者我们使用这些“子DB”来防止应用程序和路由器之间的信息泄漏。
这同时改进了 Java 路由器可用的有关其 NetDB 活动的信息,并简化了我们对多宿主应用程序的支持。</p>
<p>还包括 I2PSnark 和 SusiMail 应用程序中的许多错误修复和功能增强。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:" title="I2P 2.3.0 新版本 - 安全修复可调的黑名单DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - 安全修复可调的黑名单DTG API</summary></details><p>此版本包含 CVE-2023-36325 的修复。
CVE-2023-36325 是一个发生在布隆过滤器中的上下文混淆错误。
攻击者制作包含唯一 messageID 的 I2NP 消息,并将该 messageID 发送给客户端。
该消息在通过布隆过滤器后,不允许在第二条消息中重复使用。
随后,攻击者将相同的消息直接发送给路由。
路由器将消息传递给布隆过滤器并被丢弃。
这泄露了之前已经看到的 messageID 信息,使攻击者有充分的理由相信路由器承载了客户端。
这个问题已经通过将布隆过滤器的功能分离到不同的上下文中得到了解决,这些上下文中是基于消息是通过客户端隧道,还是探测隧道直接发送到路由的。
在正常情况下,这种攻击需要数天才能成功执行,并且可能受到攻击期间路由重启和对误报的灵敏度等若干因素的干扰。
建议使用 Java I2P 的用户立即更新以免受攻击。</p>
<p>在修复这个上下文混淆错误的过程中,我们修改了一些策略来防御这类型的泄漏。
这包括对 netDb 的调整、速率限制机制和洪泛路由的行为。</p>
<p>此版本添加了 not_bob 作为第二个默认hosts来源并把<a href="http://notbob.i2p">notbob.i2p</a><a href="http://ramble.i2p">ramble.i2p</a>添加到控制台主页。</p>
<p>这个版本还包含一个可调整的黑名单。
黑名单是半永久性的每个被封禁的IP地址会被一直屏蔽直到路由器重新启动。
在 sybil 攻击期间观察到黑名单爆炸性增长的用户可以通过将黑名单配置为按一定时间段使条目过期来缩短超时间隔。
此功能在默认情况下是关闭的,目前仅建议高级用户使用。</p>
<p>该版本还包括一个API用于使用桌面GUI(DTG)修改插件。
现在可以将菜单项添加到系统托盘中,从而更直观地启动使用本地应用接口的插件。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="新版本 2.2.1包含DockerUbuntu Lunar和Debian Sid的打包修复" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - 2.2.0 的维护修复</summary></details><p>I2P 2.2.0 版本向前推进以加快缓解 DDOS 攻击后,我们了解到一些开发问题,因此有必要构建和发布新包。
此发布修复了 Ubuntu Lunar 和 Debian Sid 中的一个问题,即使用更新后的版本的 jakarta 包无法访问路由器控制台。
Docker 包未正确读取参数,导致无法访问配置文件。
此问题也已解决。
docker 容器现在也与 Podman 兼容。</p>
<p>本发布与 transifex 同步翻译并更新 GeoIP 数据库。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="新版本 2.2.0包含DDOS攻击的缓解措施和 Streaming 子系统的调整" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>DDOS攻击的缓解措施和 Streaming 子系统的调整</summary></details><p>我们已选择将 2.2.0 的发布日期提前到今天,即 2023 年 3 月 13 日。
此版本包括对网络数据库、洪泛和节点选择组件的修改,提高了路由器抵御 DDOS 攻击的能力。
攻击可能会持续进行,但对这些系统的改进将通过帮助路由识别和降低路由评分来帮助减轻 DDOS 攻击的风险。</p>
<p>此版本还为 Streaming 子系统添加了重放保护,以防止可以捕获加密数据包的攻击者通过将其发送给意外的接收者来重新使用它。
这是一个向后兼容的更改,因此旧路由器仍然能够使用新路由器的流媒体功能。
此问题由 I2P 开发团队在内部发现并修复,与 DDOS 攻击无关。
我们从未在实际环境遇到过重放流数据包,并且不相信此时针对 I2P 网络发生过流重放攻击。</p>
<p>您可能已经注意到,这些发行说明和发行版本身已由 idk 而非 zzz 签署。
zzz 已选择退出该项目,他的职责由其他团队成员承担。
因此,该项目正致力于更换网络统计基础设施并将开发论坛移至 i2pforum.i2p。
我们感谢 zzz 长期以来提供这些服务。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS 消息进展" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS 消息进展</summary></details><p>我们已经确认攻击者控制了大量的路由器。
我们的调查和缓解措施仍在继续当中。</p>
<p>这是提醒人们即使在 20 年后I2P 网络规模仍然相对较小的好时候。
我们没有证据表明攻击者正试图对任何特定用户或隐藏服务进行去匿名化。
但是,如果您有高风险威胁模型,您应该仔细考虑 I2P 目前是否提供了您需要的保护。
从长远来看,最好的解决方案是宣传并发展 I2P 网络以提高我们用户的安全性。</p>
<p>我们将在有必要时在新闻推送和<a href="http://zzz.i2p">zzz.i2p</a>提供更多信息。
在我们努力改进 I2P 的过程中,请您耐心等待。</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="关于最近的拒绝服务攻击" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P 保持完好,但性能受损</summary></details><p>I2P 网络目前正受到拒绝服务攻击的影响。
网络的洪泛功能受到影响,导致响应中断,隧道构建成功率下降。
网络参与者在连接到 I2P 站点和使用 I2P 服务时遇到困难。
我们在正在逐步调查和实施缓解策略。</p>
<p>虽然攻击降低了性能,但网络仍然完好无损且可用。
目前Java I2P 路由器似乎比 i2pd 路由器能更好地处理这些问题。
下周,各种缓解措施应该会开始出现在 Java 和 C++ 路由器的开发版本中。</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 包含大量 SSU2 修复</summary></details><p>自 11 月发布 2.0.0 以来,我们获知了一些情况。
随着路由器更新到该版本,网络对我们新的 SSU2 传输协议的支持率从大约 1% 提高到 60% 以上。
首先,我们已经确认 SSU2 是一个可靠、设计良好且安全的协议。
其次,我们发现并修复了协议推行中的许多小错误或很少触发的错误。
这些错误累积起来的影响降低了网络的性能。</p>
<p>此外,我们还注意到网络中隧道数量的增加和隧道构建成功率的下降,
可能是由比特币新的 I2P 临时地址功能触发的,
但由于我们的 SSU2 错误和其他拥塞控制问题而变得更差。
我们正在与比特币和其他非比特币项目合作,以减少 I2P 网络需求。
我们改进了算法以减少拥塞期间的网络负载。
我们还与 i2pd 合作开发通用的拥塞控制策略。</p>
<p>因此,我们将此版本的发布时间加快了大约六周,以便向所有人发布修复程序。
i2pd 上周发布了他们的 2.45.0 版,早期的结果令人鼓舞。
新协议和分布式网络的开发很困难。
拥塞可能会在没有任何警告和原因的情况下出现。
感谢您的耐心等待,因为我们已经诊断并希望解决问题。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 全面启用</summary></details><p>I2P 2.0.0版本在完成了小特性开发、测试和若干错误修复以后还为所有用户启用了我们新的SSU2协议。</p>
<p>我们也修复了各种问题包括安装包、网络数据库、私有地址簿添加Windows浏览器启动程序和IPv6 UPnP。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="最近的博客文章" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>部分最近的博客文章</summary></details><p>这是我们网站部分最近的博客文章的链接:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">有关我们新的 SSU2 协议的概述</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">有关I2P币及其他骗局的警告</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">与divs.exchange的Konrad的访谈</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">与StormyCloud的Dustin的访谈</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 包含 SSU2 测试</summary></details><p>我们在过去的三个月里与少量志愿测试者一起研究我们新的UDP传输协议 "SSU2"
这个版本完成了完整的实现,包括中继和对等节点测试。
我们默认在安卓和ARM平台上启用它并在一小部分其它路由上随机启用。
这将使我们能够在未来三个月内做更多的测试,完成连接迁移功能,
并修复任何剩余的问题。
我们计划在11月发布的下一个发布版本中为所有人启用该功能
无需手动配置。</p>
<p>当然,这个发布版本也包含了一些常见的错误修复。
我们还增加了一个自动死锁检测器,它已经找出一个很少见的死锁。这个死锁已经被修复。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="新出口代理 exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>新出口代理</summary></details><p>I2P出口代理exit nodes可以使你通过一个HTTP代理隧道访问互联网。
在我们的 <a href="http://i2p-projekt.i2p/en/meetings/314">月度会议</a>上,
<b>exit.stormycloud.i2p</b> 已经成为我们官方推荐的出口代理,替代早已死去的 <b>false.i2p</b>
欲了解 <a href="http://stormycloud.i2p/"> StormyCloud 组织</a>的更多信息,请访问
<a href="http://stormycloud.i2p/outproxy.html">出口代理</a>
<a href="http://stormycloud.i2p/tos.html">服务条款</a>
<a href="http://stormycloud.i2p/">StormyCloud 网站</a></p>
<p>我们建议你修改 <a href="/i2ptunnel/edit?tunnel=0">匿名服务管理器配置</a>来确保 <b>exit.stormycloud.i2p</b>存在于两个地方: <b>出口代理</b><b>SSL出口代理</b>
修改之后,<b>向下滑、点击保存</b>
<a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">在我们的博客文章上查看截图</a>
你可以在 <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob的博客</a>上查看Android版的说明和截图。</p>
<p>路由器更新不会更新你的配置,你必须手动修改。
非常感谢 StormyCloud 的支持。如果可能的话,请考虑<a href="http://stormycloud.i2p/donate.html">给他们捐赠</a></p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 包含错误修复</summary></details><p>本更新包含i2psnark
路由器I2CP和UPnP的错误修复。
修复了路由器软重启、IPv6、SSU 对等节点测试、网络数据库存储和隧道构建中的地址错误。
路由家族处理和Sybil分级也明显改善了。</p>
<p>和i2pd一起我们开发了新的UDP传输SSU2。
SSU2将带来实质性的性能和安全性改进。
它还将让我们最终替换我们最后使用的非常慢的 ElGamal 加密,
完成我们从约9年前开始的加密的完全升级。
本发布包含一个默认关闭的初步版本。
如果你想参与测试请关注zzz.i2p的当前消息。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="安装必要的 Java/Jpackage 升级" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>最近Java的“Psychic Signatures”漏洞影响到I2P。当前Linux的I2P用户或任何正在使用非捆绑JVM的I2P用户应当更新
他们的JVM或切换到 Java 15 以下
不包含该漏洞的版本。</p>
<p>新的I2P一键安装包已使用
JVM的最新发布生成。更多详情已发布在各
同捆包的新闻源中。</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 包含可靠性和性能提升</summary></details><p>1.7.0 更新包含若干性能和可靠性的改善。</p>
<p>对于支持的平台,现在系统托盘中会弹出信息。
i2psnark 现在有一个新的种子编辑器。
还大大降低了 NTCP2 的CPU占用。</p>
<p>在新安装中,长期不受支持的 BOB 接口已被移除。
除了 Debian 包以外,现有的安装将继续使用之。
其余任何 BOB 应用的用户都应该要求开发人员切换到 SAMv3 协议。</p>
<p>我们得知自 1.6.1 发布以来,网络可靠性不断恶化。
我们在发布以后很快就意识到了这个问题,然而我们花了近两个月才找到原因。
我们最终确认为 i2pd 2.40.0 中的一个bug
这个修复将在 2.41.0 中和这个版本同时发布。
在此过程中,我们在 Java I2P 中做了一些修改,以改善
网络数据库查找和存储的健壮性,并在隧道节点选择中避开性能较差的对等节点。
这将使网络在存在异常路由或恶意路由的情况下更健壮。
此外,我们正在启动一个联合项目,在同一个隔离的测试网络中测试 i2pd 和 Java I2P 路由
的预发布版本,这样我们就可以在发布前而不是发布以后发现更多问题。</p>
<p>其他方面,我们在设计新的 UDP 传输“SSU2”提案159
中继续取得重大进展并开始推行。
SSU2 将带来实质上的性能和安全提升。
这还将让我们能最终取代最后使用的,非常慢的 ElGamal 加密,
完成约9年前开始的全加密升级。
我们预计很快就会开始和 i2pd 进行联合测试,并在今年晚些时候向全网络推出。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 启用新的隧道搭建信息</summary></details><p>该更新完成了2021年开发的两个主要协议更新的推出。
为路由迁移至 X25519 加密的步伐加快了,我们预计绝大部分路由在今年年底能完成切换。
短隧道构建信息已启用以减少带宽使用。</p>
<p>我们为新安装向导增添了一个主题选择面板。
我们改善了 SSU 表现,修复了一个 SSU 对等节点测试信息的问题。
调整了隧道构建布隆过滤器以降低内存使用。
我们改善了非Java插件的支持。</p>
<p>另外,我们在设计新的 UDP 传输协议 SSU2 方面取得了重大进展,预计明年年初开始推行。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 包含新的隧道搭建信息</summary></details><p>是的没错,在 0.9.x 发布9年后我们直接从 0.9.50 跳到 1.5.0。
这并不意味着有重大的API更改也不意味着开发已经完成。
这仅仅是对近20年来为我们的用户提供匿名和安全的工作的认可。</p>
<p>此更新完成了更小的隧道构建消息的实现从而减少带宽使用。
我们继续迁移网络的路由至 X25519 加密。
当然也有许多错误修复和性能提升。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Muwire 桌面版漏洞" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire 桌面版漏洞</summary></details><p>Muwire 桌面版应用的独立安装包中发现一个安全漏洞。
其不影响控制台插件,并和以往发现的插件问题无关。
如果你正在运行 Muwire桌面版应用你应当立即<a href="http://muwire.i2p/">升级到 0.8.8</a></p>
<p>问题详情将在2021年7月15日于<a href="http://muwire.i2p/security.html">muwire.i2p</a>公布。</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Muwire 插件漏洞" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire 插件漏洞</summary></details><p>Muwire 插件中发现一个安全漏洞。
其不影响桌面客户端的独立安装包。
如果你正在运行 Muwire 插件,你应当立即<a href="/configplugins">升级到 0.8.7-b1</a></p>
<p>更多有关漏洞和及时的安全建议的信息见于<a href="http://muwire.i2p/security.html">muwire.i2p</a></p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 包含 IPv6 修复</summary></details><p>0.9.50 继续为路由加密密钥迁移至 ECIES-X25519。
我们已为补种启用 DNS over HTTPS 以保护用户免受被动 DNS 窥探。
还有若干对 IPv6 地址的修复和提升,包括新的 UPnP 支持。</p>
<p>我们终于修复了一些 SusiMail 长期存在的错误。
对带宽限制器的修改应该能改善网络隧道表现。
在我们的 Docker 容器有几处改善。
我们已经提升了对网络中可能的恶意和异常路由的防御。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 包含SSU修复及更快速的加密</summary></details><p>0.9.49 继续使 I2P 更快更安全。
我们对 SSU (UDP) 传输做了若干改进和修复,速度应有所提高。
同时此更新开始为路由迁移至新的,更快的 ECIES-X25519 加密。
(至今目标地址采用此加密已有数个更新)
这几年,我们一直致力于新加密的规范和协议,
现已经接近尾声了!迁移会在数个更新中完成。</p>
<p>对于此更新,为尽量减少中断,只有新安装的以及极小比例的现有安装
(重启时随机选择)会采用新加密。
如果你的路由确实“重新键入”以使用新加密,在你重启后的几天内,它可能会比平时流量更少或可靠性更低。
这是正常现象,因为你的路由生成了一个新的身份。
你的路由性能随后会恢复正常。</p>
<p>以往我们在改变默认签名类型时已两次“重新键入”网络,
但这是首次更改默认加密方式。
希望一切都能顺利进行,我们正逐步确定。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 包含性能提升</summary></details><p>0.9.48 在大多数服务上启用了我们的新端到端加密协议提案144
我们已经添加对新隧道建立的信息加密提案152的初步支持。
整个路由的性能都有显著提高。</p>
<p>Ubuntu Xenial (16.04 长期支持版) 的软件包已不再支持。
使用该平台的用户应当升级以继续获得 I2P 更新。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 启用了新的加密</summary></details><p>0.9.47 在一些服务中默认启用了我们的新端到端加密协议(提案 144
Sybil 分析和屏蔽工具现在已默认启用。</p>
<p>现在需要 Java 8 或更高版本。
Debian 软件包 Wheezy 和 Stretch以及 Ubuntu 软件包 Trusty 和 Precise 现已不再支持。
使用上述平台的用户需要升级以继续获得 I2P 更新。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 包含错误修复</summary></details><p>0.9.46 包含 streaming 库显著的性能提升。
我们已经完成了 ECIES 加密提案144的开发现在可以选择启用它以进行测试。</p>
<p>仅 Windows 用户:
本发布修复了一个可被本地用户利用的本地提权漏洞。
请尽快应用更新。
感谢 Blaze Infosec 披露此问题。</p>
<p>这是最后一个支持 Java 7、Debian 软件包 Wheezy 和 Stretch 以及 Ubuntu 软件包 Precise 和 Trusty 的发布。
使用上述平台的用户务必升级以获得未来的 I2P 更新。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 包含了错误修复</summary></details><p>0.9.45包含了隐身模式和带宽测试的重要修复。
这是一个对于控制台暗色主题的更新。
我们继续努力提高性能并开发新的端到端加密(提案 144)。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 发布" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 包含了错误修复</summary></details><p>0.9.44 包含一个隐藏服务处理新加密类型中拒绝服务问题的重要修复。所有用户都应尽快更新。</p>
<p>发布版本包含新端到端加密的初始支持(提案 144。此项目上的工作仍在继续尚未准备好使用。有一些控制台主页的更改及 i2psnark 中新的嵌入式 HTML5 媒体播放器。包含对受到防火墙限制的 IPv6 网络的额外修复。隧道建立的修复应当使得一些用户更快的启动。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 包含了错误修复</summary></details><p>在 0.9.43 更新版本中,我们继续致力于更强的安全性,隐私功能和性能提升。我们的新的租契集规范 (LS2) 实现现在已完成。我们正在开始用于未来发布版本的更强大快速的端到端加密(提案 144实现。一些 IPv6 探测问题已修复,当然还有一些其他错误修复。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 包含了错误修复</summary></details><p>0.9.42 继续使 I2P 更快更稳定.
此版本包含了几处改动以提高 UDP 传输速度。
我们拆分了设置文件,以便将来进一步模块化。
我们将继续努力,将关于更快、更安全的加密的建议付诸实践。
理所当然地, 还有许多错误修复。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 包含了错误修复</summary></details><p>0.9.41 继续着手落实提案 123 引入的新功能,
包括对加密的租契集做客户端级别的身份验证。
控制台的 I2P 标志及若干图标已更新。
更新了 Linux 安装程序。</p>
<p>启动速度在树莓派Raspberry Pi等平台上更快了。
已修正若干缺陷,包括部分严重影响底层网络消息的问题。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 有新的图标</summary></details><p>0.9.40 支持新的租契集格式。
我们已禁用旧的 NTCP 1 传输协议。
有一个新的 SusiDNS 导入功能,以及一个用于传入连接的新的脚本化过滤机制。</p>
<p>我们对 OSX 原生的安装程序做了很多改进,以及更新了 IzPack 安装程序。
继续使用新的图标焕新控制台。
如往常一样,我们还修复了许多缺陷!</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 带有性能提升</summary></details><p>0.9.39 包含了针对新网络库格式的大量更新(proposal 123).
我们将 i2pcontrol 插件作为一个 webapp 打包进来从而支持 RPC 应用的开发.
另外还有众多的性能提升和bug修复.</p>
<p>我们移除了午夜和经典主题以减轻维护压力.
之前使用这些主题的用户现在将会看到暗或者亮色调主题.
另外主页有了新的的图标,这是控制台更新的第一步.</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 含有全新安装向导</summary></details><p>0.9.38 含有一个若为首次安装则会启动的向导还有一个带宽测试器。我们已经支持最新的GeoIP数据库格式。我们的网站上有一个新的配置Firefox的安装包和一个新的本地Mac OSX安装包。我们继续努力支持新的“LS2”网络数据库格式。</p>
<p>这次更新还有大量的bug修复包括修复了susimail附件的一些问题还含有针对纯IPv6路由器的一个修复。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 旅行报告" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>35C3 会议上的I2P</summary></details><p>I2P 团队大多数人出席了莱比锡的 35C3 会议。每天都开会回顾上一年阐述了我们2019年的发展和设计目标。</p>
<p>项目愿景和新的路线图见<a href="http://i2p-projekt.i2p/en/get-involved/roadmap">此文</a></p>
<p>我们为网页和控制台在LS2Testnet和可用性提升上继续努力。
一个计划已在TailsDebian和Ubuntu Disco中就位。我们在安卓和I2P_Bote的修复上仍需要人手。</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 已发布" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37NTCP2 已启用</summary></details><p>0.9.37版启用了更快更安全的传输协议NTCP2。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 已发布" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36NTCP2 及缺陷修复</summary></details><p>0.9.36包含一个新的更安全的传输协议叫作NTCP2。
此协议默认禁用,但是您可以启用它。在<a href="/configadvanced">高级设置</a>中设置 <tt>i2np.ntcp2.enable=true</tt>,然后重新启动。
在下个发布中NTCP2将被启用。</p>
<p>此发布也包含性能优化和缺陷修复</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 发布" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35SusiMail 文件夹及 SSL 向导</summary></details><p>0.9.35 在Susimail中加入了文件夹的支持以及在您的隐藏服务页面用于建立HTTPS的新SSL向导。
我们如同往常一样收集错误修复尤其是在Susimail中</p>
<p>我们正在为0.9.36中的几部分而努力包括新的OSX安装包以及更快、更安全的被称为NTCP2的传输协议。</p>
<p>7月20-22号 I2P 将在纽约市HOPE。欢迎拜访并打招呼</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 发布" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 包含错误修复</summary></details><p>0.9.34包含大量错误修复!
同时还有Susimail、IPV6处理和隧道对等节点选择。
我们在UPnP中加入了IGD2模式的支持。
您还可以在将来的发布中看到更多的改进。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 发布" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 包含错误修复</summary></details><p>0.9.33包含大量的错误修复包括i2psnarki2ptunnelstreaming和SusiMail。
对于那些不能直接访问补种页面的用户,我们现在提供几种形式的代理用于补种。
我们现在在隐藏服务管理器中默认设置了比率限制。
对于高流量服务器,如有必要请浏览并调整限制。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KaiserMeltdown和Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>安全问题几乎在每种系统中均有所发现</summary></details><p>在全球范围内几乎所有已售出的电脑里的现代CPU中发现了很严重的问题包括移动设备。这些安全漏洞名为“Kaiser”“Meltdown”“Spectre”。</p>
<p>KAISER/KPTI 的白皮书可在<a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>中找到Meltdown在<a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>以及SPECTRE在<a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>。英特尔第一响应列于<a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>之下。</p>
<p>当有可用更新时更新系统对于我们的I2P使用者来说很重要。Windows 10系统补丁已从现在起可用随后不久则是Windows 7和8。MacOS的补丁同样也已可用。大多Linux系统也同样具有包含修复的内核。这同样适用于安卓系统在2018年1月2日的安全补丁中就包含此问题的补丁。请在可行时尽快更新您的系统。</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="新年快乐!- 来自34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>新年与 I2P 在34C3</summary></details><p>I2P团队祝各位新年快乐</p>
<p>从2017年12月27日至30日在莱比锡举行的34C3会议上不少于7位 I2P 团队成员参加了会议。除了在桌上的<a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">会议</a>以外我们还会见了从四面八方来的I2P的朋友。
会议的结果已发布在<a href="http://zzz.i2p" target="_blank">zzz.i2p</a></p>
<p>此外我们分发了很多贴纸,并将有关我们项目的信息提供给任何询问的人。
我们的年度I2P晚餐取得了圆满成功感谢所有与会人士对I2P的持续支持。</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 发布" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 包含控制台升级</summary></details><p>0.9.32包含若干路由控制台和有关web应用地址簿i2psnark和Susimail的修复。
我们亦同时修改了处理用于发布路由信息的配置主机名的方式以消除一些通过DNS的网络穷举攻击。
我们已经在控制台中加入了一些检查以抵御重绑定攻击。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 版本發佈" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 含控制面板更新</summary></details><p>您可以很輕易的發現這個版本的變化!
我們改進了路由器控制面板,使的它更容易上手,
使用時變得更加容易連接和加強了對不同瀏覽器的支持,
網頁也顯得更加整潔。
這是我們長期計劃中的第一步,設計一個對使用者更加友好的路由器控制面板。
我們還為 i2psnark 添加了 torrent 評級和評論。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="召集翻譯員" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>即將發佈的 0.9.31 版本有比一般版本需要更多翻譯的部分</summary></details><p>在即將發佈的 0.9.31 版本裡的使用者介面,將會迎來重大的更新,
請注意我們將會有比平常更多的文字需要被翻譯。
如果您是翻譯人員,我們期望您在這次版本發佈前
留給我們更多的時間,加速翻譯的進度。
我們也特意提早了三個禮拜,公佈需要翻譯的資料。</p>
<p>如果您還不是 I2P 的翻譯員,現在是一個加入的好時機!
請參考
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">新翻譯者指南</a>
了解如何參與這個偉大的項目。</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 已发布" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 更新到 Jetty 9 </summary></details><p>從 0.9.30 版本開始,支持了新的 Jetty 9 和 Tomcat 8 。
之前的版本將不再獲得支持,並且在即將發布的 Debian Stretch 和 Ubuntu Zesty 中不能使用。
路由器會調整 jetty.xml 這個配置檔案,將每個 Jetty 網站遷移到新的 Jetty 9 設置。
這些動作應該可以適用於不是很老的和沒有手動修改過的配置,但如果是很老舊的版本和手動修改過配置,可能就不適用這個升級方式。
請確認你的 Jetty 網站在升級後正常運作,如果有任何問題需要幫助,請利用 IRC 與我們聯繫(只提供英文幫助)。</p>
<p>請注意有幾個插件與 Jetty 9 不兼容,必須要更新。
以下的幾個插件已更新,適用於 0.9.30 版本,並且請先重啟路由器後再安裝他們:
i2pbote 0.4.6; zzzot 0.15.0。
以下幾個插件(列出當前版本)還不適用於 0.9.30 版本。
你可以聯繫這幾個插件的開發人員,了解新版本開發的進度:
BwSchedule 0.0.36; i2pcontrol 0.11。</p>
<p>這一個版本還支持將之前的 DSA-SHA1 後台服務2014及更早的版本升級到更安全的 EdDSA 簽名類型。
如果您需要更詳細的信息,請參閱<a href="http://zzz.i2p/topics/2271">zzz.i2p</a>,其中包括使用指南和常見問題解答。</p>
<p>請注意:在非 Android ARM 平台上例如Raspberry PiBlockfile 資料庫將會在重新啟動時升級,這可能需要幾分鐘的時間。
請耐心等待!</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 已发布" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29包含缺陷修复</summary></details><p>版本 0.9.29 修正了的許多故障申報裡面的問題,包括壓縮信息損壞的解決方法。
新版本支持 IPv6 上的 NTP。
我們添加了對 Docker 先期版本的支持。
我們轉換好了新的線上幫助文件。
我們現在允許HTTP表頭使用同源參照位址通過 HTTP代理。
我們修正了許多在Java 9下的問題雖然我們並不推薦在一般情況下使用Java 9。</p>
<p>一如往常的,我們建議您更新到這個版本。要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote安全漏洞" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote安全漏洞</summary></details><p>I2P-Bote 版本 0.4.5 修復了所有早期存在插件中的安全漏洞
這對 Android 版本的程式沒有影響。</p>
<p>當用戶打開電子郵件時,大部分的內容經過編碼調整。 但是,
附件的檔案名稱沒有經過編碼處理,當瀏覽器的 JavaScript 功能是開啟的時候,
容易被利用來執行惡意代碼。 現在,這個部分已經被加進編碼處理的範圍內,
並且我們還對全部的頁面,額外增加了內容管理安全政策。</p>
<p>所有 I2P-Bote 的使用者,當 I2P 0.9.29 版本在2月中旬發佈後
I2P-Bote 會在路由器重啟時自動更新。 但是,在這新舊版本交接的時候,
為了保險起見,我們建議您
<a href="http://bote.i2p/install/">按照安裝頁面上的操作指示</a>
手動進行升級。</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 版本發佈" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 版本含錯誤修正</summary></details><p>版本 0.9.28 修復了 25個以上的故障報修和升級了許多隨附軟體包括Jetty
增進了 IPv6 最新版本中出現的 peer test 的功能。
我們對其它可能帶有惡意的主機來的連線,不斷改進偵測和阻止它的能力。
我們針對Java 9做了一點初級的修復雖然我們並不推薦在一般情況下使用 Java 9。</p>
<p>I2P 的護法們將會出現在 33C3請不要只是在外旁觀請您提供如何將 I2P 做的更好的意見和想法。
在這次會議裡面,我們將會討論 2017 的項目路線圖和排定優先順序。</p>
<p>一如往常的,我們建議您更新到這個版本。要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote安全漏洞" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote安全漏洞</summary></details><p>I2P-Bote 版本 0.4.4 修復了所有早期存在插件中的安全漏洞
這對 Android 版本的程式沒有影響。</p>
<p>缺乏對 CSRF 攻擊的防護,意味當使用者使用 I2P-Bote 的時候,沒有把瀏覽器 JavaScript 功能
關閉,同時在不知情的情況下打開了一個惡意網站。你有可能不自覺的觸發 CSRF 攻擊,
而使你的 I2P-Bote 在你不知情下送出信息。可能發生的一種情形是駭客有可能利用這個漏洞
提取到 I2P-Bote 的私鑰地址,而我們現在沒有辦法證明這個安全漏洞是存在的。 </p>
<p>當 0.9.28 版本在12月中旬發佈之後所有的 I2P-Bote 使用者將會在重啟路由器後,
得到自動更新。 但是,如果您是 I2P 或 I2P-Bote 的固定使用者,遇到新舊版本交接,
比較保險的做法是
<a href="http://bote.i2p/install/">按照安裝頁面上的操作指示</a>手動進行升級。
如果您是 I2P-Bote 的固定使用者,而且您習慣打開瀏覽器的 JavaScript 功能,
您可以考慮在新版本發佈後,產生新的 I2P-Bote 地址,放棄舊的地址,降低您被攻擊的風險。</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 版本發佈" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 版本含錯誤修復</summary></details><p>版本 0.9.27 修復了一些問題。
之前 0.9.26版本,更新了加速密碼加密解密速度的 GMP 庫,但那只適用於新安裝和 Debian/Ubuntu 版本的軟體,現在 0.9.27 版本可以直接透過網路,更新原生的密碼加密庫。
我們也改進了 IPv6 的傳輸能力、SSU peer test 測試和隱藏模式。</p>
<p><a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P 夏季</a>期間,我們更新了許多插件,您的路由器將在重新啟動後自動更新它們。</p>
<p>一如往常的,我們建議您更新到這個版本。要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P 在 Stack Exchange 上的計劃書" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P 將項目計劃書放在 Stack Exchange 上了!</summary></details><p>I2P 將項目計劃書放在 Stack Exchange 上了!
請您<a href="https://area51.stackexchange.com/proposals/99297/i2p">踴躍參與</a>,我們將啟動項目的 Beta 階段。</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 版本發佈" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26版本包含了密碼部分的更新,改進了 Debian 的安裝包,和修復了錯誤 </summary></details><p>版本 0.9.26 做了一個重大升級,把軟體原生的密碼加密庫更新了,
一個新的帶簽章的地址簿訂閱協議,
並對 Debian / Ubuntu 安裝包進行了重大改進。</p>
<p>加密学方面,我们升级到 GMP 6.0.0,并添加较新处理器的支持,这可以大幅加速密码运算。
另外,我们现在使用常数时间的 GMP 函数以防止侧信道攻击。
出于谨慎GMP 更改只对新的安装和 Debian/Ubuntu 构建启用;我们会在 0.9.27 发布时更新它们。</p>
<p>對於 Debian / Ubuntu 版本,我們在軟件包裡添加了幾個隨附軟體,
包括 Jetty 8 和 geoip並刪除了對應的隨附軟體源代碼。</p>
<p>我們整合修復了一些問題,包括定時器的問題
這會造成隨著時間推移,軟體的不穩定和性能下降。
再次提醒您,我們建議所有使用者更新到最新版本。
這將會是幫助網絡良好的成長並保持安全的最佳方式。</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 釋出" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 包含 SAM 3.3、QR 码及缺陷修复</summary></details><p>0.9.25 包含 SAM 的一个主要新版本 v3.3,以支持复杂的多协议应用程序。
增加了 QR 码用于与其他人分享隐身服务。
增加了“身份”图像用于视觉上区分地址。</p>
<p>我们在控制台中添加了新的“路由器家族”配置页面,
这可以让您更容易的声明您的一组路由器是由同一个人运行。
这会添加一些变更以增加网络容量,并能提升隧道构建成功率。</p>
<p>一如往常的,我們建議您更新到這個版本。要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 釋出" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24包含了一些漏洞修補和加速器</summary></details><p>0.9.24 包含新版本的 SAM (v3.2) 和众多问题修复和效率改进。
注意,这是首个必需使用 Java 7 的发布版本。
请尽快升级到 Java 7 或 8。
如果您在使用 Java 6您的路由将不会自动更新。</p>
<p>為了避免古早的共享資料庫造成麻煩,我們要把它移除。
如果某些古早I2P-Bote外掛(0.2.10以下,飢餓流浪漢所簽屬),允許互動郵件存取協定,那移除後它們會崩潰。
比較建議的修復是用當今str4d簽署的I2P-Bote外掛來取代古早的。
更多細節請參考 <a href="http://bote.i2p/news/0.4.3">這篇</a></p>
<p>我們舉辦了完美的<a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3-30號混沌通訊大會</a>而且對於我們2016的計畫有順利進展。
Echelon的演講包括了I2P的歷史和現狀他的投影片在 <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">這裡</a>(PDF)。
Str4d出席了<a href="http://www.realworldcrypto.com/rwc2016/program">現實世界加密</a>也演說了我們的加密遷移,他的投影片在<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">這裡</a> (PDF)。</p>
<p>一如往常的,我們建議您更新到這個版本。要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 釋出" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 版本修正個數個程式錯誤,並且對於 I2PSnark 做了些許的改良</summary></details><p>I2P這是在由 zzz 簽署發行的49個版本之後由我(str4d)簽署的第一份發行版。這是個是對於所有人員與事物的重要冗餘測試。</p>
<p><b>做點家事</b></p>
<p>我的簽名金鑰已經在路由更新上超過兩年了(自 0.9.9)所以如果您正在使用這版本的I2P那麼這個更新應該就像之前的一樣簡單。不過若您使用的是早於0.9.9的版本,您必須手動更新至目前版本。目前版本的更新資料夾可以在<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">這裡</a>下載,而手動更新的介紹則在<a href="http://i2p-projekt.i2p/en/download#update">此處</a>
一旦您完成手動更新您的路由器便會像往常一樣找到0.9.23更新並下載。</p>
<p>若您的 I2P 是經用套件管理系統安裝的話,那您並不會被這次變更所影響,可以如往常一般繼續更新。</p>
<p><b>更新資訊</b></p>
<p>迁移 RouterInfos 到新的、更强的 Ed25519 签名很顺利,预计已有至少一半的网络转换密钥。此次更新加速了密钥更新的过程。为了减少网络客户端的流失,您的路由器将在每次重启时有较小的概率转换到 Ed25519。在它转换密钥后可预期的两天内将有更低的带宽因为它需要将新的身份重新集成到网络。</p>
<p>請注意,這是支援 Java 6 的最後一個版本,煩請盡速將您的 Java 更新到 7 或 8 版本。目前我們已經在處理 I2P 與 Java 9 的相容性問題,部分的成果會隨著此次的改版釋出。</p>
<p>我們也有針對 I2PSnark 做了一些改善,也在路由控制台新增了一個可以查看舊聞的頁面。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 釋出" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>帶著漏洞修復的0.9.22 開始轉移至 Ed25519</summary></details><p>0.9.22包含了修復i2psnark未完成便卡住的問題和開始將路由資訊轉移至新的、更強的Ed25519簽署。
為了減少網路擾動您的路由器每次重啟只有一些機率會轉換至Ed25519。
一旦密鑰更新了,您可以期待在幾天內看到更少的頻寬使用,因為它用了新身分重新融合到了網路中。
如果一切順利,我們會在下個釋出版本加速更新密鑰的速率。</p>
<p>在多倫多舉辦的 I2PCon 研討會完美結束了!
所有的簡報以及影片皆以陳列於 <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon 頁面</a></p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21釋出" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21釋出版本帶著增進的效能與漏洞的修復。</summary></details><p>0.9.21 包含几个更改,以增加网络容量、提高播种效率,并更有效率的使用带宽。我们已经迁移共享客户端隧道到 ECDSA 签名,并使用新的 "multisession" 功能为那些不支持 ECDSA 的站点添加一个 DSA 后备。</p>
<p>2015年多洛伦 I2PCon 的报告人和时间表已经公布。查阅 <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon 页面</a>了解详细信息。在 <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a> 上预定您的座位。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon 多伦多报告人和时间表已公布" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>2015年在多伦多的 I2PCon 报告人和时间表已公布</summary></details><p>2015年多洛伦 I2PCon 的报告人和时间表已经公布。查阅 <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon 页面</a>了解详细信息。在 <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a> 上预定您的座位。</p>
</article>
</div>

View File

@ -0,0 +1,604 @@
<div>
<header title="Noticias I2P">Novas e actualizacións do router</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Liberada" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 con carpetas de SusiMail y SSL Wizard</summary></details><p>0.9.35 Añade soporte para carpetas en SusiMail, y un nuevo SSL Wizard para la configuración HTTPS en tu website de Servicio Oculto.</p>
<p>Estamos trabajando duro en varias cosas para 0.9.36, incluyendo un nuevo instalador para OSX y un más rápido, y más seguro protocolo de transferencia llamado NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
it if you could set aside a little more time than usual during this release cycle
in order to bring the translations up to speed. We have pushed the strings early
to give you three weeks to work on them.</p>
<p>If you're not currently an I2P translator, now would be a great time to get
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
<p>Several plugins are not compatible with Jetty 9 and must be updated.
The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
i2pbote 0.4.6; zzzot 0.15.0.
The following plugins (with current versions listed) will not work with 0.9.30.
Contact the appropriate plugin developer for the status of new versions:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="Vulnerabilidade na Seguridade de I2P-Bote" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>Vulnerabilidade na Seguridade de I2P-Bote</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="Publicada a versión 0.9.28 " href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>A versión 0.9.28 contén arranxos a bugs</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="Vulnerabilidade na Seguridade de I2P-Bote" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>Vulnerabilidade na Seguridade de I2P-Bote</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
for this.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
which will speed up crypto operations considerably.
Also, we are now using constant-time GMP functions to prevent side-channel attacks.
For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
we will include them for in-net updates in the 0.9.27 release.</p>
<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
<p>There's a collection of bug fixes also, including a fix for a timer bug
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contains SAM 3.3, QR codes, and bug fixes</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
It adds QR codes for sharing hidden service addresses with others,
and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
to make it easier to declare that your group of routers is run by a single person.
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
Your router will not automatically update if you are using Java 6.</p>
<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration,
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
<p><b>Housekeeping</b></p>
<p>My signing key has been in router updates for over two years (since 0.9.9), so
if you are on a recent version of I2P this update should be just as easy as
every other update. However, if you are running an older version than 0.9.9, you
will first need to manually update to a recent version. Update files for recent
versions can be downloaded
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
and instructions on how to manually update are provided
<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
updated, your router will then find and download the 0.9.23 update as usual.</p>
<p>If you installed I2P via a package manager, you are not affected by the change,
and can update as usual.</p>
<p><b>Update details</b></p>
<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
with at least half of the network already estimated to have rekeyed. This
release accelerates the rekeying process. To reduce network churn, your router
will have a small probability of converting to Ed25519 at each restart. When it
does rekey, expect to see lower bandwidth usage for a couple of days as it
reintegrates into the network with its new identity.</p>
<p>Note that this will be the last release to support Java 6. Please update to
Java 7 or 8 as soon as possible. We are already working to make I2P compatible
with the upcoming Java 9, and some of that work is in this release.</p>
<p>We have also made some minor improvements in I2PSnark, and added a new page in
the routerconsole for viewing older news items.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
and use bandwidth more effectively.
We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
using the new "multisession" capability for those sites that don't support ECDSA.</p>
<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto speakers and schedule announced" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 speakers and schedule announced</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -0,0 +1,605 @@
<div>
<header title="חדשות I2P">הזנת חדשות, ועדכוני נתב</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 עם תיקוני תקלים</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 עם תיקוני תקלים</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 עם תיקוני תקלים</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 עם תיקוני תקלים</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 עם תיקוני תקלים</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 עם תיקוני תקלים</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 עם צלמיות חדשות</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 עם שיפורי ביצועים</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 עם אשף התקנה חדש</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P ב־35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 עם NTCP2 מאופשר</summary></details><p>0.9.37 מאפשר פרוטוקול העברה מאובטח יותר ומהיר יותר הנקרא NTCP2.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 עם NTCP2 ותיקוני תקלים</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>שחרור זה מכיל גם מספר שיפורי ביצועים ותיקוני תקלים.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 עם תיקיות SusiMail ואשף SSL</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 עם תיקוני תקלים</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 עם תיקוני תקלים</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>סוגיות אבטחה נמצאו בכל מערכת כמעט</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="שנה טובה! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>שנה חדשה ו־I2P ב־34C3</summary></details><p>שנה טובה לכולם מצוות I2P!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 עם עדכוני מסוף</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 עם עדכוני מסוף</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="קריאה למתרגמים" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>לשחרור 0.9.31 העתידי יש מחרוזות בלתי מתורגמות יותר מהרגיל</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
it if you could set aside a little more time than usual during this release cycle
in order to bring the translations up to speed. We have pushed the strings early
to give you three weeks to work on them.</p>
<p>If you're not currently an I2P translator, now would be a great time to get
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
<p>Several plugins are not compatible with Jetty 9 and must be updated.
The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
i2pbote 0.4.6; zzzot 0.15.0.
The following plugins (with current versions listed) will not work with 0.9.30.
Contact the appropriate plugin developer for the status of new versions:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 מכיל תיקוני תקלים</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote פְּגִיעוּת אבטחה" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote פְּגִיעוּת אבטחה</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 מכיל תיקוני תקלים</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote פְּגִיעוּת אבטחה" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote פְּגִיעוּת אבטחה</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
for this.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 מכיל תיקוני תקלים</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
which will speed up crypto operations considerably.
Also, we are now using constant-time GMP functions to prevent side-channel attacks.
For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
we will include them for in-net updates in the 0.9.27 release.</p>
<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
<p>There's a collection of bug fixes also, including a fix for a timer bug
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contains SAM 3.3, QR codes, and bug fixes</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
It adds QR codes for sharing hidden service addresses with others,
and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
to make it easier to declare that your group of routers is run by a single person.
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
Your router will not automatically update if you are using Java 6.</p>
<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration,
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
<p><b>ניהול משק־בית</b></p>
<p>My signing key has been in router updates for over two years (since 0.9.9), so
if you are on a recent version of I2P this update should be just as easy as
every other update. However, if you are running an older version than 0.9.9, you
will first need to manually update to a recent version. Update files for recent
versions can be downloaded
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
and instructions on how to manually update are provided
<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
updated, your router will then find and download the 0.9.23 update as usual.</p>
<p>If you installed I2P via a package manager, you are not affected by the change,
and can update as usual.</p>
<p><b>פרטי עדכון</b></p>
<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
with at least half of the network already estimated to have rekeyed. This
release accelerates the rekeying process. To reduce network churn, your router
will have a small probability of converting to Ed25519 at each restart. When it
does rekey, expect to see lower bandwidth usage for a couple of days as it
reintegrates into the network with its new identity.</p>
<p>Note that this will be the last release to support Java 6. Please update to
Java 7 or 8 as soon as possible. We are already working to make I2P compatible
with the upcoming Java 9, and some of that work is in this release.</p>
<p>We have also made some minor improvements in I2PSnark, and added a new page in
the routerconsole for viewing older news items.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 שוחרר" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
and use bandwidth more effectively.
We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
using the new "multisession" capability for those sites that don't support ECDSA.</p>
<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto speakers and schedule announced" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 speakers and schedule announced</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -0,0 +1,637 @@
<div>
<header title="I2P Hírek">Hírfolyam és router frissítések</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 IPv6 hibajavításokkal</summary></details><p>0.9.50-vel folytatódik a router titkosítási kulcsok áttérése a ECIES-X25519-re
Engedélyeztük a HTTPS-en keresztüli DNS-t az újratápláláshoz, hogy védjük felhasználóinkat a passzív DNS szimatolástól.
Számos javítás és fejlesztés került bele a kiadásba az IPv6 címekkel kapcsolatban, ideértve új UPnP támogatást.</p>
<p>Végre kijavítottunk néhány hosszú ideje fennálló SusiMail romlási hibát. A sávszélességi korlátozó változtatásai javítani fogják a hálózati alagutak teljesítményét. Van néhány Docker konténerre vonatkozó fejlesztésünk. Fejlesztettük a hálózati védelmünket lehetséges rosszindulató vagy hibás routerek ellen.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 hibajavításokkal</summary></details><p>A 0.9.43-as kiadásban folytatódott a munka az erősebb biztonsági és adatvédelmi képességeken és a teljesítmény fejlesztésén.
Az új bérletkészlet specifikáció (LS2) szerinti implementációnk már teljes.
Megkezdjük az implementálását az erősebb és gyorsabb végponttól-végpontig titkosításnak (144-es javaslat) egy jövőbeli kiadáshoz.
Számos IPv6 cím detektálási probléma lett kijavítva, és természetesen egyéb hibák is ki lettek javítva.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 hibajavításokkal</summary></details><p>A 0.9.42-es verzióban folytatódott a munka az I2P gyorsabbá és biztonságosabbá tételében.
Tartalmaz néhány módosítást az UDP átvitel felgyorsítására.
Szétválasztottuk a konfigurációs fájlokat így lehetővé téve a munkát egy modulárisabb csomagoláson.
Folytatjuk a munkát az újabb javaslatok implementálásával a gyorsabb és biztonságosabb titkosítás érdekében.
És persze rengeteg hiba is ki lett javítva.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 hibajavításokkal</summary></details><p>A 0.9.41 verziójú kiadásban folytatódott a munka az új funkciók megvalósításával a 123-as
indítványhoz, beleértve a kliensenkénti hitelesítéssel a titkosított bérletkészletekhez.
A konzol frissített I2P logót és néhány új ikont kapott.
A Linux-os telepítőt frissítettük.</p>
<p>Az elindulásnak gyorsabbnak kellene lennie olyan platformokon mint pl. a Raspberry Pi.
Kijavítottunk számos hibát, beleértve néhány komolyabbat amelyek az alacsony szintű
hálózati üzeneteket érintették.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 új ikonokkal</summary></details><p>A 0.9.40 verziójú kiadás tartalmazza a támogatást az új titkosított bérletkészlet
formátumhoz.
A régi NTCP1 átviteli protokollt letiltottuk.
Van új SusiDNS importálás funkció és egy új szkriptelt szűrési mechanizmus
a beérkező kapcsolatokhoz.</p>
<p>Rengeteget fejlesztettünk a natív OSX-es telepítőn és az IzPack telepítőt
szintén frissítettük.
A munka folytatódik a konzol új ikonokkal való felfrissítésével.
És mint mindig, rengeteg hibát is kijavítottunk!</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 teljesítményjavításokkal</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 új telepítővarázslóval</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 engedélyezett NTCP2-vel</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 NTCP2-vel és hibajavításokkal</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 SusiMail mappákkal és SSL varázslóval</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 hibajavításokkal</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 hibajavításokkal</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 konzol frissítésekkel</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 konzol frissítésekkel</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
it if you could set aside a little more time than usual during this release cycle
in order to bring the translations up to speed. We have pushed the strings early
to give you three weeks to work on them.</p>
<p>If you're not currently an I2P translator, now would be a great time to get
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 frissítések a Jetty 9-hez</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
<p>Several plugins are not compatible with Jetty 9 and must be updated.
The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
i2pbote 0.4.6; zzzot 0.15.0.
The following plugins (with current versions listed) will not work with 0.9.30.
Contact the appropriate plugin developer for the status of new versions:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 hibajavításokat tartalmaz</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 hibajavításokat tartalmaz</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
for this.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 hibajavításokat tartalmaz</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 titkosítási frissítéseket, Debian csomagolási fejlesztéseket és hibajavításokat tartalmaz</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
which will speed up crypto operations considerably.
Also, we are now using constant-time GMP functions to prevent side-channel attacks.
For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
we will include them for in-net updates in the 0.9.27 release.</p>
<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
<p>There's a collection of bug fixes also, including a fix for a timer bug
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 SAM 3.3-at, QR kódokat és hibajavításokat tartalmaz</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
It adds QR codes for sharing hidden service addresses with others,
and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
to make it easier to declare that your group of routers is run by a single person.
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 számos hibajavítást és gyorsítást tartalmaz</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
Your router will not automatically update if you are using Java 6.</p>
<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration,
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 különféle hibajavításokat és az I2PSnark-ban néhány kisebb fejlesztést tartalmaz</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
<p><b>Housekeeping</b></p>
<p>My signing key has been in router updates for over two years (since 0.9.9), so
if you are on a recent version of I2P this update should be just as easy as
every other update. However, if you are running an older version than 0.9.9, you
will first need to manually update to a recent version. Update files for recent
versions can be downloaded
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
and instructions on how to manually update are provided
<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
updated, your router will then find and download the 0.9.23 update as usual.</p>
<p>If you installed I2P via a package manager, you are not affected by the change,
and can update as usual.</p>
<p><b>Update details</b></p>
<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
with at least half of the network already estimated to have rekeyed. This
release accelerates the rekeying process. To reduce network churn, your router
will have a small probability of converting to Ed25519 at each restart. When it
does rekey, expect to see lower bandwidth usage for a couple of days as it
reintegrates into the network with its new identity.</p>
<p>Note that this will be the last release to support Java 6. Please update to
Java 7 or 8 as soon as possible. We are already working to make I2P compatible
with the upcoming Java 9, and some of that work is in this release.</p>
<p>We have also made some minor improvements in I2PSnark, and added a new page in
the routerconsole for viewing older news items.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 hibajavításokkal és az Ed25519-re való áttérés megkezdésével</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Megjelent" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 megjelent teljesítmény- és hibajavításokkal.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
and use bandwidth more effectively.
We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
using the new "multisession" capability for those sites that don't support ECDSA.</p>
<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
hogy a legfrissebb kiadást futtatod.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto speakers and schedule announced" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 speakers and schedule announced</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -1,8 +1,190 @@
<div>
<header title="Berita I2P">Umpan berita, dan pembaruan router</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<header title="Berita I2P">Umpan berita, dan pembaruan router</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 telah dirilis" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 dirilis</summary></details><p>I2P 2.6.1 dirilis dalam rangka memperbaiki bug Antar-Muka di dalam aplikasi Hidden Service Manager.
Bug ini menyebabkan tidak bisa melakukan pengguliran, membuat beberapa konfigurasi tidak dapat diakses.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 telah dirilis" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 dirilis</summary></details><p>Perilisan I2P 2.6.0 ini, melanjutkan pekerjaan kami dalam memperbaiki bug, penambahan fitur, dan meningkatkan keandalan jaringan.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P tidak lagi mengizinkan I2P-over-Tor, sambungan dari Tor keluar alamat IP kini diblok.
Kami tidak menyarankan hal ini karena hal itu menurunkan kinerja I2P dan menggunakan seluruh sumber daya Tor keluar tanpa manfaat.
Jika Anda adalah orang yang suka membantu yang menjalankan baik Tor Exit dan I2P, kami menyarankan Anda untuk lanjut melakukan hal tersebut, menggunakan alamat IP berbeda untuk masing-masing.
Non-exit relai dan klien Tor tidak terpengaruh oleh hal ini dan tidak perlu melakukan perubahan apapun.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 dengan perbaikan HTTP</summary></details><p>I2P 2.5.2 dirilis untuk memperbaiki sebuah bug yang ditemukan di versi 2.5.0 yang kadang membuat konten HTTP menjadi terpotong.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 dirilis" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>Rilis I2P 2.5.1 dirilis untuk mengatasi serangan denial of service (DOS)</summary></details><p>I2P 2.5.1 dirilis untuk mengatasi serangan DOS yang mempengaruhi jaringan dan layanan I2P.
Dengan rilis ini kami menonaktifkan bagian berbasis IP dari alat pendeteksi serangan Sybil yang ditargetkan untuk memperkuat efek dan durasi serangan.
Ini akan membantu jaringan kembali ke operasi normal.
Anda yang telah menonaktifkan alat deteksi serangan Sybil dapat mengaktifkannya kembali dengan aman.
Penyesuaian pada subsistem lain untuk meningkatkan validasi Routerinfo dan pemilihan peer juga telah dilakukan.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Cuaca Badai" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Cuaca Jaringan: Badai. I2P sedang diserang.</summary></details><p>Jaringan I2P saat ini berada dalam serangan DOS.
Serangan ini mempengaruhi I2P dan i2pd tetapi dengan cara yang berbeda dan mempunyai dampak serius pada kesehatan jaringan.
Jangkauan situs I2P sangat terdegradasi.</p>
<p>Jika Anda me-hosting layanan di dalam I2P dan di-hosting di floodfill router, Anda harus mempertimbangkan multihoming layanan pada router yang floodfill-nya dinonaktifkan, untuk meningkatkan jangkauan.
Mitigasi lain sedang dibahas tetapi solusi jangka panjang dan kompatibel dengan versi -versi sebelumnya masih sedang dikerjakan.
</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="Rilis baru I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>Lebih Banyak Peningkatan Aplikasi, Audit strategi Isolasi NetDB</summary></details><p>Rilis I2P 2.5.0 ini memberikan lebih banyak perbaikan bagi pengguna dibandingkan rilis 2.4.0, yang berfokus pada penerapan strategi isolasi NetDB.</p>
<p>Fitur-fitur baru telah ditambahkan ke I2PSnark seperti kemampuan untuk mencari melalui torrent. Bug telah diperbaiki untuk meningkatkan kompatibilitas dengan klien I2P torrent lainnya seperti BiglyBT dan qBittorrent. Kami ingin mengucapkan terima kasih kepada semua pengembang yang telah bekerja dengan libtorrent dan qBittorrent untuk mengaktifkan dan meningkatkan dukungan I2P mereka. Fitur-fitur baru juga telah ditambahkan ke SusiMail termasuk dukungan untuk pemformatan Markdown di dalam email dan kemampuan untuk drag-and-drop lampiran ke dalam email. Tunnels dibuat dengan Hidden Services manager sekarang mendukung "Keepalive" yang meningkatkan kinerja dan kompatibilitas dengan teknologi web, memungkinkan situs I2P yang lebih canggih.</p>
<p>Selama rilis ini kami juga membuat beberapa penyesuaian terhadap NetDB untuk meningkatkan ketahanannya terhadap spam dan untuk meningkatkan kemampuan router untuk menolak pesan yang mencurigakan. Ini adalah bagian dari upaya untuk "mengaudit" penerapan pertahanan "Sub-DB isolation" dari rilis 2.4.0. Investigasi ini mengungkap satu peristiwa kecil yang mengganggu isolasi, yang sudah kami perbaiki. Masalah ini ditemukan dan diperbaiki secara internal oleh tim I2P.</p>
<p>Selama rilis ini beberapa perbaikan dilakukan pada proses rilis distribusi hilir kami untuk Android dan Windows. Ini akan menghasilkan peningkatan pengiriman dan ketersediaan untuk produk-produk downstream.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="Rilis I2P 2.4.0 dengan peningkatan Congestion dan keamanan NetDB" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>Rilis I2P 2.4.0 dengan peningkatan Congestion dan keamanan NetDB</summary></details><p>Rilis ini, I2P 2.4.0, melanjutkan upaya kami untuk meningkatkan keamanan dan stabilitas jaringan I2P. Rilis ini berisi perbaikan signifikan pada Network Database, sebuah struktur penting dalam jaringan I2P yang digunakan untuk menemukan peers.</p>
<p>Perubahan penanganan congestion akan meningkatkan stabilitas jaringan dengan memberikan router kemampuan untuk meringankan peers yang macet dengan cara menghindari mereka. Ini akan membantu jaringan membatasi efek tunnel spam. Ini juga akan membantu pemulihan jaringan selama dan setelah serangan DDOS.</p>
<p>Perubahan NetDB juga membantu mengamankan setiap router dan aplikasi yang menggunakannya. Router sekarang dapat bertahan dengan memisahkan NetDB menjadi beberapa "sub-DB" yang kami gunakan untuk mencegah kebocoran informasi antara aplikasi dan router. Ini juga meningkatkan informasi yang tersedia untuk router Java tentang aktivitas NetDB mereka dan menyederhanakan dukungan kami untuk aplikasi multihoming.</p>
<p>Juga termasuk sejumlah perbaikan bug dan peningkatan di seluruh aplikasi I2PSNark dan SusiMail.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
</article><article id="urn:uuid:" title="Rilis Baru I2P 2.3.0 - Perbaikan Keamanan, blocklist yang Dapat Diubah, API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Perbaikan Keamanan, Blocklist yang dapat diubah, DTG API</summary></details><p>Rilis ini berisi perbaikan untuk CVE-2023-36325. CVE-2023-36325 adalah bug contex-confusing yang terjadi di filter bloom. Penyerang membuat pesan I2NP yang berisi messageID unik, dan mengirimkan messageID tersebut ke sebuah klien. Pesan tersebut, setelah melewati filter Bloom, tidak diizinkan untuk digunakan kembali di dalam pesan kedua. Penyerang kemudian mengirim pesan yang sama langsung ke router. Router meneruskan pesan ke filter bloom lalu pesan tersebut dibuang. Ini membocorkan informasi yang telah dilihat oleh MessageID sebelumnya, memberi penyerang alasan yang kuat untuk percaya bahwa router menjadi hosting klien. Ini telah diperbaiki dengan memisahkan fungsionalitas filter bloom ke dalam konteks yang berbeda, apakah pesan turun ke tunnel klien atau tunnel eksplorasi, dikirim ke router secara langsung. Dalam keadaan normal, serangan ini membutuhkan waktu beberapa hari untuk berhasil dan dapat dikacaukan oleh beberapa faktor seperti router yang memulai kembali selama fase serangan dan sensitivitas terhadap false-positive. Pengguna Java I2P disarankan untuk segera mengupdate untuk menghindari serangan.</p>
<p>Dalam rangka memperbaiki bug contex confusion ini, kami telah merevisi beberapa strategi kami untuk membuat kode secara defensif, terhadap jenis kebocoran ini. Hal ini termasuk penyesuaian pada netDb, mekanisme rate-limiting, dan perilaku router floodfill.</p>
<p>Rilis ini menambahkan not_bob sebagai penyedia host default kedua, dan menambahkan <a href="http://notbob.i2p">notbob.i2p</a> dan <a href="http://ramble.i2p">ramble.i2p</a> ke beranda console.</p>
<p>Rilis ini juga berisi blocklist yang dapat diubah. Blocklist ini bersifat semi-permanen, di mana masing-masing alamat IP yang diblokir biasanya diblokir sampai router di-restart. Pengguna yang mengamati pertumbuhan bloklist eksplosif selama serangan sybil dapat memilih untuk waktu yang lebih pendek dengan mengkonfigurasi blocklist untuk meng-kedaluwarsa entri pada interval tertentu. Fitur ini tidak aktif secara default dan saat ini hanya direkomendasikan untuk pengguna tingkat lanjut.</p>
<p>Rilis ini juga menyertakan API untuk memodifikasi plugin dengan Desktop GUI (DTG). Sekarang dimungkinkan untuk menambahkan item menu ke system tray, memungkinkan peluncuran plugin yang lebih intuitif yang menggunakan antarmuka aplikasi asli.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="Rilis baru 2.2.1, perbaikan paket untuk Docker, Ubuntu Lunar dan Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - rilis pemeliharaan untuk 2.2.0</summary></details><p>Setelah rilis I2P 2.2.0, yang dikedepankan untuk mempercepat mitigasi serangan DDOS, kami belajar tentang beberapa masalah berkembang yang membuatnya perlu untuk membangun dan merilis paket baru. Rilis ini memperbaiki masalah dalam Ubuntu Lunar dan Debian Sid di mana konsol router tidak dapat diakses menggunakan versi terbaru dari paket jakarta. Paket Docker tidak membaca argumen dengan benar, sehingga file konfigurasi tidak dapat diakses. Masalah ini juga telah teratasi. Kontainer Docker sekarang juga kompatibel dengan Podman.</p>
<p>Rilis ini menyinkronkan terjemahan dengan transifex dan memperbarui database GeoIP.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="Rilis Baru 2.2.0, Mitigasi terhadap serangan DDOS dan penyesuaian pada subsistem Streaming" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigasi terhadap serangan DDOS dan penyesuaian pada subsistem Streaming</summary></details><p>Kami telah memilih untuk memajukan tanggal rilis 2.2.0, yang akan terjadi hari ini, 13 Maret 2023. Rilis ini mencakup perubahan pada komponen NetDB, Floodfill, dan Peer-Selection yang meningkatkan kemampuan router untuk bertahan dari serangan DDOS. Serangan ini kemungkinan akan terus berlanjut, tetapi perbaikan sistem ini akan membantu mengurangi risiko serangan DDOS dengan membantu router mengidentifikasi dan menurunkan prioritas router yang tampak berbahaya.</p>
<p>Rilis ini juga menambahkan perlindungan replay ke subsistem Streaming, yang mencegah penyerang yang dapat menangkap paket terenkripsi untuk dapat menggunakannya kembali, dengan mengirimkannya ke penerima yang tidak dituju. Ini adalah perubahan yang backward-compatible, sehingga router versi sebelumnya masih dapat menggunakan kemampuan streaming dari router yang lebih baru. Masalah ini ditemukan dan diperbaiki secara internal, oleh tim pengembangan I2P, dan tidak terkait dengan serangan DDOS. Kami belum pernah menemukan paket streaming replay di luar I2P dan tidak yakin serangan streaming replay pernah terjadi terhadap jaringan I2P saat ini.</p>
<p>Seperti yang mungkin Anda perhatikan, catatan rilis ini dan rilis itu sendiri telah ditandatangani oleh idk, bukan ZZZ. zzz telah memilih untuk keluar dari proyek dan tanggung jawabnya diambil alih oleh anggota tim lainnya. Dengan demikian, proyek ini sedang berupaya mengganti infrastruktur statistik jaringan dan memindahkan forum pengembangan ke i2pforum.i2p. Kami berterima kasih kepada zzz karena telah menyediakan layanan ini untuk waktu yang lama.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="Pembaruan DDoS" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>Pembaruan DDoS</summary></details><p>Kami telah mengkonfirmasi bahwa penyerang mengendalikan sejumlah besar router. Investigasi dan mitigasi kami masih berlanjut.</p>
<p>Ini saat yang tepat untuk mengingatkan semua oranag bahwa bahkan setelah 20 tahun, jaringan I2P masih relatif kecil. Kami tidak memiliki bukti bahwa penyerang berupaya mendeanonimkan pengguna atau layanan tersembunyi tertentu. Namun, jika Anda memiliki model ancaman berisiko tinggi, Anda harus hati-hati mempertimbangkan apakah I2P saat ini memberikan perlindungan yang Anda butuhkan. Solusi terbaik dalam jangka panjang adalah menyebarkan dan menumbuhkan jaringan I2P untuk meningkatkan keamanan pengguna kami.</p>
<p>Kami akan memberikan informasi tambahan di sini di news feed dan di <a href="http://zzz.i2p">zzz.i2</a> seperlunya. Kami meminta kesabaran Anda saat kami berupaya meningkatkan I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="Tentang serangan DDOS baru -baru ini" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P tetap utuh dengan gangguan kinerja</summary></details><p>Jaringan I2P saat ini dipengaruhi oleh serangan DDOS. Fungsi jaringan floodfill telah terpengaruh, mengakibatkan respons terganggu dan tingkat keberhasilan pembangunan tunnel menurun. Peserta jaringan telah mengalami kesulitan yang terhubung ke situs I2P dan menggunakan layanan I2P. Strategi mitigasi sedang diselidiki dan diterapkan secara bertahap.</p>
<p>Meskipun serangan tersebut telah menurunkan kinerja, jaringan tetap utuh dan dapat digunakan. Router Java I2P tampaknya menangani masalah ini lebih baik daripada router i2pd untuk saat ini. Berbagai mitigasi harus mulai muncul di dev build untuk router Java dan C ++ di pekan depan.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 dengan banyak perbaikan SSU2</summary></details><p>Kami telah mempelajari beberapa hal sejak rilis 2.0.0 kami pada bulan November. Karena router telah diperbarui ke rilis tersebut, dukungan jaringan telah berubah dari sekitar 1% menjadi lebih dari 60% untuk protokol transport SSU2 baru kami. Pertama, kami telah mengkonfirmasi bahwa SSU2 adalah protokol yang solid, dirancang dengan baik, dan aman. Kedua, namun, kami telah menemukan dan memperbaiki banyak bug minor atau yang jarang dipicu dalam implementasi protokol. Secara kumulatif, dampak bug ini telah menurunkan kinerja jaringan.</p>
<p>Juga, kami menyadari peningkatan jumlah tunnel dan pengurangan tingkat keberhasilan pembuatan tunnel dalam jaringan, mungkin dipicu oleh fitur alamat transien I2P baru Bitcoin, tetapi diperburuk oleh bug SSU2 kami dan masalah kontrol congestion lainnya. Kami bekerja dengan Bitcoin dan proyek non-Bitcoin lainnya untuk mengurangi tuntutan jaringan I2P. Kami telah meningkatkan algoritma kami untuk mengurangi beban jaringan selama masa congestion. Kami juga berkolaborasi dengan i2pd untuk mengembangkan strategi pengendalian congestion umum.</p>
<p>Oleh karena itu, kami telah mempercepat rilis ini sekitar enam pekan, untuk mengirimkan perbaikan kepada semua orang. i2pd merilis versi 2.45.0 pekan lalu dan hasil awalnya menggembirakan. Protokol baru, dan jaringan terdistribusi, sulit dikembangkan. Congestion bisa tiba dengan sedikit peringatan dan dengan sedikit petunjuk untuk penyebabnya. Terima kasih atas kesabaran Anda karena kami telah mendiagnosis dan semoga masalahnya dapat diperbaiki.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>Transportasi SSU2 diaktifkan</summary></details><p>I2P release 2.0.0 mengaktifkan UDP transport SSU2 baru kami untuk semua pengguna, setelah menyelesaikan fitur kecil, pengujian, dan banyak perbaikan bug.</p>
<p>Kami juga membuat banyak perbaikan, termasuk untuk installer, database jaringan, menambah buku alamat pribadi, peluncur Windows Browser, dan IPV6 UPNP.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Postingan Blog Terbaru" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Beberapa posting blog terbaru</summary></details><p>Berikut tautan ke beberapa posting blog terbaru di situs web kami:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transportasi">Tinjauan umum transport SSU2 baru kami</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">Peringatan tentang koin I2P dan penipuan lainnya</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">Wawancara dengan Konrad dari diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">Wawancara dengan Dustin dari StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 dengan SSU2 untuk pengujian</summary></details><p>Kami telah menghabiskan tiga bulan terakhir mengembangkan protokol transportasi UDP baru kami "SSU2" dengan sejumlah kecil penguji sukarela. Rilis ini menyelesaikan implementasi, termasuk pengujian relay dan peer. Kami mengaktifkannya secara default untuk platform Android dan ARM, dan sebagian kecil dari router lain secara acak. Ini akan memungkinkan kami untuk melakukan lebih banyak pengujian dalam tiga bulan ke depan, menyelesaikan fitur migrasi koneksi, dan memperbaiki masalah yang tersisa. Kami berencana untuk mengaktifkannya untuk semua orang pada rilis berikutnya yang dijadwalkan pada bulan November. Tidak diperlukan konfigurasi manual.</p>
<p>Tentu saja, ada banyak perbaikan bug di rilis ini. Kami juga menambahkan detektor deadlok otomatis yang telah menemukan deadlock langka yang sekarang sudah diperbaiki.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="Outproxy baru exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>Outproxy baru</summary></details><p>I2P "Outproxies" (exit node) dapat digunakan untuk mengakses internet melalui tunnel proxy HTTP Anda. Sebagaimana disetujui dalam <a href="http://i2p-projekt.i2p/en/meetings/314">pertemuan bulanan</a>kami, <b>exit.stormycloud.i2p</b> kini menjadi proksi resmi kami yang direkomendasikan, menggantikan <b>false.i2p</b>yang sudah lama tidak aktif. Untuk informasi lebih lanjut tentang <a href="http://stormycloud.i2p/">organisasi</a>StormyCloud, <a href="http://stormycloud.i2p/outproxy.html">outproxy</a>, dan <a href="http://stormycloud.i2p/tos.html">persyaratan layanan</a>, lihat <a href="http://stormycloud.i2p/">situs web StormyCloud</a>.</p>
<p>Kami menyarankan Anda mengubah <a href="/i2ptunnel/edit?tunnel=0">konfigurasi Hidden Services Manager Anda </a> untuk menentukan <b>exit.stormycloud.i2p </b> di dua tempat: <b>Outproxies </b> dan <b>SSL Outproxies &lt;/bo B3&gt;. Setelah mengedit, <b>scroll ke bawah dan klik Simpan</b>. Lihat posting blog <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">kami untuk melihat tangkapan layar </a>. Untuk instruksi di Android dan tangkapan layar, lihat&lt;A6&gt;Blog notbob .</b></p>
<p>Pembaruan router tidak akan memperbarui konfigurasi Anda, Anda harus mengeditnya secara manual. Terima kasih kepada StormyCloud atas dukungannya, dan mohon pertimbangkan untuk memberikan<a href="http://stormycloud.i2p/donate.html">donasi</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 dengan perbaikan bug</summary></details><p>Rilis ini termasuk perbaikan bug di I2PSNark, router, I2CP, dan UPnP. Router memperbaiki bug alamat dalam soft restart, IPv6, pengujian peer SSU, penyimpanan database jaringan, dan pembangunan tunnel. Penanganan family router dan klasifikasi Sybil juga telah ditingkatkan secara signifikan.</p>
<p>Bersama dengan i2pd, kami mengembangkan transport UDP baru kami, SSU2. SSU2 akan memberikan peningkatan kinerja dan keamanan yang substansial. Hal ini juga memungkinkan kami untuk mengganti enkripsi ElGamal yang sangat lambat, menyelesaikan peningkatan kriptografi penuh yang kami mulai sekitar 9 tahun yang lalu. Rilis ini berisi implementasi awal yang dinonaktifkan secara default. Jika Anda ingin berpartisipasi dalam pengujian, silakan cari informasi saat ini di zzz.I2Pp.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Instal pembaruan penting Java/Jpackage" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>Kerentanan Java "Psychic Signatues" baru-baru ini mempengaruhi I2P. Pengguna I2P saat ini di Linux, atau pengguna I2P mana pun yang menggunakan JVM yang tidak dibundel harus memperbarui JVM mereka atau beralih ke versi yang tidak mengandung kerentanan, di bawah Java 15.</p>
<p>Bundel I2P Easy-Install baru telah dibuat menggunakan rilis terbaru Java Virtual Machine. Rincian lebih lanjut telah diterbitkan di bundle newsfeeds masing -masing.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 dengan peningkatan keandalan dan kinerja</summary></details><p>Rilis 1.7.0 berisi beberapa peningkatan kinerja dan keandalan.</p>
<p>Sekarang ada pesan popup di system tray, untuk platform yang mendukungnya. i2psnark memiliki editor torrent baru. Transport NTCP2 sekarang menggunakan lebih sedikit CPU.</p>
<p>Antarmuka BOB, yang sudah lama tidak digunakan lagi, sudah dihapus untuk instalasi baru. Ini akan terus berfungsi pada instalasi yang sudah ada, kecuali untuk paket Debian. Pengguna aplikasi BOB yang tersisa harus meminta pengembang untuk mengkonversi ke protokol SAMv3.</p>
<p>Kami tahu bahwa sejak rilis 1.6.1, keandalan jaringan terus menurun. Kami menyadari masalah ini setelah rilis dikeluarkan, namun kami memerlukan waktu hampir dua bulan untuk menemukan penyebabnya. Kami akhirnya mengidentifikasinya sebagai bug di i2pd 2.40.0, dan perbaikannya akan dilakukan pada rilis 2.41.0 yang akan dirilis pada waktu yang hampir bersamaan dengan rilis ini. Sejalan dengan ini, kami telah membuat beberapa perubahan di sisi Java I2P untuk meningkatkan ketahanan pencarian database jaringan dan store, dan menghindari peers yang berkinerja buruk dalam pemilihan tunnel peers. Ini akan membantu jaringan menjadi lebih kuat bahkan di hadapan router yang punya banyak bug atau berniat jahat. Selain itu, kami memulai program bersama untuk menguji router i2pd pra-rilis dan router Java I2P bersama-sama dalam jaringan pengujian yang terisolasi, sehingga kami dapat menemukan lebih banyak masalah sebelum rilis, bukan setelahnya.</p>
<p>Dalam berita lain, kami terus membuat kemajuan besar dalam desain transport UDP baru kami "SSU2" (proposal 159) dan telah memulai implementasi. SSU2 akan memberikan peningkatan kinerja dan keamanan yang substansial. Hal ini juga memungkinkan kami untuk menggantikan penggunaan terakhir kami atas enkripsi ElGamal yang sangat lambat, menyelesaikan peningkatan kriptografi penuh yang dimulai sekitar 9 tahun yang lalu. Kami berharap dapat segera memulai pengujian bersama dengan i2pd, dan meluncurkannya ke jaringan pada akhir tahun ini.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 mengaktifkan pesan pembuatan tunnel baru</summary></details><p>Rilis ini melengkapi peluncuran dua pembaruan protokol utama yang dikembangkan pada tahun 2021. Transisi ke enkripsi X25519 untuk router dipercepat, dan kami memperkirakan hampir semua router akan mendapat rekey pada akhir tahun ini. Pesan pembuatan short tunnel diaktifkan untuk pengurangan bandwidth yang signifikan.</p>
<p>Kami menambahkan panel pemilihan tema ke wizard penginstalan baru. Kami telah meningkatkan kinerja SSU dan memperbaiki masalah dengan pesan uji peer SSU. Filter Bloom pembuatan tunnel telah disesuaikan untuk mengurangi penggunaan memori. Kami telah meningkatkan dukungan untuk plugin non-Java.</p>
<p>Dalam berita lain, kami membuat kemajuan yang sangat baik pada desain UDP Transport SSU2 baru kami dan berharap untuk memulai implementasi awal tahun depan.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 dengan pesan tunnel build baru</summary></details><p>Ya, benar, setelah 9 tahun rilis 0.9.x, kita langsung beralih dari 0.9.50 ke 1.5.0. Hal ini tidak menandakan adanya perubahan besar pada API, atau klaim bahwa pengembangan telah selesai. Ini hanyalah pengakuan atas kerja keras selama hampir 20 tahun untuk memberikan anonimitas dan keamanan bagi pengguna kami.</p>
<p>Rilis ini menyelesaikan implementasi pesan tunnel build yang lebih kecil untuk mengurangi bandwidth. Kami melanjutkan transisi router jaringan ke enkripsi X25519. Tentu saja ada banyak juga perbaikan bug dan peningkatan kinerja.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Kerentanan Desktop MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Kerentanan Desktop MuWire</summary></details><p>Kerentanan keamanan telah ditemukan dalam aplikasi desktop standalone MuWire. Ini tidak mempengaruhi plugin console, dan tidak terkait dengan masalah plugin yang diumumkan sebelumnya. Jika Anda menjalankan aplikasi desktop MuWire, Anda harus <a href="http://muwire.i2p/">segera memperbarui ke versi 0.8.8</a>.</p>
<p>Detail masalah ini akan dipublikasikan di <a href="http://muwire.i2p/security.html">muwire.i2p</a> pada 15 Juli 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Kerentanan Plugin MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Kerentanan Plugin MuWire</summary></details><p>Kerentanan keamanan telah ditemukan di plugin MuWire. Itu tidak mempengaruhi klien desktop standalone. Jika Anda menjalankan plugin MuWire, Anda harus <a href="/configplugins">segera memperbarui ke versi 0.8.7-b1</a>.</p>
<p>Lihat <a href="http://muwire.i2p/security.html">muwire.i2p </a> untuk informasi lebih lanjut tentang kerentanan dan rekomendasi keamanan yang diperbarui.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 dengan perbaikan IPv6</summary></details><p>0.9.50 melanjutkan transisi ke ECIES-X25519 untuk kunci enkripsi router. Kami telah mengaktifkan DNS melalui HTTPS untuk reseeding guna melindungi pengguna dari DNS snooping pasif. Ada banyak perbaikan dan peningkatan untuk alamat IPv6, termasuk dukungan UPnP baru.</p>
<p>Kami akhirnya telah memperbaiki beberapa bug korupsi SusiMailmail yang sudah berlangsung lama. Perubahan pada batasan bandwidth akan meningkatkan kinerja tunnel jaringan. Ada beberapa perbaikan pada container Docker kami. Kami telah meningkatkan pertahanan kami untuk kemungkinan router berbahaya dan rentan di dalam jaringan.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 dengan perbaikan SSU dan kripto yang lebih cepat</summary></details><p>0.9.49 melanjutkan membuat I2P lebih cepat dan lebih aman. Kami memiliki beberapa perbaikan dan perbaikan pada transportasi SSU (UDP) yang akan menghasilkan kecepatan lebih tinggi. Rilis ini juga memulai migrasi ke enkripsi baru, ECIES-X25519 yang lebih cepat untuk router. (Destinations telah menggunakan enkripsi ini untuk beberapa rilis sekarang) Kami telah mengerjakan spesifikasi dan protokol untuk enkripsi baru selama beberapa tahun, dan kami hampir selesai! Migrasi ini akan memerlukan beberapa rilis untuk diselesaikan.</p>
<p>Untuk rilis ini, untuk meminimalkan gangguan, hanya instalasi baru dan persentase yang sangat kecil dari instalasi yang sudah ada (dipilih secara acak saat restart) yang akan menggunakan enkripsi baru. Jika router Anda melakukan "rekey" untuk menggunakan enkripsi baru, mungkin memiliki lalu lintas yang lebih rendah atau lebih sedikit keandalan dari biasanya selama beberapa hari setelah Anda restart. Ini normal karena router Anda telah menghasilkan identitas baru. Performa Anda akan pulih setelah beberapa saat.</p>
<p>Kami telah "rekey" jaringan dua kali sebelumnya, ketika mengubah tipe signatur default, tetapi ini adalah pertama kalinya kami mengubah jenis enkripsi default. Mudah-mudahan semuanya berjalan lancar, tapi kami memulainya perlahan-lahan untuk memastikannya.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 dengan peningkatan kinerja</summary></details><p>0.9.48 mengaktifkan protokol enkripsi end-to-end kami yang baru (proposal 144) untuk sebagian besar layanan. Kami telah menambahkan dukungan awal untuk enkripsi pesan tunnel build baru (proposal 152). Ada peningkatan kinerja yang signifikan di seluruh router.</p>
<p>Paket untuk Ubuntu Xenial (16.04 LTS) tidak lagi didukung. Pengguna pada platform tersebut harus melakukan upgrade distro sehingga Anda dapat terus menerima pembaruan I2P.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 menggunakan enkripsi baru</summary></details><p>0.9.47 mengaktifkan protokol enkripsi end-to-end kami yang baru (proposal 144) secara default untuk beberapa layanan. Alat analisis dan pemblokiran Sybil sekarang diaktifkan secara default.</p>
<p>Java 8 atau lebih tinggi sekarang diperlukan. Paket Debian untuk Wheezy dan Stretch, serta untuk Ubuntu Trusty dan Precise, tidak lagi didukung. Pengguna di platform tersebut harus melakukan upgrade distro untuk terus menerima pembaruan I2P.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 dengan perbaikan bug</summary></details><p>0.9.46 berisi peningkatan kinerja yang signifikan di streaming library. Kami telah menyelesaikan pengembangan enkripsi ECIES (proposal 144) dan sekarang ada opsi untuk mengaktifkannya untuk pengujian.</p>
<p>Hanya untuk Pengguna Windows: Rilis ini memperbaiki kerentanan eskalasi hak istimewa lokal yang dapat dieksploitasi oleh pengguna lokal. Harap terapkan pembaruan sesegera mungkin. Terima kasih kepada Blaze Infosec atas pengungkapan masalah secara bertanggung-jawab.</p>
<p>Ini adalah rilis terakhir yang mendukung Java 7, paket Debian Wheezy and Stretch, dan paket Ubuntu Precise dan Trusty. Pengguna di platform tersebut harus melakukan upgrade distro untuk menerima pembaruan I2P di masa depan.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 telah rilis" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 dengan perbaikan bug</summary></details><p>0.9.45 berisi perbaikan penting untuk mode sembunyi dan pengujian lebar pita (bandwidth).
Ada pembaruan untuk tampilan gelap pada konsol.
Kami terus berupaya meningkatkan kinerja dan pengembangan enkripsi end-to-end yang baru (proposal 144).</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 telah rilis" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 dengan perbaikan bug</summary></details><p>0.9.44 berisi perbaikan penting untuk masalah denial of service dalam hidden service yang menangani jenis enkripsi baru. Semua pengguna harus memperbarui sesegera mungkin.</p>
<p>Rilis ini mencakup dukungan awal untuk enkripsi end-to-end yang baru (proposal 144). Pekerjaan berlanjut pada proyek ini, dan belum siap digunakan. Ada perubahan pada halaman beranda console, dan embedded HTML5 media player baru di i2psnark. Perbaikan tambahan untuk jaringan IPv6 yang dilindungi firewall sudah disertakan. Perbaikan Tunnel Build akan menghasilkan startup yang lebih cepat untuk beberapa pengguna.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 dengan perbaikan bug</summary></details><p>Dalam rilis 0.9.43, kami terus bekerja pada fitur keamanan dan privasi yang lebih kuat dan peningkatan kinerja. Implementasi spesifikasi leaseset baru (LS2) kami sekarang lengkap. Kami memulai implementasi enkripsi end-to-end yang lebih kuat dan lebih cepat (proposal 144) untuk rilis di masa depan. Beberapa masalah deteksi alamat IPv6 telah diperbaiki, dan tentunya ada beberapa perbaikan bug lainnya.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 dengan perbaikan bug</summary></details><p>0.9.42 melanjutkan pekerjaan untuk membuat I2P lebih cepat dan lebih dapat diandalkan. Ini mencakup beberapa perubahan untuk mempercepat transport UDP kami. Kami telah membagi file konfigurasi untuk memungkinkan pekerjaan di masa depan untuk pengemasan yang lebih modular. Kami terus berupaya menerapkan proposal baru untuk enkripsi yang lebih cepat dan aman. Tentu saja ada banyak perbaikan bug juga.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 dengan perbaikan bug</summary></details><p>0.9.41 melanjutkan pekerjaan untuk mengimplementasikan fitur-fitur baru untuk proposal 123, termasuk otentikasi per klien untuk leaseset terenkripsi. Console memiliki logo I2P yang diperbarui dan beberapa ikon baru. Kami telah memperbarui penginstal Linux.</p>
<p>Startup akan lebih cepat pada beberapa platform seperti Raspberry Pi. Kami telah memperbaiki beberapa bug, termasuk beberapa yang serius yang mempengaruhi pesan jaringan tingkat rendah.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 dengan ikon baru</summary></details><p>0.9.40 menyertakan dukungan untuk format leaseset terenkripsi yang baru. Kami menonaktifkan protokol transport NTCP 1 yang lama. Ada fitur impor SusiDNS baru, dan mekanisme penyaringan skrip baru untuk koneksi yang masuk.</p>
<p>Kami telah melakukan banyak perbaikan pada penginstal OSX, dan kami telah memperbarui penginstal IzPack juga. Pekerjaan terus dilakukan untuk menyegarkan console dengan ikon baru. Seperti biasa, kami juga memperbaiki banyak bug!</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 dengan peningkatan kinerja</summary></details><p>0.9.39 mencakup perubahan ekstensif untuk tipe database jaringan baru (proposal 123). Kami telah menggabungkan plugin I2pcontrol sebagai webapp untuk mendukung pengembangan aplikasi RPC. Ada banyak peningkatan kinerja dan perbaikan bug.</p>
<p>Kami telah menghapus tema midnight dan classic untuk mengurangi beban pemeliharaan; Pengguna sebelumnya dari tema -tema tersebut sekarang akan melihat tema dark atau light. Ada juga ikon halaman beranda baru, langkah pertama dalam memperbarui console.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 dengan wizard pengaturan baru</summary></details><p>0.9.38 termasuk wizard instal pertama dengan tester bandwidth. Kami telah menambahkan dukungan untuk format database GeoIP terbaru. Ada penginstal profil Firefox baru dan penginstal Mac OSX asli di situs web kami. Pekerjaan terus dilakukan untuk mendukung format netdb "LS2" yang baru.</p>
<p>Rilis ini juga berisi banyak perbaikan bug, termasuk beberapa masalah dengan lampiran susimail, dan perbaikan untuk router khusus IPv6.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="Laporan kunjungan 35C3" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P di 35C3</summary></details><p>Tim I2P sebagian besar hadir di 35C3 di Leipzig. Pertemuan harian diadakan untuk meninjau tahun lalu dan membahas tujuan pengembangan dan desain kami di tahun 2019.</p>
<p>Visi proyek dan roadmap baru dapat<a href="http://i2p-projekt.i2p/en/get-involved/roadmap">diulas di sini </a>.</p>
<p>Pekerjaan akan dilanjutkan pada LS2, Testnet, dan peningkatan kegunaan pada situs web dan console kami. Ada rencana untuk menggunakan Tails, Debian, dan Ubuntu Disco. Kami masih membutuhkan orang untuk mengerjakan perbaikan Android dan I2P_BOTE.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 dengan NTCP2 telah diaktifkan</summary></details><p>0.9.37 memungkinkan protokol transportasi yang lebih cepat dan aman yang disebut sebagai NTCP2.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 dirilis" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 memiliki perbaikan NTCP2 dan bug</summary></details><p>0.9.36 memiliki transport protocol yang baru dan lebih aman bernama NTCP2.
Ini dinonaktifkan secara default, tapi dapat diaktifkan untuk pengujian dengan menambah entry di <a href="/configadvanced">advanced configuration</a>beris <tt>i2np.ntcp2.enable=true</tt> lalu restart router Anda.
NTCP2 akan diaktifkan di rilis berikutnya.</p>
<p>Rilis ini juga berisi beberapa peningkatan kinerja dan perbaikan bug.</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 dirilis" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 dirilis dengan folders SusiMail dan SSL Wizard</summary></details><p>0.9.35 menambah dukungan folders di SusiMail, dan SSL Wizard baru untuk pengaturan HTTPS di situs web Hidden Service Anda.
Ada juga beberapa perbaikan bug, terutama di SusiMail.</p>
<p>Kami berusaha keras untuk memperbaiki versi 0.9.36, termasuk installer baru untuk OSX
dan protol baru yang lebih cepat dan aman, yang bernama NTCP2.</p>
<p>I2P akan hadir di HOPE di New York City, bulan Juli tanggal 20-22. Silakan mampir!</p>
<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 dirilis" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 memiliki perbaikan bug</summary></details><p>0.9.34 memiliki banyak perbaikan bug!
Ada banyak perbaikan di SusiMail, IPv6 handling, and pemilihan tunnel peer.
@ -33,8 +215,7 @@ Makan malam tahunan kita adalah sukses besar sebagai tanda terima kasih kepada s
Versi-versi sebelumnya tidak didukung lagi dan tidak tersedia di rilis Debian Stretch and Ubuntu Zesty mendatang.
Router akan memigrasikan file konfigurasi jetty.xml untuk setiap situs Jetty ke setup Jetty 9 yang baru.
Ini seharusnya berfungsi untuk konfigurasi yang baru dan tidak dimodifikasi, namun mungkin tidak berfungsi untuk pengaturan yang dimodifikasi atau yang sangat lama.
Pastikan situs web Jetty Anda berfungsi setelah melakukan pembaruan, dan hubungi kami di IRC jika memerlukan bantuan.
</p>
Pastikan situs web Jetty Anda berfungsi setelah melakukan pembaruan, dan hubungi kami di IRC jika memerlukan bantuan.</p>
<p>Beberapa plugin tidak kompatibel dengan Jetty 9 sehingga harus diperbarui.
Plugin-plugin berikut telah diperbarui untuk bekerja dengan 0.9.30, dan router Anda harus memperbaruinya setelah restart:
I2pbote 0.4.6; Zzzot 0.15.0

View File

@ -1,10 +1,387 @@
<div>
<header title="I2P News">News feed, e aggiornamenti dei router</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
<header title="I2P News">News feed e aggiornamenti dei router</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="Rilasciata versione 1.9.0" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="Rilasciata versione 1.8.0" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="Rilasciata versione 1.7.0" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="Rilasciata versione 1.6.0" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="Rilasciata versione 1.5.0" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="Rilasciata versione 0.9.50" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="Rilasciata versione 0.9.49" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>Versione 0.9.49 con correzioni SSU e crittografia velocizzata</summary></details><p>La versione 0.9.49 continua il lavoro per rendere I2P più veloce e sicuro.
Abbiamo diversi miglioramenti e correzioni per il trasporto SSU (UDP), il che dovrebbe risultare in una maggiore velocità.
Con questo rilascio inizia inoltre la migrazione per i router verso la nuova e performante cifratura X25519.
(Le destinazioni utilizzano questa cifratura già da qualche rilascio oramai)
Per anni abbiamo lavorato sulle specifiche e sui protocolli per la nuova cifratura e oramai siamo vicinissimi alla fine! La migrazione richiederà diversi rilasci per essere completata.</p>
<p>Per questo rilascio, al fine di minimizzare le interruzioni, solo le nuove installazioni e una piccola percentuale di quelle esistenti (selezionate randomicamente al riavvio) utilizzeranno la nuova cifratura.
Se il tuo router si "riconfigura" per utilizzare la nuova cifratura, potrebbe avere meno traffico o meno affidabilità del normale per diversi giorni dopo il riavvio.
Questa è una situazione normale poichè il tuo router ha generato una nuova identità.
Le tue prestazioni dovrebbero ristabilirsi dopo un certo periodo.</p>
<p>In passato abbiamo già "riconfigurato" due volte la rete per cambiare il tipo di firma di default, ma questa è la prima volta che modifichiamo il tipo di cifratura di default.
Fortunatamente tutto andrà bene, ma stiamo iniziando lentamente per esserne sicuri.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="Rilascio 0.9.48" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>Versione 0.9.48 con miglioramenti delle prestazioni</summary></details><p>La versione 0.9.48 abilita il nostro nuovo protocollo di cifratura end-to-end (proposta 144) per la maggior parte dei servizi.
Abbiamo aggiunto un supporto preliminare per la nuova cifratura dei tunnel build message (proposta 152).
Ci sono miglioramenti significativi delle prestazioni in tutto il router.</p>
<p>I pacchetti per Ubuntu Xenial (16.04 LTS) non sono più supportati.
Gli utenti di quella piattaforma dovrebbero eseguire l'aggiornamento per continuare a ricevere gli aggiornamenti I2P.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="Rilascio 0.9.47" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>La versione 0.9.47 abilita la nuova cifratura</summary></details><p>La versione 0.9.47 abilita di default il nostro nuovo protocollo di cifratura end-to-end (proposta 144) per alcuni servizi.
Lo strumento per il blocco e l'analisi Sybil è ora abilitato di default.</p>
<p>È ora necessario Java 8 o superiori.
I pacchetti Debian per Wheezy e Stretch, e per Ubuntu Trusty e Precise, non sono più supportati.
Gli utenti di queste piattaforme dovrebbero eseguire l'aggiornamento per continuare a ricevere gli aggiornamenti I2P.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="Rilascio 0.9.46" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>Versione 0.9.46 con correzioni di bug</summary></details><p>La versione 0.9.46 contiene miglioramenti significanti delle prestazioni nella libreria streaming.
Abbiamo completato lo sviluppo della cifratura ECIES (proposta 144) ed è ora disponibile un'opzione per abilitarla per il testing.</p>
<p>Solo utenti Windows:
Questo rilascio corregge una vulnerabilità dell'escalation dei privilegi locali che potrebbe venir sfruttata da un utente locale.
Per favore esegui l'aggiornamento il prima possibile.
Grazie a Blaze Infosec per la divulgazione responsabile del problema.</p>
<p>Questo è l'ultimo rilascio che supporta Java 7, i pacchetti Debian Wheezy e Stretch, e i pacchetti Ubuntu Precise e Trusty.
Gli utenti di quelle piattaforme dovrebbero eseguire l'aggiornamento per continuare a ricevere gli aggiornamenti I2P.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="Rilascio 0.9.45" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>Versione 0.9.45 con correzioni di bug</summary></details><p>La versione 0.9.45 contiene importanti correzioni per la modalità hidden e per il tester di larghezza di banda.
C'è un aggiornamento per il tema scuro della console.
Continuiamo a lavorare sull'aumento delle prestazioni e a sviluppare la nuova cifratura end-to-end (proposta 144).</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="Rilascio 0.9.44" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>Versione 0.9.44 con correzioni di bug</summary></details><p>La versione 0.9.44 contiene una correzione per un problema di denial of service riguardante i servizi nascosti che utilizzano i nuovi tipi di cifratura.
Tutti gli utenti dovrebbero aggiornare il prima possibile.</p>
<p>Il rilascio include il supporto iniziale per la nuova cifratura end-to-end (proposta 144).
I lavori continuano su questo progetto e non è ancora pronto per l'utilizzo.
Ci sono modifiche alla pagina principale della console e ai riproduttori multimediali HTML5 integrati in i2psnark.
Sono incluse correzioni aggiuntive per le reti IPv6 dietro firewall.
Le correzioni riguardo la creazione dei tunnel dovrebbero risultare in una maggiore velocità di avvio per alcuni utenti.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="La versione 0.9.38 è disponibile" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P al 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="La versione 0.9.37 è disponibile" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="La versione 0.9.36 è disponibile" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="La versione 0.9.35 è disponibile" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="La versione 0.9.34 è disponibile" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
@ -78,8 +455,8 @@ There are preliminary fixes for Java 9, although we do not yet recommend Java 9
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="Vulnerabilità di sicurezza di I2P-Bote" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>Vulnerabilità di sicurezza di I2P-Bote</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="Vulnerabilità di sicurezza di I2P-Bote" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>Vulnerabilità di sicurezza di I2P-Bote</summary></details><p>I2P-Bote 0.4.5 corregge una vulnerabilità presente nelle versioni precedenti del
plugin I2P-Bote. La versione per Android era priva di questo bug.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled

View File

@ -0,0 +1,507 @@
<div>
<header title="I2P ニュース">ニュースフィードとルーターの更新</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 リリース" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 リリース</summary></details><p>2.8.2は、2.8.1のリリースで導入されてしまった、SHA256の不具合を原因とするバグを修正します。
このバグは主に、高帯域幅のルーターに影響します。</p>
<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 リリース" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 リリース</summary></details><p>2.8.1は、2.8.0の端末内にあるサイトへアクセスする際の欠陥を修正します。
我々はアプリケーションのメッセージを強調するため、コンソール内のいくつかのアプリケーションに、通知の泡を追加しました。
我々は、トンネルの信頼性に影響しうる、トンネル試験のバグを修正しました。
アドレス帳は今、購読から追加された最近のホスト名を表示する「最新」タブを備えます。
ダークテーマのいくつか修正と改善があります。</p>
<p>我々は、Java 21以上で以前に不調だったインストーラーを修正しました。
我々はまた、Linux上で空白を含むディレクトリーパスへのインストールを修正しました。
Dockerを使用する方々のためには、我々は古いDockerコンテナとコンテナのライブラリを更新しました。</p>
<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 リリース" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 リリース</summary></details><p>このリリースでは、バグ修正、不使用コードの削除、及びネットワーク安定性の改善によってI2Pを改善します。</p>
<p>我々は、ネットワーク内の混雑したルーターの扱いを改善しました。
UPnPとNATトラバーサルでの問題は、接続の改善とエラー報告によって対処されました。
ルーターのパフォーマンス改善と負担軽減のため、NetDBから不要なleasesetを除去する、更なる能動的な方策があります。
他の変更には、ルーターの再起動またはシャットダウン時などに、可観測性を減らす実装があります。</p>
<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 リリース" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 - HTTPの修正</summary></details><p>I2P 2.5.2では、2.5.0で発生した一部のHTTPコンテンツを切り詰めてしまうバグを修正しました。</p>
<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 リリース" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>サービス拒否攻撃に対処するI2Pリリース2.5.1をリリース</summary></details><p>I2P 2.5.1 は、I2Pネットワークとサービスに影響を及ぼすサービス拒否攻撃に対処するためにリリースされました。
このリリースでは、攻撃の効果と期間を増幅するために標的にされたSybil攻撃検知器のIPに基づく部分を無効化しました。
これにより、ネットワークは正常な動作に戻るはずです。
Sybil攻撃検知器を無効にしている人は、安全に再び有効にしてください。
また、ルーター情報の検証とピア選択を改善するために、他のサブシステムの調整も行われました。</p>
<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="荒天" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>ネットワーク天気: 荒天。I2Pは攻撃に曝されている。</summary></details><p>I2Pネットワークは現在、サービス拒否攻撃を受けています。
この攻撃はI2Pとi2pdに影響を与えますが、その方法は異なっており、ネットワークの健全性に深刻な影響を及ぼしています。
I2Pサイトの到達可能性はひどく低下しています。</p>
<p>I2P内でサービスをホスティングしており、それがFloodfillルーターでホスティングされている場合、到達可能性を改善するために、Floodfillを無効にしたルーターを追加してサービスの冗長性を高めることを検討すべきです。
その他の緩和策も検討されていますが、長期的で下位互換性のある解決策はまだ中で作業中です。</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="新リリース I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>アプリケーションの更なる改善、NetDB分離計画の調査</summary></details><p>このリリース、I2P 2.5.0は、NetDB分離計画の実装に焦点を当てた2.4.0のリリースよりも更に、利用者が触れる部分の改善を提供します。</p>
<p>I2PSnarkへ、トレント全体を検索する新機能が追加されました。
BiglyBTとqBittorrentのような他のI2Pトレントクライアントでバグが修正され、互換性が改善されます。
libtorrentとqBittorrentでI2Pのサポートの有効化と改善をするために作業した開発者全員に感謝します。
SusiMailもまた、新機能が追加され、電子メール内でマークダウン形式のためのサポートと、電子メール内へ添付をドラッグアンドドロップする機能が追加されました。
秘匿サービスマネージャーで作成されたトンネルは今、性能と、ウェブ技術との互換性を改善する「Keepalive」をサポートします。</p>
<p>このリリースを通じて我々はまた、怪しいメッセージを却下するルーターの機能を改善するためと、スパムへの回復力を改善するために、NetDBにいくつかの調整を行いました。
これは、2.4.0のリリースからの「Sub-DB分離」防御の実装「調査」への取り組みの一部です。
この研究は我々が修復した一つの小さな分離穿孔を扱いません。
この問題はI2Pチームによって発見され、内部で修復されました。</p>
<p>このリリースを通じて、AndroidとWindows用の我々の下流の配布にて、リリースの過程にいくつかの改善を行いました。
その結果、これらの下流の所産の配送と入手しやすさが改善されるはずです。</p>
<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:" title="新リリース I2P 2.3.0 - セキュリティ修正、微調整可能なブロック一覧、DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - セキュリティ修正、微調整可能なブロック一覧、DTG API</summary></details><p>このリリースにはCVE-2023-36325のための修正が含まれます。
CVE-2023-36325は、bloomフィルターに発生するコンテキスト混乱バグです。
攻撃者は、唯一無二のmessageIDを含むI2NPメッセージを作成し、そのmessageIDをクライアントに送信します。
そのメッセージは、bloomフィルターを通過した後、二回目のメッセージで再使用することができません。
攻撃者はその後、同じメッセージをルーターへ直接送信します。
ルーターはそのメッセージをbloomフィルターに渡し、削除します。
これによって、messageIDが以前に見たことがあるという情報が漏れてしまい、攻撃者は、ルーターがクライアントをホストしていると信じる強い根拠を与えてしまいます。
この問題は、bloomフィルターの機能を、メッセージがクライアントトンネルを通ったか、調査トンネルを通ったか、ルーターに直接送られたかに基づいて、異なるコンテキストに分離することで解決されました。
通常の状況下で、この攻撃は成功するまでに数日かかり、攻撃する段階の間にルーターが再起動したり、誤検知の影響を受けやすいなど、いくつかの要因によって混乱する可能性があります。
Java I2Pの利用者は、この攻撃を回避するために直ちに更新することを推奨します。</p>
<p>このコンテキスト混乱バグを修正する過程で、我々はこの種の漏洩に対して防御的なコードを書くために、いくつかの計略を改めました。
これには、netDb、転送量制限機構、floodfillルーターの動作に対する微調整が含まれます。</p>
<p>このリリースは、初期設定の第二のhosts提供者としてnot_bobを追加し、更に、コンソールホームページに<a href="http://notbob.i2p">notbob.i2p</a><a href="http://ramble.i2p">ramble.i2p</a>を追加しました。</p>
<p>このリリースには、微調整可能なブロック一覧も含まれています。
ブロック一覧は半永続的で、ブロックされたIPアドレスは通常、ルーターが再起動するまでブロックされます。
sybil攻撃中にブロック一覧の爆発的な増加を観測したユーザーは、ブロック一覧が一定間隔で項目を失効するように設定することで、より短いタイムアウトを選択することができます。
この機能は初期設定では無効になっており、現時点では高度な利用者にのみ推奨されます。</p>
<p>このリリースには、Desktop GUI(DTG)でプラグインを変更するためのAPIも含まれています。
システムトレイにメニュー項目を追加できるようになり、ネイティブアプリケーションインタフェースを使用するプラグインをより直感的に起動できるようになりました。</p>
<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="新リリース 2.2.1。Docker、Ubuntu Lunar、及びDebian Sid用のパッケージ化" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - 2.2.0用の保守リリース</summary></details><p>DDOS攻撃用の緩和策を短期で仕上げるため、前倒しにしたI2P 2.2.0リリースの後、いくつかの開発中の問題が判明し、新しいパッケージの構築とリリースが必要になりました。
このリリースでは、Ubuntu LunarおよびDebian Sidにおいて、jakartaパッケージの更新版を使用してルーターコンソールにアクセスできない問題を修正します。
Dockerパッケージでは引数を正しく読み込まず、その結果、構成ファイルにアクセスできないことがありました。
この問題も解決されています。
DockerコンテナはPodmanにも対応しました。</p>
<p>このリリースでは、transifexと翻訳を同期させ、GeoIPデータベースを更新します。</p>
<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="2.2.0 新リリース。DDOS攻撃への緩和策と、ストリーミングサブシステムへの微調整" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>DDOS攻撃への緩和策と、ストリーミングサブシステムへの微調整</summary></details><p>我々は2.2.0のリリース日を、2023年3月13日の本日に行い、前倒しにする方針を決定しました。
このリリースはDDOS攻撃を切り抜けるためのルーターの能力を改善するNetDb、Floodfill、及びピア選択の構成要素に渡る変更が含みます。
今後も攻撃は続くと思われますが、これらのシステムへの改善により、ルーターが悪意があると思われるルーターを特定し、優先順位を下げることで、DDOS攻撃の危険を軽減する助けになるでしょう。</p>
<p>このリリースでは、ストリーミングサブシステムに再生保護が追加され、暗号化パケットを捕らえられる攻撃者が、意図しない受信者にパケットを送信して再利用できるようになることを防ぎます。
これは後方互換性のある変更であるため、古いルーターでも新しいルーターのストリーミング機能を使用することが可能です。
この問題は、I2P開発チームが内部で発見し修正したもので、DDOS攻撃とは関係ありません。
また、現時点で再生したストリーミングパケットに遭遇したことはなく、I2Pネットワークに対してストリーミング再生攻撃が行われたことはないと考えています。</p>
<p>お気づきかもしれませんが、このリリースートとリリースそのものは、zzzではなくidkが署名しています。
zzzはプロジェクトから離れることを選択し、彼の使命はチームの他の一員によって担われています。
そのため、プロジェクトはネットワーク統計の基盤を交換し、開発フォーラムをi2pforum.i2pに移行する作業を行っています。
長い間、これらのサービスを提供してくれたzzzに感謝します。</p>
<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 リリース" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 非常に多いSSU2の修正</summary></details><p>我々は11月中にあった2.0.0のリリースから、幾つかの事を学びました。
ルーターがこのリリースに更新されたことで、ネットワークでは、私たちの新しいSSU2トランスポートプロトコルが、約1から60以上になりました。
まず、SSU2が堅牢であり、良き設計であり、安全なプロトコルであることを確認しました。
しかし、2つ目は、プロトコルの実装において、細かいバグや稀に発生するバグを多数発見し、修正したことです。
これらのバグの影響が累積して、ネットワークの性能が低下しています。</p>
<p>また、Bitcoinの新しいI2Pトランジェントアドレス機能によって引き起こされた可能性がある、
ネットワークにおけるトンネル数の増加や、トンネル構築の成功率の低下も確認されていますが、
私たちのSSU2バグと他の輻輳制御の問題によって悪化しています。
我々は、Bitcoinや他の非Bitcoinプロジェクトと協力して、I2Pネットワーク需要を減らしています。
私たちは、輻輳時のネットワーク負荷を軽減するために、アルゴリズムを改善しました。
また、i2pdと協力し、共通の輻輳制御戦略を開発しています。</p>
<p>そのため、今回のリリースは6週間ほど前倒しにして、皆様に修正をお届けすることにしました。
i2pdは先週、バージョン2.45.0をリリースしましたが、初期の成果は妙妙たるものです。
新しいプロトコルと分散型ネットワークは、開発するには困難です。
輻輳は、ほとんど前触れもなく、原因の手掛かりもわからないままやってくるものです。
診断の結果、問題が解決されればよいのですが、ご迷惑をおかけしました。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 リリース" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 トランスポート有効</summary></details><p>I2Pは小さな機能、試験及び非常に多いバグ修正の達成後に2.0.0をリリースし、全ユーザーに新しいUDPトランスポートのSSU2を有効にします。</p>
<p>我々はまた、インストーラー、ネットワークデータベース、非公開アドレス帳への追加、Windowsブラウザランチャー、及びIPv6 UPnPを含めた修正を成し遂げました。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="最近のブログ投稿" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>幾つかの最近のブログ投稿</summary></details><p>我々のウェブサイト上の幾つかの最近のブログ投稿へのリンク:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">新しいSSU2トランスポートの概観</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">I2P貨幣と他の詐欺についての警告</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">diva.exchangeからのKonradとの取材</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">StormyCloudからのDustinとの取材</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 リリース" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 試験用SSU2</summary></details><p>私たちはこの3ヶ月間、少数の有志の試験者とともに、
新しいUDPトランスポートプロトコル"SSU2"の開発に取り組んできました。
このリリースでは、中継とピア試験を含む実装を完了しました。
我々は、AndroidとARMの装置、および無作為に他のルーターのごく一部で、初期設定でこれを有効にしています。
これにより、今後3ヶ月でより多くの試験を行い、接続の移行機能を完成させ、残っている問題を修正することができます。
11月に予定されている次のリリースでは、全員がこの機能を利用できるようにする予定です。
手動での設定は必要ありません。</p>
<p>もちろん、このリリースには通常のバグ修正も含まれています。
また、自動停頓検出機能を追加し、すでに稀な停頓を発見し、現在では修正されています。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="新しいアウトプロキシ exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>新しいアウトプロキシ</summary></details><p>I2P"アウトプロキシ"出口ードは、HTTPプロキシトンネルを介してインターネットにアクセスする為に使われているかもしれません。
我々の<a href="http://i2p-projekt.i2p/en/meetings/314">毎月の会合</a>で公認され、今、<b>exit.stormycloud.i2p</b>は我々の公式推奨アウトプロキシであり、長期間不能な<b>false.i2p</b>を置き換えます。
更なる情報は<a href="http://stormycloud.i2p/">団体</a>StormyCloud、<a href="http://stormycloud.i2p/outproxy.html">アウトプロキシ</a><a href="http://stormycloud.i2p/tos.html">利用規約</a>上にあり、<a href="http://stormycloud.i2p/">StormyCloudウェブサイト</a>をご覧下さい。</p>
<p>我々は<a href="/i2ptunnel/edit?tunnel=0">秘匿サービスマネージャー設定</a>で、<b>アウトプロキシ</b><b>SSLアウトプロキシ</b>の二箇所に、<b>exit.stormycloud.i2p</b>を指定するよう提案します。
編集後、<b>下にスクロールして、保存をクリックしてください</b>
<a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">スクリーンショットは我々のブログ投稿</a>でご覧下さい。
Android用の説明とスクリーンショットは、<a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbobのブログ</a>をご覧下さい。</p>
<p>ルーターアップデートは設定をアップデートしませんので、手動でそれを変更する必要があります。
StormyCloudには、これらの支援について、感謝します。<a href="http://stormycloud.i2p/donate.html">寄付</a>をご検討下さい。</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 リリース" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 バグ修正</summary></details><p>このリリースはi2psnark、ルーター、I2CPとUPnPにバグ修正が含まれています。
ルーターはソフト再起動、IPv6、SSUピア検査、ネットワークデータベース保管とトンネル構築にてアドレスのバグを修正しました。
ルーターファミリー取り扱いとSybil区分は大幅に改善しています。</p>
<p>i2pdと共に、我々は新しいUDPトランスポートSSU2を開発中です。
SSU2はかなりのパフォーマンスとセキュリティの改善をもたらします。
また、これまで使っていた非常に低速なElGamal暗号をようやく置き換えることができ、約9年前に始めた暗号技術の全面的なアップグレードを完了することができるようになります。
このリリースには予備的な実装が含まれており、初期設定では無効になっています。
テストに参加したい方は、 zzz.i2p 上で最新の情報をご覧ください。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="極めて重要なJava/Jpackageのアップデートをインストール" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>最近のJavaの"Psychic Signatues"脆弱性は、I2Pに影響します。 Linux上のI2Pの現在のユーザ、またはバンドルされていないJVMを使用しているI2Pのユーザは、JVMをアップデートするか、または以下の、脆弱性を含まないバージョンに切り替える必要があります。
Java 15</p>
<p>新しいI2Pイージーインストールバンドルは、Java仮想マシンの最新リリースを使用して生成されました。詳細は、それぞれのバンドルニュースフィードで発表されています。</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 リリース" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 信頼性とパフォーマンスの改善</summary></details><p>1.7.0のリリースには、いくつかのパフォーマンスと信頼性の改善を含みます。</p>
<p>システムトレイにポップアップメッセージが、対応しているプラットフォームで表示されるようになりました。
i2psnarkに新しいトレントエディタが追加されました。
NTCP2トランスポートは、CPUの使用を大幅に削減しました。</p>
<p>長い間非推奨だったBOBインターフェースは、新規インストールでは削除されました。
Debianパッケージを除き、既存のインストールでは引き続き動作します。
BOBアプリケーションの残りのユーザは、SAMv3プロトコルに変換するよう開発者に依頼する必要があります。</p>
<p>我々は1.6.1リリース以降、ネットワークの信頼性が確実に低下していると存じています。
リリース後すぐにこの問題に気づきましたが、原因を突き止めるのに2ヶ月近くかかりました。
最終的にはi2pd 2.40.0のバグであることを突き止め、
このリリースとほぼ同時にリリースされる2.41.0で修正されます。
ネットワークデータベースの探索と保存の堅牢性を改善し、
トンネルピアの選択でパフォーマンスの低いピアを回避します。
これにより、バグや悪意のあるルーターが存在する場合でも、ネットワークはより堅牢になるはずです。
更に、プレリリースのi2pdとJava I2Pルータをテストする共同プログラムを開始します。
そうすることで、リリース後ではなく、リリース前に多くの問題を発見することができます。</p>
<p>その他、新しいUDPトランスポート"SSU2"提案159の設計を引き続き大きく進め、実装を開始しました。
SSU2は、パフォーマンスとセキュリティを大幅に改善させる予定です。
また、これまで使用してきた非常に低速なElGamal暗号を最終的に置き換えることができるようになり、
約9年前に始まった暗号技術の全面的なアップグレードが完了しました。
間もなくi2pdとの共同検査を開始し、今年後半にはネットワークに展開する予定です。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 リリース" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 新トンネルの構築メッセージを有効化</summary></details><p>今回のリリースでは、2021年に開発された2つのメジャーなプロトコルアップデートの展開が完了しました。
ルーターのX25519暗号化への移行が加速され、年内にほぼすべてのルーターが鍵交換される見込みです。
短いトンネル構築メッセージが有効になり、大幅な帯域幅の削減が可能になりました。</p>
<p>新規インストールウィザードにテーマ選択パネルを追加しました。
SSUのパフォーマンスを改善し、SSUのピアテストメッセージに関する問題を修正しました。
トンネル構築のBloomフィルターを調整し、メモリ使用量を削減しました。
Java以外のプラグインのサポートを強化しました。</p>
<p>その他のニュースとしては、新しいUDP transport SSU2の設計が順調に進んでおり、来年初めには実装を開始できる見込みです。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 リリース" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 新トンネルの構築メッセージ</summary></details><p>はい、そうです。9年間に渡って0.9.xをリリースしてきましたが、0.9.50から1.5.0に移行します。
これは、APIの大幅な変更を意味するものではなく、また、開発が完了したことを示すものでもありません。
これは、ユーザーの皆様に匿名性と安全を提供するための約20年間の努力が認められたことを意味しています。</p>
<p>このリリースでは、帯域幅を削減するためにトンネルの構築メッセージを小さくする実装が終了しました。
また、ネットワークルーターのX25519暗号化への移行も継続しています。
もちろん、多数のバグ修正やパフォーマンスの改善も行われています。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire デスクトップ脆弱性" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire デスクトップ脆弱性</summary></details><p>MuWireのスタンドアロンデスクトップアプリケーションにセキュリティ上の脆弱性が発見されました。
なお、コンソールのプラグインには影響がなく、先に告知されたプラグインの問題とは関係ありません。
MuWireのデスクトップアプリケーションを使用している場合は、直ちに<a href="http://muwire.i2p/">バージョン0.8.8にアップデートしてください</a></p>
<p>2021年7月15日に、
<a href="http://muwire.i2p/security.html">muwire.i2p</a>で問題の詳細が公開されます。</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire プラグイン脆弱性" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire プラグイン脆弱性</summary></details><p>MuWireプラグインにセキュリティ上の脆弱性が発見されました。
なお、スタンドアロンのデスクトップクライアントには影響ありません。
MuWireプラグインを使用している場合は、直ちに<a href="/configplugins">バージョン0.8.7-b1にアップデートしてください</a></p>
<p>脆弱性の詳細および最新のセキュリティ推奨事項に関する更新については
<a href="http://muwire.i2p/security.html">muwire.i2p</a>をご覧ください。</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 リリース" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 IPv6の修正</summary></details><p>0.9.50では、ルーターの暗号鍵をECIES-X25519に移行しました。
受動的なDNS詮索からユーザーを保護するため、再シードにDNS over HTTPSを有効にしました。
新しいUPnPのサポートを含む、IPv6アドレスに多数の修正と改善が行われています。</p>
<p>長年にわたり発生していたSusiMailの破損バグをようやく修正しました。
帯域幅制限の変更により、ネットワークトンネルのパフォーマンスが向上しました。
我々のDockerコンテナにいくつかの改善があります。
ネットワーク上の悪意のある、あるいはバグのあるルーターの可能性に対する防御機能を改善しました。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 リリース" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 SSUの修正と高速な暗号法</summary></details><p>0.9.49 では、I2P をより速く、より安全にするための作業を続けています。
SSU (UDP) トランスポートに関するいくつかの改善と修正により、より速い速度が得られるはずです。
このリリースでは、ルーター用の新しい高速なECIES-X25519暗号への移行も開始します。
(送信先では、数回前のリリースからこの暗号を使用しています。)
新しい暗号の仕様とプロトコルは数年前から取り組んできました。
そして、完成に近づいています!移行が完了するまでには、数回のリリースが必要です。</p>
<p>今回のリリースでは、混乱を最小限に抑えるため、新規インストールと既存のインストールのごく一部のみが新しい暗号化を使用します。
(再起動時にランダムに選択) は新しい暗号化を使用します。
ルーターが新しい暗号を使用するために「鍵交換」した場合、再起動後数日間は通常よりもトラフィックや信頼性が低下することがあります。
これは、 ルーターが新しいアイデンティティを生成したためで、正常な動作です。
しばらくすると、パフォーマンスが回復するはずです。</p>
<p>過去に2回、デフォルトの署名の種類を変更する際に、ネットワークを「鍵交換」したことがあります。
今回は初めてデフォルトの暗号化タイプを変更しました。
うまくいけばスムーズにいくのですが、念のためゆっくり始めています。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 リリース" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 パフォーマンス増強</summary></details><p>0.9.48では我々の新しいエンドツーエンド暗号プロトコル提案144が大部分のサービスでデフォルトで有効になっています。
トンネル構築メッセージの新しい暗号化提案152の予備的サポートも追加しました。
ルーターの至る所で著しいパフォーマンス改善があります。</p>
<p>Ubuntu Xenial (16.04 LTS) 用のパッケージはもはやサポートされません。
このプラットフォームのユーザがI2Pアップデートを受け取り続けるためにはアップグレードが必要です。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 リリース" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 新しい暗号を有効化</summary></details><p>0.9.47では我々の新しいエンドツーエンド暗号プロトコル提案144が一部のサービスでデフォルトで有効になっています。
Sybil攻撃の分析・ブロッキングツールはデフォルトで有効になりました。</p>
<p>Java 8以降が必要になりました。
Debian Wheezy・Stretch用とUbuntu Trusty・Precise用のパッケージはもはやサポートされません。
これらプラットフォームのユーザがI2Pアップデートを受け取り続けるためにはアップグレードが必要です。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 リリース" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 バグ修正</summary></details><p>0.9.46ではストリーミングライブラリの著しいパフォーマンス改善がなされました。
ECIES暗号提案144の開発を完了し、テスト向けに有効化オプションが付きました。</p>
<p>Windowsユーザのみ
このリリースでは、ローカルユーザによる不正利用の可能性があったローカル権限昇格の脆弱性を修正しました。
アップデートをなるべく早く適用してください。
Blaze Infosec による信頼性の高い問題点公表に感謝します。</p>
<p>これはJava 7、Debian Wheezy・Stretch、Ubuntu Precise・Trustyをサポートする最後のリリースです。
これらプラットフォームのユーザが以降のI2Pアップデートを受け取るにはアップグレードが必要です。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 リリース" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 バグ修正</summary></details><p>0.9.45では、秘匿モードと帯域幅テスターに対する重要な修正がありました。
コンソールのダークテーマに対する更新がありました。
パフォーマンス改善と新しいエンドツーエンド暗号提案144の開発を継続しました。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 リリース" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 バグ修正</summary></details><p>0.9.44では、秘匿サービスで新しい暗号タイプを扱う際の DoS攻撃の問題に対する重要な修正がありました。
全てのユーザはできるだけ早くアップデートしてください。</p>
<p>このリリースは新しいエンドツーエンド暗号提案144の初期サポートを含んでいます。
このプロジェクトは作業継続中で、まだ使用できる段階にはありません。
コンソールホームページと、I2PSnark の埋め込みHTML5メディアプレイヤーに変更がありました。
ファイアーウォール付IPv6ネットワークに対する追加の修正がありました。
トンネル構築の修正により一部ユーザでは起動が速くなるでしょう。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 リリース" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 バグ修正</summary></details><p>0.9.43のリリースでは、より強固なセキュリティ&プライバシー機能とパフォーマンス改善の作業を継続しています。
LeaseSet新仕様 (LS2) の実装は完了しました。
将来のリリースに向けて、より強固で高速なエンドツーエンド暗号提案144の実装を開始しています。
いくつかあったIPv6アドレス検出問題は修正され、もちろんそれ以外のバグ修正もいくらか行われました。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 リリース" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 バグ修正</summary></details><p>0.9.42では、I2Pの高速化と信頼性向上を継続しています。
UDP転送のスピードアップのための更新がいくらかあります。
よりモジュール化したパッケージングにする作業にこれから取りかかれるよう、設定ファイルを分割しました。
より高速で安全な暗号のための新案の実装を継続しています。
またもちろんたくさんのバグ修正が行われました。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 リリース" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 バグ修正</summary></details><p>0.9.41では、暗号化LeaseSet向けのクライアントごとの認証など、
提案123の新機能の実装を継続しています。
コンソールのI2Pロゴといくつかのアイコンが新しくなりました。
Linux用インストーラを更新しました。</p>
<p>Raspberry Piのようなプラットフォームでの起動が速くなりました。
低水準ネットワークメッセージに影響する重大なバグなど、いくつかの不具合を修正しました。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 リリース" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 新アイコン</summary></details><p>0.9.40 は新しい暗号化されたリースセット形式をサポートします。
古い NTCP 1 トランスポートプロトコルを無効にしました。
新しい SusiDNS のインポート機能と、新しいスクリプトによる着信接続のフィルタリングメカニズムがあります。</p>
<p>OSXネイティブインストーラに対して大幅な改善を行い、また IzPackインストーラも更新しました。
新アイコンによるコンソールの新調は継続しています。
またいつものように多くのバグを修正しました!</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 リリース" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 パフォーマンス改善</summary></details><p>0.9.39では、新型ネットワークデータベース提案123に対する広範な変更が行われました。
i2pコントロールプラグインをWebアプリとしてバンドルしました。RPCアプリケーションの開発をサポートするためのものです。
多数のパフォーマンス改善とバグ修正が行われました。</p>
<p>メンテナンス負荷を減らすため、ミッドナイトとクラシックの2つのテーマを削除しました。
以前からの当該テーマ利用者は、ダークもしくはライトのテーマを確認するとよいでしょう。
また、ホームページに新アイコンが入りました。これはコンソール更新の第一歩です。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 リリース" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 新しいセットアップウィザード</summary></details><p>0.9.38では、新規インストール用に帯域幅テスト付き新型ウィザードが含まれています。
最新の GeoIPデータベース形式のサポートを追加しました。
Firefoxプロファイルの新インストーラと、新しいMac OSXネイティブインストーラをWebサイトに置きました。
新しい「LS2」NetDB形式のサポート作業を継続しています。</p>
<p>またこのリリースでは大量のバグ修正が行われています。
SusiMailの添付ファイルに関するいくつかの問題や、IPv6限定ルーター用の修正です。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 出張報告" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>35C3でのI2P</summary></details><p>I2Pチームはライプツィヒの35C3でのほとんど全てに参加しました。
日ごとに会合が開かれ、昨年の振り返り、2019年の開発設計の目標の講義が行われました。</p>
<p>プロジェクトビジョンと新ロードマップは <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">こちら</a> で確認できます。</p>
<p>LS2、テストネット、Webサイトとコンソールの使い勝手改善は継続して行われます。
Tails、Debian、Ubuntu Discoに置く計画の準備が整っています。AndroidとI2P_Bote修正作業のための人員がまだ必要です。</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 リリース" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 NTCP2が有効化</summary></details><p>0.9.37では、NTCP2と呼ばれるさらに高速で安全な転送プロトコルが有効になりました。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 がリリースされました" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 では バグフィックスと共に NTCP2 をサポート</summary></details><p>0.9.36 は、より安全な新しいトランスポート・プロトコルである NTCP2 をサポートしています。
デフォルトでは無効になっていますが、<a href="/configadvanced">高度な設定</a><tt>i2np.ntcp2.enable=true</tt>を追加して再起動することで、有効にしてテストすることができます。
NTCP2 は次のリリースからデフォルトで有効になる予定です。</p>
<p>本リリースは、その他のパフォーマンス向上やバグフィックスも含んでいます。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 リリース" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 SusiMailフォルダとSSLウィザード</summary></details><p>0.9.35では、SusiMailのフォルダのサポートと、あなたの秘匿サービスサイトでHTTPSを設定するための新しいSSLウィザードを追加しました。
またいつものように多数のバグ修正 - 特にSusiMail関連 - を行いました。</p>
<p>0.9.36に向けていくつかの事柄に注力しました。
新しいOSXインストーラや、NTCP2と呼ばれるさらに高速で安全な転送プロトコルなどです。</p>
<p>I2Pは7月20-22日ニューヨークでのHOPEに参加します。お気軽にお声掛けください。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 リリース" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 バグ修正</summary></details><p>0.9.34では多くのバグ修正を行いました!
またSusiMail、IPv6ハンドリング、トンネルピア選択で改善を行いました。
UPnPのIGD2スキーマのサポートを追加しました。
また将来のリリースで登場する改良のための準備を行いました。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 リリース" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 バグ修正</summary></details><p>0.9.33では多数のバグ修正を行いました。例えばI2PSnark、I2PTunnel、streaming、SusiMailに関して。
リシードサイトに直接アクセスできない人のために、リシード用にいくつかのタイプのプロキシをサポートしました。
秘匿サービスマネージャーはデフォルトで速度制限を設定するようになりました。
高トラフィックサーバーを運用する人は、必要に応じてこの制限値を見直し、調整してください。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER、Meltdown、Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>ほぼ全システム上でセキュリティ問題を発見</summary></details><p>モバイル端末を含めほぼ全ての市販のコンピュータに搭載されている現代CPUについて極めて深刻な問題が見つかりました。これらセキュリティ問題は「Kaiser」「Meltdown」「Spectre」と呼ばれています。</p>
<p>KAISER/KPTI の白書は <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>、Meltdown は <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>、SPECTRE は <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a> にあります。インテル最初の返答は <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a> にまとめられています。</p>
<p>I2Pユーザは可能な限りシステムをアップデートすることが肝要です。Windows 10 のパッチが現在利用可能になり、Windows 7 と 8 もすぐに続くでしょう。MaxOS のパッチもすでに利用可能です。Linuxシステムの多くでも修正済の新カーネルが利用できます。Androidも同様で、2018年1月2日のセキュリティ修正にこの問題に対するパッチが含まれています。
できるだけ早くシステムをアップデートしてください。</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="新年おめでとうございます! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>新年 そして34C3でのI2P</summary></details><p>I2Pより皆様に新年のお慶びを申し上げます</p>
<p>7人ものI2Pチームメンバーが2017年12月27-30日ライプツィヒでの34C3に参加しました。我々のテーブルでの<a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">会議</a>のほか、至る所でI2Pのたくさんの友人と会いました。
会議の結果は <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> に既に投稿済みです。</p>
<p>また、たくさんのステッカーを配布したり、質問してくれた方全てに我々のプロジェクトの情報提供などしました。
我々I2Pの年1度の晩餐会は、全ての参加者に対しI2P継続的支援への感謝表現として大成功でした。</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 リリース" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 コンソールの更新</summary></details><p>0.9.32では、ルーターコンソールと関連Webアプリアドレス帳、I2PSnark、SusiMailで多数のバグ修正を行いました。
また、発行されたRouterInfo用の設定ホスト名の取り扱い方法を変更しました。DNSを介したネットワーク列挙攻撃を軽減するためです。
コンソールにDNSリバインディング攻撃防止のためチェックをいくつか追加しました。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 リリース" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 コンソールの更新</summary></details><p>今回のリリースの変更点はいつもよりずいぶん顕著です!
ルーターコンソールを新調し、理解をしやすく、使い勝手を改善、クロスブラウザサポート、そして全体的に整頓を行いました。
これはルーターコンソールをよりユーザーフレンドリーにする長期計画の第一歩です。
また I2PSnark に Torrent のレーティングとコメントのサポートを追加しました。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="翻訳者求む" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>来たる0.9.31のリリースは普段より未翻訳文章が多い</summary></details><p>0.9.31リリースの準備の際、これはUIの大幅なアップデートが含まれるのですが、
留意すべき未翻訳文書がいつもよりも多くなりました。
あなたが翻訳者なら、今リリースサイクルの間、翻訳を十分なものにするために、
いつもより多少時間を割いていただければ幸いです。
3週間作業に取り掛かれるよう、既に文書は提出済みです。</p>
<p>あなたがまだI2P翻訳者でないなら、参加するいい機会です
どうやって始めたらいいかについての情報は <a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">新規翻訳者向けガイド</a> を参照。</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 リリース" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 Jetty 9 へのアップデート</summary></details><p>0.9.30 には Jetty 9 と Tomcat 8 へのアップグレードが含まれます。
以前のバージョンはもはやサポートされないほか、来たる Debian Stretch、Ubuntu Zesty では利用できません。
ルーターは 設定ファイル jetty.xml を Jetty Webサイトそれぞれについて 新しい Jetty 9 設定に移行します。
これは直近・無修正の設定ならばうまくいくはずですが、修正版もしくは極めて古い設定では動かないかもしれません。
あなたのJetty Webサイトがアップグレード後でも動くことを確認してください。またサポートが必要な場合はIRCで我々に連絡してください。</p>
<p>一部のプラグインは Jetty 9 と互換性がなくアップデートが必要です。
以下のプラグインは 0.9.30 で動くよう更新されており、ルーターは再起動後にこれらをアップデートするでしょう: i2pbote 0.4.6、zzzot 0.15.0
以下のプラグイン(現バージョンを記載)は 0.9.30 では動かないでしょう。当該プラグイン開発者に新バージョンについての進捗を確認してください: BwSchedule 0.0.36、i2pcontrol 0.11</p>
<p>またこのリリースでは 古い2014年以前のDSA-SHA1秘匿サービスから より安全な EdDSA署名型への移行をサポートしています。
ガイドやFAQなどの詳しい情報は <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> を参照。</p>
<p>注: Raspberry Pi のような非Android ARMプラットフォームでは、ブロックファイルのデータベースが再起動でアップグレードされます。これは数分かかる場合があります。辛抱強くお待ちください。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 リリース" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 バグ修正</summary></details><p>0.9.29では、壊れた圧縮メッセージに対する迂回策など、多数のTracチケットに対する修正を行いました。
NTP over IPv6 をサポートしました。
予備の Dockerサポートを追加しました。
manページを翻訳しました。
同一オリジンのリファラヘッダをHTTPプロキシに通過させるようにしました。
Java 9向けに多くの修正を行いました。ただしまだ Java 9 の通常使用は推奨されていません。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote セキュリティ脆弱性" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote セキュリティ脆弱性</summary></details><p>I2P-Bote 0.4.5 では、以前の全ての版の I2P-Boteプラグインに存在するセキュリティ脆弱性を修正しました。
Androidアプリへの影響はありません。</p>
<p>メールをユーザに表示する際、大部分のフィールドはエスケープされていました。
しかし、添付ファイルのファイル名はエスケープされておらず、JavaScript有効のブラウザ上での悪意あるコード実行に使用される可能性がありました。
今ではエスケープされており、さらに Content Security Policy が全てのページに実装されています。</p>
<p>全I2P-Boteユーザは2月半ばにリリースされた I2P 0.9.29 以降、初回のルーター再起動で自動更新されるでしょう。
しかし移行期にI2P・I2P-Bote を使用するつもりならば、安全のために、<a href="http://bote.i2p/install/">インストールページの指示に従い</a>、手動でアップグレードすることを推奨します。</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 リリース" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 バグ修正</summary></details><p>0.9.28では、25以上のTracチケットに対する修正を行いました。また、Jettyなどバンドルされている多数のソフトウェアパッケージの更新を行いました。
前リリースで導入された IPv6ピアのテスト機能の修正を行いました。
悪意のありそうなピアを検出・ブロックするための改善を続けています。
Java 9向けの予備的修正を行いました。ただしまだ Java 9 の通常使用は推奨されていません。</p>
<p>I2P は 33C3 に参加します。ぜひ我々のテーブルに足を止めてネットワーク改善方法のアイデアをご提供ください。
会議では2017年のロードマップと優先順位を検討します。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote セキュリティ脆弱性" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote セキュリティ脆弱性</summary></details><p>I2P-Bote 0.4.4 では、以前の全ての版の I2P-Boteプラグインに存在するセキュリティ脆弱性を修正しました。
Androidアプリへの影響はありません。</p>
<p>CSRF保護の不足のため、ユーザがI2P-Bote起動中にJavaScript有効のブラウザ上で悪意のあるサイトを読み込むと、
敵対者がI2P-Bote上で当該ユーザとしてメッセージ送信などのアクションを発火できてしまっていました。
I2P-Boteアドレスの秘密鍵の抽出もできていた可能性がありますが、これについての実証は行われていません。</p>
<p>全I2P-Boteユーザは12月半ばにリリースされた I2P 0.9.28 以降、初回のルーター再起動で自動更新されるでしょう。
しかし移行期にI2P・I2P-Bote を使用するつもりならば、安全のために、<a href="http://bote.i2p/install/">インストールページの指示に従い</a>、手動でアップグレードすることを推奨します。
また、あなたが日ごろI2P-Bote起動中にJavaScript有効でサイトを閲覧している場合、新たな I2P-Boteアドレスの生成を検討すべきです。</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 リリース" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 バグ修正</summary></details><p>0.9.27では多数のバグ修正が行われました。
暗号加速のための 更新されたGMPライブラリ、これは 0.9.26 の新規インストール用とDebianビルドのみにバンドルされていましたが、0.9.27ではネットワーク内アップデートに含められました。
IPv6転送、SSUピアテスト、秘匿モードへの改善を行いました。</p>
<p><a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> のあいだ多数のプラグインの更新を行いました。それらはルーター再起動後に自動アップデートされるでしょう。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P の Stack Exchange が提案" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P が Stack Exchange の提案サイトに挙げられています!</summary></details><p>I2P が Stack Exchange の提案サイトに挙げられています!ベータフェーズが開始できるよう<a href="https://area51.stackexchange.com/proposals/99297/i2p">利用に努めて</a>ください。</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 リリース" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 暗号更新、Debianパッケージの改善、バグ修正</summary></details><p>0.9.26 では、組み込みの暗号ライブラリの大きなアップグレード、新しい署名付きアドレス帳購読プロトコル、Debian/Ubuntuパッケージの大幅な改善を行いました。</p>
<p>暗号について、GMP 6.0.0 をアップグレードし、新型プロセッサへのサポートを追加しました。
これにより暗号操作のかなりの速度向上が見込まれます。
また、サイドチャネル攻撃防止のため定数時間GMP関数を用いるようにしました。
用心のため、GMP変更は 新規インストール用とDebian/Ubuntuビルドのみで有効です。
0.9.27 のリリース時にネットワーク内アップデートに含められる予定です。</p>
<p>Debian/Ubuntuビルドについて、Jetty 8 や geoip など一部パッケージの依存関係を追加し、等価の同梱コードは削除しました。</p>
<p>また、たくさんのバグ修正が行われました。例えば、時間経過に伴い動作不安定とパフォーマンス劣化を起こすタイマーバグの修正など。
例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 リリース" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 SAM 3.3、QRコード、バグ修正</summary></details><p>0.9.25では メジャー新バージョンのSAM v3.3 が含まれ、洗練されたマルチプロトコルのアプリケーションをサポートしています。
秘匿サービスアドレス共有用のQRコードと、アドレスを視覚的に区別するための「identicon」画像を追加しました。</p>
<p>「ルーターファミリー」設定ページをコンソールに追加しました。あなたのルーターグループが1人の人間により運用されていることを簡単に示せます。
ネットワーク容量を増やし、うまくいけばトンネル構築が成功しやすくなるいくつかの変更が行われました。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 リリース" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 いくつかのバグ修正と速度向上</summary></details><p>0.9.24 では、新バージョンのSAMv3.2)の搭載、多数のバグ修正、効率改善を行いました。
このリリースは 初めて Java 7 を必要とすることに注意してください。
Java 7 または 8 にできるだけ早く更新してください。
Java 6 をお使いの場合、自動アップデートは行われません。</p>
<p>古めかしいcommons-loggingライブラリにより発生する問題を防ぐため、それを削除しました。
これにより、とても古い I2P-Boteプラグイン0.2.10以前。HungryHobo が署名は、IMAP が有効の場合クラッシュします。
推奨される修正は、古い I2P-Boteプラグインを 現在の str4d が署名しているものに替えることです。
詳細については <a href="http://bote.i2p/news/0.4.3">この投稿</a> を参照。</p>
<p>素晴らしい <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 会議</a> が開かれ、2016年のプロジェクト計画について良い進展を見せています。
Echelon は I2Pの歴史と現在状況についての講演を行いました。スライドは <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">こちら</a>pdf
Str4d は <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> に参加し、我々の暗号の移行について講演しました。スライドは <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">こちら</a>pdf</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 リリース" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 様々なバグ修正、I2PSnarkの細かな改善</summary></details><p>こんにちはI2P zzzがこれまで49のリリースに署名してきましたが、これは初めて私str4dが署名したリリースです。
これは人員を含めたあらゆる事柄に関する冗長性の重要なテストです。</p>
<p><b>保全作業</b></p>
<p>私の署名鍵は2年以上0.9.9以降)にわたってルーターアップデート内にあります。
ですから、最近のバージョンのI2Pを使用中なら、このアップデートは他の更新と変わらず簡単に済みます。
しかし、0.9.9よりも古いバージョンを動かしている場合、まず手動で最近のものにアップデートする必要があります。
最近のバージョン向けのアップデートファイルは <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">こちら</a> でダウンロードでき、手動でのアップデート方法の説明は <a href="http://i2p-projekt.i2p/en/download#update">こちら</a> で閲覧できます。
手動アップデートが終われば、ルーターが 0.9.23 のアップデートを通常通り探し出しダウンロードします。</p>
<p>パッケージマネージャ経由でI2Pをインストールしている場合はこの変更の影響を受けません。いつも通り更新できます。</p>
<p><b>更新詳細</b></p>
<p>ルーター情報を強固な新署名 Ed25519 に移行することはうまくいっており、少なくともネットワークの半分は鍵交換されたと既に見られています。
このリリースはその鍵交換過程を加速するものです。
ネットワークチャーンを減らすため、各々の再起動時でEd25519に変換する確率は少なくなります。
鍵交換の際、新しいアイデンティティでネットワークに再統合される何日かの間、使用帯域幅は少なくなるでしょう。</p>
<p>これが Java 6 をサポートする最後のリリースであることに注意してください。
Java 7 または 8 にできるだけ早く更新してください。
来たる Java 9 とI2Pを互換にすべく作業を既に行っており、一部の作業はこのリリースに含まれています。</p>
<p>また、I2PSnarkの細かな改善を行い、またルーターコンソールに過去のニュース項目閲覧のための新ページを追加しました。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22がリリースされました" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 バグ修正とEd25519への移行を開始</summary></details><p>0.9.22 では、I2PSnark が完了前に固まることに対する修正を行いました。また ルーター情報を強固な新署名 Ed25519 に移行し始めました。
ネットワークチャーンを減らすため、あなたのルーターが各々の再起動時でEd25519に変換する確率は少なくなります。
鍵交換の際、新しいアイデンティティでネットワークに再統合される何日かの間、使用帯域幅は少なくなるでしょう。
全てがうまくいけば、鍵交換過程を次回のリリースで加速できるでしょう。</p>
<p>I2PCon Toronto は大成功でした!
プレゼンテーションと動画の全ては <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PConページ</a> に一覧されています。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21がリリースされました" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 バグ修正とパフォーマンス向上</summary></details><p>0.9.21では、ネットワークに容量を追加し、フラッドフィルの効率を向上させるためのいくつかの変更が含まれています。
帯域幅をより効果的に使用するための変更が含まれています。
共有クライアントトンネルをECDSA署名に移行し、DSA フォールバックを追加しました。
ECDSA をサポートしないサイトのでは、新しい「マルチセッション」機能を使用してDSAフォールバックを使用します。</p>
<p>I2PCon Toronto 2015の登壇者と予定が告知されました。詳しくは <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PConページ</a> を参照。
<a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a> で席を予約してください。</p>
<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Torontoのスピーカーとスケジュールが告知されました" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015のスピーカーとスケジュールが告知されました</summary></details><p>I2PCon Toronto 2015の登壇者と予定が告知されました。詳しくは <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PConページ</a> を参照。
<a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a> で席を予約してください。</p>
</article>
</div>

View File

@ -1,31 +1,435 @@
<div>
<header title="I2P 뉴스">뉴스 및 라우터 업데이트 사항</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<header title="I2P 뉴스">뉴스 및 라우터 업데이트 사항</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39가 릴리즈 되었습니다." href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39에서 성능이 개선되었습니다</summary></details><p>0.9.39에서는 새로운 네트워크 데이터베이스 타입 (proposal 123)을 위한 대규모 변경을 포함합니다.
저희는 RPC 어플리케이션 개발을 지원하기 위해 i2pcontrol 플러그인을 웹 앱으로 포함했습니다.
많은 성능 개선과 버그 수정이 이루어졌습니다.</p>
<p>저희는 유지보수 부담을 줄이기 위해 미드나잇과 클래식 테마를 제거했습니다;
이전에 이 테마들을 사용하시던 유저분들은 다크 혹은 라이트 테마를 보시게 될 것입니다.
콘솔 업데이트의 첫 시작으로, 새로운 홈 페이지 아이콘들도 보시게 될 겁니다.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38가 릴리즈 되었습니다." href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38에서 새로운 시작 마법사를 포함합니다</summary></details><p>0.9.38에서는 대역폭 테스터가 있는 새로운 첫 설치 마법사를 포함합니다.
저희는 최신 버전의 GeoIP 데이터베이스 포맷 지원을 추가했습니다.
새로운 파이어폭스 프로파일 설치 프로그램과 네이티브 Mac OSX 설치 프로그램이 웹 사이트에 생겼습니다.
새 "LS2" netdb 포맷 지원을 위한 작업이 계속됩니다.</p>
<p>또한 이 릴리즈는 susimail 첨부파일에 관련된 여러 문제들과, IPv6 전용 라우터를 위한 수정 사항을 포함한 다양한 버그 수정을 포함합니다.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 여행 리포트" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>35C3으로 간 I2P</summary></details><p>I2P 팀은 Leipzig에서 열린 35C3에 대부분 참석했습니다.
일일 미팅을 통해 지난 해를 돌아보고 2019년의 디자인 목표와 개발을 다뤘습니다.</p>
<p>프로젝트 비전과 새 로드맵은 <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">여기</a>에서 검토하실 수 있습니다.</p>
<p>테스트넷인 LS2와 웹사이트와 콘솔에 대한 사용성 개선을 위한 작업이 계속됩니다.
계획은 Tails, Debian, Ubuntu Disco에 준비하는 것입니다.
저희는 아직 Android와 I2P_Bote 수정에 대해 작업할 분들이 필요합니다.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37이 릴리즈 되었습니다." href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37에서 NTCP2가 활성화되었습니다.</summary></details><p>0.9.37에서는 NTCP2라 불리는 더 빠르고, 더 안전한 전송 프로토콜이 활성화됩니다.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36이 릴리즈 되었습니다." href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36에서 NTCP2와 버그 수정이 이루어졌습니다.</summary></details><p>0.9.36은 NTCP2라 불리는 더 안전한 새로운 전송 프로토콜이 포함되었습니다.
기본값으로 비활성화되어있지만, 테스트를 위해 <a href="/configadvanced">고급 설정</a>에서 <tt>i2np.ntcp2.enable=true</tt>를 추가하고 재시작 해 활성화 할 수 있습니다.
NTCP2는 다음 릴리즈에서 활성화 될 것입니다.</p>
<p>이 릴리즈는 여러 성능 개선과 버그 수정을 포함합니다.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35가 릴리즈 되었습니다." href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35에서 SusiMail 폴더와 SSL 마법사 추가</summary></details><p>0.9.35에서 SusiMail 폴더 지원과 히든 서비스 웹사이트를 위한 HTTPS를 설정하는 SSL 마법사가 추가되었습니다.
또한 특히 SusiMail에서, 평소처럼 버그 수정을 했습니다.</p>
<p>저희는 0.9.36을 위해, NTCP2라 불리는 더 빠르고 안전한 전송 프로토콜과 새 OSX 설치 프로그램을 포함한 여러가지를 열심히 작업 중입니다.</p>
<p>I2P는 7월 20-22일에 New York City에서 열리는 HOPE에 있을 예정입니다. 저희를 찾아서 반가운 인사 남겨주세요!</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 릴리즈 됨." href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34는 버그 수정을 포함합니다.</summary></details><p>0.9.34는 엄청 많은 버그 수정을 포함합니다!
또한 SusiMail과 IPv6 처리, 터널 피어 선택에 관련해 개선이 이루어졌습니다.
UPnP의 IGD2 스키마 지원을 추가했습니다.
그리고 추후 릴리즈에서 보게 될 여러 개선사항을 위해 준비를 했습니다.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 릴리즈 됨." href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33은 버그 수정을 포함합니다.</summary></details><p>0.9.33은 i2psnark, i2ptunnel, 스트리밍, SusiMail을 포함한 많은 수의 버그 수정을 포함합니다.
재시딩된 사이트를 바로 접근하지 못하는 분들을 위해, 이제 재시딩을 위한 여러 종류의 프록시를 지원합니다.
히든 서비스 매니저는 이제 전송 제한을 기본으로 설정합니다.
높은 트래픽 서버들을 운영하는 경우, 검토 후에 필요에 맞게 다시 제한을 조절하시기 바랍니다.</p>
<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown 그리고 Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>보안 문제가 거의 모든 시스템에 발견되었습니다.</summary></details><p>모바일 폰들을 포함해서, 전 세계에 팔리고 있는 컴퓨터에 탑재된 현대 CPU들에서 매우 심각한 문제가 발견되었습니다. 이 보안 문제들은 "Kaiser", "Meltdown", "Spectre"로 명명되었습니다.</p>
<p>KAISER/KPTI에 관한 백서는 <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>에서, Meltdown은 <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, SPECTRE는 <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>에서 보실 수 있습니다. Intel의 첫 답변은 <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">인텔의 답변</a>에 있습니다.</p>
<p>업데이트가 가능한 한, I2P 유저분들이 시스템을 업데이트 하는것은 매우 중요합니다. Windows 10 패치는 현재 가능하며, Windows 7과 8은 곧 지원 될 것입니다. MacOS 패치는 이미 가능합니다. 많은 리눅스 시스템들도 수정이 포함된 새 커널들을 사용 가능합니다. Android도 적용되며, 2018년 1월 2일자 보안 업데이트에서 이 문제의 패치를 포함합니다.
가능한 한 빨리 시스템을 업데이트 하시기 바랍니다.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="새해 복 많이 받으세요! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>새해, 그리고 34C3에서 I2P가</summary></details><p>I2P 팀이 모든 분들에게 즐거운 신년을 기원합니다!</p>
<p>2017년 12월 17일부터 30일까지 Leipzig에서 열린 34C3에서 최소 7명의 I2P 팀 멤버들이 미팅했습니다. 저희 테이블에서 이루어진<a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">미팅</a>을 제외하고도 다양한 곳에 있는 I2P 친구분들을 만났습니다.
미팅 결과는 <a href="http://zzz.i2p" target="_blank">zzz.i2p</a>에 이미 포스팅되었습니다.</p>
<p>또한 저희는 많은 스티커를 전달해 드렸으며 프로젝트에 대해 물어보는 분들께 정보를 드렸습니다.
저희 연례 I2P 디너는 완전한 성공이였으며 계속되는 I2P 지원에 참여해주신 분들께 감사인사 드립니다.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32가 릴리즈 되었습니다" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 콘솔 업데이트 포함</summary></details><p>0.9.32는 라우터 콘솔 그리고 관련된 웹 앱 (주소록, i2psnark, susimail)의 수정을 포함합니다.
또한 DNS를 통한 몇몇 네트워크 열거 공격을 제거하기 위해, 게시된 라우터 정보를 위해 설정된 호스트 이름을 처리하는 방법을 변경했습니다.
리바인딩 공격에 저항하기 위해 콘솔에 몇몇 검사들을 추가했습니다.</p>

View File

@ -0,0 +1,597 @@
<div>
<header title="I2P-nyheter">Nyhetsstrøm og ruteroppdateringer</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 sluppet" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 med konsolloppdateringer</summary></details><p>Endringene i denne utgaven er lettere å legge merke til enn vanlig!
Vi har oppdatert ruterkonsollen for å gjøre den enklere å forstå, forbedret tilgjengelighet, støtte på tvers av nettlesere, og generell opprenskning.
Dette er første steg i en mer langsiktig plan for å gjøre ruterkonsollen mer brukervennlig.
Vi har også lagt til poenggivning for torrenter og kommentarstøtte i i2psnark.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Søken etter oversettere" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>Den forestående 0.9.31-utgaven har flere uoversatte strenger enn vanlig</summary></details><p>I forberedelsen for 0.9.31-utgaven, som bringer med seg betydelige oppdateringer i brukergrensesnittet, har vi en større ansamling enn vanlig av uoversatte strenger som trenger din oppmerksomhet. Hvis du er en oversetter, setter vi stor pris på om du kunne sette til side litt mer tid enn vanlig i denne utgivelsessyklusen for å få oversettelsen i skikk. Vi har dyttet strengene ut tidlig for å gi deg tre uker til å jobbe på dem.</p>
<p>IHvis du ikke er en I2P-oversetter enda, er dette rett tidspunkt å involvere seg på. Se
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">Guide for nye oversettere</a>
for informasjon om hvordan du kommer i gang.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 sluppet" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 oppdateres til Jetty 9</summary></details><p>0.9.30 inneholder en oppgradering til Jetty 9 og Tomcat 8.
De forrige utgavene støttes ikke lenger, og er ikke tilgjengelige i kommende Debian Stretch og Ubuntu Zesty.
Ruteren vil migrere jetty.xml-oppsettsfila for hver Jetty-nettside til det nye Jetty 9-oppsettet.
Dette bør virke for nylige, umodifiserte oppsett, men kan også virke for modifiserte og veldig gamle oppsett.
Bekreft at din Jetty-nettside fungerer etter å ha oppgradert, og kontakt oss på IRC hvis du har behov for hjelp.</p>
<p>Flere er ikke kompatible med Jetty 9 og må oppdateres.
Følgende programtillegg har blitt oppdatert for å virke med versjon 0.9.30, og din ruter burde oppdatere dem etter en omstart:
i2pbote 0.4.6; zzzot 0.15.0.
Følgende programtillegg (med gjeldende versjoner opplistet) vil ikke fungere med 0.9.30.
Kontakt den tilhørende programtilleggsutvikleren for status om nye versjoner:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>Denne utgaven inneholder migrasjon av gamle (2014 og tidligere) DSA-SHA-1 skjult tjeneste for til en sikrere EdDSA-signaturtype
Se <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for ytterligere informasjon, inkludert en guide og O-S-S.</p>
<p>Merk: På ikke-Android ARM-platformer som Raspberry Pi, vil blokkfildatabasen oppgraderes ved omstart, som kan ta flere minutter.
Ha tålmod.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 sluppet" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 inneholder feilrettinger</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 sluppet" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 inneholder feilrettinger</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
for this.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
which will speed up crypto operations considerably.
Also, we are now using constant-time GMP functions to prevent side-channel attacks.
For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
we will include them for in-net updates in the 0.9.27 release.</p>
<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
<p>There's a collection of bug fixes also, including a fix for a timer bug
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contains SAM 3.3, QR codes, and bug fixes</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
It adds QR codes for sharing hidden service addresses with others,
and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
to make it easier to declare that your group of routers is run by a single person.
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
Your router will not automatically update if you are using Java 6.</p>
<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration,
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
<p><b>Housekeeping</b></p>
<p>My signing key has been in router updates for over two years (since 0.9.9), so
if you are on a recent version of I2P this update should be just as easy as
every other update. However, if you are running an older version than 0.9.9, you
will first need to manually update to a recent version. Update files for recent
versions can be downloaded
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
and instructions on how to manually update are provided
<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
updated, your router will then find and download the 0.9.23 update as usual.</p>
<p>If you installed I2P via a package manager, you are not affected by the change,
and can update as usual.</p>
<p><b>Update details</b></p>
<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
with at least half of the network already estimated to have rekeyed. This
release accelerates the rekeying process. To reduce network churn, your router
will have a small probability of converting to Ed25519 at each restart. When it
does rekey, expect to see lower bandwidth usage for a couple of days as it
reintegrates into the network with its new identity.</p>
<p>Note that this will be the last release to support Java 6. Please update to
Java 7 or 8 as soon as possible. We are already working to make I2P compatible
with the upcoming Java 9, and some of that work is in this release.</p>
<p>We have also made some minor improvements in I2PSnark, and added a new page in
the routerconsole for viewing older news items.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
and use bandwidth more effectively.
We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
using the new "multisession" capability for those sites that don't support ECDSA.</p>
<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto speakers and schedule announced" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 speakers and schedule announced</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -1,5 +1,386 @@
<div>
<header title="I2P-nieuws">Nieuwsoverzicht en routerupdates</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
<header title="I2P-nieuws">Nieuwsoverzicht en routerupdates</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recente Blog berichten" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>

View File

@ -1,5 +1,245 @@
<div>
<header title="Wiadomości I2P">Kanał wiadomości i aktualizacji węzła</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="Wydano wersję 0.9.35" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>Wersja 0.9.35 zawiera katalogi SusiMaila i kreatora SSL</summary></details><p>Wersja 0.9.35 zawiera wsparcie dla folderów w SusiMailu i nowy kreator pozwalający skonfigurować HTTPS na Twojej ukrytej stronie w sieci I2P. Jak zwykle załatano kilkanaście błędów, zwłaszcza w SusiMailu.</p>
<header title="Wiadomości I2P">Kanał wiadomości i aktualizacji węzła</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="Wydano wersję 2.6.1" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1</summary></details><p>Wersja 2.6.1 została wydana w celu naprawy błędu interfejsu użytkownika panelu „Zarządzanie ukrytymi usługami”. Błąd ten uniemożliwiał przewijanie, przez co niektóre konfiguracje mogły być niedostępne.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Najnowsze posty na blogu" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="Wydano wersję 1.9.0" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>Wersja 1.9.0 wprowadza testy SSU2</summary></details><p>Spędziliśmy ostatnie trzy miesiące pracując nad nowym protokołem transportowym SSU2 z niewielką liczbą testerów. W tym wydaniu zakończyliśmy implementację, razem z testami przekaźników i uczestników. Domyślnie włączamy protokół SSU2 na Androidzie, platformach ARM i niewielkiej liczbie losowych węzłów. Pozwoli to na przeprowadzenie dalszych testów podczas nadchodzących trzech miesięcy, dopracowanie migracji i naprawę ewentualnych błędów. Planujemy włączenie protokołu SSU2 w następnej wersji zaplanowanej na listopad. Ręczna konfiguracja nie jest konieczna.</p>
<p>Oczywiście również naprawiliśmy sporo błędów. Oprócz tego dodano automatyczny wykrywacz zakleszczenia, którego wystąpienie jest dość rzadkie.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="Nowe proxy wyjściowe exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>Nowe proxy wyjściowe</summary></details><p>Proxy wyjściowe w sieci I2P umożliwiają dostęp do zwykłego internetu poprzez tunel HTTP. Na <a href="http://i2p-projekt.i2p/pl/meetings/314">comiesięcznym spotkaniu</a> postanowiono, że <b>exit.stormycloud.i2p</b> jest naszym nowym oficjalnym proxy wyjściowym, zastępującym martwy już serwer <b>false.i2p</b>. Więcej informacji o <a href="http://stormycloud.i2p/">organizacji</a> StormyCloud,
<a href="http://stormycloud.i2p/outproxy.html">proxy wyjściowym</a>,
i <a href="http://stormycloud.i2p/tos.html">warunkach korzystania</a>,
znajdziesz na <a href="http://stormycloud.i2p/">stronie internetowej StormyCloud</a> (w języku angielskim).</p>
<p>Aby dokonać zmiany proxy wyjściowego otwórz <a href="/i2ptunnel/edit?tunnel=0">Zarządzanie ukrytymi usługami</a> i wpisz <b>exit.stormycloud.i2p</b> w dwóch polach: <b>Serwery outproxy</b> i <b>Proxy wyjściowe SSL</b>. Po zmianie przewiń w dół i kliknij <b>Zapisz</b>. Zobacz <a href="http://i2p-projekt.i2p/pl/blog/post/2022/8/4/Enable-StormyCloud">zrzut ekranu na naszym blogu</a>. Instrukcje i zrzuty ekranu dla systemu Android znajdują się na <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">blogu użytkownika notbob</a>.</p>
<p>Aktualizacja węzła nie dokona zmiany konfiguracji proxy wyjściowego, musisz ręcznie dokonać zmian. Dziękujemy StormyCloud za ich wsparcie i prosimy rozważyć przekazanie im <a href="http://stormycloud.i2p/donate.html">darowizny</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="Wydano wersję 1.8.0" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>Wersja 1.8.0 zawiera poprawki błędów</summary></details><p>To wydanie zawiera poprawki błędów klienta i2psnark, węzła, I2CP i UPnP. Poprawki węzła naprawiają problemy z miękkim restartem, IPv6, SSU, testowaniem uczestników, zapisem bazy danych sieci i tworzeniem tuneli. Oprócz tego znacząco poprawiono obsługę rodziny węzłów i klasyfikację uczestników pod kątem ataku Sybil.</p>
<p>Razem z zespołem i2pd opracowujemy nowy transport UDP: SSU2. Ma on znacząco zwiększyć bezpieczeństwo i wydajność. Będzie to również ostatni etap zastąpienia bardzo powolnego szyfrowania ElGamal, co zakończy migrację kryptografii, którą rozpoczęliśmy około 9 lat temu. Wydanie to zawiera wstępną implementację SSU2, która jest domyślnie wyłączona. Jeżeli chcesz wziąć udział w testach, zajrzyj na forum zzz.i2p.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Zainstaluj niezbędne aktualizacje oprogramowania Java/Jpackage" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>Ostatnio odkryta w Javie podatność «Psychic Signatues» zagraża I2P. Obecni użytkownicy I2P na Linuksie lub korzystający z niedołączonej do I2P maszyny wirtualnej Javy (JVM) powinni dokonać aktualizacji JVM lub skorzystać z wersji niezawierającej tej podatności starszych niż Java 15.</p>
<p>Zostały wydane nowe łatwe w instalacji paczki I2P, które zawierają najnowsze wersje JVM. Więcej informacji w kanałach informacyjnych poszczególnych paczek.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="Wydano wersję 1.7.0" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>Wersja 1.7.0 podnosi wydajność i niezawodność</summary></details><p>Wersja 1.7.0 zawiera liczne poprawki zwiększające wydajność i niezawodność.</p>
<p>Dla obsługiwanych platform wprowadzono wyskakujące powiadomienia w zasobniku systemowym. Klient i2psnark zawiera nowy edytor torrentów. Znacząco zmniejszono wykorzystanie procesora przez transport NTCP2.</p>
<p>Już od dawna wycofywany mostek BOB został usunięty z nowych instalacji. Będzie dalej działał w obecnych instalacjach, za wyjątkiem tych zainstalowanych z paczek Debiana. Wszyscy pozostali użytkownicy mostka BOB powinni naciskać programistów na przejście używanych aplikacji na mostek SAMv3.</p>
<p>Jesteśmy świadomi powolnego spadku niezawodności sieci od czasu wydania wersji 1.6.1. Zauważyliśmy problem tuż po wydaniu, ale zajęło nam prawie dwa miesiące zidentyfikowanie przyczyn. Przyczyną był błąd w i2pd 2.40.0, który został załatany w wersji 2.41.0. W międzyczasie dokonaliśmy kilku zmian w Java I2P zwiększających niezawodność zapytań i zapisów do bazy danych węzłów, aby uniknąć tworzenia tuneli poprzez użytkowników o bardzo słabej wydajności. Powinno to zwiększyć odporność sieci na problematycznych i złośliwych użytkowników. Oprócz tego rozpoczęliśmy program testowania węzłów i2pd i Java w izolowanej sieci testowej, aby uniknąć problemów takich jak powyższy przed wydaniem kolejnej wersji, a nie po.</p>
<p>Kontynuujemy prace nad nowym transportem UDP „SSU2” (propozycja 159) i rozpoczęliśmy wdrażanie. SSU2 znacząco zwiększy bezpieczeństwo i wydajność. Ostatecznie całkowicie całkowicie zastąpiliśmy bardzo powolne szyfrowanie ElGamal, kończąc tym modernizację szyfrowania, która została rozpoczęta 9 lat temu. Już wkrótce rozpoczniemy wspólne testy z i2pd i wdrożymy zmiany do sieci jeszcze w tym roku.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="Wydano wersję 1.6.0" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>Wersja 1.6.0 uaktywnia nowe wiadomości tworzenia tuneli</summary></details><p>Niniejsze wydanie wprowadza dwie nowe poprawki protokołów opracowane w roku 2021. Przyspieszono migrację węzłów na szyfrowanie X25519, planujemy, że do końca roku prawie wszystkie węzły będą korzystały z nowych kluczy szyfrujących. Aktywowano krótkie wiadomości budowania tuneli, aby znacząco zmniejszyć wykorzystanie pasma.</p>
<p>Dodano wybór skórki konsoli podczas instalacji. Zwiększono wydajność protokołu SSU i naprawiono błąd związany z wiadomościami testowymi. Dopasowano filtr Blooma podczas tworzenia tuneli, co ma zmniejszyć wykorzystanie pamięci. Ulepszono wsparcie dla wtyczek nieopartych o Javę.</p>
<p>Oprócz tego poczyniliśmy postępy w opracowywaniu nowego protokołu transportowego przez UDP SSU2 i planujemy jego wprowadzenie na początku przyszłego roku.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="Wydano wersję 1.5.0" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>Wersja 1.5.0 wprowadza nowe wiadomości tworzenia tuneli</summary></details><p>Zgadza się (!) po 9 latach wydawania wersji 0.9.x przechodzimy prosto z wersji 0.9.50 na 1.5.0. Nie oznacza to jakieś znaczącej zmiany w API, ani też ukończenia prac nad I2P. Jest to po prostu sygnał tego, że od prawie 20 lat zapewniamy anonimowość i bezpieczeństwo naszym użytkownikom.</p>
<p>W tym wydaniu ukończono prace nad mniejszymi wiadomościami tworzenia tuneli, aby zmniejszyć wykorzystywaną przepustowość. Kontynuujemy migrację węzłów na szyfrowanie X25519. Jak zwykle poprawiono kilka błędów i poprawiono wydajność.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Podatność w aplikacji MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Podatność w aplikacji MuWire</summary></details><p>Znaleziono podatność bezpieczeństwa w samodzielnej aplikacji MuWire. Podatność nie występuje we wtyczce i nie jest związana z poprzednio ogłoszoną podatnością. Jeżeli korzystasz z aplikacji MuWire, zaleca się <a href="http://muwire.i2p/">natychmiastową aktualizację do wersji 0.8.8</a>.</p>
<p>Szczegóły tej podatności zostaną upublicznione na stronie <a href="http://muwire.i2p/security.html">muwire.i2p</a> 15 lipca 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Podatność we wtyczce MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Podatność we wtyczce MuWire</summary></details><p>Znaleziono podatność bezpieczeństwa we wtyczce MuWire. Podatność występuje tylko we wtyczce, nie w samodzielnej aplikacji. Jeżeli korzystasz z wtyczki MuWire, powinieneś jak najszybciej <a href="/configplugins">dokonać aktualizacji do wersji 0.8.7-b1</a>.</p>
<p>Zajrzyj na stronę <a href="http://muwire.i2p/security.html">muwire.i2p</a>, aby dowiedzieć się więcej o podatności i uaktualnionych zaleceń bezpieczeństwa.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="Wydano wersję 0.9.50" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>Wersja 0.9.50 z usprawnieniami IPv6</summary></details><p>Wersja 0.9.50 kontynuuje migrację kluczy szyfrujących węzłów na algorytm ECIES-X25519. Włączono DNS przez HTTPS dla operacji reseedowania, aby chronić użytkowników przed nasłuchem zapytań DNS. Wprowadzono szereg poprawek i ulepszeń dla adresów IPv6, wliczając wsparcie dla UPnP.</p>
<p>W końcu naprawiono występujące od dawna błędy w SusiMail. Zmiany w ograniczniku przepustowości powinny poprawić wydajność tuneli. Wprowadzono szereg poprawek w kontenerach Dockera. Usprawniliśmy ochronę przed potencjalnie złośliwymi i kłopotliwymi węzłami w sieci.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="Wydano wersję 0.9.49" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>Wersja 0.9.49: poprawki SSU i szybsza kryptografia</summary></details><p>W wersji 0.9.49 kontynuujemy prace nad polepszeniem szybkości i bezpieczeństwa sieci I2P. Wprowadzono szereg ulepszeń i poprawek dla transportu SSU (UDP), co powinno pozwolić osiągać większą szybkość działania. To wydanie rozpoczyna migrację na nowe, szybsze szyfrowanie ECIES-X25519 dla węzłów. (Szyfrowanie to jest już obecnie używane dla adresów celów.) Prace nad specyfikacjami i protokołami nowego szyfrowania prowadzimy od lat i zbliżamy się ku końcowi! Migracja potrwa przez kilka następnych wydań.</p>
<p>Aby nie spowodować chaosu, nowe szyfrowanie zostanie włączone tylko dla nowych instalacji i niewielkiego procenta obecnych instalacji (z pewnym prawdopodobieństwem podczas startu węzła). Jeżeli Twój węzeł dokona zmiany klucza na nowe szyfrowanie, przez kilka dni od restartu możesz doświadczyć niższego transferu i niezawodności. Jest to normalne, ponieważ Twój węzeł wygeneruje nową tożsamość. Wydajność powinna powrócić po pewnym czasie.</p>
<p>Zmiana kluczy nastąpiła w sieci I2P jeż dwa razy podczas zmiany domyślnego typu podpisu, ale po raz pierwszy zmieniamy domyślny typ szyfrowania. Miejmy nadzieję, że zmiana przebiegnie bezproblemowo, ale z ostrożności wprowadzamy ją pomału.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="Wydano wersję 0.9.48" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>Wersja 0.9.48 z poprawkami wydajności</summary></details><p>Wersja 0.9.48 wprowadza nowy protokół szyfrowania (propozycja 144) dla większości usług. Dodano wstępne wsparcie dla szyfrowania wiadomości tworzenia nowego tunelu (propozycja 152). Wprowadzono znaczne poprawki wydajności oprogramowania węzła.</p>
<p>Porzucono wsparcie dla paczek Ubuntu Xenial (16.04 LTS). Użytkownicy tego systemu powinni dokonać jego aktualizacji, aby móc dalej otrzymywać aktualizacje I2P.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="Wydano wersję 0.9.47" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>Wersja 0.9.47 aktywuje nowe szyfrowanie</summary></details><p>Wersja 0.9.47 domyślnie włącza nowy protokół szyfrowania end-to-end (propozycja 144) na niektórych usługach. Narzędzie do analizy i blokowania ataków Sybil jest teraz domyślnie włączone.</p>
<p>Wymagana jest wersja Javy w wersji 8 lub wyższej. Paczki dla Debiana w wersjach Wheezy i Stretch, oraz paczki dla Ubuntu w wersjach Trusty i Precise nie są już wspierane. Użytkownicy tych platform powinni dokonać aktualizacji systemu do nowej wersji, aby móc dalej otrzymywać aktualizacje I2P.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="Wydano wersję 0.9.46" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>Wersja 0.9.46 zawiera poprawki błędów</summary></details><p>Wersja 0.9.46 wprowadza znaczące poprawki wydajności w bibliotece strumieniowania. Zakończyliśmy prace nad szyfrowaniem ECIES (propozycja 144) i dodaliśmy możliwość testowego włączenia go.</p>
<p>Dla użytkowników Windowsa: to wydanie naprawia podatność związaną z eskalacją lokalnych uprawnień, która może zostać wykorzystana przez lokalnego użytkownika. Prosimy jak najszybciej przeprowadzić uaktualnienie. Składamy podziękowania dla Blaze Infosec za odpowiedzialne ujawnienie podatności.</p>
<p>Jest to ostatnie wydanie wspierające Javę 7, paczki Debiana Wheezy i Stretch, i paczki Ubuntu Precise i Trusty. Użytkownicy tych platform muszą dokonać uaktualnienia systemu, aby móc dalej otrzymywać aktualizacje I2P.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="Wydano wersję 0.9.45" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>Wersja 0.9.45 zawiera poprawki błędów</summary></details><p>Wersja 0.9.45 zawiera istotne poprawki dla trybu ukrytego i testera przepustowości. Poprawiono ciemną skórkę konsoli. Kontynuujemy prace zwiększające wydajności i opracowujemy nowe szyfrowanie end-to-end (propozycja 144).</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="Wydano wersję 0.9.44" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>Wersja 0.9.44 zawiera poprawki błędów</summary></details><p>Wersja 0.9.44 naprawia podatność na atak DoS ukrytej usługi obsługującej nowe rodzaje szyfrowania. Wszyscy użytkownicy powinni dokonać aktualizacji jak najszybciej.</p>
<p>To wydanie wstępnie wprowadza wsparcie dla nowego rodzaju szyfrowania (propozycja 144), trwają nad nim dalsze prace, nie jest jeszcze gotowy do użytku. Wprowadzono zmiany do strony głównej konsoli i zagnieżdżono odtwarzacz HTML5 do ip2snarka. Wprowadzono usprawnienia dla sieci IPv6 za zaporą. Poprawki startu tuneli powinny usprawnić start niektórym użytkownikom.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="Wydano wersję 0.9.43" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>Wersja 0.9.43 zawiera poprawki błędów</summary></details><p>W wersji 0.9.43 kontynuujemy prace zwiększające bezpieczeństwo, prywatność i wydajność. Zakończyliśmy wdrażanie nowej specyfikacji leasesetów (LS2). Rozpoczynamy wdrażanie mocniejszego i szybszego szyfrowania (propozycja 144). Naprawiono kilka problemów związanych z wykrywaniem adresów IPv6 i naprawiono kilka innych błędów.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="Wydano wersję 0.9.42" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>Wersja 0.9.42 zawiera poprawki błędów</summary></details><p>Wersja 0.9.42 sprawia, że sieć I2P pracuje szybciej i sprawniej. Zawiera znaczące zmiany przyspieszające transport po UDP. Rozdzieliliśmy pliki konfiguracyjne, aby w przyszłości uczynić program bardziej modularnym. Kontynuujemy prace nad propozycjami szybszego i bezpieczniejszego szyfrowania. Oczywiście naprawiliśmy sporo błędów.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="Wydano wersję 0.9.41" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>Wersja 0.9.41 zawiera poprawki błędów</summary></details><p>Są prowadzone dalsze prace w celu wdrożenia nowych funkcji z propozycji 123, takich jak uwierzytelnianie na klienta dla szyfrowanych leasesetów. W konsoli węzła pojawiło się nowe logo I2P i kilka nowych ikon. Zaktualizowano instalator na Linuksa.</p>
<p>Start na platformach takich jak Raspberry Pi powinien być szybszy. Naprawiono kilka błędów, m.in. dotyczące niskopoziomowych wiadomości sieci.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="Wydano wersję 0.9.40" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>Wersja 0.9.40 zawiera nowe ikony</summary></details><p>Wersja 0.9.40 przynosi wsparcie dla nowego formatu szyfrowanego LeaseSetu. Wyłączyliśmy stary protokół transportowy NTCP 1. Dodano możliwość importu w SusiDNS i nowy skryptowy mechanizm filtrujący dla połączeń przychodzących.</p>
<p>Dokonaliśmy mnóstwo ulepszeń we wrodzonym (native) instalatorze OSX oraz uaktualniliśmy instalator IzPack. Dalej odświeżamy wygląd konsoli dodaliśmy nowe ikony. Jak zwykle naprawiliśmy mnóstwo błędów!</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="Wydano wersję 0.9.39" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>Wersja 0.9.39 z poprawkami wydajności</summary></details><p>Wersja 0.9.39 zawiera znaczące zmiany nowych typów bazy danych sieci (propozycja 123). Wbudowaliśmy wtyczkę i2pcontrol jako webapp (aplikację internetową węzła), aby wspomóc rozwój aplikacji RPC. Oprócz tego poprawiono liczne błędy i poprawiono wydajność.</p>
<p>Usunęliśmy skórki „północ” i „klasyczną”, aby uprościć rozwój, użytkownicy tych skórek zobaczą teraz skórkę jasną bądź ciemną. Strona startowa konsoli zawiera nowe ikony, jest to pierwszy etap przebudowy konsoli.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="Wydano wersję 0.9.38" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>Wersja 0.9.38 zawiera nowy kreator instalacji</summary></details><p>Wersja 0.9.38 zawiera nowy kreator instalacji z testem przepustowości. Dodano wsparcie dla najnowszego formatu bazy danych GeoIP. Jest możliwość instalacji specjalnego profilu Firefoksa i nowy instalator na Mac OSX. Dalej pracujemy nad nowym formatem netdb „LS2”.</p>
<p>Ponadto to wydanie zawiera mnóstwo poprawek błędów, takich jak problem z załącznikami w susimailu i łatka dla węzłów działających tylko na IPv6.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="Raport z 35C3" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P na 35C3</summary></details><p>Zespół I2P prawie w całości przybył na 35C3 w Lipsku. Spotkaliśmy się, aby podsumować nasze prace w ubiegłym roku i wyznaczyć cele na rok 2019.</p>
<p>Wizja projektu i nowe plany na przyszłość znajdują się <a href="http://i2p-projekt.i2p/pl/get-involved/roadmap">tutaj</a>.</p>
<p>Będziemy pracować nad LS2, Testnetem, poprawkami użytkowania naszej strony i konsoli węzła. Chcemy, aby I2P znalazło się w systemach Tails, Debian i Ubuntu Disco. Potrzebujemy ludzi pracujących nad Androidem i I2P-Bote.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="Wersja 0.9.37 wydana" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>Wersja 0.9.37 włącza NTCP2</summary></details><p>Wersja 0.9.37 włącza nowy, bardziej bezpieczny protokół transportowy „NTCP2”.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="Wersja 0.9.36 wydana" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>Wersja 0.9.36 wprowadza NTCP2 i poprawia błędy</summary></details><p>Wersja 0.9.36 zawiera nowy, bezpieczny protokół transportowy NTCP2. Jest on domyślnie wyłączony, ale możesz go przetestować poprzez dopisanie <tt>i2np.ntcp2.enable=true</tt> do <a href="/configadvanced">zaawansowanej konfiguracji</a> i restart węzła. NTCP2 zostanie aktywowany w następnym wydaniu.</p>
<p>To wydanie zawiera także poprawki wydajnościowe i naprawia kilka błędów.</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="Wydano wersję 0.9.35" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>Wersja 0.9.35 zawiera katalogi SusiMaila i kreatora SSL</summary></details><p>Wersja 0.9.35 zawiera wsparcie dla folderów w SusiMailu i nowy kreator pozwalający skonfigurować HTTPS na Twojej ukrytej stronie w sieci I2P. Jak zwykle załatano kilkanaście błędów, zwłaszcza w SusiMailu.</p>
<p>Ciężko pracujemy nad kilkoma funkcjami w wersji 0.9.36, nad instalatorem dla OSX i szybszym i bardziej bezpiecznym transporcie NTCP2.</p>
<p>I2P będzie obecne w HOPE w Nowym Jorku, 20-22 lipca. Odwiedź nas i przywitaj!</p>
<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>

View File

@ -1,202 +1,523 @@
<div>
<header title="I2P - Notícias">Feed de notícias, e atualizações de roteador</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
it if you could set aside a little more time than usual during this release cycle
in order to bring the translations up to speed. We have pushed the strings early
to give you three weeks to work on them.</p>
<p>If you're not currently an I2P translator, now would be a great time to get
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 atualizações para Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
<p>Several plugins are not compatible with Jetty 9 and must be updated.
The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
<header title="I2P - Notícias">Feed de notícias, e atualizações de "router"</header><article id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a" title="Versão 2.9.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released" author="idk" published="2025-06-02T19:00:00Z" updated="2025-06-02T19:00:00Z"><details><summary>Versão 2.9.0 da I2P</summary></details><p>A versão 2.9.0 da I2P é uma versão de manutenção que inclui correções de bugs e trabalho em novas funcionalidades.</p>
<p>O uso de thread foi aprimorado para melhorar o desempenho do sistema i2ptunnel.
O NTCP2 foi aprimorado para resistir a ataques de probing.
O sistema de notificação foi integrado em mais aplicações para oferecer melhor feedback aos usuários do I2PSnark e das outras aplicações.
A participação automática em floodfill foi corrigida.
Os usuários podem observar uso de recursos mais elevado quando atuando como floodfill.
Se isso não é desejado, o modo floodfill pode ser desabilitado na página /config.</p>
<p>Uma nova funcionalidade de mapa global está disponível no console que mostra as localizações dos roteadores na sua visão do BD de rede.
Eles são os pares que ajudam o seu roteador a construir túneis e oferecer serviços anonimamente.</p>
<p>O trabalho continua em implementar gerenciamento de banda automático para túneis, o protocolo Datagram2 e criptografia pós-quântica.
Em dois lançamentos, na versão 2.11.0, a I2P irá requerer Java 17.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="Versão 2.8.2 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>Versão 2.8.2 da I2P</summary></details><p>A versão 2.8.2 corrige um bug que causa falhas de SHA256 que foi introduzido na versão 2.8.1.
O bug afetou principalmente roteadores de alta largura de banda.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="Versão 2.8.1 da I2P Lançada" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>Versão 2.8.1 da I2P</summary></details><p>A versão 2.8.1 conserta acessos a sites locais que estavam quebrados na 2.8.0.
Adicionamos bolhas de notificação em várias aplicações no painel para destacar mensagens da aplicação.
Corrigimos um bug de teste de túnel que pode ter estado afetando a estabilidade de túnel.
O catálogo de endereços agora possui uma nova aba "mais recente" que exibe os mais novos nomes de domínio adicionados de suas inscrições.
Há várias correções e melhorias para tema escuro.</p>
<p>Corrigimos o instalador que previamente falhava no Java 21 ou mais recente.
Também corrigimos instalar em caminhos de diretórios que contêm espaços em Linux.
Para aqueles de vocês que usam Docker, nós atualizamos bibliotecas e contêiner desatualizados do Docker.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Acesso a site local falha na 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>Bug de Acesso Local da 2.8.0</summary></details><p>Na 2.8.0, navegar para um site local (seja por nome de domínio ou b32) falhará.
A solução paliativa é usar localhost e a porta do servidor, geralmente 7658, para contornar a I2P.
Por exemplo, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
Pedimos desculpas pelo problema e estamos trabalhando em uma correção.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="Versão 2.8.0 da I2P" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>Versão 2.8.0 da I2P</summary></details><p>Esta versão melhora a I2P corrigindo bugs, removendo código inutilizado e melhorando a estabilidade de rede.</p>
<p>Aprimoramos o tratamento de roteadores congestionados na rede.
Problemas com UPnP e NAT traversal foram tratados para aprimorar a conectividade e o relatório de erros.
Nós agora temos uma estratégia mais agressiva para a remoção de leasesets do BD de rede para melhorar o desempenho do roteador e mitigar sobrecargas.
Outras mudanças foram implantadas para reduzir a observabilidade de eventos como um roteador reiniciando ou desligando.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="Lançamento I2P 2.7.0" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>Lançamento I2P 2.7.0</summary></details><p>Esta versão, I2P 2.7.0, continua nosso trabalho corrigindo bugs, melhorando o desempenho e adicionando recursos.</p>
<p>O acesso às informações do console e dos aplicativos foi aprimorado. Foram corrigidos problemas na pesquisa do I2PSnark e do SusiMail. A pesquisa netDB incorporada no console do roteador agora opera de maneira mais intuitiva e útil. Pequenas melhorias foram feitas nas telas de diagnóstico no modo avançado.</p>
<p>Bugs também foram corrigidos para melhorar a compatibilidade dentro da rede. Um problema com a publicação de leaseSets foi resolvido, o que melhora a confiabilidade dos principais serviços ocultos. O I2PSnark não altera mais o infohash quando um usuário altera apenas os rastreadores em um torrent existente. Isso evita que os torrents sejam desnecessariamente interrompidos por essas mudanças. Congratulamo-nos com esta contribuição de um novo colaborador. Um conflito no tratamento de uma opção de biblioteca de streaming foi resolvido para melhorar a compatibilidade com outras implementações I2P.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="Versão 2.6.1 do I2P lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>Versão 2.6.0 do I2P</summary></details><p>O I2P 2.6.1 é lançado para corrigir um erro na interface de utilizador da aplicação Gestor de serviços ocultos.
Este erro fazia com que o scrolling fosse desativado, tornando inacessível alguma configuração.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="Versão 2.6.0 do I2P lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>Versão 2.6.0 do I2P</summary></details><p>Esta versão, I2P 2.6.0, dá continuidade ao nosso trabalho de corrigir erros, adicionar funcionalidades, e aprimorar a confiabilidade da rede.</p>
<p>Os roteadores mais novos serão favorecidos na seleção de roteadores de floodfill.
O I2PSnark recebeu recursos que melhoram o desempenho do PeX (Peer Exchange), além de correções de erros.
Os protocolos de transporte legados estão a ser removidos, simplificando o código nos transportes UDP.
O destino hospedado localmente será acessível por clientes locais sem solicitar seu LeaseSet, melhorando o desempenho e a testabilidade.
Foram feitos ajustes adicionais às estratégias de seleção de pares.</p>
<p>O I2P não permite mais I2P-sobre-Tor, conexões de endereços IP de saída do Tor estão agora bloqueadas.
Desencorajamos isso porque degrada o desempenho do I2P e usa os recursos das saídas do Tor sem nenhum benefício.
Se for uma pessoa útil executando tanto uma saída Tor quanto o I2P, encorajamo-lo a continuar a fazer isso, usando endereços IP diferentes para cada um.
Roteadores que não sejam de saída e clientes Tor não são afetados por isso e não precisam mudar nada.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="Versão 2.5.2 do I2P lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 com correção de HTTP</summary></details><p>O I2P 2.5.2 foi lançado para corrigir um erro introduzido na versão 2.5.0 que causava o truncamento de alguns conteúdos HTTP.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="Versão 2.5.1 da I2P Lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>Versão 2.5.1 da I2P lançada para tratar dos Ataques de Negação de Serviço</summary></details><p>A I2P 2.5.1 é lançada para tratar dos Ataques de Negação de Serviço afetando a rede e os serviços I2P.
Com este lançamento nós desabilitamos as partes baseadas em IP da ferramenta de detecção de ataque Sybil que foram alvo para amplificar o efeito e a duração do ataque.
Isso deve ajudar a rede a retornar a operação normal.
Aqueles de vocês que desabilitaram a ferramenta de detecção de ataque Sybil podem reabilitá-la com segurança.
Ajustes a outros subsistemas para aprimorar a validação de RouterInfo e seleção de par também foram realizados.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Tempo tempestuoso" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Clima da rede: tempestuoso. O I2P está sob ataque.</summary></details><p>A rede I2P está atualmente sob um ataque de negação de serviço.
Este ataque afeta o I2P e o i2pd mas de formas diferentes e está a ter um efeito sério na saúde da rede.
A acessibilidade dos sítios I2P está seriamente degradada.</p>
<p>Se estiver a alojar um serviço dentro da I2P e este estiver alojado num roteador Floodfill, deve considerar o multihoming do serviço num roteador com Floodfill desativado para melhorar a acessibilidade.
Estão a ser discutidas outras medidas de mitigação, mas ainda se está a trabalhar numa solução a longo prazo e compatível com as versões anteriores.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="Nova versão I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>Mais melhorias na aplicação, revisão da estratégia de isolamento de BD de rede</summary></details><p>Esta versão, I2P 2.5.0, fornece mais melhorias visíveis ao usuário do que a versão 2.4.0, que foi focada na implementação da estratégia de isolamento do BD de rede.</p>
<p>Novas funcionalidades foram adicionadas ao I2PSnark, como a habilidade de pesquisar torrents.
Bugs foram resolvidos para melhorar a compatibilidade com outros clientes de torrents I2P como o BiglyBT e o qBittorrent.
Nós gostaríamos de agradecer a todos os desenvolvedores que trabalharam com a libtorrent e com o qBittorrent para proporcionar e melhorar seu suporte à I2P.
Novas funcionalidades também foram adicionadas ao SusiMail, incluindo suporte a formatação Markdown em emails e a habilidade de arrastar e soltar anexos nos emails.
Túneis criados com o gestor de Serviços Ocultos agora têm suporte a "Keepalive", o que melhora o desempenho e a compatibilidade com tecnologias web, permitindo sites I2P mais sofisticados.</p>
<p>Durante essa versão nós também fizemos vários ajustes no BD de rede para melhorar sua resiliência a spam e para melhorar a capacidade do roteador de rejeitar mensagens suspeitas.
Isso foi parte de um esforço para "revisar" a implementação de defesas de "Isolamento Sub-DB de rede" da versão 2.4.0.
Essa investigação descobriu um pequeno evento de perfuração do isolamento, o que qual nós consertamos.
Esse problema foi descoberto e resolvido internamente pelo time da I2P.</p>
<p>Durante essa versão várias melhorias foram feitas no processo de lançamento das nossas distribuições downstream para Android e Windows.
Isso deve resultar em uma melhor entrega e disponibilidade desses produtos downstream.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="Versão I2P 2.4.0 com melhorias de congestionamento e segurança do NetDB" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>Versão I2P 2.4.0 com melhorias de congestionamento e segurança do NetDB</summary></details><p>Esta versão, I2P 2.4.0, continua nosso esforço de melhorar a segurança e estabilidade da rede I2P.
Ela contém melhorias significativas ao BD de rede, uma estrutura essencial dentro da rede I2P usada para descobrir seus pares.</p>
<p>As mudanças no tratamento de congestão aperfeiçoarão a estabilidade da rede dando aos roteadores a possibilidade de aliviar pares congestionados evitando-os.
Isso ajudará a rede a limitar a efetividade de spam de túnel.
Isso também vai ajudar a rede a se regenerar durante e após ataques DDOS.</p>
<p>As mudanças do BD de rede também ajudam a proteger roteadores individuais e as aplicações que os utilizam.
Roteadores agora podem se defender conta atacantes separando o BD de rede em vários "Sub-BDs", os quais nós utilizamos para prevenir vazamentos de informação entre aplicações e o roteador.
Isso também aperfeiçoa a informação disponível aos roteadores Java sobre sua atividade de BD de rede e simplifica nosso suporte a aplicações multihoming.</p>
<p>Também estão incluídas uma série de correções de bugs e melhorias nos aplicativos I2PSnark e SusiMail.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:" title="Nova versão I2P 2.3.0 - Correções de segurança, listas de bloqueio ajustáveis, API DTG" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Correções de segurança, listas de bloqueio ajustáveis, API DTG</summary></details><p>Essa versão contém correções para o CVE-2023-36325.
O CVE-2023-36325 é um bug de confusão de contexto que ocorria no filtro de Bloom.
Um atacante cria uma mensagem I2NP contendo um messageID único, e envia esse messageID para um cliente.
A mensagem, após passar pelo filtro de Bloom, não é permitida ser reusada em uma segunda mensagem.
O atacante então envia a mesma mensagem diretamente para o roteador.
O roteador passa a mensagem para o filtro de Bloom, e é descartada.
Isso vaza a informação de que o messageID já foi visto antes, dando ao atacante um forte motivo para acreditar que o roteador está hospedando o cliente.
Isso foi corrigido separando a funcionalidade do filtro de Bloom em diferentes contextos com base em se uma mensagem chegou por um túnel de cliente, um túnel exploratório, ou foi enviada diretamente ao roteador.
Sob circunstâncias normais, esse ataque leva vários dias para ter sucesso e pode ser confundido por vários outros fatores, tais como roteadores reiniciarem durante a fase do ataque e sensibilidade a falsos positivos.
Recomenda-se que usuários da I2P Java atualizem a versão imediatamente para evitarem o ataque.</p>
<p>No curso da correção desse bug de confusão de contexto, nós revisamos algumas de nossas estratégias de desenvolver código defensivamente, contra esses tipos de vazamentos.
Isso inclui ajustes ao BD de rede, os mecanismos de limite de taxa, e o comportamento dos roteadores de floodfill.</p>
<p>Essa versão adiciona o not_bob como um segundo provedor de hosts padrão, e adiciona o <a href="http://notbob.i2p">notbob.i2p</a> e o <a href="http://ramble.i2p">ramble.i2p</a> à página inicial do console.</p>
<p>Essa versão também contém uma lista de bloqueio ajustável.
Bloquear pela lista de bloqueio é semi permanente. Cada endereço IP bloqueado normalmente fica bloqueado até que o roteador seja reiniciado.
Usuários que observarem crescimento explosivo da lista de bloqueio durante ataques Sybil podem optar por limites de tempo mais curtos configurando a lista de bloqueio para expirar entradas a um intervalo.
Essa funcionalidade é desabilitada por padrão e só é recomendada para usuários avançados neste momento.</p>
<p>Essa versão também inclui uma API para plugins modificarem com a GUI de Destkop (DTG).
Agora é possível adicionar itens de menu à área de notificação do sistema, permitindo a inicialização mais intuitiva de plugins que usam interfaces nativas de aplicação.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="Nova versão 2.2.1, correções de empacotamento para Docker, Ubuntu Lunar e Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - versão de manutenção para 2.2.0</summary></details><p>Após o lançamento da I2P versão 2.2.0, que foi empurrada para frente para acelerar mitigações aos ataques DDOS, nós descobrimos alguns problemas de desenvolvimento que tornaram necessário construir e lançar novos pacotes.
Essa versão corrige um problema no Ubuntu Lunar e no Debian Sid onde o console do roteador estava inacessível usando uma versão atualizada do pacote jakarta.
Os pacotes Docker não estavam lendo argumentos corretamente, resultando em arquivos de configuração inacessíveis.
Esse problema também foi resolvido.
O contêiner docker é agora também compatível com o Podman.</p>
<p>Esta versão sincroniza traduções com transifex e atualiza o banco de dados GeoIP.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="Nova versão 2.2.0, Mitigações para ataques DDOS e ajustes no subsistema Streaming" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Atenuações para ataques DDOS e ajustes no subsistema Streaming</summary></details><p>Optamos por antecipar a data de lançamento da versão 2.2.0, que ocorrerá hoje, 13 de março de 2023. Esta versão inclui alterações nos componentes NetDB, Floodfill e Peer-Selection que melhoram a capacidade do roteador de sobreviver a ataques DDOS. É provável que os ataques continuem, mas as melhorias nesses sistemas ajudarão a mitigar o risco de ataques DDOS, ajudando o roteador a identificar e despriorizar roteadores que parecem maliciosos.</p>
<p>Essa versão também adiciona proteção contra repetição ao subsistema de Streaming, o que evita que um atacante que consiga capturar um pacote criptografado possa reusá-lo enviando-o para destinatários indesejados.
Essa é uma mudança retrocompatível, então roteadores mais antigos continuarão sendo capazes de usar as capacidades de streaming de roteadores mais novos.
Esse problema foi descoberto e resolvido internamente, pelo time de desenvolvimento da I2P, e não está relacionado aos ataques DDOS.
Nós nunca encontramos um pacote de streaming repetido e não acreditamos que um ataque de repetição de streaming tenha algum dia acontecido contra a rede I2P neste momento.</p>
<p>Como você pode ter notado, estas notas de lançamento e o lançamento da versão em si foram assinados pelo idk, e não pelo zzz.
O zzz decidiu deixar o projeto e suas responsabilidades estão sendo apropriadas por outros membros do time.
Como tal, o projeto está trabalhando em substituir a infraestrutura de estatísticas de rede e mover o fórum de desenvolvimento para i2pforum.i2p.
Nós agradecemos o zzz por fornecer esses serviços por tanto tempo.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="Atualização de DDoS" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>Atualização de DDoS</summary></details><p>Nós confirmamos que o atacante controla um grande número de roteadores.
Nossas investigações e mitigações continuam.</p>
<p>Esse é um bom momento para lembrar as pessoas de que mesmo após 20 anos, a rede I2P é relativamente pequena.
Nós não temos indícios de que o atacante está tentando desanonimizar algum usuário ou serviço oculto em particular.
Todavia, se seu modelo de risco é de alto risco, você deve considerar cuidadosamente se a I2P atualmente oferece a proteção que você requer.
A melhor solução a longo prazo é divulgar e a fazer crescer a rede I2P para aumentar a segurança de nossos usuários.</p>
<p>Nós providenciaremos informações adicionais aqui no feed de notícias e em <a href="http://zzz.i2p">zzz.i2p</a> conforme necessário.
Nós pedimos a sua paciência enquanto trabalhamos para melhorar a I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="Sobre os recentes ataques de Negação de Serviço" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>A I2P continua intacta com desempenho prejudicado</summary></details><p>A rede I2P está atualmente sendo afetada por um ataque de Negação de Serviço.
A função de floodfill da rede foi afetada, resultando em respostas sendo prejudicadas e taxas de sucesso de construção de túnel caindo.
Participantes na rede têm sofrido dificuldades ao conectar a sites I2P e ao usar serviços I2P.
Estratégias de mitigação estão sendo investigadas e implementadas gradualmente.</p>
<p>Embora o ataque tenha degradado o desempenho, a rede segue intacta e usável.
Roteadores I2P Java parecem estar lidando com esses problemas melhor do que os roteadores i2pd por agora.
Várias mitigações devem começar a aparecer nas construções de desenvolvimento tanto dos roteadores Java quanto dos roteadores C++ na próxima semana.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="Versão 2.1.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 com diversas correções de SSU2</summary></details><p>Nós descobrimos várias coisas desde a nossa versão 2.0.0 em novembro.
Conforme os roteadores atualizaram para essa versão, a rede foi de em torno de 1% para mais de 60% de suporte para nosso novo protocolo de transporte SSU2.
Em primeiro lugar, nós confirmamos que o SSU2 é um protocolo seguro, bem projetado, e sólido.
Em segundo lugar, contudo, nós encontramos e corrigimos diversos bugs pequenos ou de baixa ocorrência na implementação do protocolo.
Cumulativamente, os efeitos desses bugs reduziram o desempenho da rede.</p>
<p>Ainda, nós estamos a par do maior número de túneis e da menor taxa de sucesso de construção de túneis na rede,
possivelmente causados pela nova funcionalidade do Bitcoin de endereço transiente da I2P,
mas tornados piores pelos nossos bugs do SSU2 e outros problemas de controle de congestão.
Nós estamos trabalhando com o Bitcoin e com outros projetos não Bitcoin para reduzir as demandas de rede da I2P.
Nós aperfeiçoamos nossos algoritmos para reduzir a carga sobre a rede durante momentos de congestão.
Nós também estamos colaborando com a i2pd para desenvolver estratégias em comum de controle de congestão.</p>
<p>Portanto, nós aceleramos esse lançamento em cerca de seis semanas, para levar as correções para todo mundo.
A i2pd lançou sua versão 2.45.0 na semana passada e os resultados iniciais são encorajadores.
Novos protocolos, e redes distribuídas, são difíceis de desenvolver.
A congestão pode chegar com pouco aviso e com pouco indício de causa.
Obrigado por sua paciência enquanto nós diagnosticávamos e, assim se espera, resolvíamos os problemas.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="Versão 2.0.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>Transporte SSU2 Habilitado</summary></details><p>A I2P versão 2.0.0 habilita nosso novo transporte UDP SSU2 para todos os usuários, após o término de pequenas funcionalidades, testes, e diversas correções de bugs.</p>
<p>Nós também temos correções por todo o lugar, incluindo instalador, base de dados de rede, adição ao livro de endereços privado, inicializador de navegador do Windows, e UPnP IPV6.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Publicações recentes no blogue" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Alguns posts recentes do blog</summary></details><p>Aqui estão links para diversas publicações recentes no nosso website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Visão geral do nosso novo transporte SSU2</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">Um aviso sobre moedas I2P e outros golpes</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">Uma entrevista com o Konrad do diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">Uma entrevista com o Dustin da StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="Versão 1.9.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 com SSU2 para testes</summary></details><p>Nós passamos os últimos três meses trabalhando em nosso novo protocolo de transporte UDP "SSU2"
com um pequeno número de testadores voluntários.
Essa versão completa a implementação, incluindo testes de par e de transmissor.
Nós estamos o habilitando por padrão para as plataformas Android e ARM, e para uma pequena porcentagem de outros roteadores aleatoriamente.
Isso nos permitirá fazer muito mais testes nos próximos três meses, terminar a funcionalidade de migração de conexão,
e consertar quaisquer problemas restantes.
Nós planejamos habilitá-lo para todo mundo no próximo lançamento agendado para novembro.
Nenhuma configuração manual é necessária.</p>
<p>Claro, há a coleção usual de correções de bugs nesta versão também. Também adicionamos um detector automático de deadlock que já encontrou um raro deadlock que agora está corrigido.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="Novo Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>Novo Outproxy</summary></details><p>"Proxies de saída" (nodos de saída) da I2P podem ser usados para acessar a internet através
do seu túnel de proxy HTTP.
Conforme aprovado em nossa <a href="http://i2p-projekt.i2p/en/meetings/314">reunião mensal</a>,
<b>exit.stormycloud.i2p</b> é agora nosso proxy de saída recomendado e oficial, substituindo o há muito morto <b>false.i2p</b>.
Para mais informações sobre a <a href="http://stormycloud.i2p/">organização</a>,
o <a href="http://stormycloud.i2p/outproxy.html">proxy de saída</a>,
e os <a href="http://stormycloud.i2p/tos.html">termos de serviço</a> da StormyCloud,
veja o <a href="http://stormycloud.i2p/">website da StormyCloud</a>.</p>
<p>Nós sugerimos que você modifique a sua <a href="/i2ptunnel/edit?tunnel=0">configuração do Gerenciador de Serviços Ocultos</a>
para especificar <b>exit.stormycloud.i2p</b>
em dois lugares: <b>Proxies de Saída</b> e <b>Proxies de Saída SSL</b>.
Após editar, <b>role para baixo e clique em Salvar</b>.
Veja nossa <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">publicação no blog para uma captura de tela</a>.
Para instruções para o Android e capturas de tela, veja o <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">blog do notbob</a>.</p>
<p>As atualizações do roteador não atualizarão sua configuração, você deve editá-la manualmente. Obrigado a StormyCloud por seu apoio, e por favor, considere um <a href="http://stormycloud.i2p/donate.html">doação</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 com correções de bugs</summary></details><p>Essa versão inclui correções de bugs no i2psnark,
no roteador, I2CP, e UPnP.
As correções no roteador tratam bugs no reinício suave, IPv6, testes de par SSU,
armazenamento do banco de dados de rede, e construção de túnel.
O tratamento de família de roteador e classificação de Sybil também foram
melhorados significativamente.</p>
<p>Junto da i2pd, nós estamos desenvolvendo nosso novo transporte UDP, o SSU2.
O SSU2 trará melhoras substanciais de desempenho e segurança.
Ele também permitirá que nós finalmente substituamos nosso último uso da criptografia muito lenta ElGamal,
completando a atualização completa de criptografia que nós iniciamos cerca de 9 anos atrás.
Essa versão contém uma implementação preliminar que fica desabilitada por padrão.
Se você deseja participar em testes, por favor, busque informações atuais
em zzz.i2p.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Instalar atualizações essenciais do Java/Jpackage" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>A recente vulnerabilidade Java de "Assinaturas Psíquicas" afeta a I2P. Usuários atuais da
I2P no Linux, ou quaisquer usuários da I2P que estiverem usando uma JVM que não veio junto no pacote devem atualizar
sua JVM ou mudar para uma versão que não contém a vulnerabilidade, abaixo
do Java 15.</p>
<p>Novos pacotes I2P Easy-Install foram gerados usando a versão mais recente doJava Virtual Machine. Mais detalhes foram publicados nos respectivosfeeds de notícias do pacote.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 com melhorias de confiabilidade e desempenho</summary></details><p>A versão 1.7.0 contém várias melhorias de desempenho e confiabilidade.</p>
<p>Agora há mensagens pop-up na bandeja do sistema, para as plataformas que o suportam. i2psnark tem um novo editor de torrent. O transporte NTCP2 agora usa muito menos CPU.</p>
<p>A há muito obsoleta interface BOB está removida para novas instalações.
Ela continuará funcionando em instalações existentes, exceto em pacotes Debian.
Quaisquer usuários de aplicações BOB que ainda restarem devem pedir aos desenvolvedores que as convertam para o protocolo SAMv3.</p>
<p>Nós sabemos que desde a nossa versão 1.6.1, a estabilidade da rede tem deteriorado continuamente.
Nós ficamos a par do problema logo após o lançamento, mas levou quase dois meses para nós encontrarmos a causa.
Nós eventualmente a identificamos como um bug na i2pd 2.40.0,
e a correção será na sua versão 2.41.0, que será lançada mais ou menos na mesma data que esta versão.
Ao longo do caminho, nós fizemos várias mudanças do lado da I2P Java para melhorar a
robustez dos armazenamentos e buscas na base de dados de rede, e evitar pares com desempenho ruim na seleção de par de túnel.
Isso deve ajudar a rede a ficar mais robusta mesmo com a presença de roteadores problemáticos ou maliciosos.
Ainda, nós estamos iniciando um programa conjunto para testar os roteadores I2P Java e i2pd pré-lançamento
juntos em uma rede para testes isolada, para que possamos encontrar mais problemas antes dos lançamentos, não depois.</p>
<p>Em outras novidades, nós continuamos a fazer bastante progresso no projeto do nosso novo transporte UDP "SSU2" (proposta 159)
e começamos a implementação.
O SSU2 trará melhoras substanciais de desempenho e segurança.
Ele também permitirá que nós finalmente substituamos nosso último uso da criptografia muito lenta ElGamal,
completando uma atualização completa de criptografia que começou cerca de 9 anos atrás.
Nós esperamos iniciar a testar em conjunto com a i2pd logo, e disponibilizá-lo para a rede mais tarde neste ano.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 permite novas mensagens de construção do túnel</summary></details><p>Este lançamento completa a implementação de duas grandes atualizações do protocolo desenvolvidas em 2021.
A transição para a criptografia X25519 para roteadores é acelerada, e esperamos que quase todos os roteadores sejam chaveados novamente até o final do ano.
As mensagens de construção dos túneis curtos são habilitadas para uma redução significativa da largura de banda.</p>
<p>Adicionamos um painel de seleção de temas ao novo assistente de instalação.
Melhoramos o desempenho da SSU e corrigimos um problema com as mensagens de teste dos pares da SSU.
O filtro Bloom construído no túnel foi ajustado para reduzir o uso de memória.
Melhoramos o suporte para plugins não-Java.</p>
<p>Em outras palavras, estamos fazendo excelentes progressos no projeto de nosso novo SSU2 de transporte UDP e esperamos começar a implementação no início do próximo ano.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 com novas mensagens de construção do túnel</summary></details><p>Sim, é isso mesmo, após nove anos de versões 0.9.x, nós estamos indo direto de 0.9.50 para 1.5.0.
Isso não simboliza uma grande mudança de API, ou uma declaração de que o desenvolvimento agora está completo.
É simplesmente um reconhecimento dos quase 20 anos de trabalho para proporcionar anonimato e segurança para nossos usuários.</p>
<p>Essa versão finaliza a implementação de mensagens de criação de túnel menores para reduzir largura de banda.
Nós continuamos a transição dos roteadores da rede para a criptografia X25519.
Claro que há também diversas correções de bugs e melhorias de desempenho.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Vulnerabilidade de desktop MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>Uma vulnerabilidade de segurança foi descoberta na versão autônoma da aplicação de desktop do MuWire.
Ela não afeta o plugin do console, e não está relacionada com o problema no plugin anunciado previamente.
Se você executa a aplicação para desktop do MuWire, você deve <a href="http://muwire.i2p/">atualizar para a versão 0.8.8</a> imediatamente.</p>
<p>Os detalhes da edição serão publicados em <a href="http://muwire.i2p/security.html">muwire.i2p</a>
em 15 de julho de 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Vulnerabilidade de plug-in MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Vulnerabilidade de plug-in Muwire</summary></details><p>Foi detetada uma vulnerabilidade de segurança no plugin MuWire. Ele não afeta o cliente de desktop autônomo. Se você estiver executando o plugin MuWire, você deve <a href="/configplugins">Atualização para a versão 0.8.7-B1</a> imediatamente.</p>
<p>Ver <a href="http://muwire.i2p/security.html">muwire.i2p</a>
para obter mais informações sobre a vulnerabilidade e recomendações de segurança atualizadas.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 com correções do IPv6</summary></details><p>A versão 0.9.50 dá continuidade à transição ao ECIES-X25519 para chaves de criptografia dos roteadores.
Nós habilitamos DNS sobre HTTPS para repropagação para proteger usuários contra snooping passivo de DNS.
Há diversas correções e melhorias para endereços IPv6, incluindo o novo suporte aUPnP.</p>
<p>Nós finalmente corrigimos alguns antigos bugs de corrupção no SusiMail.
Mudanças no limitador de banda devem melhorar o desempenho de túnel da rede.
Há várias melhorias no nossos contêiners Docker.
Nós melhoramos nossas defesas contra possíveis roteadores com problemas ou maliciosos na rede.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0,9,49 com correções do SSU e criptografia mais rápida</summary></details><p>A versão 0.9.49 dá continuidade ao trabalho para tornar a I2P mais rápida e mais segura.
Nós temos várias melhorias e correções para o transporte SSU (UDP) que devem resultar em velocidades mais rápidas.
Essa versão também dá início à migração para a nova e mais rápida criptografia ECIES-X25519 para os roteadores.
(Destinos têm usado essa criptografia há alguns lançamentos agora)
Nós temos trabalhado nas especificações e protocolos para a nova criptografia por vários anos,
e nós estamos chegando perto de terminar! A migração levará diversos lançamentos para ser completada.</p>
<p>Para esse lançamento, para minimizar o transtorno, apenas novas instalações e uma porcentagem muito pequena de instalações existentes
(selecionadas aleatoriamente ao reiniciar) estarão usando a nova criptografia.
Se seu roteador "rechavear" para usar a nova criptografia, ele pode ter tráfego menor ou menor estabilidade do que o normal por vários dias após você reiniciar.
Isso é normal, porque seu roteador gerou uma nova identidade.
Seu desempenho deveria ser recuperado após um tempo.</p>
<p>Nós "rechaveamos" a rede duas vezes antes, ao alterar o tipo de assinatura padrão, mas esta é a primeira vez que mudamos o tipo de criptografia padrão. Espero que tudo corra bem, mas estamos começando devagar para ter certeza.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 com melhorias de desempenho</summary></details><p>0.9.48 permite nosso novo protocolo de criptografia de ponta-a-ponta (proposta 144) para a maioria dos serviços.
Adicionamos suporte preliminar para a criptografia de novas mensagens de construção de túnel (proposta 152).
Há melhorias significativas de desempenho em todo o roteador.</p>
<p>Pacotes para Ubuntu Xenial (16.04 LTS) não são mais suportados. Os usuários nessa plataforma devem atualizar para que você possa continuar a receber atualizações I2P.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 permite nova criptografia</summary></details><p>A versão 0.9.47 habilita nosso novo protocolo de criptografia de ponta a ponta (proposta 144) por padrão para alguns serviços. A ferramenta de análise e bloqueio Sybil agora está habilitada por padrão.</p>
<p>Java 8 ou superior agora é necessário. Os pacotes Debian para Wheezy e Stretch, e para Ubuntu Trusty e Precise, não são mais suportados. Os usuários nessas plataformas devem atualizar para que você possa continuar a receber atualizações I2P.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 com correções de falha</summary></details><p>0.9.46 contém melhorias significativas de desempenho na biblioteca de streaming. Concluímos o desenvolvimento da criptografia ECIES (proposta 144) e agora há uma opção para habilitá-la para testes.</p>
<p>Para usuários de Windows apenas:
Essa versão corrige uma vulnerabilidade de escalação de privilégio local
que poderia ser explorada por um usuário local.
Por favor, aplique a atualização o mais breve possível.
Obrigado à Blaze Infosec pela divulgação responsável do problema.</p>
<p>Esta é a última versão a suportar Java 7, pacotes Debian Wheezy e Stretch, e pacotes Ubuntu Precise e Trusty. Os usuários nessas plataformas devem atualizar para receber atualizações futuras do I2P.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 com correções de falha</summary></details><p>0.9.45 contém correções importantes para o modo oculto e o testador de largura de banda. Há uma atualização para o tema escuro do console. Continuamos a trabalhar na melhoria do desempenho e no desenvolvimento de uma nova encriptação de ponta a ponta (proposta 144).</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="Lançada versão 0.9.44" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 com correções de erros</summary></details><p>0.9.44 contém uma correção importante para um problema de negação de serviço no processamento de novos tipos de criptografia de serviços ocultos. Todos os usuários devem atualizar o mais rápido possível.</p>
<p>Esse lançamento contém suporte inicial para uma nova criptografia ponta-a-ponta (proposta 144).
Este é trabalho em andamento e ainda não está pronto para uso.
Há mudanças na pagina inicial do painel, e novos media players HTML5 embutidos no i2psnark.
Correções adicionais para redes IPV6 protegidas por firewall estão incluídas.
Correções para a construção do túnel devem resultar em uma inicialização mais rápida para certos usuários. </p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 com correções de falha</summary></details><p>No lançamento 0.9.43, nos continuamos trabalhando em fortes recursos de segurança, privacidade e melhorias de desempenho.
Nossa implementação da nova especificação leaseset (LS2) está agora completa.
Estamos começando a implementar uma criptografia ponta-a-ponta mais rápida, forte e segura (proposta 144) em um futuro lançamento.
Diversos problemas de detecção de endereços IPv6 foram solucionados, e nisso é claro há diversas outras correções de falha. </p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 com correções de falha</summary></details><p>0.9.42 continua com o trabalho de tornar a I2P mais rápida e viável.
Isso inclui diversas mudanças para acelerar o nosso transporte UDP.
Nós dividimos os arquivos de configuração para permitir um empacotamento mais modular em futuros trabalhos.
Nos continuamos com o trabalho de implementar novas propostas para uma criptografia mais rápida e segura.
E há, é claro, diversas correções de falha.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 com correções de falha</summary></details><p>0.9.41 continua com o trabalho de implementar novas funcionalidade para a proposta 123,
incluindo autenticação entre clientes para leasesets criptografados.
O painel possui uma logo do I2P atualizada e diversos novos ícones.
Atualizamos o instalador do Linux. </p>
<p>A inicialização deve estar mais rápida para plataformas como o Raspberry Pi.
Corrigimos diversos falhas, incluindo alguns erros graves afetando mensagens de baixo nível da rede. </p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 com novos ícones</summary></details><p>0.9.40 inclui suporte para o novo formato de leaseset criptografado.
Nós desativamos o antigo protocolo de transporte NTCP 1.
Há um novo recurso de importação SusiDNS, e um novo mecanismo de filtro automatizado para conexões de entrada. </p>
<p>Nós realizamos diversas melhorias para o instalador nativo do OSX, assim como atualizamos o instalador IzPack.
O trabalho continua em renovar o painel com novos ícones.
Como de praxe, nós corrigimos muitas falhas!</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 com melhorias de desempenho</summary></details><p>0.9.39 inclui mudanças extensas para os novos tipos de base de dados da rede (proposta 123)
Nós empacotamos a extensão i2pcontrol como um aplicativo web para suportar o desenvolvimento de aplicações RPC.
Há numerosas melhorias de desempenho e correções de falha. </p>
<p>Nós removemos os temas clássico e meia-noite para reduzir a carga de manutenção;
usuários prévios desses temas agora verão os temas escuro ou claro.
Também há novos ícones na página inicial, um primeiro passo na atualização do console.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 com o novo instalador passo-a-passo</summary></details><p>A versão 0.9.38 inclui um novo assistente de primeira instalação com um testador de largura de banda.
Nós adicionamos suporte ao formato mais recente de base de dados de GeoIP.
Agora há um novo instalador de perfil do Firefox e um novo instalador nativo para Mac OSX no nosso website.
O trabalho continua para dar suporte ao novo formato de BD de rede "LS2".</p>
<p>Esta versão também contém muitas correções de bugs, incluindo vários problemas com anexos susimail e uma correção para roteadores somente IPv6.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Relatório de Viagem" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P no 35C3</summary></details><p>A equipe I2P esteve praticamente toda presente no 35C3 em Leipzig. Foram realizadas reuniões diárias para revisar o ano passado e abordar nossas metas de desenvolvimento e design para 2019.</p>
<p>A Visão do Projeto e o novo Roteiro podem ser <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">Reveja aqui</a>.</p>
<p>O trabalho continuará no LS2, no Testnet e nas melhorias de usabilidade do nosso site e console. Um plano está em vigor para estar no Tails, Debian e Ubuntu Disco. Ainda precisamos de pessoas para trabalhar no Android e I2P_Bote correções.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 com NTCP2 habilitado</summary></details><p>0.9.37 possibilita um protocolo de transporte mais seguro e rápido chamado NTCP2. </p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>A versão 0.9.36 contém um protocolo de transporte novo e mais seguro chamado NTCP2.
Ele fica desabilitado por padrão, mas você pode habilitá-lo para testes adicionando a <a href="/configadvanced">configuração avançada</a> <tt>i2np.ntcp2.enable=true</tt> e reiniciando.
O NTCP2 estará habilitado no próximo lançamento.</p>
<p>Esse lançamento também contém várias melhorias de desempenho e correções de falha. </p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="Lançada a versão 0.9.35" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>Versão 0.9.35 com pastas SusiMail e Assistente de SSL</summary></details><p>A versão 0.9.35 adiciona suporte para pastas no SusiMail, e um novo 'Assistente' de SSL Wizard para a configurar HTTPS no seu site da Web de "Serviço Oculto".
Nós também temos a coleção usual de correções de erros, especialmente no SusiMail.</p>
<p>Nós estamos a trabalhar muito em várias coisas para a versão 0.9.36, incluindo um novo instalador de OSX e um protocolo de transporte mais rápido e seguro, chamado de NTCP2.</p>
<p>A I2P estará na HOPE em Nova York, de 20 a 22 de julho. Encontre-nos e diga olá!</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="Lançada versão 0.9.34" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 com correções de erros</summary></details><p>A versão 0.9.34 contém várias correções de bugs!
Ela também inclui melhorias no SusiMail, tratamento de IPv6, e seleção de par de túnel.
Nós adicionamos suporte para os esquemas IGD2 no UPnP.
Há também preparação para mais melhorias que você verá em lançamentos futuros.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 com correções de falha</summary></details><p>A versão 0.9.33 contém um grande número de correções de bugs, incluindo o i2psnark, o i2ptunnel, streaming, e o SusiMail.
Para aqueles que não conseguem acessar os sites de repropagação diretamente, nós agora suportamos vários tipos de proxies para repropagação.
Nós agora definimos limites de taxa por padrão no gerenciador de serviços ocultos.
Para aqueles que executam servidores de alto tráfego, por favor, revisem e ajustem os limites conforme necessário.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown e Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Problemas de segurança encontrados em quase todos os sistemas</summary></details><p>Um problema muito sério foi encontrado em CPUs modernas que são encontradas em quase todos os computadores vendidos em todo o mundo, incluindo celulares. Esses problemas de segurança são chamados de "Kaiser", "Meltdown" e "Spectre".</p>
<p>O whitepaper do KAISER/KPTI pode ser encontrado em <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, o do Meltdown em <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, e o do SPECTRE em <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. A primeira resposta da Intel está listada em <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">resposta da Intel</a>.</p>
<p>É importante para nossos usuários da I2P atualizar seu sistema, contando que atualizações estejam disponíveis. Patches para o Windows 10 estão disponíveis a partir de agora, Windows 7 e 8 virão logo em seguida. Patches para MacOS já estão disponíveis também. Muitos sistemas Linux têm um Kernel mais novo com uma correção incluída disponível também. O mesmo se aplica ao Android, cuja correção de segurança de 2 de janeiro de 2018 inclui um patch para esses problemas.
Por favor, atualize seus sistemas o quanto antes estiver disponível e for possível.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Bom ano! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Bom ano e I2P em 34C3</summary></details><p>Bom ano da equipa do I2P!</p>
<p>Não menos que 7 membros do time da I2P se encontraram no 34C3 em Leipzig de 27 a 30 de dezembro de 2017. Além dos <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">encontros</a> na nossa mesa nós conhecemos vários amigos da I2P por todo o lugar.
Resultados dos encontros já estão publicados em <a href="http://zzz.i2p" target="_blank">zzz.i2p</a>.</p>
<p>Também distribuímos muitos adesivos e demos informações sobre nosso projeto para quem quisesse. Nosso jantar anual I2P foi um sucesso total como um agradecimento a todos os participantes pelo apoio contínuo da I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 com atualizações do painel</summary></details><p>A versão 0.9.32 contém várias correções no console do roteador e aplicações web associadas (livro de endereços, i2psnark, e susimail).
Nós também mudamos a forma como nós lidamos com nomes de host configurados para informações de roteador publicadas, para eliminar alguns ataques de enumeração de rede via DNS.
Nós adicionamos algumas verificações no console para resistir a ataques de revinculação.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 com atualizações do painel</summary></details><p>As mudanças nessa versão são muito mais perceptíveis do que o normal!
Nós renovamos o console do roteador para torná-lo mais fácil de entender,
melhoramos a acessibilidade e suporte cross-browser ,
e organizamos as coisas no geral.
Esse é um primeiro passo em um plano de mais longo prazo para tornar o console do roteador mais amigável ao usuário.
Nós também adicionamos suporte a classificações e comentários de torrents ao i2psnark.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Chamada para os Tradutores" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>A próxima versão 0.9.31 tem mais strings não traduzidas do que o normal</summary></details><p>Em preparação para a versão 0.9.31, que traz consigo atualizações significativas
à interface de usuário, nós temos uma coleção maior do que o normal de strings
não traduzidas que precisam de atenção. Se você é um tradutor, nós ficaríamos muito felizes
se você pudesse reservar um pouco mais de tempo do que o normal durante esse ciclo de lançamento
para ajustar o ritmo das traduções. Nós disponibilizamos as strings mais cedo
para dar a você três semanas para trabalhas nelas.</p>
<p>Se você não é atualmente um tradutor I2P, agora seria um ótimo momento para se envolver! Por favor, veja o
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">Novo Guia do Tradutor</a>
para obter informações sobre como começar.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 atualizações para Jetty 9</summary></details><p>A versão 0.9.30 contém uma atualização para o Jetty 9 e para o Tomcat 8.
As versões anteriores não têm mais suporte, e não estão disponíveis nos futuros lançamentos Debian Stretch e Ubuntu Zesty.
O roteador migrará o arquivo de configurações jetty.xml para cada website Jetty para a nova configuração do Jetty 9.
Isso deve funcionar para configurações recentes e não modificadas, mas pode não funcionar para configurações modificadas ou muito antigas.
Verifique que seu website Jetty funciona após atualizar, e nos contate no IRC se você precisar de assistência.</p>
<p>Diversos plugins não são compatíveis com o Jetty 9 e precisam ser atualizados.
Os seguintes plugins foram atualizados para funcionar com a 0.9.30, e seu roteador deve atualizá-los após reiniciar:
i2pbote 0.4.6; zzzot 0.15.0.
The following plugins (with current versions listed) will not work with 0.9.30.
Contact the appropriate plugin developer for the status of new versions:
Os seguintes plugin (com as versões atuais listadas) não funcionarão com a 0.9.30.
Entre em contato com o desenvolvedor apropriado do plugin para o status das novas versões:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contém correções de erros</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P - Vulnerabilidade de Segurança Bote" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P - Vulnerabilidade de Segurança Bote</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contém correções erro</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P - Vulnerabilidade de Segurança Bote" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P - Vulnerabilidade de Segurança Bote</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
for this.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
<p>Esta versão também oferece suporte à migração de serviços ocultos DSA-SHA1 antigos (2014 e anteriores) para o tipo de assinatura EdDSA mais seguro. Ver <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> para obter mais informações, incluindo um guia e perguntas frequentes.</p>
<p>Nota: Em plataformas ARM não Android, como o Raspberry Pi, o banco de dados blockfile será atualizado na reinicialização, o que pode levar vários minutos. Por favor, seja paciente.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contém correções de erros</summary></details><p>A versão 0.9.29 contém correções para diversos tickets Trac, incluindo alternativas para mensagens compactadas corrompidas.
Nós agora suportamos NTP sobre IPv6.
Nós adicionamos suporte preliminar ao Docker.
Nós agora traduzimos as páginas de manual.
Nós agora passamos headers Referer same-origin pelo proxy HTTP.
Há mais correções para o Java 9, embora nós ainda não recomendemos o Java 9 para uso geral.</p>
<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P - Vulnerabilidade de Segurança Bote" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P - Vulnerabilidade de Segurança Bote</summary></details><p>O I2P-Bote 0.4.4 corrige uma vulnerabilidade de segurança presente em todas as versões anteriores doplug-in I2P-Bote. O aplicativo para Android não foi afetado.</p>
<p>Ao mostrar emails para o usuário, a maioria dos campos estava sendo escapada. Contudo, os nomes de arquivos
dos anexos não eram escapados, e poderiam ser usados para executar código malicioso em um navegador
com JavaScript habilitado. Eles agora estão escapados, e adicionalmente a isso uma Política de Segurança de Conteúdo
foi implementada para todas as páginas.</p>
<p>Todos os usuários do I2P-Bote serão atualizados automaticamente na primeira vez que eles reiniciarem seu roteador
após a versão 0.9.29 da I2P ser lançada na metade de fevereiro. Todavia, por segurança nós recomendamos que você
<a href="http://bote.i2p/install/">siga as instruções na página de instalação</a> para
atualizar manualmente se você planeja usar a I2P ou o I2P-Bote no meio-tempo.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contém correções erro</summary></details><p>A versão 0.9.28 contém correções para mais de 25 tickets Trac, e atualizações para vários pacotes de software embutidos incluindo o Jetty.
Há correções para a funcionalidade de teste de par IPv6 introduzida no último lançamento.
Nós damos continuidade a melhorias para detectar e bloquear pares que sejam potencialmente maliciosos.
Há correções preliminares para Java 9, embora nós ainda não recomendemos o Java 9 para uso geral.</p>
<p>I2P estará em 33C3, por favor, pare em nossa mesa e nos dê suas ideias sobre como melhorar a rede. Revisaremos nosso roteiro de 2017 e nossas prioridades para 2017 no Congresso.</p>
<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P - Vulnerabilidade de Segurança Bote" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P - Vulnerabilidade de Segurança Bote</summary></details><p>O I2P-Bote 0.4.4 corrige uma vulnerabilidade de segurança presente em todas as versões anteriores doplug-in I2P-Bote. O aplicativo para Android não foi afetado.</p>
<p>Uma ausência de proteção contra CSRF significava que se um usuário estava executando o I2P-Bote e então carregava um
site malicioso em um navegador com JavaScript habilitado, o adversário poderia disparar ações
no I2P-Bote em nome do usuário, tais como enviar mensagens. Isso pode ter permitido também
a extração de chaves privadas para endereços I2P-Bote, contudo, nenhuma prova de exploração foi testada
para isso.</p>
<p>Todos os usuários do I2P-Bote serão atualizados automaticamente na primeira vez que eles reiniciarem seu roteador
após a versão 0.9.28 da I2P ser lançada na metade de dezembro. Contudo, por segurança nós recomendamos que você
<a href="http://bote.i2p/install/">siga as instruções na página de instalação</a> para
atualizar manualmente se você planeja usar a I2P ou o I2P-Bote no meio-tempo. Você deveria
também considerar gerar novos endereços I2P-Bote se você navega por sites regularmente com
JavaScript habilitado enquanto executa o I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="Lançada a versão 0.9.27" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>A versão 0.9.27 contém correções de erros</summary></details><p>0.9.27 contém algumas correções de erros.
Biblioteca GMP atualizada para aceleração de encriptação, que foi incorporada no lançamento da versão 0.9.26 apenas para novas instalações e compilações Debian, está agora incluída na atualização de rede para a versão 0.9.27.
Existem alguns melhoramentos no transporte de IPv6, teste de peer SSU, e modo ocultado.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
which will speed up crypto operations considerably.
Also, we are now using constant-time GMP functions to prevent side-channel attacks.
For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
we will include them for in-net updates in the 0.9.27 release.</p>
<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
<p>There's a collection of bug fixes also, including a fix for a timer bug
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>A versão 0.9.25 contém SAM 3.3, códigos QR, e correções de erros</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
It adds QR codes for sharing hidden service addresses with others,
and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
to make it easier to declare that your group of routers is run by a single person.
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="Lançada a versão 0.9.24" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
Your router will not automatically update if you are using Java 6.</p>
<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration,
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
<p>Atualizamos uma série de plugins durante <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Verão</a> e seu roteador irá atualizá-los automaticamente após a reinicialização.</p>
<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="Proposta do I2P Stack Exchange" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P é agora um site proposto no Stack Exchange!</summary></details><p>I2P é agora um site proposto no Stack Exchange! Por favor <a href="https://area51.stackexchange.com/proposals/99297/i2p">comprometer-se a usá-lo</a> Assim, a fase beta pode começar.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contém atualizações de criptografia, melhorias no empacotamento Debian e correções de bugs</summary></details><p>0.9.26 contém uma grande atualização para a nossa biblioteca de criptografia nativa, um novo protocolo de assinatura de catálogo de endereços com assinaturas e grandes melhorias para o pacote Debian / Ubuntu.</p>
<p>Para criptografia, nós atualizamos para o GMP 6.0.0, e adicionamos suporte para novos processadores,
o que acelerará as operações de criptografia consideravelmente.
Ainda, nós agora estamos usando funções GMP de tempo constante para prevenir ataques de canal lateral.
Por precaução, as mudanças de GMP estão habilitadas somente para novas instalações e construções Debian/Ubuntu;
nós as incluiremos para atualizações em rede no lançamento da versão 0.9.27.</p>
<p>Para compilações Debian/Ubuntu, adicionamos dependências em vários pacotes, incluindo Jetty 8 e geoip, e removemos o código empacotado equivalente.</p>
<p>Há ainda uma coleção de correção de bugs, incluindo uma correção para um bug de temporizador
que causava instabilidade e degradação de desempenho ao longo do tempo.
Como de costume, nós recomendamos que todos os usuários atualizem para essa versão.
A melhor forma de ajudar a rede e se manter seguro é executar a versão mais recente.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>A versão 0.9.25 contém SAM 3.3, códigos QR, e correções de erros</summary></details><p>A versão 0.9.25 contém uma grande nova versão do SAM, v3.3, para dar suporte a aplicações multi protocolo sofisticadas.
Ela adiciona QR codes para compartilhar endereços de serviços ocultos com os outros,
e imagens "identicon" para distinguir endereços visualmente.</p>
<p>Nós adicionamos uma nova página de configuração de "família do roteador" no console,
para tornar mais fácil declarar que o seu grupo de roteadores é executado por uma única pessoa.
Há várias mudanças para aumentar a capacidade da rede e, assim se espera, melhorar o sucesso de construção de túneis.</p>
<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="Lançada a versão 0.9.24" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contém várias correções de bugs e acelerações</summary></details><p>A versão 0.9.24 contém uma nova versão do SAM (v3.2) e várias correções de bugs e melhorias de eficiência.
Note que essa versão é a primeira a requerer Java 7.
Por favor, atualize para o Java 7 ou 8 o mais breve possível.
Seu roteador não atualizará automaticamente se você estiver usando Java 6.</p>
<p>Para prevenir os problemas causados pela antiga biblioteca commons-logging, nós a removemos.
Isso fará com que plugins muito antigos do I2P-Bote (0.2.10 e anterior, assinados por HungryHobo) travem se eles tiverem IMAP habilitado.
A correção recomendada é substituir seu antigo plugin do I2P-Bote pelo atual assinado pelo str4d.
Para mais detalhes, veja <a href="http://bote.i2p/news/0.4.3">esta publicação</a>.</p>
<p>Nós tivemos um ótimo <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">Congresso 32C3</a> e estamos fazendo um bom progresso nos nossos planos de projeto de 2016.
O Echelon deu uma palestra sobre a história da I2P e o status atual, e seus slides estão <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">aqui</a> (pdf).
O Str4d participou do <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> e deu uma palestra sobre nossa migração de criptografia.
Seus slides estão <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">aqui</a> (pdf).</p>
<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contém uma variedade de correções de bugs, e algumas pequenas melhorias no I2PSnark</summary></details><p>Olá, I2P! Este é o primeiro lançamento assinado por mim (str4d), depois de 49 lançamentos
assinados pelo zzz. Esse é um teste importante da nossa redundância para todas as coisas,
incluindo pessoas.</p>
<p><b>Limpeza</b></p>
<p>My signing key has been in router updates for over two years (since 0.9.9), so
if you are on a recent version of I2P this update should be just as easy as
every other update. However, if you are running an older version than 0.9.9, you
will first need to manually update to a recent version. Update files for recent
versions can be downloaded
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
and instructions on how to manually update are provided
<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
updated, your router will then find and download the 0.9.23 update as usual.</p>
<p>If you installed I2P via a package manager, you are not affected by the change,
and can update as usual.</p>
<p>A minha chave de assinatura esteve em atualizações do roteador por mais de dois anos (desde a versão 0.9.9), então
se você está em uma versão recente da I2P essa atualização deve ser tão fácil quanto
qualquer outra. Todavia, se você estiver executando uma versão mais antiga do que a 0.9.9, você
precisará primeiro atualizar manualmente para uma versão mais recente. Arquivos de atualização para versões
recentes podem ser baixados
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">aqui</a>,
e instruções de como atualizar manualmente são providenciadas
<a href="http://i2p-projekt.i2p/en/download#update">aqui</a>. Uma vez que você tenha atualizado
manualmente, seu roteador então encontrará e baixará a atualização 0.9.23 como de costume.</p>
<p>Se você instalou o I2P através de um gerenciador de pacotes, você não é afetado pela alteração e pode atualizar como de costume.</p>
<p><b>Detalhes da atualização</b></p>
<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
with at least half of the network already estimated to have rekeyed. This
release accelerates the rekeying process. To reduce network churn, your router
will have a small probability of converting to Ed25519 at each restart. When it
does rekey, expect to see lower bandwidth usage for a couple of days as it
reintegrates into the network with its new identity.</p>
<p>Note that this will be the last release to support Java 6. Please update to
Java 7 or 8 as soon as possible. We are already working to make I2P compatible
with the upcoming Java 9, and some of that work is in this release.</p>
<p>We have also made some minor improvements in I2PSnark, and added a new page in
the routerconsole for viewing older news items.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
and use bandwidth more effectively.
We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
using the new "multisession" capability for those sites that don't support ECDSA.</p>
<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto - Oradores e agenda anunciados" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 - Oradores e agenda anunciados</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>A migração de informações de roteador para novas e mais fortes assinaturas Ed25519 está indo bem,
com pelo menos metade da rede já estimada a ter rechaveado. Esse
lançamento acelera o processo de rechaveamento. Para reduzir a agitação na rede, seu roteador
terá uma pequena probabilidade de converter para Ed25519 a cada reinício. Quando ele
rechavear, espere ver uso de banda reduzido por alguns dias enquanto ele se
reintegra à rede com sua nova identidade.</p>
<p>Note que essa será a última versão a suportar Java 6. Por favor, atualize para
o Java 7 ou 8 o mais breve possível. Nós já estamos trabalhando em tornar a I2P compatível
com o futuro Java 9, e um pouco desse trabalho está nesse lançamento.</p>
<p>Também fizemos algumas pequenas melhorias no I2PSnark e adicionamos uma nova página noconsole do roteador para visualizar notícias mais antigas.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="Lançada a versão 0.9.22" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 com correções de bugs e inicia a migração Ed25519</summary></details><p>A versão 0.9.22 contém correções para o i2psnark ficando travado antes da finalização, e inicia a migração das informações de roteador para novas e mais fortes assinaturas Ed25519.
Para reduzir a agitação na rede, seu roteador terá uma pequena probabilidade de converter para Ed25519 a cada reinício.
Quando ele rechavear, espere ver uso de banda mais baixo por alguns dias enquanto ele se reintegra à rede com sua nova identidade.
Se tudo ocorrer bem, nós aceleraremos o processo de rechaveamento no próximo lançamento.</p>
<p>I2PCon Toronto foi um grande sucesso! Todas as apresentações e vídeos estão listados no <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">Página I2PCon</a>.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="Lançada a versão 0.9.21" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>Versão 0.9.21 lançada com melhorias de desempenho e correções de falhas.</summary></details><p>A versão 0.9.21 contém diversas modificações que adicionam capacidade a rede, aumentam a eficiência das inundações,
e usam a banda de maneira mais eficiente.
Nós migramos os túneis clientes compartilhados para assinaturas ECDSA e acrescentamos um plano B
usando a nova capacidade "multisessão" para aqueles sites que não suportam ECDSA.</p>
<p>Os palestrantes e a programação da I2PCon em Toronto 2015 foram anunciados.
Dê uma olhada na <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">página da I2PCon</a>para mais detalhes.
Reserve seu assento no <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466"> Eventbrite I2PCon</a>.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto - Oradores e agenda anunciados" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 - Oradores e agenda anunciados</summary></details><p>Os palestrantes e a programação da I2PCon em Toronto 2015 foram anunciados.
Dê uma olhada na <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">página da I2PCon</a>para mais detalhes.
Reserve seu assento no <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466"> Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -0,0 +1,523 @@
<div>
<header title="Notícias da I2P">Feed de notícias e atualizações do roteador</header><article id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a" title="Versão 2.9.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released" author="idk" published="2025-06-02T19:00:00Z" updated="2025-06-02T19:00:00Z"><details><summary>Versão 2.9.0 da I2P</summary></details><p>A versão 2.9.0 da I2P é uma versão de manutenção que inclui correções de bugs e trabalho em novas funcionalidades.</p>
<p>O uso de thread foi aprimorado para melhorar o desempenho do sistema i2ptunnel.
O NTCP2 foi aprimorado para resistir a ataques de probing.
O sistema de notificação foi integrado em mais aplicações para oferecer melhor feedback aos usuários do I2PSnark e das outras aplicações.
A participação automática em floodfill foi corrigida.
Os usuários podem observar uso de recursos mais elevado quando atuando como floodfill.
Se isso não é desejado, o modo floodfill pode ser desabilitado na página /config.</p>
<p>Uma nova funcionalidade de mapa global está disponível no console que mostra as localizações dos roteadores na sua visão do BD de rede.
Eles são os pares que ajudam o seu roteador a construir túneis e oferecer serviços anonimamente.</p>
<p>O trabalho continua em implementar gerenciamento de banda automático para túneis, o protocolo Datagram2 e criptografia pós-quântica.
Em dois lançamentos, na versão 2.11.0, a I2P irá requerer Java 17.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="Versão 2.8.2 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>Versão 2.8.2 da I2P</summary></details><p>A versão 2.8.2 corrige um bug que causa falhas de SHA256 que foi introduzido na versão 2.8.1.
O bug afetou principalmente roteadores de alta largura de banda.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="Versão 2.8.1 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>Versão 2.8.1 da I2P</summary></details><p>A versão 2.8.1 conserta acessos a sites locais que estavam quebrados na 2.8.0.
Adicionamos bolhas de notificação em várias aplicações no painel para destacar mensagens da aplicação.
Corrigimos um bug de teste de túnel que pode ter estado afetando a estabilidade de túnel.
O catálogo de endereços agora possui uma nova aba "mais recente" que exibe os mais novos nomes de domínio adicionados de suas inscrições.
Há várias correções e melhorias para tema escuro.</p>
<p>Corrigimos o instalador que previamente falhava no Java 21 ou mais recente.
Também corrigimos instalar em caminhos de diretórios que contêm espaços em Linux.
Para aqueles de vocês que usam Docker, nós atualizamos bibliotecas e contêiner desatualizados do Docker.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Acesso a site local falha na 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>Bug de Acesso Local da 2.8.0</summary></details><p>Na 2.8.0, navegar para um site local (seja por nome de domínio ou b32) falhará.
A solução paliativa é usar localhost e a porta do servidor, geralmente 7658, para contornar a I2P.
Por exemplo, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
Pedimos desculpas pelo problema e estamos trabalhando em uma correção.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="Versão 2.8.0 da I2P" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>Versão 2.8.0 da I2P</summary></details><p>Esta versão melhora a I2P corrigindo bugs, removendo código inutilizado e melhorando a estabilidade de rede.</p>
<p>Aprimoramos o tratamento de roteadores congestionados na rede.
Problemas com UPnP e NAT traversal foram tratados para aprimorar a conectividade e o relatório de erros.
Nós agora temos uma estratégia mais agressiva para a remoção de leasesets do BD de rede para melhorar o desempenho do roteador e mitigar sobrecargas.
Outras mudanças foram implantadas para reduzir a observabilidade de eventos como um roteador reiniciando ou desligando.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="Lançamento I2P 2.7.0" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>Lançamento I2P 2.7.0</summary></details><p>Esta versão, I2P 2.7.0, continua nosso trabalho corrigindo bugs, melhorando o desempenho e adicionando recursos.</p>
<p>O acesso às informações do console e dos aplicativos foi aprimorado. Foram corrigidos problemas na pesquisa do I2PSnark e do SusiMail. A pesquisa netDB incorporada no console do roteador agora opera de maneira mais intuitiva e útil. Pequenas melhorias foram feitas nas telas de diagnóstico no modo avançado.</p>
<p>Bugs também foram corrigidos para melhorar a compatibilidade dentro da rede. Um problema com a publicação de leaseSets foi resolvido, o que melhora a confiabilidade dos principais serviços ocultos. O I2PSnark não altera mais o infohash quando um usuário altera apenas os rastreadores em um torrent existente. Isso evita que os torrents sejam desnecessariamente interrompidos por essas mudanças. Congratulamo-nos com esta contribuição de um novo colaborador. Um conflito no tratamento de uma opção de biblioteca de streaming foi resolvido para melhorar a compatibilidade com outras implementações I2P.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="Versão 2.6.1 da I2P Lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>Versão 2.6.1 da I2P</summary></details><p>A I2P 2.6.1 é lançada para corrigir um bug de Interface de Usuário na aplicação Gerenciador de Serviços Ocultos.
Esse bug fazia com que a rolagem ficasse desabilitada, tornando algumas configurações inacessíveis.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="Versão 2.6.0 da I2P Lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>Versão 2.6.0 da I2P</summary></details><p>Esta versão, I2P 2.6.0, dá continuidade ao nosso trabalho de corrigir bugs, adicionar funcionalidades, e aprimorar a confiabilidade da rede.</p>
<p>Roteadores mais novos serão favorecidos ao escolher roteadores de floodfill.
A I2PSnark recebeu funcionalidades que aprimoram o desempenho de PeX (Troca de pares), em adição a correções de bugs.
Protocolos de transporte depreciados estão sendo removidos, simplificando o código nos transportes UDP.
Destinos hospedados localmente serão alcançáveis por clientes locais sem solicitar seus LeaseSets, melhorando desempenho e testabilidade.
Ajustes adicionais foram feitos nas estratégias de seleção de par.</p>
<p>A I2P não mais permite I2P-sobre-Tor. Conexões a partir de endereços IP de saída do Tor são agora bloqueadas.
Nós desencorajamos isso porque degrada o desempenho da I2P e usa os recursos das saídas do Tor sem gerar benefícios.
Se você é uma pessoa que ajuda executando tanto uma saída do Tor quanto a I2P, nós encorajamos você a continuar fazendo isso, usando endereços IP diferentes para cada um.
Relays que não são de saída e clientes Tor não são afetados por isso e não precisam mudar nada.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="Versão 2.5.2 da I2P Lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 com correção de HTTP</summary></details><p>A I2P 2.5.2 é lançada para corrigir um bug introduzido na versão 2.5.0 que causava truncamento de alguns conteúdos HTTP. </p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="Versão 2.5.1 da I2P Lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>Versão 2.5.1 da I2P lançada para tratar dos Ataques de Negação de Serviço</summary></details><p>A I2P 2.5.1 é lançada para tratar dos Ataques de Negação de Serviço afetando a rede e os serviços I2P.
Com este lançamento nós desabilitamos as partes baseadas em IP da ferramenta de detecção de ataque Sybil que foram alvo para amplificar o efeito e a duração do ataque.
Isso deve ajudar a rede a retornar a operação normal.
Aqueles de vocês que desabilitaram a ferramenta de detecção de ataque Sybil podem reabilitá-la com segurança.
Ajustes a outros subsistemas para aprimorar a validação de RouterInfo e seleção de par também foram realizados.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Clima Tempestuoso" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Clima da Rede: Tempestuoso. A I2P está sob ataque.</summary></details><p>A rede I2P no momento está sob um ataque de Negação de Serviço.
Esse ataque afeta a I2P e a i2pd, mas de diferentes formas, e está tendo um sério efeito na saúde da rede.
A alcançabilidade de sites I2P está gravemente degradada.</p>
<p>Se você está hospedando um serviço dentro da I2P e ele está hospedado em um roteador de Floodfill, você deveria considerar fazer multihoming do serviço em um roteador com função de Floodfill desabilitada para melhorar a alcançabilidade.
Outras mitigações estão sendo discutidas, mas ainda se está trabalhando em uma solução retrocompatível e de longo prazo.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="Nova versão I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>Mais melhorias na aplicação, revisão da estratégia de isolamento de BD de rede</summary></details><p>Esta versão, I2P 2.5.0, fornece mais melhorias visíveis ao usuário do que a versão 2.4.0, que foi focada na implementação da estratégia de isolamento do BD de rede.</p>
<p>Novas funcionalidades foram adicionadas ao I2PSnark, como a possibilidade de pesquisar torrents.
Bugs foram resolvidos para melhorar a compatibilidade com outros clientes de torrents I2P como o BiglyBT e o qBittorrent.
Nós gostaríamos de agradecer a todos os desenvolvedores que trabalharam com a libtorrent e com o qBittorrent para proporcionar e melhorar seu suporte à I2P.
Novas funcionalidades também foram adicionadas ao SusiMail, incluindo suporte a formatação Markdown em emails e a habilidade de arrastar e soltar anexos nos emails.
Túneis criados com o gestor de Serviços Ocultos agora têm suporte a "Keepalive", o que melhora o desempenho e a compatibilidade com tecnologias web, permitindo sites I2P mais sofisticados.</p>
<p>Durante essa versão nós também fizemos vários ajustes no BD de rede para melhorar sua resiliência a spam e para melhorar a capacidade do roteador de rejeitar mensagens suspeitas.
Isso foi parte de um esforço para "revisar" a implementação de defesas de "Isolamento Sub-DB de rede" da versão 2.4.0.
Essa investigação descobriu um pequeno evento de perfuração do isolamento, o que qual nós consertamos.
Esse problema foi descoberto e resolvido internamente pelo time da I2P.</p>
<p>Durante essa versão várias melhorias foram feitas no processo de lançamento das nossas distribuições downstream para Android e Windows.
Isso deve resultar em uma melhor entrega e disponibilidade desses produtos downstream.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="Versão I2P 2.4.0 com melhorias de congestionamento e segurança do NetDB" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>Versão I2P 2.4.0 com melhorias de congestionamento e segurança do NetDB</summary></details><p>Esta versão, I2P 2.4.0, continua nosso esforço de melhorar a segurança e estabilidade da rede I2P.
Ela contém melhorias significativas ao BD de rede, uma estrutura essencial dentro da rede I2P usada para descobrir seus pares.</p>
<p>As mudanças no tratamento de congestão aperfeiçoarão a estabilidade da rede dando aos roteadores a possibilidade de aliviar pares congestionados evitando-os.
Isso ajudará a rede a limitar a efetividade de spam de túnel.
Isso também vai ajudar a rede a se regenerar durante e após ataques DDOS.</p>
<p>As mudanças do BD de rede também ajudam a proteger roteadores individuais e as aplicações que os utilizam.
Roteadores agora podem se defender conta atacantes separando o BD de rede em vários "Sub-BDs", os quais nós utilizamos para prevenir vazamentos de informação entre aplicações e o roteador.
Isso também aperfeiçoa a informação disponível aos roteadores Java sobre sua atividade de BD de rede e simplifica nosso suporte a aplicações multihoming.</p>
<p>Também estão incluídas uma série de correções de bugs e melhorias nos aplicativos I2PSnark e SusiMail.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:" title="Nova versão I2P 2.3.0 - Correções de segurança, listas de bloqueio ajustáveis, API DTG" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Correções de segurança, listas de bloqueio ajustáveis, API DTG</summary></details><p>Essa versão contém correções para o CVE-2023-36325.
O CVE-2023-36325 é um bug de confusão de contexto que ocorria no filtro de Bloom.
Um atacante cria uma mensagem I2NP contendo um messageID único, e envia esse messageID para um cliente.
A mensagem, após passar pelo filtro de Bloom, não é permitida ser reusada em uma segunda mensagem.
O atacante então envia a mesma mensagem diretamente para o roteador.
O roteador passa a mensagem para o filtro de Bloom, e é descartada.
Isso vaza a informação de que o messageID já foi visto antes, dando ao atacante um forte motivo para acreditar que o roteador está hospedando o cliente.
Isso foi corrigido separando a funcionalidade do filtro de Bloom em diferentes contextos com base em se uma mensagem chegou por um túnel de cliente, um túnel exploratório, ou foi enviada diretamente ao roteador.
Sob circunstâncias normais, esse ataque leva vários dias para ter sucesso e pode ser confundido por vários outros fatores, tais como roteadores reiniciarem durante a fase do ataque e sensibilidade a falsos positivos.
Recomenda-se que usuários da I2P Java atualizem a versão imediatamente para evitarem o ataque.</p>
<p>No curso da correção desse bug de confusão de contexto, nós revisamos algumas de nossas estratégias de desenvolver código defensivamente, contra esses tipos de vazamentos.
Isso inclui ajustes ao BD de rede, os mecanismos de limite de taxa, e o comportamento dos roteadores de floodfill.</p>
<p>Essa versão adiciona o not_bob como um segundo provedor de hosts padrão, e adiciona o <a href="http://notbob.i2p">notbob.i2p</a> e o <a href="http://ramble.i2p">ramble.i2p</a> à página inicial do console.</p>
<p>Essa versão também contém uma lista de bloqueio ajustável.
Bloquear pela lista de bloqueio é semi permanente. Cada endereço IP bloqueado normalmente fica bloqueado até que o roteador seja reiniciado.
Usuários que observarem crescimento explosivo da lista de bloqueio durante ataques Sybil podem optar por limites de tempo mais curtos configurando a lista de bloqueio para expirar entradas a um intervalo.
Essa funcionalidade é desabilitada por padrão e só é recomendada para usuários avançados neste momento.</p>
<p>Essa versão também inclui uma API para plugins modificarem com a GUI de Destkop (DTG).
Agora é possível adicionar itens de menu à área de notificação do sistema, permitindo a inicialização mais intuitiva de plugins que usam interfaces nativas de aplicação.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="Nova versão 2.2.1, correções de empacotamento para Docker, Ubuntu Lunar e Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - versão de manutenção para 2.2.0</summary></details><p>Após o lançamento da I2P versão 2.2.0, que foi empurrada para frente para acelerar mitigações aos ataques DDOS, nós descobrimos alguns problemas de desenvolvimento que tornaram necessário construir e lançar novos pacotes.
Essa versão corrige um problema no Ubuntu Lunar e no Debian Sid onde o console do roteador estava inacessível usando uma versão atualizada do pacote jakarta.
Os pacotes Docker não estavam lendo argumentos corretamente, resultando em arquivos de configuração inacessíveis.
Esse problema também foi resolvido.
O contêiner docker é agora também compatível com o Podman.</p>
<p>Esta versão sincroniza traduções com transifex e atualiza o banco de dados GeoIP.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="Nova versão 2.2.0, Mitigações para ataques DDOS e ajustes no subsistema Streaming" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Atenuações para ataques DDOS e ajustes no subsistema Streaming</summary></details><p>Optamos por antecipar a data de lançamento da versão 2.2.0, que ocorrerá hoje, 13 de março de 2023. Esta versão inclui alterações nos componentes NetDB, Floodfill e Peer-Selection que melhoram a capacidade do roteador de sobreviver a ataques DDOS. É provável que os ataques continuem, mas as melhorias nesses sistemas ajudarão a mitigar o risco de ataques DDOS, ajudando o roteador a identificar e despriorizar roteadores que parecem maliciosos.</p>
<p>Essa versão também adiciona proteção contra repetição ao subsistema de Streaming, o que evita que um atacante que consiga capturar um pacote criptografado possa reusá-lo enviando-o para destinatários indesejados.
Essa é uma mudança retrocompatível, então roteadores mais antigos continuarão sendo capazes de usar as capacidades de streaming de roteadores mais novos.
Esse problema foi descoberto e resolvido internamente, pelo time de desenvolvimento da I2P, e não está relacionado aos ataques DDOS.
Nós nunca encontramos um pacote de streaming repetido e não acreditamos que um ataque de repetição de streaming tenha algum dia acontecido contra a rede I2P neste momento.</p>
<p>Como você pode ter notado, estas notas de lançamento e o lançamento da versão em si foram assinados pelo idk, e não pelo zzz.
O zzz decidiu deixar o projeto e suas responsabilidades estão sendo apropriadas por outros membros do time.
Como tal, o projeto está trabalhando em substituir a infraestrutura de estatísticas de rede e mover o fórum de desenvolvimento para i2pforum.i2p.
Nós agradecemos ao zzz por fornecer esses serviços por tanto tempo.</p>
<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="Atualização de DDoS" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>Atualização de DDoS</summary></details><p>Nós confirmamos que o atacante controla um grande número de roteadores.
Nossas investigações e mitigações continuam.</p>
<p>Esse é um bom momento para lembrar as pessoas de que mesmo após 20 anos, a rede I2P é relativamente pequena.
Nós não temos indícios de que o atacante está tentando desanonimizar algum usuário ou serviço oculto em particular.
Todavia, se seu modelo de risco é de alto risco, você deve considerar cuidadosamente se a I2P atualmente oferece a proteção que você requer.
A melhor solução a longo prazo é divulgar e fazer crescer a rede I2P para aumentar a segurança de nossos usuários.</p>
<p>Nós providenciaremos informações adicionais aqui no feed de notícias e em <a href="http://zzz.i2p">zzz.i2p</a> conforme necessário.
Nós pedimos a sua paciência enquanto trabalhamos para melhorar a I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="Sobre os recentes ataques de Negação de Serviço" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>A I2P continua intacta com desempenho prejudicado</summary></details><p>A rede I2P está atualmente sendo afetada por um ataque de Negação de Serviço.
A função de floodfill da rede foi afetada, resultando em respostas sendo prejudicadas e taxas de sucesso de construção de túnel caindo.
Participantes na rede têm sofrido dificuldades ao conectar a sites I2P e ao usar serviços I2P.
Estratégias de mitigação estão sendo investigadas e implementadas gradualmente.</p>
<p>Embora o ataque tenha degradado o desempenho, a rede segue intacta e usável.
Roteadores I2P Java parecem estar lidando com esses problemas melhor do que os roteadores i2pd por agora.
Várias mitigações devem começar a aparecer nas construções de desenvolvimento tanto dos roteadores Java quanto dos roteadores C++ na próxima semana.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="Versão 2.1.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 com diversas correções de SSU2</summary></details><p>Nós descobrimos várias coisas desde a nossa versão 2.0.0 em novembro.
Conforme os roteadores atualizaram para essa versão, a rede foi de em torno de 1% para mais de 60% de suporte para nosso novo protocolo de transporte SSU2.
Em primeiro lugar, nós confirmamos que o SSU2 é um protocolo seguro, bem projetado, e sólido.
Em segundo lugar, contudo, nós encontramos e corrigimos diversos bugs pequenos ou de baixa ocorrência na implementação do protocolo.
Cumulativamente, os efeitos desses bugs reduziram o desempenho da rede.</p>
<p>Ainda, nós estamos a par do maior número de túneis e da menor taxa de sucesso de construção de túneis na rede,
possivelmente causados pela nova funcionalidade do Bitcoin de endereço transiente da I2P,
mas tornados piores pelos nossos bugs do SSU2 e outros problemas de controle de congestão.
Nós estamos trabalhando com o Bitcoin e com outros projetos não Bitcoin para reduzir as demandas de rede da I2P.
Nós aperfeiçoamos nossos algoritmos para reduzir a carga sobre a rede durante momentos de congestão.
Nós também estamos colaborando com a i2pd para desenvolver estratégias em comum de controle de congestão.</p>
<p>Portanto, nós aceleramos esse lançamento em cerca de seis semanas, para levar as correções para todo mundo.
A i2pd lançou sua versão 2.45.0 na semana passada e os resultados iniciais são encorajadores.
Novos protocolos, e redes distribuídas, são difíceis de desenvolver.
A congestão pode chegar com pouco aviso e com pouco indício de causa.
Obrigado por sua paciência enquanto nós diagnosticávamos e, assim se espera, resolvíamos os problemas.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="Versão 2.0.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>Transporte SSU2 Habilitado</summary></details><p>A I2P versão 2.0.0 habilita nosso novo transporte UDP SSU2 para todos os usuários, após o término de pequenas funcionalidades, testes, e diversas correções de bugs.</p>
<p>Nós também temos correções por todo o lugar, incluindo instalador, base de dados de rede, adição ao livro de endereços privado, inicializador de navegador do Windows, e UPnP IPV6.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Posts Recentes do Blog" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Alguns posts recentes do blog</summary></details><p>Aqui estão links para diversas publicações recentes no nosso website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Visão geral do nosso novo transporte SSU2</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">Um aviso sobre moedas I2P e outros golpes</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">Uma entrevista com o Konrad do diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">Uma entrevista com o Dustin da StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="Versão 1.9.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 com SSU2 para testes</summary></details><p>Nós passamos os últimos três meses trabalhando em nosso novo protocolo de transporte UDP "SSU2"
com um pequeno número de testadores voluntários.
Essa versão completa a implementação, incluindo testes de par e de transmissor.
Nós estamos o habilitando por padrão para as plataformas Android e ARM, e para uma pequena porcentagem de outros roteadores aleatoriamente.
Isso nos permitirá fazer muito mais testes nos próximos três meses, terminar a funcionalidade de migração de conexão,
e consertar quaisquer problemas restantes.
Nós planejamos habilitá-lo para todo mundo no próximo lançamento agendado para novembro.
Nenhuma configuração manual é necessária.</p>
<p>Claro, há a coleção usual de correções de bugs nesta versão também. Também adicionamos um detector automático de deadlock que já encontrou um raro deadlock que agora está corrigido.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="Novo Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>Novo Outproxy</summary></details><p>"Proxies de saída" (nodos de saída) da I2P podem ser usados para acessar a internet através
do seu túnel de proxy HTTP.
Conforme aprovado em nossa <a href="http://i2p-projekt.i2p/en/meetings/314">reunião mensal</a>,
<b>exit.stormycloud.i2p</b> é agora nosso proxy de saída recomendado e oficial, substituindo o há muito morto <b>false.i2p</b>.
Para mais informações sobre a <a href="http://stormycloud.i2p/">organização</a>,
o <a href="http://stormycloud.i2p/outproxy.html">proxy de saída</a>,
e os <a href="http://stormycloud.i2p/tos.html">termos de serviço</a> da StormyCloud,
veja o <a href="http://stormycloud.i2p/">website da StormyCloud</a>.</p>
<p>Nós sugerimos que você modifique a sua <a href="/i2ptunnel/edit?tunnel=0">configuração do Gerenciador de Serviços Ocultos</a>
para especificar <b>exit.stormycloud.i2p</b>
em dois lugares: <b>Proxies de Saída</b> e <b>Proxies de Saída SSL</b>.
Após editar, <b>role para baixo e clique em Salvar</b>.
Veja nossa <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">publicação no blog para uma captura de tela</a>.
Para instruções para o Android e capturas de tela, veja o <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">blog do notbob</a>.</p>
<p>As atualizações do roteador não atualizarão sua configuração, você deve editá-la manualmente. Obrigado a StormyCloud por seu apoio, e por favor, considere uma <a href="http://stormycloud.i2p/donate.html">doação</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 com correções de bugs</summary></details><p>Essa versão inclui correções de bugs no i2psnark,
no roteador, I2CP, e UPnP.
As correções no roteador tratam bugs no reinício suave, IPv6, testes de par SSU,
armazenamento do banco de dados de rede, e construção de túnel.
O tratamento de família de roteador e classificação de Sybil também foram
melhorados significativamente.</p>
<p>Junto da i2pd, nós estamos desenvolvendo nosso novo transporte UDP, o SSU2.
O SSU2 trará melhoras substanciais de desempenho e segurança.
Ele também permitirá que nós finalmente substituamos nosso último uso da criptografia muito lenta ElGamal,
completando a atualização completa de criptografia que nós iniciamos cerca de 9 anos atrás.
Essa versão contém uma implementação preliminar que fica desabilitada por padrão.
Se você deseja participar em testes, por favor, busque informações atuais
em zzz.i2p.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Instalar atualizações essenciais do Java/Jpackage" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>A recente vulnerabilidade Java de "Assinaturas Psíquicas" afeta a I2P. Usuários atuais da
I2P no Linux, ou quaisquer usuários da I2P que estiverem usando uma JVM que não veio junto no pacote devem atualizar
sua JVM ou mudar para uma versão que não contém a vulnerabilidade, abaixo
do Java 15.</p>
<p>Novos pacotes I2P Easy-Install foram gerados usando a versão mais recente doJava Virtual Machine. Mais detalhes foram publicados nos respectivos feeds de notícias do pacote.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 com melhorias de confiabilidade e desempenho</summary></details><p>A versão 1.7.0 contém várias melhorias de desempenho e confiabilidade.</p>
<p>Agora há mensagens pop-up na bandeja do sistema, para as plataformas que o suportam. i2psnark tem um novo editor de torrent. O transporte NTCP2 agora usa muito menos CPU.</p>
<p>A há muito obsoleta interface BOB está removida para novas instalações.
Ela continuará funcionando em instalações existentes, exceto em pacotes Debian.
Quaisquer usuários de aplicações BOB que ainda restarem devem pedir aos desenvolvedores que as convertam para o protocolo SAMv3.</p>
<p>Nós sabemos que desde a nossa versão 1.6.1, a estabilidade da rede tem deteriorado continuamente.
Nós ficamos a par do problema logo após o lançamento, mas levou quase dois meses para nós encontrarmos a causa.
Nós eventualmente a identificamos como um bug na i2pd 2.40.0,
e a correção será na sua versão 2.41.0, que será lançada mais ou menos na mesma data que esta versão.
Ao longo do caminho, nós fizemos várias mudanças do lado da I2P Java para melhorar a
robustez dos armazenamentos e buscas na base de dados de rede, e evitar pares com desempenho ruim na seleção de par de túnel.
Isso deve ajudar a rede a ficar mais robusta mesmo com a presença de roteadores problemáticos ou maliciosos.
Ainda, nós estamos iniciando um programa conjunto para testar os roteadores I2P Java e i2pd pré-lançamento
juntos em uma rede para testes isolada, para que possamos encontrar mais problemas antes dos lançamentos, não depois.</p>
<p>Em outras novidades, nós continuamos a fazer bastante progresso no projeto do nosso novo transporte UDP "SSU2" (proposta 159)
e começamos a implementação.
O SSU2 trará melhoras substanciais de desempenho e segurança.
Ele também permitirá que nós finalmente substituamos nosso último uso da criptografia muito lenta ElGamal,
completando uma atualização completa de criptografia que começou cerca de 9 anos atrás.
Nós esperamos iniciar a testar em conjunto com a i2pd logo, e disponibilizá-lo para a rede mais tarde neste ano.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 permite novas mensagens de construção do túnel</summary></details><p>Este lançamento completa a implementação de duas grandes atualizações do protocolo desenvolvidas em 2021.
A transição para a criptografia X25519 para roteadores é acelerada, e esperamos que quase todos os roteadores sejam chaveados novamente até o final do ano.
As mensagens de construção dos túneis curtos são habilitadas para uma redução significativa da largura de banda.</p>
<p>Adicionamos um painel de seleção de temas ao novo assistente de instalação.
Melhoramos o desempenho da SSU e corrigimos um problema com as mensagens de teste dos pares da SSU.
O filtro Bloom construído no túnel foi ajustado para reduzir o uso de memória.
Melhoramos o suporte para plugins não-Java.</p>
<p>Em outras palavras, estamos fazendo excelentes progressos no projeto de nosso novo SSU2 de transporte UDP e esperamos começar a implementação no início do próximo ano.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 com novas mensagens de construção do túnel</summary></details><p>Sim, é isso mesmo, após nove anos de versões 0.9.x, nós estamos indo direto de 0.9.50 para 1.5.0.
Isso não simboliza uma grande mudança de API, ou uma declaração de que o desenvolvimento agora está completo.
É simplesmente um reconhecimento dos quase 20 anos de trabalho para proporcionar anonimato e segurança para nossos usuários.</p>
<p>Essa versão finaliza a implementação de mensagens de criação de túnel menores para reduzir largura de banda.
Nós continuamos a transição dos roteadores da rede para a criptografia X25519.
Claro que há também diversas correções de bugs e melhorias de desempenho.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Vulnerabilidade de desktop MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Vulnerabilidade do Muwire Desktop</summary></details><p>Uma vulnerabilidade de segurança foi descoberta na versão autônoma da aplicação de desktop do MuWire.
Ela não afeta o plugin do console, e não está relacionada com o problema no plugin anunciado previamente.
Se você executa a aplicação para desktop do MuWire, você deve <a href="http://muwire.i2p/">atualizar para a versão 0.8.8</a> imediatamente.</p>
<p>Os detalhes da edição serão publicados em <a href="http://muwire.i2p/security.html">muwire.i2p</a>
em 15 de julho de 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Vulnerabilidade de plug-in MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Vulnerabilidade de plug-in Muwire</summary></details><p>Foi detetada uma vulnerabilidade de segurança no plugin MuWire. Ele não afeta o cliente de desktop autônomo. Se você estiver executando o plugin MuWire, você deve <a href="/configplugins">atualizar para a versão 0.8.7-B1</a> imediatamente.</p>
<p>Ver <a href="http://muwire.i2p/security.html">muwire.i2p</a>
para obter mais informações sobre a vulnerabilidade e recomendações de segurança atualizadas.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 com correções do IPv6</summary></details><p>A versão 0.9.50 dá continuidade à transição ao ECIES-X25519 para chaves de criptografia dos roteadores.
Nós habilitamos DNS sobre HTTPS para repropagação para proteger usuários contra snooping passivo de DNS.
Há diversas correções e melhorias para endereços IPv6, incluindo o novo suporte aUPnP.</p>
<p>Nós finalmente corrigimos alguns antigos bugs de corrupção no SusiMail.
Mudanças no limitador de banda devem melhorar o desempenho de túnel da rede.
Há várias melhorias no nossos contêiners Docker.
Nós melhoramos nossas defesas contra possíveis roteadores com problemas ou maliciosos na rede.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 com correções do SSU e criptografia mais rápida</summary></details><p>A versão 0.9.49 dá continuidade ao trabalho para tornar a I2P mais rápida e mais segura.
Nós temos várias melhorias e correções para o transporte SSU (UDP) que devem resultar em velocidades mais rápidas.
Essa versão também dá início à migração para a nova e mais rápida criptografia ECIES-X25519 para os roteadores.
(Destinos têm usado essa criptografia há alguns lançamentos agora)
Nós temos trabalhado nas especificações e protocolos para a nova criptografia por vários anos,
e nós estamos chegando perto de terminar! A migração levará diversos lançamentos para ser completada.</p>
<p>Para esse lançamento, para minimizar o transtorno, apenas novas instalações e uma porcentagem muito pequena de instalações existentes
(selecionadas aleatoriamente ao reiniciar) estarão usando a nova criptografia.
Se seu roteador "rechavear" para usar a nova criptografia, ele pode ter tráfego menor ou menor estabilidade do que o normal por vários dias após você reiniciar.
Isso é normal, porque seu roteador gerou uma nova identidade.
Seu desempenho deveria ser recuperado após um tempo.</p>
<p>Nós "rechaveamos" a rede duas vezes antes, ao alterar o tipo de assinatura padrão, mas esta é a primeira vez que mudamos o tipo de criptografia padrão. Espero que tudo corra bem, mas estamos começando devagar para ter certeza.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 com melhorias de desempenho</summary></details><p>0.9.48 permite nosso novo protocolo de criptografia de ponta-a-ponta (proposta 144) para a maioria dos serviços.
Adicionamos suporte preliminar para a criptografia de novas mensagens de construção de túnel (proposta 152).
Há melhorias significativas de desempenho em todo o roteador.</p>
<p>Pacotes para Ubuntu Xenial (16.04 LTS) não são mais suportados. Os usuários nessa plataforma devem atualizar para que você possa continuar a receber atualizações I2P.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 permite nova criptografia</summary></details><p>A versão 0.9.47 habilita nosso novo protocolo de criptografia de ponta a ponta (proposta 144) por padrão para alguns serviços. A ferramenta de análise e bloqueio Sybil agora está habilitada por padrão.</p>
<p>Java 8 ou superior agora é necessário. Os pacotes Debian para Wheezy e Stretch, e para Ubuntu Trusty e Precise, não são mais suportados. Os usuários nessas plataformas devem atualizar para que você possa continuar a receber atualizações I2P.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 com correções de falha</summary></details><p>0.9.46 contém melhorias significativas de desempenho na biblioteca de streaming. Concluímos o desenvolvimento da criptografia ECIES (proposta 144) e agora há uma opção para habilitá-la para testes.</p>
<p>Para usuários de Windows apenas:
Essa versão corrige uma vulnerabilidade de escalação de privilégio local
que poderia ser explorada por um usuário local.
Por favor, aplique a atualização o mais breve possível.
Obrigado à Blaze Infosec pela divulgação responsável do problema.</p>
<p>Esta é a última versão a suportar Java 7, pacotes Debian Wheezy e Stretch, e pacotes Ubuntu Precise e Trusty. Os usuários nessas plataformas devem atualizar para receber atualizações futuras do I2P.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 com correções de falha</summary></details><p>0.9.45 contém correções importantes para o modo oculto e o testador de largura de banda. Há uma atualização para o tema escuro do console. Continuamos a trabalhar na melhoria do desempenho e no desenvolvimento de uma nova encriptação de ponta a ponta (proposta 144).</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 com correções de falha</summary></details><p>0.9.44 contém uma correção importante para um problema de negação de serviço no processamento de novos tipos de criptografia de serviços ocultos. Todos os usuários devem atualizar o mais rápido possível.</p>
<p>Esse lançamento contém suporte inicial para uma nova criptografia ponta-a-ponta (proposta 144).
Este é trabalho em andamento e ainda não está pronto para uso.
Há mudanças na pagina inicial do painel, e novos media players HTML5 embutidos no i2psnark.
Correções adicionais para redes IPV6 protegidas por firewall estão incluídas.
Correções para a construção do túnel devem resultar em uma inicialização mais rápida para certos usuários. </p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 com correções de falha</summary></details><p>No lançamento 0.9.43, nos continuamos trabalhando em fortes recursos de segurança, privacidade e melhorias de desempenho.
Nossa implementação da nova especificação leaseset (LS2) está agora completa.
Estamos começando a implementar uma criptografia ponta-a-ponta mais rápida, forte e segura (proposta 144) em um futuro lançamento.
Diversos problemas de detecção de endereços IPv6 foram solucionados, e nisso é claro há diversas outras correções de falha. </p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 com correções de falha</summary></details><p>0.9.42 continua com o trabalho de tornar a I2P mais rápida e viável.
Isso inclui diversas mudanças para acelerar o nosso transporte UDP.
Nós dividimos os arquivos de configuração para permitir um empacotamento mais modular em futuros trabalhos.
Nos continuamos com o trabalho de implementar novas propostas para uma criptografia mais rápida e segura.
E há, é claro, diversas correções de falha.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 com correções de falha</summary></details><p>0.9.41 continua com o trabalho de implementar novas funcionalidade para a proposta 123,
incluindo autenticação entre clientes para leasesets criptografados.
O painel possui uma logo do I2P atualizada e diversos novos ícones.
Atualizamos o instalador do Linux. </p>
<p>A inicialização deve estar mais rápida para plataformas como o Raspberry Pi.
Corrigimos diversos falhas, incluindo alguns erros graves afetando mensagens de baixo nível da rede. </p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 com novos ícones</summary></details><p>0.9.40 inclui suporte para o novo formato de leaseset criptografado.
Nós desativamos o antigo protocolo de transporte NTCP 1.
Há um novo recurso de importação SusiDNS, e um novo mecanismo de filtro automatizado para conexões de entrada. </p>
<p>Nós realizamos diversas melhorias para o instalador nativo do OSX, assim como atualizamos o instalador IzPack.
O trabalho continua em renovar o painel com novos ícones.
Como de praxe, nós corrigimos muitas falhas!</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 com melhorias de desempenho</summary></details><p>0.9.39 inclui mudanças extensas para os novos tipos de base de dados da rede (proposta 123)
Nós empacotamos a extensão i2pcontrol como um aplicativo web para suportar o desenvolvimento de aplicações RPC.
Há numerosas melhorias de desempenho e correções de falha. </p>
<p>Nós removemos os temas clássico e meia-noite para reduzir a carga de manutenção;
usuários prévios desses temas agora verão os temas escuro ou claro.
Também há novos ícones na página inicial, um primeiro passo na atualização do console.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 com o novo instalador passo-a-passo</summary></details><p>A versão 0.9.38 inclui um novo assistente de primeira instalação com um testador de largura de banda.
Nós adicionamos suporte ao formato mais recente de base de dados de GeoIP.
Agora há um novo instalador de perfil do Firefox e um novo instalador nativo para Mac OSX no nosso website.
O trabalho continua para dar suporte ao novo formato de BD de rede "LS2".</p>
<p>Esta versão também contém muitas correções de bugs, incluindo vários problemas com anexos susimail e uma correção para roteadores somente IPv6.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Relatório de Viagem" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P no 35C3</summary></details><p>A equipe I2P esteve praticamente toda presente no 35C3 em Leipzig. Foram realizadas reuniões diárias para revisar o ano passado e abordar nossas metas de desenvolvimento e design para 2019.</p>
<p>A Visão do Projeto e o novo Roteiro podem ser <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">Reveja aqui</a>.</p>
<p>O trabalho continuará no LS2, no Testnet e nas melhorias de usabilidade do nosso site e console. Um plano está em vigor para estar no Tails, Debian e Ubuntu Disco. Ainda precisamos de pessoas para trabalhar no Android e I2P_Bote correções.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 com NTCP2 habilitado</summary></details><p>0.9.37 possibilita um protocolo de transporte mais seguro e rápido chamado NTCP2. </p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>A versão 0.9.36 contém um protocolo de transporte novo e mais seguro chamado NTCP2.
Ele fica desabilitado por padrão, mas você pode habilitá-lo para testes adicionando a <a href="/configadvanced">configuração avançada</a> <tt>i2np.ntcp2.enable=true</tt> e reiniciando.
O NTCP2 estará habilitado no próximo lançamento.</p>
<p>Esse lançamento também contém várias melhorias de desempenho e correções de falha. </p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>Versão 0.9.35 com pastas SusiMail e Assistente de SSL</summary></details><p>A versão 0.9.35 adiciona suporte para pastas no SusiMail, e um novo 'Assistente' de SSL Wizard para a configurar HTTPS no seu site da Web de "Serviço Oculto".
Nós também temos a coleção usual de correções de erros, especialmente no SusiMail.</p>
<p>Nós estamos trabalhando duro em muitas coisas para a versão 0.9.36, incluindo um instalador para OSX e um protocolo de transporte mais rápido e seguro chamado NTCP2. </p>
<p>A I2P estará na HOPE em Nova York, de 20 a 22 de julho. Encontre-nos e diga olá!</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 com correções de falha</summary></details><p>A versão 0.9.34 contém várias correções de bugs!
Ela também inclui melhorias no SusiMail, tratamento de IPv6, e seleção de par de túnel.
Nós adicionamos suporte para os esquemas IGD2 no UPnP.
Há também preparação para mais melhorias que você verá em lançamentos futuros.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 com correções de falha</summary></details><p>A versão 0.9.33 contém um grande número de correções de bugs, incluindo o i2psnark, o i2ptunnel, streaming, e o SusiMail.
Para aqueles que não conseguem acessar os sites de repropagação diretamente, nós agora suportamos vários tipos de proxies para repropagação.
Nós agora definimos limites de taxa por padrão no gerenciador de serviços ocultos.
Para aqueles que executam servidores de alto tráfego, por favor, revisem e ajustem os limites conforme necessário.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown e Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Problemas de segurança encontrados em quase todos os sistemas</summary></details><p>Um problema muito sério foi encontrado em CPUs modernas que são encontradas em quase todos os computadores vendidos em todo o mundo, incluindo celulares. Esses problemas de segurança são chamados de "Kaiser", "Meltdown" e "Spectre".</p>
<p>O whitepaper do KAISER/KPTI pode ser encontrado em <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, o do Meltdown em <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, e o do SPECTRE em <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. A primeira resposta da Intel está listada em <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">resposta da Intel</a>.</p>
<p>É importante para nossos usuários da I2P atualizar seu sistema, contando que atualizações estejam disponíveis. Patches para o Windows 10 estão disponíveis a partir de agora, Windows 7 e 8 virão logo em seguida. Patches para MacOS já estão disponíveis também. Muitos sistemas Linux têm um Kernel mais novo com uma correção incluída disponível também. O mesmo se aplica ao Android, cuja correção de segurança de 2 de janeiro de 2018 inclui um patch para esses problemas.
Por favor, atualize seus sistemas o quanto antes estiver disponível e for possível.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Feliz ano novo! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Ano novo e I2P no 34C3</summary></details><p>Feliz ano novo da equipe do I2P para todos!</p>
<p>Não menos que 7 membros do time da I2P se encontraram no 34C3 em Leipzig de 27 a 30 de dezembro de 2017. Além dos <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">encontros</a> na nossa mesa nós conhecemos vários amigos da I2P por todo o lugar.
Resultados dos encontros já estão publicados em <a href="http://zzz.i2p" target="_blank">zzz.i2p</a>.</p>
<p>Também distribuímos muitos adesivos e demos informações sobre nosso projeto para quem quisesse. Nosso jantar anual I2P foi um sucesso total como um agradecimento a todos os participantes pelo apoio contínuo da I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 com atualizações do painel</summary></details><p>A versão 0.9.32 contém várias correções no console do roteador e aplicações web associadas (livro de endereços, i2psnark, e susimail).
Nós também mudamos a forma como nós lidamos com nomes de host configurados para informações de roteador publicadas, para eliminar alguns ataques de enumeração de rede via DNS.
Nós adicionamos algumas verificações no console para resistir a ataques de revinculação.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 com atualizações do painel</summary></details><p>As mudanças nessa versão são muito mais perceptíveis do que o normal!
Nós renovamos o console do roteador para torná-lo mais fácil de entender,
melhoramos a acessibilidade e suporte cross-browser ,
e organizamos as coisas no geral.
Esse é um primeiro passo em um plano de mais longo prazo para tornar o console do roteador mais amigável ao usuário.
Nós também adicionamos suporte a classificações e comentários de torrents ao i2psnark.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Chamada para tradutores" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>A próxima versão 0.9.31 tem mais strings não traduzidas do que o normal</summary></details><p>Em preparação para a versão 0.9.31, que traz consigo atualizações significativas
à interface de usuário, nós temos uma coleção maior do que o normal de strings
não traduzidas que precisam de atenção. Se você é um tradutor, nós ficaríamos muito felizes
se você pudesse reservar um pouco mais de tempo do que o normal durante esse ciclo de lançamento
para ajustar o ritmo das traduções. Nós disponibilizamos as strings mais cedo
para dar a você três semanas para trabalhas nelas.</p>
<p>Se você não é atualmente um tradutor I2P, agora seria um ótimo momento para se envolver! Por favor, veja o
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">Novo Guia do Tradutor</a>
para obter informações sobre como começar.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 atualizações para Jetty 9</summary></details><p>A versão 0.9.30 contém uma atualização para o Jetty 9 e para o Tomcat 8.
As versões anteriores não têm mais suporte, e não estão disponíveis nos futuros lançamentos Debian Stretch e Ubuntu Zesty.
O roteador migrará o arquivo de configurações jetty.xml para cada website Jetty para a nova configuração do Jetty 9.
Isso deve funcionar para configurações recentes e não modificadas, mas pode não funcionar para configurações modificadas ou muito antigas.
Verifique que seu website Jetty funciona após atualizar, e nos contate no IRC se você precisar de assistência.</p>
<p>Diversos plugins não são compatíveis com o Jetty 9 e precisam ser atualizados.
Os seguintes plugins foram atualizados para funcionar com a 0.9.30, e seu roteador deve atualizá-los após reiniciar:
i2pbote 0.4.6; zzzot 0.15.0.
Os seguintes plugin (com as versões atuais listadas) não funcionarão com a 0.9.30.
Entre em contato com o desenvolvedor apropriado do plugin para o status das novas versões:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>Esta versão também oferece suporte à migração de serviços ocultos DSA-SHA1 antigos (2014 e anteriores) para o tipo de assinatura EdDSA mais seguro. Ver <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> para obter mais informações, incluindo um guia e perguntas frequentes.</p>
<p>Nota: Em plataformas ARM não Android, como o Raspberry Pi, o banco de dados blockfile será atualizado na reinicialização, o que pode levar vários minutos. Por favor, seja paciente.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contém correções de falha</summary></details><p>A versão 0.9.29 contém correções para diversos tickets Trac, incluindo alternativas para mensagens compactadas corrompidas.
Nós agora suportamos NTP sobre IPv6.
Nós adicionamos suporte preliminar ao Docker.
Nós agora traduzimos as páginas de manual.
Nós agora passamos headers Referer same-origin pelo proxy HTTP.
Há mais correções para o Java 9, embora nós ainda não recomendemos o Java 9 para uso geral.</p>
<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="Vulnerabilidade de Segurança do I2P-Bote" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>Vulnerabilidade de Segurança do I2P-Bote</summary></details><p>O I2P-Bote 0.4.5 corrige uma vulnerabilidade de segurança presente em todas as versões anteriores doplug-in I2P-Bote. O aplicativo para Android não foi afetado.</p>
<p>Ao mostrar emails para o usuário, a maioria dos campos estava sendo escapada. Contudo, os nomes de arquivos
dos anexos não eram escapados, e poderiam ser usados para executar código malicioso em um navegador
com JavaScript habilitado. Eles agora estão escapados, e adicionalmente a isso uma Política de Segurança de Conteúdo
foi implementada para todas as páginas.</p>
<p>Todos os usuários do I2P-Bote serão atualizados automaticamente na primeira vez que eles reiniciarem seu roteador
após a versão 0.9.29 da I2P ser lançada na metade de fevereiro. Todavia, por segurança nós recomendamos que você
<a href="http://bote.i2p/install/">siga as instruções na página de instalação</a> para
atualizar manualmente se você planeja usar a I2P ou o I2P-Bote no meio-tempo.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contém correções de falha</summary></details><p>A versão 0.9.28 contém correções para mais de 25 tickets Trac, e atualizações para vários pacotes de software embutidos incluindo o Jetty.
Há correções para a funcionalidade de teste de par IPv6 introduzida no último lançamento.
Nós damos continuidade a melhorias para detectar e bloquear pares que sejam potencialmente maliciosos.
Há correções preliminares para Java 9, embora nós ainda não recomendemos o Java 9 para uso geral.</p>
<p>I2P estará em 33C3, por favor, pare em nossa mesa e nos dê suas ideias sobre como melhorar a rede. Revisaremos nosso roteiro de 2017 e nossas prioridades para 2017 no Congresso.</p>
<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="Vulnerabilidade de Segurança do I2P-Bote" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>Vulnerabilidade de Segurança do I2P-Bote</summary></details><p>O I2P-Bote 0.4.4 corrige uma vulnerabilidade de segurança presente em todas as versões anteriores do plug-in I2P-Bote. O aplicativo para Android não foi afetado.</p>
<p>Uma ausência de proteção contra CSRF significava que se um usuário estava executando o I2P-Bote e então carregava um
site malicioso em um navegador com JavaScript habilitado, o adversário poderia disparar ações
no I2P-Bote em nome do usuário, tais como enviar mensagens. Isso pode ter permitido também
a extração de chaves privadas para endereços I2P-Bote, contudo, nenhuma prova de exploração foi testada
para isso.</p>
<p>Todos os usuários do I2P-Bote serão atualizados automaticamente na primeira vez que eles reiniciarem seu roteador
após a versão 0.9.28 da I2P ser lançada na metade de dezembro. Contudo, por segurança nós recomendamos que você
<a href="http://bote.i2p/install/">siga as instruções na página de instalação</a> para
atualizar manualmente se você planeja usar a I2P ou o I2P-Bote no meio-tempo. Você deveria
também considerar gerar novos endereços I2P-Bote se você navega por sites regularmente com
JavaScript habilitado enquanto executa o I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>Versão 0.9.27 contém correções de erros</summary></details><p>0.9.27 contém algumas correções de erros.
Biblioteca GMP atualizada para aceleração de encriptação, que foi incorporada no lançamento da versão 0.9.26 apenas para novas instalações e compilações Debian, está agora incluída na atualização de rede para a versão 0.9.27.
Existem alguns melhoramentos no transporte de IPv6, teste de peer SSU, e modo ocultado.</p>
<p>Atualizamos uma série de plugins durante <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Verão</a> e seu roteador irá atualizá-los automaticamente após a reinicialização.</p>
<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="Proposta do I2P Stack Exchange" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P é agora um site proposto no Stack Exchange!</summary></details><p>I2P é agora um site proposto no Stack Exchange! Por favor <a href="https://area51.stackexchange.com/proposals/99297/i2p">comprometer-se a usá-lo</a> Assim, a fase beta pode começar.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contém atualizações de criptografia, melhorias no empacotamento Debian e correções de bugs</summary></details><p>0.9.26 contém uma grande atualização para a nossa biblioteca de criptografia nativa, um novo protocolo de assinatura de catálogo de endereços com assinaturas e grandes melhorias para o pacote Debian / Ubuntu.</p>
<p>Para criptografia, nós atualizamos para o GMP 6.0.0, e adicionamos suporte para novos processadores,
o que acelerará as operações de criptografia consideravelmente.
Ainda, nós agora estamos usando funções GMP de tempo constante para prevenir ataques de canal lateral.
Por precaução, as mudanças de GMP estão habilitadas somente para novas instalações e construções Debian/Ubuntu;
nós as incluiremos para atualizações em rede no lançamento da versão 0.9.27.</p>
<p>Para compilações Debian/Ubuntu, adicionamos dependências em vários pacotes, incluindo Jetty 8 e geoip, e removemos o código empacotado equivalente.</p>
<p>Há ainda uma coleção de correção de bugs, incluindo uma correção para um bug de temporizador
que causava instabilidade e degradação de desempenho ao longo do tempo.
Como de costume, nós recomendamos que todos os usuários atualizem para essa versão.
A melhor forma de ajudar a rede e se manter seguro é executar a versão mais recente.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>A versão 0.9.25 contém SAM 3.3, códigos QR, e correções de erros</summary></details><p>A versão 0.9.25 contém uma grande nova versão do SAM, v3.3, para dar suporte a aplicações multi protocolo sofisticadas.
Ela adiciona QR codes para compartilhar endereços de serviços ocultos com os outros,
e imagens "identicon" para distinguir endereços visualmente.</p>
<p>Nós adicionamos uma nova página de configuração de "família do roteador" no console,
para tornar mais fácil declarar que o seu grupo de roteadores é executado por uma única pessoa.
Há várias mudanças para aumentar a capacidade da rede e, assim se espera, melhorar o sucesso de construção de túneis.</p>
<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contém várias correções de bugs e acelerações</summary></details><p>A versão 0.9.24 contém uma nova versão do SAM (v3.2) e várias correções de bugs e melhorias de eficiência.
Note que essa versão é a primeira a requerer Java 7.
Por favor, atualize para o Java 7 ou 8 o mais breve possível.
Seu roteador não atualizará automaticamente se você estiver usando Java 6.</p>
<p>Para prevenir os problemas causados pela antiga biblioteca commons-logging, nós a removemos.
Isso fará com que plugins muito antigos do I2P-Bote (0.2.10 e anterior, assinados por HungryHobo) travem se eles tiverem IMAP habilitado.
A correção recomendada é substituir seu antigo plugin do I2P-Bote pelo atual assinado pelo str4d.
Para mais detalhes, veja <a href="http://bote.i2p/news/0.4.3">esta publicação</a>.</p>
<p>Nós tivemos um ótimo <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">Congresso 32C3</a> e estamos fazendo um bom progresso nos nossos planos de projeto de 2016.
O Echelon deu uma palestra sobre a história da I2P e o status atual, e seus slides estão <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">aqui</a> (pdf).
O Str4d participou do <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> e deu uma palestra sobre nossa migração de criptografia.
Seus slides estão <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">aqui</a> (pdf).</p>
<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contém uma variedade de correções de bugs, e algumas pequenas melhorias no I2PSnark</summary></details><p>Olá, I2P! Este é o primeiro lançamento assinado por mim (str4d), depois de 49 lançamentos
assinados pelo zzz. Esse é um teste importante da nossa redundância para todas as coisas,
incluindo pessoas.</p>
<p><b>Limpeza</b></p>
<p>A minha chave de assinatura esteve em atualizações do roteador por mais de dois anos (desde a versão 0.9.9), então
se você está em uma versão recente da I2P essa atualização deve ser tão fácil quanto
qualquer outra. Todavia, se você estiver executando uma versão mais antiga do que a 0.9.9, você
precisará primeiro atualizar manualmente para uma versão mais recente. Arquivos de atualização para versões
recentes podem ser baixados
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">aqui</a>,
e instruções de como atualizar manualmente são providenciadas
<a href="http://i2p-projekt.i2p/en/download#update">aqui</a>. Uma vez que você tenha atualizado
manualmente, seu roteador então encontrará e baixará a atualização 0.9.23 como de costume.</p>
<p>Se você instalou o I2P através de um gerenciador de pacotes, você não é afetado pela alteração e pode atualizar como de costume.</p>
<p><b>Detalhes da atualização</b></p>
<p>A migração de informações de roteador para novas e mais fortes assinaturas Ed25519 está indo bem,
com pelo menos metade da rede já estimada a ter rechaveado. Esse
lançamento acelera o processo de rechaveamento. Para reduzir a agitação na rede, seu roteador
terá uma pequena probabilidade de converter para Ed25519 a cada reinício. Quando ele
rechavear, espere ver uso de banda reduzido por alguns dias enquanto ele se
reintegra à rede com sua nova identidade.</p>
<p>Note que essa será a última versão a suportar Java 6. Por favor, atualize para
o Java 7 ou 8 o mais breve possível. Nós já estamos trabalhando em tornar a I2P compatível
com o futuro Java 9, e um pouco desse trabalho está nesse lançamento.</p>
<p>Também fizemos algumas pequenas melhorias no I2PSnark e adicionamos uma nova página noconsole do roteador para visualizar notícias mais antigas.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 com correções de bugs e inicia a migração Ed25519</summary></details><p>A versão 0.9.22 contém correções para o i2psnark ficando travado antes da finalização, e inicia a migração das informações de roteador para novas e mais fortes assinaturas Ed25519.
Para reduzir a agitação na rede, seu roteador terá uma pequena probabilidade de converter para Ed25519 a cada reinício.
Quando ele rechavear, espere ver uso de banda mais baixo por alguns dias enquanto ele se reintegra à rede com sua nova identidade.
Se tudo ocorrer bem, nós aceleraremos o processo de rechaveamento no próximo lançamento.</p>
<p>A I2PCon Toronto foi um grande sucesso! Todas as apresentações e vídeos estão listados na <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">Página I2PCon</a>.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>Versão 0.9.21 lançada com melhorias de desempenho e correções de falhas.</summary></details><p>A versão 0.9.21 contém diversas modificações que adicionam capacidade a rede, aumentam a eficiência das inundações,
e usam a banda de maneira mais eficiente.
Nós migramos os túneis clientes compartilhados para assinaturas ECDSA e acrescentamos um plano B
usando a nova capacidade "multisessão" para aqueles sites que não suportam ECDSA.</p>
<p>Os palestrantes e a programação da I2PCon em Toronto 2015 foram anunciados.
Dê uma olhada na <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">página da I2PCon</a>para mais detalhes.
Reserve seu assento no <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466"> Eventbrite I2PCon</a>.</p>
<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="Palestrantes e programação da I2PCon Toronto anunciados." href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>Palestrantes e programação da I2PCon Toronto 2015 anunciados. </summary></details><p>Os palestrantes e a programação da I2PCon em Toronto 2015 foram anunciados.
Dê uma olhada na <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">página da I2PCon</a>para mais detalhes.
Reserve seu assento no <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466"> Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -1,38 +1,420 @@
<div>
<header title="Ştiri I2P">Ştiri şi actualizări de router</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<header title="Ştiri I2P">Ştiri şi actualizări de router</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Postări recente pe blog" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Eliberat" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 cu remedieri de erori</summary></details><p>0.9.44 conține o soluție importantă pentru o problemă de refuz a serviciului în gestionarea serviciilor ascunse de noi tipuri de criptare.
Toți utilizatorii ar trebui să se actualizeze cât mai curând posibil.</p>
<p>Versiunea include suportul inițial pentru noua criptare end-to-end (propunerea 144).
Lucrările continuă pentru acest proiect și încă nu este gata de utilizare.
Există modificări la pagina principală a consolei și la noi playere HTML5 integrate în i2psnark.
Sunt incluse soluții suplimentare pentru rețelele IPv6 firewalled.
Corecțiile de construire a tunelului ar trebui să conducă la o pornire mai rapidă pentru unii utilizatori.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Eliberat" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 cu remedieri de erori</summary></details><p>În versiunea 0.9.43, continuăm să lucrăm la caracteristici mai puternice de securitate și confidențialitate și îmbunătățiri ale performanței.
Implementarea noastră a noului caiet de sarcini (LS2) este acum completă.
Începem implementarea noastră pentru o criptare end-to-end mai puternică și mai rapidă (propunerea 144) pentru o versiune viitoare.
Mai multe probleme de detectare a adreselor IPv6 au fost remediate, și există, desigur, câteva alte remedieri ale erorilor.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Lansat " href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 cu remedierea erorilor </summary></details><p>0.9.42 continuă activitatea pentru ca I2P să fie mai rapid și mai fiabil.
Acesta include mai multe modificări pentru a accelera transportul nostru UDP.
Am împărțit fișierele de configurare pentru a permite lucrările viitoare pentru ambalaje mai modulare.
Continuăm munca pentru implementarea de noi propuneri pentru o criptare mai rapidă și mai sigură.
Există, de asemenea, o mulțime de remedieri de erori.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Lansat" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 remedierea erorilor </summary></details><p>0.9.41 continuă lucrările pentru implementarea noilor funcții pentru propunerea 123,
inclusiv autentificarea per client pentru închirieri criptate.
Consola are un logo I2P actualizat și câteva pictograme noi.
Am actualizat instalatorul Linux.</p>
<p>Pornirea ar trebui să fie mai rapidă pe platforme precum Raspberry Pi.
Am rezolvat mai multe bug-uri, inclusiv unele grave care afectează mesaje de rețea la nivel scăzut.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Lansat" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 cu pictograme noi</summary></details><p>0.9.40 include suport pentru noul format de închiriere criptat.
Am dezactivat vechiul protocol de transport NTCP 1.
Există o nouă caracteristică de import SusiDNS și un nou mecanism de filtrare scriptic pentru conexiunile primite.</p>
<p>Am adus o mulțime de îmbunătățiri la instalatorul autohton OSX și am actualizat și instalatorul IzPack.
Lucrarea continuă la reîmprospătarea consolei cu pictograme noi.
Ca de obicei, am rezolvat și multe bug-uri!</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Lansată" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 cu îmbunătățiri de performanță</summary></details><p>
0.9.39 include schimbări extensive pentru noile tipuri de baze de date de rețea (propunerea 123).
Am legat pluginul i2pcontrol ca un webapp pentru a sprijini dezvoltarea aplicațiilor.
Există numeroase îmbunătățiri de performanță și corecții de erori.</p>
<p>Am eliminat temele midnight și clasic pentru a reduce povara întreținerii;
utilizatorii anteriori ai acestor teme vor vedea acum tema întunecată sau luminoasă.
Există și noi pictograme pentru pagina de pornire, un prim pas în actualizarea consolei.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Lansată" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 cu un nou asistent de configurare</summary></details><p>0.9.38 include un nou asistent de configurare la prima instalare cu un tester pentru lățimea de bandă.
Am adăugat suport pentru cel mai recent format de bază de date GeoIP.
Există un nou program de instalare a profilului Firefox și un nou instalator Mac OSX nativ pe site-ul nostru.
Lucrul continuă la sprijinirea noului format netdb "LS2".</p>
<p>Această versiune conține, de asemenea, o mulțime de corecții de erori, inclusiv câteva probleme cu atașamentele susimail și o remediere pentru routerele numai cu IPv6.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>Echipa I2P a participat în cea mai mare parte la 35C3 la Leipzig.
Au avut loc întâlniri zilnice de revizuire a anului trecut și pentru acoperirea obiectivelor noastre de dezvoltare și proiectare pentru anul 2019.</p>
<p>Proiectul Vision și Noua foaie de parcurs pot fi <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">revizuite aici</a>.</p>
<p>Lucrările vor continua la LS2, pe testnet și pe îmbunătățiri de utilizare a site-ului și consolei noastre.
Un plan este disponibil pentru a fi în Tails, Debian și Distribuția Ubuntu. Încă mai avem nevoie de oameni pentru a lucra la corecțiile pentru Android și I2P_Bote.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Lansată" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 cu NTCP2 activat</summary></details><p>0.9.37 permite un protocol de transport mai rapid și mai sigur, denumit NTCP2.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Lansată" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 cu NTCP2 și corecții de erori</summary></details><p>0.9.36 conține un nou protocol de transport mai sigur numit NTCP2.
Este dezactivat în mod prestabilit, dar este posibil să îl activați pentru testare adăugând <a href="/configadvanced">configurație avansată</a><tt>i2np.ntcp2.enable=true</tt> și repornind.
NTCP2 va fi disponibil în următoarea versiune.</p>
<p>Această versiune conține, de asemenea, mai multe îmbunătățiri de performanță și corecții de erori.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Lansată" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 cu dosare SusiMail și Expert SSL</summary></details><p>0.9.35 adaugă suport pentru dosare în SusiMail și un nou expert SSL pentru configurarea HTTPS pe site-ul dvs. de servicii ascunse.
De asemenea, avem colecția uzuală pentru remedierea erorilor, în special în SusiMail.</p>
<p>Lucram din greu la mai multe lucruri pentru 0.9.36, incluzând un nou program de instalare OSX și un protocol de transport mai rapid și mai sigur, numit NTCP2.</p>
<p>I2P va fi la HOPE în New York City, 20-22 iulie. Găsiți-ne și salutați-ne!</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Lansată" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 cu remedierea erorilor</summary></details><p>0.9.34 conține o mulțime de remedieri a erorilor!
De asemenea, are îmbunătățiri pentru SusiMail, manipularea IPv6 și selecția peer-tunel.
Adăugăm suport pentru schemele IGD2 în UPnP.
Există, de asemenea, pregătiri pentru mai multe îmbunătățiri pe care le veți vedea în versiunile viitoare.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Lansată" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 cu remedierea erorilor</summary></details><p>0.9.33 conține un număr mare de remediere a erorilor, incluzând i2psnark, i2ptunnel, streaming și SusiMail.
Pentru cei care nu pot accesa direct site-urile de reseed, suportăm acum mai multe tipuri de proxy-uri pentru reseeding.
Acum setăm limitele ratei în mod implicit în managerul de servicii ascunse.
Pentru cei care rulează servere cu trafic ridicat, vă rugăm să consultați și să ajustați limitele după cum este necesar.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown și Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Probleme de securitate găsite în aproape toate sistemele</summary></details><p>O problemă foarte serioasă a fost găsită în procesoarele moderne care se găsesc în aproape toate calculatoarele vândute la nivel mondial, inclusiv pe cele mobile. Aceste probleme de securitate sunt numite "Kaiser", "Meltdown", și "Spectre".</p>
<p>Documentaţia pentru KAISER/KPTI poate fi găsită sub <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown sub <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, și SPECTRE sub <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Primul raspuns Intel este listat sub <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>Este important ca utilizatorii noștri I2P să actualizeze sistemul, atâta timp cât sunt disponibile actualizări. Patch-uri Windows 10 sunt disponibile de acum încolo, Windows 7 și 8 va urma în curând. Patch-urile MacOS sunt deja disponibile, de asemenea. O mulțime de sisteme Linux au un nou Kernel cu o soluție disponibilă. Același lucru este valabil și pentru Android, care include un patch de securitate din 2 ianuarie 2018, pentru aceste probleme.
Actualizați-vă sistemele cât mai curând posibil.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="La mulţi ani! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>An nou și I2P la 34C3</summary></details><p>An nou fericit tuturor din partea echipei I2P!</p>
<p>Nu mai puțin de 7 membri ai echipei I2P s-au întâlnit la 34C3 din Leipzig de la 27 până la 30 decembrie 2017. În afară de <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> la masa noastră am întâlnit mulți prieteni ai I2P de peste tot.
Rezultatele întâlnirilor sunt postate deja pe <a href="http://zzz.i2p" target="_blank">zzz.i2p</a>.</p>
<p>De asemenea, am făcut o mulțime de autocolante și am dat informații despre proiectul nostru oricui a cerut.
Cina noastră anuală oferită de I2P a fost un succes deplin, ca o mulțumire tuturor participanților pentru sprijinul permanent acordat la I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Lansată" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 cu actualizări ale consolei</summary></details><p>0.9.32 conține un număr de remedii în consola routerului și în aplicațiile web asociate (addressbook, i2psnark și susimail).
De asemenea, am schimbat modul în care gestionăm numele de gazdă configurat pentru informațiile publicate despre router, pentru a elimina unele atacuri de enumerare a rețelei prin DNS.
Am adăugat câteva verificări în consola pentru a rezista atacurilor de reconectare.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Lansată" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 cu actualizări ale consolei</summary></details><p>Modificările din această versiune sunt mult mai vizibile decât de obicei!
Am reînnoit consola de router pentru a face mai ușor de înțeles,
îmbunătățirea accesibilității și a suportului de tip cross-browser,
și, în general, lucrurile s-au ordonat.
Acesta este primul pas într-un plan pe termen lung pentru a face consola router-ului mai ușor de utilizat.
De asemenea, am adăugat rating pentru torrent și comentarii de sprijin pentru i2psnark.</p>
<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Apel pentru traducători" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>Versiunea 0.9.31, care urmează, are mai multe șiruri de caractere netraduse decât de obicei</summary></details><p>În pregătirea pentru lansarea versiunii 0.9.31, care aduce cu ea actualizări semnificative
la interfața cu utilizatorul, avem o colecție mai mare decât cea normală de siruri de caractere netraduse

View File

@ -1,8 +1,385 @@
<div>
<header title="Новости I2P">Новостной канал и обновления маршрутизатора</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<header title="Новости I2P">Новостной канал и обновления маршрутизатора</header><article id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a" title="Вышла версия 2.9.0" href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released" author="idk" published="2025-06-02T19:00:00Z" updated="2025-06-02T19:00:00Z"><details><summary>Релиз I2P 2.9.0</summary></details><p>I2P 2.9.0 — это релиз с исправлением ошибок и небольшим количеством новых функций.</p>
<p>Улучшена производительности системы i2ptunnel за счёт оптимизации использования потоков.
В NTCP2 улучшена защита от зондирующих атак.
Система уведомлений интегрирована в большее количество приложений, чтобы нагляднее отображать статусы в I2PSnark и других приложениях.
Исправлена автоматическая регистрация флудфилда.
Пользователи могут заметить повышенное использование ресурсов при работе в качестве floodfill.
Если этот режим сильно нагружает систему, floodfill можно отключить на странице /config.</p>
<p>В консоли доступна новая функция — глобальная карта, которая показывает местоположение маршрутизаторов в вашем представлении netDb.
Это узлы, которые помогают вашему маршрутизатору строить туннели и предоставлять анонимную связность сети.</p>
<p>Продолжаются работы по внедрению протокола Datagram2, постквантовой криптографии и автоматической подстройки пропускной способности для туннелей.
Через два релиза, начиная с версии 2.11.0, для I2P потребуется Java 17.</p>
<p>Как и всегда, мы рекомендуем вам обновиться.
Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
</article><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="Вышла 2.8.2" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>Релиз I2P 2.8.2</summary></details><p>В 2.8.2 исправлена проблема, приводящая к ошибкам SHA256, которая появилась в версии 2.8.1.
Эта проблема проявлялась преимущественно у высокоскоростных маршрутизаторов.</p>
<p>Как и всегда, мы рекомендуем вам обновиться.
Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="Вышла 2.8.1" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>Релиз I2P 2.8.1</summary></details><p>В версии 2.8.1 исправлен доступ к локальным сайтам, которые не работали в 2.8.0. Мы добавили всплывающие уведомления в несколько приложений в консоли, чтобы выделять сообщения приложений.
Мы исправили ошибку при тестировании туннеля, которая могла влиять на его стабильность.
В адресной книге теперь есть новая вкладка «Последние», на которой отображаются самые новые имена хостов, добавленные из ваших подписок.
Также была обновлена темная тема.</p>
<p>Мы исправили установщик, который ранее не работал на Java 21 или выше.
Мы также исправили установку в каталоги с пробелами в Linux.
Для тех, кто использует Docker, мы обновили устаревшие контейнеры и библиотеки внутри контейнера.</p>
<p>Как и всегда, мы рекомендуем вам обновиться.
Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Проблемы доступа к локальным сайтам в версии 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 баг с локальным доступом</summary></details><p>В версии 2.8.0 переход на локальный сайт (по имени хоста или b32) завершится ошибкой.
Обходным путем является использование localhost и порта сервера, обычно 7658, для доступа на сайт напрямую (вне I2P).
Например, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
Приносим свои извинения за возникшую проблему и работаем над ее устранением.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="Релиз I2P 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>Релиз I2P 2.8.0</summary></details><p>Этот релиз улучшает I2P, благодаря исправлениям ошибкок, удалению неиспользуемого кода и повышению стабильности сети.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>Как и всегда, мы рекомендуем вам обновиться.
Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="Релиз I2P 2.7.0" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>Релиз I2P 2.7.0</summary></details><p>В этом релизе, I2P 2.7.0, продолжена работа над исправлением ошибок, улучшением производительности и добавлением новых возможностей.</p>
<p>Улучшен доступ к информации из консоли и приложений.
Исправлены проблемы в I2PSnark и поиске в SusiMail.
Поиск по netDB, встроенный в консоль маршрутизатора, стал более интуитивным и полезеным.
Незначительные улучшения в отображение диагностической информации в расширенном режиме.
</p>
<p>Также были исправлены ошибки для улучшения совместимости внутри сети.
Решена проблема с публикацией контактных данных адресатов (LeaseSets), что повышает надежность основных скрытых сервисов.
I2PSnark больше не меняет infohash, если пользователь меняет только трекеры в существующем торренте.
Это предотвращает ненужное дублирование торрентов.
За это изменение мы благодарим нового участника проекта.
Исправлен конфликт при обработке опции потоковой библиотеки, для улучшения совместимости с другими реализациями I2P.
</p>
<p>Как и всегда, мы рекомендуем вам обновиться.
Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="Релиз I2P 2.6.1" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>Релиз I2P 2.6.1</summary></details><p>Версия I2P 2.6.1 выпущена для исправления ошибки пользовательского интерфейса в приложении управления скрытыми сервисами.
Эта ошибка приводила к неработающей прокрутке (скроллингу), что скрывало часть настроек.
</p>
<p>Как и всегда, мы рекомендуем вам обновиться.
Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>В этом релизе, I2P 2.6.0, продолжена работа над исправлением ошибок, добавлением новых возможностей и улучшением сетевой стабильности.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>Как и всегда, мы рекомендуем вам обновиться.
Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>Как и всегда, мы рекомендуем вам обновиться.
Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>Как и всегда, мы рекомендуем вам обновиться.
Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="Новый релиз I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>Дополнительные улучшения приложений, аудит стратегии изоляции NetDB</summary></details><p>Этот выпуск, I2P 2.5.0, содержит больше улучшений, ориентированных на пользователя, чем выпуск 2.4.0, который был сосредоточен на реализации стратегии изоляции NetDB.</p>
<p>В I2PSnark добавлены новые функции, например, возможность поиска по торрентам. Исправлены ошибки для улучшения совместимости с другими I2P-торрент-клиентами, такими как BiglyBT и qBittorrent. Мы хотели бы поблагодарить всех разработчиков, которые работали с libtorrent и qBittorrent, чтобы включить и улучшить их поддержку I2P. В SusiMail также добавлены новые функции, включая поддержку форматирования Markdown в письмах и возможность перетаскивать вложения в письма. Туннели, созданные с помощью менеджера Hidden Services, теперь поддерживают "Keepalive", что повышает производительность и совместимость с веб-технологиями, позволяя создавать более сложные I2P-сайты.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>В этом релизе были внесены некоторые улучшения в процесс выпуска наших последующих дистрибутивов для Android и Windows. Это должно привести к улучшению доставки и доступности этих последующих продуктов.</p>
<p>Как и всегда, мы рекомендуем вам обновиться.
Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="Релиз I2P 2.4.0 с улучшениями в области безопасности перегрузок и NetDB" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>Релиз I2P 2.4.0 с улучшениями в области безопасности перегрузок и NetDB</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Также включен ряд исправлений и улучшений в приложениях I2PSnark и SusiMail.</p>
<p>Как и всегда, мы рекомендуем вам обновиться.
Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>Как и всегда, мы рекомендуем вам обновиться.
Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>Как и всегда, мы рекомендуем вам обновиться.
Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>Как и всегда, мы рекомендуем вам обновиться.
Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="Вышла версия 2.1.0" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 с многочисленными изменениями в SSU2</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="Новый выходной прокси exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>Новый выходной прокси</summary></details><p>I2P "выходные прокси" (ноды выхода) могут быть использованы для доступа к интернет через
ваш HTTP прокси тоннель.
Как утрверждено на нашем <a href="http://i2p-projekt.i2p/en/meetings/314">месячном собрании</a>,
<b>exit.stormycloud.i2p</b> теперь наш новый официальный рекомендованный выходной прокси на замену давно сдохшего <b>false.i2p</b>.
Для дополнительной информации на StormyCloud <a href="http://stormycloud.i2p/">организации</a>,
<a href="http://stormycloud.i2p/outproxy.html">выходной прокси</a>,
и <a href="http://stormycloud.i2p/tos.html">условия использования</a>,
смотри на <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="Вышла версия 1.8.0" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 с исправлением ошибок</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="Вышла версия 1.7.0" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 с улучшенной производительностью и повышенной надежностью</summary></details><p>Версия 1.7.0 содержит ряд улучшений в части производительности и надежности</p>
<p>Теперь в системном лотке появляются всплывающие сообщения для платформ, поддерживающих его. В i2psnark есть новый редактор торрентов. Транспорт NTCP2 теперь реже, чем раньше, использует центральный процессор.</p>
<p>Давно устаревшего интерфейса BOB не будет в новой версии. Он продолжит работать в уже установленных приложениях, за исключением пакетов Debian. Все, кто продолжает пользоваться BOB, должны попросить разработчиков конвертировать BOB в протокол SAMv3.</p>
<p>Мы в курсе, что с момента выпуска версии 1.6.1 надежность сети неуклонно понижалась.
Мы узнали о проблеме вскоре после выпуска версии, но нам потребовалось почти два месяца, чтобы выявить причину неисправности.
В конце концов мы поняли, что причина — в ошибке в i2pd 2.40.0,
и эта ошибка будет исправлена в версии 2.41.0, которая выйдет примерно в то же время, что и нынешняя версия.
Попутно мы внесли несколько изменений в Java I2P, чтобы повысить
надежность поиска и хранения сетевых баз данных и избежать неэффективных одноранговых узлов при выборе узлов в туннеле.
Эти меры должны укрепить надежность сети при наличии неисправных или вредоносных маршрутизаторов.
Кроме того, мы начинаем совместную программу по тестированию предварительных версий маршрутизаторов i2pd и Java I2P
в изолированной тестовой сети, чтобы у нас была возможность выявить больше проблем до выхода версии, а не после него.</p>
<p>Что еще нового? Мы продолжаем улучшать наш UDP-транспорт SSU2 (предложение 159) и уже начали его использовать. SSU2 станет эффективнее и безопаснее. Это позволит нам отказаться от невероятного медленного шифрования ElGamal, завершив полное обновление криптографии, которое началось около 9 лет назад. Мы надеемся вскоре начать совместное с i2pd тестирование и запустить обновления в Cети в этом году.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="Вышла версия 1.6.0" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>Версия 1.6.0 позволяет создавать новые типы пакетов для построения туннелей.</summary></details><p>Эта версия — последний шаг на пути к запуску двух основных обновлений протоколов, разработанных в 2021 году.
Переход к шифрованию X25519 для маршрутизаторов ускорен, и мы ожидаем, что почти все маршрутизаторы будут перезапущены к концу года.
Для значительного сокращения пропускной способности используются небольшие пакеты для построения туннелей.</p>
<p>Мы добавили панель выбора темы в мастер установки.
Мы улучшили производительность SSU и исправили проблему с одноранговыми тестовыми сообщениями SSU.
Туннельная сборка фильтра Bloom была скорректирована для того, чтобы снизить нагрузку на память.
Мы осуществляем расширенную поддержку плагинов, не связанных с Java .</p>
<p>Помимо этого, мы продвинулись в разработке нашего нового UDP-транспорта SSU2 и надеемся начать его внедрение в начале следующего года.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="Вышла версия 1.5.0" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 с новыми типами пакетов для построения туннелей</summary></details><p>Да, вам не привиделось — после 9 лет разработки 0.9.x мы переходим сразу с 0.9.50 на 1.5.0.
Это не привело к значительному изменению API, как и не означает, что разработка завершена.
Увеличение версии всего лишь отмечает нашу работу в предоставлении анонимности и безопасности нашим пользователям за почти 20 лет.</p>
<p>В этом релизе была завершена работа над меньшими по размеру пакетами для построения туннелей, чтобы уменьшить требования к пропускной способности сети.
Мы продолжаем перевод маршрутизаторов на шифрование X25519.
Как и всегда, в новой версии исправлены ошибки и увеличена производительности.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Уязвимость в MuWire Desktop" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Уязвимость в Muwire Desktop</summary></details><p>В программе MuWire Desktop была обнаружена проблема безопасности.
Проблема не затрагивает модуль I2P-консоли, а также не имеет общего с ранее анонсированной проблемой в модуле.
Если вы используете программу MuWire Desktop, вам следует срочно <a href="http://muwire.i2p/">обновиться до версии 0.8.8</a>.</p>
<p>Детали проблемы будут опубликованы на сайте <a href="http://muwire.i2p/security.html">muwire.i2p</a> 15 июля 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Уязвимость в модуле MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Уязвимость в модуле Muwire</summary></details><p>В модуле MuWire была обнаружена проблема безопасности.
Она не затрагивает десктопную программу.
Если вы используете модуль MuWire для I2P-консоли, срочно <a href="/configplugins">обновитесь до версии 0.8.7-b1</a>.</p>
<p>Подробности и информацию об уязвимости см. на <a href="http://muwire.i2p/security.html">muwire.i2p</a>.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="Вышла версия 0.9.50" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 с исправлением ошибок IPv6</summary></details><p>0.9.50 продолжает переход на ECIES-X25519 для ключей шифрования маршрутизаторов.
Мы включили поддержку DNS over HTTPS для системы начальной загрузки узлов, чтобы защитить пользователей от пассивного наблюдения за DNS-запросами.
В этой версии исправлено большое количество ошибок и улучшена поддержка IPv6 и UPnP.</p>
<p>Наконец-то была исправлена давняя ошибка с повреждением файлов SusiMail.
Изменения в систему ограничения пропускной способности должны улучшить производительность сетевых туннелей.
Также отметим улучшения наших Docker-контейнеров.
Мы улучшили защиту для потенциально вредоносных и проблемных маршрутизаторов нашей сети I2P.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="Версия 0.9.49" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 с исправлениями SSU и ускорением шифрования</summary></details><p>В 0.9.49 продолжены работы по улучшению скорости и безопасности I2P.
Мы сделали ряд улучшений и исправлений в работе транспорта SSU (UDP), что должно ускорить его работу.
С этим релизом также начинается миграция на новый, более быстрый протокол шифрования ECIES-X25519 для транзитных маршрутизаторов
(для оконечных узлов этот протокол уже был активирован несколько релизов назад).
Мы работали над спецификацией и протоколом нового шифрования несколько лет, и наконец приближаемся к его внедрению. Процесс полной миграции на новый протокол будет длиться несколько релизов.
</p>
<p>Чтобы уменьшить возможное негативное влияние на сеть, этот релиз активирует новое шифрование только для новых установок и очень малой части существующих (решение об активации будет выбрано случайно при перезапуске маршрутизатора).
Если ваш маршрутизатор активирует новое шифрование, вы будете получать меньше трафика, чем обычно, а работа сети может быть не полностью стабильной в течение нескольких дней после запуска.
Это нормально — процесс активации подразумевает создание нового идентификатора маршрутизатора.
Производительность и стабильность вернётся в норму через какое-то время.</p>
<p>Ранее в сети уже дважды менялись идентификаторы маршрутизаторов, когда происходила смена типа подписи на новый,
но на этот раз мы впервые меняем тип шифрования.
Всё должно пройти гладко, но мы страхуемся на всякий случай.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="Версия 0.9.48" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 с улучшением производительности</summary></details><p>Версия 0.9.48 активирует наш новый протокол оконечного (end-to-end) шифрования (предложение 144) для большинства сервисов.
Мы добавили начальную поддержку шифрования сообщений построения новых туннелей (предложение 152).
Новая версия маршрутизатора получила заметное улучшение производительности.</p>
<p>Пакеты для Ubuntu Xenial (16.04 LTS) более не поддерживаются.
Пользователи этой платформы должны обновиться до актуальной версии ОС, чтобы продолжить получать обновления I2P.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="Версия 0.9.47" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 с новым шифрованием</summary></details><p>Версия 0.9.47 включает новый протокол сквозного (end-to-end) шифрования (предложение 144) по умолчанию для некоторых сервисов.
Утилита анализа и блокировки Сивилл-нод (Sybil) также активирована по умолчанию.</p>
<p>Отныне требуется Java 8 и новее.
Пакеты для Debian Wheezy и Stretch, Ubuntu Trusty и Precise больше не поддерживаются.
Пользователи перечисленных платформ должны обновить дистрибутив, чтобы продолжить получать обновления I2P.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="Версия 0.9.46" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 с исправлением ошибок</summary></details><p>0.9.46 содержит значительное увеличение производительности библиотеки потоковой передачи данных.
Мы закончили разработку шифрования ECIES (предложение 144), теперь в меню есть опция для его активации с целью тестирования.</p>
<p>Только для пользователей Windows:
Эта версия исправляет уязвимость локального повышения привилегий,
которое могло быть использовано из-под учётной записи локального пользователя.
Пожалуйста, обновитесь до этой версии как можно быстрее.
Благодарим Blaze Infosec за своевременно предоставленную информацию по этому вопросу.</p>
<p>Это последняя версия, поддерживающая Java 7, пакеты Debian Wheezy и Stretch, а также пакеты Ubuntu Precise и Trusty.
Пользователи указанных платформ должны обновить их для получения будущих обновлений I2P.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="Выпуск 0.9.45" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 с исправленными ошибками</summary></details><p>0.9.45 содержит важные исправления для скрытого режима и теста ширины канала. В консоль добавлена тёмная тема. Мы продолжаем работать над улучшением производительности и разрабатываем новый алгоритм шифрования типа точка-точка (предложение 144)</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="Вышла версия 0.9.44" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 с исправлением ошибок</summary></details><p>0.9.44 содержит важное исправление проблемы отказа в обслуживании в коде обработки новых типов шифрования скрытых сервисов.
Пользователям рекомендуется как можно скорее установить это обновление.</p>
<p>Релиз содержит первоначальную поддержку нового сквозного шифрования (предложение 144).
Работа продолжится в этом проекте, и оно ещё не готово к использованию.
Есть изменения в домашней странице консоли и новом встроенном HTML5 медиаплеере в i2psnark.
Включены дополнительные исправления для файервола IPv6 сети.
Исправления в построении тоннелей могут ускорить запуск для некоторых пользователей.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="Вышла версия 0.9.43" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 с исправлением ошибок </summary></details><p> В релизе 0.9.43 мы продолжаем работу над усилением функций безопасности и конфиденциальности и улучшением производительности.
Реализация улучшений для системы получения контактных данных адресатов или (LeaseSet) (LS2) завершена.
Мы начинаем реализацию более мощного и быстрого сквозного шифрования (предложение 144) для будущего выпуска.
Исправлено несколько проблем с обнаружением адресов IPv6, и, конечно, несколько других ошибок.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="Вышла версия 0.9.42" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 с исправлением ошибок </summary></details><p>0.9.42 продолжает работу по ускорению и повышению надежности I2P.
Он включает в себя несколько изменений для ускорения UDP-транспортировки.
Мы разделили файлы конфигурации, чтобы в будущем можно было работать с более модульной упаковкой.
Мы продолжаем работу по внедрению новых предложений для более быстрого и безопасного шифрования.
Также исправлено множество ошибок.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Выпущена" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 с исправлением ошибок </summary></details><p>0.9.41 продолжает работу по внедрению новых функций для предложения 123,
включая аутентификацию для каждого клиента для зашифрованных арендных наборов.
Консоль получила обновленный логотип I2P и несколько новых значков.
Мы обновили установщик Linux.</p>
<p>Запуск должен быть быстрее на таких платформах, как Raspberry Pi.
Мы исправили несколько ошибок, в том числе несколько серьезных, влияющих на низкоуровневые сетевые сообщения.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="Вышла версия 0.9.40" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 с новыми иконками</summary></details><p>В 0.9.40 включена поддержка нового зашифрованного формата арендного набора.
Мы отключили старый транспортный протокол NTCP 1.
Есть новая функция импорта SusiDNS и новый механизм фильтрации сценариев для входящих соединений.</p>
<p>Мы внесли много улучшений в собственный установщик OSX, а также обновили установщик IzPack.
Продолжается работа по обновлению консоли новыми значками.
Как обычно, мы исправили много ошибок!</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="Версия 0.9.39" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 с улучшениями производительности</summary></details><p>0.9.39 содержит значительные изменения для новых типов сетевых баз данных (предложение 123).
Мы добавили плагин i2pcontrol в качестве веб-приложения для поддержки разработки приложений, использующих RPC.
Также было сделано множество улучшений производительности и исправлений ошибок.</p>
<p>Были удалены темы оформления "Полночь" и "Классическая", чтобы облегчить поддержку кода.
Пользователи этих тем теперь увидят темную или светлую тему.
Также добавлены новые значки домашней страницы — первый шаг для обновления консоли.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="Версия 0.9.38" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 с новым мастером начальной настройки</summary></details><p>В 0.9.38 добавлен новый мастер начальной настройки, с тестированием пропускной способности.
Также добавлена поддержка последнего формата базы данных GeoIP.
На нашем сайте выложен новый установщик профиля Firefox, и новый, нативный установщик программы для Mac OSX.
Мы продолжаем работу над новым форматом netdb — LS2.</p>
<p>В этом выпуске были устранены различные ошибки, включая проблемы с приложенными файлами в susimail и исправление для маршрутизаторов, имеющих связность только по IPv6.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="Отчет о поездке на 35C3" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P на 35C3</summary></details><p>Команда I2P присутствовала практически в полном составе на конференции Chaos Communication Congress 35C3 в Лейпциге, Германия.
Были проведены ежедневные собрания для обсуждения прошедшего года и планов разработки в 2019 году.</p>
<p>Информация о новом плане работ <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">доступна по ссылке</a>.</p>
<p>Продолжается работа над LS2, Testnet и улучшением удобства использования веб-сайта и консоли маршрутизатора.
Запланировано добавление I2P в дистрибутивы Tails, Debian и Ubuntu Disco. Мы всё ещё ищем разработчиков для работы над I2P-Bote и версией маршрутизатора для Android.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="Версия 0.9.37" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 со включённым NTCP2</summary></details><p>0.9.37 включает поддержку более быстрого и безопасного транспортного протокола NTCP2.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="Версия 0.9.36" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 с NTCP2 и исправлениями ошибок</summary></details><p>Версия 0.9.36 включает в себя новый, более безопасный транспортный протокол под названием NTCP2.
По умолчанию он отключен, но вы можете включить его для тестирования, добавив в<a href="/configadvanced">Расширенные настройки</a> строку <tt>i2np.ntcp2.enable=true</tt> и перезапустив клиент.
NTCP2 будет включён в следующем релизе.</p>
<p>Этот релиз также содержит некоторые улучшения производительности и исправления ошибок.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="Версия 0.9.35" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 с поддержкой папок в SusiMail и мастером настройки SSL</summary></details><p>Версия 0.9.35 привносит поддержку папок в SusiMail и новый мастер SSL Wizard для настройки HTTPS у скрытых сервисов.
Также в релизе исправлено множество ошибок, особенно в SusiMail.</p>
<p>Мы работаем над релизом 0.9.36, включающим новый установщик для OSX и новый, более быстрый и защищенный протокол с названием NTCP2.</p>
<p>I2P будет на HOPE (Hackers On Planet Earth, конференция) в Нью-Йорке, 20-22 июля. Приходите знакомиться!</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="Версия 0.9.34" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 с исправлением ошибок</summary></details><p>В версии 0.9.34 исправлено множество ошибок!
Также есть улучшения в SusiMail, работе с IPv6 и выборе туннельных узлов.
@ -16,19 +393,19 @@ We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown и Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Бреши в безопасности, найденные практически во всех системах</summary></details><p>Очень серьёзная проблема была обнаружена в современных ЦП, установленных практически во всех компьютерах, продаваемых по всему миру, включая мобильные устройства. Эти бреши в безопасности были названы "Kaiser", "Meltdown" и "Spectre".</p>
<p>Описание KAISER/KPTI может быть найдено в <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown - в <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, а SPECTRE - в <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Первое сообщение от Intel доступно в <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">ответе Intel</a>.</p>
<p>Для пользователей I2P важно обновить систему, если обновления доступны. Патчи для Windows 10 доступны с настоящего момента, и скоро будут для Windows 7 и 8. Патчи для MacOS также уже доступны. Для многих Linux систем доступно также новое ядро, с включённым исправлением. То же касается Android, для которого обновление от 2 января 2018 включает патч, затрагивающий эту проблему.
<p>Для пользователей I2P важно обновить систему, если обновления доступны. Патчи для Windows 10 доступны с настоящего момента, и скоро будут для Windows 7 и 8. Патчи для MacOS также уже доступны. Для многих Linux систем доступно также новое ядро со включённым исправлением. То же касается Android, для которого обновление от 2 января 2018 включает патч, затрагивающий эту проблему.
Пожалуйста, обновите ваши системы как можно скорее, когда обновления будут доступны.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Счастливого нового года! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Новый год и I2P на 34C3</summary></details><p>Команда I2P желает всем счастливого нового года!</p>
<p>Не менее 7 членов команды I2P встретились в Лейпциге с 27 по 30 декабря 2017. Помимо <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">встреч</a> за нашим столом мы встретили много друзей I2P повсюду.
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Счастливого Нового года! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Новый год и I2P на 34C3</summary></details><p>Команда I2P желает всем счастливого Нового года!</p>
<p>Не менее 7 членов команды I2P встретились в Лейпциге с 27 по 30 декабря 2017. Помимо <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">встреч</a> за нашим столом мы встретили много друзей I2P отовсюду.
Результаты встреч уже размещены на <a href="http://zzz.i2p" target="_blank">zzz.i2p</a>.</p>
<p>Мы также раздали множество стикеров и дали информацию о нашем проекте всем, кто спрашивал.
Наш ежегодный I2P ужин был большим успехом как благодарность всем присутствовавшим за постоянную поддержку I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="Вышла версия 0.9.32" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>Версия 0.9.32 с обновленной консолью</summary></details><p>Версия 0.9.32 содержит ряд исправлений консоли маршрутизатора и связанных с ним веб-приложений (адресная книга, i2psnark и susimail).
Мы изменили логику работы настроенных имен хостов для публикуемой информации о маршрутизаторах, чтобы предотвратить часть атак перечисления с использованием DNS (enumeration attack).
Также, была добавилена проверка для предотвращения атак на подмену адреса (rebinding attack) в консоль маршрутизатора.</p>
Также, была добавлена проверка для предотвращения атак на подмену адреса (rebinding attack) в консоль маршрутизатора.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="Вышла версия 0.9.31" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>Версия 0.9.31 с обновленной консолью</summary></details><p>Изменения в данном релизе намного более заметные, нежели обычно!
Мы обновили консоль маршрутизатора для того, чтобы сделать её проще
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="Вышла версия 0.9.31" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>Версия 0.9.31 с обновленной консолью</summary></details><p>Изменения в данном релизе намного более заметные, чем обычно!
Мы обновили консоль маршрутизатора, чтобы сделать её проще
для освоения, улучшили доступность и межбраузерную поддержку
и в целом навели порядок.
Это первый шаг в долгосрочном плане по улучшению пользовательского
@ -37,18 +414,18 @@ We also have the usual collection of bug fixes, especially in SusiMail.</p>
в i2psnark.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Обращение к переводчикам" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>Предстоящий релиз 0.9.31 содержит больше строк без перевода, чем обычно.</summary></details><p>При подготовке к релизу версии 0.9.31, содержащему значительные обновления пользовательского интерфейса,
мы до сих пор имеем довольно большой объем непереведенного текста,
который требует внимания. Если Вы являетесь переводчиком, мы будем крайне признательны,
у нас до сих пор остался довольно большой объем непереведенного текста,
который требует внимания. Если вы являетесь переводчиком, мы будем крайне признательны,
если на этом этапе релиза вы сможете уделить переводу немного больше времени, чем обычно.
Мы заранее опубликовали текст для перевода,
чтобы у Вас было 3 недели для работы над ним.</p>
<p>Если вы ещё не переводчик I2P, сейчас самое время поучаствовать! Пожалуйста, взгляните на <a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">Новое руководство для переводчиков</a> для вводной информации.</p>
чтобы у вас было 3 недели для работы над ним.</p>
<p>Если вы ещё не переводчик I2P, сейчас самое время поучаствовать! Пожалуйста, ознакомьтесь с <a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">Новым руководством для переводчиков</a>, чтобы приступить к работе.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="Вышла версия 0.9.30" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 обновился до Jetty 9</summary></details><p>Версия 0.9.30 содержит обновления Jetty до версии 9 и Tomcat до версии 8.
Предыдущие версии более не поддерживаются, и отсутствуют в новых релизах Debian Stretch и Ubuntu Zesty.
Предыдущие версии более не поддерживаются и отсутствуют в новых релизах Debian Stretch и Ubuntu Zesty.
Маршрутизатор перенесет файл конфигурации jetty.xml с каждого веб-сайта Jetty в Jetty 9.
Это должно сработать для актуальных оригинальных версий, но может вызвать проблемы с модифицированными или старыми версиями.
Убедитесь, что Ваш веб-сайт работает корректно после обновления, и свяжитесь с нами в IRC, если потребуется помощь.</p>
<p>Некоторые плагины более не поддерживаются Jetty 9 и должны быть обновлены
Убедитесь, что ваш веб-сайт работает корректно после обновления и свяжитесь с нами в IRC, если потребуется помощь.</p>
<p>Некоторые плагины более не поддерживаются Jetty 9 и должны быть обновлены.
Следующие плагины были обновлены для работы с 0.9.30, и ваш маршрутизатор должен обновить их после перезагрузки:
i2pbote 0.4.6; zzzot 0.15.0.
Следующие плагины (с текущими версиями) не работают с 0.9.30.
@ -65,88 +442,89 @@ BwSchedule 0.0.36; i2pcontrol 0.11.</p>
Есть предварительные исправления для систем с Java 9, хотя мы пока не рекомендуем Java 9 для массового использования. </p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="Уязвимость безопасности I2P-Bote" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>Уязвимость безопасности I2P-Bote</summary></details><p>В I2P-Bote 0.4.5 исправлена уязвимость безопасности, присутствующая во всех предыдущих версиях плагина I2P-Bote. Android приложение не затронуто.</p>
<p>При отображении email сообщений пользователю большинство полей было экранировано. Однако имена файлов-
<p>При отображении email-сообщений пользователю большинство полей было экранировано. Однако имена файлов-
вложений не были экранированы и могли использоваться для выполнения вредоносного кода в браузере
с включенным JavaScript. Они теперь экранированы, и дополнительно политика безопасности контента
со включенным JavaScript. Они теперь экранированы, и дополнительно политика безопасности контента
была реализована для всех страниц.</p>
<p>Все пользователи I2P-Bote получат обновления автоматически во время перезапуска роутера
после релиза версии I2P 0.9.29 в середине февраля. Тем не менее, из соображений безопасности, мы рекомендуем Вам
после релиза версии I2P 0.9.29 в середине февраля. Тем не менее, из соображений безопасности, мы рекомендуем вам
<a href="http://bote.i2p/install/">следовать инструкции на странице установки</a> для
обновления вручную, если вы планируете использовать I2P или I2P-Bote до выхода 0.9.29</p>
обновления вручную, если вы планируете использовать I2P или I2P-Bote до выхода 0.9.29.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="Вышла версия 0.9.28" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>Версия 0.9.28 содержит исправления ошибок</summary></details><p>0.9.28 содержит исправления для более чем 25 тикетов на баг-трекере Trac и обновления для многих пакетов включенного программного обеспечения, включая Jetty.
Есть исправления для функции тестирования IPv6 пиров, представленной в последнем релизе.
Мы продолжаем улучшать функцию обнаружения и блокирования потенциально злонамеренных пиров.
Есть предварительные исправления для систем с Java 9, хотя мы пока не рекомендуем Java 9 для массового использования.
</p>
<p>I2P будет участвовать в 33C3, пожалуйста, не проходите мимо нашего стола и дать нам свои идеи по улучшению сети.
<p>I2P будет участвовать в 33C3, пожалуйста, не проходите мимо нашего стола и поделитесь с нами своими идеями по улучшению сети.
Мы рассмотрим нашу Дорожную карту-2017 и приоритеты на 2017 год на Конгрессе.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="Уязвимость безопасности I2P-Bote" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>Уязвимость безопасности I2P-Bote</summary></details><p>В I2P-Bote 0.4.4 исправлена уязвимость безопасности, присутствующая во всех предыдущих версиях
плагина I2P-Bote. Android приложение не затронуто.</p>
<p>Недостаток защиты CSRF означал, что если пользователь запускал I2P-Bote, а затем загружал
вредоносный сайт в браузере с включенным JavaScript, злоумышленник мог вызвать действия
в I2P-Bote от имени пользователя, например, отправка сообщений. Это могло также
вредоносный сайт в браузере со включенным JavaScript, злоумышленник мог вызвать действия
в I2P-Bote от имени пользователя, например, отправку сообщений. Это могло также
допустить извлечение личных ключей для I2P-Bote адресов, однако доказательства этой уязвимости не были протестированы.</p>
<p>Все пользователи I2P-Bote получат обновления автоматически во время перезапуска роутера
после релиза версии I2P 0.9.28 в середине декабря. Тем не менее, из соображений безопасности, мы рекомендуем Вам
после релиза версии I2P 0.9.28 в середине декабря. Тем не менее, из соображений безопасности, мы рекомендуем вам
<a href="http://bote.i2p/install/">следовать инструкции на странице установки</a> для
обновления вручную, если вы планируете использовать I2P или I2P-Bote до выхода 0.9.28. Также следует
рассмотреть вопрос о создании новых I2P-Bote-адресов, если Вы обычно просматриваете веб-сайты с включенным JavaScript, во время использования I2P-Bote.</p>
рассмотреть вопрос о создании новых I2P-Bote-адресов, если вы обычно просматриваете веб-сайты со включенным JavaScript во время использования I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="Вышла версия 0.9.27" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>Версия 0.9.27 содержит исправления ошибок</summary></details><p>0.9.27 содержит ряд исправленных ошибок
Обновленная GMP - библиотека для ускорения криптографических операций, включенная в релизе 0.9.26 только для новых установок и сборок под Debian, теперь включена в сетевое обновление до версии 0.9.27.
Есть улучшения в транспортах IPv6, тестировании SSU пиров, и скрытом режиме.</p>
<p>Мы обновили ряд плагинов в ходе мероприятия <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> и ваш маршрутизатор будет автоматически обновлять их после перезагрузки.</p>
Есть улучшения в транспортах IPv6, тестировании SSU пиров и скрытом режиме.</p>
<p>Мы обновили ряд плагинов в ходе мероприятия <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a>, и ваш маршрутизатор будет автоматически обновлять их после перезагрузки.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="Заявка на создание сайта I2P на Stack Exchange" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>Подсайт I2P предлагается к включению на Stack Exchange!</summary></details><p>Подсайт I2P теперь предлагается к включению в Stack Exchange!
Пожалуйста <a href="https://area51.stackexchange.com/proposals/99297/i2p">проголосуйте за него</a> для старта начального этапа включения.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="Заявка на создание сайта I2P на Stack Exchange" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>Подсайт I2P предлагается ко включению на Stack Exchange!</summary></details><p>Подсайт I2P теперь предлагается ко включению в Stack Exchange!
Пожалуйста, <a href="https://area51.stackexchange.com/proposals/99297/i2p">проголосуйте за него</a> для старта начального этапа включения.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="Релиз версии 0.9.26" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 содержит обновления криптографии, усовершенствования установочного пакета для Debian и исправления ошибок</summary></details><p>0.9.26 содержит значительное обновление нашей нативной криптобиблиотеки,
новый протокол подписок адресной книги с цифровыми подписями,
и значительные улучшения пакета для Debian/Ubuntu.</p>
<p>Для улучшений по части криптографии мы перешли на GMP 6.0.0, а также добавили поддержку новых процессоров,
что позволит значительно ускорить операции шифрования.
Кроме того, теперь мы постоянно используем GMP-функции для предотвращения атак "бокового канала".
Для осторожности, изменения в GMP включены для новых установок и только для Debian/Ubuntu сборок;
Из соображений безопасности, изменения в GMP включены для новых установок и только для Debian/Ubuntu сборок;
мы будем включать их (изменения в GMP) в сетевые обновления в версии 0.9.27.</p>
<p>Для Debian/Ubuntu пакета мы добавили несколько пакетов-зависимостей,
в том числе Jetty 8 и geoip, и удалили их эквивалентные части из сборки. (прим. пер. - вынесли некоторые возможности в отдельные пакеты-зависимости)</p>
<p>Здесь содержится набор исправлений ошибок, включая исправление для бага таймера
приводящий к нестабильности и снижению производительности со временем.
<p>Здесь содержится набор исправлений ошибок, включая исправление для бага таймера,
приводящего к нестабильности и снижению производительности со временем.
Как обычно, мы рекомендуем всем пользователям обновиться до этой версии.
Лучший способ помочь сети и оставаться в безопасности - это использовать последнюю версию.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="Вышла версия 0.9.25" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>Релиз 0.9.25 содержит SAM 3.3, QR-коды и исправления ошибок</summary></details><p>0.9.25 содержит новую версию SAM, а именно: мажорное обновление v3.3, чтобы поддерживать сложные многопротокольные приложения.
Этот релиз добавляет QR-коды для расшаривания адресов скрытых служб,
и идентификационные иконки для того, чтобы визуально отличать адреса.</p>
<p>Мы добавили новую страницу конфигурации - "Семейство маршрутизаторов" в консоли,
чтобы упростить объявление, что Ваша группа маршрутизаторов управляется одним человеком.
Также, внесено несколько изменений с целью увеличить пропускную способность сети и надеемся, вероятность успешного построения туннеля.</p>
чтобы упростить объявление, что ваша группа маршрутизаторов управляется одним человеком.
Также внесено несколько изменений с целью увеличить пропускную способность сети и успешно построить туннель.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="Вышел релиз 0.9.24" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>Релиз 0.9.24 содержит несколько исправлений ошибок и оптимизаций скорости.</summary></details><p>0.9.24 содержит новую версию SAM (v3.2) и многочисленные исправления ошибок и улучшения эффективности.
Обратите внимание на то, что это первый выпуск, требующий Java 7.
Пожалуйста, обновитеcь на Java 7 или 8 как можно скорее.
Ваш маршрутизатор автоматически не обновится, если Вы будете использовать Java 6.</p>
Ваш маршрутизатор автоматически не обновится, если вы будете использовать Java 6.</p>
<p>Чтобы предотвратить проблемы, вызванные древней commons-logging библиотекой, мы удалили ее.
Это может привести очень старые плагины I2P-Bote (0.2.10 и ниже, подписанные Hungry Hobo) к сбою, если они имеют опцию "IMAP enabled".
Рекомендуется исправление, чтобы заменить свой старый I2P-Bote плагин на текущий, подписанный str4d.
Для более подробной информации см <a href="http://bote.i2p/news/0.4.3"> этот пост </a>.</p>
<p>У нас был большой <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 конгресс</a> и мы добились значительных успехов по нашим планам в 2016 году по проекту.
Эшелон выступил с докладом о истории I2P и его современном состоянии, его слайды <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">можно найти здесь</a> (PDF).
Для более подробной информации см. <a href="http://bote.i2p/news/0.4.3"> этот пост </a>.</p>
<p>У нас был большой <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 конгресс</a> и мы добились значительных успехов по нашим планам в 2016 году.
Эшелон выступил с докладом об истории I2P и его современном состоянии, его слайды <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">можно найти здесь</a> (PDF).
Str4d присутствовал <a href="http://www.realworldcrypto.com/rwc2016/program">на Real World Crypto</a> и выступил с докладом о нашей криптографической миграции,
Его слайды <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">можно посмотреть здесь</a> (PDF).</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="Вышла версия 0.9.23" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 содержит различные исправления ошибок и небольшие улучшения I2PSnark</summary></details><p>Привет I2P! Это первый релиз, подписанный мною (str4d), после 49 релизов, подписанных zzz. Проверка заменяемости различных частей проекта, включая его участников.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="Вышла версия 0.9.23" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 содержит различные исправления ошибок и небольшие улучшения I2PSnark</summary></details><p>Привет I2P! Это первый релиз, подписанный мною (str4d), после 49 релизов, подписанных zzz. Проверка заменяемости различных частей проекта,
включая его участников.</p>
<p><b>На что следует обратить внимание в первую очередь</b></p>
<p>Ключ моей подписи присутствовал в обновлениях более двух лет, Начиная с версии 0.9.9,
так что с последними версиями I2P проблем возникнуть не должно. Если же уже вас версия старее чем 0.9.9,
то сначала придется обновить вручную. Сами обновления можно взять <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">отсюда</a>,
<p>Ключ моей подписи присутствовал в обновлениях более двух лет, начиная с версии 0.9.9,
так что с последними версиями I2P проблем возникнуть не должно. Если же у вас версия старше, чем 0.9.9,
то ее сначала придется обновить вручную. Сами обновления можно взять <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">отсюда</a>,
а инструкции <a href="http://i2p-projekt.i2p/ru/download#update">отсюда</a>.
После этого ваш маршрутизатор обновится до 0.9.23 самостоятельно.</p>
<p>Если вы устанавливали I2P через менеджер пакетов, то изменение вас не касается и обновление будет выполнено как обычно.</p>
<p><b>Подробности обновения</b></p>
<p>Переход маршрутизаторов на новую, более стойкую подпись Ed25519 протекает хорошо, уже обновилась половина сети. Данный релиз ускоряет этот процесс. Во избежание нарушения нормальной работы сети ваш маршрутизатор сменит тип подписи при старте с весьма небольшой вероятностью. Если такое случится, то в течении ближайших двух дней будет наблюдаться уменьшение трафика, пока новый адрес не интегрируется в сеть.</p>
<p>Это последний релиз поддерживающий Java 6. Обновитесь до 7 или 8 как можно скорее, ибо мы уже работаем над совместимостью с Java 9, в том числе уже и в данном релизе.</p>
<p>Мы также внесли незначительные улучшения в I2PSnark, а также добавили новую страницу в консоль маршрутизатора для просмотра старых новостей.</p>
<p><b>Подробности обновления</b></p>
<p>Переход маршрутизаторов на новую, более стойкую подпись Ed25519 протекает хорошо, уже обновилась половина сети. Данный релиз ускоряет этот процесс. Во избежание нарушения нормальной работы сети ваш маршрутизатор сменит тип подписи при старте с весьма небольшой вероятностью. Если такое случится, то в течение ближайших двух дней будет наблюдаться уменьшение трафика, пока новый адрес не интегрируется в сеть.</p>
<p>Это последний релиз, поддерживающий Java 6. Обновитесь до 7 или 8 как можно скорее, ибо мы уже работаем над совместимостью с Java 9, в том числе уже и в данном релизе.</p>
<p>Мы внесли незначительные улучшения в I2PSnark, а также добавили новую страницу в консоль маршрутизатора для просмотра старых новостей.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="Вышла версия 0.9.22" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 с исправлениями ошибок и началом миграции на Ed25519</summary></details><p>0.9.22 содержит исправления для i2psnark, зависающего перед завершением, и начинает миграцию маршрутизатора на новые, более сильные подписи Ed25519. Чтобы уменьшить вероятность сетевого коллапса, у Вашего маршрутизатора будет очень небольшая вероятность преобразования в Ed25519 совместимый при каждом перезапуске. Когда узлы будут повторно введены в строй, мы ожидаем увидеть более низкое использование пропускной способности в течение нескольких дней, поскольку роутеры повторно интегрируются в сеть с ее новыми идентификационными данными. Если все пройдет нормально, то мы ускорим процесс повторного ввода роутеров в строй в следующем выпуске обновления.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="Вышла версия 0.9.22" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 с исправлениями ошибок и началом миграции на Ed25519</summary></details><p>0.9.22 содержит исправления для i2psnark, зависающего перед завершением, и начинает миграцию маршрутизатора на новые, более сильные подписи Ed25519. Чтобы уменьшить вероятность сетевого коллапса, у вашего маршрутизатора будет очень небольшая вероятность преобразования в Ed25519, совместимый при каждом перезапуске. Когда узлы будут повторно введены в строй, мы ожидаем увидеть более низкое использование пропускной способности в течение нескольких дней, поскольку роутеры повторно интегрируются в сеть с ее новыми идентификационными данными. Если все пройдет нормально, то мы ускорим процесс повторного ввода роутеров в строй в следующем выпуске обновления.</p>
<p>I2PCon Торонто был очень успешным! Все презентации и видео размещены на <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">странице I2PCon</a>.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="Вышла версия 0.9.21" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 с улучшениями производительности и исправлениями ошибок</summary></details><p>0.9.21 содержит несколько изменений, чтобы добавить емкость сети, повысить эффективность floodfills, &#13;
@ -158,10 +536,10 @@ Str4d присутствовал <a href="http://www.realworldcrypto.com/rwc2016
используя новые "многосеансные" возможности тех сайтов, которые не поддерживают ECDSA.</p>
<p>Докладчики и расписание I2PCon Торонто 2015 были объявлены.&#13;
Посмотрите <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">страницу I2PCon </a> для деталей. &#13;
Забронируйте место <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">на странице Eventbrite, посвященной I2PCon</a></p>
Забронируйте место <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">на странице Eventbrite, посвященной I2PCon</a>.</p>
<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="Известны докладчики и расписание I2PCon Торонто" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>Известны докладчики и расписание I2PCon Торонто 2015</summary></details><p>Докладчики и расписание I2PCon Торонто 2015 были объявлены.&#13;
Посмотрите <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">страницу I2PCon </a> для деталей. &#13;
Забронируйте место <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">на странице Eventbrite, посвященной I2PCon</a></p>
Забронируйте место <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">на странице Eventbrite, посвященной I2PCon</a>.</p>
</article>
</div>

View File

@ -1,19 +1,424 @@
<div>
<header title="I2P-nyheter">Nyheter och uppdateringar för routern</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
<header title="I2P-nyheter">Nyheter och uppdateringar för routern</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>Den här utgåvan synkroniserar översättningar med transifex, och uppdaterar GeoIP databasen.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS-Uppdatering" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS-Uppdatering</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P förblir intakt med försämrad prestanda.</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Utgåva" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">En intervju med Konrad från diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">En intervju med Dustin från StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Utgåva" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 med tillförlitlighet och förbättrad prestanda</summary></details><p>1.7.0 Utgåvan har flera förbättringar i prestanda och tillförlitlighet.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Utgåva" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Utgiven" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>Vi har äntligen rättat några långvariga korruptionsfel i SusiMail.
Ändringar av bandbreddsbegränsaren bör förbättra nätverkets tunnelprestanda.
Det finns flera förbättringar i våra Docker-containrar.
Vi har förbättrat vårt försvar för möjliga skadliga och felaktiga routrar i nätverket.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 med SSU fixar och snabbare kryptering</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>I denna leverans, för att att minska störningar, kommer endast nya installeringar och en väldigt liten procentuell del av nuvarande installeringar
(slumpmässigt utvalda vid omstart) att använda den nya krypteringen.
Om din router "omnycklas" för att använda den nya krypteringen, kan den få lägre trafik eller lägre tillförlitlighet än tidigare under flera dagar efter en omstart.
Detta är normalt, eftersom din router genererat en ny identitet.
Dina resultat kommer att återställas efter ett tag.</p>
<p>Vi har "omnyckelat" nätverket två gånger förut, vid förändringar av standard signering,
dock är detta första gången vi har ändrat standard kryptering.
Förhoppningsvis går allt smärtfritt, men startar långsamt för att vara säkra.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 möjliggör ny kryptering</summary></details><p>0.9.47 möjliggör vårt nya ändpunkt till ändpunkt krypterings protokoll (förslag 144) som standard för vissa tjänster. Sybil analys och blockerings verktyg är nu på som standard.</p>
<p>Java 8 eller högre krävs nu.
Debianpaket för Wheezy och Stretch och för Ubuntu Trusty och Precise stöds inte längre.
Användare på dessa plattformar bör uppgradera så att du kan fortsätta få I2P-uppdateringar.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 med bug fixar</summary></details><p>0.9.46 innehåller betydande prestandaförbättringar i biblioteket för strömmning.
Vi har färdigställt utvecklingen av ECIES kryptering (förslag 144) och det finns nu ett alterantiv att aktivera det för testning.</p>
<p>Windows användare endast:
Denna leverans fixar en lokal privilegie eskaleings sårbarhet
som kunde bli exploaterad av en lokal användare.
Applicera uppdateringen så snart som möjligt.
Tack till Blaze Infosec för ett ansvarsfullt avslöjande av problemet.</p>
<p>Denna leverans är den senaste för stöd till Java 7, Debian paketen Wheezy och Stretch, samt Ubuntu paketen Precise och Trusty.
Användare på dessa platformar måste uppgradea för att få framtida I2P uppdateringar.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 med bug fixar</summary></details><p>0.9.45 innehåller viktiga felrättningar för dolt läge och bandbredds tester.
Det är en uppdatering för konsolens mörka tema.
Vi fortsätter arbeta med prestandaförbättringar samt utvecklingen av nytt ändpunkt till ändpunkt kryptering (förslag 144)</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 med bug fixar</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 innehåller en ny första installationsguid med en bandbreddstestare.
Vi har lagt till stöd för den senaste GeoIP-databasformat.
Det finns en ny Firefox profilinstallatör och en ny, infödd Mac OSX installatör på vår webbplats.
Arbetet fortsätter med att stödja det nya "LS2"-netdb-formatet.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till denna version. Det bästa sättet att upprätthålla säkerhet och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till denna version. Det bästa sättet att upprätthålla säkerhet och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 utigven" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till denna version. Det bästa sättet att upprätthålla säkerhet och hjälpa nätverket är att köra den senaste versionen.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
@ -23,17 +428,19 @@ Please update your systems as soon as available and possible.</p>
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till denna version. Det bästa sättet att upprätthålla säkerhet och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till denna version. Det bästa sättet att upprätthålla säkerhet och hjälpa nätverket är att köra den senaste versionen.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
@ -44,7 +451,7 @@ to give you three weeks to work on them.</p>
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Utgiven" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 uppdaterar till Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 uppdaterar till Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
@ -59,8 +466,9 @@ BwSchedule 0.0.36; i2pcontrol 0.11.</p>
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till denna version. Det bästa sättet att upprätthålla säkerhet och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
@ -99,7 +507,7 @@ after I2P 0.9.28 is released in mid-December. However, for safety we recommend t
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
@ -107,7 +515,7 @@ There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p
Det bästa sättet att hjälpa nätverket och hålla sig själv säker är att använda den senaste versionen.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 utgåva" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 innehåller kryptouppdateringar, Debian-paket förbättringar och felkorrigeringar. </summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 utgåva" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 innehåller kryptouppdateringar, Debian-paket förbättringar och felrättningar. </summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>För kryptering, har vi uppgraderat till GMP 6.0.0, och lagt till stöd för nyare processorer,
@ -121,17 +529,17 @@ inklusive Jetty 8 och geoip, och tagit bort motsvarande medföljande kod.</p>
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Släppt" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 innehåller SAM 3.3, QR-koder och felkorrigeringar</summary></details><p>0.9.25 innehåller en nyare version av SAM, v3.3, för att stödja avancerade fler-protokollsprogram.
Den lägger till QR-koder för att dela dolda tjänstadresser med andra,
och "identicon"-bilder för att visuellt rskilja adresser.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 innehåller SAM 3.3, QR-koder och felrättningar</summary></details><p>0.9.25 innehåller en större ny version av SAM, v3.3, för att stöda sofistikerade multiprotokollapplikationer.
Det lägger till QR-koder för att dela dolda tjänstadresser med andra,
och "identicon"-bilder för visuellt urskiljande adresser.</p>
<p>Vi har lagt till en ny "routerfamilj"-konfigurationssida i konsollen,
för att göra det enklare att din routergrupp tillhandahålls av en enda person.
Det finns flera ändringar för att öka kapaciteten i nätverket och förhoppningsvis öka chansen att lyckas bygga tunnlar.</p>
<p>Som vanligt så rekommenderar vi att alla användare uppdaterar till den här versionen.
Det bästa sättet att hjälpa nätverket och hålla sig själv säker är att använda den senaste versionen.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 släppt" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 innehåller flera felkorrigeringar och uppsnabbningar</summary></details><p>0.9.24 innehåller en ny version av SAM (v3.2) och flera felkorrigeringar och förbättrad effektivitet
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 innehåller flera felrättningar och uppsnabbningar</summary></details><p>0.9.24 innehåller en ny version av SAM (v3.2) och flera felrättningar och förbättrad effektivitet
Observera att den här versionen är den första som kräver Java 7.
Vänligen uppdatera till Java 7 eller 8 så snart som möjligt.
Uppdatera till Java 7 eller 8 så snart som möjligt.
Din router kommer inte uppdateras automatiskt om du använder Java 6.</p>
<p>För att förhindra de problem som orsakats av gamla commons-logging-biblioteket har vi tagit bort det.
Detta innebär att väldigt gamla I2P-Bote-insticksmodul (0.2.10 och tidigare, signerade av HungryHobo) kommer krasha om de har IMAP aktiverat.
@ -143,28 +551,31 @@ Echelon höll ett tal om I2Ps historia och nuvarande status, och hans presentati
Str4d besökte <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> och höll ett tal om vår krypteringsmigrering, hans presentation finns <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">här</a> (pdf).</p>
<p>Som vanligt så rekommenderar vi att alla användare uppdaterar till den här versionen.
Det bästa sättet att hjälpa nätverket och hålla sig själv säker är att använda den senaste versionen.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Release" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 innehåller en mängd olika felkorrigeringar och några mindre förbättringar i I2PSnark</summary></details><p>Hej I2P! Det här den första release som är signerad av mig (str4d), efter 49 releaser signerade zzz. Detta är ett viktigt test av vår redundans för allting, inklusive människor.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 innehåller en mängd olika felrättningar och några mindre förbättringar i I2PSnark</summary></details><p>Hej I2P! Det här den första release som är signerad av mig (str4d), efter 49 releaser signerade zzz. Detta är ett viktigt test av vår redundans för allting, inklusive människor.</p>
<p><b>Hushållning</b></p>
<p>Min signeringsnyckel har funnits med i routeruppdateringarna i över två år (sedan 0.9.9), så om du har en ny version av I2P kommer denna uppdatering att vara lika enkel som alla andra uppdateringar. Emellertid, om du kör en äldre version än 0.9.9 så måste du först uppdatera manuellt till en senare version. Uppdateringsfiler för nyare versioner kan laddas ner <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">här</a>, och instruktioner för manuell uppdatering finns <a href="http://i2p-projekt.i2p/sv/download#update">här</a>. När du har uppdaterat manuellt kommer routern själv att hitta och ladda ner 0.9.23 som vanligt.</p>
<p>Om du har installerat I2P via en pakethanterare påverkas du inte av förändringen och kan uppdatera som vanligt.</p>
<p><b>Uppdateringsdetaljer</b></p>
<p>Migrationen av RouterInfos till en ny, starkare Ed25519-signatur går bra, uppskattningsvis halva nätverket använder redan de nya nycklarna. Denna release snabbar upp processen ytterligare. För att reducera svallet i nätverket, kommer din router att ha en liten chans att konvertera till Ed25519 vid varje omstart. När den slutligen konverterar kommer du att se lägre bandbreddsanvändning i några dagar medans den återintegreras i nätverket med en ny identitet.</p>
<p>Migrationen av RouterInfos till en ny, starkare Ed25519-signatur går bra, uppskattningsvis halva nätverket använder redan de nya nycklarna. Denna utgåva snabbar upp processen ytterligare. För att reducera svallet i nätverket, kommer din router att ha en liten chans att konvertera till Ed25519 vid varje omstart. När den slutligen konverterar kommer du att se lägre bandbreddsanvändning i några dagar medans den återintegreras i nätverket med en ny identitet.</p>
<p>Observera att detta är den sista release som stöder Java 6. Uppgradera till Java 7 eller 8 så snart som möjligt. Vi arbetar redan med att göra I2P kompatibelt med den kommande Java 9, och en del av det arbetet finns med redan i denna release.</p>
<p>Vi har också gjort några mindre förbättringar i I2PSnark, och lagt till en ny sida i routerkonsollen för att läsa äldre nyheter.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till denna version. Det bästa sättet att upprätthålla säkerhet och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Släppt" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 med felkorrigeringar och påbörjar Ed25519-migrationen</summary></details><p>0.9.22 innehåller fixar för att lösa problemet med att i2psnark fastnar innan den blir klar, och påbörjar migrationen av routerinfo till nya starkare Ed25519-signaturer. För att minska nätverksbelastningen har din router bara en liten chans att konvertera till Ed25519 vid varje uppstart. När den beräknar om sina nycklar, räkna med att se minskad användning av bandbredd under ett par dagar medan den återansluter till nätverket med sin nya identitet. Om allt går som det ska, kommer vi accelerera den nya beräkningen i nästa version.</p>
<p>Vi har också gjort några mindre förbättringar i I2PSnark, och lagt till en ny sida i routerkonsolen för att läsa äldre nyheter.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 med felrättningar och påbörjar Ed25519-migrationen</summary></details><p>0.9.22 innehåller fixar för att lösa problemet med att i2psnark fastnar innan den blir klar, och påbörjar migrationen av routerinfo till nya starkare Ed25519-signaturer. För att minska nätverksbelastningen har din router bara en liten chans att konvertera till Ed25519 vid varje uppstart. När den beräknar om sina nycklar, räkna med att se minskad användning av bandbredd under ett par dagar medan den återansluter till nätverket med sin nya identitet. Om allt går som det ska, kommer vi accelerera den nya beräkningen i nästa version.</p>
<p>I2PCon Toronto var lyckad! Alla presentationer och videofilmer finns listade på <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon-sidan</a>.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till denna version. Det bästa sättet att upprätthålla säkerhet och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Utgiven" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 släppt med prestandaförbättringar och rättningar.</summary></details><p>0.9.21 innehåller flera förändringar för att öka nätverkets kapacitet, förbättra effektiviteten hos floodfills,
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 utgiven" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 utgiven med prestandaförbättringar och rättningar.</summary></details><p>0.9.21 innehåller flera förändringar för att öka nätverkets kapacitet, förbättra effektiviteten hos floodfills,
och använda bandbredden mer effektivt.
Vi har migrerat de delade klienttunnlarna till ECDSA signaturer och lagt till DSA som fallback
genom att använda den nya "multisession" möjligheten för de webbplatser som inte stödjer ECDSA. </p>
<p>Talarna och schemat för I2PCon i Toronto 2015 är klara.
Titta <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon p</a> för mer information.
Reservera plats på <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till denna version. Det bästa sättet att upprätthålla säkerhet och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto. Talare och schema offentliga." href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015. Talare och schema offentliga.</summary></details><p>Talarna och schemat för I2PCon i Toronto 2015 är klara.
Titta på <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon p</a> för mer information.
Reservera plats<a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>Talarna och schemat för I2PCon i Toronto 2015 har tillkännagivits.
Ta en titt på <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon p</a> för mer detaljer.
Reservera din plats på <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto. Talare och schema offentliga." href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015. Talare och schema offentliga.</summary></details><p>Talarna och schemat för I2PCon i Toronto 2015 har tillkännagivits.
Ta en titt<a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon p</a> för mer detaljer.
Reservera din plats på <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -0,0 +1,569 @@
<div>
<header title="I2P Habarlary">Habarlar lentasy we router täzelemeleri</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Çykaryldy" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 Ygtybarlylygy we öndürijiligi kämilleşdirilen</summary></details><p>1.7.0 wersiýasy käbir öndürijilik we ygtybarlylyk kämilleşdirmelerini öz içine alýar.</p>
<p>Indi ekranyň ýüzüne çykýan habarlary goldaýan platformalar üçin ýumuşlar panelinde şeýle habarlar bar.
i2psnark täze torrent rejeleýijisine eýe.
NTCP2 geçiriş indi has az CPU ulanýar.</p>
<p>Öňden könelen BOB interfeýsi täze gurnamalar üçin aýryldy.
Debian toplumlaryndan daşary bar bolan gurnamalarda işlemäge dowam eder.
BOB programmalaryny häzir ulanýan islendik ulanyjylar işläp düzüjilerden SAMv3 protokolyna öwürmegi soramaly.</p>
<p>1.6.1 wersiýasy çykarylandan soň ulgam ygtybarlylygynyň yzygiderli peselendigini bilýäris.
Biziň bu mesele barada wersiýa çykanyndan soň habarymyz boldy, emma sebäbini tapmak üçin iki aý ýaly möhlet gerek boldy.
Soňunda muny i2pd 2.40.0-da näsazlyk hökmünde kesgitledik we bu wersiýa bilen şol bir wagtda çykmaly 2.41.0 wersiýasy bilen düzediş giriziler.
Munuň bilen bir hatarda ulgam maglumatlar bazasynda gözlegleriň we saklamalaryň ygtybarlylygyny ösdürmek we ötük deň-duş saýlananda pes öndürijilikli deň-duşlardan gaça durmak üçin Java I2P tarapynda käbir üýtgeşmeler girizdik.
Bu näsazlykly ýa-da zyýanly routerler bolaýanda-da ulgamyň has güýçli bolmagyna kömek eder.
Mundan başga-da, i2pd we Java I2P routerleriniň deslapky wersiýalaryny birlikde izolirlenen synag ulgamynda synamak üçin birleşen maksatnama badalga berýäris we şeýlelikde meseleleri wersiýalar çykandan soň däl-de, çykarylmazdan ozal tapyp bileris.</p>
<p>Beýleki habarlarda, täze UDP geçirijimiz bolan "SSU2" (teklip 159) dizaýnynda örän öňe gitdik we durmuşa geçirip başladyk.
SSU2 öndürijilik we howpsuzlyk taýdan wajyp kämilleşmeleri üpjün eder.
Şeýle hem ol örän ýuwaş ElGamal şifrlemesiniň soňky ulanyşyny çürt-kesik çalyşmagymyza mümkinçilik berip, 9 ýyl mundan ozal başlan doly kriptografiýa täzelemesini tamamlar.
i2pd birleşen synagyna ýakynda başlamakçy we şu ýylyň dowamynda ulgama girizmekçi.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Çykaryldy" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 täze ötügiň döredilendigi baradaky habarlary işjeňleşdirýär</summary></details><p>Bu wersiýa 2021-nji ýylda işläp düzülen iki sany esasy protokol täzelemesiniň gurnalmagyny tamamlaýar.
Routerler üçin X25519 şifrlemegine geçiş çaltlaşdyrylýar we biz routerleriň hemmesiniň diýen ýaly açarynyň şu ýylyň ahyryna çenli üýtgemegini meýilleşdirýäris.
Geçirijilik ukybyny ýokary derejede azaltmak üçin ötük döredilendigi barada gysga habarlar işjeňleşdirildi.</p>
<p>Biz täze gurnama düzeltmesine mowzuk saýlama panelini goşduk.
Biz SSU işjeňligini gowulandyrdyk we SSU deň-duşlarynyň synag habarlary bilen baglanyşykly meseläni çözdük.
Ötük gurnalýarka ýadyň ulanylyşyny azaltmak üçin Blum süzgeji sazlandy.
Bizde Java bolmadyk plaginler üçin gowulandyrylan goldaw bar.</p>
<p>Beýleki täzeliklere görä biz täze UDP geçiriş SSU2 taslamasynda ajaýyp öňe gidişlikler üpjün etdik we indiki ýylyň başynda ony durmuşa geçirmäge başlamakçy.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Çykaryldy" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 täze ötügiň döredilendigi baradaky habarlar bilen</summary></details><p>Hawa, dogry, 9 ýyllyk 0.9.x çykaryşlaryndan soň biz 0.9.50-den göni 1.5.0 geçýäris.
Bu API-niň wajyp derejede üýtgejekdigini ýa-da işläp düzmegiň indiden beýläk tamamlandygyny aňlatmaýar.
Bu diňe bir ulanyjylarymyzyň bilinmezligini we goraglylygyny üpjün etmek boýunça 20 ýyllap diýen ýaly alnyp barylan işiň ykrar edilmegidir.</p>
<p>Bu çykaryş bilen, diapazon giňligini azaltmak üçin ötügiň gurnalandygy barada has kiçi habarlaryň ornaşdyrylmagy tamamlanýar.
Biz ulgamyň routerlerini X25519 şifrlenişine geçirmekligi dowam edýäris.
Elbetde ençeme näsazlyklaryň düzedilişi we işjeňligiň gowulandyrmalary hem yerine ýetirildi.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Iş stoly gorawsyzlygy" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Iş stoly gorawsyzlygy</summary></details><p>MuWire özbaşdak iş stoly programmasynda howpsuzlygyň goragsyzlygy ýüze çykaryldy.
Bu konsol plaginine täsir etmeýär we ozal bildirilen plagin meselesi bilen baglanyşykly däl.
MuWire iş stoly programmasyny işledýän bolsaňyz, derrew <a href="http://muwire.i2p/">0.8.8 wersiýasyna täzelemegiňiz</a> zerur.</p>
<p>Meseläniň jikme-jikligi 2021-nji ýylyň 15-nji iýulynda <a href="http://muwire.i2p/security.html">muwire.i2p</a>
çykarylar.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plagin goragsyzlygy" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plagin goragsyzlygy</summary></details><p>MuWire plagininde howpsuzlyk goragsyzlygy ýüze çykaryldy.
Bu özbaşdak iş stoly müşderisine täsir etmeýär.
MuWire plaginini işledýän bolsaňyz, derrew <a href="/configplugins">0.8.7-b1 wersiýasyna täzelemegiňiz</a> zerur.</p>
<p>Goragsyzlyk we täzelenen howpsuzlyk maslahatlary barada has köp maglumat üçin<a href="http://muwire.i2p/security.html">muwire.i2p</a>
saýtyny gözden geçiriň.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Çykaryldy" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>IPv6 düzedişleri bilen 0.9.50 </summary></details><p>0.9.50 router şifrleme açarlari üçin ECIES-X25519-e geçişi dowam edýär.
Ulanyjylary passiw DNS yzarlanmagyndan goramak maksady bilen, başlangyjy tamamlamak üçin HTTPS üsti bilen DNS işjeňleşdirdik.
IPv6 salgylary üçin ençeme düzedişler we gowulandyrmalar, şol sanda täze UPnP goldawy bar.</p>
<p>Käbir köp wagtdan bäri bar bolan SusiMail bidüzgünçilik näsazlyklaryny ahyrynda düzetdik.
Diapazon giňliginiň çäklendirijisine üýtgeşmeler ulgamyň ötük işleýişini gowulandyrmaly.
Biziň Docker konteýnerlerimize birnäçe gowulandyrmalar edildi.
Ulgamda mümkin bolan zyýanly we näsazlykly routerlere garşy goraglygymyzy kämilleşdirdik.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Çykaryldy" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>SSU düzedişleri we has çalt kripto bilen 0.9.49</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
it if you could set aside a little more time than usual during this release cycle
in order to bring the translations up to speed. We have pushed the strings early
to give you three weeks to work on them.</p>
<p>If you're not currently an I2P translator, now would be a great time to get
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
<p>Several plugins are not compatible with Jetty 9 and must be updated.
The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
i2pbote 0.4.6; zzzot 0.15.0.
The following plugins (with current versions listed) will not work with 0.9.30.
Contact the appropriate plugin developer for the status of new versions:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contains bug fixes</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
for this.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
which will speed up crypto operations considerably.
Also, we are now using constant-time GMP functions to prevent side-channel attacks.
For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
we will include them for in-net updates in the 0.9.27 release.</p>
<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
<p>There's a collection of bug fixes also, including a fix for a timer bug
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contains SAM 3.3, QR codes, and bug fixes</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
It adds QR codes for sharing hidden service addresses with others,
and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
to make it easier to declare that your group of routers is run by a single person.
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
Your router will not automatically update if you are using Java 6.</p>
<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration,
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
<p><b>Housekeeping</b></p>
<p>My signing key has been in router updates for over two years (since 0.9.9), so
if you are on a recent version of I2P this update should be just as easy as
every other update. However, if you are running an older version than 0.9.9, you
will first need to manually update to a recent version. Update files for recent
versions can be downloaded
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
and instructions on how to manually update are provided
<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
updated, your router will then find and download the 0.9.23 update as usual.</p>
<p>If you installed I2P via a package manager, you are not affected by the change,
and can update as usual.</p>
<p><b>Update details</b></p>
<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
with at least half of the network already estimated to have rekeyed. This
release accelerates the rekeying process. To reduce network churn, your router
will have a small probability of converting to Ed25519 at each restart. When it
does rekey, expect to see lower bandwidth usage for a couple of days as it
reintegrates into the network with its new identity.</p>
<p>Note that this will be the last release to support Java 6. Please update to
Java 7 or 8 as soon as possible. We are already working to make I2P compatible
with the upcoming Java 9, and some of that work is in this release.</p>
<p>We have also made some minor improvements in I2PSnark, and added a new page in
the routerconsole for viewing older news items.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
and use bandwidth more effectively.
We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
using the new "multisession" capability for those sites that don't support ECDSA.</p>
<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto speakers and schedule announced" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 speakers and schedule announced</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -1,149 +1,545 @@
<div>
<header title="I2P Haberleri">Haber akışı ve yöneltici güncellemeleri</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>Alışıldığı üzere bu sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu son sürümü kullanmaktır.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 sürümünde hata düzeltmeleri</summary></details><p>0.9.34 sürümü birçok hata düzeltmeleri içeriyor!
Ayrıca SusiMail, IPv6 dağıtımı, ve eş tünel seçimi için iyileştirmeler yapıldı.
<header title="I2P Haberleri">Haber akışı ve yöneltici güncellemeleri</header><article id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a" title="2.9.0 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released" author="idk" published="2025-06-02T19:00:00Z" updated="2025-06-02T19:00:00Z"><details><summary>I2P 2.9.0 sürümü</summary></details><p>I2P 2.9.0, hata düzeltmeleri ve yeni özellikler üzerinde çalışılmış bir bakım sürümüdür.</p>
<p>I2ptunnel sisteminin başarımını artırmak için işlem kullanımı iyileştirildi.
NTCP2, inceleme saldırılarına direnecek şekilde geliştirildi.
Bildirim sistemi, kullanıcılara I2PSnark ve diğer uygulamalardan daha iyi geri bildirim sağlamak için daha fazla uygulama ile bütünleştirildi.
Otomatik doldurma kaydı düzeltildi.
Kullanıcıların, otomatik doldurma olarak davranırken artan kaynak kullanımını gözlemleyebilmesi sağlandı.
Bu özellik istenmiyorsa, /config sayfasından otomatik doldurma kipinin kapatılması sağlandı.</p>
<p>Konsola, netDb görünümünüzde yönelticilerin konumlarını gösteren yeni bir küresel harita özelliği eklendi.
Bunlar, yönelticinizin tüneller oluşturmasını ve hizmetleri anonim olarak sağlamasını sağlayan eşlerdir.</p>
<p>Tüneller, Datagram2 iletişim kuralı ve Post-Quantum şifreleme için otomatik bant genişliği yönetimini ekleme çalışmaları sürüyor.
İki sürüm içinde, I2P 2.11.0 sürümünde Java 17 kullanılması zorunlu olacak.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 sürümü</summary></details><p>2.8.2 sürümünde, 2.8.1 sürümünde tanıtılan SHA256 sorunlarına neden olan hata düzeltildi.
Hata, öncelikle ban genişliği yüksek olan yönelticileri etkiledi.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 sürümü</summary></details><p>2.8.1 sürümünde 2.8.0 sürümünde bozulan yerel sitelere erişim sağlandı.
Uygulama iletilerini vurgulamak için konsoldaki çeşitli uygulamalara bildirim balonları eklendi.
Tünel güvenilirliğini etkileyebilecek bir tünel sınama hatası hazırladık.
Adres defterine aboneliklerinizden eklenen en yeni sunucu adlarını görüntüleyen yeni bir "son" sekmesi eklendi.
Birkaç karanlık tema düzeltmesi ve iyileştirmeler yapıldı.</p>
<p>Daha önce Java 21 ve üzeri sürümlerde çalışmayan kurucu düzeltildi.
Linux üzerinde boşluk içeren klasör yollarına kurulum da düzenlendi.
Docker kullananlar için, eski Docker kapsayıcısını ve kapsayıcı kitaplıkları güncellendi.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="2.8.0 sürümündeki yerel site erişim sorunları" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 yerel erişim hatası</summary></details><p>2.8.0 sürümünde bir yerel siteye (sunucu adı veya b32 ile) gezinmek başarısız oluyordu.
Geçici çözüm, I2P yönelticisini atlamak için localhost ve genellikle 7658 numaralı sunucu bağlantı noktasını kullanmak.
Örnek: <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
Bu sorun için özür dileriz. Düzeltmek için çalışıyoruz.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 sürümü" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 sürümü</summary></details><p>Bu sürümde, hataları düzelterek, kullanılmayan kodları kaldırarak ve ağ kararlılığını iyileştirerek I2P uygulamasını geliştiriyoruz.</p>
<p>Ağdaki yoğun yönelticilerin işlenmesini iyileştirdik.
UPnP ve NAT geçişindeki sorunlar, bağlantıyı ve hata bildirimini iyileştirmek için ele alındı.
Artık yöneltici başarımını iyileştirmek ve aşırı yüklenmeyi azaltmak için NetDb içinden kiralama kümelerini kaldırmak üzere daha saldırgan bir strateji uyguluyoruz.
Yönelticinin yeniden başlatılması veya kapanması gibi olayların gözlemlenebilirliğini azaltmak için başka değişiklikler yaptık.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 sürümü" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 sürümü</summary></details><p>I2P 2.7.0 sürümünde hataları düzelterek, başarımı iyileştirerek ve özellikler ekleyerek çalışmalarımızı sürdürüyoruz.</p>
<p>Konsoldan ve uygulamalardan bilgilere erişim iyileştirildi.
I2PSnark ve SusiMail aramasındaki sorunlar giderildi.
Yöneltici konsoluna gömülü netDB araması artık daha sezgisel ve kullanışlı bir şekilde çalışıyor.
Gelişmiş kipte tanılama ekranlarında küçük iyileştirmeler yapıldı.</p>
<p>Ağ içindeki uyumluluğu iyileştirmek için hatalar da düzeltildi.
Kiralama Kümelerini yayınlamayla ilgili bir sorun çözüldü ve bu da büyük gizli servislerin güvenilirliğini artırdı.
I2PSnark üzerinde artık bir kullanıcı yalnızca var olan bir torrent üzerindeki izleyicileri değiştirdiğinde infohash değerinin değişmemesi sağlandı.
Böylece, torrentlerin bu değişiklikler nedeniyle gereksiz yere kesintiye uğraması engellendi.
Yeni bir katılımcının bu katkısını memnuniyetle karşıladık.
Diğer I2P uygulamalarıyla uyumluluğu iyileştirmek için bir akış kitaplığı seçeneğinin işlenmesindeki bir çakışma sorunu çözüldü.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 sürümü</summary></details><p>I2P 2.6.1, Gizli Hizmetler Yöneticisi uygulamasındaki bir kullanıcı arayüzü hatasını düzeltmek için yayınlandı.
Bu hata kaydırmanın etkisizleştirilmesine ve bazı yapılandırmaların erişilemez olmasına yol açıyordu.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Sürümü Yayınladı" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 sürümü</summary></details><p>I2P 2.6.0 sürümünde hataları düzelterek, özellikler ekleyerek ve ağın güvenilirliğini iyileştirerek çalışmalarımızı sürdürüyoruz.</p>
<p>Otomatik doldurma yönelticileri seçilirken daha yeni yönelticilerin yeğlenmesi sağlandı.
I2PSnark, hata düzeltmelerinin yanında PeX(Peer Exchange) başarımı iyileştiren özellikler aldı.
Eski aktarım iletişim kuralları kaldırıldı ve UDP aktarımlarının kodu basitleştirildi.
Yerel olarak barındırılan hedef, yerel istemciler tarafından Kiralama Kümelerini istemeden
erişilebilir oldu ve bu da başarım ve denenebilirliği artırdı.
Eş seçimi stratejilerinde ayarlamalar yapıldı.</p>
<p>I2P artık I2P-over-Tor kullanılmasına izin vermiyor, Tor çıkış IP adreslerinden gelen bağlantılar artık engelleniyor.
Bunu önermiyoruz çünkü I2P başarımını düşürüyor ve hiçbir fayda sağlamadan Tor çıkış aktarıcılarının kaynaklarını tüketiyor.
Hem Tor çıkış aktarıcısı hem de I2P işleten yardımsever bir kişiyseniz, bunu yapmayı sürdürmek için her birinde farklı IP adresleri kullanmanızı öneririz.
Çıkış dışındaki aktarıcılar ve Tor istemcileri bundan etkilenmez ve herhangi bir şeyi değiştirmeleri gerekmez.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 sürümü HTTP düzeltmesi ile yayınlandı</summary></details><p>I2P 2.5.2 ile 2.5.0 sürümünde ortaya çıkan ve bazı HTTP içeriklerinin kırpılmasına neden olan bir hata düzeltildi.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="2.5.1 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P 2.5.1 hizmet reddi saldırılarının çözümüyle yayınlandı</summary></details><p>I2P 2.5.1, I2P ağını ve hizmetlerini etkileyen hizmet reddi saldırılarını çözmek için yayımlandı.
Bu sürümde, Sybil saldırı algılama aracının, saldırının etkisini ve süresini artırmayı hedefleyen IP tabanlı kısımlarını kullanımdan kaldırıyoruz.
Bu uygulama, ağın normal çalışmaya dönmesine yardımcı olacak.
Sybil saldırı algılama aracını kapatmış olan kullanıcılar, aracı güvenle yeniden etkinleştirebilir.
RouterInfo doğrulamasını ve eş seçimini iyileştirmek için diğer alt sistemlerde de ayarlamalar yapıldı.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Fırtınalı Hava" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Ağ havası: Fırtınalı. I2p saldırıya uğradı.</summary></details><p>I2P ağına hizmet reddi saldırısı yapılıyor.
Bu saldırı I2P ve i2pd uygulamalarını farklı şekillerde etkiliyor ve ağ sağlığı üzerinde ciddi bir etkisi var.
I2P sitelerinin erişilebilirliği büyük ölçüde bozuldu.</p>
<p>I2P üzerinde barındırdığınız bir hizmet varsa ve bu hizmet bir otomatik doldurma yönelticisinde barındırılıyorsa erişilebilirliği artırmak için hizmeti otomatik doldurma kullanılmayan bir yönelticide birden fazla sunucuya bağlamayı düşünmelisiniz.
Diğer azaltımlar tartışılıyor ancak uzun vadeli, geriye dönük uyumlu bir çözüm üzerinde çalışmayı sürdürüyoruz.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="Yeni I2P 2.5.0 sürümü yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>Ek uygulama iyileştirmeleri yapldı. NetDB yalıtım stratejisi denetimi</summary></details><p>I2P 2.5.0 sürümünde, ağ veri tabanı (NetDB) yalıtım stratejisinin uygulanmasına odaklanan 2.4.0 sürümüne göre kullanıcı tarafında ek iyileştirmeler yapıldı.</p>
<p>I2PSnark üzerine torrentlerde arama yapma gibi yeni özellikler eklendi.
BiglyBT ve qBittorrent gibi diğer I2P torrent istemcileriyle uyumluluğu artırmak için sorunlar düzeltildi.
I2P desteklerini etkinleştirmek ve geliştirmek için libtorrent ve qBittorrent ile çalışan tüm geliştiricilere teşekkür ederiz.
E-postalarda Markdown biçimlendirmesi desteği ve ek dosyaları e-postalara sürükleyip bırakma yeteneği ile birlikte yeni SusiMail özellikleri eklendi.
Gizli hizmetler yöneticisiyle oluşturulan tüneller artık başarım ve internet teknolojileriyle uyumluluğu geliştirerek daha gelişmiş I2P sitelerinin önünü açan "Keepalive" özelliğini destekliyor.</p>
<p>Bu sürüm ile, ağ veri tabanının (NetDB) istenmeyen iletilere karşı direncini artırmak ve yönelticinin şüpheli iletileri reddetme yeteneğini geliştirmek için de birkaç değişiklik yaptık.
Bu,nlar 2.4.0 sürümündeki "Alt veri tabanı yalıtımı" savunmalarının uygulanmasını "denetleme" çabasının bir parçasıydı.
Bu araştırma sırasında, küçük bir yalıtımı aşma durumu ortaya çıktı.
Bu sorun, I2P ekibi tarafından içeride bulundu ve düzeltildi.</p>
<p>Bu sürüm ile, Android ve Windows için alt dağıtımlarımızı yayınlama sürecinde çeşitli iyileştirmeler yaptık.
Bu iyileştirmeler, bu alt ürünler için aktarım ve bulunabilirliği iyileştirmiş olmalı.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 sürümü tıkanıklık ve ağ veri tabanı (NetDB) güvenliği iyileştirmeleriyle yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 sürümü tıkanıklık ve ağ veri tabanı (NetDB) güvenliği iyileştirmeleriyle yayınlandı</summary></details><p>Bu sürümde, I2P 2.4.0, I2P ağının güvenliğini ve kararlılığını iyileştirme çabalarımızı sürdürüyor.
Eşlerinizi keşfetmek için kullanılan I2P ağı içindeki önemli bir yapı olan ağ veri tabanında önemli iyileştirmeler bulunuyor.</p>
<p>Tıkanıklık yönetimi değişiklikleri, yönelticilere tıkanıklık yaşayan eşlerden kaçınarak onları rahatlatma yeteneği vererek ağ kararlılığını artıracak.
Böylece, ağda istenmeyen tünellerin etkisinin sınırlaması sağlanacak.
Ayrıca DDOS saldırıları sırasında ve sonrasında ağın iyileşmesine de yardımcı olacak.</p>
<p>Ağ veri tabanı değişiklikleri ayrıca tek tek yönelticilerin ve bunları kullanan uygulamaların güvenliğinin sağlanmasına da yardımcı oluyor.
Yönlendiriciler artık ağ veri tabanını uygulamalarla yöneltici arasındaki bilgi sızıntısını önlemek için kullandığımız birden fazla "alt veri tabanına" ayırarak saldırganlara karşı savunma yapabiliyor.
Bu aynı zamanda Java yönelticilerin ağ veri tabanı işlemleriyle ilgili güncel bilgilerini geliştiriyor ve çoklu sunucu uygulamalarına yönelik desteğimizi basitleştiriyor.</p>
<p>Ayrıca I2PSnark ve SusiMail uygulamalarında çeşitli hata düzeltmeleri ve geliştirmeler de bulunuyor.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:" title="Yeni I2P 2.3.0 sürümü yayınlandı. Güvenlik düzeltmeleri, değiştirilebilir engelleme listeleri ve DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Güvenlik düzeltmeleri, değiştirilebilir engelleme listeleri ve DTG API</summary></details><p>Bu sürümde, CVE-2023-36325 için düzeltmeler bulunuyor.
CVE-2023-36325, bloom süzgecinde ortaya çıkan bir bağlam karışıklığı hatasıdır.
Saldırgan, benzersiz bir ileti kimliği olan bir I2NP iletisi oluşturur ve bu ileti kimliğini bir istemciye gönderir.
İletinin bloom süzgecinden geçtikten sonra ikinci bir iletide kullanılmasına izin verilmez.
Saldırgan daha sonra aynı iletiyi doğrudan yönelticiye gönderir.
Yöneltici iletiyi bloom süzgecine iletir ve bırakır.
Böylece, ileti kimliğinin daha önce görüldüğü bilgisini sızdırarak saldırgana istemciyi bu yönelticinin barındırdığına inanması için güçlü bir neden verir.
Bu sorun, bloom süzgecinin işlevselliğinin, bir iletinin istemci tünelinden (bir keşif tüneli) gelip doğrudan yönelticiye gönderilip gönderilmediğine bağlı olarak farklı bağlamlara ayrılmasıyla düzeltildi.
Normal koşullar altında, bu saldırının başarılı bir şekilde gerçekleştirilmesi birkaç gün sürer ve saldırı aşamasında yönelticilerin yeniden başlatılması ve hatalı doğru sonuçlara karşı duyarlılık gibi çeşitli faktörler nedeniyle kafa karıştırıcı olabilir.
Saldırıyı önlemek için Java I2P kullanıcılarının hemen güncelleme yapması önerilir.</p>
<p>Bu bağlam karışıklığı hatasını düzeltme sürecinde, bazı stratejilerimizin kodunu bu tür sızıntılara karşı savunma amacıyla değiştirdik.
Bunlar ağ veri tabanı üzerinde yapılan değişiklikler, hız sınırlayıcı mekanizmaların ve otomatik doldurma yönelticilerinin davranışlarıdır.</p>
<p>Bu sürümde ikinci varsayılan sunucu hizmeti sağlayıcısı olarak not_bob eklendi ve konsol ana sayfasına <a href="http://notbob.i2p">notbob.i2p</a> ile <a href="http://ramble.i2p">ramble.i2p</a> eklendi.</p>
<p>Bu sürümde ayrıca değiştirilebilir bir engelleme listesi bulunuyor.
Engelleme listesi yarı kalıcıdır. Engellenen her IP adresi normalde yöneltici yeniden başlatılana kadar engellenir.
Sybil saldırıları sırasında engellenenler listesinin aşırı hızlı arttığını gözlemleyen kullanıcılar, engellenenler listesini belirli aralıklarla kayıtların süresi dolacak şekilde yapılandırarak daha kısa zaman aşımı süreleri kullanmayı yeğleyebilir.
Bu özellik varsayılan olarak kapalıdır ve şu anda yalnızca uzman kullanıcıların kullanması önerilmektedir.</p>
<p>Bu sürümde ayrıca eklentilerin Masaüstü görsel kullanıcı arayüzü (DTG) ile değiştirilebilmesi için bir API bulunuyor.
Artık sistem tepsisine menü ögeleri eklenebilir. Böylece yerel uygulama arayüzlerini kullanan eklentiler daha sezgisel olarak başlatılabilir.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="Yeni 2.2.1 sürümü yayınlandı. Docker, Ubuntu, Lunar ve Debian Sid paketleme düzeltmeleri yapıldı" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - 2.2.0 sürümü için düzeltme sürümü</summary></details><p>DDOS saldırılarını zayıflatmayı hızlandırmak amacıyla öne alınan I2P 2.2.0 sürümünün ardından, yeni paketler oluşturmayı ve yayınlamayı gerekli kılan birkaç sorunu öğrendik.
Bu sürüm, jakarta paketinin güncellenmiş bir sürümü kullanılarak yöneltici konsoluna erişilemeyen Ubuntu Lunar ve Debian Sid içindeki bir sorunu gideriyor.
Docker paketleri bağımsız değişkenleri doğru okumuyordu ve bu da yapılandırma dosyalarına erişilememesine neden oluyordu.
Bu sorun da çözüldü.
Docker kapsayıcısı artık Podman ile de uyumlu.</p>
<p>Bu sürümde, çevirileri transifex ile eşitlendi ve GeoIP ver itabanı güncellendi.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="Yeni 2.2.0, sürümünde DDOS saldırılarını zayıflatıldı ve akış alt sisteminde ince ayarlar yapıldı" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>DDOS saldırıları zayıflatıldı ve akış alt sisteminde ince ayarlar yapıldı</summary></details><p>Bugün yani 13 Mart 2023 tarihinde sunulacak olan 2.2.0 sürümünün çıkış tarihini erteledik.
Bu sürümde, NetDB, Floodfill ve Peer-Selection bileşenlerinde, yönelticinin DDOS saldırılarına karşı hayatta kalma yeteneğini geliştiren bir değişiklik bulunuyor.
Büyük olasılıkla saldırılar sürecektir. Ancak bu sistemlerde yapılan iyileştirmeler, yönelticinin kötü amaçlı görünen yönelticileri tanımlamasına ve önceliklerini kaldırmasına yardımcı olarak DDOS saldırısı riskini azaltmaya yardımcı olur.</p>
<p>Bu sürümde ayrıca akış alt sistemine, şifrelenmiş bir paketi yakalayabilen bir saldırganın onu istenmeyen alıcılara göndererek yeniden kullanmasını önleyen yeniden oynatma koruması eklendi.
Bu geriye dönük olarak uyumlu bir değişikliktir. Bu nedenle eski yönelticiler yeni yönelticilerin akış özelliklerini kullanmayı sürdürebilecektir.
Bu sorun, I2P geliştirme ekibi tarafından keşfedildi, içeride düzeltildi ve DDOS saldırılarıyla ilgili değil.
Vahşi doğada yeniden oynatılan bir akış paketiyle hiç karşılaşmadık ve şu anda I2P ağına karşı bir akış yeniden oynatma saldırısının gerçekleştiğine inanmıyoruz.</p>
<p>Fark etmiş olabileceğiniz gibi, bu sürüm notları ve sürümün kendisi zzz tarafından değil idk tarafından imzalanmıştır.
zzz projeden uzaklaşmayı seçti ve sorumlulukları diğer ekip üyeleri tarafından üstleniliyor.
Bu nedenle proje, ağ istatistikleri altyapısını değiştirmeye ve geliştirme forumunu i2pforum.i2p üzerine taşımaya çalışıyor.
Bu hizmetleri bu kadar uzun süre sağlayan zzz'ye teşekkür ediyoruz.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS güncellemesi" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS güncellemesi</summary></details><p>Saldırganın çok sayıda yönelticiyi kontrol ettiğini onayladık.
Soruşturmalarımız ve zayıflatma çalışmalarımız sürüyor.</p>
<p>Bu an, insanlara 20 yıl sonra bile I2P ağının nispeten küçük olduğunu hatırlatmak için iyi bir zaman.
Saldırganın belirli bir kullanıcıyı veya gizli hizmeti anonimleştirmeye çalıştığına dair hiçbir kanıtımız yok.
Ancak, yüksek riskli bir tehdit modeliniz varsa, I2P tarafından şu anda gerek duyduğunuz korumanın sağlanıp sağlanmadığını dikkatlice değerlendirmelisiniz.
Uzun vadede en iyi çözüm, kullanıcılarımızın güvenliğini artırmak için bu bilgiyi yaymak ve I2P ağını büyütmektir.</p>
<p>Gerektiğinde burada haber akışında ve <a href="http://zzz.i2p">zzz.i2p</a> üzerinde ek bilgi vereceğiz.
Biz I2P geliştirmeleri üzerinde çalışırken sabırlı olmanızı rica ediyoruz.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="Son hizmet reddi (DDoS) saldırıları hakkında" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P bozulan başarımda bozulmadan kaldı</summary></details><p>I2P ağı şu anda bir hizmet reddi saldırısından etkileniyor.
ın otomatik doldurma işlevi etkilendi. Bu da yanıtların kesintiye uğramasına ve tünel oluşturma başarı oranlarının düşmesine neden oldu.
Ağa karkıda bulunanlar, I2P sitelerine bağlanma ve I2P hizmetlerini kullanma konusunda zorluklar yaşadı.
Zayıflatma stratejileri kademeli olarak araştırılıp uygulanıyor.</p>
<p>Saldırı başarımı düşürmüş olsa da, ağ bozulmadan ve kullanılabilir durumda kaldı.
Java I2P yönelticileri, sorunlarla şimdilik i2pd yönlendiricilerinden daha iyi başa çıkıyor gibi görünüyor.
Önümüzdeki hafta hem Java hem de C++ yönelticilerinin geliştirme yapılarında çeşitli zayıflatmalar görünmeye başlayacak.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 sürümü çeşitli SSU2 düzeltmeleri ile yayınlandı</summary></details><p>Kasım ayında yayınlanan 2.0.0 sürümünden bu yana birçok şey öğrendik.
Yönelticiler bu sürüme güncellendikçe, yeni SSU2 aktarım iletişim kuralımız
için ağ desteği %1 oranından yaklaşık olarak %60 oranının üzerine çıktı.
İlk olarak, SSU2 iletişim kuralının sağlam, iyi tasarlanmış ve güvenli olduğunu doğruladık.
İkinci olarak, iletişim kuralının uygulanmasında çok sayıda küçük ya da nadiren karşılaşılan
hatalar bulduk ve düzelttik.
Bu hataların toplu etkisi ağın başarımını düşürüyordu.</p>
<p>Ayrıca, muhtemelen yeni Bitcoin I2P geçici adres özelliği tarafından tetiklenen ve
SSU2 hatalarımız ile diğer tıkanıklık denetimi sorunlarımız tarafından daha da
kötü duruma gelerek, ağda tünel sayısının artmasına ve tünel oluşturma başarı
oranının azalmasına neden olan sorunların farkındayız.
I2P ağ isteklerini azaltmak için Bitcoin ve Bitcoin dışındaki diğer projelerle birlikte çalışıyoruz.
Sıkışıklık zamanlarında ağ yükünü azaltmak için algoritmalarımızı geliştirdik.
Ayrıca ortak tıkanıklık denetleme stratejileri geliştirmek için i2pd ile işbirliği yapıyoruz.</p>
<p>Bu nedenle, düzeltmeleri herkese ulaştırmak için bu sürümü yaklaşık altı hafta öne aldık.
i2pd geçen hafta 2.45.0 sürümünü yayınladı ve erken sonuçlar cesaret verici.
Yeni iletişim kurallarının ve dağıtılmış ağların geliştirilmesi zordur.
Tıkanıklık, çok az uyarıyla ve nedeni hakkında çok az ipucuyla ortaya çıkabilir.
Sorunları bulup çözdüğümüzü umuyoruz. Sabrınız için teşekkür ederiz.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 taşıyıcısı etkinleştirildi</summary></details><p>I2P 2.0.0 sürümü, küçük özelliklerin, denemelerin ve çok sayıda hata düzeltmesinin tamamlanmasından sonra yeni SSU2 UDP taşıyıcımızı tüm kullanıcılar için etkinleştirdi.</p>
<p>Ayrıca kurucu, ağ veri tabanı, kişisel adres defterine ekleme, Windows tarayıcı başlatıcısı ve IPv6 UPnP ile birlikte pek çok düzeltme yaptık.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Son günlük yazıları" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Son bir kaç günlük yazısı</summary></details><p>Sitemizdeki son bir kaç günlük yazısının bağlantıları:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Yeni SSU2 taşıyıcımıza genel bakış</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">I2P taklitleri ve diğer dolandırıcılıklar hakkında uyarı</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">diva.exchange kuruluşundan Konrad ile söyleşi</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">StormyCloud kuruluşundan Dustin ile söyleşi</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 sürümü deneme için SSU2 ile yayınlandı</summary></details><p>Son üç ayı az sayıda gönüllü deneme kullanıcısıyla yeni UDP taşıyıcı iletişim kuralımız
"SSU2" üzerinde çalışarak geçirdik.
Bu sürüm, aktarıcı ve eş sınaması ile birlikte uyarlamayı tamamlıyor.
Bu özellikleri Android ve ARM platformları için varsayılan olarak ve diğer yönelticilerin
rastgele ve küçük bir yüzdesi için etkinleştiriyoruz.
Böylece önümüzdeki üç ay içinde çok daha fazla deneme yapabileceğiz ve bağlantı
taşıma özelliğini tamamlayarak kalan sorunları giderebileceğiz.
Kasım ayında çıkması planlanan bir sonraki sürümde bu özelliği herkes için etkinleştirmeyi
planlıyoruz.
El ile herhangi bir yapılandırma gerekmiyor.</p>
<p>Tabii ki, bu sürümde de olağan hata düzeltmeleri var.
Ayrıca, zaten düzeltilmiş olan nadir bir kilitlenme için otomatik bir kilitlenme algılayıcısı ekledik.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="Yeni çıkış vekil sunucusu exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>Yeni çıkış vekil sunucusu</summary></details><p>HTTP vekil sunucu tüneliniz üzerinden internete erişmek için I2P "çıkış vekil sunucuları"
ıkış düğümleri) kullanılabilir.
<a href="http://i2p-projekt.i2p/en/meetings/314">Aylık toplantımızda</a> onaylandığı şekilde
<b>exit.stormycloud.i2p</b> uzun süredir kullanılmayan <b>false.i2p</b>
vekil sunucumuzun yerini alan resmi, önerilen dış vekil sunucumuzdur.
StormyCloud <a href="http://stormycloud.i2p/">kuruluşu</a>, <a href="http://stormycloud.i2p/outproxy.html">çıkış vekil sunucusu</a> ve <a href="http://stormycloud.i2p/tos.html">hizmet koşulları</a>
hakkında ayrıntılı bilgi almak için <a href="http://stormycloud.i2p/">StormyCloud sitesine</a> bakabilirsiniz.</p>
<p><a href="/i2ptunnel/edit?tunnel=0">Gizli Hizmetler Yöneticisi yapılandırmanızı</a>,
iki yerde <b>exit.stormycloud.i2p</b> belirtecek şekilde değiştirmenizi
öneririz: <b>Outproxies</b> ve <b>SSL Outproxies</b>.
Düzenlemeden sonra <b>aşağı kaydırıp Kaydet üzerine tıklayın</b>.
Ekran görüntüsü için <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog yazımıza bakabilirsiniz</a>.
Android yönergeleri ve ekran görüntüleri için <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob blog</a> sitesine bakabilirsiniz.</p>
<p>Yöneltici güncellemeleri yapılandırmanızı güncellemeyeceğinden el ile düzenlemeniz gerekir
Teşekkürler StormyClod. Bağış yaparak bizi desteklemeyi düşünün.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>Bu sürümde, i2psnark, yöneltici, I2CP ve UPnP
üzerinde yapılmış hata düzeltmeleri bulunuyor.
Yöneltici, yumuşak yeniden başlatma, IPv6, SSU
eş sınaması, ağ veri tabanı kaydetme ve tünel
oluşturma adres hataları düzeltildi.
Yöneltici ailesi kullanımı ve Sybil sınıflandırması da
önemli ölçüde iyileştirildi.</p>
<p>i2pd ile birlikte yeni SSU2 UDP taşıyıcımızı geliştiriyoruz.
SSU2, önemli başarım ve güvenlik iyileştirmeleri getirecek.
Ayrıca, yaklaşık 9 yıl önce başlattığımız tam şifreleme
yükseltmesini tamamlıyoruz. Böylece çok yavaş ElGamal
şifrelemesini son kez kullanıyoruz ve nihayet değiştirebileceğiz.
Bu sürümde, varsayılan olarak etkisizleştirilmiş bir ön
uygulama bulunuyor. Denemelere katkıda bulunmak
istiyorsanız, zzz.i2p adresindeki güncel bilgileri bakabilirsiniz.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Temel Java/JPackage güncellemeleri kuruldu" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>Yeni bulunan Java "Psişik imzalar" güvenlik açığı I2P uygulamasını etkiliyor.
Linux için I2P kullanan veya kurulum paketinde bulunmayan bir JVM kullanan
I2P kullanıcıları, JVM yazılımlarını güncellemeli ya da bu güvenlik açığının
bulunmadığı Java 15 altındaki bir sürüme geçmeli.</p>
<p>Son Java Virtual Machine sürümü kullanılarak yeni I2P Easy-Install kolay kurulum
paketleri oluşturuldu. Ayrıntılı bilgi almak için paket haber akışlarına bakabilirsiniz.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 sürümü güvenilirlik ve başarım iyileştirmeleri ile yayınlandı.</summary></details><p>1.7.0 sürümünde birkaç başarım ve güvenilirlik iyileştirmesi yapıldı.</p>
<p>Artık destekleyen platformların sistem tepsisinde açılır iletiler var.
Yeni bir i2psnark torrent düzenleyicisi var.
NTCP2 taşıyıcısı artık çok daha az işlemci kullanıyor.</p>
<p>Uzun süredir kullanımdan kaldırılan BOB arayüzü, yeni kurulumlar için kaldırıldı.
Debian paketleri dışında var olan kurulumlarda çalışmayı sürdürecek.
BOB uygulamalarının kalan tüm kullanıcıları, geliştiricilerden SAMv3 iletişim kuralına geçmelerini istemelidir.</p>
<p>1.6.1 sürümümüzden bu yana ağ güvenilirliğinin giderek kötüleştiğini biliyoruz.
Yayınlandıktan hemen sonra sorunun farkındaydık, ancak nedenini bulmamız neredeyse iki ayımızı aldı.
Sonunda bunu i2pd 2.40.0 sürümünde bir hata olarak belirledik.
Düzeltmesi, bu sürümle yaklaşık olarak aynı zamanda çıkan 2.41.0 sürümünde olacak.
Bu arada, ağ veri tabanı aramalarının ve depolarının sağlamlığını geliştirmek ile tünel eş seçiminde başarımı düşük olan
eşlerden kaçınmak için Java I2P tarafında birkaç değişiklik yaptık.
Böylece, hatalı veya kötü niyetli yönelticilerin varlığında bile ağ daha sağlam olmalı.
Ayrıca, yayın öncesi i2pd ve Java I2P yönelticilerini yalıtılmış bir deneme ağında
birlikte denemek için ortak bir program başlatıyoruz. Böylece daha fazla sorunu
sürümler yayınlandıktan sonra değil, yayınlanmadan önce bulabiliriz.</p>
<p>Diğer yandan, yeni UDP taşıyıcımız "SSU2" (159 numaralı öneri) tasarımında büyük ilerleme kaydetmeyi sürdürüyoruz
ve kullanıma almaya başladık.
SSU2, önemli başarım ve güvenlik iyileştirmeleri getirecek.
Ayrıca, yaklaşık 9 yıl önce başlayan tam şifreleme yükseltmesini tamamlayarak, çok yavaş ElGamal şifrelemesini değiştirmeden önce son kez kullanacağız.
Yakında i2pd ile ortak denemelere başlamayı ve bu yıl ağ üzerinde kullanıma sunmayı umuyoruz.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 sürümünde yeni tünel oluşturma iletileri etkinleştirildi</summary></details><p>Bu sürümde, 2021 yılında geliştirilen iki büyük iletişim kuralı güncellemesinin dağıtımını tamamlanıyor.
Yöneltici için X25519 şifrelemesi geçişi hızlandı ve yıl sonuna kadar neredeyse tüm yönelticilerin yeniden anahtarlanmasını bekliyoruz.
Bant genişliğinde önemli bir azalma sağlayacak olan kısa tünel oluşturma iletileri etkinleştirildi.</p>
<p>Yeni kurulum yardımcısına tema seçim panosu eklendi.
SSU başarımı iyileştirildi ve SSU eş sınaması iletileriyle ilgili bir sorun düzeltildi.
Tünel oluşturma Bloom süzgeci, bellek kullanımını azaltacak şekilde ayarlandı.
Java dışı eklenti desteği genişletildi.</p>
<p>Diğer yandan, yeni UDP ulaşım SSU2 tasarımında harika bir ilerleme kaydettik ve önümüzdeki yılın başlarında uygulamaya geçirmeyi umuyoruz.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 sürümü yeni tünel oluşturma iletileri ile yayınlandı</summary></details><p>Evet, doğru. 9 yıldır süren 0.9.x sürümlerinden sonra, doğrudan 0.9.50 sürümünden 1.5.0 sürümüne geçiyoruz.
Bu durum, büyük bir API değişikliği olduğu ya da geliştirmenin tamamlandığı anlamına gelmiyor.
Yaklaşık 20 yıldır kullanıcılarımıza anonimlik ve güvenlik sağlamak için süren çalışmaları onurlandırıyor.</p>
<p>Bu sürüm, bant genişliğini azaltmak için daha küçük tünel oluşturma iletileri uygulamasını tamamlar.
Ağ yönelticilerinin X25519 şifrelemesine geçişini sürdürüyoruz.
Elbette çok sayıda hata düzeltmesi ve başarım iyileştirmesi de var.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Masaüstü Güvenlik Açığı" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Masaüstü Güvenlik Açığı</summary></details><p>MuWire bağımsız masaüstü uygulamasında bir güvenlik açığı bulundu.
Bu açık pano eklentisini etkilemiyor ve daha önce duyurulan eklenti sorunuyla ilgili değil.
MuWire masaüstü uygulamasını kullanıyorsanız hemen <a href="http://muwire.i2p/">0.8.81 sürümüne güncellemelisiniz</a>.</p>
<p>Sorunun ayrıntıları 15 Temmuz 2021 tarihinde <a href="http://muwire.i2p/security.html">muwire.i2p</a>
adresinde yayınlanacak.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Eklentisi Güvenlik Açığı" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Eklentisi Güvenlik Açığı</summary></details><p>MuWire eklentisinde bir güvenlik açığı bulundu.
Bu açık bağımsız masaüstü uygulamasını etkilemiyor.
MuWire eklentisini kullanıyorsanız hemen <a href="/configplugins">0.8.7-b1 sürümüne güncellemelisiniz</a>.</p>
<p>Güvenlik açığı ve güncellenmiş güvenlik önerileri hakkında
ayrıntılı bilgi almak için <a href="http://muwire.i2p/security.html">muwire.i2p</a> adresine bakabilirsiniz.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 sürümü IPv6 düzeltmeleri ile yayınlandı</summary></details><p>0.9.50 sürümünde, yöneltici şifreleme anahtarları için ECIES-X25519 geçişi çalışmaları sürüyor.
Kullanıcıları pasif DNS gözetlemesinden korumak için yeniden tohumlama işleminde HTTPS üzerinden DNS özelliği etkinleştirildi.
Yeni UPnP desteği ile IPv6 adresleri için çok sayıda düzeltme ve iyileştirme yapıldı.</p>
<p>Uzun süredir var olan bazı SusiMail bozulma hataları nihayet düzeltildi.
Bant genişliği sınırlayıcısında yapılan değişiklikler ağ tüneli başarımını iyileştirmiş olmalı.
Docker kapsayıcılarımızda birkaç iyileştirme yapıldı.
Ağdaki olası kötü amaçlı ve hatalı yönelticilere karşı savunma geliştirildi.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 sürümü SSU hata ayıklamaları ve daha hızlı şifreleme ile yayınlandı</summary></details><p>0.9.49 sürümünde I2P uygulamasını daha hızlı ve daha güvenli hale getirme çalışmaları sürüyor.
SSU (UDP) taşıyıcısı için daha yüksek hızlar sağlayacak çeşitli iyileştirme ve düzeltmeler yapıldı.
Ayrıca bu sürümde yönelticiler için yeni ve daha hızlı ECIES-X25519 şifrelemesine geçiş de başlatıldı.
(Hedefler birkaç sürümdür bu şifrelemeyi kullanıyordu)
Birkaç yıldır yeni şifreleme için teknik özellikler ve iletişim kuralları üzerine çalışıyoruz
ve çalışmalarımızın sonuna yaklaşıyoruz! Geçişin tamamlanması birkaç sürüm alacak.</p>
<p>Bu sürümde kesintiyi en aza indirmek için yalnızca yeni kurulumlar ve var olan kurulumların çok küçük bir
yüzdesi (yeniden başlatma sırasında rastgele seçilir) yeni şifrelemeyi kullanacak.
Yönelticiniz yeni şifrelemeyi kullanmak için "yeniden anahtarlama" yaparsa, yeniden başlatıldıktan sonraki birkaç gün boyunca normalden daha düşük trafik ya da daha düşük güvenilirlik görebilirsiniz.
Yönelticiniz yeni bir kimlik oluşturduğundan bu durum normaldir.
Başarımınız bir süre sonra düzelecektir.</p>
<p>Varsayılan imza türünü değiştirirken ağı daha önce iki kez "yeniden anahtarladık"
ancak varsayılan şifreleme türünü ilk kez değiştiriyoruz.
Her şeyin yolunda gideceğini umuyoruz. Ancak emin olmak için yavaş yavaş başlıyoruz.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 sürümü başarım iyileştirmeleri ile yayınlandı</summary></details><p>0.9.48 sürümünde, çoğu hizmet için yeni uçtan uca şifreleme iletişim kuralı (öneri 144) kullanılıyor.
Yeni tünel oluşturma ileti şifrelemesinin ön desteği eklendi (152 numaralı öneri).
Yöneltici genelinde önemli başarım iyileştirmeleri yapıldı.</p>
<p>Ubuntu Xenial (16.04 LTS) paketleri artık desteklenmiyor.
Bu platformu kullanan kullanıcıların gelecekteki I2P güncellemelerini alabilmesi için sürümlerini yükseltmesi gerekiyor.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 sürümünde yeni şifreleme kullanılıyor</summary></details><p>0.9.47 sürümünde bazı hizmetler için varsayılan olarak yeni uçtan uca şifreleme iletişim kuralı (144 numaralı öneri) kullanılıyor.
Artık Sybil inceleme ve engelleme aracı varsayılan olarak etkin.</p>
<p>Bu sürüm için Java 8 ve üzerindeki sürümler gereklidir.
Wheezy ve Stretch Debian paketleri ile Precise and Trusty Ubuntu paketleri artık desteklenmiyor.
Bu platformları kullanan kullanıcıların gelecekteki I2P güncellemelerini alabilmesi için sürümlerini yükseltmesi gerekiyor.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.46 sürümünde akış kitaplığında önemli başarım iyileştirmeleri yapıldı.
ECIES şifreleme (144 numaralı öneri) geliştirilmesi tamamlandı ve bu özelliği denemek için etkinleştirme seçeneği sunuldu.</p>
<p>Yalnızca Windows kullanıcıları:
Bu sürümde, yerel kullanıcılar tarafından kötüye kullanılabilecek
yerel izinleri yükseltme açığı düzeltildi.
Lütfen en kısa sürede sürümünüzü güncelleyin.
Sorunun açığa çıkması için sorumluluk alan Blaze Infosec teşekkürü hakediyor.</p>
<p>Bu sürüm Java 7 sürümünü, Wheezy ve Stretch Debian paketlerini ve Precise and Trusty Ubuntu paketlerini destekleyen son sürüm.
Bu platformları kullanan kullanıcıların gelecekteki I2P güncellemelerini alabilmesi için sürümlerini yükseltmesi gerekiyor.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.45 sürümünde gizli kip ve bant genişliği ölçümü için önemli düzeltmeler yapıldı.
Pano karanlık temasında bir güncelleme yapıldı.
Başarımı iyileştirme ve yeni uçtan uca şifreleme geliştirme çalışmalarını sürdürüyoruz (144 numaralı öneri).</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.44 sürümünde gizli hizmetlerde yeni şifreleme türleri işlenirken hizmet reddi sorununa yol açan önemli bir hata düzeltildi.
Tüm kullanıcıların en kısa sürede bu sürüme geçmesini öneriyoruz.</p>
<p>Bu sürümde ayrıca yeni uçtan uca şifreleme desteği bulunuyor (144 numaralı öneri)
Bu proje üzerindeki çalışmalar sürüyor ve henüz tamamlanmadı.
Pano ana sayfasında bazı değişiklikler yapıldı ve i2psnark içine yeni HTML5 ortam oynatıcısı eklendi.
Güvenlik duvarı arkasındaki IPv6 ağları için ek düzeltmeler yapıldı.
Tünel oluşturma düzeltmeleri ile bazı kullanıcıların uygulamayı daha hızlı başlatması sağlandı.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.43 sürümünde daha güçlü güvenlik ve gizlilik özellikleri üzerindeki çalışmalar sürdürüldü ve başarımda iyileştirmeler yapıldı.
Uygulamayı yeni "Kiralama kümesi" (LS2) standartlarına uyumlu hale getirme çalışmaları tamamlandı.
Gelecek sürümlere eklenecek daha güçlü ve daha hızlı uçtan uca şifreleme (144 numaralı öneri) uyarlaması üzerinde çalışma başlandı.
Bazı IPv6 adres algılama sorunları ile bazı hatalar düzeltildi.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.42 sürümünde I2P platformunu daha hızlı ve daha sağlam kılma üzerine çalışıldı.
UDP taşıyıcısını hızlandıracak bir kaç değişiklik yapıldı.
Gelecekte daha modüler bir paket oluşturmak için yapılandırma dosyaları ayrıldı.
Daha hızlı ve güvenli şifreleme için yeni fikirler üzerinde çalışma sürdürüldü.
Ayrıca çok sayıda hata düzeltmesi yapıldı.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.34 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.41 sürümünde 123 numaralı önerideki yeni özellikleri ekleme çalışmaları sürdürüldü.
"Şifrelenmiş kiralama kümeleri" (EncryptedLeaseSets) için her istemcinin kimliğinin doğrulanması özelliği eklendi.
Panodaki I2P logosu güncellendi ve bir kaç yeni simge eklendi.
Linux kurucusu güncellendi.</p>
<p>Başlangıç artık Raspberry Pi gibi platformlarda daha hızlı olmalı.
Bazı alt düzey ağ iletilerini etkileyen ciddi sorunları ve bir kaç hatayı giderdik.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 sürümünde yeni simgeler eklendi</summary></details><p>0.9.40 sürümünde yeni "Şifrelenmiş kiralama kümesi" (EncryptedLeaseSet) biçimi destekleniyor.
Eski NTCP 1 taşıyıcı iletişim kuralı etkisizleştirildi.
Yeni SusiDNS içe aktarma özelliği ve geliş bağlantıları için yeni betik ile süzme yöntemi eklendi. </p>
<p>OSX doğal kurucusu üzerinde birçok geliştirme yapıldı ve IzPack kurucusu da güncellendi.
Pano simgelerini yenileme çalışması sürüyor.
Her zamanki gibi pek çok hata düzeltildi. </p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 sürümü başarım iyileştirmeleri ile yayınlandı.</summary></details><p>0.9.39 sürümünde yeni ağ veri tabanı türleri (123 numaralı öneri) ile ilgili pek çok değişiklik yapıldı.
RPC uygulamalarının geliştirilmesini desteklemek için i2pcontrol uygulama eki bir internet uygulaması olarak eklendi.
Çeşitli başarım iyileştirmeleri ve hata düzeltmeleri yapıldı.</p>
<p>Bakım yükünü azaltmak için Gece Yarısı ve Klasik temaları kaldırıldı.
Daha önce bu temaları kullanan kullanıcılar koyu ya da açık temayı seçebilir.
Ayrıca yeni ana sayfa simgeleri ve ilk pano güncelleme adımı eklendi.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 sürümü yeni kurulum yardımcısı ile yayınlandı.</summary></details><p>0.9.38 sürümünde bant genişliği sınaması da bulunan yeni bir kurulum yardımcısı var.
Son GeoIP veri tabanı biçimi desteği eklendi.
Sitemize yeni bir Firefox profili kurucusu ve yeni bir doğal Mac OS X kurucusu eklendi.
Yeni "LS2" "Ağ veri tabanı" (NetDB) biçimini destekleme çalışmaları yapılıyor.</p>
<p>Bu sürümde ayrıca SusiMail ek dosyaları ile ilgili çeşitli sorunlar ve yalnızca IPv6 ile çalışan yönelticiler ile ilgili bir düzeltme gibi çok sayıda hata düzeltmesi yapıldı.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Gezi Raporu" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P 35C3 Etkinliğinde</summary></details><p>I2P ekibi Leipzig'de düzenlenen 35C3 etkinliğine neredeyse tümüyle katıldı.
Günlük toplantılarda geçen yıl yapılanlar gözden geçirildi ve 2019 yılı için tasarım ve geliştirme hedeflerine değinildi.</p>
<p>Proje Vizyonu ve yeni Yol Haritasına <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">buradan bakabilirsiniz</a>.</p>
<p>LS2, Testnet ve sitemiz ile panonun kullanılabilirliğini iyileştirme çalışmalarımız sürüyor.
Tails, Debian ve Ubuntu Disco üzerinde çalışmak için planımız üzerinde çalışıyoruz. Hala Android ve I2P_Bote düzeltmelerine yardımcı olacak insan kaynağına ihtiyacımız var.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 sürümünde NTCP2 etkinleştirildi</summary></details><p>0.9.37 sürümünde NTCP2 adında daha hızlı ve daha güvenli bir taşıyıcı iletişim kuralı kullanılıyor.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 sürümü NTCP2 ve hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.36 sürümünde NTCP2 olarak adlandırılan yeni ve daha güvenli bir taşıyıcı iletişim kuralı bulunuyor.
Varsayılan olarak etkisizleştirilmiştir ancak denemek için <a href="/configadvanced">gelişmiş yapılandırma</a> bölümünden <tt>i2np.ntcp2.enable=true</tt> seçeneğini ekleyip yeniden başlatabilirsiniz.
NTCP2 gelecek sürümde varsayılan olarak etkinleştirilecek.</p>
<p>Bu sürümde ayrıca bazı başarım iyileştirmeleri ve hata düzeltmeleri yapıldı.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 sürümü SusiMail klasörleri ve SSL yardımcısı ile yayınlandı</summary></details><p>0.9.35 sürümünde SusiMail uygulaması için klasör desteği ile gizli hizmetler siteniz için HTTPS kurulumu yapmanıza yardımcı olacak yeni bir SSL yardımcısı bulunuyor.
Ayrıca özellikle SusiMail üzerinde olmak üzere çeşitli hata düzeltmeleri yapıldı.</p>
<p>0.9.36 sürümüne hazırlık olarak, yeni bir OSX kurucusu ve NTCP2 olarak adlandırılan daha güvenli ve daha hızlı bir taşıyıcı iletişim kuralı gibi bir kaç şey üzerinde sıkı çalışıyoruz.</p>
<p>I2P ekibi 20-22 Temmuz arasında New York City HOPE etkinliğine katılıyor. Merhaba demek için bizi bulun!</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.34 sürümünde birçok hata düzeltmesi bulunuyor!
SusiMail, IPv6 dağıtımı, ve eş tünel seçimi için iyileştirmeler yapıldı.
UPnP için IGD2 şemaları desteği eklendi.
Ayrıca ileriki sürümlerde göreceğiniz iyileştirmeler için hazırlıklar yapıldı.
</p>
<p>Alışıldığı üzere bu sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu son sürümü kullanmaktır.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 sürümünde bazı hata düzeltmeleri bulunuyor</summary></details><p>0.9.33 sürümünde i2psnark, i2ptunnel, akış ve SusiMail üzerinde çok sayıda hata düzeltildi.
Ayrıca sonraki sürümlerde göreceğiniz iyileştirmeler için hazırlıklar yapıldı.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.33 sürümünde i2psnark, i2ptunnel, akış ve SusiMail üzerinde çok sayıda hata düzeltildi.
Yeniden tohumlanan sitelere erişemeyenler için bir kaç yeniden tohumlama vekil sunucusu türü daha destekleniyor.
Artık gizli hizmetler yönetimi bölümündeki hız sınırlamaları varsayılan olarak uygulanıyor.
Yüksek trafikli site kullanıcılarının bu sınırları gözden geçirdikten sonra ayarlaması gerekebilir.</p>
<p>Alışıldığı üzere bu sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu son sürümü kullanmaktır.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown ve Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Neredeyse tüm sistemlerde güvenlik açığı bulundu.</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>Alışıldığı üzere bu sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu son sürümü kullanmaktır.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
<p>Alışıldığı üzere bu sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu son sürümü kullanmaktır.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
it if you could set aside a little more time than usual during this release cycle
in order to bring the translations up to speed. We have pushed the strings early
to give you three weeks to work on them.</p>
<p>If you're not currently an I2P translator, now would be a great time to get
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
<p>Several plugins are not compatible with Jetty 9 and must be updated.
The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown ve Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Neredeyse her sistemi etkileyen bir güvenlik açığı bulundu.</summary></details><p>Cep telefonları da dahil olmak üzere Dünya çağında satılmış tüm bilgisayarlarda bulunan modern işlemcilerde çok ciddi bir sorun bulundu. Bu güvenlik açıkları "Kaiser", "Meltdown" ve "Spectre" olarak adlandırılıyor.</p>
<p>KAISER/KPTI ile ilgili yayını <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown ile ilgili yayını <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a> ve SPECTRE ile ilgili yayını <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a> belgelerinde bulabilirsiniz. Intel tarafından yayınlanan ilk bilgiyi <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intel yanıtı</a> belgesinde bulabilirsiniz.</p>
<p>Güncellemeler yayınlandıkça I2P kullanıcılarının sistemlerini güncellemesi önemlidir. Şu anda Windows 10 yamaları yayınlanıyor. Windows 7 ve 8 yamaları yakında yayınlanacak. MacOS yamaları yayınlandı. Çoğu Linux sisteminin çekirdeği düzeltildi. Aynı şekilde Android üzerinde 2 Ocak 2018 tarihinde yayınlanan yama ile bu sorun çözüldü.
Lütfen sistemlerinizi olabildiğince kısa sürede güncelleyin. </p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Mutlu yıllar! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Yeni yıl ve I2P 34C3 Etkinliği</summary></details><p>I2P ekibi olarak herkesin yeni yılını kutlarız!</p>
<p>I2P ekibinin en az 7 üyesi 27 - 30 Aralık 2017 tarihleri arasında Leipzig 34C3 etkinliğine katıldı. Masamızdaki <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">görüşmelerin</a> yanında her tarafta I2P dostları ile görüştük.
Görüşme sonuçları <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> üzerine eklendi bile.</p>
<p>Ayrıca çok sayıda etiket dağıttık ve soranlara projemiz hakkında bilgi verdik.
Yıllık I2P yemeğimiz çok başarılıydı. Katılan herkese I2P projesini destekledikleri için teşekkür ederiz.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 sürümü pano güncellemeleri ile yayınlandı</summary></details><p>0.9.32 sürümünde yöneltici panosunda ve ilgili internet uygulamalarında (adres defteri, i2psnark ve SusiMail) çeşitli hata düzeltmeleri yapıldı.
Ayrıca DNS üzerinden yapılan bazı ağ listeleme saldırılarını engellemek amacıyla yayınlanmış yöneltici bilgileri için yapılandırılmış sunucu adlarının işlenme yöntemi değiştirildi.
Yeniden bağlanma saldırılarını engellemek amacıyla panoya bazı denetimler eklendi.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 sürümü pano güncellemeleri ile yayınlandı</summary></details><p>Bu sürümde her zamankine göre daha çok fark edilecek değişiklikler yapıldı!
Yöneltici panosunu yenilenerek görünümünü sadeleştirildi, erişimi kolaylaştırıldı,
farklı tarayıcılarda kullanılabilmesini sağlandı ve içeriği toparlandı.
Bu işlemler yöneltici panosunun daha kullanıcı dostu bir arayüze sahip olması
için uzun dönemde yapılacak işlemlerin ilk adımını oluşturdu.
Ayrıca i2psnark üzerine torrent değerlendirme ve yorum yapma özelliği eklendi.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Çevirmenlere Duyuru" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>Yayınlanacak 0.9.31 sürümünde normalden daha fazla sayıda dizgenin çevrilmesi gerekecek.</summary></details><p>0.9.31 sürümü hazırlanırken, kullanıcı arayüzünde önemli güncellemeler yapıldığından
normal olarak çevrilmesi gerekenden çok daha fazla sayıda dizgenin çevrilmesi
gerekiyor. Çevirilerimizi yapıyorsanız çevirilerin zamanında yetişmesi için
bu sürüme normal sürümlerden daha fazla zaman ayırabilirseniz minnettar oluruz.
Üzerinde daha rahat çalışabilmeniz için dizgeleri üç hafta erken yayınladık.</p>
<p>Bir I2P çevirmeni değilseniz katkıda bulunmaya başlayabilirsiniz! Ayrıntılı
bilgi almak için
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">Yeni Çevirmen Rehberi</a>
bölümüne bakabilirsiniz.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 sürümünde Jetty uygulaması 9. sürüme güncellendi</summary></details><p>0.9.30 sürümünde Jetty 9 ve Tomcat 8 güncellemeleri bulunuyor.
Önceki sürümler artık desteklenmiyor ve yakında yayınlanacak olan Debian Stretch ve Ubuntu Zesty sürümlerinde bulunmayacak.
Yöneltici her site için eski jetty.xml yapılandırma dosyasını yeni Jetty 9 ayarlarına göre değiştirecek.
Son sürümlerde kullanılan ve üzerinde değişiklik yapılmamış ayarların sorunsuz çalışması gerekir. Ancak üzerinde değişiklik yapılmış ya da çok eski yapılandırma dosyaları çalışmayabilir.
Güncelleme sonrasında Jetty sitenizin çalıştığından emin olun. Yardıma gerek duyarsanız bizimle IRC kanalında görüşebilirsiniz.</p>
<p>Jetty 9 ile uyumlu olmadığı için güncellenmesi gereken bir kaç uygulama eki var.
Yönelticinizi yeniden başlatırsanız, şu uygulama eklerini 0.9.30 sürümüyle çalışabilecek şekilde güncellemesi beklenir:
i2pbote 0.4.6; zzzot 0.15.0.
The following plugins (with current versions listed) will not work with 0.9.30.
Contact the appropriate plugin developer for the status of new versions:
Şu uygulama ekleri (geçerli sürümleri ile listelenen) 0.9.30 sürümü ile çalışmaz.
Yeni sürümlerin durumu ile uygulama eki geliştiricisi ile iletişim görüşün:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>Alışıldığı üzere bu sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu son sürümü kullanmaktır.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>Bu sürüm ayrıca eski (2014 ve daha öncesi) DSA-SHA1 gizli hizmetlerinin daha güvenli EdDSA imza türüne aktarılmasını destekler.
Ayrıntılı bilgi almak, rehber ve SSS için <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> adresine bakabilirsiniz.</p>
<p>Not: Raspberry Pi gibi Android çalıştırmayan ARM platformlarında, yeniden başlatma sırasında blok dosyası veri tabanı güncellenir ve bu işlem bir kaç dakika sürebilir.
Lütfen sabırla bekleyin.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.29 sürümünde, bozuk sıkıştırılmış iletilerle ilgili çözümleri de içeren çeşitli Trac bildirimleri düzeltildi
Artık IPv6 üzerinden NTP destekleniyor.
Ön Docker desteği eklendi.
Rehber sayfalarını çevirme olanağı eklendi.
Artık HTTP vekil sunucusu üzerinden aynı kaynaktan gelen yönlendirme üst bilgileri aktarılıyor.
Java 9 için ek düzeltmeler yapıldı. Bununla birlikte henüz genel amaçlar için Java 9 kullanılmasını önermiyoruz.</p>
<p>Herzamanki gibi tüm kullanıcıların yeni sürüme yükseltmesini öneriyoruz.
Ağa yardımcı olmak ve güvende kalmak için son sürümü kullanmalısınız.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contains bug fixes</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
Ağa yardımcı olmak ve güvende kalmak için güncel sürümü kullanmalısınız.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Güvenlik Açığı" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Güvenlik Açığı</summary></details><p>I2P-Bote uygulama ekinin daha önceki sürümlerinde bulunan bir güvenlik açığı I2P-Bote 0.4.5 sürümünde giderildi. Android uygulaması etkilenmedi.</p>
<p>E-postalar kullanıcılara görüntülenirken, çoğu alan atlanıyordu. Ancak eklerin dosya adları
atlanmadığından, bu alan JavaScript etkinleştirilmiş olan bir tarayıcıda kötü niyetli
kodları yürütmek için kullanılabiliyordu.
Şimdi bu alanlar da atlanıyor ve ek olarak tüm sayfalar için bir İçerik Güvenliği İlkesi
uygulanıyor.</p>
<p>Tüm I2P-Bote kullanıcılarının sürümleri, Şubat ayı ortasında I2P 0.9.29 sürümünün
yayınlanmasından sonra yönelticilerini yeniden başlattıklarında otomatik olarak yükseltilecek.
Bununla birlikte o zamana kadar olan aralıkta I2P ya da I2P-Bote kullanmayı planlıyorsanız güncellemeyi el ile yapmak için <a href="http://bote.i2p/install/">kurulum sayfasındaki adımları uygulamanız</a> önerilir.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.28 sürümünde, Jetty uygulaması da dahil olmak üzere birlikte sunulan yazılım paketleri için 25 üzerinde Trac bildirimi düzeltildi
Önceki sürümde sunulan IPv&amp; eş sınaması özelliğinde bazı düzeltmeler yapıldı.
Zararlı olabilecek eşleri algılayıp engellemek için geliştirmeler yapıldı.
Java 9 için ek düzeltmeler yapıldı. Bununla birlikte henüz genel amaçlar için Java 9 kullanılmasını önermiyoruz.</p>
<p>I2P ekibi 33C3 numaralı bölümde olacak. Ağı nasıl genişleteceğimiz hakkında fikir vermek için masamıza uğrayabilirsiniz.
Kongrede 2017 önceliklerini ve 2017 yol haritasını gözden geçireceğiz.</p>
<p>Herzamanki gibi tüm kullanıcıların yeni sürüme yükseltmesini öneriyoruz.
Ağa yardımcı olmak ve güvende kalmak için son sürümü kullanmalısınız.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
for this.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 sürümünde bazı hata düzeltmeleri bulunuyor</summary></details><p>0.9.27 sürümünde çeşitli hata düzeltmeleri bulunuyor.
Şifrelemeyi hızlandırmak için güncellenen ve 0.9.26 sürümünde yalnız yeni Debian kurulumları için eklenen GMP kitaplığı şimdi ağ içi güncellemelerine eklendi.
IPv6 aktarımları, SSU eş sınaması ve gizli kip konularında iyileştirmeler yapıldı.</p>
Ağa yardımcı olmak ve güvende kalmak için güncel sürümü kullanmalısınız.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Güvenlik Açığı" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Güvenlik Açığı</summary></details><p>I2P-Bote uygulama ekinin daha önceki sürümlerinde bulunan bir güvenlik açığı I2P-Bote 0.4.4 sürümünde giderildi. Android uygulaması etkilenmedi.</p>
<p>CSRF korumasının olmaması, I2P-Bote çalıştıran bir kullanıcının JavaScript
etkinleştirilmiş bir tarayıcıda kötü amaçlı site bir site yüklemesi durumunda,
diğer taraf kullanıcı adına I2P-Bote üzerinde ileti göndermek gibi işlemleri tetikleyebilir.
Bu da etkinleştirilmiş olabilir
Bu durum, herhangi bir denenmiş güvenlik açığı kanıtı olmasa da, I2P-Bote adreslerinin
kişisel anahtarlarının ortaya çıkarılmasına yol açabilir.</p>
<p>Tüm I2P-Bote kullanıcılarının sürümleri, Aralık ayı ortasında I2P 0.9.28 sürümünün
yayınlanmasından sonra yönelticilerini yeniden başlattıklarında otomatik olarak yükseltilecek.
Bununla birlikte o zamana kadar olan aralıkta I2P ya da I2P-Bote kullanmayı planlıyorsanız güncellemeyi el ile yapmak için <a href="http://bote.i2p/install/">kurulum sayfasındaki adımları uygulamanız</a> önerilir.
Ayrıca I2P-Bote ile çalışırken düzenli olarak JavaScript kullanan sitelere bakıyorsanız yeni
I2P-Bote adresleri üretmeyi de düşünmelisiniz.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.27 sürümünde çeşitli hata düzeltmeleri bulunuyor.
Şifrelemeyi hızlandırmak için güncellenen ve 0.9.26 sürümünde yalnızca yeni Debian kurulumları için eklenen GMP kitaplığı şimdi ağ içi güncellemelerine eklendi.
IPv6 taşıyıcıları, SSU eş sınaması ve gizli kip konularında iyileştirmeler yapıldı.</p>
<p><a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> kampı sırasında çeşitli uygulama ekleri güncellendi. Yönelticiniz yeniden başlatıldıktan sonra otomatik olarak güncellenecek.</p>
<p>Herzamanki gibi tüm kullanıcıların yeni sürüme yükseltmesini öneriyoruz.
Ağa yardımcı olmak ve güvende kalmak için son sürümü kullanmalısınız.</p>
Ağa yardımcı olmak ve güvende kalmak için güncel sürümü kullanmalısınız.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange önerisi" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P Stack Exchange üzerinde önerilen bir site!</summary></details><p>Artık I2P için Stack Exchange üzerinde bir öneri sitesi var!
Lütfen deneme aşamasının başlaması için <a href="https://area51.stackexchange.com/proposals/99297/i2p">kullanın</a>.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 sürümü şifreleme güncellemeleri, Debian paketi geliştirmeleri ve hata düzeltmeleri ile yayınlandı.</summary></details><p>0.9.26 sürümünde doğal şifreleme kitaplığına büyük bir
güncelleme, yeni bir imzalar ile adres defteri abonelik iletişim
kuralı ve Debian/Ubuntu paketleri için büyük gelişmeler var.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 sürümü şifreleme güncellemeleri, Debian paketi geliştirmeleri ve hata düzeltmeleri ile yayınlandı.</summary></details><p>0.9.26 sürümünde doğal şifreleme kitaplığında büyük bir güncelleme,
yeni bir imzalar ile adres defteri aboneliği iletişim kuralı ve
Debian/Ubuntu paketleri için büyük gelişmeler var.</p>
<p>Şifreleme GMP 6.0.0 sürümüne yükseltildi ve şifreleme hızını önemli ölçüde arttıran
daha yeni işlemleciler destekleri de eklendi.
daha yeni işlemleci destekleri de eklendi.
Ayrıca artık yan kanal saldırılarını engellemek için sabit zamanlı GMP işlevleri kullanılıyor.
Not: GMP değişiklikleri yalnız yeni kurulumlar ve Debian/Ubuntu yapımları için etkin. Ağ güncellemelerine ise 0.9.27 sürümünde eklenecek.</p>
Not: GMP değişiklikleri yalnızca yeni kurulumlar ve Debian/Ubuntu yapımları için etkin. Ağ güncellemelerine ise 0.9.27 sürümünde eklenecek.</p>
<p>Debian/Ubuntu yapımları için Jetty 8 ve Geoip gibi bazı paket bağımlılıkları eklendi ve
eşdeğer kodlar kaldırıldı.</p>
<p>Ayrıca zaman içinde tutarsızlık ve başarım düşmesi gibi sorunlara yol açan
zamanlayıcı hatasını da içeren birkaç düzeltme yapıldı.
Herzamanki gibi tüm kullanıcıların yeni sürüme yükseltmesini öneriyoruz.
Ağa yardımcı olmak ve güvende kalmak için son sürümü kullanmalısınız.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 sürümünde SAM 3.3, QR kodları ve hata düzeltmeleri bulunuyor</summary></details><p>0.9.25 karmaşık çoklu iletişim kuralı uygulamalarını destekleyen yeni SAM, v3.3 sürümünü içeriyor.
Ağa yardımcı olmak ve güvende kalmak için güncel sürümü kullanmalısınız.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 sürümü SAM 3.3, QR kodları ve hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.25 sürümünde karmaşık çoklu iletişim kuralı uygulamalarını destekleyen yeni SAM, v3.3 sürümü bulunuyor.
Gizli hizmet adreslerini paylaşmak için QR kodları ve
adresleri gözle ayırt edebilmek için "identicon" görselleri eklendi.</p>
<p>Tek kişi tarafından işletilen bir yöneltici grubunu daha kolay belirtmek için
konsola yeni "yöneltici ailesi" ayar sayfası eklendi.
panoya yeni "yöneltici ailesi" yapılandırma bölümü eklendi.
Ağ kapasitesini ve tünel açma başarımını arttıracak bir kaç değişiklik yapıldı.</p>
<p>Herzamanki gibi tüm kullanıcıların yeni sürüme yükseltmesini öneriyoruz.
Ağa yardımcı olmak ve güvende kalmak için son sürümü kullanmalısınız.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 sürümünde bazı hata düzeltmeleri ve hızlandırmalar bulunuyor</summary></details><p>0.9.24 yeni SAM (v3.2) sürümünü ve çeşitli hata ve hızlandırma düzeltmelerini içeriyor.
Ağa yardımcı olmak ve güvende kalmak için güncel sürümü kullanmalısınız.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 sürümü bazı hata düzeltmeleri ve hızlandırmalar ile yayınlandı</summary></details><p>0.9.24 sürümünde yeni SAM (v3.2) sürümünü ve çeşitli hata ve hızlandırma düzeltmelerini içeriyor.
Bu sürümün çalışması için Java 7 gerekiyor.
En kısa sürede Java 7 ya da 8 sürümüne yükseltmeyi unutmayın.
Java 6 kullanıyorsanız, yönelticiniz otomatik olarak güncellenmez.</p>
<p>Eski ortak günlükleme kitaplığından kaynaklanan sorunları engellemek için kaldırdık.
Çok eski I2P-Bote uygulama ekleri (HungryHobo tarafından imzalanmış 0.2.10 ve altındaki sürümler) IMAP ayarı etkinleştirilmiş ise çöküyor.
Düzeltmek için eski I2P-Bote uygulama ekinizi str4d tarafından imzalanmış güncel sürüm ile değiştirmeniz önerilir.
Ayrıntılı bilgi almak için <a href="http://bote.i2p/news/0.4.3">bu iletiye bakın</a>.</p>
Ayrıntılı bilgi almak için <a href="http://bote.i2p/news/0.4.3">bu iletiye bakabilirsiniz</a>.</p>
<p><a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Kongresi</a> harika oldu ve 2016 proje planlarımızda iyi gidiyor.
Echelon I2P geçmişi ve güncel durumu üzerine konuştu <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">sunumuna buradan erişebilirsiniz</a> (pdf).
Str4d <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> oturumuna katılarak şifreli birleştirme üzerine konuştu. and gave a talk on our crypto migration,
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">sunumuna buradan erişebilirsiniz</a> (pdf).</p>
Str4d <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> oturumuna katılarak şifreleme uygulamalarımız üzerine konuştu.
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">Sunumuna buradan erişebilirsiniz</a> (pdf).</p>
<p>Herzamanki gibi tüm kullanıcıların yeni sürüme yükseltmesini öneriyoruz.
Ağa yardımcı olmak ve güvende kalmak için son sürümü kullanmalısınız.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 sürümünde çeşitli hata düzeltmeleri ve I2PSnark geliştirmeleri bulunuyor</summary></details><p>Merhaba I2P! Bu sürüm zzz tarafından imzalanan 49 sürümden sonra benim tarafımdan imzalanan (str4d) ilk sürüm. İnsanlar dahil, yedekli çalışmamızı gösteren önemli bir sınav.</p>
Ağa yardımcı olmak ve güvende kalmak için güncel sürümü kullanmalısınız.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 sürümü çeşitli hata düzeltmeleri ve I2PSnark geliştirmeleri ile yayınlandı</summary></details><p>Merhaba I2P! Bu sürüm zzz tarafından imzalanan 49 sürümden sonra benim tarafımdan imzalanan (str4d) ilk sürüm. İnsanlar dahil, yedekli çalışmamızı gösteren önemli bir sınav.</p>
<p><b>Temizlik</b></p>
<p>İmza anahtarım iki yıldan uzun zamandır yöneltici güncellemelerinde bulunuyordu
(0.9.9 sürümünden sonra). Son I2P sürümlerinden birini kullanıyorsanız güncelleme
@ -153,32 +549,32 @@ işlemi diğer güncellemeler kadar kolay olur. 0.9.9 öncesindeki bir sürümü
el ile güncelleme hakkındaki bilgiler için ise
<a href="http://i2p-projekt.i2p/en/download#update">buraya bakabilirsiniz</a>.
El ile güncelleme işlemini tamamladığınızda, yöneltici 0.9.23 sürümünü bulup indirebilir.</p>
<p>I2P yazılımını paket yöneticisi ile kurduysanız, değişikliklerden etkinlenmeyecek ve
normal şekilde güncelleme yapabileceksiniz.</p>
<p>I2P uygulamasını paket yöneticisi ile kurduysanız, değişikliklerden etkinlenmeyecek
ve normal şekilde güncelleme yapabileceksiniz.</p>
<p><b>Güncelleme ayrıntıları</b></p>
<p>Routerinfos için yeni ve daha güçlü Ed25519 imzalarına geçme işlemi iyi gidiyor.
ın en az yarısındaki anahtarların değiştiği öngörülüyor. Bu sürümde
anahtar değiştirme işlemi hızlandırıldı. Ağda karışıklık yaratmamak için yönelticiniz
her yeniden başlatmada az sayıda Ed25519 değişimi yapar. Anahtar değişimi
yapıldığında, yeni kimliğin ağ ile bütünleşeceği ilk bir kaç gün bant genişliği
kullanımınız daha düşük olabilir.</p>
<p>Bu sürüm Java 6 destekleyen son sürümdür. En kısa sürede Java 7 ya da 8 sürümüne yükseltmeyi unutmayın. I2P yazılımını yakında yayınlanacak Java 9 ile uyumlu
<p>"Yöneltici bilgileri" (RouterInfo) için yeni ve daha güçlü Ed25519 imzalarına
geçme işlemi iyi gidiyor. ın en az yarısındaki anahtarların değiştiği öngörülüyor.
Bu sürümde anahtar değiştirme işlemi hızlandırıldı. Ağda karışıklık yaratmamak için
yönelticiniz her yeniden başlatmada az sayıda Ed25519 değişimi yapar. Anahtar
değişimi yapıldığında, yeni kimliğin ağ ile bütünleşeceği ilk bir kaç gün bant
genişliği kullanımınız daha düşük olabilir.</p>
<p>Bu sürüm Java 6 destekleyen son sürümdür. En kısa sürede Java 7 ya da 8 sürümüne yükseltmeyi unutmayın. I2P uygulamasının yakında yayınlanacak Java 9 ile uyumlu
olacak şekilde geliştirmeye başladık ve bazı değişiklikler bu sürümde yapıldı bile.</p>
<p>Ayrıca I2PSnark üzerinde bazı küçük geliştirmeler yaparak, routerconsole içine
<p>Ayrıca I2PSnark üzerinde bazı küçük geliştirmeler yaparak, yöneltici panosuna
eski haber ögelerinin görüntülenebileceği yeni bir sayfa ekledik.</p>
<p>Alışıldığı üzere bu sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu son sürümü kullanmaktır.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 sürümünde hata ayıklamaları ve Ed25519 aktarımı bulunuyor</summary></details><p>0.9.22 sürümünde, tamamlanmadan önce takılmaya yol açan i2psnark sorunu çözüldü ve yöneltici bilgilerinin yeni ve daha güçlü Ed25519 imzalarına aktarılması sağlandı. Ağ kargaşası oluşturmamak için yönelticiniz her yeniden başlatılmada yalnız küçük olasılıklı bir Ed25519 dönüşümü yapacak. Anahtar yeniden oluşturulduğunda, yeni kimlik ağ üzerine eklenene kadar bir kaç gün boyunca düşük bant genişliği kullanımı görebilirsiniz. Herşey yolunda giderse, sonraki sürümde yeniden anahtar oluşturma işlemini hızlandıracağız.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 sürümünde hata düzeltmeleri yapıldı ve Ed25519 geçişi başlatıldı</summary></details><p>0.9.22 sürümünde, tamamlanmadan önce takılmaya yol açan i2psnark sorunu çözüldü ve yöneltici bilgilerinin yeni ve daha güçlü Ed25519 imzalarına aktarılması sağlandı. Ağ kargaşası oluşturmamak için yönelticiniz her yeniden başlatılmada yalnızca küçük olasılıklı bir Ed25519 dönüşümü yapacak. Anahtar yeniden oluşturulduğunda, yeni kimlik ağ üzerine eklenene kadar bir kaç gün boyunca düşük bant genişliği kullanımı görebilirsiniz. Herşey yolunda giderse, sonraki sürümde yeniden anahtar oluşturma işlemini hızlandıracağız.</p>
<p>I2PCon Toronto toplantısı çok başarılıydı! Tüm sunum ve görüntülere <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon sayfasından ulaşabilirsiniz</a>.</p>
<p>Alışıldığı üzere bu sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu son sürümü kullanmaktır.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 sürümünde başarım iyileştirmeleri ve hata düzeltmeleri bulunuyor.</summary></details><p>0.9.21 sürümü ağ kapasitesini arttıran çeşitli değişiklikler, floodfill etkinliğini arttıran ve bant
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 sürümü başarım iyileştirmeleri ve hata düzeltmeleri ile yayınlandı.</summary></details><p>0.9.21 sürümü ağ kapasitesini arttıran çeşitli değişiklikler, otomatik doldurma (floodfill) etkinliğini arttıran ve bant
genişliğini daha etkin kullanan özellikler ile yayınlandı.
Paylaşılan istemci tünellerini ECDSA imzaları ile birleştirdik ve ECDSA desteklemeyen siteler için yeni "bir kaç oturum" yeteneğini değerlendiren DSA kullanılmasını sağladık.</p>
<p>2015 yılında Toronta'da yapılacak I2PCon Konferansının konuşmacıları ve takvimi duyuruldu.
Ayrıntılar için <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon sayfasına</a> bakın.
Ayrıntılar için <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon sayfasına</a> bakabilirsiniz.
<a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a> konferansı için yerinizi ayırtın.</p>
<p>Alışıldığı üzere bu sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu son sürümü kullanmaktır.</p>
<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto konuşmacıları ve takvimi duyuruldu" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 konuşmacıları ve takvimi duyuruldu</summary></details><p>2015 yılında Toronta'da yapılacak I2PCon Konferansının konuşmacıları ve takvimi duyuruldu.
Ayrıntılar için <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon sayfasına</a> bakın.
Ayrıntılar için <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon sayfasına</a> bakabilirsiniz.
<a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a> konferansı için yerinizi ayırtın.</p>
</article>
</div>

View File

@ -1,37 +1,438 @@
<div>
<header title="Новини I2P">Стрічка новин, та оновлення роутера</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<header title="Новини I2P">Стрічка новин, та оновлення роутера</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="Реліз 0.9.46" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 з виправлення помилок</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="Реліз 0.9.45" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 з виправлення помилок</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="Реліз 0.9.44" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 з виправлення помилок</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="Реліз 0.9.43" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 з виправлення помилок</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="Реліз 0.9.42" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 з виправлення помилок</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="Реліз 0.9.41" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 з виправлення помилок</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Зантаження повино бути швидше на таких платформах, як Raspberry Pi. Ми виправили кілька помилок, деякі серйозні, що впливають на мережеві повідомлення низького рівня.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="Реліз 0.9.40" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 з нові значки</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="Реліз 0.9.39" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 з покращенною продуктивністью</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="Реліз 0.9.38" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>Цей реліз також має багато виправлень помилок, включаючи декілька проблем із вкладеннями susimail, та виправлення для IPv6 ройтери.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="Звіт про 35C3 проїзд" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P в 35C3</summary></details><p>Майже ціла команда I2P була в 35C3 у Лейпцигу. Мали щоденні зустрічі щоб перевірити останній рік і перевірити наші розробки та дизайн мети для 2019.</p>
<p>Ви можете перевірити Project Vision і новій Roadmap тут</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="Реліз 0.9.37" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 з NTCP2 активований</summary></details><p>0.9.37 забезпечує швидший, більш безпечний транспортний протокол під назвою NTCP2.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="Реліз 0.9.36" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 з NTCP2 та виправлення помилок</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>Цей реліз також має кілька покращення продуктивності та виправлення помилок.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="Реліз 0.9.35" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P буде в HOPE в Нью-Йорку, 20-22 липня. Знайдіть нас і привітайтеся!</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="Реліз 0.9.34" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 з виправлення помилок</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="Реліз 0.9.33" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 з виправлення помилок</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Проблеми з безпекою, що існують майже в кожній системі</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="З новим роком! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Новий рік і I2P в 34C3</summary></details><p>З новим роком від команда I2P!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="Реліз 0.9.32" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 з оновленням консолі</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="Реліз 0.9.31" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 з оновленням консолі</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
@ -39,7 +440,7 @@ This is the first step in a longer-term plan to make the router console more use
We have also added torrent ratings and comments support to i2psnark.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Заклик до перекладачів" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
it if you could set aside a little more time than usual during this release cycle
@ -49,7 +450,7 @@ to give you three weeks to work on them.</p>
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="Реліз 0.9.30" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 оновляє до Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
@ -66,7 +467,7 @@ See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, in
Please be patient.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="Реліз 0.9.29" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 має виправлення помилок</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
@ -74,7 +475,7 @@ We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="Вразливість Безпеки I2P-Bote" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>Вразливість Безпеки I2P-Bote</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
@ -84,7 +485,7 @@ has been implemented for all pages.</p>
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contains bug fixes</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="Реліз 0.9.28" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 має виправлення помилок</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
@ -92,7 +493,7 @@ There are preliminary fixes for Java 9, although we do not yet recommend Java 9
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="Вразливість Безпеки I2P-Bote" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>Вразливість Безпеки I2P-Bote</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
@ -105,7 +506,7 @@ after I2P 0.9.28 is released in mid-December. However, for safety we recommend t
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="Реліз 0.9.27" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 має виправлення помилок</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
@ -113,7 +514,7 @@ There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="Реліз 0.9.26" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
@ -127,7 +528,7 @@ including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contains SAM 3.3, QR codes, and bug fixes</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="Реліз 0.9.25" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 містить SAM 3.3, QR-коди та виправлення помилок</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
It adds QR codes for sharing hidden service addresses with others,
and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
@ -135,7 +536,7 @@ to make it easier to declare that your group of routers is run by a single perso
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="Реліз 0.9.24" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
Your router will not automatically update if you are using Java 6.</p>
@ -149,7 +550,7 @@ Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real Wor
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="Реліз 0.9.23" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
<p><b>Housekeeping</b></p>
@ -164,7 +565,7 @@ and instructions on how to manually update are provided
updated, your router will then find and download the 0.9.23 update as usual.</p>
<p>If you installed I2P via a package manager, you are not affected by the change,
and can update as usual.</p>
<p><b>Update details</b></p>
<p><b>Деталі про оновлення</b></p>
<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
with at least half of the network already estimated to have rekeyed. This
release accelerates the rekeying process. To reduce network churn, your router
@ -178,12 +579,12 @@ with the upcoming Java 9, and some of that work is in this release.</p>
the routerconsole for viewing older news items.</p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="Реліз 0.9.22" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
<p>I2PCon Торонто був великий успіх!
Всі презентації та відео перераховані на <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">сторінці I2PCon</a>. </p>
<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="Реліз 0.9.21" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 випущений з покращенною продуктивністью і з фіксами багів.</summary></details><p>0.9.21 містить декілька змін які додають міцності для мережі, збільшує ефективність floodfills,

View File

@ -0,0 +1,605 @@
<div>
<header title="Tin Tức I2P">Tin tức, và các cập nhật bộ định tuyến</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Đã Ra Mắt" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P Phát Hành 2.6.1</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.
There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
Additional fixes for firewalled IPv6 networks are included.
Tunnel build fixes should result in faster startup for some users.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
Our implementation of the new leaseset specification (LS2) is now complete.
We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
It includes several changes to speed up our UDP transport.
We have split up the configuration files to enable future work for more modular packaging.
We continue work to implement new proposals for faster and more secure encryption.
There are, of course, a lot of bug fixes also.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
including per-client authentication for encrypted leasesets.
The console has an updated I2P logo and several new icons.
We've updated the Linux installer.</p>
<p>Startup should be faster on platforms such as Raspberry Pi.
We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
We disabled the old NTCP 1 transport protocol.
There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
The work continues on refreshing the console with new icons.
As usual, we've fixed lots of bugs also!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
There are numerous performance improvements and bug fixes.</p>
<p>We've removed the midnight and classic themes to reduce the maintenance burden;
previous users of those themes will now see the dark or light theme.
There's also new home page icons, a first step in updating the console.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
We've added support for the latest GeoIP database format.
There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
Work continues on supporting the new "LS2" netdb format.</p>
<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
NTCP2 will be enabled in the next release.</p>
<p>This release also contains several performance improvements and bug fixes.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
We have refreshed the router console to make it easier to understand,
improved accessibility and cross-browser support,
and generally tidied things up.
This is the first step in a longer-term plan to make the router console more user-friendly.
We have also added torrent ratings and comments support to i2psnark.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
to the user interface, we have a larger than normal collection of untranslated
strings that need attention. If you're a translator, we would greatly appreciate
it if you could set aside a little more time than usual during this release cycle
in order to bring the translations up to speed. We have pushed the strings early
to give you three weeks to work on them.</p>
<p>If you're not currently an I2P translator, now would be a great time to get
involved! Please see the
<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
for information on how to get started.</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
This should work for recent, unmodified configurations but may not work for modified or very old setups.
Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
<p>Several plugins are not compatible with Jetty 9 and must be updated.
The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
i2pbote 0.4.6; zzzot 0.15.0.
The following plugins (with current versions listed) will not work with 0.9.30.
Contact the appropriate plugin developer for the status of new versions:
BwSchedule 0.0.36; i2pcontrol 0.11.</p>
<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
Please be patient.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
We now support NTP over IPv6.
We've added preliminary Docker support.
We now have translated man pages.
We now pass same-origin Referer headers through the HTTP proxy.
There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>When showing emails to the user, most fields were being escaped. However, the filenames
of attachments were not escaped, and could be used to execute malicious code in a browser
with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
has been implemented for all pages.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contains bug fixes</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
There are fixes for the IPv6 peer testing feature introduced last release.
We continue improvements to detect and block peers that are potentially malicious.
There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
I2P-Bote plugin. The Android app was not affected.</p>
<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
malicious site in a browser with JavaScript enabled, the adversary could trigger actions
in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
for this.</p>
<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
also consider generating new I2P-Bote addresses if you regularly browse sites with
JavaScript enabled while running I2P-Bote.</p>
</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
a new addressbook subscription protocol with signatures,
and major improvements to the Debian/Ubuntu packaging.</p>
<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
which will speed up crypto operations considerably.
Also, we are now using constant-time GMP functions to prevent side-channel attacks.
For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
we will include them for in-net updates in the 0.9.27 release.</p>
<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
<p>There's a collection of bug fixes also, including a fix for a timer bug
that caused instability and performance degradations over time.
As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contains SAM 3.3, QR codes, and bug fixes</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
It adds QR codes for sharing hidden service addresses with others,
and "identicon" images for visually distinguishing addresses.</p>
<p>We've added a new "router family" configuration page in the console,
to make it easier to declare that your group of routers is run by a single person.
There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
Note that this release is the first to require Java 7.
Please update to Java 7 or 8 as soon as possible.
Your router will not automatically update if you are using Java 6.</p>
<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration,
his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
<p>As usual, we recommend that all users update to this release.
The best way to help the network and stay secure is to run the latest release.</p>
</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
signed by zzz. This is an important test of our redundancy for all things,
including people.</p>
<p><b>Housekeeping</b></p>
<p>My signing key has been in router updates for over two years (since 0.9.9), so
if you are on a recent version of I2P this update should be just as easy as
every other update. However, if you are running an older version than 0.9.9, you
will first need to manually update to a recent version. Update files for recent
versions can be downloaded
<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
and instructions on how to manually update are provided
<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
updated, your router will then find and download the 0.9.23 update as usual.</p>
<p>If you installed I2P via a package manager, you are not affected by the change,
and can update as usual.</p>
<p><b>Update details</b></p>
<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
with at least half of the network already estimated to have rekeyed. This
release accelerates the rekeying process. To reduce network churn, your router
will have a small probability of converting to Ed25519 at each restart. When it
does rekey, expect to see lower bandwidth usage for a couple of days as it
reintegrates into the network with its new identity.</p>
<p>Note that this will be the last release to support Java 6. Please update to
Java 7 or 8 as soon as possible. We are already working to make I2P compatible
with the upcoming Java 9, and some of that work is in this release.</p>
<p>We have also made some minor improvements in I2PSnark, and added a new page in
the routerconsole for viewing older news items.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
If all goes well, we will accelerate the rekeying process in the next release.</p>
<p>I2PCon Toronto was a big success!
All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
and use bandwidth more effectively.
We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
using the new "multisession" capability for those sites that don't support ECDSA.</p>
<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
<p>As usual, we recommend that you update to this release. The best way to
maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto speakers and schedule announced" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 speakers and schedule announced</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
</article>
</div>

View File

@ -1,5 +1,328 @@
<div>
<header title="Ìròyìn 12P">Gbàgede Ìròyìn, àti àfikún-un apínṣẹ̀ìsopọ̀ká</header><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
<header title="Ìròyìn 12P">Gbàgede Ìròyìn, àti àfikún-un apínṣẹ̀ìsopọ̀ká</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
The bug primarily affected high-bandwidth routers.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
We have added notification bubbles to several applications in the console to highlight application messages.
We fixed a tunnel test bug that may have been affecting tunnel reliability.
The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
There are several dark theme fixes and improvements.</p>
<p>We fixed the installer that previously failed on Java 21 or higher.
We also fixed installing to directory paths that contain spaces on Linux.
For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
The workaround is using localhost and the server port, usually 7658, to bypass I2P.
For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
We apologize for the issue and are working on a fix.</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
<p>We have improved handling of congested routers in the network.
Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
<p>Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.</p>
<p>Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
<p>Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.</p>
<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
Reachability of I2P sites is badly degraded.</p>
<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
<p>New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.</p>
<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.</p>
<p>The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
The attacker then sends the same message directly to the router.
The router passes the message to the bloom filter, and is dropped.
This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
Users of Java I2P are recommended to update immediately to avoid the attack.</p>
<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
<p>This release also contains a tweakable blocklist.
Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
This feature is off-by-default and is only recommended for advanced users at this time.</p>
<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
This issue has also been resolved.
The docker container is now also compatible with Podman.</p>
<p>This release syncs translations with transifex and updates the GeoIP database.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
We thank zzz for providing these services for such a long time.</p>
<p>As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
Our investigations and mitigations continue.</p>
<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
We ask for your patience as we work to improve I2P.</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
Mitigation strategies are being investigated and implemented gradually.</p>
<p>While the attack has degraded performance, the network remains intact and usable.
Java I2P routers appear to be handling the issues better than i2pd routers for now.
Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
possibly triggered by Bitcoin's new I2P transient address feature,
but made worse by our SSU2 bugs and other congestion control problems.
We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
We have improved our algorithms to reduce network load during times of congestion.
We are also collaborating with i2pd to develop common congestion control strategies.</p>
<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
i2pd released their version 2.45.0 last week and the early results are encouraging.
New protocols, and distributed networks, are difficult to develop.
Congestion can arrive with little warning and with little clue of the cause.
Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
<p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
<p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
with a small number of volunteer testers.
This release completes the implementation, including relay and peer testing.
We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
This will allow us to do much more testing in the next three months, finish the connection migration feature,
and fix any remaining issues.
We plan to enable it for everyone in the next release scheduled for November.
No manual configuration is necessary.</p>
<p>Of course, there's the usual collection of bug fixes in this release as well.
We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
<p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
your HTTP proxy tunnel.
As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
to specify <b>exit.stormycloud.i2p</b>
in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
After editing, <b>scroll down and click Save</b>.
See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
<p>Router updates will not update your configuration, you must edit it manually.
Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
the router, I2CP, and UPnP.
Router fixes address bugs in soft restart, IPv6, SSU peer testing,
network database stores, and tunnel building.
Router family handling and Sybil classification have also been
significantly improved.</p>
<p>Together with i2pd, we are developing our new UDP transport, SSU2.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing the full cryptography upgrade we started about 9 years ago.
This release contains a preliminary implementation which is disabled by default.
If you wish to participate in testing, please look for current information
on zzz.i2p.</p>
<p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
their JVM or switch to a version which does not contain the vulnerability, below
Java 15.</p>
<p>New I2P Easy-Install bundles have been generated using the latest release of the
Java Virtual Machine. Further details have been published in the respective
bundle newsfeeds.</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
<p>There are now popup messages in the system tray, for those platforms that support it.
i2psnark has a new torrent editor.
The NTCP2 transport now uses much less CPU.</p>
<p>The long-deprecated BOB interface is removed for new installs.
It will continue to work in existing installs, except for Debian packages.
Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
We were aware of the problem soon after the release, but it took us almost two months to find the cause.
We eventually identified it as a bug in i2pd 2.40.0,
and the fix will be in their 2.41.0 release coming out about the same time as this release.
Along the way, we've made several changes on the Java I2P side to improve the
robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
This should help the network be more robust even in the presence of buggy or malicious routers.
Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
together in an isolated test network, so we can find more problems before the releases, not after.</p>
<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
and have started implementation.
SSU2 will bring substantial performance and security improvements.
It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
completing a full cryptography upgrade that started about 9 years ago.
We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
<p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
<p>We added a theme selection panel to the new install wizard.
We've improved SSU performance and fixed an issue with SSU peer test messages.
The tunnel build Bloom filter was adjusted to reduce memory usage.
We have enhanced support for non-Java plugins.</p>
<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
<p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
This does not signify a major API change, or a claim that development is now complete.
It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
We continue the transition of the network's routers to X25519 encryption.
Of course there are also numerous bug fixes and performance improvements.</p>
<p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
It does not affect the console plugin, and is not related to the previously-announced plugin issue.
If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
on July 15, 2021.</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
It does not affect the standalone desktop client.
If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
for more information about the vulnerability and updated security recommendations.</p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
<p>We have finally fixed some longstanding SusiMail corruption bugs.
Changes to the bandwidth limiter should improve network tunnel performance.
There are several improvements in our Docker containers.
We have improved our defenses for possible malicious and buggy routers in the network.</p>
<p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
(Destinations have been using this encryption for a few releases now)
We've been working on the specifications and protocols for new encryption for several years,
and we are getting close to the end of it! The migration will take several releases to complete.</p>
<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
(randomly selected at restart) will be using the new encryption.
If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
This is normal, because your router has generated a new identity.
Your performance should recover after a while.</p>
<p>We have "rekeyed" the network twice before, when changing the default signature type,
but this is the first time we've changed the default encryption type.
Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
<p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
We have added preliminary support for new tunnel build message encryption (proposal 152).
There are significant performance improvements throughout the router.</p>
<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
Users on that platform should upgrade so you may continue to receive I2P updates.</p>
<p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
The Sybil analysis and blocking tool is now enabled by default.</p>
<p>Java 8 or higher is now required.
Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
<p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
<p>Windows users only:
This release fixes a local privilege escalation vulnerability
which could be exploited by a local user.
Please apply the update as soon as possible.
Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
Users on those platforms must upgrade to receive future I2P updates.</p>
<p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
There's an update to the console dark theme.
We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
<p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
All users should update as soon as possible.</p>
<p>The release includes initial support for new end-to-end encryption (proposal 144).
Work continues on this project, and it is not yet ready for use.

View File

@ -1,31 +1,373 @@
<div>
<header title="I2P 新闻">新闻信息、路由器更新信息&lt;br&gt;</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<header title="I2P 新闻">新闻订阅和软件更新</header><article id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a" title="2.9.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released" author="idk" published="2025-06-02T19:00:00Z" updated="2025-06-02T19:00:00Z"><details><summary>I2P 2.9.0 版本</summary></details><p>I2P 2.9.0 是一个维护版本,包括错误修复和新功能开发。</p>
<p>改进了线程使用以提高 i2ptunnel 系统的性能。改进了 NTCP2 以抵御探测攻击。通知系统已集成到更多应用程序中,以便从 I2PSnark 和其他应用程序向用户提供更好的反馈。自动播种的注册问题已被修复。用户在参与播种时可能会观察到更多的资源使用情况。如果不希望出现这种情况,可在 /config 页面上禁用播种模式。</p>
<p>控制台中新增了全局地图功能,可在网络数据库视图中显示路由器位置。这些都是帮助路由器建立隧道和匿名提供服务的对等节点。</p>
<p>关于隧道的自动带宽管理、数据报 2 协议和后量子密码学的实现工作仍在继续。在两个版本后,即 2.11.0I2P 将需要 Java 17。</p>
<p>如往常一样,我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
</article><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 版本</summary></details><p>2.8.2 修复了 2.8.1 版本中引入的导致 SHA256 失败的错误。该错误主要影响高带宽路由器。</p>
<p>如往常一样,我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 版本</summary></details><p>2.8.1 修复了 2.8.0 中本地站点访问问题。我们在控制台中为多个应用程序添加了通知气泡,以突出显示应用程序消息。我们修复了可能影响隧道可靠性的隧道测试错误。地址簿现在新增了“最新”标签页,用于显示您订阅中添加的最新主机名。此外,我们还修复了多项深色主题问题并进行了改进。</p>
<p>我们修复了之前在 Java 21 或更高版本上失败的安装程序。 我们还修复了在 Linux 上安装到包含空格的目录路径的问题。 对于使用 Docker 的用户,我们更新了过时的 Docker 容器和容器库。</p>
<p>如往常一样,我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="2.8.0 访问本地站点失败" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 本地访问错误</summary></details><p>在 2.8.0 中,浏览本地站点(通过主机名或 b32将失败。
解决方法是使用 localhost 和服务器端口(通常为 7658来绕过 I2P。
例如,<a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>
我们对此问题深表歉意并努力修复中。</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 版本" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 版本</summary></details><p>此版本通过修复错误、删除未使用的代码以及提高网络稳定性以改进 I2P。</p>
<p>我们改进了网络中拥堵的路由器的处理。
UPnP 和 NAT 遍历的问题已解决,以改善连接性和错误回报。
我们现在有一个更激进的策略来从 NetDb 中删除赁集,以提高路由器性能并减轻过载。
另外有一些降低事件可观察性的更改,如路由器重启或关闭等。</p>
<p>如往常一样,我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 已发布</summary></details><p>本次发布I2P 2.7.0 继续修复错误,提高性能以及添加功能。</p>
<p>从控制台和应用程序的信息访问已得到改进。
I2PSnark 和 SusiMail 搜索中的问题已得到修复。
路由器控制台中嵌入的 netDB 搜索的使用方式现在更直观、更实用。
高级模式下的诊断显示亦有少量改进。</p>
<p>另外修复了一些错误以提高网络内的兼容性。
一个赁集发布的问题已解决,提高了主要隐藏服务的可靠性。
当用户仅更改现有种子上的跟踪器时I2PSnark 不再更改信息哈希。
这可以防止种子因这些更改而受到不必要的干扰。
我们欢迎这份来自新贡献者的工作。
在处理流媒体库选项时的冲突已被解决以提高与其他 I2P 实现的兼容性。</p>
<p>如往常一样,我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 版本</summary></details><p>I2P 2.6.1 的发布是为了修复隐藏服务管理器应用程序中的用户界面错误。
此错误导致滚动被禁用,从而使某些配置无法访问。</p>
<p>如往常一样,我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 版本</summary></details><p>本次发布的 I2P 2.6.0 版本继续致力于修复漏洞、添加新功能并提升网络的可靠性。</p>
<p>当选择洪泛路由时,较新的路由将受到青睐。
I2PSnark 除了修复漏洞之外还获得了一些功能这些功能可以提高PeX对等节点交换的性能。
遗留的旧传输协议正在被移除因此简化了UDP传输代码。
本地主机上的目标节点将可以直接被本地客户端访问,而不需要请求它们的赁集,这可以提高性能和可测试性。
另外对对等节点的选择策略进行了一些额外的调整。</p>
<p>I2P 不再允许通过 Tor 建立 I2P 连接,从 Tor 出口IP地址建立的连接现在已被阻止。
我们不鼓励这样做因为它会降低I2P的性能并浪费Tor出口节点的资源而无任何益处。
如果您既运行Tor出口路由又运行I2P我们鼓励您继续这样做为两者使用不同的IP地址。
非出口节点和Tor客户端不受此影响无需任何更改。</p>
<p>如往常一样,我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 发布" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 包含 HTTP 修复</summary></details><p>I2P 2.5.2 版本是为了修复在 2.5.0 中引入的导致某些 HTTP 内容被截断的错误。</p>
<p>如往常一样,我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P 版本 2.5.1 已发布以解决拒绝服务攻击</summary></details><p>I2P 2.5.1 的发布是为了解决影响 I2P 网络和服务的拒绝服务攻击。
在此版本中,我们禁用了 Sybil 攻击检测工具的基于 IP 的部分,这些部分旨在放大攻击的影响和持续时间。
这应该有助于网络恢复正常运行。
那些已禁用 Sybil 攻击检测工具的人可以安全地重新启用它。
其他子系统也进行了调整,以改进路由信息验证和对等节点选择。</p>
<p>如往常一样,我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="暴风雨天气" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>网络天气:暴风雨。 I2P 正在遭受攻击。</summary></details><p>I2P 网络目前正遭受拒绝服务攻击。
此攻击以不同的方式影响 I2P 和 i2pd并对网络健康状况造成严重影响。
I2P 站点可达性严重下降。</p>
<p>如果您在 I2P 内部托管服务,并且该服务托管在洪泛路由上,则应考虑在禁用 Floodfill 的路由器上对该服务采用多宿主形式,以提高可达性。
其他缓解措施正在讨论中,但长期的、可向后兼容的解决方案仍需进一步研究。</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="新版本 I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>更多应用改善NetDB隔离策略审计</summary></details><p>该版本 I2P 2.5.0 比 2.4.0 版本提供了更多面向用户的改进,后者侧重于实施 NetDB 隔离策略。</p>
<p>I2PSnark增加了一些新功能比如搜索种子。
若干错误已经修复以提高与其他I2P种子客户端如 BiglyBT 和 qBittorrent 的兼容性。
我们要感谢所有与libtorrent和qBittorrent合作的开发人员他们支持并改进了I2P支持。
SusiMail还增加了一些新功能包括支持邮件中的Markdown格式和将附件拖放到邮件中的功能。
使用隐藏服务管理器创建的隧道现在支持“Keepalive”这提高了性能和与网络技术的兼容性使更复杂的I2P站点成为可能。</p>
<p>在此版本中,我们还对 NetDB 进行了一些调整,以增强其对垃圾信息的韧性,并提高路由器阻挡可疑消息的能力。
这是“审计” 2.4.0 版本中“子数据库隔离”防御实现的一部分。
此次调查发现了一个小的隔离穿透事件并修复之。
这个问题是 I2P 团队在内部发现并修复的。</p>
<p>在这个版本中我们对发布Android和Windows下游发行版的过程进行了一些改进。
这将改善这些下游产品的交付和可用性。</p>
<p>如往常一样,我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 发布包含 Congestion 和 NetDB 安全提升" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 发布包含 Congestion 和 NetDB 安全提升</summary></details><p>此版本 I2P 2.4.0 持续努力提高 I2P 网络的安全性和稳定性。
其中包含对网络数据库的大幅改进,网络数据库是 I2P 网络中用于发现对等节点的基本结构。</p>
<p>拥塞控制的改进将使路由器能够通过避开拥堵的对等节点从而提高网络稳定性。
这将有助于网络限制隧道垃圾信息造成的影响。
它还将有助于在 DDOS 攻击期间和之后修复网络。</p>
<p>NetDb 的更改还有助于保护各个路由器以及使用它们的应用程序的安全。
路由器现在可以通过将 NetDB 分成多个“子DB”来防御攻击者我们使用这些“子DB”来防止应用程序和路由器之间的信息泄漏。
这同时改进了 Java 路由器可用的有关其 NetDB 活动的信息,并简化了我们对多宿主应用程序的支持。</p>
<p>还包括 I2PSnark 和 SusiMail 应用程序中的许多错误修复和功能增强。</p>
<p>如往常一样,我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
</article><article id="urn:uuid:" title="I2P 2.3.0 新版本 - 安全修复可调的黑名单DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - 安全修复可调的黑名单DTG API</summary></details><p>此版本包含 CVE-2023-36325 的修复。
CVE-2023-36325 是一个发生在布隆过滤器中的上下文混淆错误。
攻击者制作包含唯一 messageID 的 I2NP 消息,并将该 messageID 发送给客户端。
该消息在通过布隆过滤器后,不允许在第二条消息中重复使用。
随后,攻击者将相同的消息直接发送给路由。
路由器将消息传递给布隆过滤器并被丢弃。
这泄露了之前已经看到的 messageID 信息,使攻击者有充分的理由相信路由器承载了客户端。
这个问题已经通过将布隆过滤器的功能分离到不同的上下文中得到了解决,这些上下文中是基于消息是通过客户端隧道,还是探测隧道直接发送到路由的。
在正常情况下,这种攻击需要数天才能成功执行,并且可能受到攻击期间路由重启和对误报的灵敏度等若干因素的干扰。
建议使用 Java I2P 的用户立即更新以免受攻击。</p>
<p>在修复这个上下文混淆错误的过程中,我们修改了一些策略来防御这类型的泄漏。
这包括对 netDb 的调整、速率限制机制和洪泛路由的行为。</p>
<p>此版本添加了 not_bob 作为第二个默认hosts来源并把<a href="http://notbob.i2p">notbob.i2p</a><a href="http://ramble.i2p">ramble.i2p</a>添加到控制台主页。</p>
<p>这个版本还包含一个可调整的黑名单。
黑名单是半永久性的每个被封禁的IP地址会被一直屏蔽直到路由器重新启动。
在 sybil 攻击期间观察到黑名单爆炸性增长的用户可以通过将黑名单配置为按一定时间段使条目过期来缩短超时间隔。
此功能在默认情况下是关闭的,目前仅建议高级用户使用。</p>
<p>该版本还包括一个API用于使用桌面GUI(DTG)修改插件。
现在可以将菜单项添加到系统托盘中,从而更直观地启动使用本地应用接口的插件。</p>
<p>如往常一样,我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="新版本 2.2.1包含DockerUbuntu Lunar和Debian Sid的打包修复" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - 2.2.0 的维护修复</summary></details><p>I2P 2.2.0 版本向前推进以加快缓解 DDOS 攻击后,我们了解到一些开发问题,因此有必要构建和发布新包。
此发布修复了 Ubuntu Lunar 和 Debian Sid 中的一个问题,即使用更新后的版本的 jakarta 包无法访问路由器控制台。
Docker 包未正确读取参数,导致无法访问配置文件。
此问题也已解决。
docker 容器现在也与 Podman 兼容。</p>
<p>本发布与 transifex 同步翻译并更新 GeoIP 数据库。</p>
<p>如往常一样,我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="新版本 2.2.0包含DDOS攻击的缓解措施和 Streaming 子系统的调整" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>DDOS攻击的缓解措施和 Streaming 子系统的调整</summary></details><p>我们已选择将 2.2.0 的发布日期提前到今天,即 2023 年 3 月 13 日。
此版本包括对网络数据库、洪泛和节点选择组件的修改,提高了路由器抵御 DDOS 攻击的能力。
攻击可能会持续进行,但对这些系统的改进将通过帮助路由识别和降低路由评分来帮助减轻 DDOS 攻击的风险。</p>
<p>此版本还为 Streaming 子系统添加了重放保护,以防止可以捕获加密数据包的攻击者通过将其发送给意外的接收者来重新使用它。
这是一个向后兼容的更改,因此旧路由器仍然能够使用新路由器的流媒体功能。
此问题由 I2P 开发团队在内部发现并修复,与 DDOS 攻击无关。
我们从未在实际环境遇到过重放流数据包,并且不相信此时针对 I2P 网络发生过流重放攻击。</p>
<p>您可能已经注意到,这些发行说明和发行版本身已由 idk 而非 zzz 签署。
zzz 已选择退出该项目,他的职责由其他团队成员承担。
因此,该项目正致力于更换网络统计基础设施并将开发论坛移至 i2pforum.i2p。
我们感谢 zzz 长期以来提供这些服务。</p>
<p>如往常一样,我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS 消息进展" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS 消息进展</summary></details><p>我们已经确认攻击者控制了大量的路由器。
我们的调查和缓解措施仍在继续当中。</p>
<p>这是提醒人们即使在 20 年后I2P 网络规模仍然相对较小的好时候。
我们没有证据表明攻击者正试图对任何特定用户或隐藏服务进行去匿名化。
但是,如果您有高风险威胁模型,您应该仔细考虑 I2P 目前是否提供了您需要的保护。
从长远来看,最好的解决方案是宣传并发展 I2P 网络以提高我们用户的安全性。</p>
<p>我们将在有必要时在新闻推送和<a href="http://zzz.i2p">zzz.i2p</a>提供更多信息。
在我们努力改进 I2P 的过程中,请您耐心等待。</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="关于最近的拒绝服务攻击" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P 保持完好,但性能受损</summary></details><p>I2P 网络目前正受到拒绝服务攻击的影响。
网络的洪泛功能受到影响,导致响应中断,隧道构建成功率下降。
网络参与者在连接到 I2P 站点和使用 I2P 服务时遇到困难。
我们在正在逐步调查和实施缓解策略。</p>
<p>虽然攻击降低了性能,但网络仍然完好无损且可用。
目前Java I2P 路由器似乎比 i2pd 路由器能更好地处理这些问题。
下周,各种缓解措施应该会开始出现在 Java 和 C++ 路由器的开发版本中。</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 包含大量 SSU2 修复</summary></details><p>自 11 月发布 2.0.0 以来,我们获知了一些情况。
随着路由器更新到该版本,网络对我们新的 SSU2 传输协议的支持率从大约 1% 提高到 60% 以上。
首先,我们已经确认 SSU2 是一个可靠、设计良好且安全的协议。
其次,我们发现并修复了协议推行中的许多小错误或很少触发的错误。
这些错误累积起来的影响降低了网络的性能。</p>
<p>此外,我们还注意到网络中隧道数量的增加和隧道构建成功率的下降,
可能是由比特币新的 I2P 临时地址功能触发的,
但由于我们的 SSU2 错误和其他拥塞控制问题而变得更差。
我们正在与比特币和其他非比特币项目合作,以减少 I2P 网络需求。
我们改进了算法以减少拥塞期间的网络负载。
我们还与 i2pd 合作开发通用的拥塞控制策略。</p>
<p>因此,我们将此版本的发布时间加快了大约六周,以便向所有人发布修复程序。
i2pd 上周发布了他们的 2.45.0 版,早期的结果令人鼓舞。
新协议和分布式网络的开发很困难。
拥塞可能会在没有任何警告和原因的情况下出现。
感谢您的耐心等待,因为我们已经诊断并希望解决问题。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
We add support for IGD2 schemas in UPnP.
There's also preparation for more improvements you will see in future releases.</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 全面启用</summary></details><p>I2P 2.0.0版本在完成了小特性开发、测试和若干错误修复以后还为所有用户启用了我们新的SSU2协议。</p>
<p>我们也修复了各种问题包括安装包、网络数据库、私有地址簿添加Windows浏览器启动程序和IPv6 UPnP。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
We now set rate limits by default in the hidden services manager.
For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="最近的博客文章" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>部分最近的博客文章</summary></details><p>这是我们网站部分最近的博客文章的链接:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">有关我们新的 SSU2 协议的概述</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">有关I2P币及其他骗局的警告</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">与divs.exchange的Konrad的访谈</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">与StormyCloud的Dustin的访谈</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 包含 SSU2 测试</summary></details><p>我们在过去的三个月里与少量志愿测试者一起研究我们新的UDP传输协议 "SSU2"
这个版本完成了完整的实现,包括中继和对等节点测试。
我们默认在安卓和ARM平台上启用它并在一小部分其它路由上随机启用。
这将使我们能够在未来三个月内做更多的测试,完成连接迁移功能,
并修复任何剩余的问题。
我们计划在11月发布的下一个发布版本中为所有人启用该功能
无需手动配置。</p>
<p>当然,这个发布版本也包含了一些常见的错误修复。
我们还增加了一个自动死锁检测器,它已经找出一个很少见的死锁。这个死锁已经被修复。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
Please update your systems as soon as available and possible.</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place.
Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
<p>Also we did hand out lots of stickers and gave information about our project to anyone asking.
Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
We have added some checks in the console to resist rebinding attacks.</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="新出口代理 exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>新出口代理</summary></details><p>I2P出口代理exit nodes可以使你通过一个HTTP代理隧道访问互联网。
在我们的 <a href="http://i2p-projekt.i2p/en/meetings/314">月度会议</a>上,
<b>exit.stormycloud.i2p</b> 已经成为我们官方推荐的出口代理,替代早已死去的 <b>false.i2p</b>
欲了解 <a href="http://stormycloud.i2p/"> StormyCloud 组织</a>的更多信息,请访问
<a href="http://stormycloud.i2p/outproxy.html">出口代理</a>
<a href="http://stormycloud.i2p/tos.html">服务条款</a>
<a href="http://stormycloud.i2p/">StormyCloud 网站</a> </p>
<p>我们建议你修改 <a href="/i2ptunnel/edit?tunnel=0">匿名服务管理器配置</a>来确保 <b>exit.stormycloud.i2p</b>存在于两个地方: <b>出口代理</b><b>SSL出口代理</b>
修改之后,<b>向下滑、点击保存</b>
<a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">在我们的博客文章上查看截图</a>
你可以在 <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob的博客</a>上查看Android版的说明和截图。</p>
<p>路由器更新不会更新你的配置,你必须手动修改。
非常感谢 StormyCloud 的支持。如果可能的话,请考虑<a href="http://stormycloud.i2p/donate.html">给他们捐赠</a></p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 包含错误修复</summary></details><p>本发布包含i2psnark
路由器I2CP和UPnP的错误修复。
修复了路由器软重启、IPv6、SSU 对等节点测试、网络数据库存储和隧道构建中的地址错误。
路由家族处理和Sybil分级也明显改善了。</p>
<p>和i2pd一起我们开发了新的UDP传输SSU2。
SSU2将带来实质性的性能和安全性改进。
它还将让我们最终替换我们最后使用的非常慢的 ElGamal 加密,
完成我们从约9年前开始的加密升级。
本发布包含一个默认关闭的初步发行。
如果你想参与测试请关注zzz.i2p的当前消息。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="安装必要的 Java/Jpackage 升级" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>最近Java的“Psychic Signatures”漏洞影响到I2P。当前Linux的I2P用户或任何正在使用非捆绑JVM的I2P用户应当更新
他们的JVM或切换到 Java 15 以下
不包含该漏洞的版本。</p>
<p>新的I2P一键安装包已使用
JVM的最新发布生成。更多详情已发布在各
同捆包的新闻源中。</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 包含可靠性和性能提升</summary></details><p>1.7.0 发布包含若干性能和可靠性的改善。</p>
<p>对于支持的平台,现在系统托盘中会弹出信息。
i2psnark 现在有一个新的种子编辑器。
还大大降低了 NTCP2 的CPU占用。</p>
<p>在新安装中,长期不受支持的 BOB 接口已被移除。
除了 Debian 包以外,现有的安装将继续使用之。
其余任何 BOB 应用的用户都应该要求开发人员切换到 SAMv3 协议。</p>
<p>我们得知自 1.6.1 发布以来,网络可靠性不断恶化。
我们在发布以后很快就意识到了这个问题,然而我们花了近两个月才找到原因。
我们最终确认为 i2pd 2.40.0 中的一个bug
这个修复将在 2.41.0 中和这个版本几乎同时发布。
在此过程中,我们在 Java I2P 中做了一些修改,以改善
网络数据库查找和存储的健壮性,并在隧道节点选择中避开性能较差的对等节点。
这将使网络在存在异常路由或恶意路由的情况下更稳定。
此外,我们正在启动一个联合项目,在同一个隔离的测试网络中测试 i2pd 和 Java I2P 路由
的预发布版本,这样我们就可以在发布前而不是发布以后发现更多问题。</p>
<p>其他方面,我们在设计新的 UDP 传输“SSU2”提案159
中继续取得重大进展并开始推行。
SSU2 将带来实质上的性能和安全提升。
这还将让我们能最终取代最后使用的,非常慢的 ElGamal 加密,
完成约9年前开始的全加密升级。
我们预计很快就会开始和 i2pd 进行联合测试,并在今年晚些时候向全网络推出。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 启用新的隧道搭建信息</summary></details><p>该发布完成了2021年开发的两个主要协议更新的推出。
为路由迁移至 X25519 加密的步伐加快了,我们预计绝大部分路由在今年年底能完成切换。
短隧道构建信息已启用以减少带宽使用。</p>
<p>我们为新安装向导增添了一个主题选择面板。
我们改善了 SSU 表现,修复了一个 SSU 对等节点测试信息的问题。
调整了隧道构建布隆过滤器以降低内存使用。
我们改善了非Java插件的支持。</p>
<p>另外,我们在设计新的 UDP 传输协议 SSU2 方面取得了重大进展,预计明年年初开始推行。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 包含新的隧道搭建信息</summary></details><p>是的没错,在 0.9.x 发布9年后我们直接从 0.9.50 跳到 1.5.0。
这并不意味着有重大的API更改也不意味着开发已经完成。
这仅仅是对近20年来为我们的用户提供匿名和安全的工作的认可。</p>
<p>此发布完成了更小的隧道构建消息的实现从而减少带宽使用。
我们继续迁移网络的路由至 X25519 加密。
当然也有许多错误修复和性能提升。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Muwire 桌面版漏洞" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire 桌面版漏洞</summary></details><p>Muwire 桌面版应用的独立安装包中发现一个安全漏洞。
其不影响控制台插件,并和以往发现的插件问题无关。
如果你正在运行 Muwire桌面版应用你应当立即<a href="http://muwire.i2p/">升级到 0.8.8</a></p>
<p>问题详情将在2021年7月15日于<a href="http://muwire.i2p/security.html">muwire.i2p</a>公布。</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Muwire 插件漏洞" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire 插件漏洞</summary></details><p>Muwire 插件中发现一个安全漏洞。
其不影响桌面客户端的独立安装包。
如果你正在运行 Muwire 插件,你应当立即<a href="/configplugins">升级到 0.8.7-b1</a></p>
<p>更多有关漏洞和及时的安全建议的信息见于<a href="http://muwire.i2p/security.html">muwire.i2p</a></p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 包含 IPv6 修复</summary></details><p>0.9.50 继续为路由加密密钥迁移至 ECIES-X25519。
我们已为补种启用 DNS over HTTPS 以保护用户免受被动 DNS 窥探。
还有若干对 IPv6 地址的修复和提升,包括新的 UPnP 支持。</p>
<p>我们终于修复了一些 SusiMail 长期存在的错误。
对带宽限制器的修改应该能改善网络隧道表现。
在我们的 Docker 容器有几处改善。
我们已经提升了对网络中可能的恶意和异常路由的防御。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 包含SSU修复及更快速的加密</summary></details><p>0.9.49 继续使 I2P 更快更安全。
我们对 SSU (UDP) 传输做了若干改进和修复,速度应有所提高。
同时此发布开始为路由迁移至新的,更快的 ECIES-X25519 加密。
(至今目标地址采用此加密已有数个发布)
这几年,我们一直致力于新加密的规范和协议,
现已经接近尾声了!迁移会在数个发布中完成。</p>
<p>对于此发布,为尽量减少中断,只有新安装的以及极小比例的现有安装
(重启时随机选择)会采用新加密。
如果你的路由确实“重新键入”以使用新加密,在你重启后的几天内,它可能会比平时流量更少或可靠性更低。
这是正常现象,因为你的路由生成了一个新的身份。
你的路由性能随后会恢复正常。</p>
<p>以往我们在改变默认签名类型时已两次“重新键入”网络,
但这是首次更改默认加密方式。
希望一切都能顺利进行,我们正逐步确定。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 包含性能提升</summary></details><p>0.9.48 在大多数服务上启用了我们的新端到端加密协议提案144
我们已经添加对新隧道建立的信息加密提案152的初步支持。
整个路由的性能都有显著提高。</p>
<p>Ubuntu Xenial (16.04 长期支持版) 的软件包已不再支持。
使用该平台的用户应当升级以继续获得 I2P 更新。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 启用了新的加密</summary></details><p>0.9.47 在一些服务中默认启用了我们的新端到端加密协议(提案 144
Sybil 分析和屏蔽工具现在已默认启用。</p>
<p>现在需要 Java 8 或更高版本。
Debian 软件包 Wheezy 和 Stretch以及 Ubuntu 软件包 Trusty 和 Precise 现已不再支持。
使用上述平台的用户需要升级以继续获得 I2P 更新。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 包含错误修复</summary></details><p>0.9.46 包含 streaming 库显著的性能提升。
我们已经完成了 ECIES 加密提案144的开发现在可以选择启用它以进行测试。</p>
<p>仅 Windows 用户:
本发布修复了一个可被本地用户利用的本地提权漏洞。
请尽快应用更新。
感谢 Blaze Infosec 披露此问题。</p>
<p>这是最后一个支持 Java 7、Debian 软件包 Wheezy 和 Stretch 以及 Ubuntu 软件包 Precise 和 Trusty 的发布。
使用上述平台的用户务必升级以获得未来的 I2P 更新。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 包含了错误修复</summary></details><p>0.9.45包含了隐身模式和带宽测试的重要修复。
这是一个对于控制台暗色主题的更新。
我们继续努力提高性能并开发新的端到端加密(提案 144)。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 发布" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 包含了错误修复</summary></details><p>0.9.44 包含一个隐藏服务处理新加密类型中拒绝服务问题的重要修复。所有用户都应尽快更新。</p>
<p>发布版本包含新端到端加密的初始支持(提案 144。此项目上的工作仍在继续尚未准备好使用。有一些控制台主页的更改及 i2psnark 中新的嵌入式 HTML5 媒体播放器。包含对受到防火墙限制的 IPv6 网络的额外修复。隧道建立的修复应当使得一些用户更快的启动。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 包含了错误修复</summary></details><p>在 0.9.43 发布版本中,我们继续致力于更强的安全性,隐私功能和性能提升。我们的新的租契集规范 (LS2) 实现现在已完成。我们正在开始用于未来发布版本的更强大快速的端到端加密(提案 144实现。一些 IPv6 探测问题已修复,当然还有一些其他错误修复。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 包含了错误修复</summary></details><p>0.9.42 继续使 I2P 更快更稳定.
此版本包含了几处改动以提高 UDP 传输速度。
我们拆分了设置文件,以便将来进一步模块化。
我们将继续努力,将关于更快、更安全的加密的建议付诸实践。
理所当然地, 还有许多错误修复。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 包含了错误修复</summary></details><p>0.9.41 继续着手落实提案 123 引入的新功能,
包括对加密的租契集做客户端级别的身份验证。
控制台的 I2P 标志及若干图标已更新。
更新了 Linux 安装程序。</p>
<p>启动速度在树莓派Raspberry Pi等平台上更快了。
已修正若干缺陷,包括部分严重影响底层网络消息的问题。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 有新的图标</summary></details><p>0.9.40 支持新的租契集格式。
我们已禁用旧的 NTCP 1 传输协议。
有一个新的 SusiDNS 导入功能,以及一个用于传入连接的新的脚本化过滤机制。</p>
<p>我们对 OSX 原生的安装程序做了很多改进,以及更新了 IzPack 安装程序。
继续使用新的图标焕新控制台。
如往常一样,我们还修复了许多缺陷!</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 带有性能提升</summary></details><p>0.9.39 包含了针对新网络库格式的大量更新(proposal 123).
我们将 i2pcontrol 插件作为一个 webapp 打包进来从而支持 RPC 应用的开发.
另外还有众多的性能提升和bug修复.</p>
<p>我们移除了午夜和经典主题以减轻维护压力.
之前使用这些主题的用户现在将会看到暗或者亮色调主题.
另外主页有了新的的图标,这是控制台更新的第一步.</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 含有全新安装向导</summary></details><p>0.9.38 含有一个若为首次安装则会启动的向导还有一个带宽测试器。我们已经支持最新的GeoIP数据库格式。我们的网站上有一个新的配置Firefox的安装包和一个新的本地Mac OSX安装包。我们继续努力支持新的“LS2”网络数据库格式。</p>
<p>这次发布还有大量的bug修复包括修复了susimail附件的一些问题还含有针对纯IPv6路由器的一个修复。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 旅行报告" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>35C3 会议上的I2P</summary></details><p>I2P 团队大多数人出席了莱比锡的 35C3 会议。每天都开会回顾上一年阐述了我们2019年的发展和设计目标。</p>
<p>项目愿景和新的路线图见<a href="http://i2p-projekt.i2p/en/get-involved/roadmap">此文</a></p>
<p>我们为网页和控制台在LS2Testnet和可用性提升上继续努力。
一个计划已在TailsDebian和Ubuntu Disco中就位。我们在安卓和I2P_Bote的修复上仍需要人手。</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 已发布" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37NTCP2 已启用</summary></details><p>0.9.37版启用了更快更安全的传输协议NTCP2。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 已发布" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36NTCP2 及缺陷修复</summary></details><p>0.9.36包含一个新的更安全的传输协议叫作NTCP2。
此协议默认禁用,但是您可以启用它。在<a href="/configadvanced">高级设置</a>中设置 <tt>i2np.ntcp2.enable=true</tt>,然后重新启动。
在下个发布中NTCP2将被启用。</p>
<p>此发布也包含性能优化和缺陷修复</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 发布" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35SusiMail 文件夹及 SSL 向导</summary></details><p>0.9.35 在Susimail中加入了文件夹的支持以及在您的隐藏服务页面用于建立HTTPS的新SSL向导。
我们如同往常一样收集错误修复尤其是在Susimail中。</p>
<p>我们正在为0.9.36中的几部分而努力包括新的OSX安装包以及更快、更安全的被称为NTCP2的传输协议。</p>
<p>7月20-22号 I2P 将在纽约市HOPE。欢迎拜访并打招呼</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 发布" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 包含错误修复</summary></details><p>0.9.34包含大量错误修复!
同时还有Susimail、IPV6处理和隧道对等节点选择。
我们在UPnP中加入了IGD2模式的支持。
您还可以在将来的发布中看到更多的改进。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 发布" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 包含错误修复</summary></details><p>0.9.33包含大量的错误修复包括i2psnarkI2P隧道streaming和SusiMail。
对于那些不能直接访问补种页面的用户,我们现在提供几种形式的代理用于补种。
我们现在在隐藏服务管理器中默认设置了比率限制。
对于高流量服务器,如有必要请浏览并调整限制。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KaiserMeltdown和Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>安全问题几乎在每种系统中均有所发现</summary></details><p>在全球范围内几乎所有已售出的电脑里的现代CPU中发现了很严重的问题包括移动设备。这些安全漏洞名为“Kaiser”“Meltdown”“Spectre”。</p>
<p>KAISER/KPTI 的白皮书可在<a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>中找到Meltdown在<a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>以及SPECTRE在<a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>。英特尔第一响应列于<a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>之下。</p>
<p>当有可用更新时更新系统对于我们的I2P使用者来说很重要。Windows 10系统补丁已从现在起可用随后不久则是Windows 7和8。MacOS的补丁同样也已可用。大多Linux系统也同样具有包含修复的内核。这同样适用于安卓系统在2018年1月2日的安全补丁中就包含此问题的补丁。请在可行时尽快更新您的系统。</p>
</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="新年快乐!- 来自34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>新年与 I2P 在34C3</summary></details><p>I2P团队祝各位新年快乐</p>
<p>从2017年12月27日至30日在莱比锡举行的34C3会议上不少于7位 I2P 团队成员参加了会议。除了在桌上的<a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">会议</a>以外我们还会见了从四面八方来的I2P的朋友。
会议的结果已发布在<a href="http://zzz.i2p" target="_blank">zzz.i2p</a></p>
<p>此外我们分发了很多贴纸,并将有关我们项目的信息提供给任何询问的人。
我们的年度I2P晚餐取得了圆满成功感谢所有与会人士对I2P的持续支持。</p>
</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 发布" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 包含控制台升级</summary></details><p>0.9.32包含若干路由控制台和有关web应用地址簿i2psnark和Susimail的修复。
我们亦同时修改了处理用于发布路由信息的配置主机名的方式以消除一些通过DNS的网络穷举攻击。
我们已经在控制台中加入了一些检查以抵御重绑定攻击。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 已发布" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 包含了控制台方面的更新</summary></details><p>此次发布内含的修改比往常更加令人瞩目!
我们让路由控制台焕然一新,使其更加易懂,
@ -43,7 +385,7 @@ We have added some checks in the console to resist rebinding attacks.</p>
<p>如果你还不是I2P的翻译人员现在将是加入我们的绝佳时机
请参阅<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">新翻译人员指南</a>
来获取如何参与的指导。</p>
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 发布" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 升级到Jetty 9</summary></details><p>0.9.30版本包含升级到Jetty 9和Tomcat 8的更新。
</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 发布" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 升级到Jetty 9</summary></details><p>0.9.30版本包含升级到Jetty 9和Tomcat 8的更新。
之前的版本不再被支持也不会在即将到来的Debian Stretch和Ubuntu Zesty中提供。
路由器会将每个Jetty网站的jetty.xml设置文件迁移到新的Jetty 9设置中。
对于最近的未曾修改的设置的迁移应该会成功,但是对于修改过的或是非常老的设置则可能不会。
@ -59,7 +401,7 @@ BwSchedule 0.0.36i2pcontrol 0.11。</p>
<p>注意在非Android的ARM平台例如树莓派文件块数据库将在重启时升级这也许会花上数分钟。
请保持耐心。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29发布" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29包含缺陷修复</summary></details><p>0.9.29版本包含大量Trac工单的修复包括针对错误压缩的消息的变通方案。
</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29发布" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29包含缺陷修复</summary></details><p>0.9.29版本包含大量Trac工单的修复包括针对错误压缩的消息的变通方案。
我们现在在IPv6上提供对NTP的支持。
我们对Docker加入了初步的支持。
我们翻译了手册页。
@ -118,8 +460,8 @@ IPv6 传输、SSU 对等端测试、隐身模式等也有改进。</p>
增加了 QR 码用于与其他人分享隐身服务。
增加了“身份”图像用于视觉上区分地址。</p>
<p>我们在控制台中添加了新的“路由器家族”配置页面,
这可以让您更容易的声明您的一组路由器是由一个人运行。
一些变更以增加网络容量,并希望能够提升隧道构建成功率。</p>
这可以让您更容易的声明您的一组路由器是由一个人运行。
这会添加一些变更以增加网络容量,并提升隧道构建成功率。</p>
<p>如往常一样,我们建议所有用户升级到此发布版本。
帮助网络和保持安全的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 发布" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 包含几个问题修复和更快速度</summary></details><p>0.9.24 包含新版本的 SAM (v3.2) 和众多问题修复和效率改进。
@ -147,9 +489,9 @@ Str4d 出席了 <a href="http://www.realworldcrypto.com/rwc2016/program">Real Wo
</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 发布" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 带有bug修复并且开始 Ed25519 迁移</summary></details><p>0.9.22 包含对 i2psnark 在完成前被攻陷的修复,并且开始将路由器信息向更新、更强的 Ed25519 签名迁移。 为了减少网络的流失,您的路由器将只在每次重启时有较小的概率开始转换为 Ed25519。 在转换之后,请预期到在几天内看到较低的带宽使用量,因为它需要重新将新的身份集成到网络中。 如果一切顺利,我们在下一个版本中加快密钥更新的过程。</p>
<p>I2PCon Toronto 成功! 所有演讲和视频资料已放在 <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon 页面</a></p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 发布" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 版本带有性能改进和缺陷修复。</summary></details><p>0.9.21&nbsp;包含几个更改,以增加网络容量、提高播种效率,并更有效率的使用带宽。我们已经迁移共享客户端隧道到 ECDSA 签名,并使用新的 "multisession"&nbsp;功能为那些不支持 ECDSA&nbsp;的站点添加一个 DSA&nbsp;后备。</p>
<p>2015年多洛伦 I2PCon&nbsp;的报告人和时间表已经公布。查阅 <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon 页面</a>了解详细信息。在 <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>&nbsp;上预定您的座位。&lt;br&gt;</p>
</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 发布" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 版本带有性能改进和缺陷修复。</summary></details><p>0.9.21 包含几个更改,以增加网络容量、提高播种效率,并更有效率的使用带宽。我们已经迁移共享客户端隧道到 ECDSA 签名,并使用新的 "multisession" 功能为那些不支持 ECDSA 的站点添加一个 DSA 后备。</p>
<p>2015年多洛伦 I2PCon 的报告人和时间表已经公布。查阅 <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon 页面</a>了解详细信息。在 <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a> 上预定您的座位。</p>
<p>如往常一样,我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon&nbsp;多伦多报告人和时间表已公布" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>2015年在多伦多的 I2PCon&nbsp;报告人和时间表已公布&lt;br&gt;</summary></details><p>2015年多洛伦 I2PCon&nbsp;的报告人和时间表已经公布。查阅 <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon 页面</a>了解详细信息。在 <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>&nbsp;上预定您的座位。&lt;br&gt;</p>
</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon 多伦多报告人和时间表已公布" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>2015年在多伦多的 I2PCon 报告人和时间表已公布</summary></details><p>2015年多洛伦 I2PCon 的报告人和时间表已经公布。查阅 <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon 页面</a>了解详细信息。在 <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a> 上预定您的座位。</p>
</article>
</div>

View File

@ -1,8 +1,372 @@
<div>
<header title="I2P 新聞">新聞提要和路由器更新</header><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
We also have the usual collection of bug fixes, especially in SusiMail.</p>
<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
<header title="I2P 新聞">新聞提要和路由器更新</header><article id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a" title="2.9.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released" author="idk" published="2025-06-02T19:00:00Z" updated="2025-06-02T19:00:00Z"><details><summary>I2P 2.9.0 版本</summary></details><p>I2P 2.9.0 是一个维护版本,包括错误修复和新功能开发。</p>
<p>改进了线程使用以提高 i2ptunnel 系统的性能。改进了 NTCP2 以抵御探测攻击。通知系统已集成到更多应用程序中,以便从 I2PSnark 和其他应用程序向用户提供更好的反馈。修复了自动播种注册问题。用户在充当播种时可能会观察到更多的资源使用情况。如果不希望出现这种情况,可在 /config 页面上禁用播种模式。</p>
<p>控制台中新增了全局地图功能,可在网络数据库视图中显示路由器位置。这些都是帮助路由器建立隧道和匿名提供服务的对等节点。</p>
<p>关于隧道的自动带宽管理、数据报 2 协议和后量子密码学的实现工作仍在继续。在两个版本后,即 2.11.0I2P 将需要 Java 17。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 版本</summary></details><p>2.8.2 修复了在 2.8.1 版本中引入的导致 SHA256 失败的错误。
该错误主要影响高带宽路由器。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 版本</summary></details><p>2.8.1 修复了 2.8.0 中出现问题的本地站点访问问题。
我们在控制台中为多个应用程序添加了通知气泡,以突出显示应用的消息。
我们修复了可能影响隧道可靠性的隧道测试错误。
地址簿现在有一个新的“最新”选项卡,显示从您的订阅中添加的最新主机名。
对暗色主题进行了若干处修复和改进。</p>
<p>我们修复了之前在 Java 21 或更高版本上失败的安装程序。
我们还修复了在 Linux 上安装到包含空格的目录路径出现的问题。
对于使用 Docker 的用户,我们更新了过时的 Docker 容器和容器库。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="2.8.0 访问本地站点失败" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 本地访问错误</summary></details><p>在 2.8.0 中,浏览本地站点(通过主机名或 b32将失败。
解决方法是使用 localhost 和服务器端口(通常为 7658来绕过 I2P。
例如,<a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>
我们对此问题深表歉意并努力修复中。</p>
</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 发布</summary></details><p>此版本通过修复错误、删除未使用的代码以及提高网络稳定性以改进 I2P。</p>
<p>我们改进了网络中拥堵的路由器的处理。
UPnP 和 NAT 遍历中的问题已解决,以改善连接性和错误回报。
我们现在有一个更激进的策略来从 NetDb 中删除赁集,以提高路由器性能并减轻过载。
另外有一些降低事件可观察性的更改,如路由器重启或关闭等。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 发布</summary></details><p>本次发布I2P 2.7.0 继续修复错误,提高性能以及添加功能。</p>
<p>从控制台和应用程序的信息访问已得到改进。
I2PSnark 和 SusiMail 搜索中的问题已得到修复。
路由器控制台中嵌入的 netDB 搜索的使用方式现在更直观、更实用。
高级模式下的诊断显示亦有少量改进。</p>
<p>另外修复了一些错误以提高网络内的兼容性。
一个赁集发布的问题已解决,提高了主要隐藏服务的可靠性。
当用户仅更改现有种子上的跟踪器时I2PSnark 不再更改信息哈希。
这可以防止种子因这些更改而受到不必要的干扰。
我们欢迎这份来自新贡献者的工作。
在处理流媒体库选项时的冲突已被解决以提高与其他 I2P 实现的兼容性。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 版本</summary></details><p>I2P 2.6.1 的发布是为了修复隐藏服务管理器应用程序中的用户界面错误。
此错误导致滚动被禁用,从而使某些配置无法访问。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 版本</summary></details><p>本次发布的I2P 2.6.0版本继续致力于修复漏洞、添加新功能并提升网络的可靠性。</p>
<p>当选择洪泛路由时,较新的路由将受到青睐。
I2PSnark 除了修复漏洞之外还获得了一些功能这些功能可以提高PeX对等节点交换的性能。
遗留的旧传输协议正在被移除因此简化了UDP传输代码。
本地主机上的目标节点将可以直接被本地客户端访问,而不需要请求它们的赁集,这可以提高性能和可测试性。
另外对对等节点的选择策略进行了一些额外的调整。</p>
<p>I2P 不再允许通过 Tor 建立 I2P 连接,从 Tor 出口IP地址建立的连接现在已被阻止。
我们不鼓励这样做因为它会降低I2P的性能并浪费Tor出口节点的资源而无任何益处。
如果您既运行Tor出口路由又运行I2P我们鼓励您继续这样做为两者使用不同的IP地址。
非出口节点和Tor客户端不受此影响无需任何更改。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 发布" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 包含 http 修复</summary></details><p>I2P 2.5.2 版本是为了修复 2.5.0 中引入的导致某些 HTTP 内容被截断的错误。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P 版本 2.5.1 已发布以解决拒绝服务攻击</summary></details><p>I2P 2.5.1 的发布是为了解决影响 I2P 网络和服务的拒绝服务攻击。
在此版本中,我们禁用了 Sybil 攻击检测工具的基于 IP 的部分,这些部分旨在放大攻击的影响和持续时间。
这应该有助于网络恢复正常运行。
那些已禁用 Sybil 攻击检测工具的人可以安全地重新启用它。
其他子系统也进行了调整,以改进路由信息验证和节点选择。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="暴风雨天气" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>网络天气:暴风雨。 I2P 正在遭受攻击。</summary></details><p>I2P 网络目前正遭受拒绝服务攻击。
此攻击以不同的方式影响 I2P 和 i2pd并对网络健康状况造成严重影响。
I2P 站点可达性严重下降。</p>
<p>如果您在 I2P 内部托管服务,并且该服务托管在洪泛路由上,则应考虑在禁用 Floodfill 的路由器上对该服务采用多宿主形式,以提高可达性。
其他缓解措施正在讨论中,但长期的、可向后兼容的解决方案仍需进一步研究。</p>
</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="新版本 I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>更多应用改善NetDB隔离策略审计</summary></details><p>该版本 I2P 2.5.0 比 2.4.0 版本提供了更多面向用户的改进,后者侧重于实施 NetDB 隔离策略。</p>
<p>I2PSnark增加了一些新功能比如搜索种子。
若干错误已经修复以提高与其他I2P种子客户端(如 BiglyBT 和 qBittorrent)的兼容性。
我们要感谢所有与libtorrent和qBittorrent合作的开发人员他们支持并改进了I2P支持。
SusiMail还增加了一些新功能包括支持邮件中的Markdown格式和将附件拖放到邮件中的功能。
使用隐藏服务管理器创建的隧道现在支持“Keepalive”这提高了性能和与网络技术的兼容性使更复杂的I2P站点成为可能。</p>
<p>在此版本中,我们还对 NetDB 进行了一些调整,以提高其对垃圾邮件的韧性,并提高路由器阻挡可疑消息的能力。
这是“审计” 2.4.0 版本中“子数据库隔离”防御实现的一部分。
此次调查发现了一个小的隔离穿透事件并修复之。
这个问题是 I2P 团队在内部发现并修复的。</p>
<p>在这个版本中我们对发布Android和Windows下游发行版的过程进行了一些改进。
这将改善这些下游产品的交付和可用性。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 发布包含 Congestion 和 NetDB 安全提升" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 发布包含 Congestion 和 NetDB 安全提升</summary></details><p>此版本 I2P 2.4.0 持续努力提高 I2P 网络的安全性和稳定性。
其中包含对网络数据库的大幅改进,网络数据库是 I2P 网络中用于发现对等节点的基本结构。</p>
<p>拥塞控制的改进将使路由器能够通过避开拥堵的对等节点从而提高网络稳定性。
这将有助于网络限制隧道垃圾信息造成的影响。
它还将有助于在 DDOS 攻击期间和之后修复网络。</p>
<p>NetDb 的更改还有助于保护各个路由器以及使用它们的应用程序的安全。
路由器现在可以通过将 NetDB 分成多个“子DB”来防御攻击者我们使用这些“子DB”来防止应用程序和路由器之间的信息泄漏。
这同时改进了 Java 路由器可用的有关其 NetDB 活动的信息,并简化了我们对多宿主应用程序的支持。</p>
<p>还包括 I2PSnark 和 SusiMail 应用程序中的许多错误修复和功能增强。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:" title="I2P 2.3.0 新版本 - 安全修复可调的黑名单DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - 安全修复可调的黑名单DTG API</summary></details><p>此版本包含 CVE-2023-36325 的修复。
CVE-2023-36325 是一个发生在布隆过滤器中的上下文混淆错误。
攻击者制作包含唯一 messageID 的 I2NP 消息,并将该 messageID 发送给客户端。
该消息在通过布隆过滤器后,不允许在第二条消息中重复使用。
随后,攻击者将相同的消息直接发送给路由。
路由器将消息传递给布隆过滤器并被丢弃。
这泄露了之前已经看到的 messageID 信息,使攻击者有充分的理由相信路由器承载了客户端。
这个问题已经通过将布隆过滤器的功能分离到不同的上下文中得到了解决,这些上下文中是基于消息是通过客户端隧道,还是探测隧道直接发送到路由的。
在正常情况下,这种攻击需要数天才能成功执行,并且可能受到攻击期间路由重启和对误报的灵敏度等若干因素的干扰。
建议使用 Java I2P 的用户立即更新以免受攻击。</p>
<p>在修复这个上下文混淆错误的过程中,我们修改了一些策略来防御这类型的泄漏。
这包括对 netDb 的调整、速率限制机制和洪泛路由的行为。</p>
<p>此版本添加了 not_bob 作为第二个默认hosts来源并把<a href="http://notbob.i2p">notbob.i2p</a><a href="http://ramble.i2p">ramble.i2p</a>添加到控制台主页。</p>
<p>这个版本还包含一个可调整的黑名单。
黑名单是半永久性的每个被封禁的IP地址会被一直屏蔽直到路由器重新启动。
在 sybil 攻击期间观察到黑名单爆炸性增长的用户可以通过将黑名单配置为按一定时间间隔使条目过期来选择更短的超时时间。
此功能在默认情况下是关闭的,目前仅建议高级用户使用。</p>
<p>该版本还包括一个API用于使用桌面GUI(DTG)修改插件。
现在可以将菜单项添加到系统托盘中,从而更直观地启动使用本地应用程序接口的插件。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="新发布 2.2.1包含DockerUbuntu Lunar和Debian Sid的打包修复" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - 2.2.0 的维护修复</summary></details><p>I2P 2.2.0 版本向前推进以加快缓解 DDOS 攻击后,我们了解到一些开发问题,因此有必要构建和发布新包。
此发布修复了 Ubuntu Lunar 和 Debian Sid 中的一个问题,即使用更新后的版本的 jakarta 包无法访问路由器控制台。
Docker 包未正确读取参数,导致无法访问配置文件。
此问题也已解决。
docker 容器现在也与 Podman 兼容。</p>
<p>本发布与 transifex 同步翻译并更新 GeoIP 数据库。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="新版本 2.2.0包含DDOS攻击的缓解措施和流传输子系统的调整" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>DDOS攻击的缓解措施和流传输子系统的调整</summary></details><p>我们已选择将 2.2.0 的发布日期提前到今天,即 2023 年 3 月 13 日。
此版本包括对网络数据库、洪泛和节点选择组件的修改,提高了路由器抵御 DDOS 攻击的能力。
攻击可能会持续进行,但对这些系统的改进将通过帮助路由识别和降低路由评分来帮助减轻 DDOS 攻击的风险。</p>
<p>此版本还为 Streaming 子系统添加了重放保护,以防止可以捕获加密数据包的攻击者通过将其发送给意外的接收者来重新使用它。
这是一个向后兼容的更改,因此旧路由器仍然能够使用新路由器的流媒体功能。
此问题由 I2P 开发团队在内部发现并修复,与 DDOS 攻击无关。
我们从未在实际环境遇到过重放流数据包,并且不相信此时针对 I2P 网络发生过流式重放攻击。</p>
<p>您可能已经注意到,这些发行说明和发行版本身已由 idk 而非 zzz 签署。
zzz 已选择退出该项目,他的职责由其他团队成员承担。
因此,该项目正致力于更换网络统计基础设施并将开发论坛移至 i2pforum.i2p。
我们感谢 zzz 长期以来提供这些服务。</p>
<p>如往常一样,我们建议您升级到这个版本。
维护安全并帮助网络的最佳方式就是运行最新版本。</p>
</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS 消息进展" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS 消息进展</summary></details><p>我们已经确认攻击者控制了大量的路由器。
我们的调查和缓解措施仍在继续。</p>
<p>这是提醒人们即使在 20 年后I2P 网络规模仍然相对较小的好时候。
我们没有证据表明攻击者正试图对任何特定用户或隐藏服务进行去匿名化。
但是,如果您有高风险威胁模型,您应该仔细考虑 I2P 目前是否提供了您需要的保护。
从长远来看,最好的解决方案是宣传并发展 I2P 网络以提高我们用户的安全性。</p>
<p>我们将在有必要时在新闻推送和<a href="http://zzz.i2p">zzz.i2p</a>提供更多信息。
在我们努力改进 I2P 的过程中,请您耐心等待。</p>
</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="关于最近的拒绝服务攻击" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P 保持完好,但性能受损</summary></details><p>I2P 网络目前正受到拒绝服务攻击的影响。
网络的洪泛功能受到影响,导致响应中断,隧道构建成功率下降。
网络参与者在连接到 I2P 站点和使用 I2P 服务时遇到困难。
我们在正在逐步调查和实施缓解策略。</p>
<p>虽然攻击降低了性能,但网络仍然完好无损且可用。
目前Java I2P 路由器似乎比 i2pd 路由器能更好地处理这些问题。
下周,各种缓解措施应该会开始出现在 Java 和 C++ 路由器的开发版本中。</p>
</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 包含大量 SSU2 修复</summary></details><p>自 11 月发布 2.0.0 以来,我们获知了一些情况。
随着路由器更新到该版本,网络对我们新的 SSU2 传输协议的支持率从大约 1% 提高到 60% 以上。
首先,我们已经确认 SSU2 是一个可靠、设计良好且安全的协议。
其次,我们发现并修复了协议推行中的许多小错误或很少触发的错误。
这些累积错误的影响降低了网络的性能。</p>
<p>此外,我们还注意到网络中隧道数量的增加和隧道构建成功率的下降,
可能是由比特币新的 I2P 临时地址功能触发的,
但由于我们的 SSU2 错误和其他拥塞控制问题而变得更差。
我们正在与比特币和其他非比特币项目合作,以减少 I2P 网络需求。
我们改进了算法以减少拥塞期间的网络负载。
我们还与 i2pd 合作开发通用的拥塞控制策略。</p>
<p>因此,我们将此版本的发布时间加快了大约六周,以便向所有人发布修复程序。
i2pd 上周发布了他们的 2.45.0 版,早期的结果令人鼓舞。
新协议和分布式网络很难开发。
拥堵可能会在没有任何警告和原因的情况下出现。
感谢您的耐心等待,因为我们已经诊断并希望解决问题。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 已启用</summary></details><p>I2P 2.0.0版本在完成了小特性开发、测试和若干错误修复以后为所有用户启用了我们新的SSU2 UDP传输。</p>
<p>我们也修复了所有部分包括安装包、网络数据库、私有地址簿添加Windows浏览器启动程序和IPv6 UPnP。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="最近的部落格文章" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>最近的博客文章</summary></details><p>这是我们网站部分最近的博客文章的链接:</p>
<ul>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">有关我们新的SSU2 传输的概述</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">有关I2P币及其他骗局的警告</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">与来自divs.exchange的Konrad的访谈</a></li>
<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">与来自StormyCloud的Dustin的访谈</a></li>
</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 已发布" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>带SSU2测试的1.9.0</summary></details><p>在过去的三个月里我们花了很多时间与小规模志愿者一起研究我们新的UDP传输协议 "SSU2"
这个版本完成了实现,包括中继和对等测试。
我们默认在安卓和ARM平台上启用它并在一小部分其它路由器上随机启用。
这将使我们能够在未来三个月内做更多的测试,完成连接迁移功能
并修复任何剩余的问题。
我们计划在11月发布的下一个版本中为所有人启用该功能。
无需手动配置。</p>
<p>当然,这个发布版本也包含了一些日常的错误修复。
我们还增加了一个自动死锁检测器,它已经找出一个很少见的死锁。这个死锁已经被修复。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="新出口代理 exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>新出口代理</summary></details><p>I2P出口代理可以使你通过一个HTTP代理隧道访问互联网。
在我们的 <a href="http://i2p-projekt.i2p/en/meetings/314">月度会议</a>上,
<b>exit.stormycloud.i2p</b> 已经成为我们官方推荐的出口代理,替代早已死去的 <b>false.i2p</b>
欲了解 <a href="http://stormycloud.i2p/"> StormyCloud 组织</a>的更多信息,请访问
<a href="http://stormycloud.i2p/outproxy.html">出口代理</a>
<a href="http://stormycloud.i2p/tos.html">使用条款</a>
<a href="http://stormycloud.i2p/">StormyCloud 网站</a></p>
<p>我们建议你修改 <a href="/i2ptunnel/edit?tunnel=0">匿名服务管理器配置</a>来确保 <b>exit.stormycloud.i2p</b>存在于两个地方: <b>出口代理</b><b>SSL出口代理</b>
修改之后,<b>s向下滑、点击保存</b>
<a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">在我们的博客文章上查看截图</a>
你可以在 <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob的博客</a>上查看Android版的说明和截图。</p>
<p>路由器更新不会更新你的配置,你必须手动修改。
非常感谢StormyCloud的支持。如果可能的话请考虑<a href="http://stormycloud.i2p/donate.html">给他们捐赠</a></p>
</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 包含错误修复</summary></details><p>本发布包含i2psnark
路由器I2CP和UPnP的错误修复。
修复了路由器软重启、IPv6、SSU 对等测试、网络数据库存储和隧道构建中的地址错误。
路由家族处理和Sybil分级也明显改善了。</p>
<p>和i2pd一起我们开发了新的UDP传输SSU2。
SSU2将带来实质性的性能和安全性改进。
它还将让我们最终替换我们最后使用的非常慢的 ElGamal 加密,
完成我们从9年前开始的加密的完全升级。
本发布包含一个默认关闭的初步推行。
如果你想参与测试请关注zzz.i2p的当前消息。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="安装必要的Java/Jpackage升级" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>最近Java的“Psychic Signatures”漏洞影响到I2P。当前Linux的I2P用户或任何正在使用非捆绑JVM的I2P用户应当升级
他们的JVM或切换到 Java 15 以下
不包含该漏洞的版本。</p>
<p>新的I2P易安装包已使用
JVM的最新发布生成。更多详情已发布在各
同捆包的新闻源中。</p>
</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 包含可靠性和性能提升</summary></details><p>1.7.0 发布包含若干性能和可靠性的改善。</p>
<p>对于支持的平台,现在系统托盘中会弹出信息。
i2psnark 现在有一个新的种子编辑器。
现在大大降低了 NTCP2 的CPU占用。</p>
<p>在新安装中,长期不受支持的 BOB 接口已被移除。
除了 Debian 包以外,现有的安装将继续使用之。
其余任何 BOB 应用的用户都应该要求开发人员切换到SAMv3协议。</p>
<p>我们得知自 1.6.1 发布以来,网络可靠性不断恶化。
我们在发布以后很快就意识到了这个问题,然而我们花了近两个月才找到原因。
我们最终确认为 i2pd 2.40.0 中的一个bug
这个修复将在 2.41.0 中和这个版本几乎同时发布。
在此过程中,我们在 Java I2P 中做了一些修改,以改善
网络数据库查找和存储的健壮性,并在隧道节点选择中避开性能较差的对等节点。
这将使网络在存在异常路由或恶意路由的情况下更健壮。
此外,我们正在启动一个联合项目,在同一个隔离的测试网络中测试 i2pd 和 Java I2P 路由
的预发布版本,这样我们就可以在发布前而不是发布以后发现更多问题。</p>
<p>其他方面,我们在设计新的 UDP 传输“SSU2”提案159
中继续取得重大进展并开始推行。
SSU2 将带来实质上的性能和安全提升。
这还将让我们能最终取代最后使用的,非常慢的 ElGamal 加密,
完成约9年前开始的全加密升级。
我们预计很快就会开始和 i2pd 进行联合测试,并在今年晚些时候向网络推出。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 启用新的隧道搭建信息</summary></details><p>该发布完成了2021年开发的两个主要协议更新的推出。
为路由迁移至 X25519 加密的步伐加快了,我们预计绝大部分路由在今年年底能完成切换。
短隧道构建信息已启用以减少带宽使用。</p>
<p>我们为新安装向导增添了一个主题选择面板。
我们改善了SSU表现修复了一个SSU对等节点测试信息的问题。
调整了隧道构建Bloom过滤器以降低内存使用。
我们改善了非Java插件的支持。</p>
<p>另外我们在设计新的UDP传输SSU2方面取得了重大进展预计明年年初开始推行。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 包含新的隧道搭建信息</summary></details><p>是的没错,在 0.9.x 发布9年后我们直接从 0.9.50 跳到 1.5.0。
这并不意味着有重大的API更改也不意味着开发已经完成。
这仅仅是对近20年来为我们的用户提供匿名和安全的工作的认可。</p>
<p>此发布完成了更小的隧道构建消息的实现从而减少带宽使用。
我们继续迁移网络的路由至 X25519 加密。
当然也有许多错误修复和性能提升。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Muwire 桌面版漏洞" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire 桌面版漏洞</summary></details><p>Muwire 桌面版应用的独立安装包中发现一个安全漏洞。
其不影响控制台插件,并和以往发现的插件问题无关。
如果你正在运行 Muwire桌面版应用你应当立即<a href="http://muwire.i2p/">升级到 0.8.8</a></p>
<p>问题详情将在2021年7月15日于<a href="http://muwire.i2p/security.html">muwire.i2p</a>公布。</p>
</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Muwire 插件漏洞" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire 插件漏洞</summary></details><p>Muwire 插件中发现一个安全漏洞。
其不影响桌面客户端的独立安装包。
如果你正在运行 Muwire 插件,你应当立即<a href="/configplugins">升级到 0.8.7-b1</a></p>
<p>更多有关漏洞和及时的安全建议的信息见于<a href="http://muwire.i2p/security.html">muwire.i2p</a></p>
</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 包含 IPv6 修复</summary></details><p>0.9.50 继续为路由加密密钥迁移至 ECIES-X25519。
我们已为补种启用 DNS over HTTPS 以保护用户免受被动 DNS 窥探。
还有若干对 IPv6 地址的修复和提升,包括新的 UPnP 支持。</p>
<p>我们终于修复了一些 SusiMail 长期存在的错误。
对带宽限制器的修改应该能改善网络隧道表现。
在我们的 Docker 容器有几处改善。
我们已经提升了对网络中可能的恶意和异常路由的防御。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 包含SSU修复及更快速的加密</summary></details><p>0.9.49 继续使 I2P 更快更安全。
我们对 SSU (UDP) 传输做了若干改进和修复,速度应有所提高。
同时此发布开始为路由迁移至新的,更快的 ECIES-X25519 加密。
(至今目标地址采用此加密已有数个发布)
这几年,我们一直致力于新加密的规范和协议,
现已经接近尾声了!迁移会在数个发布中完成。</p>
<p>对于此发布,为尽量减少中断,只有新安装的以及极小比例的现有安装
(重启时随机选择)会采用新加密。
如果你的路由确实“重新键入”以使用新加密,在你重启后的几天内,它可能会比平时流量更少或可靠性更低。
这是正常现象,因为你的路由生成了一个新的身份。
你的路由性能随后会恢复正常。</p>
<p>以往我们在改变默认签名类型时已两次“重新键入”网络,
但这是首次更改默认加密方式。
希望一切都能顺利进行,我们正逐步确定。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 包含性能提升</summary></details><p>0.9.48 在大多数服务上启用了我们的新端到端加密协议提案144
我们已经添加对新隧道建立的信息加密提案152的初步支持。
整个路由的性能都有显著提高。</p>
<p>Ubuntu Xenial (16.04 长期支持版) 的软件包已不再支持。
使用该平台的用户应当升级以继续获得 I2P 更新。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 启用了新的加密</summary></details><p>0.9.47 在一些服务中默认启用了我们的新端到端加密协议(提案 144
Sybil 分析和屏蔽工具现在已默认启用。</p>
<p>现在需要 Java 8 或更高版本。
Debian 软件包 Wheezy 和 Stretch以及 Ubuntu 软件包 Trusty 和 Precise 现已不再支持。
使用上述平台的用户需要升级以继续获得 I2P 更新。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 包含错误修复</summary></details><p>0.9.46 包含 streaming 库显著的性能提升。
我们已经完成了 ECIES 加密提案144的开发现在可以选择启用它以进行测试。</p>
<p>仅 Windows 用户:
本发布修复了一个可被本地用户利用的本地提权漏洞。
请尽快应用更新。
感谢 Blaze Infosec 披露此问题。</p>
<p>这是最后一个支持 Java 7、Debian 软件包 Wheezy 和 Stretch 以及 Ubuntu 软件包 Precise 和 Trusty 的发布。
使用上述平台的用户务必升级以获得未来的 I2P 更新。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 包含了错误修复</summary></details><p>0.9.45包含了隐身模式和带宽测试的重要修复。
这是一个对于控制台暗色主题的更新。
我们继续努力提高性能并开发新的端到端加密(提案 144)。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 发布" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 包含了错误修复</summary></details><p>0.9.44 包含一个隐藏服务处理新加密类型中拒绝服务问题的重要修复。所有用户都应尽快更新。</p>
<p>发布版本包含新端到端加密的初始支持(提案 144。此项目上的工作仍在继续尚未准备好使用。有一些控制台主页的更改及 i2psnark 中新的嵌入式 HTML5 媒体播放器。包含对受到防火墙限制的 IPv6 网络的额外修复。隧道建立的修复应当使得一些用户更快的启动。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 包含了错误修复</summary></details><p>在 0.9.43 发布版本中,我们继续致力于更强的安全性,隐私功能和性能提升。我们的新的租契集规范 (LS2) 实现现在已完成。我们正在开始用于未来发布版本的更强大快速的端到端加密(提案 144实现。一些 IPv6 探测问题已修复,当然还有一些其他错误修复。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 包含了错误修复</summary></details><p>0.9.42 继续使 I2P 更快更稳定.
此版本包含了几处改动以提高 UDP 传输速度。
我们拆分了设置文件,以便将来进一步模块化。
我们将继续努力,将关于更快、更安全的加密的建议付诸实践。
理所当然地, 还有许多错误修复。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 包含了错误修复</summary></details><p>0.9.41 继续着手落实提案 123 引入的新功能,
包括对加密的租契集做客户端级别的身份验证。
控制台的 I2P 标志及若干图标已更新。
更新了 Linux 安装程序。</p>
<p>启动速度在树莓派Raspberry Pi等平台上更快了。
已修正若干缺陷,包括部分严重影响底层网络消息的问题。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 有新的图标</summary></details><p>0.9.40 支持新的租契集格式。
我们已禁用旧的 NTCP 1 传输协议。
有一个新的 SusiDNS 导入功能,以及一个用于传入连接的新的脚本化过滤机制。</p>
<p>我们对 OSX 原生的安装程序做了很多改进,以及更新了 IzPack 安装程序。
继续使用新的图标焕新控制台。
如往常一样,我们还修复了许多缺陷!</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 带有性能提升</summary></details><p>0.9.39 包含了针对新网络库格式的大量更新(proposal 123).
我们将 i2pcontrol 插件作为一个 webapp 打包进来从而支持 RPC 应用的开发.
另外还有众多的性能提升和bug修复.</p>
<p>我们移除了午夜和经典主题以减轻维护压力.
之前使用这些主题的用户现在将会看到暗或者亮色调主题.
另外主页有了新的的图标,这是控制台更新的第一步.</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 含有全新安装向导</summary></details><p>0.9.38 含有一个若为首次安装则会启动的向导还有一个带宽测试器。我们已经支持最新的GeoIP数据库格式。我们的网站上有一个新的配置Firefox的安装包和一个新的本地Mac OSX安装包。我们继续努力支持新的“LS2”网络数据库格式。</p>
<p>这次发布还有大量的bug修复包括修复了susimail附件的一些问题还含有针对纯IPv6路由器的一个修复。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 旅行报告" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>35C3 会议上的I2P</summary></details><p>I2P 团队大多数人出席了莱比锡的 35C3 会议。每天都开会回顾上一年阐述了我们2019年的发展和设计目标。</p>
<p>项目愿景和新的路线图见<a href="http://i2p-projekt.i2p/en/get-involved/roadmap">此文</a></p>
<p>我们为网页和控制台在LS2Testnet和可用性提升上继续努力。
一个计划已在TailsDebian和Ubuntu Disco中就位。我们在安卓和I2P_Bote的修复上仍需要人手。</p>
</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 已发布" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37NTCP2 已启用</summary></details><p>0.9.37版启用了更快更安全的传输协议NTCP2。</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 已发布" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36NTCP2 及缺陷修复</summary></details><p>0.9.36包含一个新的更安全的传输协议叫作NTCP2。
此协议默认禁用,但是您可以启用它。在<a href="/configadvanced">高级设置</a>中设置 <tt>i2np.ntcp2.enable=true</tt>,然后重新启动。
在下个发布中NTCP2将被启用。</p>
<p>此发布也包含性能优化和缺陷修复</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 发布" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35SusiMail 文件夹及 SSL 向导</summary></details><p>0.9.35 在Susimail中加入了文件夹的支持以及在您的隐藏服务页面用于建立HTTPS的新SSL向导。
我们如同往常一样收集错误修复尤其是在Susimail中。</p>
<p>我们正在为0.9.36中的几部分而努力包括新的OSX安装包以及更快、更安全的被称为NTCP2的传输协议。</p>
<p>7月20-22号 I2P 将在纽约市HOPE。欢迎拜访并打招呼</p>
<p>一如往常一般,我們建議您更新到這個版本,要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 版本發佈" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 包含問題修復</summary></details><p>0.9.34 版修復了許多問題!
此版本還改進了 SusiMail、IPv6 handling 和 tunnel peer 自選的功能。

530
data/win/beta/entries.html Normal file
View File

@ -0,0 +1,530 @@
<div>
<header title="I2P News">News feed, and router updates</header>
<article
id="urn:uuid:1d530419-42fd-4ab6-979c-644872a2a8b9"
title="I2P Easy-Install 2.9.0"
href="http://i2p-projekt.i2p/en/blog/post/2025/06/07/i2p_easy-install_2.9.0_release"
author="idk"
published="2025-06-07T17:00:00Z"
updated="2025-06-07T17:00:00Z">
<details>
<summary>I2P Easy-Install 2.9.0</summary>
</details>
<p>
This release updates the embedded I2P router to I2P 2.9.0.
It also updates the embedded I2P Firefox profile to 2.9.0.
</p>
</article>
<article
id="urn:uuid:598e5703-364e-4806-9083-d1bdfc430d2e"
title="I2P Easy-Install 2.8.2"
href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release"
author="idk"
published="2025-04-02T14:00:00Z"
updated="2025-04-02T14:00:00Z">
<details>
<summary>I2P Easy-Install 2.8.2</summary>
</details>
<p>
This release updates the embedded I2P router to I2P 2.8.2.
It also updates the embedded I2P Firefox profile to 2.8.2.
Due to the point release of I2P, 2.8.2 has become the final release to support Chrome and Chromium browsers due to the adoption of ManifestV3.
Previously, this had been announced as 2.8.1.
</p>
</article>
<article
id="urn:uuid:dc6880db-d329-4693-9c1c-ed02fa361864"
title="I2P Easy-Install 2.8.1"
href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release"
author="idk"
published="2025-03-21T13:00:00Z"
updated="2025-03-21T13:00:00Z">
<details>
<summary>I2P Easy-Install 2.8.1</summary>
</details>
<p>
This release updates the embedded I2P router to I2P 2.8.1.
It also updates the embedded I2P Firefox profile to 2.8.1.
Chrome extension configuration has been removed from the profile manager.
Chrome-specific proxy management has been retained for now.
This will be the final release to support Chrome and Chromium browsers due to the adoption of ManifestV3.
</p>
</article>
<article
id="urn:uuid:1d9a0eaf-148c-4c97-9c27-f8f15be29ef6"
title="Easy-Install for Windows Release 2.8.0"
href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release"
author="idk"
published="2024-10-12T16:00:00Z"
updated="2024-10-12T16:00:00Z">
<details>
<summary>I2P Easy-Install 2.8.0</summary>
</details>
<p>
This release updates the embedded I2P router to I2P 2.8.0.
It also updates the embedded I2P Firefox profile to 2.8.0.
</p>
</article>
<div>
<header title="I2P News">News feed, and router updates</header>
<article
id="urn:uuid:1d9a0eaf-148c-4c97-9c27-f8f15be29ef6"
title="Easy-Install for Windows Release 2.7.0"
href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release"
author="idk"
published="2024-10-20T16:00:00Z"
updated="2024-10-20T16:00:00Z">
<details>
<summary>I2P Easy-Install 2.7.0</summary>
</details>
<p>
This release updates the embedded I2P router to I2P 2.7.0.
It also updates the embedded I2P Firefox profile to 2.7.0.
</p>
</article>
<article
id="urn:uuid:eda5b6e0-8d11-4410-9088-f892e9ea4d5f"
title="Easy-Install for Windows Release 2.6.1"
href="http://i2p-projekt.i2p/en/blog/post/2024/08/26/easy-install_for_windows_release_2.6.1"
author="idk"
published="2024-08-26T18:00:00Z"
updated="2024-08-26T18:00:00Z">
<details>
<summary>I2P Easy-Install 2.6.1</summary>
</details>
<p>
This release updates the embedded I2P router to I2P 2.6.1.
It also updates the embedded I2P Firefox profile to 2.6.2.
</p>
</article>
<article
id="urn:uuid:a58ced07-3a33-4294-9bb5-e344feb84754"
title="Easy-Install for Windows Release 2.6.0"
href="http://i2p-projekt.i2p/en/blog/post/2024/07/20/easy-install_for_windows_release_2.6.0"
author="idk"
published="2024-07-20T23:00:00Z"
updated="2024-07-20T23:00:00Z">
<details>
<summary>I2P Easy-Install 2.6.0</summary>
</details>
<p>
This release of the I2P Easy-Install bundle updates the embedded I2P router to I2P 2.6.0.
It also includes an updated I2P Firefox Profile, an updated version of I2P in Private Browsing, and updated browser plugins.
Discovery of browser configuration has been improved on some platforms.
</p>
</article>
<article
id="urn:uuid:0a728047-f126-4ce2-91a1-c09dd11a9a8b"
title="Easy-Install for Windows Release 2.5.2"
href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release"
author="idk"
published="2024-05-15T23:00:00Z"
updated="2024-05-15T23:00:00Z">
<details>
<summary>2.5.2 with HTTP fix</summary>
</details>
<p>
I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.
</p>
<p>
As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.
</p>
</article>
<article
id="urn:uuid:bf83d82a-0849-474f-b883-73cf8e779bde"
title="Easy-Install for Windows Release 2.5.0"
href="http://i2p-projekt.i2p/en/blog/post/2024/4/8/easy-install_for_windows_release_2.5.0"
author="idk"
published="2024-04-08T22:00:00Z"
updated="2024-04-08T22:00:00Z">
<details>
<summary>I2P Easy-Install Bundle for Windows 2.5.0</summary>
</details>
<p>
This latest release of the I2P Easy-Install Bundle for Windows revises the packaging of the bundle to be self-contained and portable.
The profile manager is moved to an I2P plugin and un-bundled from the router launcher itself, enabling it to be updated without a router update or even a router restart.
Many of these changes were previewed in the recent pre-releases.
During testing we chose to disable Chromium-wrapping capabilities, meaning the bundle still depends on an existing Firefox installation.
The profile manager has also been integrated with the desktop UI.
</p>
</article>
<article
id="urn:uuid:94cffa29-35bd-41d6-adc8-f5cb407f8012"
title="Easy-Install for Windows Release 2.4.9"
href="http://i2p-projekt.i2p/en/blog/post/2024/3/20/easy-install_for_windows_release_2.4.9"
author="idk"
published="2024-03-20T15:00:00Z"
updated="2024-03-20T15:00:00Z">
<details>
<summary>I2P Easy-Install Bundle for Windows 2.4.9</summary>
</details>
<p>
<p>This is a pre-release of the I2P Easy-Install Bundle for Windows.
This changes how the I2P bundle and browser profile manager are installed and integrated with the host system.
The Easy-Install bundle is now a "portable" system that can be moved to different locations within or between Windows file-systems while retaining all built-in functionality.
A shortcut for starting the I2P router is still provided by the installer for convenience, but the shortcuts for starting the I2P Browser are now integrated with the I2P desktop UI.</p>
<p>The browser profile manager itself has been split away from the monolithic I2P router+Java/jpackage, and moved into an I2P plugin managed by the router.
While this was done primarily to reduce how complex the existing code was, this also results in behavior which is closer to the main distribution of I2P for Windows and will lead to a more flexible installer, which can bundle additional default plugins and may be suitable for installation as a Windows service.
I2P Plugins can also be updated independently of the router that hosts them, so it will be possible to update the browser profile manager independently of the router itself.
It also means that the browser profile manager can be un-installed by uninstalling the plugin, and much more importantly that the browser profile manager is now compatible with all Java I2P distributions.</p>
<p><strong>Why a dev build 3 weeks before the release?</strong></p>
<p>By further delineating the components of the bundle, these changes also affected how the release process happens.
In particular the build process of each component has been encapsulated in a CI description which can be reproduced on a local PC.
This simplifies and automates the build process by ensuring that up-to-date build tools are installed in a brand-new container for every build.
In effect this should speed up the release process for I2P Easy-Install for Windows considerably.
This release is a test-run of the new process, so I can document what is going on.
It breaks down roughly like this:</p>
<ul>
<li>It takes ~22 minutes to compile all the targets for the <code>i2p.plugins.firefox</code> and make the resulting artifacts available. During this process, I must insert 1 HSM and enter 1 password. (This part used to be about 30 steps, now it takes 1)</li>
<li>It takes ~22 minutes to compile all the targets for the <code>i2p.firefox</code> project and make the resulting artifacts available. This process produces only unsigned artifacts identified by their hashes, and is non-interactive. (This part used to be around 60 steps the first time, and 40 steps each additional time)</li>
<li><code>i2p.firefox</code> updates are signed in their <code>.su3</code> form. The <code>NSIS</code>-powered <code>.exe</code> installer is the current updater. The next step is to sign <em>just this installer</em> and generate a torrent of the result. (This process used to depend on the previous build process and couldn't be done independently. Now it takes about 30 seconds)</li>
<li>Generate and sign a newsfeed to notify the users of an update. This process is the only process that is <strong>slower</strong> when containerized, because there are dozens of feeds to be signed in their respective containers. It takes about an hour.</li>
</ul>
<p>For you the end user, nothing much should change.
You'll get your updates a lot faster, and have more options available for testing.
The same installer is used for the updater, and the process is handled the same way.
However for developers, testers, and maintainers, this release will result in big changes for the better.</p>
<p>This release still embeds a <code>2.4.0</code> Java I2P router. No changes have been made to update the embedded router.
Network behavior will be unchanged until the official <code>2.5.0</code> release.</p>
</p>
</article>
<article
id="urn:uuid:dba13cd7-443c-450d-a888-3ad8880f8a2d"
title="Easy-Install for Windows Release 2.3.0"
href="http://i2p-projekt.i2p/en/blog/post/2023/7/10/easy-install_for_windows_release_2.3.0"
author="idk"
published="2023-07-10T23:00:00Z"
updated="2023-07-10T23:00:00Z">
<details>
<summary>I2P Easy-Install for Windows 2.3.0 Release</summary>
</details>
<p>
The I2P Easy-Install bundle for Windows version 2.3.0 has now been released.
As usual, this release includes an updated version of the I2P router.
This extends to security issues which affect people hosting services on the network.
</p>
<p>
This will be the last release of the Easy-Install bundle which will be incompatible with the I2P Desktop GUI.
It has been updated to include new versions of all included webextensions.
A longstanding bug in I2P in Private Browsing which makes it incompatible with custom themes has been fixed.
Users are still advised to *not* install custom themes.
Snark tabs are not automatically pinned to the top of the tab order in Firefox.
Except for using alternate cookieStores, Snark tabs now behave as normal browser tabs.
</p>
<p>
<b>Unfortunately, this release is still an unsigned <code>.exe</code> installer.</b>
Please verify the checksum of the installer before using it.
<b>The updates, on the other hand</b> are signed by my I2P signing keys and therefore safe.
</p>
<p>
This release was compiled with OpenJDK 20.
It uses i2p.plugins.firefox version 1.1.0 as a library for launching the browser.
It uses i2p.i2p version 2.3.0 as an I2P router, and to provide applications.
As always it is recommended that you update to the latest version of the I2P router at your earliest convenient opportunity.
</p>
<ul>
<li><a href="http://git.idk.i2p/i2p-hackers/i2p.firefox/-/tree/i2p-firefox-2.3.0">Easy-Install Bundle Source</a></li>
<li><a href="http://git.idk.i2p/i2p-hackers/i2p.i2p/-/tree/i2p-2.3.0">Router Source</a></li>
<li><a href="http://git.idk.i2p/i2p-hackers/i2p.plugins.firefox/-/tree/1.1.0">Profile Manager Source</a></li>
</ul>
</article>
<article
id="urn:uuid:dd6a31af-009b-4eed-be23-041f8440a641"
title="I2P Easy-Install 2.2.0 for Windows release"
href="http://i2p-projekt.i2p/en/blog/post/2023/3/20/i2p_easy-install_2.2.0_for_windows_release"
author="idk"
published="2023-03-20T18:00:00Z"
updated="2023-03-20T18:00:00Z">
<details>
<summary>SUMMARY_HERE</summary>
</details>
<p>
The I2P Easy-Install bundle for Windows version 2.2.0 has been released.
As usual, this release includes an updated version of the I2P Router.
This release of I2P provides improved strategies for dealing with network congestion.
These should improve performance, connectivity, and secure the long-term health of the I2P network.
It also includes several minor bugfixes and stability improvements when managing the router updates.
It is now better at co-existing with other I2P routers on the same device.
</p>
<p>
<b>Unfortunately, this release is still an unsigned <code>.exe</code> installer.</b>
Please verify the checksum of the installer before using it.
<b>The updates, on the other hand</b> are signed by my I2P signing keys and therefore safe.
</p>
<p>
This release was compiled with OpenJDK 19.
It uses i2p.plugins.firefox version 1.0.9 as a library for launching the browser.
It uses i2p.i2p version 2.2.0 as an I2P router, and to provide applications.
As always it is recommended that you update to the latest version of the I2P router at your earliest convenient opportunity.
</p>
<ul>
<li><a href="http://git.idk.i2p/i2p-hackers/i2p.firefox/-/tree/i2p-firefox-2.2.0">Easy-Install Bundle Source</a></li>
<li><a href="http://git.idk.i2p/i2p-hackers/i2p.i2p/-/tree/i2p-2.2.0">Router Source</a></li>
<li><a href="http://git.idk.i2p/i2p-hackers/i2p.plugins.firefox/-/tree/1.0.9">Profile Manager Source</a></li>
</ul>
</article>
<article
id="urn:uuid:0e16492e-a30d-4cbc-80bf-503b3837e283"
title="I2P Easy Install for Windows 2.1.0"
href="http://i2p-projekt.i2p/en/blog/post/2023/01/13/i2p_easy_install_for_windows_2.1.0"
author="idk"
published="2023-01-13T01:00:00Z"
updated="2023-01-13T01:00:00Z">
<details>
<summary>Windows Easy-Install Bundle 2.1.0 released to improve stability, performance.</summary>
</details>
<p>
The I2P Easy-Install bundle for Windows version 2.1.0 has been released.
As usual, this release includes an updated version of the I2P Router.
This release of I2P provides improved strategies for dealing with network congestion.
These should improve performance, connectivity, and secure the long-term health of the I2P network.
</p>
<p>
This release features mostly under-the-hood improvements to the browser profile launcher.
Compatibility with Tor Browser Bundle has been improved by enabling TBB configuration through environment variables.
The Firefox profile has been updated, an the base versions of the extensions have been updated.
Improvements have been made throughout the codebase and the deployment process.
</p>
<p>
<b>Unfortunately, this release is still an unsigned <code>.exe</code> installer.</b>
Please verify the checksum of the installer before using it.
<b>The updates, on the other hand</b> are signed by my I2P signing keys and therefore safe.
</p>
<p>
This release was compiled with OpenJDK 19.
It uses i2p.plugins.firefox version 1.0.7 as a library for launching the browser.
It uses i2p.i2p version 2.1.0 as an I2P router, and to provide applications.
As always it is recommended that you update to the latest version of the I2P router at your earliest convenient opportunity.
</p>
<ul>
<li><a href="http://git.idk.i2p/i2p-hackers/i2p.firefox/-/tree/i2p-firefox-2.1.0">Easy-Install Bundle Source</a></li>
<li><a href="http://git.idk.i2p/i2p-hackers/i2p.i2p/-/tree/i2p-2.1.0">Router Source</a></li>
<li><a href="http://git.idk.i2p/i2p-hackers/i2p.plugins.firefox/-/tree/1.0.7">Profile Manager Source</a></li>
</ul>
</article>
<article
id="urn:uuid:df1ead45-ee60-410b-a776-0c608116ee30"
title="I2P Easy-Install for Windows 2.0.0 Update, Unsigned EXE"
href="http://i2p-projekt.i2p/en/blog/post/2022/11/23/easy_install_bundle_2.0.0"
author="idk"
published="2022-11-23T01:00:00Z"
updated="2022-11-23T01:00:00Z">
<details>
<summary>The I2P Easy-Install bundle for Windows has been released.</summary>
</details>
<p>
In this release, support has been added for most major browsers, including all major Firefox(Gecko) and Chromium forks.
Compatibility with external I2P Service installs and un-bundled I2P user installs has been improved.
The Easy-Install bundle can now detect other I2P routers and prompt the user to launch them instead, if they already have I2P.
The browser extensions have been updated to the latest versions.
The Easy-Install now has access to `i2p.plugins.firefox`'s usability mode via the `-usability` command-line flag.
The default mode is the "Strict" mode where Javascript is disabled by NoScript.
In usability mode, Javascript is restricted by JShelter.
For more details, see the profile manager repository at i2pgit.org.
</p>
<p>
It is recommended that you update to this release for the best security, privacy, and performance, and to help the network.
</p>
</article>
<article
id="urn:uuid:41ccd648-2087-4465-abe3-0b56a9d6db4e"
title="I2P Easy-Install Bundle 1.9.5"
href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/easy_install_bundle_1.9.5"
author="idk"
published="2022-09-07T18:00:00Z"
updated="2022-09-07T18:00:00Z">
<details>
<summary>I2P Easy-Install Bundle 1.9.5 Point Release</summary>
</details>
<p>
This point release includes a bug fix in the included I2P router, which resolves
a highly obscure bug where the context clock is out of sync with the clock in
use by the File System, resulting in a router which is unable to read the current
state of it's own NetDB. Although this bug has only been observed on Windows 11
so far, it is highly recommended that all users update to the new build.
</p>
<p>
This release also features faster startup times improved stability in the profile
manager.
</p>
</article>
<article
id="urn:uuid:65dbab43-5817-4798-9c2b-87d403f4ee7c"
title="Windows Easy-Install Bundle 1.9.0 - Major Stability/Compatibility Improvements"
href="http://i2p-projekt.i2p/en/blog/post/2022/08/28/easy_install_bundle_1.9.0"
author="idk"
published="2022-08-28T23:00:00Z"
updated="2022-08-28T23:00:00Z">
<details>
<summary>This update includes the new 1.9.0 router and major quality-of-life improvements for bundle users</summary>
</details>
<p>
This release includes the new I2P 1.8.0 router and is based on Java 18.02.1.
</p>
<p>
The old batch scripts have been phased out in favor of a more flexible and stable solution in the jpackage itself. This should fix all bugs related to path-finding and path-quoting which were present in the batch scripts. After you upgrade, the batch scripts can be safely deleted. They will be removed by the installer in the next update.
</p>
<p>
A sub-project for managing browsing tools has been started: <a href="http://git.idk.i2p/idk/i2p.plugins.firefox">i2p.plugins.firefox</a> which has extensive capabilities for configuring I2P browsers automatically and stably on many platforms. This was used to replace the batch scripts but also functions as a cross-platform I2P Browser management tool. Contributions are welcome.
</p>
<p>
This release improves compatibility with externally-running I2P routers such as those provided by the IzPack installer and by third-party router implementations such as i2pd. By improving external router discovery it requires less of a system's resources, improves start-up time, and prevents resource conflicts from occurring.
</p>
<p>
Besides that, the profile has been updated to the latest version of the Arkenfox profile. I2P in Private Browsing and NoScript have both been updated. The profile has been restructured in order to allow for evaluating different configurations for different threat models.
</p>
</article>
<article id="urn:uuid:6dc28ef4-9628-46d6-83e7-72a6e3f2836e" title="Update for Windows Easy-Install Bundle 1.8.0" href="http://i2p-projekt.i2p/en/blog/post/2022/5/23/1.8.0-Release" author="idk" published="2022-05-23T13:00:00Z" updated="2022-05-23T13:00:00Z">
<details>
<summary>This update includes the new 1.8.0, new languages, and profile/launcher improvements</summary>
</details>
<p>
This release includes the new I2P 1.8.0 router and is based on Java 17.03.
</p>
<p>
New installations will be done without admin rights, making the updates fully silent for new installs. Admin installs will still require an elevation prompt to update. If you have installed I2P with the IzPack installer, a jpackage will not be installed.
</p>
<p>
The launcher scripts have been fixed to avoid launching multiple instances of I2P when run repeatedly before I2P has a chance to start. The profile selector was fixed to work with IzPack installs in admin-less mode.
</p>
<p>
I2P in Private Browsing was updated with experimental machine translations for multiple new languages. Community members are invited to contribute to them directly via Gitlab or Github for now.
<ul>
<li>Arabic</li>
<li>Chinese</li>
<li>French</li>
<li>German</li>
<li>Italian</li>
<li>Japanese</li>
<li>Portugese</li>
<li>Russian</li>
</ul>
</p>
<p>
As always, it is recommended that you update to the latest release for compatibility, stability, and security.
</p>
</article>
<article id="urn:uuid:690fddd1-2f40-4a15-9491-5db2413ad6ec" title="Update for Windows Jpackage 1.7.6" href="http://i2p-projekt.i2p/en/blog/post/2022/05/08/CHANGEME_URL_HERE" author="idk" published="2022-05-08T22:00:00Z" updated="2022-05-08T22:00:00Z">
<details>
<summary>Fixes a missing config file, temporary unsigned exe</summary>
</details>
<p>
This release will show a warning that the .exe is un-signed. This is normal and temporary. The relase is verified by I2P's update mechanism instead.
</p>
<p>
This release makes sure that new configuration files, which are essential to supporting multiple I2P routers, are included in the final build.
</p>
</article>
<article id="urn:uuid:6ee4b12e-dc0b-4928-9409-886896f60105" title="Update for Windows Jpackage 1.7.5" href="http://git.idk.i2p/i2p-hackers/i2p.firefox/-/issues/17" author="idk" published="2022-05-05T19:00:00Z" updated="2022-05-05T19:00:00Z">
<details>
<summary>Fixes a broken priority when a non-jpackaged router is in use</summary>
</details>
<p>
This release fixes an issue where the a jpackaged I2P router was prioritized over a non-jpackaged I2P router when the non-jpackaged router should have been preferred.
</p>
<p> It is recommended that all users update to the latest version.</p>
</article>
<article id="urn:uuid:23c541fa-c0cb-4f5c-91a7-f0f1fc3c8f24" title="Update for Windows Jpackage 1.7.4" href="http://i2p-projekt.i2p/en/blog/post/2022/04/21/Easy-Install-Updates.html" author="idk" published="2022-04-21T11:00:00Z" updated="2022-04-21T11:00:00Z">
<details>
<summary>Fix for CVE-2022-21449: Psychic Signatures in Java</summary>
</details>
<p>
This package updates the embedded Java Virtual Machine to Java 17.03, and switches to the more rapidly updated Oracle distribution of the OpenJDK. this resolves CVE-2022-21449 for the Windows Easy-Install package.
</p>
<p>
It also enables installation to be performed "Adminlessly" without placing the I2P router into the Program Files directory. This will be the default behavior for new installations.
</p>
</article>
<article id="urn:uuid:fb49443f-a87a-424f-84ae-6252392bfe7e" title="Update for Windows Jpackage 1.6.1" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="idk" published="2021-12-11T21:00:00Z" updated="2021-12-11T21:00:00Z">
<details>
<summary>Update 1.6.1</summary>
</details>
<p>
This release of the I2P Easy-Install bundle upgrades the jpackaged I2P router to the latest released version, 1.6.1. It also includes extension updates.
</p>
</article>
<article id="urn:uuid:49619c67-d629-4f15-a21d-569aba3f8a4c" title="Update for Windows Jpackage 1.5.1" href="http://i2p-projekt.i2p/en/blog/post/2021/11/02/i2p-jpackage-1.5.1" author="idk" published="2021-11-02T19:00:00Z" updated="2021-11-02T19:00:00Z">
<details>
<summary>1.5.1 With Extension Updates and Bugfixes</summary>
</details>
<p>
This is the first update of our jpackaged "Easy-Install" bundle for Windows. In this update, the HTTPS Everywhere will begin to self-disable on recent versions of Firefox. I2P in Private Browsing is updated to version 1.26. NoScript is updated to 11.2.11.
The jpackaged I2P Router was built with Adoptium JDK 17 and I2P version 1.5.1, which is a branch of 1.5.0 for the update. For more details on how the release process works, visit <a href="http://git.idk.i2p/i2p-hackers/i2p.firefox">
the gitlab repository</a>.
</p>
<p>
We want your feedback! Please let us know what you think of this new version of I2P. We're also interested in revising and finalizing the set of recommended browser extensions in the next update. Please visit <a href="http://git.idk.i2p/i2p-hackers/i2p.firefox/issues">to
participate in the discussion, report issues, and request features</a>.
</p>
</article>
</div>

View File

@ -0,0 +1,16 @@
[
{
"date": "2025-04-02",
"version": "2.9.0",
"minVersion": "1.5.0",
"minJavaVersion": "1.8",
"updates": {
"su3": {
"torrent": "magnet:?xt=urn:btih:88bfdbc25eeef113ba3105f9a47eb74734e79396&dn=i2pwinupdate.su3&tr=http%3A%2F%2Ftracker2.postman.i2p%2Fannounce.php",
"url": [
"http://ekm3fu6fr5pxudhwjmdiea5dovc3jdi66hjgop4c7z7dfaw7spca.b32.i2p/i2pwinupdate.su3"
]
}
}
}
]

20
docker-news.sh Executable file
View File

@ -0,0 +1,20 @@
#! /usr/bin/env sh
dir=$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)
echo "Changing to xml working dir: $dir"
cd "$dir" || exit 1
echo "Removing old backup build directory"
rm "$dir/build.old" -rf
echo "Moving build directory to build.old"
mv "$dir/build" "$dir/build.old"
echo "Building signing container i2p.newsxml"
docker build -t i2p.newsxml.signing -f Dockerfile.signing .
echo "Removing old signing container"
docker rm -f i2p.newsxml.signing
echo "Running signing container"
docker run -it \
-u $(id -u):$(id -g) \
--name i2p.newsxml.signing \
-v $HOME/.i2p-plugin-keys/:/.i2p-plugin-keys/:ro \
-v $HOME/i2p/:/i2p/:ro \
i2p.newsxml.signing
docker cp i2p.newsxml.signing:/opt/i2p.newsxml/build build

27
docker-newsxml.sh Executable file
View File

@ -0,0 +1,27 @@
#! /usr/bin/env sh
dir=$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)
echo "Changing to xml working dir: $dir"
cd "$dir" || exit 1
if [ -f "etc/su3.vars" ]; then
. etc/su3.vars
fi
if [ -f "etc/su3.vars.custom" ]; then
. etc/su3.vars.custom
fi
if [ -f "etc/su3.vars.custom.docker" ]; then
. etc/su3.vars.custom.docker
fi
if [ -d "$dir/build" ]; then
echo "Building hosting container i2p.newsxml"
docker build -t i2p.newsxml .
echo "Removing old newsxml container"
docker rm -f newsxml
echo "Running newsxml container"
docker run -d --restart=always --name "$DOCKERNAME" -p 127.0.0.1:"$SERVEPORT":3000 i2p.newsxml
else
echo "No build directory found. Perform the signing procedure with news.sh or docker-news.sh."
exit 1
fi

View File

@ -1 +1 @@
feedgen==0.3.1
feedgen>=0.3.1

View File

@ -4,3 +4,7 @@ I2P=$HOME/i2p
KS=su3keystore.ks
# signer
SIGNER=yourname@mail.i2p
# port, used for Docker only
SERVEPORT=3000
# Name to use when serving news in a docker container
DOCKERNAME=newsxml

View File

@ -1,6 +1,7 @@
#!./env/bin/python
# -*- coding: utf-8 -*-
from datetime import datetime
import collections
from feedgen.feed import FeedGenerator
import glob
import json
@ -8,28 +9,71 @@ from lxml import etree
import re
import os.path
DATA_DIR = 'data'
I2P_OS = os.getenv("I2P_OS", "")
I2P_BRANCH = os.getenv("I2P_BRANCH", "")
DATA_DIR = os.path.join('data')
RELEASE_DIR = os.path.join(DATA_DIR, I2P_OS, I2P_BRANCH)
ENTRIES_FILE = os.path.join(DATA_DIR, 'entries.html')
PLATFORM_ENTRIES_FILE = os.path.join(DATA_DIR, I2P_OS, I2P_BRANCH, 'entries.html')
TRANSLATED_ENTRIES_FILES = os.path.join(DATA_DIR, 'translations/entries.*.html')
RELEASES_FILE = os.path.join(DATA_DIR, 'releases.json')
TRANSLATED_PLATFORM_ENTRIES_FILES = os.path.join(DATA_DIR, I2P_OS, I2P_BRANCH, 'translations/entries.*.html')
RELEASES_FILE = os.path.join(RELEASE_DIR, 'releases.json')
CRL_FILES = os.path.join(DATA_DIR, 'crls/*.crl')
BLOCKLIST_FILE = os.path.join(DATA_DIR, 'blocklist.xml')
BUILD_DIR = 'build'
BUILD_DIR = os.path.join('build', I2P_OS, I2P_BRANCH)
NEWS_FILE = os.path.join(BUILD_DIR, 'news.atom.xml')
TRANSLATED_NEWS_FILE = os.path.join(BUILD_DIR, 'news_%s.atom.xml')
def load_feed_metadata(fg):
fg.id('urn:uuid:60a76c80-d399-11d9-b91C-543213999af6')
fg.link( href='http://i2p-projekt.i2p/' )
fg.link( href='http://echelon.i2p/news/news.atom.xml', rel='self' )
fg.link( href='http://psi.i2p/news/news.atom.xml', rel='alternate' )
fg.link( href='http://tc73n4kivdroccekirco7rhgxdg5f3cjvbaapabupeyzrqwv5guq.b32.i2p/news.atom.xml', rel='self' )
fg.link( href='http://dn3tvalnjz432qkqsvpfdqrwpqkw3ye4n4i2uyfr4jexvo3sp5ka.b32.i2p/news/news.atom.xml', rel='alternate' )
def load_entries(fg, entries_file):
def load_entries(fg, entries_file, platform_entries_file=None):
metadatas = {}
finalentries = {}
print('Loading entries from %s' % entries_file)
entries = prepare_entries_file(fg, entries_file)
# split() creates a junk final element with trailing </div>
for entry_str in entries[:-1]:
entry_parts = entry_str.split('</details>', 1)
md = extract_entry_metadata(entry_parts[0])
metadatas[md['published']] = md
finalentries[md['id']] = entry_parts[1]
if os.path.exists(platform_entries_file) and platform_entries_file != entries_file and platform_entries_file is not None and platform_entries_file != "data/entries.html":
print('Loading platform entries from %s' % platform_entries_file)
entries = prepare_entries_file(fg, platform_entries_file)
for entry_str in entries[:-1]:
entry_parts = entry_str.split('</details>', 1)
md = extract_entry_metadata(entry_parts[0])
metadatas[md['updated']] = md
finalentries[md['id']] = entry_parts[1]
sorted_metadata = collections.OrderedDict(sorted(metadatas.items()))
for metadata in sorted_metadata.values():
fe = fg.add_entry()
fe.id(metadata['id'])
fe.title(metadata['title'])
fe.summary(metadata['summary'])
fe.link( href=metadata['href'] )
fe.author( name=metadata['author'] )
fe.published(metadata['published'])
fe.updated(metadata['updated'])
fe.content(finalentries[metadata['id']], type='xhtml')
def prepare_entries_file(fg, entries_file=None):
with open(entries_file) as f:
entries_data = f.read().strip('\n')
# Replace HTML non-breaking space with unicode
entries_data = entries_data.replace('&nbsp;', u'\u00a0')
entries_data = entries_data.replace('&nbsp;', '\u00a0')
# Strip the leading <div> from translations
if entries_data.startswith('<div>'):
entries_data = entries_data[5:]
@ -39,24 +83,14 @@ def load_entries(fg, entries_file):
fg.subtitle(entries_parts[0].split('>')[1])
entries = entries_parts[1].split('</article>')
# split() creates a junk final element with trailing </div>
for entry_str in entries[:-1]:
entry_parts = entry_str.split('</details>', 1)
metadata = extract_entry_metadata(entry_parts[0])
return entries
fe = fg.add_entry()
fe.id(metadata['id'])
fe.title(metadata['title'])
fe.summary(metadata['summary'])
fe.link( href=metadata['href'] )
fe.author( name=metadata['author'] )
fe.published(metadata['published'])
fe.updated(metadata['updated'])
fe.content(entry_parts[1], type='xhtml')
def extract_entry_metadata(s):
m = {k:v.strip('"') for k,v in re.findall(r'(\S+)=(".*?"|\S+)', s)}
m['summary'] = re.findall(r'<summary>(.*)</summary>', s)[0]
summary = re.findall(r'<summary>(.*)</summary>', s, re.DOTALL)
if len(summary) > 0:
m['summary'] = summary[0]
return m
def load_releases(fg):
@ -110,20 +144,20 @@ def load_blocklist(fg):
b.from_xml(root.getchildren()[0])
def generate_feed(entries_file=None):
def generate_feed(entries_file=None, platform_entries_file=None):
language = entries_file and entries_file.split('.')[1] or 'en'
fg = FeedGenerator()
fg.load_extension('i2p')
fg.language(language)
load_feed_metadata(fg)
load_entries(fg, entries_file and entries_file or ENTRIES_FILE)
load_entries(fg, entries_file and entries_file or ENTRIES_FILE, platform_entries_file and platform_entries_file or PLATFORM_ENTRIES_FILE)
load_releases(fg)
load_revocations(fg)
load_blocklist(fg)
if not os.path.exists(BUILD_DIR):
os.mkdir(BUILD_DIR)
os.makedirs(BUILD_DIR)
fg.atom_file(entries_file and TRANSLATED_NEWS_FILE % language or NEWS_FILE, pretty=True)
if __name__ == '__main__':

37
news.sh
View File

@ -1,6 +1,7 @@
#!/bin/sh
BUILD=./build
BUILD=./build/"$I2P_OS"/"$I2P_BRANCH"
RELEASES=./data/"$I2P_OS"/"$I2P_BRANCH"/releases.json
NEWS_PREFIX=$BUILD/news_
ATOM_SUFFIX=.atom.xml
TMP=$BUILD/tmp
@ -42,8 +43,10 @@ show_su3_and_mv () {
mv $file $BUILD
}
./generate_news.py
final_generate_signed_feeds () {
echo "Generating signed feeds"
python3 ./generate_news.py
#sleep 20s
mkdir -p $TMP
@ -71,3 +74,31 @@ done
rm -r $TMP
echo
ls -l $BUILD
}
I2P_OSS="win mac mac-arm64 $I2P_OSS"
I2P_BRANCHES="beta stable testing $I2P_BRANCHES"
if [ -z $I2P_OS ]; then
if [ -z $I2P_BRANCH ]; then
final_generate_signed_feeds
for I2P_OS in $I2P_OSS; do
for I2P_BRANCH in $I2P_BRANCHES; do
echo "building news for: $I2P_OS, $I2P_BRANCH."
export I2P_OS
export I2P_BRANCH
./news.sh
done
done
else
if [ -f $RELEASES ]; then
final_generate_signed_feeds
fi
fi
else
if [ -f $RELEASES ]; then
final_generate_signed_feeds
fi
fi

View File

@ -9,6 +9,6 @@ setup(
description='I2P Atom extension for feedgen',
author='str4d',
install_requires="feedgen==0.3.1",
install_requires="feedgen>=0.3.1",
packages=['feedgen.ext'],
)

View File

@ -7,7 +7,7 @@ if [ ! $venv ]; then
exit 1
else
if [ ! -d $venv_dir ] ; then
if $venv --version | grep '[2-9][0-9].0.*'; then
if $venv --version | awk -F: '{if($2>20)print$2}' ; then
$venv $venv_dir
else
$venv --distribute $venv_dir

14
test.sh Executable file
View File

@ -0,0 +1,14 @@
#! /usr/bin/env sh
# This script is used to download and extract the latest news from I2P
# and display it on a terminal. I use it to test when I check in the news.
i2p() {
java -jar ~/i2p/lib/i2p.jar "$@"
}
if [ ! -f news.su3 ]; then
echo "Downloading news.su3..."
eepget http://tc73n4kivdroccekirco7rhgxdg5f3cjvbaapabupeyzrqwv5guq.b32.i2p/news.su3
fi
i2p su3file extract -x news.su3
gunzip news.xml.gz
less news.xml

10
validate_html.sh Executable file
View File

@ -0,0 +1,10 @@
#
# check that all the html files are valid xml
# sudo apt install libxml2-utils
# no output = pass
# zzz 1/23
#
for i in `find -name *.html`
do
xmllint $i > /dev/null || echo "FAIL $i"
done