Re: [WebDNA] TLS 1.2 and [tcpconnect]

This WebDNA talk-list message is from

2018


It keeps the original formatting.
numero = 113998
interpreted = N
texte = 1598 --Apple-Mail-6A31ED0B-9FD0-43B4-A5CB-0885C3E4B88A Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable That only works for incoming connection that will not work for an outgoing c= onnection Robert Minor Cybermill.com 314-962-4024 ext 500 > On Mar 1, 2018, at 09:58, Brian Willson wrote: >=20 > Hi, Jym. >=20 > I=E2=80=99m trying to figure out the answer to your [tcpconnect] question.= >=20 > But I can confirm that older TLS protocols can be turned off. In fact, I h= ad to do this with Mac OS X Server v.5.1.5 -- which, short-sightedly, I thou= ght was all I had to do -- because it still supports TLS 1 and TLS 1.1, as w= ell as TLS 1.2. >=20 > (OS X Server v5.3.1 uses TLS 1.2 by default, FWIW.) >=20 > Brian >=20 > --- > Brian Willson > www.3ip.com >=20 >=20 >> On Mar 1, 2018, at 9:28 AM, Jym Duane wrote: >>=20 >> Robert >>=20 >> I am in the process (expense) of moving a site to an updated server, in o= rder to have TLS1.2 to do the tcp connect. >>=20 >> this sounds like after i do that i wont be able to still? is that due to w= ebdna? >>=20 >> will be updated to latest centos and Apache to support the TLS1.2 >>=20 >> have not got completely there yet to try it. >>=20 >> Please send script as a workaround either while transitioning or after if= needed would be greatly appreciated. >>=20 >> PS- i think older protocols can be tuned off on the server? >>=20 >> Jym >>=20 >>=20 >>> On 3/1/2018 6:12 AM, Bob Minor wrote: >>> No not at all. I can send you the php script or you can do the same thin= g with webdna on a newer server >>>=20 >>> All I really do is read the post variables and resend them to authnet as= another tcpconnect so to speak. But this would be running on an updated ser= ver.=20 >>>=20 >>> Robert Minor >>> Cybermill.com >>> 314-962-4024 ext 500 >>>=20 >>> On Mar 1, 2018, at 07:52, Brian Willson wrote: >>>=20 >>>> Yikes. Sounds complicated. >>>>=20 >>>> Is there no way to tweak the [tcpconnect] script to accom= modate TLS 1.2 and/or its ciphers? If not, that would prove a major setback h= ere. >>>>=20 >>>> Brian >>>>=20 >>>> --- >>>> Brian Willson >>>> www.3ip.com >>>>=20 >>>>=20 >>>>> On Mar 1, 2018, at 7:42 AM, Bob Minor wrote:= >>>>>=20 >>>>> I got around it by running my own Linux server that does the php call t= o authnet and dumps the data just as the gateway did. kinda like a gateway f= or my gateway.=20 >>>>>=20 >>>>> Robert Minor >>>>> Cybermill.com >>>>> 314-962-4024 ext 500 >>>>>=20 >>>>> On Mar 1, 2018, at 06:34, Brian Willson wrote: >>>>>=20 >>>>>> Hey, everybody. >>>>>>=20 >>>>>> For years I=E2=80=99ve been using [tcpconnect] to connect my online s= hopping carts with Authorize.net=E2=80=99s AIM solution, and it=E2=80=99s wo= rked great, with only a minor tweak or two required. >>>>>>=20 >>>>>> Yesterday, Authorize.net began requiring connections via the TLS 1.2 p= rotocol, and my script broke. I.e., it can no longer connect to the endpoint= .. >>>>>>=20 >>>>>> (I'd mistakenly assumed all I needed to do was make sure my server su= pported TLS 1.2, duh.) >>>>>>=20 >>>>>> Can anyone tell me how to make sure my script forces a connection via= TLS 1.2? >>>>>>=20 >>>>>> I was hoping all I=E2=80=99d need is a tweak to this line... >>>>>>=20 >>>>>> [text show=3DF]response=3D[tcpconnect host=3Dsecure2.authorize.net= &port=3D443&ssl=3DT] >>>>>>=20 >>>>>> ...but simply using =E2=80=9Cssl=3DF=E2=80=9D didn=E2=80=99t work, ha= .. >>>>>>=20 >>>>>> Here=E2=80=99s my main connect code: >>>>>>=20 >>>>>> --- >>>>>>=20 >>>>>> [text show=3DF]response=3D[tcpconnect host=3Dsecure2.authorize.net&po= rt=3D443&ssl=3DT][!] >>>>>>=20 >>>>>> [/!][tcpsend]POST /gateway/transact.dll = HTTP/1.0[crlf][!] >>>>>>=20 >>>>>> [/!]User-Agent: e3IP[crlf][!] >>>>>>=20 >>>>>> [/!]Host: secure2.authorize.net:443[crlf][!] >>>>>>=20 >>>>>> [/!]Content-type: application/x-www-form-urlencoded[crlf][!] >>>>>>=20 >>>>>> [/!]Content-length: [countchars][content][/countchars][crlf][!] >>>>>>=20 >>>>>> [/!][crlf][!] >>>>>>=20 >>>>>> [/!][content][crlf][!] >>>>>>=20 >>>>>> [/!][/tcpsend][/tcpconnect][/text] >>>>>>=20 >>>>>> --- >>>>>>=20 >>>>>> Thanks so much in advance for any help you can offer. >>>>>>=20 >>>>>> Brian >>>>>>=20 >>>>>> --- >>>>>> Brian Willson >>>>>> www.3ip.com >>>>>>=20 >>>>>> --------------------------------------------------------- This messag= e is sent to you because you are subscribed to the mailing list talk@webdna.= us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webd= na.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>>>> --------------------------------------------------------- This message= is sent to you because you are subscribed to the mailing list talk@webdna.u= s To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdn= a.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>>>=20 >>>> --------------------------------------------------------- This message i= s sent to you because you are subscribed to the mailing list talk@webdna.us T= o unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.u= s/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>> --------------------------------------------------------- This message i= s sent to you because you are subscribed to the mailing list talk@webdna.us T= o unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.u= s/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>=20 >> --=20 >> Jym Duane - CTO - Purpose Media >> Creating Your Success Story >> Marketing : Television - Internet -Print >> Phone: (877) 443-1323 >> Email: jym@purposemedia.com >> Web: www.purposemedia.com >>=20 >> Oregon - www.GuideToOregon.com >> PO Box 1725, Jacksonville, OR 97530 >>=20 >> California - www.OrangeCounty.net >> PO Box 2025, Capistrano Beach, CA 92624=20 >> --------------------------------------------------------- This message is= sent to you because you are subscribed to the mailing list talk@webdna.us T= o unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.u= s/page.dna?numero=3D55 Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- This message is s= ent to you because you are subscribed to the mailing list talk@webdna.us To u= nsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/p= age.dna?numero=3D55 Bug Reporting: support@webdna.us --Apple-Mail-6A31ED0B-9FD0-43B4-A5CB-0885C3E4B88A Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable That only works for incoming connection tha= t will not work for an outgoing connection

Robert M= inor
314-962-4024 ext 500

On Mar 1, 2018, at 09:58, Brian Willson <willson@3ip.com> wrote:

Hi, Jym.

I=E2=80=99m trying to figure out the answer to your [tcpconnect] qu= estion.

But I can c= onfirm that older TLS protocols can be turned off. In fact, I had to do this= with Mac OS X Server v.5.1.5 -- which, short-sightedly, I thought was all I= had to do -- because it still supports TLS 1 and TLS 1.1, as well as TLS 1.= 2.

(OS X Server v5= ..3.1 uses TLS 1.2 by default, FWIW.)

Brian

---
Brian Willson
www.3ip.com


On Mar 1, 2018, at 9:28 AM, Jym Duane <jym@purposemedia.com> wrote:

=20 =20

Robert

I am in the proces= s (expense) of moving a site  to an updated server, in order to have TLS1.2 to do the tcp connect.

this sounds like after i do that i wont be able to still? is that due to webdna?

will be updated to latest centos and Apache to support the TLS1.2

have not got compl= etely there yet to try it.

Please send script as a workaround either while transitioning or after if needed would be greatly appreciated.

PS- i think older protocols can be tuned off on the server?

Jym


On 3/1/2018 6:12 AM, Bob Minor wrote:
No not at all. I can send you the php script or you can do the same thing with webdna on a newer server

All I really do is read the post variables and resend t= hem to authnet as another tcpconnect so to speak. But this would be running on an updated server. 

Robert Minor
314-962-4024 ext 500

On Mar 1, 2018, at 07:52, Brian Willson <willson@3ip.com> wrote:

Yikes. Sounds complicated.

Is there no way to tweak the [tcpconnect] script to accommodate TLS 1.2 and/or its ciphers? If not, that would prove a major setback here.

Brian

---
Brian Willson


On Mar 1, 2018, at 7:42 AM, Bob Minor <bob.minor@cybermill.com> wrote:

I got around it by running my own Linux server that does the php call to authnet and dumps the data just as the gateway did. kinda like a gateway for my gateway. 

Hey, everybody.

For years I=E2=80=99ve been usin= g [tcpconnect] to connect my online shopping carts with Authorize.net=E2=80=99s AIM solution, and it=E2=80=99s worked great, w= ith only a minor tweak or two required.

Yesterday, Authorize.net bega= n requiring connections via the TLS 1.2 protocol, and my script broke. I.e., it can no longer connect to the endpoint.

(I'd mistakenly assumed all I needed to do was make sure my server supported TLS 1.2, duh.)

Can anyone tell me how to make sure my script forces a connection via TLS 1.2?

I was hoping all I=E2=80=99d nee= d is a tweak to this line...

   [text show=3DF]response=3D[tcpconnect host=3Dse= cure2.authorize.net&port=3D443&ssl=3DT]

...but simply using =E2=80=9Cs= sl=3DF=E2=80=9D didn=E2=80=99t work, ha.

Here=E2=80=99s my main connect= code:

---

[text show=3DF]response=3D[tcpconnect host=3Dse= cure2.authorize.net&port=3D443&ssl=3DT][!]

[/!][tcpsend]POST /gateway/transact.dll HTTP/1.0[crlf][!]

[/!]User-Agent: e3IP[crlf][!]

[/!]Host: secure2.auth= orize.net:443[crlf][!]

[/!]Content-type: application/x-www-form-urlencoded[crlf][!]=

[/!]Content-length: [countchars][content][/countchars][crlf][!= ]

[/!][crlf][!]

[/!][content][crlf][!]
=

[/!][/tcpsend][/tcpconnect][= /text]

---

Thanks so much in advance for any help you can offer.

Brian

---
Brian Willson
www.3ip.com

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us<= /a> archives: http://www.webdna.us/pag= e.dna?numero=3D55 Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?= numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55= Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

--=20Jym Duane - CTO - Purpose MediaCreating Your Success StoryMarketing : Television - Internet -PrintPhone: (877) 443-1323Email: jym@purposemedia.comWeb: www.purposemedia.comOregon - www.GuideToOregon.comPO Box 1725,  Jacksonville, OR 97530California - www.OrangeCounty.netPO Box 2025,  Capistrano Beach, CA 92624 
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us= To unsubscribe, E-mail to: talk-leave@webdna.us archives: h= ttp://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdn= a.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leav= e@webdna.us archives: http://www.w= ebdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us= --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --Apple-Mail-6A31ED0B-9FD0-43B4-A5CB-0885C3E4B88A-- . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
  2. Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
  3. Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
  4. Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
  5. Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
  6. Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
  7. Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Diane Blackmore 2018)
  8. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Diane Blackmore 2018)
  9. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Tom Duke 2018)
  10. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Diane Blackmore 2018)
  11. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Stuart Tremain 2018)
  12. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
  13. [WebDNA] TLS 1.2 and [tcpconnect] (Bob Knight 2018)
  14. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  15. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  16. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
  17. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  18. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
  19. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  20. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
  21. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  22. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  23. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  24. Re: [WebDNA] TLS 1.2 and [tcpconnect] (christophe.billiottet@webdna.us 2018)
  25. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  26. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  27. Re: [WebDNA] TLS 1.2 and [tcpconnect] (dbrooke@euca.us 2018)
  28. Re: [WebDNA] TLS 1.2 and [tcpconnect] (dbrooke@euca.us 2018)
  29. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  30. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  31. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  32. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  33. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  34. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  35. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  36. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Robert Minor 2018)
  37. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  38. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
  39. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  40. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  41. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  42. [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
1598 --Apple-Mail-6A31ED0B-9FD0-43B4-A5CB-0885C3E4B88A Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable That only works for incoming connection that will not work for an outgoing c= onnection Robert Minor Cybermill.com 314-962-4024 ext 500 > On Mar 1, 2018, at 09:58, Brian Willson wrote: >=20 > Hi, Jym. >=20 > I=E2=80=99m trying to figure out the answer to your [tcpconnect] question.= >=20 > But I can confirm that older TLS protocols can be turned off. In fact, I h= ad to do this with Mac OS X Server v.5.1.5 -- which, short-sightedly, I thou= ght was all I had to do -- because it still supports TLS 1 and TLS 1.1, as w= ell as TLS 1.2. >=20 > (OS X Server v5.3.1 uses TLS 1.2 by default, FWIW.) >=20 > Brian >=20 > --- > Brian Willson > www.3ip.com >=20 >=20 >> On Mar 1, 2018, at 9:28 AM, Jym Duane wrote: >>=20 >> Robert >>=20 >> I am in the process (expense) of moving a site to an updated server, in o= rder to have TLS1.2 to do the tcp connect. >>=20 >> this sounds like after i do that i wont be able to still? is that due to w= ebdna? >>=20 >> will be updated to latest centos and Apache to support the TLS1.2 >>=20 >> have not got completely there yet to try it. >>=20 >> Please send script as a workaround either while transitioning or after if= needed would be greatly appreciated. >>=20 >> PS- i think older protocols can be tuned off on the server? >>=20 >> Jym >>=20 >>=20 >>> On 3/1/2018 6:12 AM, Bob Minor wrote: >>> No not at all. I can send you the php script or you can do the same thin= g with webdna on a newer server >>>=20 >>> All I really do is read the post variables and resend them to authnet as= another tcpconnect so to speak. But this would be running on an updated ser= ver.=20 >>>=20 >>> Robert Minor >>> Cybermill.com >>> 314-962-4024 ext 500 >>>=20 >>> On Mar 1, 2018, at 07:52, Brian Willson wrote: >>>=20 >>>> Yikes. Sounds complicated. >>>>=20 >>>> Is there no way to tweak the [tcpconnect] script to accom= modate TLS 1.2 and/or its ciphers? If not, that would prove a major setback h= ere. >>>>=20 >>>> Brian >>>>=20 >>>> --- >>>> Brian Willson >>>> www.3ip.com >>>>=20 >>>>=20 >>>>> On Mar 1, 2018, at 7:42 AM, Bob Minor wrote:= >>>>>=20 >>>>> I got around it by running my own Linux server that does the php call t= o authnet and dumps the data just as the gateway did. kinda like a gateway f= or my gateway.=20 >>>>>=20 >>>>> Robert Minor >>>>> Cybermill.com >>>>> 314-962-4024 ext 500 >>>>>=20 >>>>> On Mar 1, 2018, at 06:34, Brian Willson wrote: >>>>>=20 >>>>>> Hey, everybody. >>>>>>=20 >>>>>> For years I=E2=80=99ve been using [tcpconnect] to connect my online s= hopping carts with Authorize.net=E2=80=99s AIM solution, and it=E2=80=99s wo= rked great, with only a minor tweak or two required. >>>>>>=20 >>>>>> Yesterday, Authorize.net began requiring connections via the TLS 1.2 p= rotocol, and my script broke. I.e., it can no longer connect to the endpoint= .. >>>>>>=20 >>>>>> (I'd mistakenly assumed all I needed to do was make sure my server su= pported TLS 1.2, duh.) >>>>>>=20 >>>>>> Can anyone tell me how to make sure my script forces a connection via= TLS 1.2? >>>>>>=20 >>>>>> I was hoping all I=E2=80=99d need is a tweak to this line... >>>>>>=20 >>>>>> [text show=3DF]response=3D[tcpconnect host=3Dsecure2.authorize.net= &port=3D443&ssl=3DT] >>>>>>=20 >>>>>> ...but simply using =E2=80=9Cssl=3DF=E2=80=9D didn=E2=80=99t work, ha= .. >>>>>>=20 >>>>>> Here=E2=80=99s my main connect code: >>>>>>=20 >>>>>> --- >>>>>>=20 >>>>>> [text show=3DF]response=3D[tcpconnect host=3Dsecure2.authorize.net&po= rt=3D443&ssl=3DT][!] >>>>>>=20 >>>>>> [/!][tcpsend]POST /gateway/transact.dll = HTTP/1.0[crlf][!] >>>>>>=20 >>>>>> [/!]User-Agent: e3IP[crlf][!] >>>>>>=20 >>>>>> [/!]Host: secure2.authorize.net:443[crlf][!] >>>>>>=20 >>>>>> [/!]Content-type: application/x-www-form-urlencoded[crlf][!] >>>>>>=20 >>>>>> [/!]Content-length: [countchars][content][/countchars][crlf][!] >>>>>>=20 >>>>>> [/!][crlf][!] >>>>>>=20 >>>>>> [/!][content][crlf][!] >>>>>>=20 >>>>>> [/!][/tcpsend][/tcpconnect][/text] >>>>>>=20 >>>>>> --- >>>>>>=20 >>>>>> Thanks so much in advance for any help you can offer. >>>>>>=20 >>>>>> Brian >>>>>>=20 >>>>>> --- >>>>>> Brian Willson >>>>>> www.3ip.com >>>>>>=20 >>>>>> --------------------------------------------------------- This messag= e is sent to you because you are subscribed to the mailing list talk@webdna.= us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webd= na.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>>>> --------------------------------------------------------- This message= is sent to you because you are subscribed to the mailing list talk@webdna.u= s To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdn= a.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>>>=20 >>>> --------------------------------------------------------- This message i= s sent to you because you are subscribed to the mailing list talk@webdna.us T= o unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.u= s/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>> --------------------------------------------------------- This message i= s sent to you because you are subscribed to the mailing list talk@webdna.us T= o unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.u= s/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>=20 >> --=20 >> Jym Duane - CTO - Purpose Media >> Creating Your Success Story >> Marketing : Television - Internet -Print >> Phone: (877) 443-1323 >> Email: jym@purposemedia.com >> Web: www.purposemedia.com >>=20 >> Oregon - www.GuideToOregon.com >> PO Box 1725, Jacksonville, OR 97530 >>=20 >> California - www.OrangeCounty.net >> PO Box 2025, Capistrano Beach, CA 92624=20 >> --------------------------------------------------------- This message is= sent to you because you are subscribed to the mailing list talk@webdna.us T= o unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.u= s/page.dna?numero=3D55 Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- This message is s= ent to you because you are subscribed to the mailing list talk@webdna.us To u= nsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/p= age.dna?numero=3D55 Bug Reporting: support@webdna.us --Apple-Mail-6A31ED0B-9FD0-43B4-A5CB-0885C3E4B88A Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable That only works for incoming connection tha= t will not work for an outgoing connection

Robert M= inor
314-962-4024 ext 500

On Mar 1, 2018, at 09:58, Brian Willson <willson@3ip.com> wrote:

Hi, Jym.

I=E2=80=99m trying to figure out the answer to your [tcpconnect] qu= estion.

But I can c= onfirm that older TLS protocols can be turned off. In fact, I had to do this= with Mac OS X Server v.5.1.5 -- which, short-sightedly, I thought was all I= had to do -- because it still supports TLS 1 and TLS 1.1, as well as TLS 1.= 2.

(OS X Server v5= ..3.1 uses TLS 1.2 by default, FWIW.)

Brian

---
Brian Willson
www.3ip.com


On Mar 1, 2018, at 9:28 AM, Jym Duane <jym@purposemedia.com> wrote:

=20 =20

Robert

I am in the proces= s (expense) of moving a site  to an updated server, in order to have TLS1.2 to do the tcp connect.

this sounds like after i do that i wont be able to still? is that due to webdna?

will be updated to latest centos and Apache to support the TLS1.2

have not got compl= etely there yet to try it.

Please send script as a workaround either while transitioning or after if needed would be greatly appreciated.

PS- i think older protocols can be tuned off on the server?

Jym


On 3/1/2018 6:12 AM, Bob Minor wrote:
No not at all. I can send you the php script or you can do the same thing with webdna on a newer server

All I really do is read the post variables and resend t= hem to authnet as another tcpconnect so to speak. But this would be running on an updated server. 

Robert Minor
314-962-4024 ext 500

On Mar 1, 2018, at 07:52, Brian Willson <willson@3ip.com> wrote:

Yikes. Sounds complicated.

Is there no way to tweak the [tcpconnect] script to accommodate TLS 1.2 and/or its ciphers? If not, that would prove a major setback here.

Brian

---
Brian Willson


On Mar 1, 2018, at 7:42 AM, Bob Minor <bob.minor@cybermill.com> wrote:

I got around it by running my own Linux server that does the php call to authnet and dumps the data just as the gateway did. kinda like a gateway for my gateway. 

Hey, everybody.

For years I=E2=80=99ve been usin= g [tcpconnect] to connect my online shopping carts with Authorize.net=E2=80=99s AIM solution, and it=E2=80=99s worked great, w= ith only a minor tweak or two required.

Yesterday, Authorize.net bega= n requiring connections via the TLS 1.2 protocol, and my script broke. I.e., it can no longer connect to the endpoint.

(I'd mistakenly assumed all I needed to do was make sure my server supported TLS 1.2, duh.)

Can anyone tell me how to make sure my script forces a connection via TLS 1.2?

I was hoping all I=E2=80=99d nee= d is a tweak to this line...

   [text show=3DF]response=3D[tcpconnect host=3Dse= cure2.authorize.net&port=3D443&ssl=3DT]

...but simply using =E2=80=9Cs= sl=3DF=E2=80=9D didn=E2=80=99t work, ha.

Here=E2=80=99s my main connect= code:

---

[text show=3DF]response=3D[tcpconnect host=3Dse= cure2.authorize.net&port=3D443&ssl=3DT][!]

[/!][tcpsend]POST /gateway/transact.dll HTTP/1.0[crlf][!]

[/!]User-Agent: e3IP[crlf][!]


[/!]Content-type: application/x-www-form-urlencoded[crlf][!]=

[/!]Content-length: [countchars][content][/countchars][crlf][!= ]

[/!][crlf][!]

[/!][content][crlf][!]
=

[/!][/tcpsend][/tcpconnect][= /text]

---

Thanks so much in advance for any help you can offer.

Brian

---
Brian Willson
www.3ip.com

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us<= /a> archives: http://www.webdna.us/pag= e.dna?numero=3D55 Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?= numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55= Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us

--=20Jym Duane - CTO - Purpose MediaCreating Your Success StoryMarketing : Television - Internet -PrintPhone: (877) 443-1323Email: jym@purposemedia.comWeb: www.purposemedia.comOregon - www.GuideToOregon.comPO Box 1725,  Jacksonville, OR 97530California - www.OrangeCounty.netPO Box 2025,  Capistrano Beach, CA 92624 
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us= To unsubscribe, E-mail to: talk-leave@webdna.us archives: h= ttp://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdn= a.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leav= e@webdna.us archives: http://www.w= ebdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us= --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --Apple-Mail-6A31ED0B-9FD0-43B4-A5CB-0885C3E4B88A-- . Bob Minor

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Pop-Up Redirects (1998) Robert Minor duplicate mail (1997) Tab Charactor (1997) ThisAutoNumber (2003) Summing fields (1997) [WebDNA] WebDNA Sciprt for Zipping files? (2012) [WebDNA] WebDNA not interpreting for directory (2014) MacAuthorize order data fields WAS:How To question... (1997) Merging databases (1997) cybercash with webcatalog (1999) RE: Remote delivery (1998) Is there a way......... (2000) question: webmerchant connection (1997) WC2.0 Memory Requirements (1997) Visitor info (2000) Big Databases (1997) WebCatalog can't find database (1997) [OT] Networking 3 printers wirelessly (2005) Text data with spaces in them... (1997) File Info Cache Size is out of range? (1998)