aaroncampbell
Hi there, actually I am just partly agree with dutchfoxer.
Yes, Flash is very insecure in someway. Because it can be easily decompiled by some applications in the market. And after decompiling, the user can browse all the scripts inside Flash.
However Flash is good in a certain way. Let's say, Flash itself cant be refreshed. This can totally prevent multiple execution of some server side script using Refresh.
As long as you dont put the authetication part inside Flash, then it will be perfect.
My suggestion is like this.
Use Flash to build the login interface.
When login, use PHP to do the authentication.
And inside PHP, store the login information inside session.
Finally, all the other forthcoming PHP have to check the session.
(e.g. inside the admin_movie.php, check whether a session present, if yes, then echo the movie url back to Flash)
By this, I think it is already secure enough.
Cheers :)
Vicker
Main Topics
Browse All Topics





by: dutchfoxerPosted on 2005-10-04 at 17:14:39ID: 15018586
You know that people can unlock a SWF movie and see the actionscript inside? They can. So they could see the actionscripts on all the different keyframes. Would they also see the passwords? No, because it is not in the flash file.
arch.php?p er=10&page =1& field=D escription &cat=movie s&term=log in
Would they be able to jump to keyframe3 without loggin in? Yes. Without having the FLA file I could change the actionscript to jump to keyframe nr 3 -> gotoAndStop(3)
Flash is not secure in that way.
So I would turn things around. After they log in correctly they get to see your flash admin page. If not, no Flash file whatso-ever. So the HTML-file holding the flash is behind a secured access / directory. That would be savest.
Tutorials... not really. There are some examples of flash-files for loggin in.
Heres many downloadable FLA's with login functionality. Some are very creative in hiding actionscript etc:
http://www.flashkit.com/se
Good luck!