Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#1465 closed Feature Request (Rejected)

Proxy functions or udf

Reported by: e1m1 Owned by:
Milestone: Component: AutoIt
Version: Severity: None
Keywords: proxy, packets Cc:


Hello, I just got idea for new autoit funcs, (Maybe it can be done as UDF too). Sorry for my bad english, if something here is unclear, PM me.

Make UDF tat allows to create proxy. Proxy funcs would allow other programs to connect trough proxy so that autoit could play with packets.These funcs would enable creating script that could aout answer in msn/irc/skype (or block messages like "hi, visit me at" it could be also usde to block some games like runescape cuz if u block packet sent to client when u click on logon button then it would be impossible to play that game. it other workds it would make school/library/coffee administrators work easier.

just some ideas about how func could look like.

$sPacket - binary or string
creates proxy so that app can connect to server trough proxy
dumpckets 0 = no dump, 1 = dump incoming to txt file 2 = dump out going to txt file 3 = dump both incoming and outgoing packets to txt file.

Should wait until given packet comes but let trough all aother packets so that net app would still work.
it should match packets from beginning so that PacketWait(0x3c) would continue autoit when packets even if packet is 0x3c0.
iDirection if 0 should wait for incoming packet, and if 1 should wait for outgoing packet.(or it can be also devided onto 2 func)

would send packet to client,server or both.

This func would block packets. if iDirection = 0 then would block incoming, if 1 would block outgoing, and if 2 would block both
if iAdd = 0 then remove packet from block list
if iAdd = 1 then add packet to blocklist.

auto call user defined function when given packet appears. Should not forward package to clinet/server (because we might want edit packet before forwarding it and if we want forward it, we could use other funcs) but it shouldcall UDF giving packet as parameter, iDirection would tell for which direction packets it should act for (wether it is client --> server or server <-- client)
sFunc would be function name to call

would set packet match mode
0 would match packet from beginning (0x3c would alsowork if packet is 0x3c01)
1 would match entire packet (if packet is 0x3c01 but we are waiting for 0x3c then it won't react

for any questions PM me.
Thanks for reading.

let me know waht do you think about it.

Attachments (0)

Change History (4)

comment:1 Changed 14 years ago by Valik

  • Resolution set to Rejected
  • Status changed from new to closed

Just... no.

comment:2 Changed 14 years ago by anonymous

why not?

comment:3 Changed 14 years ago by Valik

First of all, there's no way in hell ANYBODY should want their packets passing through AutoIt because of how slow it is. If that alone isn't a good enough reason, then how about because it's a not a general purpose need? Very few people need such functionality and fewer still have a legitimate use for it. Furthermore, you can write application-specific proxies using AutoIt in it's current form.

comment:4 Changed 14 years ago by anonymous

I respect your decition and thanks for good explanation.

Guidelines for posting comments:

  • You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
  • In-depth discussions should take place on the forum.

For more information see the full version of the ticket guidelines here.

Add Comment

Modify Ticket

as closed The ticket will remain with no owner.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.