TGOS wrote:
For the foreseeable future (next few decades, imo) this should be the least of your worries. This is my personal opinion, of course, based on a bit over a year of doing quantum computing research....(and a quantum computer may be able to solve it pretty fast)
What gave you that idea? See http://www.alvestrand.no/objectid/ (result of a 10-second google search that seems to be fairly relevant). OIDs can be used to refer to many things _including_ crypto algorithms.OIDs are S/MIME Object IDs and MIME is a mail standard. Why is a mail standard used to encrypt webpage passwords?
It is your right to choose a language poorly suited to the task you wish to accomplish, of course. No one is going to try to stop you.Doesn't matter. What if I want to write the code in a scripting language that can't access any external libraries?
You're assuming the intent is to give people access to the data. On the contrary, the intent is to keep the data secure. For example, the method you propose is very vulnerable to dictionary attacks on the master password. So a better method would be desirable.Just writing all data into a simple text-only or XML format and encrypting everything with Cast/IDEA/Twofish/Serpent, using a key generated as MD5 checksum of the master password will guarantee access to all of it's data by all kind of applications, scripts or whatever else without the need to be allowed to execute native code or to force people to first several thousand lines of code into the used language.
Like Nelson, I feel I must bow out of this discussion, which is clearly going nowhere... the fact that you didn't bother to do a careful search on what OIDs are is pretty indicative, imo.
