http://wordpress.org/development/2007/01/wordpress-207/ WordPress development and updates Thu, 19 Nov 2009 14:58:17 +0000 http://wordpress.org/?v=2.9-beta-1 hourly 1 http://wordpress.org/development/2007/01/wordpress-207/comment-page-44/#comment-42154 WordPress 2.0.7 « roid in TW Tue, 03 Feb 2009 22:05:28 +0000 http://wordpress.org/development/2007/01/wordpress-207/#comment-42154 [...] — roidtw @ 23:32 我原來還以為 WordPress 會從 2.0.6 直接跳到 2.1 , 沒想到 2.0.7 還是出來了… 改的檔案不多(只有 6 個檔案), 主要是針對 php [...] [...] — roidtw @ 23:32 我原來還以為 WordPress 會從 2.0.6 直接跳到 2.1 , 沒想到 2.0.7 還是出來了… 改的檔案不多(只有 6 個檔案), 主要是針對 php [...]

]]> http://wordpress.org/development/2007/01/wordpress-207/comment-page-44/#comment-33653 Aggiornamento a Wordpress 2.0.7 Sun, 29 Jun 2008 18:45:50 +0000 http://wordpress.org/development/2007/01/wordpress-207/#comment-33653 [...] questo “appunto” sottolineato dagli sviluppatori di Wordpress: entro la fine del mese, dovrebbe vedere la [...] [...] questo “appunto” sottolineato dagli sviluppatori di Wordpress: entro la fine del mese, dovrebbe vedere la [...]

]]> http://wordpress.org/development/2007/01/wordpress-207/comment-page-43/#comment-33544 Alfabetic » Blog Archive » Wordpress cuestiones de seguridad llevar a la piratería informática en masa. ¿Es su blog el siguiente paso? Thu, 12 Jun 2008 18:46:44 +0000 http://wordpress.org/development/2007/01/wordpress-207/#comment-33544 [...] en un guión que no estaba debidamente filtrado de entrada del usuario. Para su crédito, Wordpress liberado una nueva versión parcheada que la vulnerabilidad (entre otros) y pidió a sus usuarios a [...] [...] en un guión que no estaba debidamente filtrado de entrada del usuario. Para su crédito, Wordpress liberado una nueva versión parcheada que la vulnerabilidad (entre otros) y pidió a sus usuarios a [...]

]]> http://wordpress.org/development/2007/01/wordpress-207/comment-page-43/#comment-33531 TechCrunch Japanese アーカイブ » Wordpressのセキュリティ問題で大量のハッキングが発生。次はあなたのブログ？ Thu, 12 Jun 2008 07:33:38 +0000 http://wordpress.org/development/2007/01/wordpress-207/#comment-33531 [...] そのブログは当時の最新版のWordpressを使っていた。そしてその後、適切にユーザーインプットをフィルターしないというスクリプト内の単純な弱点がエントリーポイントだということを私は探り当てた。Wordpressの名誉のためにいっておくと、（特に）脆弱性をパッチし、ユーザーにアップデートを求める新バージョンがすでにリリースされている。 [...] [...] そのブログは当時の最新版のWordpressを使っていた。そしてその後、適切にユーザーインプットをフィルターしないというスクリプト内の単純な弱点がエントリーポイントだということを私は探り当てた。Wordpressの名誉のためにいっておくと、（特に）脆弱性をパッチし、ユーザーにアップデートを求める新バージョンがすでにリリースされている。 [...]

]]> http://wordpress.org/development/2007/01/wordpress-207/comment-page-43/#comment-33528 Enterprise Software Blog » Blog Archive » Wordpress Security Lapse Cause Mass Hacking Attempt Thu, 12 Jun 2008 02:23:40 +0000 http://wordpress.org/development/2007/01/wordpress-207/#comment-33528 [...] to a simple flaw in a script that was not adequately filtering user input. To its credit, Wordpress released a new version that patched the vulnerability (among others) and asked its users to [...] [...] to a simple flaw in a script that was not adequately filtering user input. To its credit, Wordpress released a new version that patched the vulnerability (among others) and asked its users to [...]

]]> http://wordpress.org/development/2007/01/wordpress-207/comment-page-43/#comment-33527 My Blog Was Hacked. Is Yours Next? Huge Wordpress Security Issues Wed, 11 Jun 2008 21:28:08 +0000 http://wordpress.org/development/2007/01/wordpress-207/#comment-33527 [...] to a simple flaw in a script that was not adequately filtering user input. To its credit, Wordpress released a new version that patched the vulnerability (amongst others) and asked its users to [...] [...] to a simple flaw in a script that was not adequately filtering user input. To its credit, Wordpress released a new version that patched the vulnerability (amongst others) and asked its users to [...]

]]> http://wordpress.org/development/2007/01/wordpress-207/comment-page-43/#comment-30800 Lap Cat Software Blog » Blog Archive » WordPress Bug Fix! Sat, 12 Apr 2008 14:29:09 +0000 http://wordpress.org/development/2007/01/wordpress-207/#comment-30800 [...] All Hope Dashed”). I’m very happy to report that the ETag parsing bug has been fixed in WordPress 2.0.7. Thus, if you’re running WordPress 2.0.7 on your site, you no longer have to comment out the [...] [...] All Hope Dashed”). I’m very happy to report that the ETag parsing bug has been fixed in WordPress 2.0.7. Thus, if you’re running WordPress 2.0.7 on your site, you no longer have to comment out the [...]

]]> http://wordpress.org/development/2007/01/wordpress-207/comment-page-43/#comment-26848 n3rd.tv » Blog Archive » Episode 0×13 Wed, 12 Mar 2008 14:53:19 +0000 http://wordpress.org/development/2007/01/wordpress-207/#comment-26848 [...] Wordpress 2.0.7 [...] [...] Wordpress 2.0.7 [...]

]]> http://wordpress.org/development/2007/01/wordpress-207/comment-page-43/#comment-25498 Weblog Tools Collection » Blog Archive » What Happened In 2007 Mon, 31 Dec 2007 18:39:23 +0000 http://wordpress.org/development/2007/01/wordpress-207/#comment-25498 [...] Jan 15, 2007 - WordPress 2.0.7 was released because of a bug in certain versions of PHP which would cause a security vulnerability in a wordpress powered blog. [...] [...] Jan 15, 2007 – WordPress 2.0.7 was released because of a bug in certain versions of PHP which would cause a security vulnerability in a wordpress powered blog. [...]

]]> http://wordpress.org/development/2007/01/wordpress-207/comment-page-43/#comment-24375 Scarform | The Linking Game (January, 2007) Fri, 19 Oct 2007 16:45:44 +0000 http://wordpress.org/development/2007/01/wordpress-207/#comment-24375 [...] Wordpress 2.0.7 is available to the 2 of you who haven’t upgraded yet. Security issues with feedburner and a few php issues fixed in this update that only took about ten days to follow up 2.0.6, and will only take another 5 days to follow 2.0.7 with the long awaited 2.1. [...] [...] Wordpress 2.0.7 is available to the 2 of you who haven’t upgraded yet. Security issues with feedburner and a few php issues fixed in this update that only took about ten days to follow up 2.0.6, and will only take another 5 days to follow 2.0.7 with the long awaited 2.1. [...]

]]>