i suggest you could use `strace` to see what's going on here:
- launch vscode with `strace -fys300 -o /tmp/vscode.trace vscode`
- start vscode console and run `wg genkey`
- exit vscode
- examine the trace log, searching for (likely) execve("/usr/bin/wg", ["wg",
"genkey"] ...
- see if it's invoked correctly, what in/outputs it uses
- hopefully understand what's the difference to running it directly with
`strace -fys300 -o /tmp/wggenkey.trace wg genkey`
** Changed in: wireguard (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2136094
Title:
wg genkey generate empty key through vscode console
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/2136094/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
