---
title: "Discussion on \"Command Auditing in an SSH Terminal: What the Client Can See, and What Only the Server Can Enforce\" | Hashnode"
description: "Discussion on \"Command Auditing in an SSH Terminal: What the Client Can See, and What Only the Server Can Enforce\". SSH command auditing: client hints vs server ForceCommand, bash DEBUG hooks, and forgeable in-band markers."
url: "https://hashnode.com/posts/command-auditing-in-an-ssh-terminal-what-the-client-can-see-and-what-only-the-server-can-enforce/6ae8a43ea79f72eea5cacf0e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Command Auditing in an SSH Terminal: What the Client Can See, and What Only the Server Can Enforce](https://mistlab.hashnode.dev/command-auditing-in-an-ssh-terminal-what-the-client-can-see-and-what-only-the-server-can-enforce?utm_source=hashnode&utm_medium=feed)

SSH command auditing: client hints vs server ForceCommand, bash DEBUG hooks, and forgeable in-band markers.

Nov 2 · 11 min read · mistlab.hashnode.dev  
Read the article

-   [#terminal](https://hashnode.com/tag/terminal)
-   [#rust](https://hashnode.com/tag/rust)
-   [#ssh](https://hashnode.com/tag/ssh)
-   [#linux](https://hashnode.com/tag/linux)

## Written by

[c-wind](https://hashnode.com/@c-wind)

@c-wind

  
[View profile](https://hashnode.com/@c-wind)

Building developer tools around SSH and terminals. Rust, Linux, ops.

Building developer tools around SSH and terminals. Rust, Linux, ops.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.