Unhash online dating kalkofe rekalked online dating
Then again, in the real world, your data is never just a bunch of random dates.
Rather, the dates will be dates something, and might be associated with other data (names, descriptions, etc.) that could reveal any manipulation under close inspection. Some months see noticeably more births than others (for example, there's a notable peak in births in September, about 9 months after the Christmas holiday season), and there are also significant weekly trends (presumably because C-sections and induced labor are not usually scheduled for weekends) and sharp peaks and troughs around specific holidays (presumably for similar reasons).
We don't really know what your dates might be about, so let's just make a random guess and say that they're people's birthdays. A suspicious person could examine your birthday data and see if it matches these expected patterns.
If it does not, they might suspect that it has been encrypted, or otherwise tampered with.
For this simple cipher, this will also immediately reveal the key.
(A more complex format-preserving cipher would typically yield a frequency distribution that looks a lot closer to uniform than normal data would.
Well, they'd likely start the same way anyone breaking a simple amateur cipher would — with frequency analysis.
Just looking at the frequence distribution of the dates (assuming there are enough of them) should reveal information about the nature of the encryption; for the simple encryption scheme you describe, the distribution of birthdays by month will look the same as expected, except shifted by some number of months.
If you reused the key for multiple times for enough text, someone could potentially crack the message using something like crib-dragging.To encrypt application data, use the server-side encryption features of an AWS service, or a client-side encryption library, such as the AWS Encryption SDK or the Amazon S3 encryption client.