Question 1

How to use Kerberos authentication with WinRM for Go?

Accepted Answer

Use the TransportDecorator with ClientKerberos struct, specifying parameters like username, password, realm, and KrbConf file as shown in the README. Ensure the remote Windows host is configured for Kerberos with AllowUnencrypted settings.

Question 2

WinRM for Go vs PowerShell Remoting – which is better for automation?

Accepted Answer

WinRM for Go is a library for building custom Go applications, offering programmatic control, while PowerShell Remoting is native to Windows and better for script-based automation. Choose based on your toolchain; WinRM for Go integrates well into Go ecosystems.

Question 3

How to handle timeouts and cancellation in WinRM for Go?

Accepted Answer

Use context.WithTimeout or similar with RunWithContext methods; the library supports Go's context package to abort commands on the remote machine, but note that HTTP request cancellation may not be immediate.

Question 4

Can WinRM for Go work through an SSH tunnel?

Accepted Answer

Yes, by setting a custom Dial function in parameters, such as using ssh.Client.Dial, as demonstrated in the README example for tunneling to other hosts securely.

Question 5

Is WinRM for Go secure for production use with HTTPS?

Accepted Answer

It supports TLS and client certificate authentication, but the README examples often use AllowUnencrypted='true' for simplicity. Always configure encrypted connections and valid certificates to avoid security risks in production.

Question 6

How to install the command-line tool for WinRM?

Accepted Answer

The CLI tool is split into a separate project at winrm-cli; this library is for programmatic use. Install it from the linked GitHub repository for standalone command execution.

winrm

What is winrm?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions