Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Dennis IT SysAdmin <it@fourpeakslandscape.com>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: WireGuard 0.3.1 Potential Bug #AddConf
Date: Tue, 24 Nov 2020 22:04:10 +0000	[thread overview]
Message-ID: <BY5PR17MB36173DFB2D19C80A9798729EA9FB0@BY5PR17MB3617.namprd17.prod.outlook.com> (raw)
In-Reply-To: <BY5PR17MB36175E4EB9A88CE42A2D1D86A9FB0@BY5PR17MB3617.namprd17.prod.outlook.com>


While setting up the VPN and also working on creating a powershell module for setup, I went through to test the components in wg.exe, and I noticed an issue with addconf which is supposed to allow appending to a current configuration:

Several scenarios tested-




Windows ( Under an admin (not system) account where config was created (not created using system account):
[

PS C:\Program Files\WireGuard>      wg addconf WireGuard 'C:\Program Files\WireGuard\Data\Configurations\WireGuardVPN.conf.dpapi'

fopen: Permission denied

]



Windows ( Under SYSTEM account where config was NOT created (using PSTools to get into SYSTEM environment):
[

PS C:\Program Files\WireGuard>    wg addconf WireGuard 'C:\Program Files\WireGuard\Data\Configurations\WireGuardVPN.conf.dpapi'​ 

Line unrecognized: `\x01'
Configuration parsing error

]



DebianServer ( Under SU account where config was created & under USER account where config was NOT created - Same result ):

[
root@unix:/home/system#     wg addconf WireGuard /etc/wireguard/wg0.conf 

Line unrecognized: `Address=172.10.10.1/24'
Configuration parsing error

]















Thanks,

Dennis Fair  |  I.T Systems Admin
Four Peaks Landscape Management
p: 480-967-0376  |  f: 480-967-0406
m: 480-319-5345
e: it@fourpeakslandscape.com


       reply	other threads:[~2020-11-25 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BY5PR17MB36175E4EB9A88CE42A2D1D86A9FB0@BY5PR17MB3617.namprd17.prod.outlook.com>
2020-11-24 22:04 ` Dennis IT SysAdmin [this message]
2020-11-25 13:03   ` Jason A. Donenfeld

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BY5PR17MB36173DFB2D19C80A9798729EA9FB0@BY5PR17MB3617.namprd17.prod.outlook.com \
    --to=it@fourpeakslandscape.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).