Done!
Hi Tim,
Apologies for the delay on this. Sadly, and also ironically, for you, the
muppet who didn’t get round to setting up a repo and doing the release is also
the PAUSE admin responsible for indexing permission changes.
I’ll give you co-maint on all the packages in the Net-SAML2 distribution
HI, I am withdrawing this request.
On Tue, Feb 28, 2017 at 12:40 PM, Jeff Fearn wrote:
> Hi Chris, and modules list, Net::SAML2 is about to stop function as it
> only supports SHA1 certificates and modern SSL libraries block weak
> certificates. I have a github repo [1] with some community [2] an
Hi,
Apologies for the lack of communication on this - I'm now two acquisitions away
from the company where I originally wrote this code, which makes it harder to
just say yes, go for it.
I'm trying find out whether we are OK to simply add a co-maint, or whether we
need to do something more fo
Hi Chris!
> Apologies for the lack of communication on this - I'm now two acquisitions
> away from the company where I originally wrote this code, which makes it
> harder to just say yes, go for it.
>
> I'm trying find out whether we are OK to simply add a co-maint, or whether we
> need to do
> Are you happy for Jeff to have co-maint, so we can get some releases of
> Net-SAML2 done? If so, I’m happy to make the permission changes on your
> behalf.
Another idea: we could set up a github group, and switch to a team model, as I
know there are a few other people relying on this distribu
Hi Chris,
I’m one of the PAUSE admins
Last month, Jeff Fearn (pause id JFEARN) asked:
> Net::SAML2 is about to stop function as it
> only supports SHA1 certificates and modern SSL libraries block weak
> certificates. I have a github repo [1] with some community [2] and
> personal fixes to address
Hi Jeff
Have you been in contact with Chris? There's no indication in your email
to the modules list tells us how much effort you've put into getting
assistance directly from Chris.
--
Ron Savage - savage.net.au
Hi Chris, and modules list, Net::SAML2 is about to stop function as it
only supports SHA1 certificates and modern SSL libraries block weak
certificates. I have a github repo [1] with some community [2] and
personal fixes to address this and some other fixes, which I'd like to
ship.
Would it be pos
