internetrelaychat/IRCP
internetrelaychat/IRCP
1
Fork 0
mirror of git://git.acid.vegas/IRCP.git synced 2024-11-26 01:46:39 +00:00
Code Issues Activity

Updated README

Browse Source
This commit is contained in:
Dionysus 2023-05-31 21:05:09 -04:00
parent e670bce212
commit 3b90515ded
Signed by: acidvegas
GPG Key ID: EF4B922DB85DC9DE
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -56,9 +56,9 @@ The IRC networks we scanned are PUBLIC networks...any person can freely connect
![](.screens/preview.png) ![](.screens/preview.png)
## Threat Scope ## Threat Scope
While IRC is an unfavored chat protocol as of 2023 *(roughly 7,000 networks)*, it still has a beating heart **(over 3000,000 users & channels)* with potential for user growth & active development being done on [IRCv3](https://ircv3.net/) protocol implementations. While IRC is an generally unfavored chat protocol as of 2023 *(roughly 7,000 networks)*, it still has a beating heart **(over 300,000 users & channels)* with potential for user growth & active development being done on [IRCv3](https://ircv3.net/) protocol implementations.
Point is..IRC is not going anywhere. With that being said, every network being on the same port leads way for a lot of potential threats: Point is..it's is not going anywhere. With that being said, every network being on the same port leads way for a lot of potential threats:
* A new RCE is found for a very common IRC bot * A new RCE is found for a very common IRC bot
* A new 0day is found for a certain IRCd version * A new 0day is found for a certain IRCd version
@ -66,10 +66,10 @@ Point is..IRC is not going anywhere. With that being said, every network being o
* Tracing users network/channel whereabouts * Tracing users network/channel whereabouts
* Mass spamming attacks on every network * Mass spamming attacks on every network
![](.screens/base.png)
Mass scanning *default* ports of services is nothing new & though port 6667 is not a common target, running an IRCd on a **non-standard** port should be the **standard**. If we have learned anything in the last 10 years, using standard ports for *anything* is almost always smells like a bad idea. Mass scanning *default* ports of services is nothing new & though port 6667 is not a common target, running an IRCd on a **non-standard** port should be the **standard**. If we have learned anything in the last 10 years, using standard ports for *anything* is almost always smells like a bad idea.
![](.screens/base.png)
## Todo ## Todo
* Built in identd * Built in identd
* Checking for IPv6 availability *(SSL= in 005 responses may help verify IPv6)* * Checking for IPv6 availability *(SSL= in 005 responses may help verify IPv6)*