crossterm VS RustCrypto

I have this feeling with all rust apps using crossterm crate as their backend like GitUI for example

I guess you could use EventStream like in this example

Made a small toy using crossterm that simulates the falling sand using the rules laid out by day 14. Bit late to the party but was pretty fun. The moment I saw the prompt I was fully intent on making some sort of visualization for this after getting the solution.

There are plenty of terminal UI libraries that are actually nice to work with. For Python, there's Textual and PyTermGUI. For Rust, there's ratatui and Cursive (or, if you want something a bit lower level, crosster or termion). For Go, there's bubbletea.

Switching the backend of Cursive to crossterm removed dependence on ncurses

I don't know where to start, CrossTerm can read events asynchronously with tokio https://github.com/crossterm-rs/crossterm/blob/master/examples/event-stream-tokio.rs , but I don't have any idea what that really means, I am coming from the HTML Canvas and TypeScript. I want the most simple and basic method possible. Cheers!

Just wondering if anyone has any insight into the current development and maintenance of termion? It currently has 67 issues and 24 merge requests and no code activity has happened since Sep 27 2021, so nothing in over a year. I am of course grateful for the existing project, but just somewhat concerned that it ends up being abandoned or forgotten seeing as it is one of the premiere tui libraries written purely in Rust (other being crossterm).

I might make a gui frontend in the future, but for now i'll focus on the terminal. The terminal doesn't mean it doesnt support mac or windows though, they have terminals too! And the library used for accepting key-input is crossterm which supports windows!

I used crossterm. Really love the simplicity of the API, definitely fit my purposes well.

For the terminal part you could use https://crates.io/crates/crossterm

I would say a toy (or personal-use-only) password manager is a relatively simple project. If we are to forget about the GUI parts, you need to determine serialization of your password database (bincode + serde should be enough) and how to encrypt it. For the latter you need only two algorithms: a password hash for deriving encryption key from password and optional salt (the latter is usually randomly generated and stored as a "key file"), and an AEAD algorithm for encrypting and decrypting serialized database. There are certain pitfalls with encryption (e.g. you should not reuse nonce with the same key, especially with modes like GCM) and with properly erasing sensitive data from memory, as well as preventing it from leaking to things like swap, but learning about those is part of the learning experience.

FYI: the rust-crypto crate is unmaintained. Take a look at https://github.com/RustCrypto/AEADs instead

For AEAD with AES, you may want to use RustCrypto (https://github.com/RustCrypto/AEADs.git) instead

Dexios is a secure command-line encryption tool, that uses audited crates provided by the RustCrypto Team.

This is in relation to RustCrypto/AEADs#421 - myself and another user are having the exact same issue.

I choose an AEDS crate from the RustCrypto group: AES-GCM in its SIV variant (the SIV variant isn't really needed but it doesn't cost much).

Use RustCrypto's aes with one of its block modes (https://docs.rs/block-modes/latest/block_modes/) or AEAD algorithms (https://github.com/RustCrypto/AEADs). There's a lot of modular stuff in RustCrypto, just need to browse a little 😉.

crypto_secretbox: https://github.com/RustCrypto/AEADs/tree/master/xsalsa20poly1305

I'd recommend https://github.com/RustCrypto/AEADs. RustCrypto's crates are high quality, widely used and some have even been audited. Unfortunately they don't provide a read/write interface.