Skip Navigation

maltfield

@ maltfield @monero.town

Posts
131
Comments
48
Joined
3 yr. ago

  • Removed

    BusKill (Open-Source Hardware Dead Man Switch) Announces Bitcoin Black Friday Deal

    Jump

  • [QubesOS] Disarm BusKill Dead Man Switch with Keyboard Shortcut (Guide)

    Jump

  • BusKill Dead Man Switch now available in a brick-and-mortar in Germany 🧱🛡️

    Jump

  • BusKill Dead Man Switch now available in a brick-and-mortar in Germany 🧱🛡️

    Jump

  • BusKill Dead Man Switch now available in a brick-and-mortar in Germany 🧱🛡️

    Jump

  • BusKill Dead Man Switch now available in a brick-and-mortar in Germany 🧱🛡️

    Jump

  • Thank you for supporting open-source security hardware <3

  • BusKill Dead Man Switch now available in a brick-and-mortar in Germany 🧱🛡️

    Jump

  • I made a video of this (demo in Windows, MacOS, Linux, TAILS, and QubesOS) with the old DIY model here (sorry for the terrible audio quality)

    We're currently working on an updated video with someone who is much better at video production than me; it should be finished in early 2024.

  • 3D-Printed USB Dead Man Switch (Proof-of-Concept Demo)

    Jump

  • You'd need magnets, pogo pins, wire, glue, solder, etc. The list of materials needed is listed in the "Materials" section of this article.

    @Goldfishlaser@lemmy.ml can provide more info

  • What are You Working on Wednesday

    Jump

  • I build open-source USB Dead Man Switches and the accompanying (also free) software

    |

    | |:--:| | Watch the BusKill Explainer Video for more info youtube.com/v/qPwyoD_cQR4 |

    You attach the kill cable to your body and if the connection between you to your computer is severed, then your device will lock, shutdown, or shred its encryption keys. It's designed to protect high-risk users’ data. Data could include private keys (eg theft of cryptocurrency assets), contacts of correspondence (eg sources of a journalist – such as whistleblowers), etc.

  • BusKill (FOSS Dead Man Switch) v0.7.0 released 💾

    Jump

  • I've paid myself nothing so-far. The price just barely breaks-even for the business. There's one-time costs like a few grand for a CNC'd injection mold and assembly jig, but also certification fees, product boxes, cardstock paper for documentation inserts, printing fees, artist commissions, packaging materials, warehousing, shipping, other logistics fees, etc.

    All of this is explained in-detail in "The Finances" section here.

    I prefer open-source hardware to be designed using common off-the-shelf items that are easily found everywhere in the world. Unfortunately, the one vendor of a USB-A magnetic breakaway couplers decided to EOL their product shortly after I published a guide on how to build your own BusKill cable. After we published, they all got sold-out, and we had to go to manufacturers for a custom component.

    Prices would drop dramatically if we could do production runs (and actually sell) >10,000 units at a time. Currently we only sell a few cables per month. If you want to help, please tell all your security-conscious friends about BusKill :)

  • BusKill (USB Dead Man Switch) v0.7.0 released 💾

    Jump

  • It should only be posted once to this community. It's also been cross-posted to other relevant communities.

  • BusKill (FOSS Dead Man Switch) v0.7.0 released 💾

    Jump

  • BusKill (Linux Dead Man Switch) v0.7.0 released 💾

    Jump

  • Good bot

  • Removed

    BusKill (USB Dead Man Switch) v0.7.0 released 💾

    Jump

  • BusKill (USB Dead Man Switch) v0.7.0 released 💾

    Jump

  • Stripe API Key: $70k Stolen from CCs via merchant to debit card "Instant Payments"

    Jump

  • I'm curious if any security engineers have covered this incident.

    Stripe does support generating Restricted API Keys. With "Restricted API Keys" you're able to mint a key that can live on your e-commerce website that has permission to accept payments but does not have permission to modify your merchant account's payout methods (eg adding a new "Instant Payments" debit card to the merchant account as this attacker did).

    Unfortunately, I've asked WooCommerce to support Restricted API Keys 1 year ago, but they marked it as "low priority"

    ...I would appreciate if more people would jump-in on ^ that ticket and scold WooCommerce so that they add support for Restricted API Keys ;)