• BastingChemina@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    9
    ·
    8 hours ago

    The fact that people give Claude access to their secrets is a big liability in the first place.

    Even Claude itself warns you about it. I did shared a snippet of code with API keys in it by mistake, I got a huge warning telling me that I should consider these compromise and change them immediately.

  • Artisian@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    11 hours ago

    So this is a pretty bad headline; it isn’t Claude Code sharing the secrets, it’s the user syncing their command history.

    I’m sad we can’t get claude to share what it’s seen.

  • partial_accumen@lemmy.world
    link
    fedilink
    English
    arrow-up
    35
    ·
    21 hours ago

    When a user chooses the “Yes, and don’t ask again” option to approve running a command, that choice gets stored as part of a rule in the local “.claude/settings.local.json” file on the user’s computer.

    Saving privileged credentials in the clear in a config file? I think I can take credit for Claude doing that as this. Claude was clearly trained on my StackOverflow posts from 15 years ago.

  • eicker@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    50
    arrow-down
    5
    ·
    23 hours ago

    The irony is spectacular: a coding assistant designed to automate development also automates the creation of security liabilities. And Anthropic’s response seems to be more automation. Perhaps the next AI agent can monitor the first AI agent while a third one explains to management why the database credentials are now public.

  • Wispy2891@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    2
    ·
    16 hours ago

    Why they’re blaming the tool instead of the user?

    It’s the vibe coder’s fault if they don’t even watch the files edited in a commit.

    Not only they approve a commit without reading the code, but they approve without watching the list of edited files in a commit? They don’t use vs code or something that shows a diff? Just type in a box and let the algorithm have full control on the commits, blindly?