Hacking Articles Tips Tricks Videos Tutorials
468 subscribers
65.8K photos
15 videos
157 files
132K links
Exploit
Pentesting
Hacking
Red Team
Blue Team
Kali Linux
Bug Bounty
Black Hat
Cyber security etc

@Hacking_Video
@Hacking_attack
Download Telegram
intigriti Challenge 0722 by Vroemy

Another awesome XSS challenge from Intigriti. Personally, I learn a lot trying to solve these monthly challenges by Intigriti. The…Continue reading on Medium »
Read more...
hacking: security in practice
What are some ways you protect your own system?

It's something I never really thought about, a friend of mine had some idiot in a game get his IP address and although my knowledge might be dated, the only thing I can only think of in terms of attacking an "IP" is to DDOS with some IP stresser....the only other group I can think of is a government agency that can subpoena your ISP.

In terms of regular folks, what can they do? For instance, would they scan the IP for open ports? I just did it for mine and noticed two ports (in the 50,000+ range) open, is that bad? What do you use to scan your own system? What do you use to protect yourself? Do you also disable UPnP? etc?

submitted by /u/razzrazz-
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video
Hacking Articles Tips Tricks Videos Tutorials
Photo
KitPloit - PenTest Tools!
PR-DNSd - Passive-Recursive DNS Daemon

https://blogger.googleusercontent.com/img/a/AVvXsEhczPfUXK-C9SGRwVyjCaV2wOMhQYaatAO36meWvK3QDnqy5Vje9lezAHa3bcmNIaoHz7Jwfyr2bh2PKLfhAijuRFWS_Al5yDMFFuaI4YahJqdymQYDakYTZHhlSK_gJ0jOcRxb5_g2gZj8Jbgk38LdnBrQ2evpYkph4PSJQ7XQXLG_skUJ1KTJP3kU=w640-h360

Passive-Recursive DNS daemon.
Quickstart

nameserver 127.0.0.1 | sudo tee /etc/resolv.conf dig google.com dig -x $(dig +short google.com)">go get github.com/korc/PR-DNSd
sudo setcap cap_net_bind_service,cap_sys_chroot=ep go/bin/PR-DNSd
go/bin/PR-DNSd -upstream 9.9.9.9:53 -listen 127.0.0.1:53
echo nameserver 127.0.0.1 | sudo tee /etc/resolv.conf
dig google.com
dig -x $(dig +short google.com)


If you can't use setcap, you have to use -chroot ""and -listen :options, or run as root.

Use cases

* run as local host DNS service, to fix your netstat/tcpview/lsof etc. output
* as enterprise-internal DNS server, to also be able to do meaningful EDR/IR and log analysis
* as cloud service, to also collect Passive DNS data from non-enterprise (home, BYOD etc.) devices
* hint: you probably want to configure DDoS protection options

* in cloud as DNS-over-TLS server, to additionally provide private DNS for supporting devices (ex: Android 9's private DNS setting)
* ex: domain pattern based firewall/proxy configuration for mobile devices
Running as your own private server for Android9's Private DNS settings

After appropriate setcap, run:

PR-DNSd -tlslisten :853 -cert YOUR_SERVER_CRT_KEY_PEM -upstream 1.1.1.1:53 -store pr-dnsd

Options

-cert string
TCP-TLS listener certificate (required for tls listener)
-chroot string
chroot to directory after start (default "/var/tmp")
-count int
Count of replies allowed before debounce delay is applied (default 100)
-ctmout string
Client timeout for upstream queries
-debounce string
Required time duration between UDP replies to single IP to prevent DoS (default "200ms")
-key string
TCP-TLS certificate key (default same as -cert value)
-listen string
listen address (default ":53")
-silent
Don't report normal data
-store string
Store PTR data to specified file
-tlslisten string
TCP-TLS listener address (default ":853")
-upstream string
upstream DNS serv er (tcp-tls:// prefix for DoT) (default "1.1.1.1:53")
(with tls and chroot, ensure ca-certificates and resolv.conf in chroot are properly set up)

Download PR-DNSd

___________________________
@hacking_Attack
@Hacking_Video