Rajiv Shah

Is it possible to revisit this topic? I assume things have changed since 2017 regarding OS security

Hi @debris , would you be open to providing a `reset` method on `Keccak` so that we can zero out the buffer there?

Is this actually possible? From what I read from the [documentation](https://developer.apple.com/documentation/security/certificate_key_and_trust_services/keys/storing_keys_in_the_secure_enclave) it seems like you can't store existing keys in the Secure Enclave. You'd have to generate a new one...

We have an app that uses Rust and Electron (using Sentry SDKs for both), and are using the Rust component in our [Capacitor](https://capacitorjs.com/)-based mobile app that we're developing. We're looking...

@mdev0730 you can use https://github.com/tradle/rn-nodeify to patch this so that it uses `react-native-crypto` instead

One other issue is that "fix vuln" shows even though a vulnerability is not fixable:  I'm happy to make a PR to fix this, but I'm not sure what...

It seems like the URL is being truncated after the `#` since `#` is usually used as a [fragment identifier](https://en.wikipedia.org/wiki/Fragment_identifier). Does it work if you replace the `#` with `%23`...

Thanks for the report @michi-zuri ! This looks like an issue with the `file-saver` package. I think it should be fixed by https://github.com/eligrey/FileSaver.js/pull/613. I also fixed the issue with `TAURI_CONFIG_DIR`...

Was just about to open an issue for this 😄 We're running into the same issue with the same library (`react-native-http`). Patching it as shown in #67 fixed the issue

Looks like it's still occurring on the latest version (2.0.0). I can take a closer look and hopefully make a PR to fix it