oops markdown
This commit is contained in:
parent
dd3df1366c
commit
1c465ab0b1
|
@ -45,6 +45,7 @@ decent extent. Namely, the format for strings beginning with `:\x00\x00>` and
|
|||
- @ (2 bytes)
|
||||
- @ or ?
|
||||
- `\xc1` (3 bytes)
|
||||
|
||||
An example:
|
||||
```
|
||||
b'\x00\x00\x008\x94S@\xc8.@A\x01:\xa0\xc0i\x11\xa1@|.@\xc1\x9b\x1c\xe6?'
|
||||
|
@ -89,7 +90,9 @@ Noting a delay between packets led me to derive the following packet structure:
|
|||
- JUICY DATA
|
||||
- END call
|
||||
- END packet, which is equal to the next START packet
|
||||
|
||||
This proved to be incorrect, but more on that later.
|
||||
|
||||
The following code differentiates between these packets from the netcat, where
|
||||
the variable `rawn` is the raw byte string:
|
||||
``` python
|
||||
|
@ -170,6 +173,7 @@ By playing with the packet, the format appears to go:
|
|||
- Byte 0: CA
|
||||
- Byte 1-2: Memory offset
|
||||
- Byte 3-end: Size of memory to return
|
||||
|
||||
...so if we ask for a really large chunk of data, we can get a dump.
|
||||
With the inject:
|
||||
```
|
||||
|
|
Loading…
Reference in New Issue