rofi-pass
trophy-case
rofi-pass | trophy-case | |
---|---|---|
9 | 14 | |
695 | 394 | |
- | 1.0% | |
6.1 | 2.8 | |
3 months ago | 29 days ago | |
Shell | ||
GNU General Public License v3.0 only | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rofi-pass
-
What password and ssh/gpg key manager would you recomend for Archcraft using Openbox?
Looking at the instructions and information on GitHub - https://github.com/carnager/rofi-pass I am somewhat confused.
-
What's everyone working on this week (4/2022)?
It's supposed to be cross platform standalone rofi-pass for my Windows. On Linux I use the original one and it's great
- Creating my own password manager
-
tessen v1.2.1 released: autotype and copy password store data on Wayland, like rofi-pass
I made this post a few weeks ago about tessen's initial release. Since then, I've added a few features that might've prevented rofi-pass users from switching to Wayland based compositors (I was one of them).
-
Best FOSS Password managers ?
Pass combined with rofi-pass
-
tessen: autotype and copy password-store data on Wayland, like rofi-pass
I've made a script called tessen which is, more or less, a replacement of rofi-pass but for Wayland. It can use bemenu or the wayland fork of rofi. It relies on wtype for autotyping instead of using ydotool because ydotool needs a daemon running with root privileges.
-
Using Vim as an encrypted password manager
rofi-pass is also very nice you already use rofi
-
Which self hosted password manager?
Easy to sync because it's a git repo, supports every type of MFA / key under the sun (well, everything that GPG does, because it's basically a frontend for GPG). Easy to programmatically search / create scripts for (I use rofi-pass). Easy to install on a vps and access from anywhere. Most importantly, does one thing and does it well, Unix philosophy.
trophy-case
-
Rust from a security perspective, where is it vulnerable?
You could check cargo-fuzz trophy case, which is a list of issues that have been found via fuzzing.
-
capnproto-rust: out-of-bound memory access bug
I've added it to the trophy case.
-
[LWN] A pair of Rust kernel modules
That said, what's present in what quantities under what circumstances in the Rust fuzzing trophy case does a pretty good job of illustrating how effective the Rust compiler is at ruling out entire classes of bugs.
-
Looking for simple rust programs to crash
The same fuzzing techniques applied to Rust yielded a lot of bugs as well. But in Rust's case only 7 out of 340 fuzzer-discovered bugs, or 2%, were memory corruption issues. Naturally, all of the memory corruption bugs were in unsafe code.
-
Everything Is Broken: Shipping rust-minidump at Mozilla, Part 1
https://github.com/rust-fuzz/trophy-case has like 70 of my issues in it, including the nine minidump bugs
-
Fuzzcheck (a structure-aware Rust fuzzer)
If you have found any bugs with this tool, perhaps add them to the Rust fuzz trophy case?
-
Rust is more portable than C for pngquant/libimagequant
Source: https://github.com/rust-fuzz/trophy-case (over 40 of those are just from me).
-
Rust takes a major step forward as Linux's second official language
But to bring some data, check out the fuzz trophy case. It shows that failures in Rust are most often assertions/panics (equivalent to C++ exception) with memory corruption being relatively rare (it's not never—Rust isn't promising magic—but it's a significant change).
-
Shouldn't have happened: A vulnerability postmortem
You need to read the list more carefully.
• The list is not for Rust itself, but every program every written in Rust. By itself it doesn't mean much, unless you compare prevalence of issues among Rust programs to prevalence of issues among C programs. For some context, see how memory unsafety is rare compared to assertions and uncaught exceptions: https://github.com/rust-fuzz/trophy-case
• Many of the memory-unsafety issues are on the C FFI boundary, which is unsafe due to C lacking expressiveness about memory ownership of its APIs (i.e. it shows how dangerous is to program where you don't have the Rust borrow checker checking your code).
• Many bugs about missing Send/Sync or evil trait implementations are about type-system loopholes that prevented compiler from catching code that was already buggy. C doesn't have these guarantees in the first place, so lack of them is not a CVE for C, but just how C is designed.
- Safer usage of C++ in Chrome
What are some alternatives?
pass-otp - A pass extension for managing one-time-password (OTP) tokens
diem - Diem’s mission is to build a trusted and innovative financial network that empowers people and businesses around the world.
pass-tessen - fuzzy data selection and copy-paste from password store
go-fuzz - Randomized testing for Go
pass-import - A pass extension for importing data from most existing password managers
gccrs - GCC Front-End for Rust
bemenu - Dynamic menu library and client program inspired by dmenu
BLAKE3 - the official Rust and C implementations of the BLAKE3 cryptographic hash function
tessen - an interactive menu to autotype and copy pass and gopass data
bitwarden_rs - Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs [Moved to: https://github.com/dani-garcia/vaultwarden]
rofi - Rofi: A window switcher, run dialog and dmenu replacement - fork with wayland support
go - The Go programming language