...$$$ to them.
...$$$ to them.
...not the symptoms.
If you want your files encrypted 'at rest' so that if someone comes and pulls your HDD (or software equivalent) then you can implement a strategy similar to:
(a)Encrypt all content with individual symmetric keys (one key per piece of content) - prefix each piece of content with a key ID (for key lookup on exit) - there are many ways to associate content with a key - prefixing is just the simplest
(b)Encrypt those keys (which you'll need stored locally for performance reasons) with a randomly generated one-time pad stored on a removable hardware device (HSM/USB for example)
(c)Decrypt files as appropriate as they exit your webserver - observe the key ID of the content, ask a process on your machine to give you the symmetric key for that ID, decrypt the content, send it back to the requesting connection.
Don't store the master key and/or one time pad locally, simply have a daemon/service/long running process on your web server require (at startup) you to plugin your hardware device (e.g. read a file from a mount that is only there when you plug the thing in.) This means that stealing the content doesn't do them much good (if they crack a key it's only for that particular piece of content, they'll have to crack lots of keys), and if they get the locally stored symmetric key file it doesn't do them much good either because you're protecting that with a VERY strong key and/or cipher which is stored air-gapped - they'd have to not only steal all the files involved, they'd have to inject into the service/daemon that issues symmetric keys.
This type of approach has performance implications of course, and to make it truly close to unbreakable requires more specifics (process injection prevention, signing and impersonation attack prevention, both on the key request side and the service/daemon unlocking scheme, et cetera) - this would be quite a discouraging system to attempt to break.
My $0.02, YMMV
About two seconds of googling. I'm sure that, if I gave a sh** about Kurzweil, I could come up with dozens and dozens examples of his horsesh** that hasn't happened...
I will admit that on a few occasions I have encrypted something I could then later not decrypt...
He's the absolute king at predicting stuff that never happens. He's always talking 10 years ahead - everything with him is "In , is going to happen..."
He's absolute crap - he reminds me of guys who talk all kinds of bollocks about crypto and don't actually understand modular arithmetic
Ridiculous. You can run nVidia installs silently on Windows if you choose. I have also seen executable based installers on Linux that show advertisements.
It's the same silly argument where people blame Microsoft for all BSODs when, again nVidia being the majority culprit, bad drivers are the root cause - then people like yourself say "well, Microsoft should build a driver model that doesn't allow for BSODs."
That's kind of funny because I had heard there were problems with vs 2012 - especially the betas, but they'd been fixed by the time is moved to it. That was about 8 months into it's lifecycle. Never experienced your problems - again, on all the OS variants I have to support today. Kind of curious that you're using vs 2012 when it's 2017 and anyone who paid for MSDN was eligible for 2013. If you're using the express version, that's even weirder. I'm not aware of any libraries or frameworks that are stuck on vs 2012. Almost seems unbelievable...
Visual Studio crashes on a whim? Weird, I use it every single day across multiple machines and virtual machines (Win 7,8.1,10, x86 and x64) when debugging Qt applications, and for writing tools for the Windows side of the house - the last crash I experienced was in a 3rd party plugin for Visual Studio 2010 over 5 years ago. I've been using it on the Windows side for decades (all the way back to Visual C++ 1.5 days when I used it and Borland C++) and never had problems with crashing (not that it never crashed, but it rare.)
You put in one code for your phone, you put in another code to get some default boring ass phone image with banal information.
Seriously? "Man dives through plate glass window" "In other news, band-aid sales have skyrocketed recently..."
I guess you missed the "for example." Rather than talk about the differences between 72, 80, and the various flavors along the way and their shortcomings - I pointed out something small but important that counters the silly article's "SmallTalk is the magic bullet!" voice.
I still think SmallTalk is cool, and in 85 it was SERIOUSLY cool (image based persistence? Awesome...) Like all other languages - it has issues.
Easy with the hype
SmallTalk is cool - and for its time it was incredible really - but it has warts that have held it back forever (including the stupidify of the major players in the market.)
For example - algebraic precedence. When 5 + 5 * 5 = 50 - you're going to have problems with adoption.
In any case - it's a nice shiny hammer. You should have it next to all your other hammers in the toolbox.
The power to destroy a planet is insignificant when compared to the power of the Force. - Darth Vader