It's technically impossible to decrypt such passwords. As it should be,
that's the point.
Simply don't display existing passwords in views.
--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and
Sounds like a server with a Plesk control panel?
There is an option to serve both standard and SSL pages from the same
directory. If you can't set that, you'll have to duplicate your code in both
httpdocs and httpsdocs folders. Now, that perhaps might have some
consequences in regards to cache
In my experience, protecting PHP code is a pain. Two best known
solutions are Zend Guard and ionCube. Both require special PHP
modules, but these are quite common on hosting servers.
AFAIK, ionCube has provided the most secure solution in the past. It's
also quite affordable when compared with
I've often been scratching my head while looking at software such as
osCommerce, which is now at v2.2 RC 2a, and back in 2003 it was at
v2.2 Milestone 2. LOL
Ah, well... I guess there is limited space for humour in software
development, so why not.
But CakePHP doesn't strike me as such a
