Title: JS++ Suggestions
blakeo_x - October 17, 2005 12:12 AM (GMT)
One of my projects, JS++, may cause problems with IF boards even though the code runs client-side. If you would like to read about what this code will do, you can read my
Devlog Entry about it.
Please read through the list of suggestions already brought to my attention below. If you know of a potential problem not included in the list, please post a reply to this topic explaining what the problem is and how you think it can be fixed.
Suggestions
Death - November 7, 2005 02:30 AM (GMT)
ahem...i kno kinda late, but...it just hit me now as I was browsing...if u do that, then you are going to have users that modify their info on the hacks on every page load...and...if u were to do that, admins everywhere would be kinda annoyed...because u kno as soon as someone leaked that, lets use an oldschool example, in RPG Inferno you can edit your stats through codes...and you could set it to auto-heal you, and you could make it auto-battle for you, thus like botting, you would have everyone and their dog using the hacks.
Paper - November 7, 2005 09:02 PM (GMT)
I think that it is a good idea. However, the admin should be able to select between different security levels to ensure proper security.
Prehaps you could also code it to accept links to "modules" that just plug in.
blakeo_x - November 7, 2005 10:08 PM (GMT)
Good points/ideas. I plan to put in a variable disallowing system so you cant set variables already in use by other codes. What else would you propose I do to ensure secure use of this code?
Epsilekt - November 8, 2005 02:14 AM (GMT)
That is a BIG NO! NO!
I have many scripts that use functions to change important things. Creating this code could allow users to change too many things. Like, for instance, say I used a cookie to log some data, they could write document.cookie = and change the whole thing and screw everything up.
blakeo_x - November 8, 2005 06:20 AM (GMT)
Exactly why I have this topic. Thanks for the input! :yes:
See, what I plan to do is set up a filter so only certain JavaScript functions, variables, operations, etc. can be accessed through this code. I think it would be pretty simple to set up a cookie filter.
I can see cookies are definately a security risk, so they are out of the picture.