Downloads:

1,193

Downloads of v 0.9.44:

56

Last Update:

17 Feb 2020

Published Date:

17 Feb 2020

Reviewed Date:

18 Feb 2020

Reviewer:

gravatar

Package Maintainer(s):

Software Author(s):

  • I2P Team

Tags:

security privacy anonymity darknet admin

I2P

(Waiting for Maintainer to take corrective action)

0.9.44 | Updated: 17 Feb 2020

Downloads:

1,193

Downloads of v 0.9.44:

56

Published:

17 Feb 2020

Reviewed:

18 Feb 2020

Reviewer:

gravatar

Maintainer(s):

Software Author(s):

  • I2P Team

I2P 0.9.44

(Waiting for Maintainer to take corrective action)

Some Checks Have Failed or Are Not Yet Complete

1 Test Failing and 1 Passing Test


Validation Testing Failed


Verification Testing Passed

Details

This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.

  • Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
  • This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
  • You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
  • There are also no guarantees that it will be approved.

There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.

Sanshiro (maintainer) on 22 Jan 2020 16:07:02 +00:00:

User 'Sanshiro' (maintainer) submitted package.

chocolatey-ops (reviewer) on 22 Jan 2020 16:43:17 +00:00:

i2p has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • The DocsUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The LicenseUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectSourceUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The MailingListUrl element in the nuspec file should be a valid Url. Please correct this More...
Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the ReleaseNotes element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...
  • In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...

chocolatey-ops (reviewer) on 22 Jan 2020 19:03:10 +00:00:

i2p has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/f802444cc48e20118e72ede0452ca42c for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

Sanshiro (maintainer) on 23 Jan 2020 16:55:30 +00:00:

User 'Sanshiro' (maintainer) submitted package.

chocolatey-ops (reviewer) on 23 Jan 2020 17:28:39 +00:00:

i2p has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • The DocsUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The LicenseUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectSourceUrl element in the nuspec file should be a valid Url. Please correct this More...
Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...

chocolatey-ops (reviewer) on 23 Jan 2020 18:12:41 +00:00:

i2p has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/96bc30dc0e2bdba14d980a02d90746e7 for details.
This is an FYI only. There is no action you need to take.

Sanshiro (maintainer) on 24 Jan 2020 16:18:06 +00:00:

User 'Sanshiro' (maintainer) submitted package.

chocolatey-ops (reviewer) on 24 Jan 2020 16:52:20 +00:00:

i2p has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • The DocsUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The LicenseUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectSourceUrl element in the nuspec file should be a valid Url. Please correct this More...
Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...

Sanshiro (maintainer) on 24 Jan 2020 17:22:36 +00:00:

User 'Sanshiro' (maintainer) submitted package.

chocolatey-ops (reviewer) on 24 Jan 2020 18:00:05 +00:00:

i2p has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • The DocsUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The LicenseUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectSourceUrl element in the nuspec file should be a valid Url. Please correct this More...
Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...

chocolatey-ops (reviewer) on 24 Jan 2020 18:29:15 +00:00:

i2p has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/e517b530c27b5966c7bcb281ae388ef7 for details.
This is an FYI only. There is no action you need to take.

Sanshiro (maintainer) on 25 Jan 2020 16:26:55 +00:00:

User 'Sanshiro' (maintainer) submitted package.

chocolatey-ops (reviewer) on 25 Jan 2020 17:00:09 +00:00:

i2p has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • The DocsUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The LicenseUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectSourceUrl element in the nuspec file should be a valid Url. Please correct this More...
Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...

Sanshiro (maintainer) on 25 Jan 2020 17:38:26 +00:00:

How to fix this validation testing error?
> In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL

chocolatey-ops (reviewer) on 25 Jan 2020 19:23:15 +00:00:

i2p has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/3c4716c52573fbadb347b88db8b71552 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

chocolatey-ops (reviewer) on 14 Feb 2020 19:25:33 +00:00:

We've found i2p v0.9.44 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

  • Log in to the site and respond to the review comments.
  • Resubmit fixes for this version.
  • If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

Sanshiro (maintainer) on 16 Feb 2020 16:55:15 +00:00:

User 'Sanshiro' (maintainer) submitted package.

chocolatey-ops (reviewer) on 16 Feb 2020 17:29:27 +00:00:

i2p has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • The DocsUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The LicenseUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectSourceUrl element in the nuspec file should be a valid Url. Please correct this More...
Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...

chocolatey-ops (reviewer) on 16 Feb 2020 18:46:16 +00:00:

i2p has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/814c34ddcc652467d523a52975bc9be7 for details.
This is an FYI only. There is no action you need to take.

Sanshiro (maintainer) on 17 Feb 2020 15:36:09 +00:00:

User 'Sanshiro' (maintainer) submitted package.

chocolatey-ops (reviewer) on 17 Feb 2020 16:08:50 +00:00:

i2p has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • The DocsUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The LicenseUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectSourceUrl element in the nuspec file should be a valid Url. Please correct this More...

