... mitted for any third-party password hashers that don't implement a harden_runtime() method. If you have different password hashes in your database (such as SHA1 hashes from users who haven't logged in since the default hasher switched to PBKDF2 in Djan ... er and this fix doesn't remedy that difference (or any difference when changing hashers). You may be able to upgrade those hashes to prevent a timing attack for that case. バグ修正 ¶ TIME_ZONE=None と USE_TZ=False の使用を妨げる PostgreSQL のクラッシュ ... afe timing hasher since default number redirect login request work factor attack URLs example users runtime method hashers hashes 修正 security クイック検索 Last update: 2026年10月09日 « previous | up | next » ... ... mitted for any third-party password hashers that don't implement a harden_runtime() method. If you have different password hashes in your database (such as SHA1 hashes from users who haven't logged in since the default hasher switched to PBKDF2 in Djan ... er and this fix doesn't remedy that difference (or any difference when changing hashers). You may be able to upgrade those hashes to prevent a timing attack for that case. バグ修正 ¶ TIME_ZONE=None と USE_TZ=False の使用を妨げる PostgreSQL のクラッシュ ... ... mitted for any third-party password hashers that don't implement a harden_runtime() method. If you have different password hashes in your database (such as SHA1 hashes from users who haven't logged in since the default hasher switched to PBKDF2 in Djan ... er and this fix doesn't remedy that difference (or any difference when changing hashers). You may be able to upgrade those hashes to prevent a timing attack for that case. バグ修正 ¶ Skipped URL checks (new in 1.9) if the ROOT_URLCONF setting isn't def ... ... mitted for any third-party password hashers that don't implement a harden_runtime() method. If you have different password hashes in your database (such as SHA1 hashes from users who haven't logged in since the default hasher switched to PBKDF2 in Djan ... er and this fix doesn't remedy that difference (or any difference when changing hashers). You may be able to upgrade those hashes to prevent a timing attack for that case. バグ修正 ¶ Skipped URL checks (new in 1.9) if the ROOT_URLCONF setting isn't def ... ... SAFE_EVAL ¶ Represents 'unsafe-eval' . Allows use of eval() and similar JavaScript functions. Strongly discouraged. UNSAFE_HASHES ¶ Represents 'unsafe-hashes' . Allows inline event handlers and some javascript: URIs when their content hashes match a po ... ... SAFE_EVAL ¶ Represents 'unsafe-eval' . Allows use of eval() and similar JavaScript functions. Strongly discouraged. UNSAFE_HASHES ¶ Represents 'unsafe-hashes' . Allows inline event handlers and some javascript: URIs when their content hashes match a po ... ... ixes: Module-level warnings emitted during tests are no longer silently hidden ( #18985 ). Prevented filtering on password hashes in the user admin ( #20078 ). 前のトピックへ Django 1.5.2 リリースノート 次のトピックへ Django 1.5 リリースノート 関連キー ... ... ixes: Module-level warnings emitted during tests are no longer silently hidden ( #18985 ). Prevented filtering on password hashes in the user admin ( #20078 ). 前のトピックへ Django 1.5.2 リリースノート 次のトピックへ Django 1.5 リリースノート 関連キー ... ... push --force-with-lease origin ticket_xxxxx Note that this will rewrite history of ticket_xxxxx - if you check the commit hashes before and after the operation at GitHub you will notice that the commit hashes do not match anymore. This is acceptable, ... ... push --force-with-lease origin ticket_xxxxx Note that this will rewrite history of ticket_xxxxx - if you check the commit hashes before and after the operation at GitHub you will notice that the commit hashes do not match anymore. This is acceptable, ... 2026年10月08日