Beta v7.1.1

[MichaIng]

Beta v7.1.1

(2021-04-25)

Changes (since v7.1.0)

• DietPi-Software | Kodi: Worked around an issue on 64-bit RPi systems, where the wrong Kodi package is tried to be installed, causing an APT failure. Many thanks to @mmnpkf for reporting this issue: DietPi-Software | Kodi: Apply workaround for missing RPi 64-bit package #4194
• DietPi-Software | Chromium: Worked around an issue on 64-bit RPi systems, where the install failed, as The Raspberry Pi repository does not ship a 64-bit build yet. The Chromium package from the Debian repository is now installed instead.

[MichaIng]

One more thing I want to do is migrating OpenBazaar from global GOPATH install to module-style install, since future Go versions might not support to install 3rd party Go software via go get on a global GOPATH level anymore. I.e. GO111MODULE, which already defaults to no since Go v1.16 might not be used anymore with Go v1.17.

I'll see if I can do that tomorrow, otherwise it is not a blocker task, since next DietPi release is scheduled for May 29 already, which should be early enough to migrate to the future-prove module-style install method.

[Joulinar]

Do we have a release schedule now 👀

[MichaIng]

Yes, I think regular releases are more important than trying to finish a certain list of planned changes. Usually things take longer than expected and when dealing with 190 software options, regularly an implementation requires an update to keep up with upstream, which should not take unnecessary long, especially when installs are broken completely or APT keys expired and such.

This also means that I'll remove most issues from milestones and only add those where I'm sure that I will implement them or if someone else did start to work on them.

[Joulinar]

Ok so we are becoming agile and going into smaller sprints. 🤣

[Joulinar]

@MichaIng
not sure if dietpi-vpn is working correctly now. I tested on v7.1.1 and if I select Custom on the initial screen, I get straight to the VPN status overview. (including a NordVPN Subscription information)

Before I was getting the explorer to be able to select the configuration file. For this I need to select Provider : [Custom] > Custom again now.

One more strange thing. If I leave dietpi-vpn, I will get following CLI root@DietPi3:~# directory....

[MichaIng]

Yeah, the NordVPN subscription URL is an affiliate link to their permanent 2-3 years 68%-70% off offer. I have to check back with Dan about the status of this.
Mid-term we should create (new) affiliate subscription URLs for all selectable providers and make it transparent as well that this is a way to support DietPi.

Testing DietPi-VPN:

• First access: OpenVPN is installed, provider selection appears
• 🈴 Selecting "Custom" applies choice directly. Hmm...

[Joulinar]

at least I would not expect to see a NordVPN subscription information if I select custom. Maybe my expectations is different than it was intended 🤣

[MichaIng]

It was simply forgotten to be changed/shown conditionally. I'll change it so that it's only shown when NordVPN provider has been selected.

[MichaIng]

Done: 4904995

[Joulinar]

one more thing. I created a PiVPN server and copied the created conf file over to the testing system. On dietpi-vpn I selected the conf file. So far so good. However it seems I'm forced to enter user + pw even if not required. Furthermore PiVPN created the conf file password protected. But there is no possibility to enter this pw. Therefore connection is failing

[  OK  ] DietPi-VPN | systemctl restart dietpi-vpn
[.     ] DietPi-VPN | Waiting for connection (1/20)
Broadcast message from root@DietPi3 (Sun 2021-04-25 14:43:25 CEST):

Password entry required for 'Enter Private Key Password:' (PID 2488).
Please enter password with the systemd-tty-ask-password-agent tool:

[FAILED] DietPi-VPN | Connection failed/timeout: dietpi4.lan
[   .. ]Enter Private Key Password:  dietpi-vpn
[  OK  ] DietPi-VPN | systemctl stop dietpi-vpn

[MichaIng]

That is a limitation we need to have a look into for next release I think. Interactive input breaks automated connection at boot and requires some more changes. For now it works with all public VPN providers I know, which use user/password authentication applied via OVPN config or dedicated credentials file for unattended connection.

The cases with key authentication are:

• Key authentication in general, which can be unattended as well with an unprotected key. That key is part of the OVPN config, isn't it?
• Key authentication with password-protected key. In theory it should be possible to enter the password once and have the key decrypted and unprotected from then on, but better in a dedicated file. Not sure whether it's possible to have the key protected and it's password in a dedicated file? Otherwise we'd need to disable the autostart feature when the key stays password-protected without password file.

[Joulinar]

Ok at least something to keep in mind if we have users reporting on it. Maybe it's a rarely used case and not a real issue. We will see 😃

[Joulinar]

did a test on dietpi-ddns with DuckDNS.

First I get ask for the Token

and afterwards to enter the new password again

I would expect to get ask to enter the Token again 😉

---

EDIT
did a test with custom DDNS provider ddnss.de. So far it is working. But the DDNS update test feedback seems to be interesting

┌───────────────────────────────────────────────────┤ DietPi-DDNS ├─────
│ DDNS update test succeeded:                                           
│ <head>                                                                
│ <meta name="robots" content="noindex">                                
│ <title>DDNSS - Kostenloser DynDNS Service : Re-ProutDNS v5.01v</title>
│ </head>                                                               
│ <body>                                                                
│ <p><font face="Verdana" size="2"></font></p>                          
│ <p><font face="Verdana" size="2">Updated 1 hostname.</font></p>       
│ </body>                                                               

[MichaIng]

I would expect to get ask to enter the Token again 😉

Ah dammit, that's the way G_WHIP_PASSWORD works, that second text cannot be changed currently. There was never the case the some sort of hidden key was not named "password". I'll think about it, probably adding a way to replace the word, as it is done in DietPi-DDNS itself, is required. Or changing it to something more generic, like "Please confirm the last input"?

feedback seems to be interesting

My custom provider also has a <br> tag in it's output 😄. We should talk to those providers and convince them them nobody is opening the update URL in a browser that interprets HTML, aside of for testing reasons, and that they hence should switch to a short plain text output 😄. But even that it looks strange, I think we need to keep it. Sometimes providers return a valid 200 response with a message that the update failed. Especially for custom providers this is important information to debug the case that the test succeeds (no error code) while the domain was not updated.