<?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"
	>
<channel>
	<title>Comments on: CORE GRASP (potential) pitfalls</title>
	<atom:link href="http://mordred.niama.net/blog/?feed=rss2&#038;p=120" rel="self" type="application/rss+xml" />
	<link>http://mordred.niama.net/blog/?p=120</link>
	<description></description>
	<pubDate>Fri, 15 May 2026 11:15:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: 37Gqfff22.com</title>
		<link>http://mordred.niama.net/blog/?p=120#comment-945285</link>
		<dc:creator>37Gqfff22.com</dc:creator>
		<pubDate>Thu, 24 Jul 2025 05:46:14 +0000</pubDate>
		<guid isPermaLink="false">http://mordred.niama.net/blog/?p=120#comment-945285</guid>
		<description>My coder is trying to persuade me to move to .net 
from PHP. I have always disliked the idea because of the expenses.

But he's tryiong none the less. I've been using WordPress on various websites for about 
a year and am anxious about switching to another 
platform. I have heard excellent things about blogengine.net.
Is there a way I can import all my wordpress content into 
it? Any kind of help would be really appreciated!</description>
		<content:encoded><![CDATA[<p>My coder is trying to persuade me to move to .net<br />
from PHP. I have always disliked the idea because of the expenses.</p>
<p>But he&#8217;s tryiong none the less. I&#8217;ve been using WordPress on various websites for about<br />
a year and am anxious about switching to another<br />
platform. I have heard excellent things about blogengine.net.<br />
Is there a way I can import all my wordpress content into<br />
it? Any kind of help would be really appreciated!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 37Gq22.com</title>
		<link>http://mordred.niama.net/blog/?p=120#comment-924602</link>
		<dc:creator>37Gq22.com</dc:creator>
		<pubDate>Tue, 01 Jul 2025 19:18:52 +0000</pubDate>
		<guid isPermaLink="false">http://mordred.niama.net/blog/?p=120#comment-924602</guid>
		<description>Since the admin of this website is working, no uncertainty very soon it will be renowned, 
due to its quality contents.</description>
		<content:encoded><![CDATA[<p>Since the admin of this website is working, no uncertainty very soon it will be renowned,<br />
due to its quality contents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wednesday</title>
		<link>http://mordred.niama.net/blog/?p=120#comment-693313</link>
		<dc:creator>Wednesday</dc:creator>
		<pubDate>Wed, 13 Mar 2024 23:28:59 +0000</pubDate>
		<guid isPermaLink="false">http://mordred.niama.net/blog/?p=120#comment-693313</guid>
		<description>Do you mind if I quote a few of your articles as long as I provide credit and sources back to your blog?
My blog is in the very same area of interest as yours and my visitors would truly benefit from a lot of the information you present here.
Please let me know if this okay with you. Regards!</description>
		<content:encoded><![CDATA[<p>Do you mind if I quote a few of your articles as long as I provide credit and sources back to your blog?<br />
My blog is in the very same area of interest as yours and my visitors would truly benefit from a lot of the information you present here.<br />
Please let me know if this okay with you. Regards!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marvel</title>
		<link>http://mordred.niama.net/blog/?p=120#comment-693310</link>
		<dc:creator>Marvel</dc:creator>
		<pubDate>Wed, 13 Mar 2024 23:27:26 +0000</pubDate>
		<guid isPermaLink="false">http://mordred.niama.net/blog/?p=120#comment-693310</guid>
		<description>If you desire to get a great deal from this article then you have to apply such methods to your won website.</description>
		<content:encoded><![CDATA[<p>If you desire to get a great deal from this article then you have to apply such methods to your won website.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keaton</title>
		<link>http://mordred.niama.net/blog/?p=120#comment-693308</link>
		<dc:creator>Keaton</dc:creator>
		<pubDate>Wed, 13 Mar 2024 23:22:52 +0000</pubDate>
		<guid isPermaLink="false">http://mordred.niama.net/blog/?p=120#comment-693308</guid>
		<description>My brother suggested I might like this website. He was entirely right.
This post actually made my day. You cann't imagine simply how 
much time I had spent for this info! Thanks!</description>
		<content:encoded><![CDATA[<p>My brother suggested I might like this website. He was entirely right.<br />
This post actually made my day. You cann&#8217;t imagine simply how<br />
much time I had spent for this info! Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kathaleen</title>
		<link>http://mordred.niama.net/blog/?p=120#comment-693307</link>
		<dc:creator>Kathaleen</dc:creator>
		<pubDate>Wed, 13 Mar 2024 23:22:42 +0000</pubDate>
		<guid isPermaLink="false">http://mordred.niama.net/blog/?p=120#comment-693307</guid>
		<description>Hello there! I know this is kinda off topic however ,
I'd figured I'd ask. Would you be interested in trading links or maybe guest authoring 
a blog article or vice-versa? My blog goes over a lot of the same 
topics as yours and I think we could greatly benefit from each other.

If you are interested feel free to shoot me an email. I look forward to hearing from 
you! Great blog by the way!</description>
		<content:encoded><![CDATA[<p>Hello there! I know this is kinda off topic however ,<br />
I&#8217;d figured I&#8217;d ask. Would you be interested in trading links or maybe guest authoring<br />
a blog article or vice-versa? My blog goes over a lot of the same<br />
topics as yours and I think we could greatly benefit from each other.</p>
<p>If you are interested feel free to shoot me an email. I look forward to hearing from<br />
you! Great blog by the way!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Genae</title>
		<link>http://mordred.niama.net/blog/?p=120#comment-693296</link>
		<dc:creator>Genae</dc:creator>
		<pubDate>Wed, 13 Mar 2024 23:07:32 +0000</pubDate>
		<guid isPermaLink="false">http://mordred.niama.net/blog/?p=120#comment-693296</guid>
		<description>Appreciate the recommendation. Will try it out.</description>
		<content:encoded><![CDATA[<p>Appreciate the recommendation. Will try it out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Genice</title>
		<link>http://mordred.niama.net/blog/?p=120#comment-693295</link>
		<dc:creator>Genice</dc:creator>
		<pubDate>Wed, 13 Mar 2024 23:06:37 +0000</pubDate>
		<guid isPermaLink="false">http://mordred.niama.net/blog/?p=120#comment-693295</guid>
		<description>Great site. A lot of useful info here. I am sending it to several friends ans also sharing in delicious.
And naturally, thanks for your effort!</description>
		<content:encoded><![CDATA[<p>Great site. A lot of useful info here. I am sending it to several friends ans also sharing in delicious.<br />
And naturally, thanks for your effort!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Codex Securitatis &#187; Blog Archive &#187; Vale mundum!</title>
		<link>http://mordred.niama.net/blog/?p=120#comment-18923</link>
		<dc:creator>Codex Securitatis &#187; Blog Archive &#187; Vale mundum!</dc:creator>
		<pubDate>Thu, 21 Feb 2008 18:43:30 +0000</pubDate>
		<guid isPermaLink="false">http://mordred.niama.net/blog/?p=120#comment-18923</guid>
		<description>[...] CORE GRASP (potential) pitfalls The Unexpected SQL Injection The Curse of Magic Quotes [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] CORE GRASP (potential) pitfalls The Unexpected SQL Injection The Curse of Magic Quotes [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ivan</title>
		<link>http://mordred.niama.net/blog/?p=120#comment-11080</link>
		<dc:creator>ivan</dc:creator>
		<pubDate>Fri, 24 Aug 2007 00:54:38 +0000</pubDate>
		<guid isPermaLink="false">http://mordred.niama.net/blog/?p=120#comment-11080</guid>
		<description>Those are interesting observations but not necessarily *design* flaws.
Currently can use GRASP to apply and propagate taint marks on a number of input sources (GET/POST/COOKIE/etc), there is nothing in the *design* that  prevents application of the same concept to other input sources. Specifically (you outline this in our blog), Grasp can be extended to implement application of taint marks on database input. in fact, that also has a potential privacy-enhancing benefit, using that you con not only prevent you 'second order injections' but also prevent (to a certain extent) confidential DB data from leaking out disregarding of how the PHP application chooses to use it.

As for an attack on the FSMs, that may or may not be possible in theory (I really haven't checked) but in practice it is quite unlikely that a normal PHP application will purposely make queries with SQL statements that have more than a few levels of recursion.

Regarding the performance issues pointed out there are a few things to be said. First, that the performance optimizations of the current version are really very basic: a fully-tainted or fully-untainted string does not consume 1 taint byte per byte in the string but just a single byte while strings with mixed source bytes do consume one taint byte per string byte. There are several ways to optimize this to reduce the memory footprint and the taint-propagation runtime. Note also that the current implementation has an overhead of 1-byte per taint mark when in theory just 1-bit would be necessary, on the other hand the use of an entire byte allows for extensions to the meaning of the taint mark. Second, the 30% performance hit numbers are the *worst case scenario*, that is when all inputs are sensitive sinks and all strings have mixed sources. this is not the average case for common PHP applications.

In sum, Grasp for PHP is in its infancy and there's still a lot of room for improvements, optimizations and new ideas. I would not dismiss it right away without giving it a try...</description>
		<content:encoded><![CDATA[<p>Those are interesting observations but not necessarily *design* flaws.<br />
Currently can use GRASP to apply and propagate taint marks on a number of input sources (GET/POST/COOKIE/etc), there is nothing in the *design* that  prevents application of the same concept to other input sources. Specifically (you outline this in our blog), Grasp can be extended to implement application of taint marks on database input. in fact, that also has a potential privacy-enhancing benefit, using that you con not only prevent you &#8217;second order injections&#8217; but also prevent (to a certain extent) confidential DB data from leaking out disregarding of how the PHP application chooses to use it.</p>
<p>As for an attack on the FSMs, that may or may not be possible in theory (I really haven&#8217;t checked) but in practice it is quite unlikely that a normal PHP application will purposely make queries with SQL statements that have more than a few levels of recursion.</p>
<p>Regarding the performance issues pointed out there are a few things to be said. First, that the performance optimizations of the current version are really very basic: a fully-tainted or fully-untainted string does not consume 1 taint byte per byte in the string but just a single byte while strings with mixed source bytes do consume one taint byte per string byte. There are several ways to optimize this to reduce the memory footprint and the taint-propagation runtime. Note also that the current implementation has an overhead of 1-byte per taint mark when in theory just 1-bit would be necessary, on the other hand the use of an entire byte allows for extensions to the meaning of the taint mark. Second, the 30% performance hit numbers are the *worst case scenario*, that is when all inputs are sensitive sinks and all strings have mixed sources. this is not the average case for common PHP applications.</p>
<p>In sum, Grasp for PHP is in its infancy and there&#8217;s still a lot of room for improvements, optimizations and new ideas. I would not dismiss it right away without giving it a try&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
