But standardized and verified digital encryption routines are available in modern operating systems to make strong cryptography available and accessible to the average developer.
I was atempting to point out that you don't necessarily need crypto experience to implement strong cryptography. The part that really demands experience has already been done and is readily available.
"Art" as in there are different implementations but none that are standardized, proven secure and readily available (that I am aware of) as a local service.
This seems like the end result of one of those "chatgpt - make me a business" online courses. There's no information about who's behind it, AI generated content everywhere, etc.
I built something similar years ago --- data hidden locally in plain sight.
Instead of stenography, I simply appended the encrypted data/payload to the end of a JPG file in my photo library. The file opens and displays normally.
Part of the photo/carrier file is used as salt for decryption. The part that is used changes randomly based on the last modification time of the file. The file creation time is maintained/doesn't change with payload modifications.
Encryption is also tied to disk parameters so a simple file copy makes the data unreadable. The access utility can be used to move the file and re-encrypt the data on a different disk.
A strong password and strong encryption is enough. The presence of 'blindlock' on a device is a clear indication that one of your files is a wallet. Phoning home to do a licence check is EVERY time you use it is obnoxious and defeats the purpose of having local software.
The question is, have you done something so unique and challenging that your website itself wouldn't serve as a prompt to rebuild the whole thing? Would I spend less than $49 doing so?
27 comments
[ 3.6 ms ] story [ 8.5 ms ] threadWhat's your security/cryptography background?
But standardized and verified digital encryption routines are available in modern operating systems to make strong cryptography available and accessible to the average developer.
I was atempting to point out that you don't necessarily need crypto experience to implement strong cryptography. The part that really demands experience has already been done and is readily available.
What level of trust do you grant to this project?
Impossible to say without seeing the implementation/source code.
One is not supposed to trust "art" with their passwords.
Instead of stenography, I simply appended the encrypted data/payload to the end of a JPG file in my photo library. The file opens and displays normally.
Part of the photo/carrier file is used as salt for decryption. The part that is used changes randomly based on the last modification time of the file. The file creation time is maintained/doesn't change with payload modifications.
Encryption is also tied to disk parameters so a simple file copy makes the data unreadable. The access utility can be used to move the file and re-encrypt the data on a different disk.
A strong password and strong encryption is enough. The presence of 'blindlock' on a device is a clear indication that one of your files is a wallet. Phoning home to do a licence check is EVERY time you use it is obnoxious and defeats the purpose of having local software.
>A vibe-coded password manager? Sign me up!
I see "pricing" but can't spot "source code", perhaps you forgot to add a link?