Anonymous ID: b6cbab July 23, 2021, 7:41 a.m. No.14181873   🗄️.is 🔗kun   >>1901

>>14181808

>https://www.thegatewaypundit.com/2021/07/cyber-expert-code-monkey-z-posts-explosive-background-information-mike-lindells-upcoming-cybersecurity-election-data/

 

codefag here. Been thinking about this. Specifically #10+. A few years back we had to refactor code due to the extremely dangerous TLS Heartbleed vulnerability. Like CM says, it's not hard to implement, but it had to be phased in in order to not cut off other systems that were connected/using ours. Judging from the fact that the Dominion software was on multiple servers, all connecting up, and the state their antivirus was in, you can be sure that they were not applying any security updates. Many updates can disable systems comms, and so lazy admins may not apply them regularly.

 

IMO, Heartbleed or Cloudbleed would give an attacker what they would have needed to read packets.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2014-0160

https://nvd.nist.gov/vuln/detail/CVE-2014-0160

Anonymous ID: b6cbab July 23, 2021, 7:49 a.m. No.14181934   🗄️.is 🔗kun

>>14181901

Go big!

TLS+ Heartbleed was a bad one because it affected nearly everyone using HTTPS/SSL. Top priority. Wiki actually has some pretty good info on it.

https://en.wikipedia.org/wiki/Transport_Layer_Security#Attacks_against_TLS/SSL