Package Details: i2p 2.7.0-1

Git Clone URL: https://aur.archlinux.org/i2p.git (read-only, click to copy)
Package Base: i2p
Description: A distributed anonymous network
Upstream URL: https://geti2p.net
Keywords: anonymous censorship encrypted i2p network
Licenses: GPL2
Conflicts: i2p-bin, i2p-dev
Submitter: Mikos
Maintainer: Salama
Last Packager: Salama
Votes: 318
Popularity: 0.59
First Submitted: 2005-09-04 19:46 (UTC)
Last Updated: 2024-10-09 18:13 (UTC)

Dependencies (4)

Sources (9)

Pinned Comments

Salama commented on 2023-04-01 09:18 (UTC) (edited on 2024-06-24 12:01 (UTC) by Salama)

You can download the keys from https://geti2p.net/_static/idk.key.asc and https://geti2p.net/_static/zzz.key.asc then gpg --import

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 27 Next › Last »

jpg commented on 2015-05-26 17:15 (UTC)

Hi, i also had (like D101101) the following problem: "error: unmappable character for encoding ASCII" i was able to solve it by doing this before the makepkg 'LANG="en_US.UTF-8"'

<deleted-account> commented on 2015-04-13 04:26 (UTC)

https://geti2p.net/en/blog/post/2015/04/12/0.9.19-Release

skydrome commented on 2015-02-24 16:47 (UTC)

https://geti2p.net/en/blog/post/2015/02/22/0.9.18-Release

skydrome commented on 2015-02-12 02:15 (UTC)

Great, glad this is getting sorted now, next release in a few weeks

zin commented on 2015-02-09 09:58 (UTC)

The key from https://geti2p.net/en/get-involved/develop/release-signing-key is EE7256A8: "zzz on i2p (key signing) <zzz@mail.i2p>" You can add it manually from specified keyserver: gpg --keyserver pool.sks-keyservers.net --recv-keys 0xEE7256A8 You can specify the keyserver in your ~/.gnupg/gpg.conf : keyserver pool.sks-keyservers.net gpg --recv-keys 0xEE7256A8 # will work if you add/uncomment in ~/.gnupg/gpg.conf keyserver-options auto-key-retrieve Then gpg will automatically get then makepkg trust the key. Please check zkai and skydome comments, follow their advice.

socrat commented on 2015-02-09 05:43 (UTC)

skydrome the problem wasnt with that. looks like the keyserver wasnt supplying the key for some time. I just check again and I got it with gpg --recv-keys 0xEE7256A8 while it failed before that.

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 27 Next › Last »