Les images sont multi-arch et publiées à la fois sur Docker Hub (`jpillora/chisel`) et sur le registre de conteneurs GitHub (`ghcr.io/jpillora/chisel`).

### Fedora

Le paquet est maintenu par la communauté Fedora. Si vous rencontrez des problèmes liés à l'utilisation du RPM, veuillez utiliser ce [suivi de problèmes](https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&component=chisel&list_id=11614537&product=Fedora&product=Fedora%20EPEL).```sh
sudo dnf -y install chisel

## Démo

Vous pouvez lancer votre propre serveur de démo en quelques minutes (l'ancienne démo Heroku a disparu avec le niveau gratuit d'Heroku). [`example/fly.toml`](https://github.com/jpillora/chisel/blob/HEAD/example/fly.toml) déploie ce `chisel server` vers l'allocation gratuite de [fly.io](https://fly.io) :```sh
$ chisel server --port $PORT --backend http://example.com
# listens on $PORT, proxies normal web requests to http://example.com

Visiter l'URL de votre application dans un navigateur atteint le proxy backend par défaut du serveur et affiche une copie de [example.com](http://example.com).

## Utilisation

<!-- générez ces textes d'aide manuellement,
  ou utilisez https://github.com/jpillora/md-tmpl
    avec $ md-tmpl -w README.md -->

<!--tmpl,code=plain:echo "$ chisel --help" && go run main.go --help | sed 's#0.0.0-src (go1\..*)#X.Y.Z#' -->``` plain 
$ chisel --help

  Usage: chisel [command] [--help]

  Version: X.Y.Z

  Commands:
    server - runs chisel in server mode
    client - runs chisel in client mode

  Read more:
    https://github.com/jpillora/chisel

--host, Defines the HTTP listening host – the network interface
(defaults the environment variable HOST and falls back to 0.0.0.0).

--port, -p, Defines the HTTP listening port (defaults to the environment
variable PORT and falls back to port 8080).

--key, (deprecated use --keygen and --keyfile instead)
An optional string to seed the generation of a ECDSA public
and private key pair. All communications will be secured using this
key pair. Share the subsequent fingerprint with clients to enable detection
of man-in-the-middle attacks (defaults to the CHISEL_KEY environment
variable, otherwise a new key is generate each run).

--keygen, A path to write a newly generated PEM-encoded SSH private key file.
If users depend on your --key fingerprint, you may also include your --key to
output your existing key. Use - (dash) to output the generated key to stdout.

--keyfile, An optional path to a PEM-encoded SSH private key. When
this flag is set, the --key option is ignored, and the provided private key
is used to secure all communications. (defaults to the CHISEL_KEY_FILE
environment variable). Since ECDSA keys are short, you may also set keyfile
to the inline key string itself, exactly as printed by --keygen (a base64
string with a "ck-" prefix); no extra base64 encoding is needed.

--authfile, An optional path to a users.json file. This file should
be an object with users defined like:
  {
    "<user:pass>": ["<addr-regex>","<addr-regex>"]
  }
when <user> connects, their <pass> will be verified and then
each of the remote addresses will be compared against the list
of address regular expressions for a match. Patterns are NOT
anchored by default: "10.0.0.1:80" also matches
"210.0.0.1:8080", and "." matches any character. Anchor your
patterns, e.g. "^10\.0\.0\.1:80$". The empty string ""
matches every address. Addresses will
always come in the form "<remote-host>:<remote-port>" for normal remotes,
"R:<local-interface>:<local-port>" for reverse port forwarding
remotes, and "socks" for SOCKS5 proxy access. Note that SOCKS5
access previously bypassed this list; existing authfiles which
should allow SOCKS5 must add an entry matching "socks" (the
empty wildcard "" matches everything, including "socks"). This
file will be automatically reloaded on change. Reloads apply
to new connections and to new tunnels of connected clients;
established tunnels are not interrupted.

--auth, An optional string representing a single user with full
access, in the form of <user:pass>. It is equivalent to creating an
authfile with {"<user:pass>": [""]}. If unset, it will use the
environment variable AUTH.

--keepalive, An optional keepalive interval. Since the underlying
transport is HTTP, in many instances we'll be traversing through
proxies, often these proxies will close idle connections. You must
specify a time with a unit, for example '5s' or '2m'. Defaults
to '25s' (set to 0s to disable).

--backend, Specifies another HTTP server to proxy requests to when
chisel receives a normal HTTP request. Useful for hiding chisel in
plain sight. --proxy is accepted as an alias for this flag.

--socks5, Allow clients to access the internal SOCKS5 proxy. See
chisel client --help for more information.

--reverse, Allow clients to specify reverse port forwarding remotes
in addition to normal remotes.

--tls-key, Enables TLS and provides optional path to a PEM-encoded
TLS private key. When this flag is set, you must also set --tls-cert,
and you cannot set --tls-domain.

--tls-cert, Enables TLS and provides optional path to a PEM-encoded
TLS certificate. When this flag is set, you must also set --tls-key,
and you cannot set --tls-domain.

--tls-domain, Enables TLS and automatically acquires a TLS key and
certificate using LetsEncrypt. Setting --tls-domain requires port 443.
You may specify multiple --tls-domain flags to serve multiple domains.
The resulting files are cached in the "$HOME/.cache/chisel" directory.
You can modify this path by setting the CHISEL_LE_CACHE variable,
or disable caching by setting this variable to "-". You can optionally
provide a certificate notification email by setting CHISEL_LE_EMAIL.

--tls-ca, a path to a PEM encoded CA certificate bundle or a directory
holding multiple PEM encode CA certificate bundle files, which is used to 
validate client connections. The provided CA certificates will be used 
instead of the system roots. This is commonly used to implement mutual-TLS. 

--pid Generate pid file in current working directory

-v, Enable verbose logging

--help, This help text

<!--/tmpl-->


<!--tmpl,code=plain:echo "$ chisel client --help" && go run main.go client --help | sed 's#0.0.0-src (go1\..*)#X.Y.Z#' -->``` plain 
$ chisel client --help

  Usage: chisel client [options] <server> <remote> [remote] [remote] ...

  <server> is the URL to the chisel server.

  <remote>s are remote connections tunneled through the server, each of
  which come in the form:

    <local-host>:<local-port>:<remote-host>:<remote-port>/<protocol>

    ■ local-host defaults to 0.0.0.0 (all interfaces).
    ■ local-port defaults to remote-port.
    ■ remote-port is required*.
    ■ remote-host defaults to 127.0.0.1 (server localhost).
    ■ protocol defaults to tcp.

  which shares <remote-host>:<remote-port> from the server to the client
  as <local-host>:<local-port>, or:

    R:<local-interface>:<local-port>:<remote-host>:<remote-port>/<protocol>

  which does reverse port forwarding, sharing <remote-host>:<remote-port>
  from the client to the server's <local-interface>:<local-port>.

    example remotes

      3000
      example.com:3000
      3000:google.com:80
      192.168.0.5:3000:google.com:80
      socks
      5000:socks
      R:2222:localhost:22
      R:socks
      R:5000:socks
      stdio:example.com:22
      1.1.1.1:53/udp

    When the chisel server has --socks5 enabled, remotes can
    specify "socks" in place of remote-host and remote-port.
    The default local host and port for a "socks" remote is
    127.0.0.1:1080. Connections to this remote will terminate
    at the server's internal SOCKS5 proxy. When the server also
    has --authfile set, SOCKS5 access requires an entry matching
    the token "socks" in the user's address list.

    When the chisel server has --reverse enabled, remotes can
    be prefixed with R to denote that they are reversed. That
    is, the server will listen and accept connections, and they
    will be proxied through the client which specified the remote.
    Reverse remotes specifying "R:socks" will listen on the server's
    default socks port (1080) and terminate the connection at the
    client's internal SOCKS5 proxy.

    When stdio is used as local-host, the tunnel will connect standard
    input/output of this program with the remote. This is useful when 
    combined with ssh ProxyCommand. You can use
      ssh -o ProxyCommand='chisel client chiselserver stdio:%h:%p' \
          [email protected]
    to connect to an SSH server through the tunnel.

  Options:

    --fingerprint, A *strongly recommended* fingerprint string
    to perform host-key validation against the server's public key.
    Fingerprint mismatches will close the connection.
    Fingerprints are generated by hashing the ECDSA public key using
    SHA256 and encoding the result in base64.
    Fingerprints must be 44 characters containing a trailing equals (=).
    Legacy MD5 colon fingerprints (deprecated) are still accepted,
    but only in their full 16-octet form; truncated prefixes are
    rejected.

    --auth, An optional username and password (client authentication)
    in the form: "<user>:<pass>". These credentials are compared to
    the credentials inside the server's --authfile. defaults to the
    AUTH environment variable.

    --keepalive, An optional keepalive interval. Since the underlying
    transport is HTTP, in many instances we'll be traversing through
    proxies, often these proxies will close idle connections. You must
    specify a time with a unit, for example '5s' or '2m'. Defaults
    to '25s' (set to 0s to disable).

    --max-retry-count, Maximum number of times to retry before exiting.
    Defaults to unlimited.

    --min-retry-interval, Minimum wait time before retrying after a
    disconnection. Defaults to 1 second.

    --max-retry-interval, Maximum wait time before retrying after a
    disconnection. Defaults to 5 minutes.

    --proxy, An optional HTTP CONNECT or SOCKS5 proxy which will be
    used to reach the chisel server. Authentication can be specified
    inside the URL. Credentials must be URL-encoded; for example a
    "#" in the password must be written as "%23".
    For example, http://admin:[email protected]:8081
            or: socks://admin:[email protected]:1080
    The socks://, socks5:// and socks5h:// schemes are equivalent:
    DNS is always resolved by the proxy.

    --header, Set a custom header in the form "HeaderName: HeaderContent".
    Can be used multiple times. (e.g --header "Foo: Bar" --header "Hello: World")

    --hostname, Optionally set the 'Host' header (defaults to the host
    found in the server url).

    --sni, Override the ServerName when using TLS (defaults to the 
    hostname).

    --tls-ca, An optional root certificate bundle used to verify the
    chisel server. Only valid when connecting to the server with
    "https" or "wss". By default, the operating system CAs will be used.

    --tls-skip-verify, Skip server TLS certificate verification of
    chain and host name (if TLS is used for transport connections to
    server). If set, client accepts any TLS certificate presented by
    the server and any host name in that certificate. This only affects
    transport https (wss) connection. Chisel server's public key
    may be still verified (see --fingerprint) after inner connection
    is established.

    --tls-key, a path to a PEM encoded private key used for client 
    authentication (mutual-TLS).

    --tls-cert, a path to a PEM encoded certificate matching the provided 
    private key. The certificate must have client authentication 
    enabled (mutual-TLS).

    --pid Generate pid file in current working directory

    -v, Enable verbose logging

    --help, This help text

  Signals:
    The chisel process is listening for:
      a SIGINT or SIGTERM to begin a graceful shutdown
        (a second signal forces an immediate exit),
      a SIGUSR2 to print process stats, and
      a SIGHUP to short-circuit the client reconnect timer

  Version:
    X.Y.Z

  Read more:
    https://github.com/jpillora/chisel

Pour utiliser votre propre certificat (auto-signé ou CA interne), générez une paire clé/certificat et pointez les deux côtés vers les bons fichiers :```sh
chisel server --port 443 --tls-key key.pem --tls-cert cert.pem
chisel client --tls-ca ca.pem https://chisel.example.com 3000

```markdown
## Utilisation

### Tests

Pour exécuter les tests unitaires, utilisez la commande suivante :

```bash
go test ./...

go run examples/basic/main.go

chisel server --reverse --authfile users.json
chisel client --auth exituser:password <server-address> R:socks
# server-side consumers point SOCKS5 clients at 127.0.0.1:1080,
# and their traffic exits via the chisel client's network
```
See also the step-by-step [reverse tunneling example](https://github.com/jpillora/chisel/blob/HEAD/example/reverse-tunneling-authenticated.md).

### Running behind a CDN (Cloudflare)

chisel works through CDNs that support WebSockets. For Cloudflare: enable WebSockets, proxy (orange-cloud) the DNS record, and connect clients with `https://`. The CDN terminates TLS, but the inner SSH layer means `--fingerprint` validation still authenticates your chisel server end-to-end — the CDN cannot read or modify tunneled traffic. Keep `--keepalive` at its `25s` default to stay under CDN idle timeouts, and note that proxies which strip `Upgrade` headers cannot carry chisel at all.

### Tuning with environment variables

Less common knobs are environment variables, all read with a `CHISEL_` prefix (e.g. `CHISEL_WS_TIMEOUT=10s`):

| Variable        | Side        | Default            | Purpose                                            |
| --------------- | ----------- | ------------------ | -------------------------------------------------- |
| `WS_TIMEOUT`    | client      | `45s`              | timeout de la poignée de main websocket            |
| `SSH_TIMEOUT`   | client      | `30s`              | timeout de la poignée de main ssh                  |
| `CONFIG_TIMEOUT`| server      | `10s`              | attente de la requête de config du client          |
| `SSH_WAIT`      | both        | `35s`              | durée d'attente des nouveaux tunnels pour une connexion active |
| `PING_TIMEOUT`  | both        | keepalive interval | timeout de réponse au ping keepalive (aucun ping si `--keepalive 0`) |
| `DIAL_TIMEOUT`  | exit node   | `30s`              | timeout de connexion tcp pour les cibles du tunnel |
| `WS_READ_LIMIT` | both        | `524288`           | taille maximale des messages websocket entrants en octets (0 = aucune limite ; négatif = défaut) |
| `WS_BUFF_SIZE`  | both        | go default         | tailles des tampons de lecture/écriture websocket  |
| `UDP_MAX_SIZE`  | both        | `9012`             | taille maximale des paquets udp en octets          |
| `UDP_DEADLINE`  | exit node   | `15s`              | délai de lecture des flux udp et âge de purge en inactivité |
| `UDP_MAX_CONNS` | exit node   | `100`              | nombre maximal de flux udp simultanés par tunnel   |
| `SHUTDOWN_GRACE`| server      | `5s`               | temps de drain des requêtes http à l'arrêt         |

`HOST`, `PORT`, `AUTH`, and `CHISEL_KEY`/`CHISEL_KEY_FILE` are documented in the `--help` texts above.

#### Caveats

Since WebSockets support is required:

- IaaS providers all will support WebSockets (unless an unsupporting HTTP proxy has been forced in front of you, in which case I'd argue that you've been downgraded to PaaS)
- PaaS providers vary in their support for WebSockets
  - Heroku has full support
  - Openshift has full support though connections are only accepted on ports 8443 and 8080
  - Google App Engine standard has **no** support (the flexible environment does)

## Contributing

- http://golang.org/doc/code.html
- http://golang.org/doc/effective_go.html
- `github.com/jpillora/chisel/share` contains the shared package
- `github.com/jpillora/chisel/server` contains the server package
- `github.com/jpillora/chisel/client` contains the client package

## Changelog

- `1.0` - Version initiale
- `1.1` - Remplacement du chiffrement symétrique simple par ECDSA SSH
- `1.2` - Ajout de la prise en charge de SOCKS5 (serveur) et de HTTP CONNECT (client)
- `1.3` - Ajout de la prise en charge du tunnel inversé
- `1.4` - Ajout de la prise en charge d'en-têtes HTTP arbitraires
- `1.5` - Ajout de la prise en charge de SOCKS inversé (par @aus)
- `1.6` - Ajout de la prise en charge de stdio côté client (par @BoleynSu)
- `1.7` - Ajout de la prise en charge de l'UDP
- `1.8` - Passage à une image Docker `scratch`
- `1.9` - Passage à Go 1.21. Remplacement de la graine `--key` par des chaînes de clés P256 avec `--key{gen,file}` (par @cmenginnz)
- `1.10` - Passage à Go 1.22. Ajout de `.rpm`, `.deb` et `.apk` aux versions publiées. Correction de la mauvaise comparaison de versions.
- `1.11` - Passage à Go 1.25.1. Mise à jour de toutes les dépendances.
- `1.12` - (non publié) Passe de fiabilité et de sécurité :
  - les pings keepalive expirent désormais (`CHISEL_PING_TIMEOUT`), de sorte que les connexions mortes se reconnectent rapidement après la mise en veille/réveil, les timeouts NAT et les redémarrages du serveur
  - les rechargements d'authfile survivent aux renommages par l'éditeur et aux échanges de configmaps kubernetes, et s'appliquent en direct aux clients connectés (nouveaux tunnels ; les tunnels établis ne sont pas interrompus)
  - **rupture** : avec `--socks5` + `--authfile`, l'accès SOCKS5 exige désormais une entrée authfile correspondant à `socks` (les entrées génériques `""` continuent de fonctionner)
  - **rupture** : les empreintes MD5 héritées tronquées sont rejetées — `--fingerprint` doit être la forme complète SHA256 (ou la forme complète MD5 à 16 octets avec deux-points)
  - **rupture** : les chaînes d'authentification sans deux-points (par ex. `--auth user`) provoquent une erreur fatale au démarrage au lieu de désactiver silencieusement l'authentification
  - la demi-fermeture TCP est propagée à travers les tunnels, et les cibles inaccessibles rejettent le tunnel au lieu de présenter une connexion morte (`CHISEL_DIAL_TIMEOUT`, défaut 30s)
  - arrêt gracieux sur SIGTERM avec drain des requêtes HTTP (`CHISEL_SHUTDOWN_GRACE`) ; un second signal force la sortie
  - les nœuds de sortie UDP ne cassent plus ni ne fuient au-delà de 100 flux simultanés (`CHISEL_UDP_MAX_CONNS`)
  - les messages websocket entrants sont plafonnés en taille avant authentification (`CHISEL_WS_READ_LIMIT`)
  - le serveur ne panique plus lorsqu'un client se déconnecte entre la poignée de main SSH et sa requête de config (#608)
  - le client se termine avec un code non nul lorsque `--max-retry-count` est épuisé ; nouveau `--min-retry-interval` (défaut 1s) ; `socks5://` accepté pour `--proxy`
  - les builds `go install` rapportent leur vraie version ; les sessions et les échecs de connexion sont journalisés au niveau info
  - les versions publiées fournissent désormais des images Docker multi-arch construites avec goreleaser vers GHCR et Docker Hub avec des versions correctement estampillées ; la publication se fait en deux étapes — le tagging crée une version GitHub brouillon plus des images taguées par version, et la publication du brouillon promeut les tags Docker `latest` / `X` / `X.Y`

### Mise à niveau vers 1.12

Quatre changements peuvent nécessiter une action lors de la mise à niveau depuis 1.11.x ou une version antérieure :

1. **SOCKS5 + `--authfile`** (appliqué depuis v1.11.7) : les utilisateurs qui doivent conserver l'accès proxy ont besoin d'une entrée authfile correspondant au jeton `socks` (le caractère générique `""` continue de fonctionner). Voir [Authentification](#authentication). Les requêtes refusées sont journalisées côté serveur comme `Denied connection to socks (ACL)`.
2. **`--fingerprint`** : les empreintes MD5 héritées tronquées sont rejetées. Utilisez l'empreinte SHA256 complète affichée par le serveur et le client (la forme complète MD5 à 16 octets avec deux-points est toujours acceptée, mais dépréciée).
3. **`--auth`** : les valeurs doivent être `<user>:<pass>` — les chaînes sans deux-points échouent désormais au démarrage au lieu de désactiver silencieusement l'authentification.
4. **Codes de sortie** : `chisel client` avec `--max-retry-count` se termine désormais avec un code non nul lorsque les tentatives de connexion sont épuisées ; les scripts qui vérifient `$?` et les unités systemd `Restart=on-failure` le remarqueront.

## Licence

[MIT](https://github.com/jpillora/chisel/blob/master/LICENSE) © Jaime Pillora