dwightgunning

Joined 16 years ago

Karma
548
Submissions
218
Member since
Dec 28
Australian software engineer, currently based in The Netherlands.

www.dwightgunning.com

View on Hacker News

Recent submissions

Comment · 3 months ago
Perhaps a happy accident.
Comment · 11 months ago
That's not a tax, that's the expense ratio, which is basically describing fees captured by the fund manager. Funds accessible to Dutch investors involve similar ERs. It's not an alternative.
Comment · 1 year ago
Proud to have helped work on this. Happy to field any questions.
Comment · 2 years ago
Is there a robust Syncthing app for iOS? Last time I checked there was only an affiliate project and their story wasn't convincing.
Comment · 2 years ago
Comment · 2 years ago
Comment · 3 years ago
The Sound Map of Amsterdam shows the (calculated) noise load for the most important traffic sources in the city.
Comment · 3 years ago
Comment · 3 years ago
They don’t have access to the ssh private key. They have access to the encrypted password file (and presumably not the password used to encrypt it).

The attack works when the user doesn’t realize they’re sending their SHH private key through the password form of malicious-site.com.

Something like accidentally putting your Google password into the Dropbox login form. Dropbox have now seen your Google password.

Comment · 3 years ago
Seems logical to move smaller sums more frequently.
Comment · 3 years ago
So many ads I can’t even get to the obituary.
Comment · 3 years ago
For a long while I've trusted and used various KeePass ports/forks on my phone and laptops and stored the password file in cloud storage.

With the recent LastPass exposure, the supply-chain attack on PyTorch, needing to be vigilent and avoid granting apps access to my cloud drive, I've actually just been reviewing my setup and workflow.

Here's what I'm planning to change...

Phone: Switching from MiniKeePass to KeePassium. I've found it's not too difficult to build KeePassium from source and install without needing an Apple Developer subscription. This means I can properly audit the code and control/verify all updates.

Laptops: Start building KeePassXC from source. In the short term, I'll be more diligent in obtaining updated versions from trusted sources and using PGP to verify the package.

File sync: Start storing the password file on a self-hosted file server. Having recently setup Tailscale on all my devices, it's now convenient to manage Samba and remove cloud storage from the system. In case the SMB share is inaccessible, I'll fallback to the backups kept by KeePassium and use cron+rsync to maintain an secondary copy on my laptop.

Backups: I'm planning to periodically backup to a hardware keypad encrypted USB drive. In comparison to a regular USB / external drive, the hardware encryption makes it harder for somebody to quickly make a copy of the password file and take it away to be brute-forced.

Would welcome any pointers on things I may not be considering or suggestions for improvement!

Comment · 3 years ago
Comment · 3 years ago
> This coffee is still good. It was roasted in June and July 2022 with a one year best buy date.

Still good but hardly fresh for a specialty.

Anyway. There’s a 6x number in here that somebody (or somebodies) completely missed…

Seems like what they thought was a fair-to-good deal was actually a such a terrible deal that, given their incorrect definition of a unit, the numbers in their model lined up.

That might be something the consultant could have spotted, since they’d seen the numbers around previous deals. I’m not sure it’s their duty/obligation to.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton