inso24: fix post
This commit is contained in:
parent
fb6d837d31
commit
97404e467e
|
@ -2,7 +2,7 @@ builddir = build
|
||||||
|
|
||||||
pandocflags = -M wf-embed-base=https://git.lain.faith/haskal/writeups/raw/branch/main/ -M wf-link-base=https://git.lain.faith/haskal/writeups/src/branch/main/ --filter writefreely-validate --wrap=none --strip-comments
|
pandocflags = -M wf-embed-base=https://git.lain.faith/haskal/writeups/raw/branch/main/ -M wf-link-base=https://git.lain.faith/haskal/writeups/src/branch/main/ --filter writefreely-validate --wrap=none --strip-comments
|
||||||
|
|
||||||
postid = temp
|
postid = ckzulowi2i
|
||||||
|
|
||||||
rule pandoc
|
rule pandoc
|
||||||
command = pandoc $pandocflags -o $out $in
|
command = pandoc $pandocflags -o $out $in
|
||||||
|
|
|
@ -368,7 +368,7 @@ so i opened up the man page for bash..........and then i immediately gave up and
|
||||||
@rhelmot whether there was any cheese with bash environment variables you could do, and she offered
|
@rhelmot whether there was any cheese with bash environment variables you could do, and she offered
|
||||||
up `BASH_ENV`
|
up `BASH_ENV`
|
||||||
|
|
||||||
```
|
```text
|
||||||
BASH_ENV
|
BASH_ENV
|
||||||
If this parameter is set when bash is executing a shell script, its value is interpreted as a
|
If this parameter is set when bash is executing a shell script, its value is interpreted as a
|
||||||
filename containing commands to initialize the shell, as in ~/.bashrc. The value of BASH_ENV
|
filename containing commands to initialize the shell, as in ~/.bashrc. The value of BASH_ENV
|
||||||
|
@ -629,7 +629,7 @@ needed to gain code execution. notice that `pts.txt` is in the `quizzes` directo
|
||||||
allowed input because it's 7 chars and only uses allowed characters. what happens if we try to run
|
allowed input because it's 7 chars and only uses allowed characters. what happens if we try to run
|
||||||
the quiz `pts.txt`?
|
the quiz `pts.txt`?
|
||||||
|
|
||||||
```
|
```bash
|
||||||
$ make username=user quizz=pts.txt
|
$ make username=user quizz=pts.txt
|
||||||
pts.txt:1:1: error: expected ‘,’ or ‘;’ at end of input
|
pts.txt:1:1: error: expected ‘,’ or ‘;’ at end of input
|
||||||
1 | user = {1,2,3,4,5,6,1}
|
1 | user = {1,2,3,4,5,6,1}
|
||||||
|
@ -665,7 +665,7 @@ this actually compiles, and interestingly enough just `main = { .... };` still c
|
||||||
run because `main` gets put in `.data` which is not normally executable. hence the `const` in the
|
run because `main` gets put in `.data` which is not normally executable. hence the `const` in the
|
||||||
above example. that actually causes main to get put in `.rodata`
|
above example. that actually causes main to get put in `.rodata`
|
||||||
|
|
||||||
```
|
```bash
|
||||||
gcc -x c -w - <<EOF
|
gcc -x c -w - <<EOF
|
||||||
const int main[] = {
|
const int main[] = {
|
||||||
-443987883, 440, 113408, -1922629632,
|
-443987883, 440, 113408, -1922629632,
|
||||||
|
@ -859,6 +859,6 @@ insomni'hack teaser wasn't one of these ctfs
|
||||||
both of these misc challenges were really interesting and presented novel exploitation paths that
|
both of these misc challenges were really interesting and presented novel exploitation paths that
|
||||||
needed to work around very tight constraints. and solving them was a lot of fun
|
needed to work around very tight constraints. and solving them was a lot of fun
|
||||||
|
|
||||||
```
|
```c
|
||||||
const int main[] = {15544, 268382464, 5};
|
const int main[] = {15544, 268382464, 5};
|
||||||
```
|
```
|
||||||
|
|
Loading…
Reference in New Issue