diff options
| author | Timber | 2024-06-02 12:06:49 +0200 |
|---|---|---|
| committer | Timber | 2024-06-02 12:06:49 +0200 |
| commit | d8b94cdde827b4d3f175112ebc31d7ec96b8cb24 (patch) | |
| tree | 0d2b1ccd48e4048c2a32b8e080e0546182ee35cd | |
| parent | ef450bd09e9ada80e7905fc05f2757a7d3f7c93f (diff) | |
Remove colon
| -rw-r--r-- | future-of-pwning-1.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/future-of-pwning-1.md b/future-of-pwning-1.md index 5a69abb..31cc614 100644 --- a/future-of-pwning-1.md +++ b/future-of-pwning-1.md @@ -32,7 +32,7 @@ The file is then emulated with `/app/forw -emu /tmp/binary.ex` and the last 500 ### The idea So apparently we can emulate *any* file in the *ForwardCom* file format `.ex`. -Looking at the [Github page](https://github.com/ForwardCom) we learn that ForawrdCom is an: +Looking at the [Github page](https://github.com/ForwardCom) we learn that ForawrdCom is an > [e]xperimental instruction set and computer system with variable-length vector registers. There we also find a [manual](https://github.com/ForwardCom/manual), [code examples](https://github.com/ForwardCom/code-examples) and the [bintools](https://github.com/ForwardCom/bintools) which *should* compile to the executable `forw` we already have. |