For now, e-mail me at email@example.com for servers. Currently accepting Bitcoin and PayPal.
The attack is detected by using real-time analytics from the netflow of the routers which analyze 1/2000 of the traffic. The vacuum checks the report and compares it's characteristics to a DDoS attack. If the algorithm matches, mitigation automatically starts. It's measured in Packets Per Seconds (PPS), and includes several protocols like DNS, ICMP, IP fragmentation - Null and Private, TCP Null - RST - SYN - ACK, UDP.
The vacuuming is used to channel the DDoS load with a 15Tbit/s network. The vacuum is sent across 10 different datacenters, and they all abosrb the traffic at a capacity of 4Tbit/s.
Wide range of networking skills alongside various frameworks for virtualization and containers. We provide VPN, Proxies, Socks, basically anything requested.
With knowledge in a multitude of programming languages, we are able to tailor the experience for the end-user.
Constantly learning and implementing continuous integration, and putting new environments and tools into production while keeping all information secure. From deployment with ansible, to CI/CD pipelines implemented for team projects, it provides us the feature rich environments we want and deserve.
Secure Shell, or SSH, is used to create a secure channel between a local and remote computer. While SSH is commonly used for secure terminal access and file transfers, it can also be used to create a secure tunnel between computers for forwarding other network connections that are not normally encrypted. SSH tunnels are also useful for allowing outside access to internal network resources.
For security reasons, sometimes you need to jump through hoops in order to connect to a server in SSH, and from that server SSH to another server. We do this with multiple hops.
1. Connect the local machine to host1
ssh -L38080:localhost:38080 awknode@host1
2. Connect to host2 from host1
ssh -L38080:localhost:38080 awknode@host2
3. Connect to host3 from host2
ssh -L38080:localhost:8080 awknode@host3
Now if everything went as expected you should be able to see your /lol/ folder by firing up a browser and entering the target remote URL as a localhost URL with the 38080 port, for example: http://localhost:38080/lol
Flags: -t flag to chain commands // -v for verbose
ssh -v -L38080:localhost:38080 awknode@host1 -t ssh -v -L38080:localhost:38080 awknode@host2 -t ssh -v -L38080:localhost:8080 awknode@host3
The best choice for securing yourself on IRC as an end-point IP is with an IRC bouncer called a ZNC.
We use the ZNC to keep the content (chats) available to us with a buffer from the server that you can attach/detatch from.
Instead of connecting to 6667 or +6697 (ssl), you'd choose a port that you created from the ZNC installation, and it goes as follows:
Download the latest source tarball.
tar -xzvf znc-1.7.5.tar.gz
(use --prefix="$HOME/.local" (cmake -DCMAKE_INSTALL_PREFIX="$HOME/.local") if you don't want a system wide installation or simply don't have root access; use --with-openssl=/path/to/openssl (cmake -DOPENSSL_ROOT_DIR=/path/to/openssl) if you have a non-standard SSL path)
(use --help to see other configure options)
(if you are on a dedicated server and your CPU has more than one core, you can use make -jX where X is the number of CPU cores to speed up compilation)
Now you want to configure the ZNC server (make sure you answer all the prompts) with:
Then you're all setup! From here, you'll connect to your ZNC from your favorite IRC client with:
/server znc.server.here:+sslport user:password
Once connected, type:
/znc addnetwork awknode
Check your *status window and paste the information about the SSL fingerprint into the input text field for IRC and hit enter.
/znc jumpnetwork awknode
/znc addserver irc.awknode.com +6697
More coming soon.Services