329 karma · joined January 20, 2022
Security research historically has two difficult components that build on one another: 1. Understanding complex system internals: uncovering the inner workings hidden by abstractions or interfaces 2. Finding vulnerabilities in these uncovered mechanisms
Sometimes both steps are equally hard. But often, finding the vulnerability is trivial once the real mechanisms are uncovered, rather than relying on assumptions about inner workings.
CVE-2026-3854 is a case where the vulnerability is not plainly obvious after understanding the internals. Still, I am confident that this command injection would have been found quickly had it been exposed to a more traditional or accessible attack surface.
Neither the release post, nor the model card seems to indicate anything like this?
I recommend anybody in offensive/defensive cybersecurity to experiment with this. This is the real data point we needed - without the hype!
Never thought I'd say this but OpenAI is the 'open' option again.
https://media.ccc.de/v/39c3-skynet-starter-kit-from-embodied...
> [...] we also exploit the embodied AI agent in the robots, performing prompt injection and achieve root-level remote code execution.
Here's what I landed on: This config tries to emulate as much of tmux with native ghostty features (splits and tabs).
https://codeberg.org/jfkimmes/dotfiles/src/branch/master/gho...
They have SFU support as of recently, so it should scale similarly to Jitsi et al.
It's offline. Neither you nor the merchant have to have a connection to the bank for the transaction to happen.
By that definition neither the wallet holder nor the merchant would have to be online for a real 'offline' system.
GNU Taler e.g. is an online system on the other hand, where the merchant has to be online for pragmatic reasons. It's kind of sad to see them being categorically excluded by this requirement. Their the best we currently have afaik.
(Check out my answer below for sources https://news.ycombinator.com/item?id=36520725)
Basically he used (and invented) blind signatures to allow the bank to sign a 'coin' without knowing what they signed. The customer takes the blindly signed coins from the bank, pays at a merchant and later the merchant deposits the coins at the bank again, where the signature is checked.
In this context offline just means that the merchant can verify the authenticity of the coin without immediately needing a connection to the bank. At some point in the future, however, the merchant will have to connect to the bank to get their money. Check out his original paper for details[1].
Offline systems have drawbacks, though. E.g the GNU Taler people made the pragmatic decision to have an online system. See chapter 1.2.1 'Offline vs Online' of Florian Dold's Phd thesis for a discussion on why[2].
[1]: https://chaum.com/wp-content/uploads/2022/01/Chaum-1990-Chap... [2]: https://taler.net/papers/thesis-dold-phd-2019.pdf
(There is a lot of discussion on paid instances on mastodon. There is also e.g https://masto.host/ for a managed solution.)
> The Framework is… a pretty good laptop! Frankly, for the first model from a brand new company, Framework did an astounding job of feeling like your everyday consumer electronics seller. Pre-ordering opened up quick, shipped soon thereafter, and there weren’t any hiccups.
I was definitely impressed of how well everything worked, from shipping the laptop to build quality. It is a very fun device to use.
In case the author reads here:
> I sure wish Framework provided fwupd support! I have yet to update my BIOS because I’d prefer to use fwupd rather than create a mess with my bootloader.
There is an image for the most recent BIOS upgrade in LVFS-Testing [1].
[1]: https://knowledgebase.frame.work/en_us/framework-laptop-bios... >> "LVFS update"
I tried `touch`ing hidden files for each step and then add those as a dependency but that is not very elegant. Do you have this problem at all?
[1]: https://ec.europa.eu/info/strategy/priorities-2019-2024/euro...
Thank you for trying! You have an amazing product and provided much needed innovation in this space.
(Written from my Framework Laptop)
Private payments can easily solved without a blockchain. For private payments you don't need a completely trust-less system. Taler[1] solves this quite elegantly: they provide completetly anonymous payments for the customer but still require the merchant to be 'on-record' to make money laundering harder/impossible. For that they rely on a regulated and trusted party as you would with a regular payment provider or bank. No proof of work needed, no value volatility, just an online representation of cash with accountability for the merchant built-in.
Of course, this also means that your second point is still valid for Taler: The involved trusted parties could collectively decide that they want to discriminate against certain merchants, in the same way the current payment providers did.
No thanks, Medium. These dark patterns crop up everywhere lately...