This commit is contained in:
writer 2024-10-15 10:29:29 +09:00
parent f5a0f7393a
commit e9b6619dcc
10 changed files with 13 additions and 15 deletions

View File

@ -387,9 +387,9 @@ ASIS_85c9febd4c15950ab1f19a6bd7a94f87
---- ----
[Paillier cryptosystem]: http://en.wikipedia.org/wiki/Paillier_cryptosystem [Paillier cryptosystem]: http://en.wikipedia.org/wiki/Paillier_cryptosystem
[here]: https://github.com/go-outside-labs/CTFs-Gray-Hacker-and-PenTesting/tree/master/CTFs_and_WarGames/2014-ASIS-CTF/crypto_paillier [here]: https://github.com/autistic-symposium/sec-pentesting-toolkit/tree/master/CTFs_and_WarGames/2014-ASIS-CTF/crypto_paillier
[modulo]: http://en.wikipedia.org/wiki/Modulo_operation [modulo]: http://en.wikipedia.org/wiki/Modulo_operation
[oracle]: http://en.wikipedia.org/wiki/Oracle_machine [oracle]: http://en.wikipedia.org/wiki/Oracle_machine
[ASIS CTF]: http://asis-ctf.ir/home/ [ASIS CTF]: http://asis-ctf.ir/home/
[Binary search]:http://en.wikipedia.org/wiki/Binary_search_algorithm [Binary search]:http://en.wikipedia.org/wiki/Binary_search_algorithm
[my scripts]: https://github.com/go-outside-labs/Python-and-Algorithms-and-Data-Structures/tree/master/src/searching_and_sorting/searching [my scripts]: https://github.com/autistic-symposium/master-algorithms-pytree/master/src/searching_and_sorting/searching

View File

@ -276,7 +276,7 @@ If you like this solution, take a look at my [exploit for this problem].
**Hack all the things!** **Hack all the things!**
[his cryptographic scheme]: http://en.wikipedia.org/wiki/Caesar_cipher [his cryptographic scheme]: http://en.wikipedia.org/wiki/Caesar_cipher
[exploit for this problem]: https://github.com/go-outside-labs/CTFs-Gray-Hacker-and-PenTesting/tree/master/CTFs_and_WarGames/2014-CSAW-CTF/cryptography/crypto-200 [exploit for this problem]: https://github.com/autistic-symposium/sec-pentesting-toolkit/tree/master/CTFs_and_WarGames/2014-CSAW-CTF/cryptography/crypto-200
[scripts from other authors]:https://github.com/go-outside-labs/CTFs-and-Hacking-Scripts-and-Tutorials/tree/master/2014-CSAW-CTF/cryptography/crypto-200/from_the_net [scripts from other authors]:https://github.com/go-outside-labs/CTFs-and-Hacking-Scripts-and-Tutorials/tree/master/2014-CSAW-CTF/cryptography/crypto-200/from_the_net
[well-known table of word frequency values]: http://en.wikipedia.org/wiki/Letter_frequency [well-known table of word frequency values]: http://en.wikipedia.org/wiki/Letter_frequency
[telnetlib]: https://docs.python.org/2/library/telnetlib.html [telnetlib]: https://docs.python.org/2/library/telnetlib.html

View File

@ -547,7 +547,6 @@ endobj
[MySQL database dump file]:http://dev.mysql.com/doc/refman/5.0/en/mysqldump-sql-format.html [MySQL database dump file]:http://dev.mysql.com/doc/refman/5.0/en/mysqldump-sql-format.html
[CSAW CTF 2014 Forensic -Obscurity]: https://gist.github.com/Mia-Stein/4574e99fe0f0dbdb56a9
[online hex-decode]: http://ddecode.com/hexdecoder/ [online hex-decode]: http://ddecode.com/hexdecoder/
[which we can just google]: http://phpxref.ftwr.co.uk/wordpress/wp-content/themes/twentythirteen/js/html5.js.source.html [which we can just google]: http://phpxref.ftwr.co.uk/wordpress/wp-content/themes/twentythirteen/js/html5.js.source.html
[Tailing]: http://en.wikipedia.org/wiki/Tail_(Unix) [Tailing]: http://en.wikipedia.org/wiki/Tail_(Unix)

View File

