Timeline for What Are the Risks of AES-GCM [Key, Nonce, Message] where Nonce = Message
Current License: CC BY-SA 4.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Oct 7, 2021 at 7:59 | history | edited | CommunityBot |
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
Mar 14, 2019 at 5:01 | comment | added | user66406 | Thank you. Your posts were very helpful! | |
Mar 13, 2019 at 13:11 | comment | added | rmalayter | The common case is for the key to be stored with whatever application the bank is using for lookups. These are typically server applications, and secure key storage is platform-specific. Sometimes even mainframe. But the key is kept and used only by a server on the banks side. Note the bank can also just store the mapping of account-> HMAC on their server and not expose the key to anything other than the system which generates the HMACs. | |
Mar 13, 2019 at 6:10 | comment | added | user66406 | I would appreciate your response to one other question. Where do banks store their private key typically? Let's say they have 1,000 bankers on 1,000 different desktop computers within a windows domain. If every one of them needs to query our database and needs access to the private key, do they store the private key using Windows Cryptographic Service Provider or a Certificate Store? If so, practically speaking if a malicious person has root control of a domain computer couldn't they get the private key? Is there a solution to this? | |
Mar 13, 2019 at 6:09 | comment | added | user66406 | I wanted to use encryption so that the Banker's could decrypt the Account Numbers on the client side. For example, if the banker executed an API call that returned a list of accounts using encryption he could determine which Account Numbers were returned without having to maintain a lookup table on the client side. | |
Mar 13, 2019 at 4:15 | history | edited | rmalayter | CC BY-SA 4.0 |
Link for HMAC
|
Mar 13, 2019 at 4:07 | history | answered | rmalayter | CC BY-SA 4.0 |