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

[FEAT]: activate OpenCL for the flatpak application #499

Open
claudioandre-br opened this issue Aug 18, 2024 · 1 comment
Open

[FEAT]: activate OpenCL for the flatpak application #499

claudioandre-br opened this issue Aug 18, 2024 · 1 comment
Labels
binaries Binaries will be impacted external issues Only an external entity can solve the problem properly help wanted Extra attention is needed O: backlog Backlog (stale ignores this label)

Comments

@claudioandre-br
Copy link
Member

Description

Currently, OpenCL flatpak works (could work [1]) for the CPU [2].

At the moment, the only way to use a john "containerized package" with GPU access is via Docker. Offering access to all important john resources securely via flapak [3] is something that offers value to the end user.

It seems this is/will be possible soon (at least for NVIDIA):
https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/1535

[1] OpenCL is disabled in flatpak binaries.
[2] I've tested it a bit, but unfortunately I don't own any suitable hardware. I've never tested it with a GPU.
[3] I mean, OpenCL in a sandboxed app.

Alternatives Considered

No response

Additional Context

Deploy john with OpenCL support in a secure, sandboxed and containerized way will allow users to use the full power of the tool, protected against a good number of flaws that may exist in the binary during the development process.

  • I won't be able to test it (no hardware). But the changes are safe and easy to “understand”: enable OpenCL and add the necessary permissions/extensions.
  • I use snap, but IMO flatpak is taking a better route.
@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 Aug 18, 2024
@claudioandre-br
Copy link
Member Author

See flathub/com.openwall.John#13

@claudioandre-br claudioandre-br added O: backlog Backlog (stale ignores this label) and removed keep open Do NOT close automatically. labels Nov 16, 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 O: backlog Backlog (stale ignores this label)
Projects
None yet
Development

No branches or pull requests

1 participant