All,

 

We are making a change in the next release and getting rid of the “—no-check-certificate” option to wget in the plugin download function.  This is because we have a valid SSL cert and we want it checked when someone downloads unraid.  For those plugins that bring code from non-trusted source, they will need to put that switch on the URL inside the plugin.

 

Wanted to alert you all to this ahead of time.

Your anticipation stretches a long way. Next version would be 14C, so 14D is also (already) in the pipeline 

Your anticipation stretches a long way. Next version would be 14C, so 14D is also (already) in the pipeline 

Already running a 14c internally, so might just name the next one d or even 15. Forget the designation. In the next public release this will take affect ;-)

My opinion is just do it regardless and we can fix whatever breaks. The "no cert thing" is a hangover for old v5 days and is a  practice we should have dropped ages ago.

 

The one thing it does mean though is that we need to be updating ca-cert in line with upstream. I dont think this is common but it is not rare either.

is this referring to this line of code:

 

<!ENTITY pluginURL "https://github.com/PhAzE-Variance/unRAID/raw/master/Plugins/Couchpotato.plg">

 

changes to:

 

<!ENTITY pluginURL "--no-check-certificate https://github.com/PhAzE-Variance/unRAID/raw/master/Plugins/Couchpotato.plg">

 

so it will still download from github (which is still an untrusted source)?  Is there any issue with adding that to plugins now or will it break downloading on current betas?

is this referring to this line of code:

 

<!ENTITY pluginURL "https://github.com/PhAzE-Variance/unRAID/raw/master/Plugins/Couchpotato.plg">

 

changes to:

 

<!ENTITY pluginURL "--no-check-certificate https://github.com/PhAzE-Variance/unRAID/raw/master/Plugins/Couchpotato.plg">

 

so it will still download from github (which is still an untrusted source)?  Is there any issue with adding that to plugins now or will it break downloading on current betas?

 

No it refers to URL downloads, eg.

 

<FILE Name="/boot/config/plugins/&name;/&name;-&version;.txz" Run="upgradepkg --install-new">

<URL>https://raw.github.com/bergware/dynamix/master/archive/&name;-&version;.txz</URL>

</FILE>

 

becomes

 

<FILE Name="/boot/config/plugins/&name;/&name;-&version;.txz" Run="upgradepkg --install-new">

<URL>--no-check-certificate https://raw.github.com/bergware/dynamix/master/archive/&name;-&version;.txz</URL>

</FILE>

 

Oh, my old plugins had the no check in there but my new plugins don't use that command to download anymore. Kewl

--no-check-certificate is to be dropped not added

 

It has not been needed since the very early days of v6 beta anyway

Is there a comprehensive guide for plugin design for the new v6 plugin system?

 

I have developed a virtualbox plugin that needs to be adapted from v5 plugin architecture.

 

Is there a recommended plugin template or example that I can rely on for the changes?

 

Is there a comprehensive guide for plugin design for the new v6 plugin system?

 

I have developed a virtualbox plugin that needs to be adapted from v5 plugin architecture.

 

Is there a recommended plugin template or example that I can rely on for the changes?

The only thing I've seen is this thread.