- This topic has 10 replies, 6 voices, and was last updated 20 years, 3 months ago by
.
-
Posts
-
There seems to be some new exploit out that i encountered in my usual chat room. It seems there is some program out that makes it impossible for ANYONE to ignore you, either on yahelite or messsy. If any of you find this program tell yahoo about it so it can get patched. This exploit is verry annoying it makes those normal chat trolls even more dissgracefull and horrible.
If your talking about Voice Chat only…that problem can happen and is Yahoo’s Fault but usually stops about a day or two after when the servers are reset.
This is not an exploit.
Not talking just voice chat, it would let me ignore other people using messenger and yahelite, but when i tried to ignore this certain person, it would not ignore on either. everyone else in the room was unable to ignore him either. This person has been known to use booters, exploits and such in the past. that is why i suspected such. He uses voice chat as a weapon , sits and degrade women, him and his brother have been comming into our room for years and degrading women and us because of our relegion.
Okay I am not quite sure. I need some clarification. Are you able to ignore his chat text? There is an exploit out there that takes advantage of voice that keeps one from ignoring users on voice if they bring in a bunch of names at once. Yahoo’s voice servers have always been a weak link in their chat service.
When i went to ignore him, it would not ignore at all. it would not ignore text, it would not ignore voice. Everyone in the chat room said the same thing, they could not ignore him either. i tried ignoring him on messenger, and yahelite. i could not text ignore him, or voice ignore him on yahelite.
That doesn’t seem possible considering how clients (and their ignore system) work. Third party clients, if using the YCHT protocol, don’t ignore the user on the server side, they just ignore them on the client end (they write the usernames to a text file when ignoring a user, and check that text file when a username enters the room to to see if that user should be ignored. The client then just blocks their posts from being seen, however, they may still log all of the conversation, YmLite does this, but I don’t know if any other cleints do). There would have to be an “exploit” that affects all clients, or at least those present in the room you were in, (highly unlikely). The most likely scenario is that you were chatting with a user who had several ID’s in the room (or he was just bringingthem in and out) that were a clone of the ID that you ignored. Thus, making it appear as if he were unable to be ignored.
I agree with Zhugeliang, it is the program that ignores, all packets are still sent to your computer. If you have a packet filter you can see everything typed in the room. I find it difficult to believe there is an exploit that affects all chat clients. Of course stranger things have happened on Chat.
I have seen this over the last couple of days myself.
I believe this is caused by some type of race condition on YahVox that comes with Elite.
This has happened to me twice in the past week.
What I noticed is that if you click to ignore someone in YahVox, and a new speaker takes the mic at nearly the same time, the ignores are then broken.
I suspect that YahVox is sending up the wrong session id/user name combiation. Yahoo may be looking for hackers that attempt to play games with mismatched sessions and usernames at which point your ignore capabilities for the room are terminated.
The effect is that you can no longer ignore anyone in that room.
What is interesting is that ignore works fine if you enter another room.
You can attempt to change to a different chat client (Messanger, java, etc), and you will not be able to ignore anyone in the room where the error occurs.
Normal ignore functions seem to return after 24 hours.
I think the problem actually happens to be an “exploit” with the yahoo voice chat. People have figured out how to use raw voice chat sockets. That’s how they dodge being ignored on voice. At least that’s how I understand. i happen to chat with a few people who have figured this out, and one has written a program to do it. I’m not 100% sure on all of the details, but this seems to be how they are doing it. I’ll post on this again if I find more information about it.
People have figured out how to use raw voice chat sockets. That’s how they dodge being ignored on voice.
Raw voice is just a term that’s used to mean that the yacscom voice library isn’t needed to participate in voice chat in simplest terms. The reason raw voice exists is to allow for more control over voice packets than what is given with yacscom.dll, such as the ability to modify voice packet headers and payloads as they’re received or sent out. This doesn’t mean that it’s something malicious just that the concept can be used for things of that nature when you’re connected to the voice chat server.
Voice ignoring is a one way communication channel {unicast not broadcast} between you/the voice user and the rtp control voice server [remote TCP port 5001]. When you ignore a voice user you send a vc ignore packet with your sequence source id [SSRC id #] along with the person’s that you’re ignoring from voice. What happens is the control server receives the ignore and instantly stops sending you voice audio data from that person. They have no control over whether they’re ignored or not by you or by other voice users.
If there is a way to fool the server into not acknowledging other user’s ignores then I don’t know about it. Each time they join voice *by logging into the voice server with their cookie* they’re sent their own SSRC id and that id is known to anyone connected to voice in the room at that time. It’s main purpose is to identify the source of the audio broadcasts to the room. More than likely the voice server you were connected to in a room was acting strange and not acknowledging voice ignores. This would explain why you thought that there might be something out there since you couldn’t ignore this guy. Over the years some of Yahoo!’s voice servers have been known to act this way, it’s actually pretty common.
- You must be logged in to reply to this topic.