fix: xml parsing error caused by an apostrophe
This commit is contained in:
parent
2dc52c870f
commit
2c7dcea6ba
@ -40,13 +40,22 @@ services:
|
|||||||
nginx:
|
nginx:
|
||||||
image: nginx:latest
|
image: nginx:latest
|
||||||
container_name: nginx-onion
|
container_name: nginx-onion
|
||||||
command:
|
command:
|
||||||
volumes:
|
volumes:
|
||||||
- ./web/config/onion-default.conf:/etc/nginx/conf.d/default.conf:rw
|
- ./web/config/onion-default.conf:/etc/nginx/conf.d/default.conf:rw
|
||||||
- ./web/public:/usr/share/nginx/html:ro
|
- ./web/public:/usr/share/nginx/html:ro
|
||||||
- nginx-tor-socket:/var/run/onion-sockets:rw
|
- nginx-tor-socket:/var/run/onion-sockets:rw
|
||||||
healthcheck:
|
healthcheck:
|
||||||
test: ["CMD", "curl", "-f", "--unix-socket", "/var/run/onion-sockets/site.sock", "||", "exit 1"]
|
test:
|
||||||
|
[
|
||||||
|
"CMD",
|
||||||
|
"curl",
|
||||||
|
"-f",
|
||||||
|
"--unix-socket",
|
||||||
|
"/var/run/onion-sockets/site.sock",
|
||||||
|
"||",
|
||||||
|
"exit 1",
|
||||||
|
]
|
||||||
interval: 10s
|
interval: 10s
|
||||||
timeout: 5s
|
timeout: 5s
|
||||||
retries: 5
|
retries: 5
|
||||||
@ -126,7 +135,10 @@ add_header Onion-Location http://golfed6fzytoktol4de4o4nerap3xuykhfm5makfzscib65
|
|||||||
Or alternatively include an HTML `<meta>` attribute:
|
Or alternatively include an HTML `<meta>` attribute:
|
||||||
|
|
||||||
```html
|
```html
|
||||||
<meta http-equiv="onion-location" content="http://golfed6fzytoktol4de4o4nerap3xuykhfm5makfzscib65df3khnpyd.onion" />
|
<meta
|
||||||
|
http-equiv="onion-location"
|
||||||
|
content="http://golfed6fzytoktol4de4o4nerap3xuykhfm5makfzscib65df3khnpyd.onion"
|
||||||
|
/>
|
||||||
```
|
```
|
||||||
|
|
||||||
Notably, with proxying enabled through Cloudflare, I encountered difficulties in getting the response headers to pass through to the client, necessitating the use of the `<meta>` attribute instead.
|
Notably, with proxying enabled through Cloudflare, I encountered difficulties in getting the response headers to pass through to the client, necessitating the use of the `<meta>` attribute instead.
|
||||||
@ -148,4 +160,3 @@ I highly recommend checking out the sites I browsed while figuring this stuff ou
|
|||||||
- ["Connect two NGINX's through UNIX sockets" by David Sierra](https://blog.davidsierra.dev/posts/connect-nginxs-through-sockets/)
|
- ["Connect two NGINX's through UNIX sockets" by David Sierra](https://blog.davidsierra.dev/posts/connect-nginxs-through-sockets/)
|
||||||
- ["Create a complete Tor Onion Service with Docker and OpenSUSE in less than 15 minutes" by Jason S. Evans](https://www.youtube.com/watch?v=iUxiTk6w1sc)
|
- ["Create a complete Tor Onion Service with Docker and OpenSUSE in less than 15 minutes" by Jason S. Evans](https://www.youtube.com/watch?v=iUxiTk6w1sc)
|
||||||
- [Onionscan Documentation](https://onionscan.org/)
|
- [Onionscan Documentation](https://onionscan.org/)
|
||||||
|
|
||||||
|
@ -9,7 +9,7 @@ categories = []
|
|||||||
|
|
||||||
In the ever-evolving landscape of malware, Shellcode Reflective DLL Injection (RDI) stands as a formidable technique despite its age, distinguished by its stealth and efficiency. Unlike traditional DLL injection methods, which often leave apparent traces for AV systems to detect, RDI operates on a more subtle level. Basically it challenges typical defensive solutions such as behavior monitoring, heuristics, or signature-based detection.
|
In the ever-evolving landscape of malware, Shellcode Reflective DLL Injection (RDI) stands as a formidable technique despite its age, distinguished by its stealth and efficiency. Unlike traditional DLL injection methods, which often leave apparent traces for AV systems to detect, RDI operates on a more subtle level. Basically it challenges typical defensive solutions such as behavior monitoring, heuristics, or signature-based detection.
|
||||||
|
|
||||||
Implementing a reflective loader myself provided a great insight into PE files and Windows API, and it's definitely a good initial foothold into more advanced techniques.
|
Implementing a reflective loader myself provided a great insight into PE files and Windows API, and it is definitely a good initial foothold into more advanced techniques.
|
||||||
|
|
||||||
## Steps
|
## Steps
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user