Live data from Hacker News

Non-official site with a tampered version of KeePass

security.infoteam.ch

41–50 of 82 posts

Re: Non-official site with a tampered version of KeePass

#41
post #15

What are some safety measures you take when downloading a new version of keepass? Checking the digital signature of the binary? Original keepass downloads are hosted on sourceforge which has not had the best history of integrity the way I see it.

All keepass executable downloads have valid digital signatures and are signed by the developer.

Re: Non-official site with a tampered version of KeePass

#42
post #34
post #27

Earlier quoted context omitted.

I agree, that's why signed source code releases are the safest thing you can get. Keepass has signed releases (including the source code archive) that can be checked with OpenPGP. https://keepass.info/integrity.html

If you trust the signed source code there's no reason you shouldn't trust the signed binary - unless you have sufficient time and expertise to audit the source.

This is how I view it:

* Being open source protects against a malicious developer. Otherwise there is nothing preventing him to build the binary with a different source, and send the passwords to his own server.

* Signed code archive prevents against a compromised hosting site.

Re: Non-official site with a tampered version of KeePass

#43
post #20
post #14

Hah, the Linux version points you to the original website (only the Mac and Windows versions appear to be modified)! The year of the Linux desktop is truly here.

doesnt that just imply that these scammers thought the linux userbase to be too small to be worthwhile? the comparatively small userbase is actually an underappreciated security feature of linux ;)

Isn’t that the infamous “security by obscurity”?

Re: Non-official site with a tampered version of KeePass

#44
post #40

Earlier quoted context omitted.

This. And the benefit is it's easy to add your own fixes to your local version too. Stuff like removing the PerformSelfTest() call, adding items to the ListView in batch, item bounds checking when refreshing the ListView, etc. can quite noticeably speed up the UI, and random window focusing/sizing issues aren't too hard to fix either.

You might also consider submitting such changes as a patch to Dominic, the developer.

In a perfect world I would love to, but every time I've tried to submit improvements to open-source software I've come out extremely frustrated with how many hoops I have to jump through just to get my code properly considered, let alone merged. Half the time the developers are extremely resistant to changes and believe the change is wrong/unnecessary, or the current state is already correct, or that the changes are too big and/or not worth it, or that their upstream code is responsible, etc., and the other half the time they're admittedly quite welcoming but present hoops that on my end I simply don't feel like jumping through (like putting more personal info on the internet than I care to), especially when I'm already going out of my way to help people. Maybe you'd think the problem is with me, or maybe Dominic would be an exception in all regards, but wherever the problem is, I've grown very reluctant about the idea in general, so I just fix bugs on my own computer and let someone else who cares & has the time/energy to put up a real fight fix the issues for everyone else.

Re: Non-official site with a tampered version of KeePass

#45
post #3

I've reported the website here: https://safebrowsing.google.com/safebrowsing/report_phish/?t... Hopefull it will be blocked by the browsers using the safe browsing list.

safebrowsing is useless. We've reported scams of VLC shipping malware for years. They are still there.

Re: Non-official site with a tampered version of KeePass

#46
post #20
post #14

Hah, the Linux version points you to the original website (only the Mac and Windows versions appear to be modified)! The year of the Linux desktop is truly here.

doesnt that just imply that these scammers thought the linux userbase to be too small to be worthwhile? the comparatively small userbase is actually an underappreciated security feature of linux ;)

No, I meant a tongue-in-cheek statement that Linux is the only worthwhile desktop because it's not affected :P

Re: Non-official site with a tampered version of KeePass

#47
post #45
post #3

I've reported the website here: https://safebrowsing.google.com/safebrowsing/report_phish/?t... Hopefull it will be blocked by the browsers using the safe browsing list.

safebrowsing is useless. We've reported scams of VLC shipping malware for years. They are still there.

FWIW, report the domains to https://someonewhocares.org/ , as he keeps updating it, and it is used by e.g. PiHole and my own hostfile generator.

Re: Non-official site with a tampered version of KeePass

#48

Pretty ironicly, Terms of use warn to be very careful when downloading files with an exe.,. Vbs,. Lnk,. Bat,. Sys, or a suffix com., Because these files may contain a virus or spyware !

Not ironic: totally intentional marketing trick. It makes you more inclined to trust the provider of the warning. They seem knowledgable about something important, and they're sharing that information with you. More insidiously, it makes you less likely to apply the warning to them. Because (unconsciously you think this) why would someone warn you about a trick they themselves are trying to pull?

Re: Non-official site with a tampered version of KeePass

#49
post #40

Earlier quoted context omitted.

You might also consider submitting such changes as a patch to Dominic, the developer.

In a perfect world I would love to, but every time I've tried to submit improvements to open-source software I've come out extremely frustrated with how many hoops I have to jump through just to get my code properly considered, let alone merged. Half the time the developers are extremely resistant to changes and believe the change is wrong/unnecessary, or the current state is already correct, or that the changes are…

> their upstream code is responsible

Then you're not going to the good people. Stop going through intermediaries, go straight for the source (package specific issues on Ubuntu must be reported to Ubuntu -like python not recognizing a new module-, but bad code inside the package must be dealt with with upstream).

> Half the time the developers are extremely resistant to changes and believe the change is wrong/unnecessary, or the current state is already correct, or that the changes are too big and/or not worth it, [...]

That's why I take the habit of jumping on IRC first, talking with devs a bit and trying to understand why I find a specific piece of code problematic.

I was trying to add support for i686 on an AUR package I maintain; quickly dismissed "we don't support i686 anymore anyway, just slap comments in your PKGBUILD and ship it".

I was working with the btrfs(8) util, which has the most horrific interface ever designed; "OK, we're not hostile to a new interface design, but you'll have to provide a comprehensive explanation of what you want and how it should behave".

And finally, documentation usually gets merged real fast (recently on cbsd(8) and nextcloud).[0][1]

[0] https://github.com/nextcloud/documentation/pull/826

[1] https://github.com/cbsd/cbsd-wwwdoc/pull/12

Post reply on HN