Ok, it was my fault, I just didn't look at the results: The leading zero (from PKCS#1 padding) is not part of the python result string, which looks (in hex) like.
Ok, it was my fault, I just didn't look at the results: The leading zero (from PKCS#1 padding) is not part of the python result string, which looks (in hex) like: 02 a2 16 4e 51 45 aa 8d 94 b0 de 64 4d 4c 4c bd 0b 01 b8 d2 de dc ed 23 0b 25 c2 11 6c 0a 0b 1f 4f 19 d0 33 18 db e0 81 25 33 f6 e3 70 8d 97 d2 c7 ef 32 ef 27 3c c0 ac 47 68 c0 5b 7b 6d 0d ba 44 da cb bf e8 71 75 d3 2f 9a b1 97 6b 70 4f ff 98 6f 5a 9a 74 3c 65 94 eb 57 52 8a 2f 73 1f 14 7d 76 08 d3 e5 8b 82 b8 5d ed 2b 75 52 29 b5 22 af 76 55 bc 5d e9 41 99 00 4d 61 72 74 69 6e So, 02 at the beginning points to random padding (somehow I was expecting 0xff padding...). The last 6 bytes (after the zero) are exactly the "Message" I was expecting, but a normal print didn't show them just because of the zero byte...
Python may remove any leading "00" since the most significant bit of "02" is 0 therefore there is no need of "00" to indicate the sign of the number. Your padding seems correct assuming PKCS#1 (section 8.1 of PKCS#1 v1.5): 02 -> public key operation a2--99 -> non-zero random data 4d 61 72 74 69 6e -> ASCII encoding of "Martin" :) – Jcs Feb 25 at 12:40.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.