z0r0
Dec 2 2003, 02:09 PM
looked all through the foums and never seen anything about compileing a exploit thats perl with cygwin, could someone tell me if this is possible, and what the cmd is, iv seen things like "chmod -x ***.pl" but i try that in cygwin and get "no such file or directory" iv added the file to the root directory of cygwin and still says that.
coder
Dec 2 2003, 02:20 PM
chmod changes the permissions of a file!
http://www.mkssoftware.com/docs/man1/chmod.1.aspin order to compile perl, you need a perl compiler (there are several compilers posted on GSO, search!) some, now i'm not sure- but i'm pretty sure that some Perl interpreters can compile src code into binaries (for *nix) using some of the common switches- i've been googling around , but can't seem to find anything to back this up right now.
now, why do you have to run it in cygwin, does it make use of any special *nix libraries? Perl by nature should be cross-platform
z0r0
Dec 2 2003, 02:30 PM
hmmmm that part isnt needed..the CHMOD
searched all over these forums for a Perl interpreters cant seem to find anything about one, im gunna keep searching google for diff things.
coder
Dec 2 2003, 03:32 PM
http://www.governmentsecurity.org/forum/in...?showtopic=4695There you go, now next time- try actually searching for something
It was on the first page of the "File Downloads" section!
-take it easy
z0r0
Dec 2 2003, 03:49 PM
Sorry, an error occurred. If you are unsure on how to use a feature, or don't know why you got this error message, try looking through the help files for more information.
The error returned was:
You do not have permission to view this topic
hmmmms think im still on a "trial membership" i dont even see the files section....Prally why search turned up nada
coder
Dec 2 2003, 04:14 PM
I apologize, that was my mistake
PM me and I will send you a copy!
Yorn
Dec 2 2003, 04:49 PM
perl2exe sucks. Use the cygwin command: "perlcc nameofscript.pl"
You'll have to include two .dlls, but it is worth it if you love to code in PERL.
z0r0
Dec 2 2003, 04:59 PM
thats what i was looking for! the cmmds for cy, are these 2 dll's i need downloadable anywhere? although "Perlcc: command not found"
coder
Dec 2 2003, 05:20 PM
| QUOTE (Yorn @ Dec 2 2003, 04:49 PM) |
perl2exe sucks. Use the cygwin command: "perlcc nameofscript.pl"
You'll have to include two .dlls, but it is worth it if you love to code in PERL. |
why does it suck?
why is compiling Single executables not as good as compiling binaries that require large/bulky dll's ? I'm just curious (not trying to argue
)
andydis
Dec 2 2003, 06:34 PM
http://burks.bton.ac.uk/burks/language/per...tut/running.htmthats all you need to know there, if you try running perl and it says command not found then run cygwinsetup again and choose the option to add everything, id advise that it comes with loadsa kewl stuff
:-)
Bl00r
Dec 2 2003, 09:33 PM
try ActivePerl
| QUOTE |
| ActivePerl is ActiveState's quality-assured distribution of Perl, available for Linux, Solaris, and Windows. As part of ActiveState's support for Perl, we provide the ActivePerl packages free to the Perl community. |
damulint
Dec 8 2003, 02:43 AM
I used to Activestate..
Same opinion Bl00r..
With using Nikto web Scanner..
w00dy
Dec 8 2003, 03:19 AM
Back to the original post, perl scripts do not need compiling. They are like .bat files. the 'chmod -x ***.pl' is the command to make that perl file executable (on *nix system). All you need to run the perl script is a perl interpreter such as the one found at www.perl.com . Then open a command prompt and type the file name and any options needed.
I think the perl binary @ perl.com is the combination of active states and the real perl interpreter.
Andy
Dec 8 2003, 04:33 AM
were u able to get boomerang to work with active perl on win platform?
Yorn
Dec 8 2003, 05:38 PM
| QUOTE (coder @ Dec 2 2003, 11:20 AM) |
why does it suck?
why is compiling Single executables not as good as compiling binaries that require large/bulky dll's ? I'm just curious (not trying to argue ) |
I rarely can get socket programming (or much else) to work with most perl compilers. That's why I think converting to C first is almost imperative. That is an extra step of work, but having two DLL files isn't horrible at all.
The reason *why* I like DLLs is because if you are creating PERL scripts for installation on a remotely controlled machine or your own, I find that having a couple dll files that are a couple meg and 15 files that are only like 20kb are better than having 15 files that are 300kb each.
I guess it is more personal preference and what the intended purpose of the machine is.
Tx_
Dec 17 2003, 02:02 PM
sorry cant help u there
Tx_
Dec 17 2003, 02:04 PM
but its all fun
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.
