/explore
|
You are here 
|
0xboku.com | ||
| | | | |
blog.nuculabs.de
|
|
| | | | | Hello and welcome to Nucu Labs agent! We've been contracted by some external contractors to help them break..., I mean, assist them in making their life easier with their "competition". We obtained their competition's software from a poorly configured AWS server. Their competition, X, uses the software in order to setup a private communication channel to their servers, the software is simple, it fires up a server, listens on a port and waits for the right password, when the right password is entered, the server remembers the client and stops asking for passwords, simple. | |
| | | | |
blog.dornea.nu
|
|
| | | | | [AI summary] The blog post discusses the process of creating and executing a shellcode in C to read a file named 'flag.txt' and dump its content, including assembly code, compilation steps, and execution considerations. | |
| | | | |
zerosum0x0.blogspot.com
|
|
| | | | | On Linux systems, you can include system() from the standard C library to easily shell a Postgres server. The mechanism for Windows is a bit... | |
| | | | |
hjr265.me
|
|
| | | I have lines like these in my /etc/hosts file: 127.0.0.1 toph.local 127.0.0.1 drafts.toph.local 127.0.0.1 quiz.toph.local I can run development servers locally and access them over .local hostnames (e.g. toph.local) instead of the loopback IP addresses (e.g. 127.0.0.1). It works fine. But every time I start working on a new project, I needed to add a new line to the /etc/hosts file. It didn't sit right with me. I should be able to point all *. | ||
