hacking contest

hacking exploits security forum
hacking
compliance articles
upgrade backup exec
information security consultant

Full Version: Executable Path's
Jay
When down loading tools etc they all say make sure they are in the executable path so the only way i seem to get them to work is by copying them to windows/sytem32 Is this the right way ?
ShadyCrazy1
Not sure what you mean..

But what I think your talking about Is downloading files to a FTP DIR , Which has its chmod settings, which is



admin user global*
read read read
write write write
exe. exe. exe.

and if these are set correct, it allows that FTP DIR to execute files..

This is probally off subject, But hope this helps ..

wink.gif
Rigpa
Since you referred to windows/system32 i take it you run a windows OS, maybe thatīll help a little :

most programs don't automatically add their executable path to the PATH: environment variable -- and the PATH: variable tops out at 1,023 characters in length. This length can be modified by a registry edit, but command-line sessions still truncate the variable to 1,023 characters. (This is not the total space devoted to environment variables, just the maximum size of any given variable.)

Fortunately there is a more sophisticated way to handle how Windows looks for executables. Open the registry key HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionApp Paths and create a new key (i.e. subfolder). The name of the new key can be anything you wish and is simply used to describe the app being pointed to in it. Within this new key will be a pre-created REG_SZ value with the name (Default). Edit its value to be the full path and filename to the executable you want to add. This change takes effect immediately.

Many programs, when installed, take advantage of this technique to add their executables and their directories to this list, so you may see examples from other installed apps in App Paths.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.

 
Invision Power Board © 2001-2005 Invision Power Services, Inc.