Re: Challenge

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



uni wrote:

Can anyone decrypt this code:
3188C1i6BuK5WQ.xjOstFuoti5§Űirsc5q3tX7pH3tiXFu5e0E5óje3t;ŰÉZ@9órÚtFküZ5e;xÓhD):JÓttc3thg.95l6!kxtUoóYu.xFWü1étŐÁ¤,$nÉDF7#xejXz§9ÚtXuÉbmÓ;xiuKtütotMYs1;xküEQüaŐ!áÉ3tŐt_dCK4AhPhPHu"ZóÓEu65Á68g/egU3MAZKNFU5p7éS1O08(gK6b5öMKKT6V5ÜfKfKKu7éfíEíAR0NI274eőKÜfífiNÚKNEíMUA+6ÁEKIKfogyeú7dSUAMKCMKKRKMgUKMfÚKNFKeCfKSi8ÓipKNM1fKKINKkp5SNKKjKöSUAXKÖ0NgK8NKReDHKfKeTgKhV7MKÜqKNÚ6CQKKhKhCKhCfKNKipKpgKm0KÁgÚ0GALMKKS6CqyekKÓgKeSKé7ÜfÚfK7űg18ü0SArIKfK5ÁRíKwHUgK5wNKNKKaKRR1Kűi0gK6ű5SQí0SKsKDN1s0KRgK6c5(8DfKKTeNRy7I0TKNfKGoi0SUKT6cM1KwKkKNEKAC8LKNDKLU3Ó8NEUKÍ0M7éLKKpKxqKARKT6NG28ClL0Ngíi0KZ5NEKKpAŐNÚ0Q8QMKK/gyKZfyfKK+7NgULKfíKNfKCÚfÚgy0QfÚgK6NiCRK0TKR0NqKKCfíMi8ŐfK6Nqol0AMKNgKfyizeNgKDKKTKNRiKMgiKZqÚh0eőKNgyevfy0NgKMíKMKNQÚ8NKNeZH2KÍ6mNK6MKMKNgUGoKN5hqKKCKMAégKAX7CMo8l3Cg1B07xQKKR6NKÜfí8CQKgKKQK=g10ÖKŰKéf2qUgKSoKRgiMK3bKÖqK6lO0qKi0KQCíKőgÚ5ÜfKKQ6RMK3Gm+gíAsKxSU6M3mQK5TKMqKKN7ugiKDKMgí7ÜqKK5póMe"Z.x3tMUüZi5Lu.<áZ5ÚiXDu"ZiuŐMXuÓÁ@xGZ.<5q3qsJ5cKtXupY¤,:düÜiP#xÓZ_xZl2qsx/c6tbQ/ó_úBÓFuéMWuÉÜFuFM7yüÉX<XTűZ.xP-üMűtZec5DQjeÓZjeg!yé¤,.x"Z.xAMsgFk6tZe.xszotpeuóüZ_TÚ5i5FG5É35pó5YÖZ>Ó
This mailing list is about implementation of cryptosystems in linux, and is not as much about security of any single cryptosystems, unless it is included in or planed to be in the linux kernel or linux application. So your question is not that terribly on-topic. Other places would be more appropirate, and more likely to give you a better answer, if that is what you want. The sci.crypt newsgroup is one such place.

Also, If this is to be taken seriously, you need to give more details, like the algorithm, encoding scheme and other details of your system. A basic assumption is cryptology is that the adversary know everything except one piece of secret information - the key you used for encryption. The history has proved that such information almost always leaks out or are reverse engineered anyway. It is known as "security by obscurity". Even if you think your system is secure with all detailes published, but don't do it "just in case", you are still limiting the number of people that can analyze the system. The GSM mobile phone encryption (which is broken) is an example of such a system.

Since the question implies that you lack some knowledge in crytology, I would recomend to buy some books on the topic. Bruce Schneiers "Applied cryptography" is one such book. The book "Handbook of Applied cryptography" (Menezes et al) is a little bit harder to read, but is freely downloadable on the net (http://www.cacr.math.uwaterloo.ca/hac/). Both of them are a little bit old (both 1996 i think), but still covers the basics. They lack some of the newer algorithms though.

(BTW: On sci.crypt you would be flamed to charcoal with a question like yours)




-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/



[Index of Archives]     [Kernel]     [Linux Crypto]     [Gnu Crypto]     [Gnu Classpath]     [Netfilter]     [Bugtraq]
  Powered by Linux