<?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>Dev4Press</title>
	<atom:link href="https://www.dev4press.com/blog/product/gd-security-toolbox/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dev4press.com</link>
	<description>Premium Plugins for WordPress and bbPress</description>
	<lastBuildDate>Tue, 20 Apr 2021 14:16:27 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.4</generator>

<image>
	<url>https://www.dev4press.com/wp-content/uploads/2023/03/cropped-dev4press-sign-32x32.png</url>
	<title>Dev4Press</title>
	<link>https://www.dev4press.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Updated security plugins for FLoC</title>
		<link>https://www.dev4press.com/blog/plugins/2021/updated-security-plugins-for-floc/</link>
					<comments>https://www.dev4press.com/blog/plugins/2021/updated-security-plugins-for-floc/#respond</comments>
		
		<dc:creator><![CDATA[Milan Petrovic]]></dc:creator>
		<pubDate>Tue, 20 Apr 2021 14:16:26 +0000</pubDate>
				<guid isPermaLink="false">https://www.dev4press.com/?p=34460/</guid>

					<description><![CDATA[<img src="https://www.dev4press.com/wp-content/uploads/2021/04/gd-security-headers-15-768x382.png" alt="" /><br/>Both GD Security Toolbox Pro and GD Security Headers plugins have been updated with changes related to the Permissions Policy header to add the new rule dealing with the upcoming Google targeting feature called FLoC.]]></description>
		
					<wfw:commentRss>https://www.dev4press.com/blog/plugins/2021/updated-security-plugins-for-floc/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Dev4Press History: GD Press Tools</title>
		<link>https://www.dev4press.com/blog/notes/2019/dev4press-history-gd-press-tools/</link>
					<comments>https://www.dev4press.com/blog/notes/2019/dev4press-history-gd-press-tools/#respond</comments>
		
		<dc:creator><![CDATA[Milan Petrovic]]></dc:creator>
		<pubDate>Thu, 24 Oct 2019 09:00:18 +0000</pubDate>
				<guid isPermaLink="false">https://www.dev4press.com/?p=33398/</guid>

					<description><![CDATA[<img src="https://www.dev4press.com/wp-content/uploads/2019/10/gdpet_ver_2-0-dashboard.png" alt="" /><br/>GD Press Tools is one of the oldest plugins I made, and the first one that was offered as a Pro plugin on Dev4Press website back in 2009. The first stable version of GD Press Tools was released on WordPress.org ... <p class="read-more-container"><a title="Dev4Press History: GD Press Tools" class="read-more button" href="https://www.dev4press.com/blog/notes/2019/dev4press-history-gd-press-tools/#more-33398" aria-label="Read more about Dev4Press History: GD Press Tools">Read more</a></p>]]></description>
		
					<wfw:commentRss>https://www.dev4press.com/blog/notes/2019/dev4press-history-gd-press-tools/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Security related HTTP Headers, Part 3: Content Security Policy</title>
		<link>https://www.dev4press.com/blog/notes/2017/security-related-http-headers-part-3-content-security-policy/</link>
					<comments>https://www.dev4press.com/blog/notes/2017/security-related-http-headers-part-3-content-security-policy/#respond</comments>
		
		<dc:creator><![CDATA[Milan Petrovic]]></dc:creator>
		<pubDate>Mon, 16 Oct 2017 08:16:52 +0000</pubDate>
				<guid isPermaLink="false">https://www.dev4press.com/?p=31714/</guid>

					<description><![CDATA[<img src="https://www.dev4press.com/wp-content/uploads/2017/09/data-1590455_1920-768x519.jpg" alt="" /><br/>Content Security Policy (or CSP) is very complex and powerful security-related HTTP header, that might be complex to implement, but essential in limiting what browser is allowed to load when browsing your website.]]></description>
		
					<wfw:commentRss>https://www.dev4press.com/blog/notes/2017/security-related-http-headers-part-3-content-security-policy/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Security related HTTP Headers, Part 2: Referrer Policy</title>
		<link>https://www.dev4press.com/blog/notes/2017/security-related-http-headers-part-2-referrer-policy/</link>
					<comments>https://www.dev4press.com/blog/notes/2017/security-related-http-headers-part-2-referrer-policy/#respond</comments>
		
		<dc:creator><![CDATA[Milan Petrovic]]></dc:creator>
		<pubDate>Mon, 25 Sep 2017 17:00:33 +0000</pubDate>
				<guid isPermaLink="false">https://www.dev4press.com/?p=31710/</guid>

					<description><![CDATA[<img src="https://www.dev4press.com/wp-content/uploads/2017/09/pexels-photo-768x512.jpg" alt="" /><br/>Referrer Policy is a new HTTP header drafted in 2015, implemented last year. This header controls referrer header value browser sends when the user is navigating away from your website pages.]]></description>
		
					<wfw:commentRss>https://www.dev4press.com/blog/notes/2017/security-related-http-headers-part-2-referrer-policy/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Security related HTTP Headers, Part 1: Introduction</title>
		<link>https://www.dev4press.com/blog/notes/2017/security-related-http-headers-part-1-introduction/</link>
					<comments>https://www.dev4press.com/blog/notes/2017/security-related-http-headers-part-1-introduction/#respond</comments>
		
		<dc:creator><![CDATA[Milan Petrovic]]></dc:creator>
		<pubDate>Wed, 13 Sep 2017 10:00:01 +0000</pubDate>
				<guid isPermaLink="false">https://www.dev4press.com/?p=31707/</guid>

					<description><![CDATA[<img src="https://www.dev4press.com/wp-content/uploads/2017/09/lewis-ngugi-186309-768x480.jpg" alt="" /><br/>Response to each request made to the server from the client side (browser) returns the content and the special block with HTTP response headers containing various information about the content.]]></description>
		
					<wfw:commentRss>https://www.dev4press.com/blog/notes/2017/security-related-http-headers-part-1-introduction/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Security Hardening: 6 Months Overview</title>
		<link>https://www.dev4press.com/blog/notes/2017/security-hardening-6-months-overview/</link>
					<comments>https://www.dev4press.com/blog/notes/2017/security-hardening-6-months-overview/#respond</comments>
		
		<dc:creator><![CDATA[Milan Petrovic]]></dc:creator>
		<pubDate>Tue, 14 Mar 2017 15:00:42 +0000</pubDate>
				<guid isPermaLink="false">https://www.dev4press.com/?p=30177</guid>

					<description><![CDATA[<img src="https://www.dev4press.com/wp-content/uploads/2017/03/server_load_after-768x354.png" alt="Dev4Press Server Load and Downtime, with GD Security Toolbox Pro" /><br/>Dev4Press server started experiencing occasional problems with overload in back in July. The problems started getting worse in August and September. And, the investigation lead to some interesting findings.]]></description>
		
					<wfw:commentRss>https://www.dev4press.com/blog/notes/2017/security-hardening-6-months-overview/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Improving security leads to better website performance</title>
		<link>https://www.dev4press.com/blog/notes/2016/improving-security-leads-to-better-website-performance/</link>
					<comments>https://www.dev4press.com/blog/notes/2016/improving-security-leads-to-better-website-performance/#respond</comments>
		
		<dc:creator><![CDATA[Milan Petrovic]]></dc:creator>
		<pubDate>Wed, 21 Sep 2016 19:00:47 +0000</pubDate>
				<guid isPermaLink="false">https://www.dev4press.com/?p=30179</guid>

					<description><![CDATA[Dev4Press server started experiencing occasional problems with overload in back in July. The problems started getting worse in August and September. And, the investigation lead to some interesting findings.]]></description>
		
					<wfw:commentRss>https://www.dev4press.com/blog/notes/2016/improving-security-leads-to-better-website-performance/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>reCAPTCHA for comment spam prevention</title>
		<link>https://www.dev4press.com/blog/notes/2016/recaptcha-for-comment-spam-prevention/</link>
					<comments>https://www.dev4press.com/blog/notes/2016/recaptcha-for-comment-spam-prevention/#comments</comments>
		
		<dc:creator><![CDATA[Milan Petrovic]]></dc:creator>
		<pubDate>Wed, 15 Jun 2016 07:00:29 +0000</pubDate>
				<guid isPermaLink="false">https://www.dev4press.com/?p=29788</guid>

					<description><![CDATA[<img src="https://www.dev4press.com/wp-content/uploads/2016/05/spam_recaptcha-768x419.png" alt="Spam without and with reCAPTCHA" /><br/>One of the most popular and very effective methods to combat spam is to use some form of captcha protection. But, captchas can lead to poor user experience. reCAPTCHA by Google is a quite different captcha trying to minimize user interaction.]]></description>
		
					<wfw:commentRss>https://www.dev4press.com/blog/notes/2016/recaptcha-for-comment-spam-prevention/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Login Honeypot to fight comments spam</title>
		<link>https://www.dev4press.com/blog/notes/2016/login-honeypot-to-fight-comments-spam/</link>
					<comments>https://www.dev4press.com/blog/notes/2016/login-honeypot-to-fight-comments-spam/#respond</comments>
		
		<dc:creator><![CDATA[Milan Petrovic]]></dc:creator>
		<pubDate>Thu, 26 May 2016 17:00:53 +0000</pubDate>
				<guid isPermaLink="false">https://www.dev4press.com/?p=29786</guid>

					<description><![CDATA[<img src="https://www.dev4press.com/wp-content/uploads/2016/04/spam_login_honeypot-768x388.png" alt="Spam without and with login honeypot" /><br/>There are many ways to fight spam. And, spam delivery method will largely influence the way to fight it. Honeypot on the login form is very effective if your website is free for anyone to register.]]></description>
		
					<wfw:commentRss>https://www.dev4press.com/blog/notes/2016/login-honeypot-to-fight-comments-spam/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>In-depth analysis of comment spam</title>
		<link>https://www.dev4press.com/blog/notes/2016/in-depth-analysis-of-comment-spam/</link>
					<comments>https://www.dev4press.com/blog/notes/2016/in-depth-analysis-of-comment-spam/#respond</comments>
		
		<dc:creator><![CDATA[Milan Petrovic]]></dc:creator>
		<pubDate>Thu, 21 Apr 2016 10:00:50 +0000</pubDate>
				<guid isPermaLink="false">https://www.dev4press.com/?p=29784</guid>

					<description><![CDATA[Before we get to methods to fight comment spam, it is very important to understand how spammers and spambots work, what methods they use, what types of comments they are posting.]]></description>
		
					<wfw:commentRss>https://www.dev4press.com/blog/notes/2016/in-depth-analysis-of-comment-spam/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Comment spam: how does it work?</title>
		<link>https://www.dev4press.com/blog/notes/2016/comment-spam-how-does-it-work/</link>
					<comments>https://www.dev4press.com/blog/notes/2016/comment-spam-how-does-it-work/#comments</comments>
		
		<dc:creator><![CDATA[Milan Petrovic]]></dc:creator>
		<pubDate>Tue, 12 Apr 2016 10:00:30 +0000</pubDate>
				<guid isPermaLink="false">https://www.dev4press.com/?p=29774</guid>

					<description><![CDATA[Any WordPress website that allows comments or implements forum (bbPress or something else) attracts comment spam. If you ever wondered how comment spam finds your website, this is a good place to start.]]></description>
		
					<wfw:commentRss>https://www.dev4press.com/blog/notes/2016/comment-spam-how-does-it-work/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
	</channel>
</rss>
