‹ BackHN Continuity

Thread

An agent used DNS to reach an external chatbot

198 points · 189 comments · apsec112

  1. garo-pro · · focus · HN ↗
    Most interesting here:

    > We therefore stopped the affected training run and have subsequently decided to pause all other training, evaluation, and inference with tool-use (defined broadly) for our most capable models until we have both validated that the gap is resolved and performed additional red-teaming of the system. When training restarts, we will begin a fresh run with additional alignment improvements, including more comprehensive misalignment interventions. We will not resume training this particular model, even though the existing reward signal already correctly penalized this behavior.

    1. CTDOCodebases · · focus · HN ↗
      Maybe I lack intelligence but when you have a program that is basically brute forcing a solution to a problem repeatedly how is it possible to contain it?

      Sooner or later it's going to come up with a solution that is more intelligent than the lead security person anticipated.

      1. oezi · · focus · HN ↗
        I am really suprised that they do not start putting up the same signs you would for humans to prevent unauthorized access:

          Keep out. If you can read this sign you are off track. Leave now.
        
        I mean, how are the agents to know that they are overreaching if they just get cache miss or 404.

        From the conversation log and CoT you also get the impression that the RLHF has been overdone. The agents seem really obsessed to obtain the answer and understanding motive ('it could be browsercomp').

        1. Tostino · · focus · HN ↗
          What they should do, is inject a system prompt at that point telling the model to get out of there. It is the entire reason they train the different levels into the template.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.