Private/Public key generation for local builds #104
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The default key generation is marked as a TODO in the gradle/i2p-make-plugin.gradle file. Detail manual steps as a workaround in order to allow local builds.
|
Figured out the issue with deployment and updated the README with those notes. |
grooveadelic
force-pushed
the
using-local-signing-keys
branch
from
ea4a0b4 to
8b99fa7
Compare
grooveadelic
force-pushed
the
using-local-signing-keys
branch
from
8b99fa7 to
842dea9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not familiar enough with gradle to straight up change the TODO line. Should I make that change by running the steps detailed in the README as shell commands?
Additionally, how do I trust additional signers in my I2P router?