<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Testing for Cipher Suite Preference</title>
	<atom:link href="http://www.exploresecurity.com/testing-for-cipher-suite-preference/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.exploresecurity.com/testing-for-cipher-suite-preference/</link>
	<description>IT security tools, techniques and commentary</description>
	<lastBuildDate>Sun, 07 Sep 2025 03:12:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.6.1</generator>
	<item>
		<title>By: Jerome</title>
		<link>http://www.exploresecurity.com/testing-for-cipher-suite-preference/#comment-91385</link>
		<dc:creator>Jerome</dc:creator>
		<pubDate>Mon, 01 Sep 2025 08:46:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.exploresecurity.com/?p=296#comment-91385</guid>
		<description><![CDATA[Clearly manual testing is much slower. That&#039;s why a tool is useful. Manual testing is used to provide definitive evidence of a particular result from an automated tool. For certain types of vulnerability, however, it&#039;s not possible to test using something like OpenSSL out-of-the-box because obviously it is not designed to send malformed packets. As you can tell from the date of this post (and other posts in the same category) it&#039;s been some time since I last looked at this area. The tools mentioned in this post may not be best-in-class. In general, for any tool you are relying on, it&#039;s useful to read the docs so you know what its capabilities and limitations are, and then try it out against known targets i.e. a server you&#039;ve configured. Additionally, as in this post, running two tools to ensure there is agreement is a good way to try to eliminate errors. Any discrepancy can be followed up with manual testing. Hope that&#039;s useful.]]></description>
		<content:encoded><![CDATA[<p>Clearly manual testing is much slower. That&#8217;s why a tool is useful. Manual testing is used to provide definitive evidence of a particular result from an automated tool. For certain types of vulnerability, however, it&#8217;s not possible to test using something like OpenSSL out-of-the-box because obviously it is not designed to send malformed packets. As you can tell from the date of this post (and other posts in the same category) it&#8217;s been some time since I last looked at this area. The tools mentioned in this post may not be best-in-class. In general, for any tool you are relying on, it&#8217;s useful to read the docs so you know what its capabilities and limitations are, and then try it out against known targets i.e. a server you&#8217;ve configured. Additionally, as in this post, running two tools to ensure there is agreement is a good way to try to eliminate errors. Any discrepancy can be followed up with manual testing. Hope that&#8217;s useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Desain</title>
		<link>http://www.exploresecurity.com/testing-for-cipher-suite-preference/#comment-91370</link>
		<dc:creator>Desain</dc:creator>
		<pubDate>Thu, 21 Aug 2025 12:40:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.exploresecurity.com/?p=296#comment-91370</guid>
		<description><![CDATA[How thorough is this manual testing method compared to automated tools like ssl-enum-ciphers in Nmap?]]></description>
		<content:encoded><![CDATA[<p>How thorough is this manual testing method compared to automated tools like ssl-enum-ciphers in Nmap?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
