[SOLVED] Security Risk for Expired Memberships?

I hate to be redundant as I could swear I've asked this question a few years back, but don't see it in my topics or also by searching the forums...

I believe different extension developers handle this differently, so I'm just looking for some clarity.

I think I seen somewhere that once the Joomlapolis membership is expired, upgrades/updates are no longer available. I'm just wondering if that applies to security updates/patches also. I just need to warn my client if they're going to need membership indefinitely in order to keep their site secure and immune to future security vulnerabilities that could arise.

If your subscription expires you will no longer be able to download updates of any kind. This includes bug fixes, feature implementations, security fixes (depending on the issue we may make an exception), etc.. Core CB it self is of course free and always available for download regardless of your subscription.

Oh, that's right... I always forget that the core component is free as I always buy a membership when I use it for a new client in order to get the newest extensions. So there shouldn't every really be a security issue unless it pertains to the plugins. Is there a way to stay informed on that, by the way? I don't think plugins show up on the updates section of Joomla - just in the plugins manager of CB [I believe]. Or maybe just keeping up on your newsletters would keep me informed of such (I'm subscribed). I'm usually not quite this concerned but this particular client that's going to be using your component has to keep government documents secure - and in a secure system. I'm also sure, as soon as their business takes off, that they'll be more than happy to keep their membership 'alive' and constantly updated indefinitely.

Our newsletter and frontpage is used to announce new milestone releases. If we ever have a security release we'll also announce it. We'll eventually have a new site launched with update package builder and that'll keep the version checking in CB > Plugin Management up to date. In addition to that we plan to implement a web store for easy download and install of plugins directly from CB backend (requires new JP site and rewrite of our package builder first).

Good enough for me. Thanks again for taking the time to explain.