In 1986, Congress passed the Computer Fraud and Abuse Act (CFAA), now codified under Title 18 U.S. Code § 1030. This law makes it a federal crime to gain unauthorized access to “protected” computers (otherwise known as “hacking”) with the intent to defraud or do damage.

No everyone lives in the USA @@robhill8894

@@robhill8894and?

​@robhill8894 it's a good thing criminals care about laws, tho😊

@@robhill8894there are many things that are illegal that are still done. Most of the crime is committed by your very own government. So why not be a step or two ahead of them?

Very handy in case of a randomware attack ;)

@@krem2335woosh

what do you do?

I’d look into emissions security if u can’t detect covert comms using emissions then u mind as well not even try

Seems like just yesterday I was watching hak5 on tech TV.

@@atheistmecca971 That's right I totally forgot about that!

In 1986, Congress passed the Computer Fraud and Abuse Act (CFAA), now codified under Title 18 U.S. Code § 1030. This law makes it a federal crime to gain unauthorized access to “protected” computers (otherwise known as “hacking”) with the intent to defraud or do damage.

No way you can keep up 100%, tech and info is changing every day so fast.

I remember a particular wifi at a Starbucks. Good times.

You can make ALL of these tools yourself and you’ll gain A TON of knowledge doing it.

An easy way to think of it is that a Pineapple can pretend to be a real Wi-Fi, tricking devices and launching attacks. A Flipper can only really scout out networks and disrupt them. Although it can create networks, any user that joins won't be able to access the internet as it's just not built for that. Both are great tools in their own respect, but it's like comparing a swiss army knife to a machete.

As a lifelong 007 fan, I am quite honored to receive this comment. Thank you :)

I have to second this. 100% agree with putting food on the table but I miss when you were teaching 10 year old me how to hack and crack for free at home in safe and legal ways

Soon... 😉

Yeah, there are other attacks like Thunderspy which won't be blocked by such software. Physical access is all it needs.

If you think Crowdstrike will protect you, you're a sucker.

So what happens when a USB device lies about what it is? - not sure what it is currently. But 15 years ago, almost every business used the same dell keyboard. I always considered it insecure and a bit strange.

​@@pragmaticperson7127Their repetitive misuse of literally says it all.

@@goat-eyeslol. fax.(kidding)

Good morning, Most likely it's a relativ robbing you... Change all your password a activate 2FA on Facebook

Why wouldn't they be? Your property is your property. No one can tell you what to do or not to do with your property.

@@ethanrandall3005 Sorry, I should’ve said safe not okay.

In 1986, Congress passed the Computer Fraud and Abuse Act (CFAA), now codified under Title 18 U.S. Code § 1030. This law makes it a federal crime to gain unauthorized access to “protected” computers (otherwise known as “hacking”) with the intent to defraud or do damage.

Till the 🐄🐄🐄come home

Yeah, I'm never buying cheap charging cables again

Bro your joking💀

Snooping on HTTP is only one of the myriad of attack vectors. Personally, I find captive portals to be highly effective at collecting credentials and other PII - especially with realistic looking phishing pages. Many operating systems don't even show the URL of the portal, so it only has to "look the part". Then there's DNS spoofing as part of a greater phishing campaign, DoS attacks, WPA handshake captures for password cracking -- especially when coupled with deauthentication attacks, denial of certain protocols (what do most folks do when the VPN "just won't connect"). Both pineapples can be used for enterprise-WPA evil twin attacks. The Enterprise makes a great platform for lateral movement within a network when coupled with C2. Of course testing access points/base stations for vulnerabilities & misconfigurations (e.g. WPS) is a must, and one place it shines where other tools fail to check is testing clients/stations for misconfigurations (e.g. PNL leakage / susceptibility to rogue access points in general). TLS and HSTS are great - but I wouldn't just blindly trust this best-effort protocol.