Comments on: Primus shows how consecutive IDs in a URL can have massive negative consequences http://jasondoucette.ca/primus-security-failure/ Daily thoughts from the trenches of a self-funded company Mon, 21 Nov 2011 10:02:19 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: Primus Canada http://jasondoucette.ca/primus-security-failure/comment-page-1/#comment-5062 Primus Canada Fri, 05 Jun 2009 22:46:41 +0000 http://jasondoucette.ca/?p=120#comment-5062 We take the protection of our customers' privacy extremely seriously. As soon as we learned of this technical glitch it was promptly resolved. We regret any confusion or concern this has caused. Primus Canada We take the protection of our customers’ privacy extremely seriously. As soon as we learned of this technical glitch it was promptly resolved. We regret any confusion or concern this has caused.

Primus Canada

]]> By: meraxes's status on Thursday, 04-Jun-09 15:35:19 UTC - Identi.ca http://jasondoucette.ca/primus-security-failure/comment-page-1/#comment-5019 meraxes's status on Thursday, 04-Jun-09 15:35:19 UTC - Identi.ca Thu, 04 Jun 2009 15:35:22 +0000 http://jasondoucette.ca/?p=120#comment-5019 [...] Primus. Keep int id's in the DB, not in URLS. http://jasondoucette.ca/2009/06/04/primus-security-failure/ [...] [...] Primus. Keep int id’s in the DB, not in URLS. http://jasondoucette.ca/2009/06/04/primus-security-failure/ [...]

]]> By: hyfen.net » How to harvest the Primus customer database in 3 easy steps http://jasondoucette.ca/primus-security-failure/comment-page-1/#comment-5017 hyfen.net » How to harvest the Primus customer database in 3 easy steps Thu, 04 Jun 2009 15:14:22 +0000 http://jasondoucette.ca/?p=120#comment-5017 [...] Jason Doucette (who reminded me about what I’d read in bed this morning) has a much more thorough analysis. [...] [...] Jason Doucette (who reminded me about what I’d read in bed this morning) has a much more thorough analysis. [...]

]]>