# Outdated documentation and unmaintained Windows build?

**URL:** <https://discourse.pijul.org/t/outdated-documentation-and-unmaintained-windows-build/1331>\
**Category:** Question\
**Created:** [February 18, 2026, 1:18pm UTC](https://discourse.pijul.org/t/outdated-documentation-and-unmaintained-windows-build/1331 "2026-02-18T13:18:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Wallby](https://avatars.discourse-cdn.com/v4/letter/w/4491bb/32.png) [@Wallby](https://discourse.pijul.org/u/Wallby)\
**Post date:** [February 18, 2026, 1:18pm UTC](https://discourse.pijul.org/t/outdated-documentation-and-unmaintained-windows-build/1331/1 "2026-02-18T13:18:28Z")

</div>

To get pijul to compile on Windows at all I had to change in `pijul/src/commands/mod.rs`:

```auto
#[cfg(not(unix))]
- fn pager(_repo_config_pager: Option<&pijul_config::Choice>) -> bool {
+ fn pager(_config: &pijul_config::Config) -> bool {

```

And I used a portable openssl build from [Download Free OpenSSL Windows Installers & ZIP Files](https://kb.firedaemon.com/support/solutions/articles/4000121705#ZIP-File) , and ran (in powershell)`$env:OPENSSL_DIR="PathToUnzippedOpenssl"`before running `cargo build`.

Now compilation worked.

I could go through the `pijul identity new` prompt to generate a key, something that is not documented in [Uploading public keys - The Pijul manual](https://pijul.org/manual/the_nest/public_keys.html#ssh-public-keys) .

But then `pijul identity prove User@ssh.pijul.com`caused an exception:

```auto
thread 'main' (38592) panicked at <RustupPath>rustup\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\clap_builder-4.5.53\src\builder\debug_asserts.rs:732:9:
Argument 'no_keyring' is positional and it must take a value but action is SetTrue
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

```

So I still can not push anything to nest dot pijul dot com it seems?