Author |
Topic |
|
seven
Senior Member
USA
1037 Posts |
Posted - 05 July 2001 : 12:41:54
|
I am looking for a method to upload a file using an ASP page thAa does not rely on a component or dll. I need to upload to a different website on a different server, seperate from where the page resides. Any ideas?
|
|
camusflage
Starting Member
USA
26 Posts |
Posted - 05 July 2001 : 17:54:14
|
If things haven't been too harshly locked down, you may be able to do a script host launched ftp session (if you're using ftp), or you may be able to instantiate an IE component to run an http post.
Mike
|
|
|
seven
Senior Member
USA
1037 Posts |
Posted - 09 July 2001 : 17:32:32
|
ummm... uhhh, I am still not sure what to do. |
|
|
camusflage
Starting Member
USA
26 Posts |
Posted - 10 July 2001 : 08:31:09
|
quote:
ummm... uhhh, I am still not sure what to do.
set wsh = server.createobject("wscript.shell") wsh.run "C:\winnt\system32\ftp.exe -s:<filename>"
filename is a file that contains commands to stuff into ftp.exe
BE CAREFUL WITH WSH. I cannot emphasize this enough. You can end up with orphan processes that even task manager can't touch. In these cases, you need kill.exe from the res kit to get rid of them.
Mike
|
|
|
George_Zhu
Starting Member
China
46 Posts |
Posted - 10 July 2001 : 08:54:10
|
Is this WSH unlocked? I mean will this command -- set wsh = server.createobject("wscript.shell") always working?
[font color=SlateBlue]Learning is all I want[/font] ----------------------- http://www.zhujie.org |
|
|
camusflage
Starting Member
USA
26 Posts |
Posted - 10 July 2001 : 19:41:22
|
quote:
Is this WSH unlocked? I mean will this command -- set wsh = server.createobject("wscript.shell") always working?
Like I wrote in my original message, it depends upon how tightly things have been locked down. It's pretty trivial to tweak the permissions on any component you want tor. I can tell you that if I were running a server which had anything less than completely trusted code on it, C:\WINNT\System32\wshom.ocx (wscript.shell) and C:\WINNT\System32\scrrun.dll (scripting.filesystemobject) would be the first things to get whacked. Just to prove a point, from an anonymous page(IUSR context), I created a wscript.network (?) object, dropped an existing drive mapping, added a new one, and then refreshed the admin-level explorer view from my terminal session. Beleive it or not, my drive mapping for my interactive session got changed by an anonymous web page. It all depends on your host though, as to what is installed and what is locked down. I'm pretty sure script host was IE4+, and since almost anything of the modern era on an NT server requires IE4, 5, and even 6 now, it's probably sitting there.
Mike
|
|
|
|
Topic |
|