You are viewing a single thread.
View all comments
130 points

*bad Devs

Always look on the official repository. Not just to see if it exists, but also to make sure it isn’t a fake/malicious one

permalink
report
reply
94 points
*

*bad Devs

Or devs who don’t give a shit. Most places have a lot of people who don’t give a shit because the company does not give a shit about them either.

permalink
report
parent
reply
40 points

What’s the diff between a bad dev and a dev that doesn’t care? Either way, whether ist lack of skill or care, a bad dev is a bad dev at the end of the day.

permalink
report
parent
reply
29 points

I can be good at a trade, but if I’m working for a shit company with shit pay and shit treatment, they’re not going to get my best work.

You get out what you put in, that’s something employers don’t realise.

permalink
report
parent
reply
17 points

The difference is whether the fault for the leak of your personal data rests with the worker who was incompetent, or the employer who didn’t pay for proper secure software.

permalink
report
parent
reply
26 points

You’d be surprised how well someone who wants to can camouflage their package to look legit.

permalink
report
parent
reply
7 points

True. You can’t always be 100% sure. But a quick check for download counts/version count can help. And while searching for it in the repo, you can see other similarly named packages and prevent getting hit by a typo squatter.

Despite, it’s not just for security. What if the package you’re installing has a big banner in the readme that says “Deprecated and full of security issues”? It’s not a bad package per say, but still something you need to know

permalink
report
parent
reply
6 points
2 points

Yeah, I’m confused on what the intent of the comment was. Apart from a code review, I don’t understand how someone would be able to tell that a package is fake. Unless they are grabbing it from a. Place with reviews/comments to warn them off.

permalink
report
parent
reply
1 point

the first most obvious sign is multiple indentical packages, appearing to be the same thing, with weird stats and figures.

And possibly weird sizes. Usually people don’t try hard on package managing software, unless it’s an OS for some reason.

permalink
report
parent
reply
1 point
*

we just experienced this with LZMA on debian according to recent reports. 2 years of either manufactured dev history, or one very, very weird episode.

permalink
report
parent
reply
1 point

That’s what my ex wife used to say

permalink
report
parent
reply
17 points

The official repositories often have no useful oversight either. At least once a year, you’ll hear about a malicious package in npm or PyPI getting widespread enough to cause real havoc. Typosquatting runs rampant, and formerly reputable packages end up in the hands of scammers when their original devs try to find someone to hand them over to.

permalink
report
parent
reply

Technology

!technology@lemmy.world

Create post

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


Community stats

  • 18K

    Monthly active users

  • 11K

    Posts

  • 518K

    Comments