Re: Vulnerabilities when editing untrusted code...

[BrowserUk]

in reply to Vulnerabilities when editing untrusted code... (Komodo)

Use a sensible editor, instead of an operating system, to view and edit your source files. :)

[LanX]

I'm not using Komodo...

[BrowserUk]

Sorry. Beyond the name I've no knowledge of Komodo. I meant Emacs.

[LanX]

Which demonstrates your vi-gnorance ... as I wrote Emacs doesn't have this problem.

[rurban]

Every perl editor which tries to check for compile time errors and warnings (Komodo, Padre, emacs with flyspell using perl -c, vi?) need to put use Safe upfront, and no Safe at the end of the BEGIN or the begin of INIT.

This cannot be done within Perl generally as users need to execute BEGIN blocks, just not in editors.

The only remaining problem with Safe is then XS code, which might get executed at compile-time and cannot be checked for harm.

[BrowserUk]

Every perl editor which tries to check for compile time errors and warnings...

Which is one reason I don't use such editors. It's like sticking your finger in a power socket to check if it's live.

[Anonymous Monk]

It's like sticking your finger in a power socket to check if it's live.

Or to see if there are any wires in it, bad idea all around (ouch)

[LanX]

Hi Reini

I'm not sure what you mean... the editor should parse the code for all occurrences of BEGIN, CHECK and UNITCKECK and wrap each block with "use Safe" and "no Safe"?

Regarding the described problems to parse for such blocks I have no idea how to achieve this reliably withot adding a hook to Perl's parser.

Please see Intercepting compile time blocks like BEGIN {} for more detailed description of what I mean.