-
ERROR 418 posted an update 8 years, 6 months ago
Is your router hacked ?
http://www.cyberwar.news/2017-06-26-cia-discovered-to-be-routinely-hacking-home-wi-fi-routers-made-by-linksys-dlink-and-belkin-to-monitor-all-your-internet-traffic.htmlLOL – The AI must not like multiple links, probably thinks it’s spam. I’ll break my post up into a couple of comments…
The Giza Forum (Legacy)
Closed Archive of The Old Forum
…
Consider upgrading your firmware with
https://openwrt.org/ – requires medium to advanced technical skill
http://www.dd-wrt.com/site/index – low to intermediate skill
…or http://www.polarcloud.com/tomato. (Links to other firmwares at the end of this article.)
Besides tighter security (any router newer than 2014 has factory built-in back-doors now standard,) these open source firmwares offer options generally only available on Enterprise class, or top-end routers.
https://www.flashrouters.com/learn/router-basics/benefits-of-open-source-firmware
Linksys is owned by Cisco. I used to work with a technology “partner” (read: exploited subcontractor) of Cisco’s. Heard a few strange things about John Chambers (exec chairman and former CEO) during that time. Watch him on some videos done by Cisco: he is very unsettling
Thank you Cara.
https://wikileaks.org/vault7/
scroll down to Cherry Blossom.
You’re right about Chambers. Isn’t it funny how all the tech (leaders ?) people in high positions are, (what’s the word,) unstable ?
Having worked in the tech sector for about 15 years, I can see why people might become unstable:
– constant, incomplete, shifting projects;
– many “products” not really products but just marketing wrap around “happy” accidents of success;
– no real, substantive communication between “sales”, ” engineering” and “finance”;
– “god” complex of people promoted within the sector as world-changers;
– sense of “special destiny” by many who work in the sector that they are “changing the world”;
– repeated obfuscation of issues possible and frequent because many outside the sector don’t understand it sufficiently;….
and many more
… – unrealistic deadlines, then throwing more programmers at the problem during the construction phase (waterfall);
– PM’s that allow scope creep;
– burnout;
and my favorite – “That’s not a bug, it’s a feature. It can be a bug in the next release cycle”
But yeah, the god-complex (w/ the associated ego clashes) is a big one.
Like you said: ‘and many more’