- Open Discord
- Click + → Create Server
- Name it
Done.
| rm ~/.git-credentials | |
| gh auth logout | |
| git config --global --unset-all credential.https://github.com.helper | |
| git config --global --unset-all credential.https://gist.github.com.helper | |
| git config --list --show-origin | grep credential | |
| [ble: exit 1] | |
| # save new | |
| git config --global credential.helper store |
Cron jobs are the Unix way of telling your computer: “At this time, do that thing, relentlessly, forever.” Think of it as a tiny, tireless scheduler living in your system’s basement, checking its watch every minute ⏱️.
Here’s the clean, practical path.
First, open your crontab (cron table) for editing:
crontab -ehttps://cloud.oracle.com/compute/instances then vnc -> security -> default -> security rules -> add ingress rule
sudo echo "-A INPUT -p tcp -m state --state NEW -m tcp --dport <your_port> -j ACCEPT" >> /etc/iptables/rules.v4
sudo iptables-restore < /etc/iptables/rules.v4Yes—this is very doable, and it’s one of those “small automation, big leverage” moves that makes repos feel alive instead of archival. 🚀 In practice, you’re talking about a GitHub Actions workflow that:
main.That loop is fully supported, no hacks required.
| api_key="" | |
| ## reverse ip lookup | |
| curl -X GET "https://api.shodan.io/dns/reverse?ips=8.8.8.8,1.1.1.1&key=$api_key" | |
| ## search | |
| curl -X GET https://api.shodan.io/shodan/host/search?key=$api_key&query='http.title:"Grafana" -org:"YourCompany"' |
| #!/bin/bash | |
| sudo -s | |
| docker pull ubuntu:22.04 | |
| docker run -it \ | |
| --name hackbox-build \ | |
| ubuntu:22.04 \ | |
| /bin/bash |
| sudo apt install -y \ | |
| libuv1-dev \ | |
| libjson-c-dev \ | |
| libwebsockets-dev \ | |
| zlib1g-dev | |
| git clone https://github.com/tsl0922/ttyd.git --depth=1 | |
| cd ttyd && mkdir build && cd build | |
| cmake .. | |
| make && sudo make install |