Re: [WebDNA] TLS 1.2 and [tcpconnect]

This WebDNA talk-list message is from

2018


It keeps the original formatting.
numero = 113991
interpreted = N
texte = 1591 --Apple-Mail-7DF157AB-4F20-4F32-A92A-A5B2C5E027B4 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable No not at all. I can send you the php script or you can do the same thing wi= th webdna on a newer server All I really do is read the post variables and resend them to authnet as ano= ther tcpconnect so to speak. But this would be running on an updated server.= =20 Robert Minor Cybermill.com 314-962-4024 ext 500 > 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 an= d/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 a= uthnet and dumps the data just as the gateway did. kinda like a gateway for m= y 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 shop= ping carts with Authorize.net=E2=80=99s AIM solution, and it=E2=80=99s worke= d great, with only a minor tweak or two required. >>>=20 >>> Yesterday, Authorize.net began requiring connections via the TLS 1.2 pro= tocol, 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 suppo= rted TLS 1.2, duh.) >>>=20 >>> Can anyone tell me how to make sure my script forces a connection via TL= S 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&po= rt=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=3D= 443&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 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 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-7DF157AB-4F20-4F32-A92A-A5B2C5E027B4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable No not at all. I can send you the php scrip= t or you can do the same thing with webdna on a newer server

<= div>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. 

Robert Minor
Cybermill.com
314-962-4024 ext 500
On Mar 1, 2018, at 07:52, Brian Willson <willson@3ip.com> wrote:

Y= ikes. Sounds complicated.

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

Brian
---
Brian Willson
www.3ip.com
=


On M= ar 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 au= thnet and dumps the data just as the gateway did. kinda like a gateway for m= y gateway. 

Rober= t Minor
Cy= bermill.com
314-962-4024 ext 500
=

On Mar 1, 2018, at 06:34, Brian Willson <<= a href=3D"mailto:willson@3ip.com" class=3D"">willson@3ip.com> wrote:<= br class=3D"">
Hey, everybody.

For years I=E2=80=99ve been using [tcpconnect] to connect my onlin= e shopping carts with Auth= orize.net=E2=80=99s AIM solution, and it=E2=80=99s worked great, with on= ly a minor tweak or two required.

=
Yesterday, Auth= orize.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 s= ure 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[tcpconne= ct host=3Dsecure2.autho= rize.net&port=3D443&ssl=3DT]

...but simply using =E2=80=9Cssl=3DF=E2=80=9D d= idn=E2=80=99t work, ha.

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

---

[text show=3DF]response=3D[tcpconnect host=3Dsecure2.authorize.net&am= p;port=3D443&ssl=3DT][!]

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

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

[/!]Host: secure2.authorize.net:4= 43[crlf][!]

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

[/!]Content-length: [countchars][con= tent][/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: 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-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-7DF157AB-4F20-4F32-A92A-A5B2C5E027B4-- . 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)
1591 --Apple-Mail-7DF157AB-4F20-4F32-A92A-A5B2C5E027B4 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable No not at all. I can send you the php script or you can do the same thing wi= th webdna on a newer server All I really do is read the post variables and resend them to authnet as ano= ther tcpconnect so to speak. But this would be running on an updated server.= =20 Robert Minor Cybermill.com 314-962-4024 ext 500 > 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 an= d/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 a= uthnet and dumps the data just as the gateway did. kinda like a gateway for m= y 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 shop= ping carts with Authorize.net=E2=80=99s AIM solution, and it=E2=80=99s worke= d great, with only a minor tweak or two required. >>>=20 >>> Yesterday, Authorize.net began requiring connections via the TLS 1.2 pro= tocol, 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 suppo= rted TLS 1.2, duh.) >>>=20 >>> Can anyone tell me how to make sure my script forces a connection via TL= S 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&po= rt=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=3D= 443&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 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 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-7DF157AB-4F20-4F32-A92A-A5B2C5E027B4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable No not at all. I can send you the php scrip= t or you can do the same thing with webdna on a newer server

<= div>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. 

Robert Minor
314-962-4024 ext 500
On Mar 1, 2018, at 07:52, Brian Willson <willson@3ip.com> wrote:

Y= ikes. Sounds complicated.

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

Brian
---
Brian Willson
www.3ip.com
=


On M= ar 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 au= thnet and dumps the data just as the gateway did. kinda like a gateway for m= y gateway. 

Rober= t Minor
Cy= bermill.com
314-962-4024 ext 500
=

On Mar 1, 2018, at 06:34, Brian Willson <<= a href=3D"mailto:willson@3ip.com" class=3D"">willson@3ip.com> wrote:<= br class=3D"">
Hey, everybody.

For years I=E2=80=99ve been using [tcpconnect] to connect my onlin= e shopping carts with Auth= orize.net=E2=80=99s AIM solution, and it=E2=80=99s worked great, with on= ly a minor tweak or two required.

=
Yesterday, Auth= orize.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 s= ure 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[tcpconne= ct host=3Dsecure2.autho= rize.net&port=3D443&ssl=3DT]

...but simply using =E2=80=9Cssl=3DF=E2=80=9D d= idn=E2=80=99t work, ha.

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

---

[text show=3DF]response=3D[tcpconnect host=3Dsecure2.authorize.net&am= p;port=3D443&ssl=3DT][!]

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

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

[/!]Host: secure2.authorize.net:4= 43[crlf][!]

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

[/!]Content-length: [countchars][con= tent][/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: 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-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-7DF157AB-4F20-4F32-A92A-A5B2C5E027B4-- . 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:

[OT] Who's got a cool link (2002) How do I get Google to crawl a WebCat site? (2003) [OT] Hacked IIS/FTP (2002) Sorting via date (2002) Shownext never shows next...still (1997) [OT] I am old. (2003) Generating and appending SKU to a db automatically (1998) WC2b12: Yes, Formulas.db is for real (1997) Re:WebDNA Writer Needed (1997) Sorting search by date. (2000) [include ...] behavior (1997) Funny Chars (1999) WebCatalog Mac and cgi-bin (WebSTAR 2.0) (1997) Running _every_ page through WebCat ? (1997) Shared conversion under WebTen (1998) [OT] See Flash? (2003) Encrypt broken on Mac 3.05b13?? (2000) WebDelivery downloads alias, not original ? (1997) Shownext never shows next...still (1997) Summing fields (1997)