Re: [WebDNA] TLS 1.2 and [tcpconnect]

This WebDNA talk-list message is from

2018


It keeps the original formatting.
numero = 113990
interpreted = N
texte = 1590 --Apple-Mail=_35D169E9-6EAE-4E76-92CB-3DA9DC4E1A73 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 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 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 --Apple-Mail=_35D169E9-6EAE-4E76-92CB-3DA9DC4E1A73 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 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. 

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=3DT]

...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=3DT][!]
<= div class=3D"">
[/!][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 --Apple-Mail=_35D169E9-6EAE-4E76-92CB-3DA9DC4E1A73-- . 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)
1590 --Apple-Mail=_35D169E9-6EAE-4E76-92CB-3DA9DC4E1A73 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 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 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 --Apple-Mail=_35D169E9-6EAE-4E76-92CB-3DA9DC4E1A73 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 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. 

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=3DT]

...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=3DT][!]
<= div class=3D"">
[/!][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 --Apple-Mail=_35D169E9-6EAE-4E76-92CB-3DA9DC4E1A73-- . 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:

Help! WebCat2 bug (1997) Cart Transfer from Un-Secure to Secure (2000) A Couple Photos from the SmithMicro Booth at MacWorld (2000) WAS Strange non-display problem, now BAD MATH (2002) Emailer (WebCat2) (1997) Re1000001: Setting up shop (1997) Trouble with Netscape (1998) Credit card processing - UK (1997) [Sum] function? (1997) I'm having trouble using [url][interpret][math] together inlookup (1997) Sorting... stumped. (2006) To Use Cookies or Not To Use Cookies (2003) EMailer - WebSTAR V - OSX - WebDNA (2003) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997) YACBQ.....(Yet another checkbox question) (2000) Cancel Subscription (1996) triggering an update of two frames (1998) A multi-processor savvy WebCatalog? (1997) Search for 20 finds 2000, 200 Why? (1997) Error: Permision deny. (2005)