# Need help with emscripten port

**URL:** <https://internals.rust-lang.org/t/need-help-with-emscripten-port/3154>\
**Category:** Uncategorized\
**Created:** [February 8, 2016, 10:37pm UTC](https://internals.rust-lang.org/t/need-help-with-emscripten-port/3154 "2016-02-08T22:37:00Z")\
**Posts on this page:** 1\
**Showing post:** 143

<div class="post-metadata">

**Author:** ![brson](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/brson/32/5197_2.png) [@brson](https://internals.rust-lang.org/u/brson)\
**Post date:** [March 15, 2017, 11:48pm UTC](https://internals.rust-lang.org/t/need-help-with-emscripten-port/3154/143 "2017-03-15T23:48:01Z")

</div>

While I’m thinking about it, I came up with a seemingly good use case for wasm over the weekend, but don’t expect I can carry the project to completion, if somebody else wanted to.

[This blog post](https://blog.codinghorror.com/password-rules-are-bullshit/) laid out simple rules for validating the complexity of passwords, and one if it’s biggest points is that people should deny users the ability to use known common passwords. Basically, these days it is best practice to use the many leaked password lists as a blacklist, since users employing these passwords are trivially targeted.

So the idea here is to take the [fst](https://docs.rs/fst/0.1.38/fst/) crate and encode that giant password list into a hopefully small FST, and do the search fast and compactly. Create a C interface so anybody can use it server-side, then bind that C interface to a JS interface via wasm so anybody can use it client-side. Package it up to produce builds for common platforms and do a ‘Show HN’ to get some karma.

I did a prototype over the weekend but seems likely won’t get much farther any time soon: [https://github.com/brson/pwrabs](https://github.com/brson/pwrabs)

---

_[View the full topic](https://internals.rust-lang.org/t/need-help-with-emscripten-port/3154)._