Shoutbox

Automatically block specific transfer requests (suggestion) - Printable Version

-Shoutbox (https://shoutbox.menthix.net)
+-- Forum: MsgHelp Archive (/forumdisplay.php?fid=58)
+--- Forum: Messenger Plus! for Live Messenger (/forumdisplay.php?fid=4)
+---- Forum: Scripting (/forumdisplay.php?fid=39)
+----- Forum: Plug-Ins (/forumdisplay.php?fid=28)
+------ Thread: Automatically block specific transfer requests (suggestion) (/showthread.php?tid=40945)

Automatically block specific transfer requests (suggestion) by frankiedaman on 03-22-2005 at 11:39 PM

Hiya, i have a small suggestion for a plugin or maybe for the next messenger plus update.

As you may all know, Bropia, Serflog and other MSN viruses are rampant over the networks on MSN Messenger. A lot of contacts on my lists just accept anything they get, fools. And at least 5 -10 times a day they are constantly sending me viruses under their numerous aliases (e.g. Crazy frog gets killed.pif, Mona lisa wants her smile back.pif)

A great idea would be to have something to block these transfer requests in advance so that not only would people accept them thinking it was harmless content, but to stop these numerous requests from infected individuals which constantly annoy people.

It could work in the form of a filename blocklist. Just an idea :)

What do ya think? :)


RE: Automatically block specific transfer requests (suggestion) by mwe99 on 03-22-2005 at 11:43 PM

I thought that too :) to stop you automatically accept .pif files! Wonderful idea and i don't imagine it would be too difficult?


RE: Automatically block specific transfer requests (suggestion) by Ezra on 03-22-2005 at 11:45 PM

There are new plugins coming that do this...

Don't really remember the names :-S...

Something PifBlock..

Nah, i don't know... it's late


RE: Automatically block specific transfer requests (suggestion) by Plik on 03-23-2005 at 12:06 AM

The new leaked beta (7.0.732) blocks the following filetypes

quote:
Originally posted by mess.be
Exe (executable), Com (executable), Scr (screensaver), Bat (batch file), Pif (MS-Dos executable), VBS (Visual Basic Script), JS (Java Script), HTA (HTML Application) Reg (Windows Registration), msi (Microsoft Installer)

RE: Automatically block specific transfer requests (suggestion) by mwe99 on 03-23-2005 at 12:08 AM

Oooh MSN 7.0.732 :D yay! I have that but didn't know it blocked those.. although i now can't send MSN Messenger to people over MSN but i rarely do anyways :)


RE: Automatically block specific transfer requests (suggestion) by CookieRevised on 03-23-2005 at 03:07 AM

quote:
Originally posted by Madman
The new leaked beta (7.0.732) blocks the following filetypes
quote:
Originally posted by mess.be
Exe (executable), Com (executable), Scr (screensaver), Bat (batch file), Pif (MS-Dos executable), VBS (Visual Basic Script), JS (Java Script), HTA (HTML Application) Reg (Windows Registration), msi (Microsoft Installer)

Indeed, and from what I've heared this feature is one of the least welcomed features since a very very very long time... It is very good that MS tries to do something about the virusses (Y). But it isn't good if this "feature" would be build in and no way to turn it off. MSN will loose a lot of 'above-average' MSN users... Only time will tell...

On a very personal note: if this feature would be build in without the ability to turn off, I'm strongly wondering who the *beeeep* n00b was that suggested this to MSN... And who was the n00b then to forget to include all the other extensions which can be run automatically. Luckely this is still in private beta hands only, so we have to wait until this "feature" matures to see what's up with this...
RE: Automatically block specific transfer requests (suggestion) by TheBlasphemer on 03-23-2005 at 06:33 AM

quote:
Originally posted by CookieRevised
quote:
Originally posted by Madman
The new leaked beta (7.0.732) blocks the following filetypes
quote:
Originally posted by mess.be
Exe (executable), Com (executable), Scr (screensaver), Bat (batch file), Pif (MS-Dos executable), VBS (Visual Basic Script), JS (Java Script), HTA (HTML Application) Reg (Windows Registration), msi (Microsoft Installer)

Indeed, and from what I've heared this feature is one of the least welcomed features since a very very very long time... It is very good that MS tries to do something about the virusses (Y). But it isn't good if this "feature" would be build in and no way to turn it off. MSN will loose a lot of 'above-average' MSN users... Only time will tell...

