|
crash_demons
|
 |
« Reply #195 on: July 13, 2009, 11:04:29 PM » |
|
YahFilter works fine with the "Cloak" trick.
However, it will notify you via chat posts when you are doing the [usually] required disconnect/reconnect - unlike resume features in some clients which may not notify you. ------------ YahFilter includes the ability to deny specific YMSG packets, fields or filter field-data by a RegEx rule. [Filters] Later, I decided that I wanted to add features for things that I couldn't do in my favorite clients.
------------
It's primary goal was to allow me packet-level regular-expression filtering. This type of filtering, unliked phrase-based filters, allows for some better detection for spam patterns. Filters are editable via the "YahFilter.txt" file created upon first run.
|
|
|
|
« Last Edit: July 14, 2009, 12:12:11 AM by crash_demons »
|
Logged
|
|
|
|
|
|
|
YahOne
|
 |
« Reply #196 on: October 05, 2009, 03:45:20 PM » |
|
YahFilter 64 Final Build Released.->-> <-<- Version 64-Final fixes Replace-Filter bugs, YURL text obfuscation, etc. There are also alternate SKINS for YF Just click my sig for the download. !
|
|
|
|
« Last Edit: October 06, 2009, 12:09:26 PM by YahOne »
|
Logged
|
 YahFilter 64 FULL Click Button For Your Copy!
|
|
|
|
|
Oasis
YahProbie
Offline
Posts: 1
|
 |
« Reply #197 on: October 05, 2009, 05:29:03 PM » |
|
I could use some help, please.
A friend and I both use the latest Yahfilter with the latest Yahelite, and for some reason or another, we can't see each other when we're online. Neither of us are invisible.
Also, for some reason on my end, Yahelite only shows my Local User list, and not my other Yahoo Buddy list ONLY while using Yahfilter.
Is there some menu I checked by mistake on Yahfilter, or something I need to check?
|
|
|
|
|
Logged
|
|
|
|
|
crash_demons
|
 |
« Reply #198 on: October 06, 2009, 12:43:29 AM » |
|
There are also alternative skins for YF You forgot to add a link to the alternative skin package. @Oasis Please ensure that none of your filters (default or otherwise) are filtering your buddylist or status messages. You should be able to see all messages via the Packet viewer. If it is logged as red, then it has been denied - then a feature, one of the "Drop" options, or a Filter matched the packet. If a Filter matched the packet, the Debug window (Help>Debug) will output the matched filter line when the match occurs. I would suggest Trying to login with Filters and Drop options disabled to see if any changes occur, then use information above to narrow the culprit.
|
|
|
|
|
Logged
|
|
|
|
|
crash_demons
|
 |
