Re: [WebDNA] TLS 1.2 and [tcpconnect]

This WebDNA talk-list message is from

2018


It keeps the original formatting.
numero = 114001
interpreted = N
texte = 1601 --Apple-Mail=_31FBDEDB-FFE5-4953-A0DA-7FD4F95C24B0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Just to follow up... I=E2=80=99ve been in touch with my hosting = provider, and it seems I can configure a new server to run both MacOS = and a virtual Linux machine, so perhaps I can take care of my Authnet = connection problem by using your php script, after all. Thanks very much. Brian --- Brian Willson www.3ip.com > On Mar 1, 2018, at 11:14 AM, Bob Minor = wrote: >=20 > You can pop it on to your server just as is. >=20 > Robert Minor > Cybermill.com > 314-962-4024 ext 500 >=20 > On Mar 1, 2018, at 09:37, Brian Willson > wrote: >=20 >> Thanks very much, Bob. >>=20 >> If this can also be done with WebDNA on a TLS 1.2-enabled server = (which I have -- Mac Mini Server w/ OS X Server v 5.1.5), that would be = perfect in my case. >>=20 >> But do you mean this is not something [tcpconnect] can do, and must = basically rewrite your php code in WebDNA? >>=20 >> (My server also supports php, of course.) >>=20 >> Thanks so much again for your help. >>=20 >> Brian >>=20 >> --- >> Brian Willson >> www.3ip.com >>=20 >>=20 >>> On Mar 1, 2018, at 10:16 AM, Robert Minor > wrote: >>>=20 >>> OK here is the php, just put it on your new server and instead of = calling your tcp to authnet call your new php page. All it does is reads = your post variables and sends them back out to authnet using the = protocol of the newer server. Again there is no reason you can=E2=80=99t = just do it with webdna I just wrote it in php. >>>=20 >>> >> $pstit=3D""; >>>=20 >>> foreach ($_POST as $key =3D> $value) >>> { >>> $pstit .=3D "$key=3D$value"."&"; >>> } >>> $pstit .=3D "this=3Dthat"; >>>=20 >>> # Start CURL session >>> # >>> $ch=3Dcurl_init("https://secure.authorize.net/gateway/transact.dll = "); >>> //$ch=3Dcurl_init("http://65.175.90.231/printvars.php = "); >>> curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); >>> curl_setopt($ch, CURLOPT_HEADER, 0); >>> curl_setopt($ch, CURLOPT_POSTFIELDS, $pstit); // set the fields to = post >>> curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); // make sure we get = the response back >>> curl_setopt($ch, CURLOPT_POST, 1); >>>=20 >>> $buffer =3D curl_exec($ch); // execute the = post >>>=20 >>> curl_close($ch); // close our session >>>=20 >>> print_r($buffer); >>>=20 >>> ?> >>>=20 >>>=20 >>>> On Mar 1, 2018, at 8:37 AM, Bob Minor > wrote: >>>>=20 >>>> No the older protocols cannot be completed turned off. Apples = she=E2=80=99ll script uses the older connection.=20 >>>>=20 >>>> All you need to do i >>>>=20 >>>> Change the tcpconnect to your new servers page >>>>=20 >>>> http://mynewserver.com/authnetpost.tpl = >>>>=20 >>>> Create the page on the new server authnetpost.tpl >>>>=20 >>>> On that page read the posted variables and resend them using the = newer servers tcp connect which is already updated. This is the same = exact code as you have on your old server. Only with the read variables.=20= >>>>=20 >>>> When I get to my server I will send you the PHP to do this, but you = can do it with WebDNA >>>>=20 >>>> Robert Minor >>>> Cybermill.com >>>> 314-962-4024 ext 500 >>>>=20 >>>> On Mar 1, 2018, at 08:28, 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 = ------------------------------------------------= --------- 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 --Apple-Mail=_31FBDEDB-FFE5-4953-A0DA-7FD4F95C24B0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Just to follow up... I=E2=80=99ve been in touch with my = hosting provider, and it seems I can configure a new server to run both = MacOS and a virtual Linux machine, so perhaps I can take care of my = Authnet connection problem by using your php script, after all.

Thanks very = much.

Brian

---
Brian Willson


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

You can pop it on to your server = just as is.

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

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

Thanks very much, = Bob.

If this can = also be done with WebDNA on a TLS 1.2-enabled server (which I have -- = Mac Mini Server w/ OS X Server v 5.1.5), that would be perfect in my = case.

But do = you mean this is not something [tcpconnect] can do, and must basically = rewrite your php code in WebDNA?

(My server also supports php, of = course.)

Thanks = so much again for your help.

Brian

