@EllaRose I noticed Destiny disappeared at some point. I hope you didn't throw it out completely. I know our designs were different, but I've still been working on an integer based variant and had an awesome breakthrough: I've devised a variant that offers a reduction from the GapSVP lattice problem, without resorting to anything over-complicated
I have a small doubt. In my workplace they use two servers say X and Y. X sends files(data) to Y. I was debugging an issue where X was unable to connect to Y. I exported the certificate of Y and placed it in keystore of X.
Which did not work. Then I got the Private key of Y and placed it in Keystore of X as PrivateKeyEntry
Then it started to work. I tried to check the internal implementation, It seems they are trying to sign with private key present in keystore.
I could not make sense why this would need a private key.
I googled and understood that. Encrypting with public key and receiver decrypting with private key is encryption.
and signing where the private key of sender is used to sign.
But what is the above case? Why would I get the private key of another server place it in my keystore and sign using it.
I do not have formal education in math or crypto so please correct me in case of my lack of understanding.
The both servers are local deployment so it might be possible that I did not understand the entire process completly
My manager was saying the certificate of Y should be enough. I was also equally perplexed when that was not the case.