@ -9,11 +9,10 @@ The problems are very straightforward and very similar to those from the last [C
[Cryptol]: http://www.cryptol.net/ [Cryptol]: http://www.cryptol.net/
[Continuing to talk about]: http://https://singularity-sh.vercel.app/smashing-the-stack-for-fun-or-wargames-narnia-0-4.html
[Wargames]: http://overthewire.org/wargames/ [Wargames]: http://overthewire.org/wargames/
[Krypton]: http://overthewire.org/wargames/krypton/ [Krypton]: http://overthewire.org/wargames/krypton/
[CSAW CTF]: https://ctf.isis.poly.edu/ [CSAW CTF]: https://ctf.isis.poly.edu/
[see my post here]: http://https://singularity-sh.vercel.app/csaw-ctf-2014-cryptography-200.html
## Level 0: Base64 Transformation ## Level 0: Base64 Transformation

View File

@ -60,8 +60,8 @@ If you think about it, a Stack is a perfect object for a process: the process ca
[Python & Algorithms]: https://github.com/go-outside-labs/Python-and-Algorithms-and-Data-Structures/blob/master/book/book_second_edition.pdf [Python & Algorithms]: https://github.com/autistic-symposium/master-algorithms-pyblob/master/book/book_second_edition.pdf
[here are some examples]: https://github.com/go-outside-labs/Python-and-Algorithms-and-Data-Structures/tree/master/src/abstract_structures/Stacks [here are some examples]: https://github.com/autistic-symposium/master-algorithms-pytree/master/src/abstract_structures/Stacks

View File

@ -1429,4 +1429,4 @@ That's it. The [source code is available] as usual.
Hack all the things! Hack all the things!
[source code is available]: https://github.com/go-outside-labs/CTFs-Gray-Hacker-and-PenTesting/tree/master/Web_Exploits [source code is available]: https://github.com/autistic-symposium/sec-pentesting-toolkit/tree/master/Web_Exploits

View File

@ -40,7 +40,7 @@ The basic unit in network communication is the *packet*. So let's create one!
Scapy builds packets by the *layers* and then by the *fields* in each layer. Each layer is nested inside the parent layer, represented by the **<** and **>** brackets. Scapy builds packets by the *layers* and then by the *fields* in each layer. Each layer is nested inside the parent layer, represented by the **<** and **>** brackets.
Let's start by specifying the packet's source IP and then its destination IP. This type of information goes in the **IP header**, which is a *layer 3 protocol* in the [0SI model](http://https://singularity-sh.vercel.app/wiresharking-for-fun-or-profit.html): Let's start by specifying the packet's source IP and then its destination IP. This type of information goes in the **IP header**, which is a *layer 3 protocol* in the 0SI model.
```python ```python
>>> ip = IP(src="192.168.1.114") >>> ip = IP(src="192.168.1.114")

View File

@ -2,7 +2,7 @@
When it comes to the reconnaissance of some target network, the start point is undoubtedly on host discovering. This task might come together with the ability to sniff and parse the packets flying in the network. When it comes to the reconnaissance of some target network, the start point is undoubtedly on host discovering. This task might come together with the ability to sniff and parse the packets flying in the network.
A few weeks ago, I talked about [how to use Wireshark](http://https://singularity-sh.vercel.app/wiresharking-for-fun-or-profit.html) for packet sniffing, but what if you don't have Wireshark available to monitor a network traffic? What if you don't have Wireshark available to monitor a network traffic?
Again, Python comes with several solutions and today I'm going through the steps to build a **UDP Host discovery tool**. First, we are going to see how we deal with [raw sockets](http://en.wikipedia.org/wiki/Raw_socket) to write a simple sniffer, which is able to view and decode network packets. Then we are going to multithread this process within a subnet, which will result in our scanner. Again, Python comes with several solutions and today I'm going through the steps to build a **UDP Host discovery tool**. First, we are going to see how we deal with [raw sockets](http://en.wikipedia.org/wiki/Raw_socket) to write a simple sniffer, which is able to view and decode network packets. Then we are going to multithread this process within a subnet, which will result in our scanner.
@ -15,7 +15,7 @@ The cool thing about using **UDP datagrams** is that, differently from TCP, they
## Writing a Packet Sniffing ## Writing a Packet Sniffing
We start with a very simple task: with Python's [socket](http://https://singularity-sh.vercel.app/black-hat-python-networking-the-socket-module.html) library, we will write a very simple packet sniffer. We start with a very simple task: with Python's socket library, we will write a very simple packet sniffer.
In this sniffer we create a raw socket and then we bind it to the public interface. The interface should be in **promiscuous mode**, which means that every packet that the network card sees are captured, even those that are not destined to the host. In this sniffer we create a raw socket and then we bind it to the public interface. The interface should be in **promiscuous mode**, which means that every packet that the network card sees are captured, even those that are not destined to the host.

View File

@ -38,7 +38,7 @@ The basic unit in a network communication is the *packet*. So let's create one
Scapy builds packets by the *layers* and then by the *fields* in each layer. Each layer is nested inside the parent layer, represented by the **<** and **>** brackets. Scapy builds packets by the *layers* and then by the *fields* in each layer. Each layer is nested inside the parent layer, represented by the **<** and **>** brackets.
Let's start by specifying the packet's source IP and then its destination IP. This type of information goes in the **IP header**, which is a *layer 3 protocol* in the [0SI model](http://https://singularity-sh.vercel.app/wiresharking-for-fun-or-profit.html): Let's start by specifying the packet's source IP and then its destination IP. This type of information goes in the **IP header**, which is a *layer 3 protocol* in the 0SI model.
```python ```python
>>> ip = IP(src="192.168.1.114") >>> ip = IP(src="192.168.1.114")

View File

@ -62,8 +62,8 @@ If you think about it, a Stack is the perfect object for a process: the process
[Python & Algorithms]: https://github.com/go-outside-labs/Python-and-Algorithms-and-Data-Structures/blob/master/book/book_second_edition.pdf [Python & Algorithms]: https://github.com/autistic-symposium/master-algorithms-pyblob/master/book/book_second_edition.pdf
[here are some examples]: https://github.com/go-outside-labs/Python-and-Algorithms-and-Data-Structures/tree/master/src/abstract_structures/Stacks [here are some examples]: https://github.com/autistic-symposium/master-algorithms-pytree/master/src/abstract_structures/Stacks