# ترقية منع كلمات المرور الشائعة - Pwned Passwords v2

**URL:** <https://meta.discourse.org/t/upgrading-common-password-prevention-pwned-passwords-v2/81922>\
**Category:** Feature\
**Created:** [1 مارس 2018، 8:34م UTC](https://meta.discourse.org/t/upgrading-common-password-prevention-pwned-passwords-v2/81922 "2018-03-01T20:34:39Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [2 مارس 2018، 2:01ص UTC](https://meta.discourse.org/t/upgrading-common-password-prevention-pwned-passwords-v2/81922/5 "2018-03-02T02:01:30Z")

</div>

Hmm… a bloom filter bitfield on 500M elements with a false-positive probability of one-in-a-thousand (0.001) is, if I’ve done my arithmetic correctly, about 900MB. Certainly too big to ship in core, but might be suitable for those sites which don’t want to take the API call hit (for performance, stability, or privacy)? I’ve contacted Troy to see if he’d be able to provide a 10+ length list.

---

_[View the full topic](https://meta.discourse.org/t/upgrading-common-password-prevention-pwned-passwords-v2/81922)._