Has the core not been upgraded?

On Thu, Oct 30, 2014 at 2:50 PM, Pat David wrote:

https://www.drupal.org/SA-CORE-2014-005

I am wondering if registry.gimp.org should be updated and/or taken offline until an upgrade or alternate solution is in place?

-- pat david
http://blog.patdavid.net
_______________________________________________ gimp-web-list mailing list
gimp-web-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-web-list

Everybody is still welcome to contribute here: http://gimper.net/resources/categories/plugins.1/

Pat David wrote:

https://www.drupal.org/SA-CORE-2014-005

I am wondering if registry.gimp.org should be updated and/or taken offline until an upgrade or alternate solution is in place?

On Sat, Nov 1, 2014 at 12:33 AM, GIMPER wrote:

Everybody is still welcome to contribute here: http://gimper.net/resources/categories/plugins.1/

What does this have to do with the Drupal security vulnerability? I'm not against promoting GIMPer, nor their plug-in registry replacement as it appears in that link, but please don't drive a thread off topic. Feel free to start a separate thread in the future.

SAM

I prefer to encrypt my email

GPG FINGERPRINT 4096 KEY
8D8B F0E2 42D8 A068 572E
BF3C E8F7 3234 7257 E65F
https://keybase.io/samrocketman

Learn how to encrypt your email with the Email Self Defense guide:
https://emailselfdefense.fsf.org/en/

Hi Pat, and all,

thanks for understanding :-)

Regarding a static site, I'm not entirely sure Drupal can be mirrored easily, but I've started a mirroring process and will have a look at the result tomorrow (it's taking a while...). I'll keep you posted.

cheers

On Thu, Nov 13, 2014 at 6:15 PM, Pat David wrote:

Hi Ingo!

I'm CC'ing the list as your email came in off-list.

I completely understand, and was somewhat aware that you were winding things down. :)

At the moment, I was wondering if there would be a way to 'freeze' the current state of the registry as a static site, and to leave it in place for the time being? This way the registry itself can stay online (though not-functional for dynamic use), until we can find a new home/leader/implementation that makes the most sense moving forward.

I know there was some discussion around how best to utilize it moving forward, and I have some thoughts around this that I'll detail in a later email.

For now, I will go investigate what might be required to generate a static site to de-couple the registry from Drupal so we can avoid any issues with vulnerabilities for the time being.

Oh, and thank you, thank you, thank you for maintaining it for so long! :)

pat

On Thu Nov 13 2014 at 11:09:28 AM Ingo Lütkebohle wrote:

Hi,

unfortunately this is not fixed, yet.

As many if you know, I no longer have time to maintain the registry. For a while I was content in just letting it run, but with security problems such as this one, I am uncomfortable doing so any longer.

If a responsible someone else (or a group) could host and maintain the site, I'd be happy to hand it over. Alternatively, I could also give someone just the plugin files and meta-data, for import into another site.

If nobody steps up within the next few weeks, I think I will have to shut it down, as sad as that would make me. I would keep the data around for later recovery, however.

Best Regards,

Ingo Am 30.10.2014 20:51 schrieb "Pat David" :

https://www.drupal.org/SA-CORE-2014-005

I am wondering if registry.gimp.org should be updated and/or taken offline
until an upgrade or alternate solution is in place?

-- pat david
http://blog.patdavid.net

_______________________________________________

gimp-web-list mailing list
gimp-web-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-web-list

Ingo Lütkebohle, Dr.-Ing.

PGP Fingerprint 3187 4DEC 47E6 1B1E 6F4F  57D4 CD90 C164 34AD CE5B