can't get it to work - always fails with "unknown option -nocert"

[wizzard0]

• open any PEM file

• select entire file or just base64 lines lines between ---begin certificate---

• expected result: some visualization?

• result: error notification:

  Errors: unknown option -nocert
  usage: x509 [-C] [-addreject arg] [-addtrust arg] [-alias] [-CA file]
  [-CAcreateserial] [-CAform der | pem] [-CAkey file]
  [-CAkeyform der | pem] [-CAserial file] [-certopt option]
  [-checkend arg] [-clrext] [-clrreject] [-clrtrust] [-dates]
  [-days arg] [-email] [-enddate] [-extensions section]
  [-extfile file] [-fingerprint] [-hash] [-in file]

show-x509 v0.0.1 VS Code 1.76.0 on macOS Ventura 13.2.1 (M1)

% where openssl
> /usr/bin/openssl
% openssl version
> LibreSSL 3.3.6

[wintersteiger]

Thanks for the report! Apparently LibreSSL doesn't support the -nocert option. The extension just calls out to the openssl binary and assumes it's the normal OpenSSL. (And yes, it just puts the output into a new file editor.)

[wizzard0]

Seems so! At the same time I don’t want to replace the default macOS openssl either %)

On Mon, Mar 6, 2023 at 14:14, Christoph M. Wintersteiger @.***> wrote:

Thanks for the report! Apparently LibreSSL doesn't support the -nocert option. The extension just calls out to the openssl binary and assumes it's the normal OpenSSL. (And yes, it just puts the output into a new file editor.)

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

[wintersteiger]

I've added configuration options that let you set the path to the binary and additional arguments, so that should work in most circumstances now.