per page, with , order by , clip by
Results of 1 - 10 of about 32 for team (0.002 sec.)
Django のセキュリティポリシー — Django 6.1 ドキュメント 13419
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django のセキュリティポリシー ¶ Django の開発チームは、セキュリティ関連の問題の責任ある報告と開示に強くコミットしています。そのため、私たちはその理想 ... に届きます。 Once you've submitted an issue via email, you should receive an acknowledgment from a member of the security team within 3 working days. After that, the security team will begin their analysis. Depending on the action to be taken, you m ... ay receive followup emails. It can take several weeks before the security team comes to a conclusion. There is no need to chase the security team unless you discover new, relevant information. All repo ... の公開キーは、一般的に使用されているほとんどのキーサーバーから入手可能です。 Respecting maintainer time ¶ Django's security team are volunteers. Please be mindful and respectful of their time when submitting reports. Your initial report should give th ...
https://man.mtool.work/django/6.1/internals/security.html
Django のセキュリティポリシー — Django 6.1 ドキュメント 13419
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django のセキュリティポリシー ¶ Django の開発チームは、セキュリティ関連の問題の責任ある報告と開示に強くコミットしています。そのため、私たちはその理想 ... に届きます。 Once you've submitted an issue via email, you should receive an acknowledgment from a member of the security team within 3 working days. After that, the security team will begin their analysis. Depending on the action to be taken, you m ... ay receive followup emails. It can take several weeks before the security team comes to a conclusion. There is no need to chase the security team unless you discover new, relevant information. All repo ... の公開キーは、一般的に使用されているほとんどのキーサーバーから入手可能です。 Respecting maintainer time ¶ Django's security team are volunteers. Please be mindful and respectful of their time when submitting reports. Your initial report should give th ...
https://man.mtool.work/django/6.1/internals/security.html
アクセシビリティ — Django 6.1 ドキュメント 9907
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » アクセシビリティ ¶ The Django project is committed to ensuring that websites built with Django are usable by everyone, including people with disabil ... onsult with users who rely on assistive technologies or with accessibility experts. You can reach out to the Accessibility team via the Accessibility Django forum topic or via the #accessibility channel on the Django Discord server . テスト基準 ¶ Des ... . For more complex interfaces, confer with other contributors to decide on testing targets. Reach out to the Accessibility team for support and to coordinate testing. ユーザーインターフェースの変更は、必ず次の方法でテストしてください: Keyboard-only n ... opic . Accessibility issues on the ticket tracker . Our django accessibility improvements project board. The Accessibility team . 目次 アクセシビリティ アクセシビリティ基準 サポート対象とテスト テスト基準 Recommended assistive technologies Known issu ...
https://man.mtool.work/django/6.1/internals/contributing/accessibility.html
Django 2.1.15 リリースノート — Django 6.1 ドキュメント 9682
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 2.1.15 リリースノート ¶ 2019年12月2日 Django 2.1.15 は 2.1.14 に含まれるセキュリティ脆弱性とデータ損失のバグを修正しています。 CVE-2019-19118 ... e user has permission to edit models included in inlines. This is a backwards-incompatible change, and the Django security team is aware that some users of Django were depending on the ability to allow editing of inlines in the admin form of an other ... he complexity of the Django admin, and in-particular the permissions related checks, it is the view of the Django security team that this change was necessary: that it is not currently feasible to maintain the existing behavior while escaping the pot ... lation related permissions edit editable save change バグ 修正 inline read allow trigger privilege interface form security team クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/releases/2.1.15.html
アクセシビリティ — Django 6.1 ドキュメント 9005
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » アクセシビリティ ¶ The Django project is committed to ensuring that websites built with Django are usable by everyone, including people with disabil ... onsult with users who rely on assistive technologies or with accessibility experts. You can reach out to the Accessibility team via the Accessibility Django forum topic or via the #accessibility channel on the Django Discord server . テスト基準 ¶ Des ... . For more complex interfaces, confer with other contributors to decide on testing targets. Reach out to the Accessibility team for support and to coordinate testing. ユーザーインターフェースの変更は、必ず次の方法でテストしてください: Keyboard-only n ... opic . Accessibility issues on the ticket tracker . Our django accessibility improvements project board. The Accessibility team . 目次 アクセシビリティ アクセシビリティ基準 サポート対象とテスト テスト基準 Recommended assistive technologies Known issu ...
https://man.mtool.work/django/6.1/internals/contributing/accessibility.html
Django 1.1.4 リリースノート — Django 6.1 ドキュメント 8554
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.1.4 リリースノート ¶ Django 1.1.4 へようこそ! This is the fourth "bugfix" release in the Django 1.1 series, improving the stability and per ... n Rails web framework had a similar exemption. Recently, engineers at Google made members of the Ruby on Rails development team aware of a combination of browser plugins and redirects which can allow an attacker to provide custom HTTP headers on a re ... st, thereby defeating CSRF protection which trusts the same-origin nature of AJAX requests. Michael Koziarski of the Rails team brought this to our attention, and we were able to produce a proof-of-concept demonstrating the same vulnerability in Djan ...
https://man.mtool.work/django/6.1/releases/1.1.4.html
Django 2.1.15 リリースノート — Django 6.1 ドキュメント 8554
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 2.1.15 リリースノート ¶ 2019年12月2日 Django 2.1.15 は 2.1.14 に含まれるセキュリティ脆弱性とデータ損失のバグを修正しています。 CVE-2019-19118 ... e user has permission to edit models included in inlines. This is a backwards-incompatible change, and the Django security team is aware that some users of Django were depending on the ability to allow editing of inlines in the admin form of an other ... he complexity of the Django admin, and in-particular the permissions related checks, it is the view of the Django security team that this change was necessary: that it is not currently feasible to maintain the existing behavior while escaping the pot ...
https://man.mtool.work/django/6.1/releases/2.1.15.html
Django 1.1.4 リリースノート — Django 6.1 ドキュメント 8554
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.1.4 リリースノート ¶ Django 1.1.4 へようこそ! This is the fourth "bugfix" release in the Django 1.1 series, improving the stability and per ... n Rails web framework had a similar exemption. Recently, engineers at Google made members of the Ruby on Rails development team aware of a combination of browser plugins and redirects which can allow an attacker to provide custom HTTP headers on a re ... st, thereby defeating CSRF protection which trusts the same-origin nature of AJAX requests. Michael Koziarski of the Rails team brought this to our attention, and we were able to produce a proof-of-concept demonstrating the same vulnerability in Djan ...
https://man.mtool.work/django/6.1/releases/1.1.4.html
Django 2.2.8 リリースノート — Django 6.1 ドキュメント 8554
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 2.2.8 リリースノート ¶ 2019年12月2日 Django 2.2.8 fixes a security issue, several bugs in 2.2.7, and adds compatibility with Python 3.8. CVE- ... e user has permission to edit models included in inlines. This is a backwards-incompatible change, and the Django security team is aware that some users of Django were depending on the ability to allow editing of inlines in the admin form of an other ... he complexity of the Django admin, and in-particular the permissions related checks, it is the view of the Django security team that this change was necessary: that it is not currently feasible to maintain the existing behavior while escaping the pot ...
https://man.mtool.work/django/6.1/releases/2.2.8.html
Django 2.2.8 リリースノート — Django 6.1 ドキュメント 8441
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 2.2.8 リリースノート ¶ 2019年12月2日 Django 2.2.8 fixes a security issue, several bugs in 2.2.7, and adds compatibility with Python 3.8. CVE- ... e user has permission to edit models included in inlines. This is a backwards-incompatible change, and the Django security team is aware that some users of Django were depending on the ability to allow editing of inlines in the admin form of an other ... he complexity of the Django admin, and in-particular the permissions related checks, it is the view of the Django security team that this change was necessary: that it is not currently feasible to maintain the existing behavior while escaping the pot ...
https://man.mtool.work/django/6.1/releases/2.2.8.html
PREV 1 2 3 4 NEXT