---
Brian Willson
www.3ip.com


On Mar = 1, 2018, at 10:16 AM, Robert Minor <bob.minor@cybermill.com> wrote:

OK here is the php, = just put it on your new server and instead of calling your tcp to = authnet call your new php page. All it does is reads your post variables = and sends them back out to authnet using the protocol of the newer = server. Again there is no reason you can=E2=80=99t just do it with = webdna I just wrote it in php.

<?php
$pstit=3D"";

foreach ($_POST as $key =3D> $value)
{
$pstit .=3D = "$key=3D$value"."&";
}
$pstit .=3D "this=3Dthat";

# Start CURL session
#
$ch=3Dcurl_init("https://secure.authorize.net/gateway/transact.dll");
<= div class=3D"">//$ch=3Dcurl_init("http://65.175.90.231/printvars.php");
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt($ch, CURLOPT_HEADER, 0);
curl_setopt($ch, CURLOPT_POSTFIELDS, $pstit);  // set = the fields to post
curl_setopt($ch, = CURLOPT_RETURNTRANSFER, 1);    // make sure we get the = response back
curl_setopt($ch, CURLOPT_POST, = 1);

$buffer =3D = curl_exec($ch);                 =       // execute the post

curl_close($ch);       =                     =      // close our session

print_r($buffer);

?>


On Mar 1, 2018, at 8:37 AM, = Bob Minor <bob.minor@cybermill.com> wrote:

No the older protocols cannot be = completed turned off. Apples she=E2=80=99ll script uses the older = connection. 

All = you need to do i

Change the tcpconnect to your new servers page

http://mynewserver.com/authnetpost.tpl

Create the page on the = new server authnetpost.tpl

On that page read the posted variables and resend them using = the newer servers tcp connect which is already updated. This is the same = exact code as you have on your old server. Only with the read = variables. 

When I get to my server I will send you the PHP to do this, = but you can do it with WebDNA

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

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

=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
=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
--------------------------------------------------------- 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=_31FBDEDB-FFE5-4953-A0DA-7FD4F95C24B0-- . 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)
1601 --Apple-Mail=_31FBDEDB-FFE5-4953-A0DA-7FD4F95C24B0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Just to follow up... I=E2=80=99ve been in touch with my hosting = provider, and it seems I can configure a new server to run both MacOS = and a virtual Linux machine, so perhaps I can take care of my Authnet = connection problem by using your php script, after all. Thanks very much. Brian --- Brian Willson www.3ip.com > On Mar 1, 2018, at 11:14 AM, Bob Minor = wrote: >=20 > You can pop it on to your server just as is. >=20 > Robert Minor > Cybermill.com > 314-962-4024 ext 500 >=20 > On Mar 1, 2018, at 09:37, Brian Willson > wrote: >=20 >> Thanks very much, Bob. >>=20 >> If this can also be done with WebDNA on a TLS 1.2-enabled server = (which I have -- Mac Mini Server w/ OS X Server v 5.1.5), that would be = perfect in my case. >>=20 >> But do you mean this is not something [tcpconnect] can do, and must = basically rewrite your php code in WebDNA? >>=20 >> (My server also supports php, of course.) >>=20 >> Thanks so much again for your help. >>=20 >> Brian >>=20 >> --- >> Brian Willson >> www.3ip.com >>=20 >>=20 >>> On Mar 1, 2018, at 10:16 AM, Robert Minor > wrote: >>>=20 >>> OK here is the php, just put it on your new server and instead of = calling your tcp to authnet call your new php page. All it does is reads = your post variables and sends them back out to authnet using the = protocol of the newer server. Again there is no reason you can=E2=80=99t = just do it with webdna I just wrote it in php. >>>=20 >>> >> $pstit=3D""; >>>=20 >>> foreach ($_POST as $key =3D> $value) >>> { >>> $pstit .=3D "$key=3D$value"."&"; >>> } >>> $pstit .=3D "this=3Dthat"; >>>=20 >>> # Start CURL session >>> # >>> $ch=3Dcurl_init("https://secure.authorize.net/gateway/transact.dll = "); >>> //$ch=3Dcurl_init("http://65.175.90.231/printvars.php = "); >>> curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); >>> curl_setopt($ch, CURLOPT_HEADER, 0); >>> curl_setopt($ch, CURLOPT_POSTFIELDS, $pstit); // set the fields to = post >>> curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); // make sure we get = the response back >>> curl_setopt($ch, CURLOPT_POST, 1); >>>=20 >>> $buffer =3D curl_exec($ch); // execute the = post >>>=20 >>> curl_close($ch); // close our session >>>=20 >>> print_r($buffer); >>>=20 >>> ?> >>>=20 >>>=20 >>>> On Mar 1, 2018, at 8:37 AM, Bob Minor > wrote: >>>>=20 >>>> No the older protocols cannot be completed turned off. Apples = she=E2=80=99ll script uses the older connection.=20 >>>>=20 >>>> All you need to do i >>>>=20 >>>> Change the tcpconnect to your new servers page >>>>=20 >>>> http://mynewserver.com/authnetpost.tpl = >>>>=20 >>>> Create the page on the new server authnetpost.tpl >>>>=20 >>>> On that page read the posted variables and resend them using the = newer servers tcp connect which is already updated. This is the same = exact code as you have on your old server. Only with the read variables.=20= >>>>=20 >>>> When I get to my server I will send you the PHP to do this, but you = can do it with WebDNA >>>>=20 >>>> Robert Minor >>>> Cybermill.com >>>> 314-962-4024 ext 500 >>>>=20 >>>> On Mar 1, 2018, at 08:28, 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 = ------------------------------------------------= --------- 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 --Apple-Mail=_31FBDEDB-FFE5-4953-A0DA-7FD4F95C24B0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Just to follow up... I=E2=80=99ve been in touch with my = hosting provider, and it seems I can configure a new server to run both = MacOS and a virtual Linux machine, so perhaps I can take care of my = Authnet connection problem by using your php script, after all.

