Re: how decrypt password in view?
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 help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Re: SSL help
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 & sessions? Don't know... Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: 1.3 on a production server?
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 software. So... as much as I'm tempted to switch existing and future applications to 1.3 ASAP, I've decided to wait. Once 1.3 is designated as beta or RC, I'll reconsider... On Jan 12, 8:51 pm, Jamie wrote: > Fair enough. In that case, why the 'alpha' designation? What does that > mean for CakePHP, and how does it differ from 'beta'? If the alpha > release is so stable and has been publicly released, then I can't > figure out why it's called alpha and not beta. > > On Jan 12, 11:02 am, "Larry E. Masters aka PhpNut" > wrote: > > > Why would I be sarcastic? How you follow the CakePHP project for any length > > of time? You will notice the alpha releases are more stable then most > > projects stable versions. > > > -- > > /** > > * @author Larry E. Masters > > * @var string $userName > > * @param string $realName > > * @returns string aka PhpNut > > * @access public > > */ > > > On Tue, Jan 12, 2010 at 12:57 PM, DanielMedia > > wrote: > > > > Just checking if you were being sarcastic Larry? > > > > On Jan 11, 8:20 pm, "Larry E. Masters aka PhpNut" > > > wrote: > > > > Yes all client work is on 1.3 > > > > Check out the new CakePHP Questions sitehttp://cakeqs.organdhelp others > > > with their CakePHP related questions. > > > > You received this message because you are subscribed to the Google Groups > > > "CakePHP" group. > > > To post to this group, send email to cake-php@googlegroups.com > > > To unsubscribe from this group, send email to > > > cake-php+unsubscr...@googlegroups.comFor > > > more options, visit this group at > > >http://groups.google.com/group/cake-php?hl=en Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: How to secure product code in a client installation
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 Zend Guard. I haven't checked if it's protection has been broken, though, so you might want to look into this before purchasing. There were some hints that it was broken a couple of months back, but I couldn't find an actual proof. Everything else is even worse than Zend Guard... and Zend Guard protected applications can easily be decompiled at the moment. There are other solutions but some of them are a complete joke - I did an extensive research some months back and couldn't find anything else really worth mentioning. I'd say the best protection is one of the above solutions, combined with the complexity of your application. Once you have thousands of lines of code, without comments, etc Well hackers, good luck stealing that, continuing development, providing support, etc. :) Anyway, if you find a better solution, I'd be glad to hear about it. On Jan 13, 3:21 am, IRoute wrote: > I want to develop a product using CakePHP which would be installed on client > machines. How to develop the product using CakePHP in such a way that the > code cannot be pirated, modified and used as a different product. Thanks in > advance for any suggestions. > -- > View this message in > context:http://old.nabble.com/How-to-secure-product-code-in-a-client-installa... > Sent from the CakePHP mailing list archive at Nabble.com. Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
