<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Phoenix Protector &#8211; NTCore</title>
	<atom:link href="https://ntcore.com/tag/phoenix-protector/feed/" rel="self" type="application/rss+xml" />
	<link>https://ntcore.com</link>
	<description></description>
	<lastBuildDate>Wed, 07 Jul 2010 11:08:37 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>

<image>
	<url>https://ntcore.com/wp-content/uploads/2018/07/cropped-ntcore_icon-2-32x32.png</url>
	<title>Phoenix Protector &#8211; NTCore</title>
	<link>https://ntcore.com</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">184274875</site>	<item>
		<title>Rebel.NET &#038; Phoenix Protector Update</title>
		<link>https://ntcore.com/rebel-net-phoenix-protector-update/</link>
					<comments>https://ntcore.com/rebel-net-phoenix-protector-update/#comments</comments>
		
		<dc:creator><![CDATA[Erik Pistelli]]></dc:creator>
		<pubDate>Wed, 07 Jul 2010 11:08:37 +0000</pubDate>
				<category><![CDATA[Update]]></category>
		<category><![CDATA[Phoenix Protector]]></category>
		<category><![CDATA[Rebel.NET]]></category>
		<guid isPermaLink="false">http://rcecafe.net/?p=147</guid>

					<description><![CDATA[Both suffered from a bug where they&#8217;d fail in case the assembly to reproduce/protect didn&#8217;t have a .rsrc section. Since at the time I wrote the code all .NET assemblies had a .rsrc section, I took it for granted and didn&#8217;t include specific checks.]]></description>
										<content:encoded><![CDATA[<p>Both suffered from a bug where they&#8217;d fail in case the assembly to reproduce/protect didn&#8217;t have a .rsrc section. Since at the time I wrote the code all .NET assemblies had a .rsrc section, I took it for granted and didn&#8217;t include specific checks.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://ntcore.com/rebel-net-phoenix-protector-update/feed/</wfw:commentRss>
			<slash:comments>4</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">147</post-id>	</item>
		<item>
		<title>Multiple Updates</title>
		<link>https://ntcore.com/multiple-update/</link>
					<comments>https://ntcore.com/multiple-update/#comments</comments>
		
		<dc:creator><![CDATA[Erik Pistelli]]></dc:creator>
		<pubDate>Thu, 19 Feb 2009 11:20:26 +0000</pubDate>
				<category><![CDATA[Update]]></category>
		<category><![CDATA[CFF Explorer]]></category>
		<category><![CDATA[Phoenix Protector]]></category>
		<category><![CDATA[Rebel.NET]]></category>
		<guid isPermaLink="false">http://rcecafe.net/?p=77</guid>

					<description><![CDATA[A serious bug in the CFF Explorer, Rebel.NET and Phoenix Protector has been fixed. The bug affected the ExportedType .NET metadata table where the member TypeDefID was declared as a TypeDef index, while it&#8217;s a dword. The table is declared correctly in my .NET article, but somehow I wrote the wrong type in the code. &#8230; <a href="https://ntcore.com/multiple-update/" class="more-link">Continue reading<span class="screen-reader-text"> "Multiple Updates"</span></a>]]></description>
										<content:encoded><![CDATA[<p>A serious bug in the CFF Explorer, Rebel.NET and Phoenix Protector has been fixed. The bug affected the ExportedType .NET metadata table where the member TypeDefID was declared as a TypeDef index, while it&#8217;s a dword. The table is declared correctly in my .NET article, but somehow I wrote the wrong type in the code.</p>
<p>Many thanks to Yaroslav Liulko for reporting the bug.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://ntcore.com/multiple-update/feed/</wfw:commentRss>
			<slash:comments>11</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">77</post-id>	</item>
		<item>
		<title>Phoenix Protector 1.6 &#038; Strong Name Signing</title>
		<link>https://ntcore.com/phoenix-protector-16-strong-name-signing/</link>
					<comments>https://ntcore.com/phoenix-protector-16-strong-name-signing/#comments</comments>
		
		<dc:creator><![CDATA[Erik Pistelli]]></dc:creator>
		<pubDate>Thu, 11 Dec 2008 15:42:00 +0000</pubDate>
				<category><![CDATA[Update]]></category>
		<category><![CDATA[.NET]]></category>
		<category><![CDATA[Phoenix Protector]]></category>
		<guid isPermaLink="false">http://rcecafe.net/?p=36</guid>

					<description><![CDATA[Due to the high request, I took 20 minutes of my time and updated the Phoenix Protector, bringing it to the version 1.6. The only addition to this version is the possibility to re-sign assemblies obfuscated by the Phoenix Protector. The reason why this wasn&#8217;t possible in past version of the Phoenix Protector is that &#8230; <a href="https://ntcore.com/phoenix-protector-16-strong-name-signing/" class="more-link">Continue reading<span class="screen-reader-text"> "Phoenix Protector 1.6 &#038; Strong Name Signing"</span></a>]]></description>
										<content:encoded><![CDATA[<p>Due to the high request, I took 20 minutes of my time and updated the Phoenix Protector, bringing it to the version 1.6. The only addition to this version is the possibility to re-sign assemblies obfuscated by the Phoenix Protector.</p>
<p>The reason why this wasn&#8217;t possible in past version of the Phoenix Protector is that the space for the signature was removed from the assembly and the &#8220;sn.exe&#8221; tool provided by Microsoft isn&#8217;t able to re-create that space.</p>
<p>Now, it is possible to tell the Phoenix Protector from the options whether to remove or not the Strong Name Signature when obfuscating an assembly:</p>
<p><img decoding="async" src="/wp-content/uploads/legacy/phoenix_sns_option.jpg"/></p>
<p>By default the Strong Name Signature is not removed.</p>
<p>After obfuscating anassembly, just use to re-sign the &#8220;sn.exe&#8221; tool this way:</p>
<p>sn.exe -R assembly.exe your_sns.pfx</p>
]]></content:encoded>
					
					<wfw:commentRss>https://ntcore.com/phoenix-protector-16-strong-name-signing/feed/</wfw:commentRss>
			<slash:comments>18</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">36</post-id>	</item>
	</channel>
</rss>
