AIM @ Work

So today it’s announced that they’ve seen a lot of activity on AIM from employees and they are cracking down.

For the techies here - what exactly can they view? Is it a port that is open per IP address? And how does web-aim differ from that?

Gracias in advance!

they can see all your cybersexing

Nice :bowrofl:

lol

all AIM uses port 80… older verions (pre 4.8 IIRC) are port 5190… regardless i’m sure you’re updated and pushing across 80…

what can they see… ??? that depends on your admin :slight_smile: i can see any one of my users on AIM and can see whta they type AND recieve… so basically… stop using it.

oh… and trillian won’t do you any justice here :tounge:

Dammit!!! ugh and all those video’s i have out there - i’m doomed!

so even the web based version uses the same port?

:wtf: I never seen one…Just playin

if both partys have an SSL?

hmm… do i use aim?

TCP exp00858:1095 oam-m05a.blue.aol.com:5190 ESTABLISHED
TCP exp00858:1098 caim-d02b.blue.aol.com:5190 ESTABLISHED
TCP exp00858:1120 oam-m12b.blue.aol.com:5190 ESTABLISHED
TCP exp00858:1123 caim-m01b.blue.aol.com:5190 ESTABLISHED

everything. u can sniff for AIM packets on a network and read peoples AIM convo’s

AIM Express? its a web app. that is less customizable, less options

she mentioned aim@work

only uses 80 IIRC…?

mp3ray - difference is that aim@work is launching form the web and not from your local machine.

remote desktop to a server of your own -> run aim on there ftw

^ so one could still see me using aim…

maybe i should switch to jabber lol

Our IT dept put this out today…

As many of you may already be aware Microsoft has announced that there is a critical flaw in all versions of Windows operating systems. This flaw could allow for a Windows computer to become infected with malicious software code. At this time Microsoft has not released a “fix” and they have indicated one will not be ready until Tuesday, January 10th. Upon its release **** will immediately begin to apply the patch to all relevant servers and desktops/laptops.

In the interim, we have instituted several measures to mitigate the risk of potential impact of this vulnerability until the official path from Microsoft is available. In addition, please note the following things that you can do as individual users to further protect your respective systems from the vulnerability:

  • Do not open, view, or click on any unexpected e-mail messages.

  • Do not open attachments that come from unfamiliar senders.

  • Do not visit unfamiliar Web sites.

  • Refrain from unnecessary Web surfing.

  • Be wary of opening images or attachments in instant message products such as AIM or MSM Messenger.

As always, make sure that any e-mail you open comes from someone whom you know or would expect an e-mail to come from.

We appreciate your cooperation and assistance in this area.

Maybe you should just stick with PittSpeed and be happy!

http://www.pittspeed.com/forums/vBChat.php?

^ dude, i was the only one in there!!!

they suck at computers, this error was out for a while now and it was easy as unregistering a DLL and this can be done using a global policy. so lame

sonny, aim spawns to other ports for some reason. no clue

be_rad, using a tool such as ethereal can grab the aim convo’s but if you simply use a SSL you will not get jack crap.