Add basic RISCV64 shellcraft support #2322
Merged
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 `mov` template isn't 100% null-byte and newline free for all inputs. Certain larger values are just emitted using the `li` pseudo-instruction by the assembler which might contain null-bytes. Co-authored-by: LevitatingLion <[email protected]>
diet-libc doesn't support RISCV, so borrow from musl. Need to consider their license.
|
This worked for me for a while so I'll merge and gather feedback when other start using it. |
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.
Add the minimum shellcraft templates to be able to use the generated linux syscall templates under RISCV64.
The
movtemplate isn't 100% null-byte and newline free for all inputs yet. Larger values are just emitted using thelipseudo-instruction by the assembler which might contain null-bytes. Theecallinstruction to trigger syscalls contains null-bytes and we'd need some encoder to get around that.