Thanks very = much.

Brian

---
Brian Willson


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

You can pop it on to your server = just as is.

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

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

Thanks very much, = Bob.

If this can = also be done with WebDNA on a TLS 1.2-enabled server (which I have -- = Mac Mini Server w/ OS X Server v 5.1.5), that would be perfect in my = case.

But do = you mean this is not something [tcpconnect] can do, and must basically = rewrite your php code in WebDNA?

(My server also supports php, of = course.)

Thanks = so much again for your help.

Brian

---
Brian Willson
www.3ip.com


On Mar = 1, 2018, at 10:16 AM, Robert Minor <bob.minor@cybermill.com> wrote:

OK here is the php, = just put it on your new server and instead of calling your tcp to = authnet call your new php page. All it does is reads your post variables = and sends them back out to authnet using the protocol of the newer = server. Again there is no reason you can=E2=80=99t just do it with = webdna I just wrote it in php.

<?php
$pstit=3D"";

foreach ($_POST as $key =3D> $value)
{
$pstit .=3D = "$key=3D$value"."&";
}
$pstit .=3D "this=3Dthat";

# Start CURL session
#
$ch=3Dcurl_init("https://secure.authorize.net/gateway/transact.dll");
<= div class=3D"">//$ch=3Dcurl_init("http://65.175.90.231/printvars.php");
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt($ch, CURLOPT_HEADER, 0);
curl_setopt($ch, CURLOPT_POSTFIELDS, $pstit);  // set = the fields to post
curl_setopt($ch, = CURLOPT_RETURNTRANSFER, 1);    // make sure we get the = response back
curl_setopt($ch, CURLOPT_POST, = 1);

$buffer =3D = curl_exec($ch);                 =       // execute the post

curl_close($ch);       =                     =      // close our session

print_r($buffer);

?>


On Mar 1, 2018, at 8:37 AM, = Bob Minor <bob.minor@cybermill.com> wrote:

No the older protocols cannot be = completed turned off. Apples she=E2=80=99ll script uses the older = connection. 

All = you need to do i

Change the tcpconnect to your new servers page

http://mynewserver.com/authnetpost.tpl

Create the page on the = new server authnetpost.tpl

On that page read the posted variables and resend them using = the newer servers tcp connect which is already updated. This is the same = exact code as you have on your old server. Only with the read = variables. 

When I get to my server I will send you the PHP to do this, = but you can do it with WebDNA

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

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

=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
=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
--------------------------------------------------------- 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=_31FBDEDB-FFE5-4953-A0DA-7FD4F95C24B0-- . 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:

Time Tracking (2003) Re:no [search] with NT (1997) WebStar Compatibility (2003) Whats wrong with this code? (1998) Merging databases (1997) Emails are Stuck (2003) Show if time tags (1997) [HIDEIF] inside [FOUNDITEM] (1997) why .HTML pages no processing? (2000) Standalone Testing (1998) Pithy questions on webcommerce & siteedit (1997) Draft Manual, Tutorial, and more (1997) [WebDNA] Sendmail BCC bug still exists (2015) New install permissions (2003) Return records from another (1997) FAX orders (1996) autosensing lanague selection (1997) E-mail Attachments (1997) Password protect (2000) Help! WebCat2 bug (1997)