Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attract the unknown contributor #384

Closed
claudioandre-br opened this issue May 16, 2024 · 2 comments
Closed

Attract the unknown contributor #384

claudioandre-br opened this issue May 16, 2024 · 2 comments
Labels
binaries Binaries will be impacted external issues Only an external entity can solve the problem properly help wanted Extra attention is needed stale

Comments

@claudioandre-br
Copy link
Member

claudioandre-br commented May 16, 2024

1. Is your feature request related to a problem? Please describe

Some john installation tutorial that is popular on the internet [1] created a method for installing john by downloading packages from john-packages (specially the Windows .7z file).

This is very good:

  • However, this tutorial seems to be highlighting the bleeding version when the latest version (currently 1.9J1+2404) should be the most recommended for this.
  • Still, it seems that there is automation in this process. So, we would like to recommend that the person adds validation and printing of file hashes to the "installer" in order to add reliability and transparency to the process.

[1] There are hundreds of downloads per day of the Windows .7z package. These numbers are not reflected in access to the repository, that is, these people do not have access to our quality controls (checksums/attestations).

2. Describe the solution you'd like

I would like to recommend that the contributor adds validation e transparency to the process.


========== BTW ==========

Caution

🔍 Please use discretion when accessing sites that claim to be sources for John the Ripper download.

@claudioandre-br claudioandre-br added help wanted Extra attention is needed binaries Binaries will be impacted external issues Only an external entity can solve the problem properly keep open Do NOT close automatically. labels May 16, 2024
claudioandre-br added a commit that referenced this issue May 18, 2024
It's good for providing transparency into what is happening in the
project.

See #384.

Signed-off-by: Claudio André <dev@claudioandre.slmail.me>
claudioandre-br added a commit that referenced this issue May 18, 2024
It's good for providing transparency into what is happening in the
project.

See #384.

Signed-off-by: Claudio André <dev@claudioandre.slmail.me>
claudioandre-br added a commit that referenced this issue May 18, 2024
It's good for providing transparency into what is happening in the
project.

See #384.

Signed-off-by: Claudio André <dev@claudioandre.slmail.me>
claudioandre-br added a commit that referenced this issue May 19, 2024
It's good for providing transparency into what is happening in the
project.

See #384.

Signed-off-by: Claudio André <dev@claudioandre.slmail.me>
claudioandre-br added a commit that referenced this issue May 21, 2024
It's good for providing transparency into what is happening in the
project.

See #384.

Signed-off-by: Claudio André <dev@claudioandre.slmail.me>
claudioandre-br added a commit that referenced this issue May 22, 2024
It's good for providing transparency into what is happening in the
project.

See #384.

Signed-off-by: Claudio André <dev@claudioandre.slmail.me>
@claudioandre-br claudioandre-br removed the keep open Do NOT close automatically. label Jun 14, 2024
Copy link

This issue is stale because it has been open for 14 days with no activity.

@github-actions github-actions bot added the stale label Jun 29, 2024
Copy link

github-actions bot commented Jul 7, 2024

"This issue was closed because it has been inactive for 7 days since being marked as stale."

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
binaries Binaries will be impacted external issues Only an external entity can solve the problem properly help wanted Extra attention is needed stale
Projects
None yet
Development

No branches or pull requests

1 participant