On a very personal note: if this feature would be build in without the ability to turn off, I'm strongly wondering who the *beeeep* n00b was that suggested this to MSN... And who was the n00b then to forget to include all the other extensions which can be run automatically (eg: screensavers). Luckely this is still in private beta hands only, so we have to wait until this "feature" matures to see what's up with this...

Don't worry :P
StuffPlug is here to rescue ;)
RE: Automatically block specific transfer requests (suggestion) by (CyBeRDuDe) on 03-23-2005 at 08:57 AM

quote:
Originally posted by TheBlasphemer
quote:
Originally posted by CookieRevised
quote:
Originally posted by Madman
The new leaked beta (7.0.732) blocks the following filetypes
quote:
Originally posted by mess.be
Exe (executable), Com (executable), Scr (screensaver), Bat (batch file), Pif (MS-Dos executable), VBS (Visual Basic Script), JS (Java Script), HTA (HTML Application) Reg (Windows Registration), msi (Microsoft Installer)

Indeed, and from what I've heared this feature is one of the least welcomed features since a very very very long time... It is very good that MS tries to do something about the virusses (Y). But it isn't good if this "feature" would be build in and no way to turn it off. MSN will loose a lot of 'above-average' MSN users... Only time will tell...

On a very personal note: if this feature would be build in without the ability to turn off, I'm strongly wondering who the *beeeep* n00b was that suggested this to MSN... And who was the n00b then to forget to include all the other extensions which can be run automatically (eg: screensavers). Luckely this is still in private beta hands only, so we have to wait until this "feature" matures to see what's up with this...

Don't worry :P
StuffPlug is here to rescue ;)
If this feature can't be disable I think M$ will get some very angry emails!!! :P...
Yes, we will just wait, hopefully the betatesters can tell m$ about this.. :D...
Stuffplug is here to rescue??? You already did it? You already did get passed the protection? :O
RE: Automatically block specific transfer requests (suggestion) by RaceProUK on 03-23-2005 at 09:56 AM

The latest leaked beta may have that feature added with no obvious way to turn it off, but I would have thought there'd be something hidden deep down that will turn it off.
Anyway, if someone really does want to send an executable, then they just ZIP it.


RE: Automatically block specific transfer requests (suggestion) by (CyBeRDuDe) on 03-23-2005 at 01:14 PM

quote:
Originally posted by raceprouk
The latest leaked beta may have that feature added with no obvious way to turn it off, but I would have thought there'd be something hidden deep down that will turn it off.
Anyway, if someone really does want to send an executable, then they just ZIP it.
I don't want to zip a single exe file everytime I have to send a exe file to someone!.. That's crap!!!... I am a programmer and many of my contacts on msn help me out testing stuff on different systems, I don't want to zip the exe file each 5 minuttes i've done something new in the program to see if it works...
I don't want to Compile -> Zip -> send and then on the other side -> Extract -> Run... The zip and extract part is not needed... I fM$ doesn't change this or some patch pr whatever is able to change this, then I'm NOT gonna update!!!!... The idea of blocking files is ok, but then they at least needs a enable/disable, only block .xxx files, etc... If they don't do this!!! Then they can go f**k them selfs!...
And now people are going to say: "If you don't want to zip and extract, just rename the file to another filename and then send it, and the other person just renames it back to .exe..."... Yes of course this is correct!.. But I don't want that, it should all just be plain and simple, send, recieve, run... I don't need no stinky Blocker to control what I should send/recieve....
But ok, lets see where this is heading, hopefully m$ will of course make a config screen for this... :D... this is just a beta only avaible to a few people (officially! :P) so many things can still change...
RE: Automatically block specific transfer requests (suggestion) by Mike on 03-23-2005 at 01:31 PM

