cat > keys.txt empties "keys.txt"

[kootenpv]

Probably you mean: cat keys.txt

[ThomasHabets]

I didn't mean that, no. It's example instructions to set up (including the ^D to signal EOF), not to see how it's set up.

But maybe it should be just cat, to show what was written.

Is there an established standard for this? Maybe the latter is more common?

[kootenpv]

I think if you have a way to generate it with a command, you would show that.

If not, then show the input you expect... that can indeed be done with cat keys.txt

Thats my take on it :)

On Mar 13, 2018 6:24 PM, "Thomas Habets" [email protected] wrote:

I didn't mean that, no. It's example instructions to set up (including the ^D to signal EOF), not to see how it's set up.

But maybe it should be just cat, to show what was written.

Is there an established standard for this? Maybe the latter is more common?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/google/sshkey-audit/issues/1#issuecomment-372748604, or mute the thread https://github.com/notifications/unsubscribe-auth/ACnnc4vs3GGYUv9irZrjKvwQFNSGWlWvks5teADUgaJpZM4SpG_h .