Toms params/result metadata

[chutuananh2k]

• Tome should define return type as well.
• Params/return metadata should provide a presentation field, borrow from html. For ex:

paramdefs:
    - name: path
      type: string
      view: input
      label: Absolute file path
      placeholder: "/etc/passwd"

resultdefs:
    - name: file
      type: binary
      view: img
      label: Screenshot
      placeholder:"spinner.png"

Or we can leverage protobuf to define params/result. It will make gui to generate form input and output much easier.

[hulto]

Great idea.
And I think we've kinda started going down the protobuf route you're thinking of.
We've added a number of types like File, Process, and Credential which you can create from the agent using the report library.
We don't have any UI components that take advantage of them yet but are developing components to explore Process trees, and File trees in the UI instead of just relying on the Text Output.
So far the "structured" data I think is only used in the UI as TextOutput and ErrorOutput. But that's also pretty new.

[hulto]

Here's where the current types are defined.

https://github.com/spellshift/realm/blob/main/tavern/internal/c2/proto/eldritch.proto

Here's the eldritch docs to report objects to the backend.

https://docs.realm.pub/user-guide/eldritch#report