Search Results for "database manager"

Written in C/CUDA, this tool recovers lost mnemonics and passphrases for BTC, ETH, TRX, DOGE, LTC, DASH, ZEC, BCH, and BTG. Supports BIP32/44/49/84 derivation paths. Features partial phrase recovery and a built-in dictionary for fast, efficient results. Compliant with wallet standards.

The all-built-in-one, automatic, ready-to-go out-of-box, easy-to-use state-of-the-art, and really awesome NASH OS! Over 25,000+ flexible features and controls and all scalable!! The most powerful solution ever built to instantly deliver new heights of online ecommerce enterprise to you.

QPass is easy to use, open source password manager application with built-in password generator. You can store in it's database such data as passwords and logins which will be encrypted using AES-256 with PBKDF2(number of iterations set by user). Each entry can include additional information about entry such as name, url adress and description.

In this program you will find tools like : Rawdata tool , file encryption , text encryption , program updater , program protecter , password manager , program settings , defult settings , settings viewer and the last is the file hashing. the file hashing you can use 6 hashing types for the file encryption 1 since i ran out of time for it , and the text encryption has 17 different types 12 encrypt and 5 hashing types. some uses encryption keys and some dont. there are AES , 4DES...

** Guys I have built a much more powerful Fully Featured CMS system at: https://github.com/MacdonaldRobinson/FlexDotnetCMS Macs CMS is a Flat File ( XML and SQLite ) based AJAX Content Management System. It focuses mainly on the Edit In Place editing concept. It comes with a built in blog with moderation support, user manager section, roles manager section, SEO / SEF URL

VaultKeepR is a decentralized, open-source password manager where everything is encrypted client-side using XChaCha20-Poly1305 and Argon2id before leaving your device. Unlike most alternatives, it encrypts metadata too -- device names, sync data, and beneficiary info never exist in plaintext on any server. Vault data is stored on IPFS (content-addressed, no central database). Cross-device sync uses encrypted CRDTs (Automerge) with no server involved in the merge.