I found a security hole in the compiler

[UEZ]

I'm missing right now the ^click^ action...

Br,

UZ

[orbs]

  On 8/16/2013 at 9:45 AM, Mobius said:

Jeez op just modify the 'AutoIt Error' and 'unable to open the script' references that are stored in the STRINGTABLE resources of the interpreter if you are really that concerned.

Security hole, what a joke.

 

i was not aware of this option, can you please elaborate on how this is done? thanks

[James]

No you didn't.

[Edano]

  On 8/16/2013 at 8:46 AM, JohnOne said:

If the error message were to appear to come from user script name, It would be less than accurate.

I have no strong opinions about it really,  but I have not seen a single reason I would consider valid to make such a change.

Also think about this, if autoit interpreter cannot open user script, how exactly would it know the title of it?

.

it could be a suggestion to use AutoItWrapper directives to create a customized error message. if you do not use the directive, it stays default.

E.

and i repeat, i don't think it's a security hole, i am not paranoid or concerned, it is just a feature suggestion. and i agree that the op is a joke, but not this suggestion

Edited August 16, 2013 by Edano

[James]

  On 8/16/2013 at 10:03 AM, Edano said:

.

it could be a suggestion to use AutoItWrapper directives to create a customized error message. if you do not use the directive, it stays default.

E.

What is the need?

[JohnOne]

  On 8/16/2013 at 9:34 AM, orbs said:

 

 

au3 script has no "title", the intention is to use the exe file name.

 

 

reason 1: so the user knows from which application the error message is coming. if you have several exe's running, then providing the exe name is a good start for troubleshooting. and even more so if you have several compiled AutoIt exe's running.

reason 2: although this is far from being AutoIt fault, or relevant in anyway, and happily in decrease, the name resembles the autoit worm which swarmed the web few years back. you don't want to scare your users, do you?

Reason 1: your script would not be running, this was the whole point of the thread it errors out when you try to start it.

Reason 2: if your users are tampering with the compiled script, why care?

It's already been pointed out that critical errors due to bad code can be handled, by a few people, including myself, I still don't see valid reason for anything else.

[Edano]

  On 8/16/2013 at 10:05 AM, James said:

What is the need?

.

what is the need of having a user chosen default icon ? nevertheless it was implied at some point.

 

Edit: it's simply nice.

Edited August 16, 2013 by Edano

[James]

  On 8/16/2013 at 10:14 AM, Edano said:

.

what is the need of having a user chosen default icon ? nevertheless it was implied at some point.

Please stop using full stops at the beginning of a sentence.

A configurable icon is a different thing altogether.

[JohnOne]

Say your exe was named "SuperSecret.exe"

What would the message say?

SuperSecret cannot open SuperSecret ?

haha

[orbs]

@JohnOne, i agree critical errors can and should be treated inside the code. we all strive for robust code, but things do get overlooked, and hardware issues may also cripple the script. also, the error may occur anytime while the script is running, not necessarily at start. still my point is it's friendlier that such msgbox's carry the script exe name rather then the generic "AutoIt" title. and if it's editable as Mobius suggested, then that's fine.

[James]

  On 8/16/2013 at 10:20 AM, JohnOne said:

Say your exe was named "SuperSecret.exe"

SuperSecret cannot open SuperSecret ?

John, that's not even a good reason. The reason this doesn't need to be done is simply the fact that there is no decent reason for it to be. If it was that good of an idea, Valik/trancexx would've made this happen when they had the chance.

[JohnOne]

  On 8/16/2013 at 10:20 AM, orbs said:

@JohnOne, i agree critical errors can and should be treated inside the code. we all strive for robust code, but things do get overlooked, and hardware issues may also cripple the script. also, the error may occur anytime while the script is running, not necessarily at start. still my point is it's friendlier that such msgbox's carry the script exe name rather then the generic "AutoIt" title. and if it's editable as Mobius suggested, then that's fine.

I am only talking about the thread first post.

Once again other unforseen runtime critical errors can be handles in the way you want 

[Edano]

  On 8/16/2013 at 10:17 AM, James said:

Please stop using full stops at the beginning of a sentence.

A configurable icon is a different thing altogether.

.

no

[orbs]

  On 8/16/2013 at 10:22 AM, James said:

John, that's not even a good reason. The reason this doesn't need to be done is simply the fact that there is no decent reason for it to be. If it was that good of an idea, Valik/trancexx would've made this happen when they had the chance.

 

@ James, are you implying that "normal" users can not suggest new ideas? i'm not sure if i should be insulted or flattered 

[James]

  On 8/16/2013 at 10:29 AM, orbs said:

@ James, are you implying that "normal" users can not suggest new ideas? i'm not sure if i should be insulted or flattered 

No, that's not what I'm saying.

[JohnOne]

For reference

>This UDF handles critical errors that do not involve a compiled having been altered.

Still don't see a real need for what the OP wants though.

[James]

  On 8/16/2013 at 10:32 AM, JohnOne said:

For reference

>This UDF handles critical errors that do not involve a compiled having been altered.

Still don't see a real need for what the OP wants though.

That's what I was trying to find. (Y)

[Edano]

  On 8/16/2013 at 10:32 AM, JohnOne said:

For reference

>This UDF handles critical errors that do not involve a compiled having been altered.

Still don't see a real need for what the OP wants though.

.

'?do=embed' frameborder='0' data-embedContent>>

i just re-found this.

[Jos]

  On 8/15/2013 at 10:19 PM, gil900 said:

reed for example Edano posts.

But maybe that's not a problem ..

Anyway, i do not really care about it.

If you don't care then stop posting about it.

*Click*