INDIGO SERVER REMOVE INSTALL
INDIGO SERVER REMOVE CODE
INDIGO SERVER REMOVE PASSWORD

This can cause a problem if I make an important change to the file, then before I release a new version including it, a user runs an existing update.

INDIGO SERVER REMOVE INSTALL

However, it seems that the installed file then ends up with a modification date and time that is when the install happened, rather than the original file's modification date. I have a file that is a Primer File, so it is saved in the TempLaunchFolder, then in On Post Install I copy it to my application directory with:įile.Install('%TempLaunchFolder%\ filename', '%AppFolder%\ filename') What I am working towards is a way a user can select several different options of their choice on the GUI so that when the program loads it will include those options.Īny ideas or advice will be most helpful - or if you can point me to documentation or previous posts, I'm happy to participate in my learning endeavor. I'm not talking about changing the text color - but the actual button color (or different button like 1043_0002.btn). I just want it to change color to show that it is selected. At this point, I don't need it to take any action - like load a page or open anything. My first obstacle is that I want a stock button (1044_0002.btn) that shows on my GUI to change to a different color (or same size different color button) when it is clicked. I am putting together a prototype GUI and program and I'm sure I will turn to all the talent here in the forum many times for advice and guidance. Last time I used AMS was version 6 (many years ago). Hope everyone has some fun with this thread. This one's a long-awaited 'redux' of an example posted in a related thread some time back - but with some core improvements and modifications - and with a new 'flag' to capture. So to get things started, below is the first of these capture-the-flag challenges. Am not saying this a 'rule' or anything (maybe you want some things kept secret) but is something I'd definitely encourage so that others can learn and benefit from the process. That is to say, after a challenge goes up and its 'flag' has been 'captured', I'd encourage the author of that challenge to follow up by posting the APZ from which the project was originally compiled. I'd also encourage 'follow up' for any CTF challenges which you post. So, the thread's open for anyone who wants to participate. And is also a great way to improve one's own skills and understanding when it comes to AMS and Lua programming in general.

It's a good way to gauge 'real world' effectiveness of any ideas you may have. And to then put those ideas to the test by inviting others to break that security. Or 'capture its flag' so to speak.Īpart from being good fun, the motivation here is to share different ideas about project security.

But the basic premise of the challenge remains the same - defeat the project's security mechanisms.

INDIGO SERVER REMOVE CODE

Or to simply capture the project's source code in its entirety.

INDIGO SERVER REMOVE PASSWORD

The challenge might be to capture a project's password or a hidden message. Its purpose is to act as a place where members can upload compiled projects which demonstrate the use of different techniques and ideas to improve project security.Ĭompiled projects should be posted as an open invitation and challenge for others to attempt to reverse-engineer. This thread is dedicated to 'capture-the-flag' challenges.

Indigo server remove