-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
请问可以获取到群号吗? #90
Comments
As far as I know, it will be not possible to get the permanent id for a room(group) or a contact, when you are using the webwxApp(wx.qq.com) API. But if others can get it, then we can have a look how they could do that. Can you provide more information about "有人做的机器人可以获取"? |
恩,我可以给你远程看.这个是个付费的软件.你用QQ或者微信吗?我怎么联系你? |
maybe they are hacking wechat for android |
@JasLin 额,这个软件作者告诉我是web协议的,而且就是WEB登陆方式,软件登陆了WEB就不能登录了.难道android协议还能和web混用? |
上传了几个截图.大神看看, |
Interesting... it seems a room id is a number of /\d{9,10}/ ? I had checked some message log, not found it in my log. So where it comes from? |
http://alimmao.com/ 这个软件,刚发现可以1天试用,以12点钟为界限.大神看看,直接用微信号登陆就是开通了1天试用 |
amazing, it works. 成功获取26个好友
成功获取18个群
30秒后开始获取群ID和UIN
群:0 南无阿米(630278141)修改昵称为“王阳”
群:0 UIN:317115075 好
群:3249470305 UIN:0 Ok Some useful links:
|
什么意思丫,可以获取了吗?是怎么弄的? |
No, I still have no idea on how to get the Uin from wxwebApp API. What I mean is that the "alimmao" really works as you said. :) |
是否会像另一个人说的那样可以和安卓补充的用协议?要不就是还有个桌面版的那种抓的包? |
Yes, if you can capture the network packages of "alimmao" that will be helpful for us to know how to get the Uin for you. I guess the Uin is inside some HTTP API call of webwxApp, need specific action to let it show out. (like the above quote said: maybe the API that set the room on top will return Uin of the room?) |
我很想提供这个包,不过我不太会抓这种软件类的包 |
我用Wireshark 抓一个完整的登录到获取群号的包这样可以么?然后我怎么给你? |
great. could you paste the related part here? thanks for the contribution! |
链接: https://pan.baidu.com/s/1nvGu4el 密码: fhpe |
@issmile Thanks, I got the file. You had captured the network packages, good job. But they are SSL encrypted. We can only see an HTTP request of getting wxwebApp QR Code, the others API is called by HTTPS, which means we can not read directly in your capture file. I believe that decoding the SSL stream is possible, because we are the client, and we can get the wx.qq.com Public SSL Certificate Key. However, I have not enough SSL knowledge right now. Could you try to find some way to:
|
额,我连doctor 都不会....这么高级的技术....有没有地方可以求助? |
一点个人经验: 上面两个图 第一张是获取到了群Uin但是没有用户Uin 只有一行数据 不太好判断(我自己没有保存群Uin的需求 因此从来没注意过群的Uin); 第二张是没有群Uin但是每个用户的Uin都拿到了 这个我曾经做到过 方法是对这个群修改群名(或任何会导致该群信息改变的行为 例如加新人进群) 然后会触发syncCheck->webwxSync 会在ModContactList里面返回该群和群成员信息 这时候返回的MemberList里面的Member的Uin是真实的 没有被重置为0 另外 这个方法已经失效了😢前天上午还能work的 前天下午就不行了.. |
@ericzhangjx Thanks for your great sharing! Hope we could find other ways to identify wechat contact in Wechaty in the future. |
After install client from AlimMao.com(link) , we can see this ChangeLog:
Could AlimMao still get Uin for now? |
@zixia 当然不能 但是它们的确找到了一种新办法.. webWxSync里面AddMsgList有时会有一种MsgType=51的消息 Content是一串xml 里面有一个叫username的tag 里面是逗号分隔的wxid 就是只能手动设置一次 没有设置则由微信给你分配一个形如wxid_******的字符串 这个当然算是一种唯一标识符(对于用户:形如wxid_12345678;对于群:形如12345678@chatroom) 阿里猫就是改成了使用wxid而不是uin来识别用户(能找到这种规律..真的是服了 五体投地) 有几个问题:
|
@ericzhangjx Thanks for your awesome analytics, this make the Uin/wxid magic clear for us. In my option, there's no need to support this because |
@ericzhangjx 测了一下, 含有wxid的只有刚登陆的几个请求, 最近联系人的请求才会有wxid返回, 所以并不包含全部联系人。现在还没发现能够返回群成员唯一标识符的请求~ |
Wechaty v0.15 Can Get the Unique ID of Contact/Room across sessions by PuppetPadchatStart from Wechaty v0.15, we enable new Puppet System with all protocols support, include but not limited to Android, iOS, Pad, Win32, Web. Learn more at:
|
Run
npm run doctor
orwechaty run doctor
(for docker user), paste output hereExpected behavior
可以获取唯一标识群的群号吗?就是重新登录后不会改变的群标识,我看有人做的机器人可以获取的
右上角的按钮就是取所有群号的触发按钮,我不会抓这种包。。。
Actual behavior
Steps to reproduce the behavior (and fixes, if any)
Paste the full output logs here with
WECHATY_LOG=silly
setThe text was updated successfully, but these errors were encountered: