4 ms·

I suspect this is an internal sabotage from devs not agreeing with it - plaintext is easily observable and people can figure it out, causing a PR damage; encryp

I suspect this is an internal sabotage from devs not agreeing with it - plaintext is easily observable and people can figure it out, causing a PR damage; encrypted passwords are basically untraceable.

orf 2y ago
Meanwhile, in reality, the offshore development firm being paid per line of code from Linksys farmed the work out to juniors who haven’t graduated and couldn’t care less if something is encrypted or not.
- throwawaysleep 2y ago
  Even if they have graduated, why would they care? I log an objection once at work. I've covered my butt. After that point, the outcomes are not my problem. It is less work to do it this way.
  - jagger27 2y ago
    Sure, log your objection between the choice of Tailwind and Bootstrap. In professions more serious than software, people generally use their spines and say "no" when they see problems to the degree of passwords sent in the clear.
autoexec 2y ago
> causing a PR damage The most you can expect from PR damage like this is that maybe an update goes out faster that fixes the problem (or at least hides it better). Nobody is afraid of bad PR. The most hated companies in the US are also massively wealthy and successful. If people refused to by routers from companies that pulled shit like this, nobody could buy a router. You can enter pretty much any major brand of wireless router into google next to words like "hardcoded" "backdoor" and "plaintext" and get results going back decades.
- JumpCrisscross 2y ago
  > most you can expect from PR damage like this is that maybe an update goes out faster Next step is trawling procurement records for public purchasers of their products, and prompting their return.
outworlder 2y ago
> I suspect this is an internal sabotage from devs not agreeing with it No, it's probably devs not even caring about it (or not caring enough to push back on deadlines). It's surprising what people will do if they aren't forced to do the right thing (passwords checked to version control, proprietary code pasted in Stackoverflow) and so on.
patmorgan23 2y ago
Bold of you to assume that the development wasn't farmed out to the cheapest subcontractor in a developing country that doesn't even know how to spell IoT.
- playingalong 2y ago
  That's kind of hate speech. Do you really think people can develop software for a wifi router and cannot spell?
  - claytongulick 2y ago
    > hate speech You must live in an unbelievably beautiful world to consider that comment to be "hate speech". I wonder what term you would use to refer to actual vile racist speech? And how you would differentiate between them when you use the term so freely?
  - Marsymars 2y ago
    I regularly review PRs from developers with English as a first language with various spelling mistakes in variable names, code comments, commit messages, etc. Not Wi-Fi routers, but I don’t see why those developers wouldn’t be able to slowly churn through Jira tickets for a router software.

orf 2y ago

Meanwhile, in reality, the offshore development firm being paid per line of code from Linksys farmed the work out to juniors who haven’t graduated and couldn’t care less if something is encrypted or not.

throwawaysleep 2y ago
Even if they have graduated, why would they care? I log an objection once at work. I've covered my butt. After that point, the outcomes are not my problem. It is less work to do it this way.
- jagger27 2y ago
  Sure, log your objection between the choice of Tailwind and Bootstrap. In professions more serious than software, people generally use their spines and say "no" when they see problems to the degree of passwords sent in the clear.

autoexec 2y ago

> causing a PR damage The most you can expect from PR damage like this is that maybe an update goes out faster that fixes the problem (or at least hides it better). Nobody is afraid of bad PR. The most hated companies in the US are also massively wealthy and successful. If people refused to by routers from companies that pulled shit like this, nobody could buy a router. You can enter pretty much any major brand of wireless router into google next to words like "hardcoded" "backdoor" and "plaintext" and get results going back decades.

JumpCrisscross 2y ago
> most you can expect from PR damage like this is that maybe an update goes out faster Next step is trawling procurement records for public purchasers of their products, and prompting their return.

outworlder 2y ago

> I suspect this is an internal sabotage from devs not agreeing with it No, it's probably devs not even caring about it (or not caring enough to push back on deadlines). It's surprising what people will do if they aren't forced to do the right thing (passwords checked to version control, proprietary code pasted in Stackoverflow) and so on.

patmorgan23 2y ago

Bold of you to assume that the development wasn't farmed out to the cheapest subcontractor in a developing country that doesn't even know how to spell IoT.

playingalong 2y ago
That's kind of hate speech. Do you really think people can develop software for a wifi router and cannot spell?
- claytongulick 2y ago
  > hate speech You must live in an unbelievably beautiful world to consider that comment to be "hate speech". I wonder what term you would use to refer to actual vile racist speech? And how you would differentiate between them when you use the term so freely?
- Marsymars 2y ago
  I regularly review PRs from developers with English as a first language with various spelling mistakes in variable names, code comments, commit messages, etc. Not Wi-Fi routers, but I don’t see why those developers wouldn’t be able to slowly churn through Jira tickets for a router software.