Reputation
Top tag
Next privilege 125 Rep.
Vote down
Badges
1 2 12
Newest
 Commentator
Impact
~16k people reached

  • 0 posts edited
  • 0 helpful flags
  • 7 votes cast
Apr
26
revised OpenVPN Client Config Dir - where common name includes non-utf8 characters?
added 159 characters in body
Apr
26
comment OpenVPN Client Config Dir - where common name includes non-utf8 characters?
You were not far from it, and your guess is qualified so please leave it here for any other brave soul wondering about this post.
Apr
26
comment OpenVPN Client Config Dir - where common name includes non-utf8 characters?
@kasperd You got me thinking, I did as you guessed garbled up the output of the log by copying the line somewhere into a text editor and save it in Python to print it (because I was lazy). Correct way to do it is with open('/var/log/openvpn/openvpn.log', 'rb') as fh: print([fh.read()]) and that got me \xc3\x83\xc2\xb6 for the ö and renaming the client configuration to /etc/openvpn/ccd/l\xc3\x83\xc2\xb6vberg worked. Write up a answer and the solution points are yours.
Apr
26
awarded  Commentator
Apr
26
revised OpenVPN Client Config Dir - where common name includes non-utf8 characters?
added 2 characters in body
Apr
26
comment OpenVPN Client Config Dir - where common name includes non-utf8 characters?
@kasperd Ah crap I'm using Python2.7 because BSD. Yea you might be right. Normally openin the file as a binary file handle and not using print on the string but print([data]) gives you a rather accurate description of the content without modifying it first. The only downside being the terminal encoding but usually none of the .encode().decode() chain problems.
Apr
26
asked OpenVPN Client Config Dir - where common name includes non-utf8 characters?
Apr
14
awarded  Notable Question
Mar
27
comment OpenVPN - tap interfaces and default gateway
Yepp this completely slipped my mind and was rather obvious on later years of using VPN, but good addition for anyone ending up here and are new to these kinda things for sure!
Jan
14
comment CentOS openLDAP cert trust issues
I'm not getting into a pissing contest with a hot headed writer on the Internet. But if you're only pushing a gig per second and running 100-500 hosts I really don't see the issue here. Sure TLS does require more CPU load but there are ways to optimize this and restructure the network (sounds like this might be needed anyway if the marginal overhead from TLS affects it this much). It is also not forced upon you, go with a less secure library than sssd for instance.
Jan
12
comment CentOS openLDAP cert trust issues
I wouldn't say it's a useless feature. You avoid internal eaves dropping for one. You avoid appliances to be able to tap into traffic where you don't want it to. There's a number of reasons why this isn't useless.
Jan
11
revised pkcs11_lib - NSS Initialize Failed (bad database?)
added 115 characters in body
Jan
11
answered pkcs11_lib - NSS Initialize Failed (bad database?)
Jan
11
asked pkcs11_lib - NSS Initialize Failed (bad database?)
Jan
10
answered Need to allow unsigned msi to install
Oct
10
awarded  Famous Question
Oct
5
awarded  Teacher
May
8
awarded  Popular Question
Sep
24
awarded  Autobiographer
Jul
27
awarded  Tumbleweed