








(1)
Your rating: Now say why...



| Downloads:1,808 |
| Version Downloads:1,338 |
| Type:Business : Word Processing |
| License:Shareware |
| Date:28 Sep 2009 |
| Platform:PPC / Intel |
| Price: $2.00 |
Overall (Version 1.x):![]() ![]() ![]() ![]() ![]() |
Features:![]() ![]() ![]() ![]() ![]() |
Ease of Use:![]() ![]() ![]() ![]() ![]() |
Value:![]() ![]() ![]() ![]() ![]() |
Stability:![]() ![]() ![]() ![]() ![]() |
+2
+5
Maclornebeyn reviewed on 25 Sep 2009
- The user interface kills too much of the window's space with unnecessary buttons, icons or information, leaving too little space for the actual document
- When asked for the password to encrypt a document, you are not asked to type it a second time. If you mistype it accidentally, your work is lost. There is a reason why (almost) every application working with encryption needs you to type in your (encoding) password twice...
- When decoding, you have to select the cipher again. Also, if you select the wrong cipher or give the wrong password, garbage is displayed instead of a proper error message.
- After ciphering, the encoded text (!) is displayed - uneditable and in yellow (and yes, Base64 is applied so that it does not look too bad...). I'm not in the very least interested, how my encoded message looks like but rather would like to be able to continue working on my document without decoding it first...
These were the issues I have found in the first three minutes of testing this application (wrote two test documents, closed and opened them a couple of times (3 or so)). After that, the application asks me to buy it or exit whenever I want to use one of the encryption features. How am I supposed to test it properly within such a short time?!?
+4
+156
Excuse my bad english.
+5
# sText now performs Base64 after encrypting with a cipher you choosed for better security" (from the release notes for v1.7)
I'm wondering... Base64 is simply an algorithm to convert purely binary data into a string composed of a selection of 64 characters which exist in every character encoding in order to e.g. send it per plain-text email. The drawback is that the amount of data is blown up to about 133% its original size.
As far as I know there is no key involved, the algorithm is well known and therefore IMO can not improve security in any way...
+1
+156
+1
+156
http://www.youtube.com/watch?v=FxYOdUIa49o