How to implement elliptic curve cryptography(EDWARDS Curve) to my Topology
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How to implement elliptic curve cryptography(EDWARDS Curve) to my Topology
Good Evening to all,
I am implementing "elliptic curve cryptography by using EDWARDS curve" to my Toplogy. I had got my Mobile Topology attached bellow, that i want to add Cryptography technique. Please can any one guide me to implement EDWARDS curve to my Mobile topology?
Yes sir, but in this case i need to implement Mobile Overlapped Topology with secured communication through elliptic curve cryptography by using EDWARDS curve
If you have to ask here about how to implement any kind of ECC, you're nowhere ready to try. You need to consult with a cryptographer and that's going to cost you $$$. There's no way around that; any attempt to not consult a cryptographer will almost certainly result in an insecure product.
In addition to that thought ... as a categorical statement, "do it yourself" implementations of cryptography, no matter how well-intentioned (or informative) they might be, are almost never preferable to using widely-accepted cryptographic protocols, and the libraries which implement them.
Granted, there is a moderate 100% chance that those libraries have been, if not "hijacked," then at least "weakened" by agencies such as #CLASSIFIED#, #CLASSIFIED#, or even #CLASSIFIED#, which spend far too much of our money to do such things. But I daresay that there's nothing that you can realistically do about that ... and, in the grand scheme of things, that's really not your true problem anyhow. If your implementation is going to be broken, then that break will probably not come from a weakness in the algorithm. No, it will come from "something else" in the grand picture ... most likely, key management.
Most crypto libraries allow for many different crypto algorithms to be used. (You could implement an "elliptic curve" driver, for instance, until you found that one already exists.) They focus their attention on keys, message integrity, and so forth. There's a reason for that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.