ledger

Problem

Solana CLI tools display user controlled input from various sources without any sanitization. A malicious user can craft input to include ANSI escape sequences, hijacking a victim's console and spoofing legitimate command output. Naturally leading to social attacks

Some affected sources of user-controlled text input

• Memo instructions
• Program logs
• Validator info

A parametrized option to set the blocksize would be useful to experiment with. As quorum is used in a private setting I think this option should be available

As an intermediate step towards #1015, and various parts thereof, would it be possible to ignore the syntax for features not currently supported, yet use the parts which are supported in trades?
I'm thinking out loud and wondering what effects this may have.

My end goal here is to be able to read a data file https://gitlab.com/snippets/1856416 without errors. Hledger would be able to parse thi

this is the natural behavior of node-hid but we should backport this behavior to all other transports.

basically it's a failsafe for race conditions.

if you open() a transport, you are responsible to close() it in a finally, if an open() happens during that time it should throw if it concerns the same device (e.g. by path id / by uuid, ... depending on the transport)

Thinking to just have it dump the raw wallet files to a file would be useful, especially for some older wallet types.