status:
20/06/09: the fifth beta release is out! get it from the download page!
cryptosms provides secure communication:
cryptosms provides public/private key encryption, key generation and key management.
it sends and receives encrypted sms and public keys, de- and encrypts files, offers key verification via fingerprints
and provides a secure login.
cryptosms runs on a lot of contemporary mobile phones, which provide j2me (see the list of devices for
supported phones).
it is based on the
encryption with elliptic curves,
which is a modern solution for encryption with small and/or embedded devices.
elliptic curve encryption provides good performance and small need for memory capacities.
cryptosms does not provide:
it does not in any way encrypt or scramble the traffic data. it only performs on the
contents. it does not hide the device's id/number from where the sms comes and where it goes to. it is not an anonymiser.
technically, cryptosms is:
cryptosms is an application for mobile phones (midlet). it is written in Java
and uses the j2me (Java Platform,
Micro Edition), which is more and more common with mobile phones. plus it uses parts of the
bouncy castle libraries,
which provide a lot of open source encryption schemes for java.
compatible devices:
see our
device list of mobile phones that have been tested running cryptosms.org
further plans and ideas:
key exchange via bluetooth, encryption for other services like mms or gprs based services, p2p messaging. a home edition for sending encrypted sms via desktop computers.
secured connection to this site:
this website is also available
ssl'd with a certificate signed by
cacert.org. the certificate's SHA1 fingerprint
is: 2B:AE:19:5E:45:B1:AD:F6:25:14:88:59:EB:1B:F3:F5:D9:68:F9:BB
terms of use:
cryptosms is open source software licensed under the
gpl.
the cryptosms.org project is non-commercial.
any help is appreciated!
disclaimer:
we are not in anyway affiliated with other software that is named "cryptosms". we are sorry for the possible
confusion for users regarding multiple projects carrying the same name.
as we share the common belief that
encryption software has to be open source to be trustworthy, we do not consider any other than an open source approach a serious one.