« Reply #199 on: October 12, 2009, 04:52:53 PM » |
|
Here are some skins I made for YahFilter. You might recognize a few of them as Yahoo messenger skins (non default)
Some nice additions to the default skins. Very minor issues follow (nitpicking): Note that since I didn't document the skin setup I don't expect you to have known exactly how all of this works, even though you seem to have figured out most of it. Not that it's important but the conference window and the captcha window in YF do not support image-skinning because of redraw and entry issues. (I noted this in the changelog way back at some point) Entry issues meaning.... skinned buttons are not truly buttons and as such you can't just hit enter to select the default button - this was essential for Conference and CAPTCHA use though, so they were left unskinned to an extent. This is slightly important because these non-image-skinned buttons use the "backc" or "defbackc" (if backc isn't present for buttons) while image-skinned buttons do not. You'll notice that you set the the button "backc" to 0 (black) on your Mac OS Brushed skin but you left the "forec" unset. (which is set to system default colors.) If the system default foreground color for a button is black, the user will be unable to read that button. Since "backc" is unused while image-skinning occurs, you may just consider setting it to gray (0x7F7F7F) and forcing button "forec" to be black; which shouldn't change how the rest of the skin looks. But all-in-all, very nice skins.
|
|
|
|
« Last Edit: October 12, 2009, 04:55:14 PM by crash_demons »
|
Logged
|
|
|
|
|
crash_demons
|
 |
« Reply #200 on: October 12, 2009, 05:37:19 PM » |
|
PS: Some Skin.ini documentation, since it was lacking: Note: Most fields support AutoIt expressions if necessary. Note: "%SKIN%" is replaced with the path to the current skin folder without a trailing slash. Supported GUI and Control Sections: GUI button label group radio input (single-line edit) edit (multiline edit)
Supported GUI and Control Properties:
splashi = sets the path to the splash screen's image, GUI section. defforec = sets the GUI default foreground color; GUI section. defbackc = sets the GUI default background color; GUI section. forec = sets the foreground color for the section containing it.; any section besides GUI backc = sets the background color for the section containing it, label control support "transparent" font = sets the font name for the section containing it.; formatted as "size|weight|attributes|fontname"; (setting a GUI font makes it a default) cursor = sets a cursor ID for the section containing it. backi = sets the background image path and image coords for the section containing it; formatted as "path|x|y|w|h|resizing" defaults to the skinned control coords, takes macros %X%, %Y%... etc for the control coords (default); GUI, label, or button sections. iconf = set a GUI icon path; sets the title-bar icon of skinned windows. iconl = set a GUI icon via an icon resource; formatted "filepath|iconID"; this was meant at one time to be merged into "iconf" backl = set an image path for the section containing it; experimental, possibly used with labels or bitmap-buttons [unused]. formatted as "path|icon-res-name|icon-type" rounded = reserved but unused. At one time, rounded custom GUI's were considered menbackc = reserved but unused. Menu backgrounds were being tested, but only system-preset colors were ever supported.
Note: you can compensate for not being able to change listbox (eg: conference) colors by setting default colors. Note: "cursor" ID's can be seen here.Note: with "backi" coordinates, you can use "%X%+10" or even "%X%*2+5" etc. Also note that widths or heights of "-1" default to the control's width or height. The "backi" resizing is defaulted to 102 and is defined by a table seen here. Note: not all visual styles and operating systems respect color and font settings for "group" and "radio" controls. Note: "font" attributes can be an addition of: italic (2) underlined (4) strike (8 ); normal font size is 8.5; normal font weight is 400.
|
|
|
|
« Last Edit: October 12, 2009, 06:30:26 PM by crash_demons »
|
Logged
|
|
|
|
|
Carbonize
|
 |
« Reply #201 on: October 13, 2009, 05:31:55 AM » |
|
* Carbonize wonders why you would want to skin something that's going to spend 99.9% of it's time in the systray :-/
|
|
|
|
|
Logged
|
|
|
|
|
crash_demons
|
 |
« Reply #202 on: October 13, 2009, 11:22:07 AM » |
|
* Carbonize wonders why you would want to skin something that's going to spend 99.9% of it's time in the systray :-/ Depends on user preference - I have the Display Image, Encryption, Code-post windows open quite a bit. But anyway, skinning isn't forced - if you want a regular GUI, you can have it. (Heck, that's the first thing it asks when you run it the first time.) Originally skinning was little more than just GUI color preferences, the images were added in more as testing.
|
|
|
|
|
Logged
|
|
|
|
|
n.1ghty1
|
 |
« Reply #203 on: October 16, 2009, 11:36:45 AM » |
|
Here's a suggestion for the /ex online or /ex messy commands; Send this packet (%USER% is the user that we are checking the online status of, and make sure it would send to the client only and not the server) C6# 7«»%USER%«» 13«»1«» And it will cause the name of the scanned user if they are on your buddy list, serverside OR local  to light up as 'Online' this would make scanning the status of local buddies a bit easier now on the downside you won't get any notification of them going offline or anything, but if you ran a second check and they were offline you could send this to have them 'go offline' in YahELite; C6# 7«»%USER%«» 13«»0«»
|
|
|
|
|
Logged
|
|
|
|
|
crash_demons
|
 |
