This is a bit if a pain. The challenge is that we'll need to develop a solution that's relatively easy to backport to older versions of satchmo. Fortunately it shouldn't be too hard but it is extra work.
I've opened ticket #748 to track the progress. I don't know a whole lot about these different implementations so if anyone has experience with any of these libraries feel free to chime in and make a recommendation. -Chris On Tue, Feb 17, 2009 at 2:56 PM, Bruce Kroeze <[email protected]> wrote: > On Tue, Feb 17, 2009 at 12:33 PM, basslineshift > <[email protected]>wrote: > >> >> Dear Authorize.Net Developer: >> >> During the week of March 16 - 20, 2009, Authorize.Net will be >> deprecating all legacy support for the SSL 2.0 protocol. Changes have >> recently been made to the Payment Card Industry Data Security Standard >> (PCI DSS) which have made the use of SSL 2.0 a PCI DSS violation. >> >> Due to this change, it is critical that you update any applications or >> integrations that may be using the SSL 2.0 protocol to support the >> more current SSL 3.0/TLS 1.0 protocols. Failure to upgrade your >> applications or integrations may result in a lost ability to >> successfully process transactions via the Authorize.Net Payment >> Gateway. >> > > Unfortunately, it looks like it will. We'll have to use something like TLS > Lite or M2Crypto to talk to Auth.net servers. At least, that's what I think > based on some googling about python's built-in urllib2. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
