DynamicPaintbrush now available

As of today (1/24/25), the recompiled update still doesn't seem to be available. Am I missing something or is RBA behind schedule on this?

Kevin
 
A few days ago I got this message from RBA in Facebook:
I'm waiting on the PixInsight folks to add a new developer key to the PixInsight app. Once they do that and release an update, I'll be able to make the module available. I'll let you know here.

I'm not sure what he's referring to with "PixInsight folks" adding and releasing an update. I don't see that happening and it shouldn't be necessary since others were able to update their plugins without it.

It is now the last week of January 2025, so we'll see if we get the update this week or not.

Lamar
 
that’s a legitimate thing. modules have to be signed now and for that to work the pi application needs to be aware of the developer's signature. other devs just applied for and got their signatures before the 1.9 series was released. @lmclouth
 
pfile said:
that’s a legitimate thing. modules have to be signed now and for that to work the pi application needs to be aware of the developer's signature. other devs just applied for and got their signatures before the 1.9 series was released. @lmclouth
Click to expand...
Yes, but earlier he said he had already applied for this and had it. But just was not at home able to re-compile his module.
In fact it was on Jan 4, 2025 that he sent an email out saying he had the signature file and gave the link of where to download it. But the module itself was not going to be updated until later (when he returned home.) That is now supposed to be happening sometime this week.
 
lmclouth said:
Yes, but earlier he said he had already applied for this and had it. But just was not at home able to re-compile his module.
In fact it was on Jan 4, 2025 that he sent an email out saying he had the signature file and gave the link of where to download it. But the module itself was not going to be updated until later (when he returned home.) That is now supposed to be happening sometime this week.
Click to expand...

he might have his copy of the signing key but the app itself has to have the public key embedded in it to check the signature.

that’s just how public key encryption works. no way around it.

rob
 
Here's the latest from RBA.

I asked him:
"It's now the first week of February, do you have an update?"

And he replied:
"I requested that my signature is added to PixInsight about 10 days ago, and I wrote to them today again. The moment they release an update to PixInsight, I will release an update with the signature and it will work, but until then, we have to wait for the update, and that's beyond my control. I hope they do one this week."

I don't see how this can be correct -- It makes no sense that PixInsight would have to release an update just so his module would work. If such was the case, they would be releasing a bunch of updates for all of these modules that use this new signature scheme.

But anyway, I guess we just have to keep waiting. :(
 
lmclouth said:
I don't see how this can be correct -- It makes no sense that PixInsight would have to release an update just so his module would work. If such was the case, they would be releasing a bunch of updates for all of these modules that use this new signature scheme.
Click to expand...

please read what i wrote again. every developer has a public/private key pair. if a new developer appears, pixinsight needs to add the signature to the public database. once the key pair exists, as long as it is not revoked, it should continue to be valid and the modules should load and run fine.

RBA never had a signature. up until 1.8.9, you didn’t need one. but other 3rd party developers applied for them before 1.9.x made them mandatory. that’s why you didn’t notice.

all other 3rd party modules that exist in PI at the moment are already in the database! this is why there is no stampede.

you’re trying to find a conspiracy where there is none. the only thing you can accuse RBA of is not squaring this away before module signatures became necessary.

rob
 
pfile said:
please read what i wrote again. every developer has a public/private key pair. if a new developer appears, pixinsight needs to add the signature to the public database. once the key pair exists, as long as it is not revoked, it should continue to be valid and the modules should load and run fine.

RBA never had a signature. up until 1.8.9, you didn’t need one. but other 3rd party developers applied for them before 1.9.x made them mandatory. that’s why you didn’t notice.

all other 3rd party modules that exist in PI at the moment are already in the database! this is why there is no stampede.

you’re trying to find a conspiracy where there is none. the only thing you can accuse RBA of is not squaring this away before module signatures became necessary.

rob
Click to expand...
Yes I understand about public/private keys, I'm a retired Sr. Software Engineer.

What I find disturbing is that if you are requiring keys and signatures for modules, you should at least update the public database more often. It has been about 6 weeks and still waiting for PixInsight to update this public database so we can finally use a module that we paid for long ago.

Yes, RBA should have requested the signature info earlier but according to him, he was not notified that he needed one before 1.9 was going to be released.
And if it takes this long to get the public database updated it really discourages developers to create modules for PixInsight since they can't get it out to the users in a timely manner.
 
lmclouth said:
Yes I understand about public/private keys, I'm a retired Sr. Software Engineer.
Click to expand...

well then i’m not sure why all the noise then.

we can’t do anything about juan’s key distribution methodology or how he interacts with developers. it’s his way or the highway. i agree that there is ample room for improvement.

rob
 
lmclouth said:
Yes, RBA should have requested the signature info earlier but according to him, he was not notified that he needed one before 1.9 was going to be released.
And if it takes this long to get the public database updated it really discourages developers to create modules for PixInsight since they can't get it out to the users in a timely manner.
Click to expand...
See this post from April 2024. I think it has been clear for a long time that signatures would be required.
 
Just opened PixInsight and was prompted to update. The update was an updated signature for RBA. I don't know much about this stuff, but that sounds to me like what RBA has been waiting for.
 
Here is the latest update from RBA's website:
A new DynamicPaintbrush version that will be compatible with the latest PixInsight v1.9.x releases will be released the moment we work out some problems with the PixInsight team, with whom I am actively talking with, daily. When that happens, hopefully before mid February, this page will be properly updated.
Click to expand...
 
You must log in or register to reply here.
Back
Top