Cryptography Who is hiring? |
- Who is hiring?
- Why would my RSA homework assignment want me to use a 398-digit number for e?
- Why there are no cryptographic bolt-seals?
- Usability of cryptographic APIs (+ survey invitation)
Posted: 02 Nov 2018 09:55 AM PDT I guess I am, so it's time for such a post :) hopefully I won't be the only one commenting here [link] [comments] |
Why would my RSA homework assignment want me to use a 398-digit number for e? Posted: 02 Nov 2018 01:50 PM PDT I'm implementing my own RSA algorithm for an assignment, but I'm confused about some of the requirements. I know 3 and 65537 are commonly used for values of `e`, but I'm supposed to use a 398-digit number that is relatively prime with phi(n). Additionally, I need to find `d` that is the inverse of `e % phi(n)`. Here's my code: n = p*q Thanks for any help [link] [comments] |
Why there are no cryptographic bolt-seals? Posted: 02 Nov 2018 03:27 PM PDT I just saw a documentary on coke traffic in France. A lot a coke comes via containers from Colombia. One of the problems is that the bolt-seals that seal the containers can be faked (serial number). Thus, the end to end chain can not be guaranteed. To me, a cryptographic bolt-seal could be a very good option. The idea is that upon closure of the seal, a crypto pair is generated in it. Then, the public key is scanned (RFID) and thus becomes the serial number of the seal. The serial number is timestamped and published. Once upon arrival, the customs or the client can check that the seal was not tampered with by public-key cryptography. All the generated public keys would then be stored on an open database, thus making it impossible to reuse the same seal twice (or by having faked seals). What do you think of it ? [link] [comments] |
Usability of cryptographic APIs (+ survey invitation) Posted: 02 Nov 2018 06:05 AM PDT Hello, usability is a very important part of a good cryptographic API. Without usability, programmers will do mistakes which will lead to insecure software. I am researching the usability of cryptographic APIs at Darmstadt University of Applied Sciences. For this purpose I want to compare the usability of different Java APIs supporting digital signatures. I am very interested in your opinions about API usability, maybe also sharing some bad examples. But even more important, I'm looking for participants to take part in my online study to investigate the usability of cryptographic APIs. I prepared an online editor where you will be presented with a programming task. This task should be solved using a randomly assigned Java API and should take you about 90 minutes. Only basic Java skills are required. If you want to take part in my research, please visit the following page: research.azeier.de By participating, you would help me understand different problems programmers are facing when using cryptographic APIs. These insights are then used to create more usable APIs. As a little incentive, all participants have the chance to win one of three 100€ voucher for amazon. For this purpose you will have to enter you E-Mail address in the survey after finishing the tasks. This address will only be used to send you the voucher in case you've won and will be deleted afterwards. I would like to thank you in advance for supporting the study and making a valuable contribution to my research. If you encounter any technical difficulties, please let me know. [link] [comments] |
You are subscribed to email updates from Cryptography news and discussions. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States |
No comments:
Post a Comment