- https://keepass.info/ is the official site, which ironically uses a suspicious-looking .info top-level domain, but is in fact the legitimate source
- https://keepass.com/ is an unofficial site which the Twitter article is reporting as spreading malware, but has somehow obtained the more legitimate-sounding .com top-level domain
And by the way, both of these sites come up on the first page of a Google search for "KeePass".
We then spent 3 hours getting approvals for me to get my own laptop on their internal network so I could use ssh from my Macbook. I felt bad because my company charges like $300/hr for our consulting services, so we wasted nearly $1000 because the main Putty download site seemed too suspicious for the client to be comfortable with.
I know Putty is legitimate and I know it's a free product, but appearances do matter. Presentation does matter. Although I do blame Microsoft a bit for not shipping an SSH client for so long.
- Google Safe Browsing
- Pihole including a couple of regularly updated malware lists
- uBlock Origin
It looks like Safe Browsing and pihole do not yet have this on the blacklist.
Kinda surprised the badware list only contains 100 or so URL's!
Maybe developers are getting used to the `getQwerpy.io` convention, but I don't see it catching on more broadly.
I get it open source, hard to keep the lights on, etc etc but I feel like if you take the steps of getting into a such a security heavy space, then you have to be able to keep up your end of the bargain.
In this case it might not mean registering every variation of keepass (keepass.com probably useful though) but it certainly means working aggressively with search engines to get things flagged, send push notifications to your users warning them of it, etc etc
Could have taken the source, added the backup to 3rd party server, and released binaries.
Why, if you don't earn enough money?
better to shut down a project and walk-away for example, then leave it up, never update it, have a vulnerability get exposed, and have everyone using your product get owned
https://news.ycombinator.com/item?id=19311856
At the time the download links on the non-official Keepass.com site seemed to point back to the official sources, but I noted of course that could change in the future, or could even be different depending on who visits the site.
I ended up submitting an objection to the TrueCrypt trademark application to the USPTO, but I'm not sure how much good it will end up doing. I was not able to pay a lawyer the several thousand dollars they wanted to draft the letter themselves.
I have been working on a fork of TrueCrypt/VeraCrypt and wanted to be sure that before releasing the code that I am following all the license terms and giving proper attribution, as TrueCrypt has a somewhat non-standard open source license.
TrueCrypt has an old trademark issued back in 2007 but which expired after 10 years in 2017. As part of the licensing review, I discovered there is a new trademark application filed August 25, 2018 by Julien Clairet under a company named "DATA ACCESS" based in Paris, France.
I discovered [that] "keepass.com" is also apparently registered to Julien / DATA ACCESS.
There is a publication period when new Trademarks are announced and an opportunity to contest the validity of the claim. The new "TrueCrypt" trademark was published on February 20, 2019, and you have 30 days from the time that the mark is published to file any opposition.
I am preparing to file a response to USPTO.
First of all, a huge thank you from everyone that loves TrueCrypt for doing this.
How long will it be before you know if they issued or rejected the trademark? Is there anything else that can be done now that the 30-day deadline has passed? Would you mind posting a link to the trademark application?
http://tsdr.uspto.gov/documentviewer?caseId=sn88092713&docId...
Typically two months after publications they will send the Notice of Allowance. It hasn't happened yet but it could happen any day I suspect.
Though I quickly realized it wasn't such a bad idea at all, for exactly the reasons such as this. Even I mess up domains sometimes, so I usually tend to use Google instead except for the ones I know by heart (or have bookmarked).
https://safebrowsing.google.com/safebrowsing/report_badware/...
* private space missions were financed from the sale of a predatory business (paypal)
* government space missions originated from the cold war arms races (that continue to this day)
* a few diseases are curable, many aren't. pharmaceuticals profit more from treatment than cure, however. Some ailments such as anaphalaxis and diabetes that are mostly treatable have been receding into "uncured/undertreated" territory because phama keeps raising the prices of insulin or epi pens.
* much of hunger, say in Africa, can be easily treated if we could find a way to keep warlords and corrupt gov's from stealing the aid, but our technology isn't helping us very much (not saying we shouldn't keep trying, but tech is of no use for this problem)
* synthetic organs sound great (if you need one). maybe this I concede is a victory for (bio)tech.
* trading money is really just trading information. Once the infrastructure is in place, it's a trivial matter.
deciding who gets to post content online is a much harder problem to solve. If you could make one call to google to have them de-listed from search, every company/political faction would be doing this to thier competitors/rivals.
Issues like this were one of the main reasons I started working on appget. I died a little bit inside every time I saw a friend google an app and click on the first link (usually an ad) or click through the installation wizard as fast as they possibly could and not unchecking the toolbar, bundle, bonus, whatever else.
AppGet solves these issues from a couple of different angles,
1. we only allow packages hosted on the official vendor, maintainer websites.
2. All package manifests are simple YAML files on GitHub where they go through a PR/Review before getting merged.
3. For your _tech normal_ friends or family, they can search for apps in https://appget.net/packages/ and click the install button, and we do the rest. No command line needed. 4. We disable all bundled app installations by default.
For example here is the page for Keepass https://appget.net/packages/i/keepass
A very cost effective way to protect your IP.
Reaffirming my decision for the n-th time to never browse the modern web without adblock.
https://phish.opendns.com/main?url=keepass.com&server=ams16&...
Still not blocked on Google Safe Browsing.