chocolatey-ops (reviewer) on 17 Feb 2020 17:34:26 +00:00:

i2p has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/8e09f5b613d19a93901e2027f475d0e4 for details.
This is an FYI only. There is no action you need to take.

Pauby (reviewer) on 18 Feb 2020 16:24:21 +00:00:

Rerunning tests.
Auto Validation Change - Validation tests have been set to rerun.

chocolatey-ops (reviewer) on 18 Feb 2020 16:29:07 +00:00:

i2p has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • The DocsUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The LicenseUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectUrl element in the nuspec file should be a valid Url. Please correct this More...
  • The ProjectSourceUrl element in the nuspec file should be a valid Url. Please correct this More...
Description

Invisible Internet Project (I2P) is an anonymous network, exposing a simple layer that applications can use to anonymously and securely send messages to each other. The network itself is strictly message based (a la IP), but there is a library available to allow reliable streaming communication on top of it (a la TCP). All communication is end to end encrypted (in total there are four layers of encryption used when sending a message), and even the end points ("destinations") are cryptographic identifiers (essentially a pair of public keys).

Install options

  • Service is not installed; scripts to do so are in $Env:ProgramFiles\i2p

Post-install notes

  • Executing "Start I2P.exe" will start background service and launch default browser to connect to local console

You can learn more about i2p at the Software Site.


tools\chocolateyInstall.ahk
; default environment
DetectHiddenWindows, off
SetKeyDelay, 100

; modified environment
#NoEnv
#NoTrayIcon
DetectHiddenText, off
SetTitleMatchMode, 2

; variables
winTitleLang      = Language Selection ahk_class SunAwtDialog ahk_exe javaw.exe
winTitleInstaller = IzPack - Installation of i2p ahk_class SunAwtFrame ahk_exe javaw.exe
winTitleDirExist  = Warning! ahk_class SunAwtDialog ahk_exe javaw.exe
winTitleDirNew    = Message ahk_class SunAwtDialog ahk_exe javaw.exe

; automate install with default options
WinWait, %winTitleLang%, , 240
WinActivate, %winTitleLang%
Send {ENTER}

WinWait, %winTitleInstaller%, , 10
WinActivate, %winTitleInstaller%
Send {ENTER}
Sleep 2000
Send {ENTER}
Sleep 2000
Send {ENTER}
Sleep 2000
Send {ENTER}
Sleep 2000
Send {ENTER}
Sleep 2000
Send {ENTER}
Sleep 50000
Send {ENTER}
Sleep 2000
Send {ENTER}
Sleep 2000
Send {ENTER}

Loop, 1000 {
  IfWinExist, %winTitleDirExist% 
  {
    WinActivate
    Send {ENTER}
  }
  IfWinExist, %winTitleDirNew% 
  {
    WinActivate
    Send {ENTER}
  }
  IfWinExist, %winTitleInstaller% 
  {
    WinActivate
    Send {ENTER}
  }
  Else
    break
  Sleep 150
}
tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop';

$toolsDir = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$ahkExe   = 'AutoHotKey'
$ahkFile  = Join-Path $toolsDir "chocolateyInstall.ahk"
Start-Process $ahkExe $ahkFile

$packageArgs = @{
  packageName    = 'i2p'
  fileType       = 'exe'
  url            = 'https://download.i2p2.de/releases/0.9.44/i2pinstall%5F0.9.44%5Fwindows.exe'
  silentArgs     = ''
  validExitCodes = @(0)
  softwareName   = 'i2p*'
  checksum       = '4d25819a846a461e6e87caf7f44dd03eb755d502e8efe990bfb0dc5af2ce9d5f'
  checksumType   = 'sha256'
  toolsDir       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
}
Install-ChocolateyPackage @packageArgs
tools\chocolateyUninstall.ahk
; default environment
DetectHiddenWindows, off
SetKeyDelay, 100

; modified environment
#NoEnv
#NoTrayIcon
DetectHiddenText, off
SetTitleMatchMode, 2

; variables
winTitleInstaller = Uninstall ahk_class SunAwtFrame ahk_exe java.exe

; automate uninstall with default options
WinWait, %winTitleInstaller%, , 60
WinActivate, %winTitleInstaller%, , 60
Send {SPACE}
Send {TAB}
Send {ENTER}
Sleep 2000
Send {ENTER}
Sleep 2000
Send {ENTER}
tools\chocolateyUninstall.ps1
$ErrorActionPreference = 'Stop';

$toolsDir = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$ahkExe   = 'AutoHotKey'
$ahkFile  = Join-Path $toolsDir "chocolateyUninstall.ahk"
Start-Process $ahkExe $ahkFile

$uninstallerFile = "${env:ProgramFiles}\i2p\Uninstaller\uninstaller.jar"
Start-Process $uninstallerFile

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
I2P 0.9.44 56 Monday, February 17, 2020 Waiting for Maintainer gravatar

Discussion for the I2P Package

Ground Rules:

  • This discussion is only about I2P and the I2P package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or I2P, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus