=20 =20 =20=---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us--Apple-Mail-B30AC79F-0B22-4A8A-AED7-21401EF8C24C--. Associated Messages, from the most recent to the oldest: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.--------------------------------------------------------- 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
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
--------------------------------------------------------- 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
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.--------------------------------------------------------- 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
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...
--------------------------------------------------------- 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[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.
--=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 tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leav=e@webdna.usarchives: http://www.w=ebdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us
wrote:>=20> Robert>=20> I am in the process (expense) of moving a site to an updated server, in o=rder 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 w=ebdna?>=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 n=eeded 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 a=nother tcpconnect so to speak. But this would be running on an updated serve=r.=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 a=nd/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 t=o authnet and dumps the data just as the gateway did. kinda like a gateway f=or 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 sh=opping carts with Authorize.net=E2=80=99s AIM solution, and it=E2=80=99s wor=ked great, with only a minor tweak or two required.>>>>>=20>>>>> Yesterday, Authorize.net began requiring connections via the TLS 1.2 p=rotocol, 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 sup=ported TLS 1.2, duh.)>>>>>=20>>>>> Can anyone tell me how to make sure my script forces a connection via T=LS 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&por=t=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.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>>>> --------------------------------------------------------- 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 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> --=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 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-B30AC79F-0B22-4A8A-AED7-21401EF8C24CContent-Type: text/html;charset=utf-8Content-Transfer-Encoding: quoted-printableNo the older protocols cannot be completed t=urned off. Apples she=E2=80=99ll script uses the older connection. All you need to do iChange the tcp=connect to your new servers pagehttp://mynewserver.com/authnetpost.tpl<=/div>Create the page on the new server authnetpost.tpl=div>On that page read the posted variables and resend th=em 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 variable=s.When I get to my server I will send you th=e PHP to do this, but you can do it with WebDNA=20 =20 =20=---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us--Apple-Mail-B30AC79F-0B22-4A8A-AED7-21401EF8C24C--. Bob MinorRobert
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.--------------------------------------------------------- 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
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
--------------------------------------------------------- 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
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.--------------------------------------------------------- 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
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...
--------------------------------------------------------- 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[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][!]
[/!]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.
--=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 tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leav=e@webdna.usarchives: http://www.w=ebdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us
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:
Multiple adding (1997) Showing once on a founditems (1997) Preventing Merchant Settling ? (1997) off topic Duplicates (1998) Tea Room trouble (1997) WebCat2b12--[searchstring] bug (1997) redirect from the errorsMessages.db entry (1997) Anyone using WebCat UNIX on a busy server yet? (1999) Newbie Tax Question (1997) More on the email templates (1997) Using Plug-In while running 1.6.1 (1997) Strange intermittent WebDNA problems (2008) Summing fields (1997) WebCat2b15MacPlugin - showing [math] (1997) Emailer (1997) listfiles-looking for slick solution (1997) Error 11 (1996) $Replace with [founditems] (1997) WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997)