rkgk/crates/haku-wasm/Cargo.toml

[package]
name = "haku-wasm"
version = "0.1.0"
edition = "2021"

[lib]
crate-type = ["cdylib"]

[dependencies]
arrayvec = { version = "0.7.4", default-features = false }
dlmalloc = { version = "0.2.6", features = ["global"] }
haku.workspace = true
log.workspace = true
paste = "1.0.15"

[features]
default = []
std = []
initial commit 2024-08-10 23:10:03 +02:00			`[package]`
			`name = "haku-wasm"`
			`version = "0.1.0"`
			`edition = "2021"`

			`[lib]`
			`crate-type = ["cdylib"]`

			`[dependencies]`
			`arrayvec = { version = "0.7.4", default-features = false }`
			`dlmalloc = { version = "0.2.6", features = ["global"] }`
			`haku.workspace = true`
			`log.workspace = true`
sync 2024-08-15 20:01:23 +02:00			`paste = "1.0.15"`
initial commit 2024-08-10 23:10:03 +02:00
user authentication through a secret token (NOT AUDITED FOR SECURITY. DO NOT RELY ON THIS CODE.) it's probably okay, but it's incredibly easy to read localStorage from the frontend and get a hold of the secret would be nice (would it?) to have more proper session tokens I guess but we're not doing that right now I'm not entirely sure if generating the password on the server is legit like this, but it leads to an incredibly frictionless experience and I'd like to keep it. if possible. I don't really see a difference compared to password managers generating passwords for you and showing them in plaintext obviously actual passwords are stored within the manager which requires a master password, but like. do we really need that. the secret isn't shown to the user and it's very long. too bad the browser secure storage API or whatever isn't ready yet 2024-08-23 19:45:07 +02:00			`[features]`
			`default = []`
			`std = []`