Skip to content

Comment on Security vulnerability in MySQL ubuntuparent

Comments

With this logic, let's not secure any software that you cannot connect to it directly.

Before we forked LedgerSMB, the SQL-Ledger author's attitude was that unless you can exploit the software without logging in it doesn't count. It's only accounting software anyway so why would anyone want to break in? Not only that but timestamps were perfectly acceptable as session id's and they didn't even have to be stored on the server, just checked to see if they were recent.

Thus began years of efforts on our part of security fixes, which I would not have started except that I had customers to support.

What "logic" is this? Where are people getting the idea that I'm instructing them not to patch MySQL?

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.