Extension Signing
-
Unless they haven't told us developers ??
The signing process is meant to 'hash' the contents of the following [initial] file-types:
rb
rbs
rbe
js
htm
html
css
[Until representations were made at the outset of v2016, only rb* files were being hashed and other potentially malicious file-types could slip through...]
Other file-types in the subfolder should be ignored.
Also any new file-types [including those like the initially-hashed ones] which are added into the subfolder 'post-signing' should be ignored ??Someone at Trimble like to comment...
Any more onerous changes have not been well explained
PS: Of course you can also write files into a Temp folder...
-
The signing process appears to be hashing my log files (.txt)
-
Well, then do not put them into the package until after signing ?
Or save your logs in a version independent folder like:
"%APPDATA%/Medeek/SketchUp/TrussPlugin" -
The signing shouldn't be including your .txt files. Can you send me an example?
In general I'd recommend you thread the Plugins folder like Windows' Program Files folder. If you have configuration files etc save them to the user's AppData. The extension update mechanism remove the old extension before copying over the new files. So that would also be an issue for you.
-
The plugin in question right now is my Medeek Truss Plugin. You can download it here:
http://design.medeek.com/calculator/sketchup/medeek_truss_ext.rbz
-
I heard from one of my coworkers that there appear to be an issue there the signing/uploading can fail at times when there are higher volume of traffic. I experienced this myself today when I tried to upload. At first I was getting just errors, but when I tried later with the same RBZ it worked fine.
A fix is being worked on.
-
It took me about 15 tries before I got it to take the other night. Hopefully there is a resolution since this becomes annoying very quickly. It does not seem to be dependent on the encryption type selected.
-
We think we have the cause identified.
-
Ugh... I'm suffering from this myself right now.
-
I have had this in beta and have reported it. My solution was to use a different browser then Firefox. Unfortunately even Edge was failing sometimes.
It doesn't matter what is the content of rbz file. The signing fails even with the simplest rbz you can think of. -
I'm not glad it is failing but I am glad that others have identified the issue and it is just not me going crazy or trying to submit flawed .rbz files. Thank-you for looking into this and working on a resolution.
-
We rolled out a patch we think should fix this issue.
-
@thomthom said:
We rolled out a patch we think should fix this issue.
Thanks. I confirm that the fix works for me. I can sign a plugin using Google account from Firefox without a problem.
-
Its working great now, I'm using Chrome as my browser and zipping the files with Windows 7.
Advertisement