quote:
Originally posted by (CyBeRDuDe)
quote:
Originally posted by raceprouk
The latest leaked beta may have that feature added with no obvious way to turn it off, but I would have thought there'd be something hidden deep down that will turn it off.
Anyway, if someone really does want to send an executable, then they just ZIP it.
I don't want to zip a single exe file everytime I have to send a exe file to someone!.. That's crap!!!... I am a programmer and many of my contacts on msn help me out testing stuff on different systems, I don't want to zip the exe file each 5 minuttes i've done something new in the program to see if it works...
I don't want to Compile -> Zip -> send and then on the other side -> Extract -> Run... The zip and extract part is not needed... I fM$ doesn't change this or some patch pr whatever is able to change this, then I'm NOT gonna update!!!!... The idea of blocking files is ok, but then they at least needs a enable/disable, only block .xxx files, etc... If they don't do this!!! Then they can go f**k them selfs!...
And now people are going to say: "If you don't want to zip and extract, just rename the file to another filename and then send it, and the other person just renames it back to .exe..."... Yes of course this is correct!.. But I don't want that, it should all just be plain and simple, send, recieve, run... I don't need no stinky Blocker to control what I should send/recieve....
But ok, lets see where this is heading, hopefully m$ will of course make a config screen for this... :D... this is just a beta only avaible to a few people (officially! :P) so many things can still change...
Yep, I was also thinking the same when I read the news at mess.be.

TB, please, do your stuff :)
We count on you!

M$ should at least make an registry option to disale this...

I never got any virus via msn... ^o)
RE: Automatically block specific transfer requests (suggestion) by RaceProUK on 03-25-2005 at 08:13 PM

quote:
Originally posted by (CyBeRDuDe)
quote:
Originally posted by raceprouk
The latest leaked beta may have that feature added with no obvious way to turn it off, but I would have thought there'd be something hidden deep down that will turn it off.
Anyway, if someone really does want to send an executable, then they just ZIP it.
I don't want to zip a single exe file everytime I have to send a exe file to someone!.. That's crap!!!... I am a programmer and many of my contacts on msn help me out testing stuff on different systems, I don't want to zip the exe file each 5 minuttes i've done something new in the program to see if it works...
I don't want to Compile -> Zip -> send and then on the other side -> Extract -> Run... The zip and extract part is not needed... I fM$ doesn't change this or some patch pr whatever is able to change this, then I'm NOT gonna update!!!!... The idea of blocking files is ok, but then they at least needs a enable/disable, only block .xxx files, etc... If they don't do this!!! Then they can go f**k them selfs!...
And now people are going to say: "If you don't want to zip and extract, just rename the file to another filename and then send it, and the other person just renames it back to .exe..."... Yes of course this is correct!.. But I don't want that, it should all just be plain and simple, send, recieve, run... I don't need no stinky Blocker to control what I should send/recieve....
But ok, lets see where this is heading, hopefully m$ will of course make a config screen for this... :D... this is just a beta only avaible to a few people (officially! :P) so many things can still change...
That's where free webhosting can be helpful - every time you update, upload, then get people to download. Probably faster than MSN P2P transfers anyway.
RE: Automatically block specific transfer requests (suggestion) by crank on 03-25-2005 at 08:19 PM

The protection isn't so hard (from what i've seen...) it's usgin the files that some windows setting blocks (you can see it on winxp pro i think not in the home edition anyways (:() and you can just clear that list though it's best you don't cuz that list is not just for msn...
something using shlwAPI ;)

Not that i know what to do with it or how to do it (:( can't program)


RE: RE: [updated 01/04/05] A-Paatch v1.08 - Removed File Protection by DJHasis on 04-05-2005 at 12:08 PM

quote:
Originally posted by Ahmad
Added a new feature "Remove File Transfer Protection" for version 7.0.0732 - thanks to bedrock :)

View first post
I don't know how but Ahmad has found a way how to crack the protection. ^o)

RE: Automatically block specific transfer requests (suggestion) by Sunshine on 04-05-2005 at 12:33 PM

Do we really need Microsoft (MSN) to do all this...why don't they just give more attention to the AV option thats already there in MSN Messenger (tools > options > filetransfer)? Maybe make it autodetect the AV prog you're using and turn that on by default (more n00bproof). Ofcourse new virusses won't be detected immediately by AV programs, but it is a way to be more secure without forcing things upon us as forbidden (ofcourse the user is responsible for keeping virusdefinitions up to date too).

If they block certain things without an option to enable/disable it (without having to use a plugin or a patch), i think they are going the wrong way.

Also i think if you use IM programs you should be aware of virusses/risks similar as when you use P2P programs. If you are not expecting a file then don't accept it, certainly if it's the first thing sent in a message (loads get send when infected person gets online).

What about kids then you say? Well, teach them the risks or don't allow them to go on without supervision.