« Reply #204 on: October 16, 2009, 03:31:25 PM » |
|
If I get around to it I may add it, but understand that this is not a top priority concern. I think I like these better - probably more universal: Signed In: (buddy available notification sent to client) C6# 7«»%USER%«» 13«»1«» 10«»0«» 97«»1«» 317«»0«» or (buddy logged in notification sent to client) 1# 7«»%USER%«» 13«»1«» Signed Out: (buddy logged out notification sent to client) 2# 7«»%USER%«» 13«»0«» Messenger User: (buddy custom-away "Yahoo! Messenger" notification sent to client) C6# 7«»%USER%«» 13«»1«» 10«»99«» 47«»0«» 19«»Yahoo! Messenger«» 97«»1«» 317«»0«»
|
|
|
|
« Last Edit: October 16, 2009, 03:36:41 PM by crash_demons »
|
Logged
|
|
|
|
kdogg__
YahProbie
Offline
Posts: 1
|
 |
« Reply #205 on: October 18, 2009, 03:30:55 AM » |
|
I have been using yahfilter and like it alot.. however recently a booter being used destroys this. i have sniffed the packet from the booter and was curious how i could go about blocking this specific packet just an example of the first big
@+Unknown(245)="vz.PHGdCz6892EIMf_Ittw-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%-" Unknown(246)="«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»"
|
|
|
|
|
Logged
|
|
|
|
|
crash_demons
|
 |
« Reply #206 on: October 18, 2009, 10:02:02 AM » |
|
I have been using yahfilter and like it alot.. however recently a booter being used destroys this. i have sniffed the packet from the booter and was curious how i could go about blocking this specific packet just an example of the first big
@+Unknown(245)="vz.PHGdCz6892EIMf_Ittw-%%%..." Unknown(246)="«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»«0D»..."
It would have been nice if you had posted the information that is listed Above the field information in the packet decoder. (Such as message TYPE [packet hex] and the status) Assuming you know the packet hex you could do something like this: (Where "XX" is the packet hex) @XX;;245;;(.)\1{20,} @XX;;246;;(.)\1{20,} That should deny the packet when the 245 or 246 fields have more 20+ repeating characters; it should also trigger "gawd mode" (same as /noact in yahelite) if you have the Boot Protection button set to enabled on the main window. Or if you just wanted to check the length of those fields... @XX;;245;;.{100,} @XX;;246;;.{100,} (which would do the same as the above except when either field is 100+ characters total) OR, if the packet type isn't something you plan on using you could just deny it altogether. @XX You may also benefit from using the "Drop Large Receive Blocks" option under "Filters", which will let you deny chunks of data that are received when they are over an amount of bytes that you set Note: filtering only keeps the packets from being sent to your client, it does not keep it from filling your buffer at Yahoo. Note: if the sender manages to send enough data to fill your buffer at Yahoo before you activate "gawd" successfully, you will be disconnected from yahoo anyway.
|
|
|
|
« Last Edit: October 18, 2009, 10:04:58 AM by crash_demons »
|
Logged
|
|
|
|
|
|
|
crash_demons
|
 |
« Reply #208 on: November 29, 2009, 03:47:15 PM » |
|
This is an internal packet processing bug. I'll have to investigate it when I get a chance.
PS: This issue is not present in my newer examples using the updated YMSGLib.au3, (including Yahsmosis), so I may just switch out parts of YahFilter with the newer examples.
YahFilter is an earlier project and creating it was a learning experience. Many of the things I do now in YMSGLib.au3 and the example scripts were based on the same concepts used in YahFilter, but they've been rewritten and redesigned a few times.
|
|
|
|
« Last Edit: November 29, 2009, 03:53:31 PM by crash_demons »
|
Logged
|
|
|
|
alien_fx_fiend
YahNewbie
Offline
Posts: 31
|
 |
« Reply #209 on: May 21, 2010, 12:14:44 PM » |
|
YahFilter won't connect anymore,I wonder if crash_daemonicus could come up with a quick fix for it. I'd appreciate it greatly!
|
|
|
|
|
Logged
|
~The Worlds Deceit Has Raped My Soul, We Melt The Plastic People Down Then We Melt Their Plastic Town~
|
|
|
|