• 0 Posts
  • 144 Comments
Joined 2 years ago
cake
Cake day: August 4th, 2023

help-circle















  • TootSweet@lemmy.worldto196@lemmy.blahaj.zonerule
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 months ago

    Nice! Thanks for clarifying that. It definitely puts some of the hypotheses to rest. I imagine some of the people saying it was staged were just too swept up in the AI bubble hype to admit to themselves or others that their Lord and Savior Generative AI could be so dumb as to do that sort of thing without a human faking it.



  • TootSweet@lemmy.worldto196@lemmy.blahaj.zonerule
    link
    fedilink
    English
    arrow-up
    68
    arrow-down
    3
    ·
    edit-2
    2 months ago

    I don’t think this is Gemini trying to run some of its own code to save facts about the user and whoops displaying the code it was trying to run to the user rather than running it or anything like that. That’s not how software works, and not how LLMs work.

    More likely somewhere in Gemini’s training data, there’s one or more code examples (specifically Python code examples, by the looks of it) that have something to do with the user’s prompt. The relationship between Python code examples and the user’s prompt may well be extremely nonobvious, but there’d have to be something about the prompt that made Gemini hallucinate that.

    Source: Am software engineer. Though I don’t have any hands-on experience with generative AI to speak of. I do think generative AI is a bullshit hype bubble, though.


  • Does it really do any good for the drive to be encrypted if it doesn’t require a password (or Yubikey or retinal scan or other authentication factor) on boot? If you’re just going to put the plaintext key/password on the same drive but in a partition that’s not encrypted, there’s no point encrypting the drive, right?

    So maybe “it asks for a password on boot” is more of a “works as intended” thing?

    How will I access the encrypted devices after installation? (System Startup) During system startup you will be presented with a passphrase prompt. …

    The quote above is from Fedora documentation here

    This is your root FS that’s encrypted that we’re talking about, correct?

    If you really want an encrypted root but no password on boot and the plaintext decryption password/key on the same drive, there are ways to do it. (It would probably require customizing the initramfs somehow. But it’s Linux, and Linux certainly isn’t going to prevent you from doing such things. Just try to dissuade you.)

    If we’re not talking about a root filesystem, that would likely change some things. If it’s Luks, I’m pretty sure it wouldn’t matter particularly where on your filesystem the key was so long as your /etc/crypttab refers to it. I’d say that sort of setup would probably only provide additional security if the encrypted drive is an external drive that you might worry could be stolen or physically accessed when the attacker doesn’t have physical access to your root filesystem.

    Also, if you shared what encryption scheme was in use (Luks, Anaconda, etc), that would probably help as well.

    Edit: Ah. Ok. You gave more info while I was typing the above response. What you want is unlocking via ssh. For sure.