Are there any passkey hardware tokens the private key is effectively irretrievable? That is why up to now FIDO U2F has been my preferred additional factor. The down side is that you have to register multiple tokens for each authentication service in case one is lost or damaged. I miss the days of openid when I could use my own idp with any service, but the walls quickly went up when the big players wanted to control the ecosystem.
Readit Newschaz6 commented on Credentials for Linux: Bringing Passkeys to the Linux Desktop alfioemanuele.io/talks/20... · Posted by u/alfie42
chaz6 commented on Killing the ISP Appliance: An eBPF/XDP Approach to Distributed BNG markgascoyne.co.uk/posts/... · Posted by u/chaz6
Is it the FTTX equivalent of a BRAS?
Yes, exactly. BRAS is functionally the same as BNG.
chaz6 commented on UK consulting on bringing in social media ban for under 16s bbc.com/news/articles/cgm... · Posted by u/1659447091
I think this will be bad for the cybersecurity industry. I cut my teeth by hanging around on IRC networks back in the day. That said, I doubt these will end up being regulated due to their popularity and antiquity.
chaz6 commented on Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss getdock.io/... · Posted by u/yadavrh
Is there any option to self-host in an air-gapped environment?
chaz6 commented on CLI agents make self-hosting on a home server easier and fun fulghum.io/self-hosting... · Posted by u/websku
I would really like some kind of agnostic backup protocol, so I can simply configure my backup endpoint using an environment variable (e.g. `-e BACKUP_ENDPOINT=https://backup.example.com/backup -e BACKUP_IDENTIFIER=xxxxx`), then the application can push a backup on a regular schedule. If I need to restore a backup, I log onto the backup app, select a backup file and generate a one time code which I can enter into the application to retrieve the data. To set up a new application for backups, you would enter a friendly name into the backup application and it would generate a key for use in the application.
If I enter the following:-
<p><p></p>
chaz6 commented on Show HN: Yapi – FOSS terminal API client for power users yapi.run/blog/what-is-yap... · Posted by u/jamiepond
Page currently shows
404 This page could not be found.chaz6 commented on Show HN: Mephisto – A RAM-only, ad-free disposable email PWA built with React mephistomail.site... · Posted by u/benmxrt
That is a valid point. Currently, the backend keeps them in RAM mainly to support multi-device syncing (like the QR handoff feature) during an active session. If a user scans the QR code to open the same inbox on mobile, the backend needs to serve those existing messages to the new client.
However, I'm exploring a 'Transfer & Purge' logic where, once a message is successfully delivered and acknowledged by the primary client, it could be encrypted or removed from the server-side RAM entirely, leaving the responsibility of persistence to the client-side IndexedDB. It’s a delicate balance between UX and the absolute 'zero-trace' goal.
That makes sense, thanks!
It's the people who aggressively slide right over just a few feet in front of me (cutting off nearly all of my safety buffer) without so much as a signal that really drive me nuts.