-
Notifications
You must be signed in to change notification settings - Fork 63
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
The ssh run_expensive() method should have a _safe() variant #3118
Labels
Comments
praiskup
added a commit
to praiskup/copr
that referenced
this issue
Feb 2, 2024
praiskup
added a commit
to praiskup/copr
that referenced
this issue
Feb 2, 2024
praiskup
added a commit
to praiskup/copr
that referenced
this issue
Feb 2, 2024
praiskup
added a commit
to praiskup/copr
that referenced
this issue
Feb 2, 2024
praiskup
added a commit
to praiskup/copr
that referenced
this issue
Feb 3, 2024
praiskup
added a commit
to praiskup/copr
that referenced
this issue
Feb 3, 2024
praiskup
added a commit
to praiskup/copr
that referenced
this issue
Feb 3, 2024
praiskup
added a commit
to praiskup/copr
that referenced
this issue
Feb 3, 2024
praiskup
added a commit
to praiskup/copr
that referenced
this issue
Feb 4, 2024
praiskup
added a commit
to praiskup/copr
that referenced
this issue
Feb 4, 2024
praiskup
added a commit
to praiskup/copr
that referenced
this issue
Feb 5, 2024
praiskup
added a commit
to praiskup/copr
that referenced
this issue
Feb 5, 2024
praiskup
added a commit
that referenced
this issue
Feb 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The command-over-ssh may produce a large output, feeding backend's memory
and DoS it. With #2977 merged, we should make sure the output is somewhat
safe to read into memory (e.g. piping through /usr/bin/head on-host, as the
remote utility is not trusted).
The text was updated successfully, but these errors were encountered: