home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Plugins
Popular Plugins
Moving Pictures
Spanish Scraper FilmAffinity.com with IMDb.es bonus to get fanarts -- v2.1.0
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="RoChess" data-source="post: 1242808" data-attributes="member: 18896"><p>[USER=54451]@peque[/USER], thanks for the diligent debugging to narrow it down.</p><p></p><p>[USER=52219]@ltfearme[/USER], no idea what point exactly, but it sounds like you need to add the code I'm using myself in a different project (SSL/Poodle flashback!!):</p><p></p><p style="margin-left: 20px"><p style="margin-left: 20px">// Add support for TLS 1.2 on .NET 4.5</p> <p style="margin-left: 20px">ServicePointManager.SecurityProtocol |= SecurityProtocolType.Tls12;</p> <p style="margin-left: 20px"></p> <p style="margin-left: 20px">// Add support for TLS 1.2 on .NET 4.0</p> <p style="margin-left: 20px">//ServicePointManager.SecurityProtocol |= (SecurityProtocolType)3072;</p> </p><p></p><p>Using |= will append it to the existing protocols, so you can still support TLS 1.0/1.1 as the industry rule to only allow TLS 1.2 is not enforced yet (though highly recommended, but you would need to test all scraper-script sources to confirm if forcing it via '=', but not like scraper-scripts pose a PCI DDS security risk). This will then cover those servers that only accept TLS 1.2, and therefore will not allow a TLS 1.0/1.1 forward-request to take place.</p><p></p><p>TLS 1.3 is still in draft, so don't have to worry about it for a while (appears to be set for another update in September 2018).</p><p></p><p>More information is available @ <strong><a href="https://blogs.perficient.com/microsoft/2016/04/tsl-1-2-and-net-support/" target="_blank">TLS 1.2 and .NET Support: How to Avoid Connection Errors - Microsoft</a></strong></p><p></p><p>The Moving-Pictures code making the connections appears to be @ <strong><a href="https://github.com/damienhaynes/moving-pictures/blob/master/Cornerstone/ScraperEngine/Nodes/RetrieveNode.cs#L197" target="_blank">damienhaynes/moving-pictures</a></strong></p><p></p><p>But I'm not familiar with the `WebGrabber` as I rely on `HttpWebRequest` myself, but the ServicePointManager should still be applicable.</p><p></p><p>Microsoft made TLS 1.2 support default in .NET 4.6, but I still have that code in place on 4.6.2 so not sure if I couldn't be bothered to remove it, or it was still needed. I'm using the Tls12 entry, but the 3072 should work just as well for you if you are on an older framework.</p><p></p><p>As you can see via SSLLabs under Configuration -> Protocols, FilmAffinity only supports TLS 1.2 -- <strong><a href="https://www.ssllabs.com/ssltest/analyze.html?d=filmaffinity.com" target="_blank">SSL Server Test: filmaffinity.com (Powered by Qualys SSL Labs)</a></strong></p></blockquote><p></p>
[QUOTE="RoChess, post: 1242808, member: 18896"] [USER=54451]@peque[/USER], thanks for the diligent debugging to narrow it down. [USER=52219]@ltfearme[/USER], no idea what point exactly, but it sounds like you need to add the code I'm using myself in a different project (SSL/Poodle flashback!!): [INDENT][INDENT]// Add support for TLS 1.2 on .NET 4.5 ServicePointManager.SecurityProtocol |= SecurityProtocolType.Tls12; // Add support for TLS 1.2 on .NET 4.0 //ServicePointManager.SecurityProtocol |= (SecurityProtocolType)3072;[/INDENT][/INDENT] Using |= will append it to the existing protocols, so you can still support TLS 1.0/1.1 as the industry rule to only allow TLS 1.2 is not enforced yet (though highly recommended, but you would need to test all scraper-script sources to confirm if forcing it via '=', but not like scraper-scripts pose a PCI DDS security risk). This will then cover those servers that only accept TLS 1.2, and therefore will not allow a TLS 1.0/1.1 forward-request to take place. TLS 1.3 is still in draft, so don't have to worry about it for a while (appears to be set for another update in September 2018). More information is available @ [B][URL="https://blogs.perficient.com/microsoft/2016/04/tsl-1-2-and-net-support/"]TLS 1.2 and .NET Support: How to Avoid Connection Errors - Microsoft[/URL][/B] The Moving-Pictures code making the connections appears to be @ [B][URL="https://github.com/damienhaynes/moving-pictures/blob/master/Cornerstone/ScraperEngine/Nodes/RetrieveNode.cs#L197"]damienhaynes/moving-pictures[/URL][/B] But I'm not familiar with the `WebGrabber` as I rely on `HttpWebRequest` myself, but the ServicePointManager should still be applicable. Microsoft made TLS 1.2 support default in .NET 4.6, but I still have that code in place on 4.6.2 so not sure if I couldn't be bothered to remove it, or it was still needed. I'm using the Tls12 entry, but the 3072 should work just as well for you if you are on an older framework. As you can see via SSLLabs under Configuration -> Protocols, FilmAffinity only supports TLS 1.2 -- [B][URL="https://www.ssllabs.com/ssltest/analyze.html?d=filmaffinity.com"]SSL Server Test: filmaffinity.com (Powered by Qualys SSL Labs)[/URL][/B] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Popular Plugins
Moving Pictures
Spanish Scraper FilmAffinity.com with IMDb.es bonus to get fanarts -- v2.1.0
Contact us
RSS
Top
Bottom
