Re: [WebDNA] TLS 1.2 and [tcpconnect]

This WebDNA talk-list message is from

2018


It keeps the original formatting.
numero = 113997
interpreted = N
texte = 1597 --Apple-Mail-11E82B86-A011-4C84-B073-F4F0B02A3995 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 wrote: >=20 > Thanks very much, Bob. >=20 > If this can also be done with WebDNA on a TLS 1.2-enabled server (which I h= ave -- Mac Mini Server w/ OS X Server v 5.1.5), that would be perfect in my c= ase. >=20 > But do you mean this is not something [tcpconnect] can do, and must basica= lly 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 v= ariables and sends them back out to authnet using the protocol of the newer s= erver. Again there is no reason you can=E2=80=99t just do it with webdna I j= ust 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 r= esponse 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=99= ll 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 s= ervers tcp connect which is already updated. This is the same exact code as y= ou 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 d= o 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, i= n 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 t= o 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 i= f 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 th= ing with webdna on a newer server >>>>>=20 >>>>> All I really do is read the post variables and resend them to authnet a= s another tcpconnect so to speak. But this would be running on an updated se= rver.=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 wrot= e: >>>>>>>=20 >>>>>>> I got around it by running my own Linux server that does the php cal= l to authnet and dumps the data just as the gateway did. kinda like a gatewa= y 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 w= orked 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 endpo= int. >>>>>>>>=20 >>>>>>>> (I'd mistakenly assumed all I needed to do was make sure my server s= upported TLS 1.2, duh.) >>>>>>>>=20 >>>>>>>> Can anyone tell me how to make sure my script forces a connection v= ia 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.n= et&port=3D443&ssl=3DT] >>>>>>>>=20 >>>>>>>> ...but simply using =E2=80=9Cssl=3DF=E2=80=9D didn=E2=80=99t work, h= a. >>>>>>>>=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 mess= age is sent to you because you are subscribed to the mailing list talk@webdn= a.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.we= bdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>>>>>> --------------------------------------------------------- This messa= ge 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.web= dna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>>>>>=20 >>>>>> --------------------------------------------------------- This messag= e is sent to you because you are subscribed to the mailing list talk@webdna.= us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webd= na.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>>>> --------------------------------------------------------- This message= is sent to you because you are subscribed to the mailing list talk@webdna.u= s To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdn= a.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>>>=20 >>>> --=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 i= s sent to you because you are subscribed to the mailing list talk@webdna.us T= o unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.u= s/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>> --------------------------------------------------------- This message i= s sent to you because you are subscribed to the mailing list talk@webdna.us T= o unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.u= s/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- 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-11E82B86-A011-4C84-B073-F4F0B02A3995 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable You can pop it on to your server just as is= ..

Robert Minor
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 b= e done with WebDNA on a TLS 1.2-enabled server (which I have -- Mac Mini Ser= ver w/ OS X Server v 5.1.5), that would be perfect in my case.

But do you mean this is not som= ething [tcpconnect] can do, and must basically rewrite your php code in WebD= NA?

(My server als= o supports php, of course.)

Thanks so much again for your help.

Brian

=
---
Brian Willson
<= /div>


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

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

&= lt;?php
$pstit=3D"";

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

# Start CURL session
#
curl_setopt($ch, CURLOPT_SSL_VERIFYPE= ER, false);
curl_setopt($ch, CURLOPT_HEADER, 0);
<= div class=3D"">curl_setopt($ch, CURLOPT_POSTFIELDS, $pstit);  // set th= e fields to post
curl_setopt($ch, CURLOPT_RETURNTRANSFE= R, 1);    // make sure we get the response back
curl_setopt($ch, CURLOPT_POST, 1);

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

curl_close($ch);   &n= bsp;                     &= nbsp;      // 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 s= he=E2=80=99ll script uses the older connection. 

All you need to do i

Change the tcpconnect to your new servers pa= ge


Crea= te the page on the new server authnetpost.tpl

On that page read the posted variables and resen= d 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 vari= ables. 

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

Robert Minor
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 compl= etely there yet to try it.

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

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

Jym


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

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

Robert Minor
314-962-4024 ext 500

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

Yikes. Sounds complicated.

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

Brian

---
Brian Willson


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

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

Hey, everybody.

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

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

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

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

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

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

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

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

---

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

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

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

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

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

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

[/!][crlf][!]

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

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

---

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

Brian

---
Brian Willson
www.3ip.com

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

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

--=20Jym Duane - CTO - Purpose MediaCreating Your Success StoryMarketing : Television - Internet -PrintPhone: (877) 443-1323Email: jym@purposemedia.comWeb: www.purposemedia.comOregon - www.GuideToOregon.comPO Box 1725,  Jacksonville, OR 97530California - www.OrangeCounty.netPO Box 2025,  Capistrano Beach, CA 92624 
=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: 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-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-11E82B86-A011-4C84-B073-F4F0B02A3995-- . 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)
1597 --Apple-Mail-11E82B86-A011-4C84-B073-F4F0B02A3995 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 wrote: >=20 > Thanks very much, Bob. >=20 > If this can also be done with WebDNA on a TLS 1.2-enabled server (which I h= ave -- Mac Mini Server w/ OS X Server v 5.1.5), that would be perfect in my c= ase. >=20 > But do you mean this is not something [tcpconnect] can do, and must basica= lly 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 v= ariables and sends them back out to authnet using the protocol of the newer s= erver. Again there is no reason you can=E2=80=99t just do it with webdna I j= ust 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 r= esponse 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=99= ll 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 s= ervers tcp connect which is already updated. This is the same exact code as y= ou 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 d= o 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, i= n 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 t= o 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 i= f 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 th= ing with webdna on a newer server >>>>>=20 >>>>> All I really do is read the post variables and resend them to authnet a= s another tcpconnect so to speak. But this would be running on an updated se= rver.=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 wrot= e: >>>>>>>=20 >>>>>>> I got around it by running my own Linux server that does the php cal= l to authnet and dumps the data just as the gateway did. kinda like a gatewa= y 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 w= orked 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 endpo= int. >>>>>>>>=20 >>>>>>>> (I'd mistakenly assumed all I needed to do was make sure my server s= upported TLS 1.2, duh.) >>>>>>>>=20 >>>>>>>> Can anyone tell me how to make sure my script forces a connection v= ia 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.n= et&port=3D443&ssl=3DT] >>>>>>>>=20 >>>>>>>> ...but simply using =E2=80=9Cssl=3DF=E2=80=9D didn=E2=80=99t work, h= a. >>>>>>>>=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 mess= age is sent to you because you are subscribed to the mailing list talk@webdn= a.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.we= bdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>>>>>> --------------------------------------------------------- This messa= ge 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.web= dna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>>>>>=20 >>>>>> --------------------------------------------------------- This messag= e is sent to you because you are subscribed to the mailing list talk@webdna.= us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webd= na.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>>>> --------------------------------------------------------- This message= is sent to you because you are subscribed to the mailing list talk@webdna.u= s To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdn= a.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>>>=20 >>>> --=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 i= s sent to you because you are subscribed to the mailing list talk@webdna.us T= o unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.u= s/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>> --------------------------------------------------------- This message i= s sent to you because you are subscribed to the mailing list talk@webdna.us T= o unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.u= s/page.dna?numero=3D55 Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- 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-11E82B86-A011-4C84-B073-F4F0B02A3995 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable You can pop it on to your server just as is= ..

Robert Minor
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 b= e done with WebDNA on a TLS 1.2-enabled server (which I have -- Mac Mini Ser= ver w/ OS X Server v 5.1.5), that would be perfect in my case.

But do you mean this is not som= ething [tcpconnect] can do, and must basically rewrite your php code in WebD= NA?

(My server als= o supports php, of course.)

Thanks so much again for your help.

Brian

=
---
Brian Willson
<= /div>


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

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

&= lt;?php
$pstit=3D"";

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

# Start CURL session
#
curl_setopt($ch, CURLOPT_SSL_VERIFYPE= ER, false);
curl_setopt($ch, CURLOPT_HEADER, 0);
<= div class=3D"">curl_setopt($ch, CURLOPT_POSTFIELDS, $pstit);  // set th= e fields to post
curl_setopt($ch, CURLOPT_RETURNTRANSFE= R, 1);    // make sure we get the response back
curl_setopt($ch, CURLOPT_POST, 1);

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

curl_close($ch);   &n= bsp;                     &= nbsp;      // 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 s= he=E2=80=99ll script uses the older connection. 

All you need to do i

Change the tcpconnect to your new servers pa= ge


Crea= te the page on the new server authnetpost.tpl

On that page read the posted variables and resen= d 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 vari= ables. 

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

Robert Minor
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 compl= etely there yet to try it.

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

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

Jym


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

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

Robert Minor
314-962-4024 ext 500

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

Yikes. Sounds complicated.

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

Brian

---
Brian Willson


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

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

Hey, everybody.

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

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

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

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

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

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

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

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

---

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

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

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


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

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

[/!][crlf][!]

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

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

---

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

Brian

---
Brian Willson
www.3ip.com

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

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

--=20Jym Duane - CTO - Purpose MediaCreating Your Success StoryMarketing : Television - Internet -PrintPhone: (877) 443-1323Email: jym@purposemedia.comWeb: www.purposemedia.comOregon - www.GuideToOregon.comPO Box 1725,  Jacksonville, OR 97530California - www.OrangeCounty.netPO Box 2025,  Capistrano Beach, CA 92624 
=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: 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-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-11E82B86-A011-4C84-B073-F4F0B02A3995-- . 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:

Web Catalog 2 demo (1997) Nutscrape Doesn't Render Right (2002) This list needs a digest: rant, rave... (1997) Error Lob.db records error message not name (1997) [WebDNA] PDF creation (2013) Product Comparison (2000) Problem displaying search result (1997) Help! WebCat2 bug (1997) limitation found on group searching (1997) New Plug-in and Type 11 errors (1997) Using Plug-In while running 1.6.1 (1997) all records returned. (1997) Search in 2 or more catalogs (1997) Handy Browser Counter Tip (1997) Emailer Question (1998) greater than or equal to (1997) AAgghh!! Help, please. SSL strikes again. (1997) HTML Editors (1997) Nitro plugin? (1998) date search not working when type=date specified (2007)