Of course, publishing only RBE means the extension won't work in anything other than >=v2016 !Īlso, if the signed RBZ includes encrypted files, then it may currently not be exempt from malicious tampering ! ill-advisedly shipping them together means any 'hacker' can easily see inside the RBS anyway, and compromise the RBE's encryption. Īlso the signer perversely allows the author to add both types of encrypted files into the same signed RBZ - although RBS works in ALL SketchUp versions anyway and publishing in RBE only protects the author's IP when there is no RBS version out there. The new signer does not allow a mixture of RB and encrypted files. RBS or RBE - because only unencrypted RB files will work. it does not include a file-type suffix, and IF the author chooses any encryption at all - i.e. RB files in the subfolder will find it works, but making the RBZ with them included and then signing it, will then fail unless the specified loader path is left 'open ended' - i.e. This is a typical error caused by the new and unfortunately half-baked v2016 signing process which has been introduced.Īn author testing his code with all. So it must be done by the author and re-signed. So v2016 won't like it unless it's running in 'Unrestricted' mode. It will work - however, editing this file manually breaks the signing hash! If the base-level 's4u_makeface.rb' were to say: There are two files added by the signing process: The base-level 's4u_makeface.rb' which sets up the extension has a path set for the extension's loader to be: The author needs to change his files and remake the RBZ and get it re-signed/republished.
0 kommentar(er)
