Releases: conradkleinespel/rpassword
v4.0.4
v.4.0.3
Updates the README.md instructions so they appear correctly on crates.io. No code changes.
v4.0.2
Updates the README.md instructions so they appear correctly on crates.io. No code changes.
v4.0.1
Updates the README.md instructions so they appear correctly on crates.io. No code changes.
v4.0.0
v3.0.1
v3.0.0
This release allows reading the password even if there is no \n
at the end of the input. Thanks @longshorej for this improvement. Here was the justification behind the change:
In general, GNU readline will return the input it has read when reaching EOF. It seems to me that rpassword's current behavior in this regard is not conventional.
This a breaking change so the version has been bumped up to 3.0.0
on crates.io.
Feel free to open an issue if you need any help.
v2.1.0
Thanks to @teythoon, rpassword
can now read the password from the TTY directly, instead of STDIN, which is safer. It goes something like this:
extern crate rpassword;
fn main() {
let pass = rpassword::read_password_from_tty(Some("Password: ")).unwrap();
println!("Password: {}", pass);
}
There should be no breaking changes. read_password_from_tty
is not used by default. It is opt-in, so that your code doesn't break.
Feel free to open an issue if you need any help.
v2.0.0
- Thanks to @DaveLancaster, you can now read passwords from anything that implements
std::io::BufRead
: #20. This makes mockingSTDIN
easier for tests. - Deprecated functions have been removed. Use
rprompt
to read input other than passwords from the command line.
Easy upgrade path:
- Upgrade to
rpassword:1.0.2
, - Handle any deprecation notices,
- Upgrade to
rpassword:2.0.0
.
Breaking changes:
- Deprecated functions were removed,
- A new function was introduced. In most cases, this won't break your code, but it might break your code if you have something like this:
use rpassword::*;
use foobar as read_password_from_reader;
v1.0.2
Fixes bug on Windows where \r
would be read.
No breaking changes.