[–] 7 points 3 weeks ago* (5 children)

It's actually possible to prevent impersonation:

In theory all the generated keys are added to a public certificate transparancy log. Browsers should check that the key is there (but your http client library probably doesn't - and this is why these compromised keys are a problem).

Website owners should also check that there are no other certificates in there, and if they see an extra misissued certificate something went really wrong at a CA and that CA would probably lose all the credibility and trust.

Also when you request a certificate the CA doesn't get your private keys, so they can't reuse your cert.

Example: https://ctlogs.dev/search?q=Programming.dev

  • source
  • parent
  • context
  • [–] 10 points 4 weeks ago

    Our management is so "forward-looking" that we are still in the March stage: they want AI used everywhere, and added everywhere in the product.

    Saying that sometimes you still need to use the brain for big decisions will make some people question your prompting skills publicly.

    Hell, we even rebranded the whole company to be an """AI company""". I hate it there and I sense layoffs coming soon, but finding a job in this period is hard. Wish me luck.

  • source
  • parent
  • context
  • [–] 3 points 1 month ago

    Oh yes, since all AI companies really want more regulations, I have an amazing idea for them: anything trained on stolen copyrighted materials needs to be published and licensed under public domain.

    Microsoft, I'm sure you'll thank me later!

  • source
  • [–] 3 points 1 month ago

    Combining the power of the asset store and AI, you too can create the next bland asset-reuse slop hit game!

    The asset store was already bland enough, adding AI to the mix surely is not gonna make the situation worse.

  • source
  • [–] 2 points 1 month ago

    Tools can not depend on other tools. One of the issues with traditional distributions is dependency resolution and package management (this is subcategory of a heavily discussed topic, I also talked about it in my LAS talk from 2025. We should avoid making individual packages or having dependencies between tools, to avoid all the unnecessary complexity that comes with it.

    I was getting excited about this, but this point might be a big dealbreaker. The C compiler for example will need to find manually installed headers and library files when you need to compile more than a hello world, and often tightly interacts with pkg-config, cmake etc.

    I fear you'd have to be working in a container anyway for some scenarios, unless there's some other parts not explained in the post.

    I'm also not a fan of the possible gatekeeping of who can create these tools, via signing and trusted repositories, but it's probably going to be fine in the end.

    TBH toolbx is quite a good environment to work in already. I would just have liked a bit more sandboxing though (i.e. have a way for it to not mount my home)

  • source
  • [–] 14 points 1 month ago (1 child)

    IMHO the entire injection procedure is to keep it "clean" and socially accepted. Very few people would be happy to see somebody being shot in the head, but seeing somebody "falling asleep" is much more "ok". It looks less violent even though the end result is the same. Surviving a lethal injection and waking up again in that nightmare must be horrible.

    The reality is that death penalty is cruel and more costly than keeping someone in prison for life, and this doesn't even consider the human cost of executing an innocent. It just doesn't make sense.

  • source
  • parent
  • context
  • view more: ‹ prev next ›