Re: [WebDNA] TLS 1.2 and [tcpconnect]

This WebDNA talk-list message is from

2018


It keeps the original formatting.
numero = 113996
interpreted = N
texte = 1596 --Apple-Mail=_A3456FBF-24E7-4B17-AD60-4DC3DEED3891 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, Jym. I=E2=80=99m trying to figure out the answer to your [tcpconnect] = question. But I can confirm 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 wrote: >=20 > Robert >=20 > I am in the process (expense) of moving a site to an updated server, = in order 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 webdna? >=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 = thing 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 server.=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 accommodate TLS = 1.2 and/or its ciphers? If not, that would prove a major setback here. >>>=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 to authnet and dumps the data just as the gateway did. kinda like a = gateway for 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 shopping carts with Authorize.net =E2=80=99s= AIM solution, and it=E2=80=99s worked great, with only a minor tweak or = two required. >>>>>=20 >>>>> Yesterday, Authorize.net began requiring = connections via the TLS 1.2 protocol, 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 = supported 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 = &port=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 = 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 = ------------------------------------------------= --------- 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 > --=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 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=_A3456FBF-24E7-4B17-AD60-4DC3DEED3891 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi, Jym.

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

But I can confirm 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 process (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 completely 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 them to authnet as another tcpconnect so to speak. But this would be running on an updated server. 

Robert Minor
Cybermill.com
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
www.3ip.com


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. 

Robert Minor
Cybermill.com
314-962-4024 ext 500

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

Hey, everybody.

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

Yesterday, Authorize.net began 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 = need is a tweak to this line...

   [text show=3DF]response=3D[tcpconnect = host=3Dsecure2.authorize.net&port=3D443&ssl=3D= T]

...but simply using = =E2=80=9Cssl=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=3Dsecure2.authorize.net&port=3D443&ssl=3D= T][!]

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

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

[/!]Host: secure2.authorize.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 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
--------------------------------------------------------- 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/pa= ge.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: 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 --Apple-Mail=_A3456FBF-24E7-4B17-AD60-4DC3DEED3891-- . 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)
1596 --Apple-Mail=_A3456FBF-24E7-4B17-AD60-4DC3DEED3891 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, Jym. I=E2=80=99m trying to figure out the answer to your [tcpconnect] = question. But I can confirm 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 wrote: >=20 > Robert >=20 > I am in the process (expense) of moving a site to an updated server, = in order 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 webdna? >=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 = thing 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 server.=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 accommodate TLS = 1.2 and/or its ciphers? If not, that would prove a major setback here. >>>=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 to authnet and dumps the data just as the gateway did. kinda like a = gateway for 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 shopping carts with Authorize.net =E2=80=99s= AIM solution, and it=E2=80=99s worked great, with only a minor tweak or = two required. >>>>>=20 >>>>> Yesterday, Authorize.net began requiring = connections via the TLS 1.2 protocol, 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 = supported 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 = &port=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 = 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 = ------------------------------------------------= --------- 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 > --=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 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=_A3456FBF-24E7-4B17-AD60-4DC3DEED3891 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi, Jym.

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

But I can confirm 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 process (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 completely 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 them to authnet as another tcpconnect so to speak. But this would be running on an updated server. 

Robert Minor
Cybermill.com
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
www.3ip.com


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. 

Robert Minor
Cybermill.com
314-962-4024 ext 500

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

Hey, everybody.

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

Yesterday, Authorize.net began 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 = need is a tweak to this line...

   [text show=3DF]response=3D[tcpconnect = host=3Dsecure2.authorize.net&port=3D443&ssl=3D= T]

...but simply using = =E2=80=9Cssl=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=3Dsecure2.authorize.net&port=3D443&ssl=3D= T][!]

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

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

[/!]Host: secure2.authorize.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 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
--------------------------------------------------------- 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/pa= ge.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: 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 --Apple-Mail=_A3456FBF-24E7-4B17-AD60-4DC3DEED3891-- . Brian Willson

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:

Re: (1998) Dubble Sku's in a Database (1999) headers (2004) generating unique IDs (2000) Different Tax levels (1998) Re:E-Mailer (WebCatb15acgiMac) (1997) syntax question, not in online refernce (1997) Re[2]: Re[3]: Problem with new formvariables (2000) Dubble Sku's in a Database (1999) attn: smitmicro - cart limitation (2002) Almost a there but..bye bye NetCloak (1997) WebCat2b12 - nesting [tags] (1997) time and welcome (1999) WebCat2 several catalogs? (1997) Accented chars and emailer (1998) Windows-based Code Editor (2002) ListFiles then delete by ModDate (2002) database visibility (2000) PCS Frames (1997) Meet your competition (2000)