First of all this seems like a great application and idea, but I believe that users should be instructed to BACKUP data until they feel comfortable with its stability since I have noticed several bugs of data corruption...
Second of all
I see you use "burp" for blowfish encryption which is very nice but have you seen http://bcrypt.sourceforge.net/ ? I believe this application users a more secure implementation of the blowfish algorithm if you want check it out and verify for me. maybe in later releases you can use this as a backup for the blowfish algorithm
(there is also http://ccrypt.sourceforge.net/ for another AES backend, but I haven't used it, just posting as a FYI)
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
is the default form of secure in 1.2 and should have fixed all of the data corruption issues. As for blowfish it is being phased out in 2.0.
Why phase out blowfish?
Slackware 12 for system
MCP (For XP and Server 2003)
Network + Certified
aim is "nycjv321" (minus quotes)
as you mentioned the impementation is fairly old and ccrypt give a number of bonuses, it's faster and the incorrect password cannot be used. I would prefer to standardise on one implementation rather than support two, is there a specific reason you like blowfish?
well I could really care less, symmetric encryption algorithms are all insecure in one way or another but are used the majority of the time, adding to that its just plain file encryption, I was just wondering what you had in plans well thx for the fast response(s)
Slackware 12 for system
MCP (For XP and Server 2003)
Network + Certified
aim is "nycjv321" (minus quotes)