QSign 9.0.55-9.0.95(公益 API发布)
-
非常感谢您
-
先生大义!
-
因为我用的是MrXiaoM版本的qsign,其它插件不知道被我丢到哪里去了结果靠复制粘贴配文件夹成功了……总之感谢,我对代码一无了解所以也不知道从哪里开始开发_(:3」∠)_
-
“9.0.56”的ANDROID_PAD协议配置文件具体怎么来的呢,我下载最新的qsign解压后里面的协议最高是8.9.88,然后我直接拷贝一份“8.9.88文件夹”重命名为“9.0.56”,把帖子的参数复制进去,前几次登录都是几分钟就报错掉线,然后折腾了好久,不知道咋回事暂时又能正常。求各位指导。
-
@兴亡谁人定 肯定不能这样用,你要把协议文件保存为ANDROID_PAD.json,在安装了fix-protocol-version插件的mirai控制台输入命令
protocol load ANDROID_PAD
加载该协议,确保支持9.0.56,然后修改KFCFactory.json
{ "9.0.56": { "base_url": "https://qsign.trpgbot.com", "type": "fuqiuluo/unidbg-fetch-qsign", "key": "miraibbs" }, }
然后想办法在mirai里通过 ANDROID_PAD 协议登录账号
-
@兴亡谁人定 没让你下载qsign,能下载到的开源qsign都已经死了,现在只有网络API,不需要你下载任何qsign。
-
@zhaodice 在 试图复活qsign,基于9.0.56版本,再捞一把。 中说:
@兴亡谁人定 肯定不能这样用,你要把协议文件保存为ANDROID_PAD.json,在安装了fix-protocol-version插件的mirai控制台输入命令
protocol load ANDROID_PAD
加载该协议,确保支持9.0.56,然后修改KFCFactory.json
{ "9.0.56": { "base_url": "https://qsign.trpgbot.com", "type": "fuqiuluo/unidbg-fetch-qsign", "key": "miraibbs" }, }
然后想办法在mirai里通过 ANDROID_PAD 协议登录账号
怎么玩呀,没看懂,我是mirai-core-jvm2.16.0版本开发,之前使用的是mrxiaom.qsign的txlib8.9.85掉线之后就code45了,你发的这个不知道怎么搞呀,能详说吗,或者给个其他类似文档了解一下
-
不是哥们,会配签名服务器不会配协议?
把这个{ "apk_id": "com.tencent.mobileqq", "app_id": 537220362, "sub_app_id": 537220362, "app_key": "0S200MNJT807V3GE", "sort_version_name": "9.0.56.16830", "build_time": 1713424357, "apk_sign": "a6b745bf24a2c277527716f6f36eb68d", "sdk_version": "6.0.0.2560", "sso_version": 21, "misc_bitmap": 150470524, "main_sig_map": 34869472, "sub_sig_map": 66560, "dump_time": 1713424357, "qua": "V1_AND_SQ_9.0.56_6372_YYB_D", "protocol_type": 6 }
创一个android_pad.json的文件放根目录
把这个{ "9.0.56": { "base_url": "https://qsign.trpgbot.com", "type": "fuqiuluo/unidbg-fetch-qsign", "key": "miraibbs" }, }
创一个KFCFactory.json在根目录,然后bot用pad协议登录,不就完事了
-
@XC_084 在 试图复活qsign,基于9.0.56版本,再捞一把。 中说:
不是哥们,会配签名服务器不会配协议?
把这个{ "apk_id": "com.tencent.mobileqq", "app_id": 537220362, "sub_app_id": 537220362, "app_key": "0S200MNJT807V3GE", "sort_version_name": "9.0.56.16830", "build_time": 1713424357, "apk_sign": "a6b745bf24a2c277527716f6f36eb68d", "sdk_version": "6.0.0.2560", "sso_version": 21, "misc_bitmap": 150470524, "main_sig_map": 34869472, "sub_sig_map": 66560, "dump_time": 1713424357, "qua": "V1_AND_SQ_9.0.56_6372_YYB_D", "protocol_type": 6 }
创一个android_pad.json的文件放根目录
把这个{ "9.0.56": { "base_url": "https://qsign.trpgbot.com", "type": "fuqiuluo/unidbg-fetch-qsign", "key": "miraibbs" }, }
创一个KFCFactory.json在根目录,然后bot用pad协议登录,不就完事了
我按照这样还是45code=45, title=禁止登录, message=登录失败,请前往QQ官网im.qq.com下载最新版QQ后重试,或通过问题反馈与我们联系
File file = new File("txlib\8.9.58");
QSignService.Factory.init(file);
QSignService.Factory.loadProtocols(null);
QSignService.Factory.register();
Bot bot = BotFactory.INSTANCE.newBot(xxxx, "xxxxx", botConfiguration -> {
botConfiguration.setProtocol(BotConfiguration.MiraiProtocol.ANDROID_PAD);
botConfiguration.fileBasedDeviceInfo();
}); -
8.9.58中放的android_pad.json,```{
"9.0.56": {
"base_url": "https://qsign.trpgbot.com",
"type": "fuqiuluo/unidbg-fetch-qsign",
"key": "miraibbs"
},
} -
@CHACCA165 我的上帝,我现在看见txlib我就烦,你再如此这般我就要用靴子狠狠地踢你的屁股,我发誓我会这样做的
-
@zhaodice 在 试图复活qsign,基于9.0.56版本,再捞一把。 中说:
@CHACCA165 我的上帝,我现在看见txlib我就烦,你再如此这般我就要用靴子狠狠地踢你的屁股,我发誓我会这样做的
......这个必须放一个文件内去读取,是不是txlib没关系。。。。屁股给你,教我登录
-
不过,我刚刚用大号登录可以,机器人账号是45- -
-
QSignService.Factory.init(file);
其中这个file直接是 KFCFactory.json
它的内容必须是
{ "9.0.56": { "base_url": "https://qsign.trpgbot.com", "type": "fuqiuluo/unidbg-fetch-qsign", "key": "miraibbs" },}然后自己想办法把{ "apk_id": "com.tencent.mobileqq", "app_id": 537220362, "sub_app_id": 537220362, "app_key": "0S200MNJT807V3GE", "sort_version_name": "9.0.56.16830", "build_time": 1713424357, "apk_sign": "a6b745bf24a2c277527716f6f36eb68d", "sdk_version": "6.0.0.2560", "sso_version": 21, "misc_bitmap": 150470524, "main_sig_map": 34869472, "sub_sig_map": 66560, "dump_time": 1713424357, "qua": "V1_AND_SQ_9.0.56_6372_YYB_D", "protocol_type": 6}给
QSignService.Factory.loadProtocols(); -
老子没看文档你当伪代码看,反正差不多这个意思
-
-
-
大佬牛逼,基友群“福利姬”已经被天煞的狗tx中断小半年了,主要是公开的那些都死了,自己也没能力逆向
-
-
2小时,毙
2024-07-05 01:32:04 I/UnidbgFetchQsign: Bot(3153064533) request_token, 2024-07-05 01:32:04 E/UnidbgFetchQsign: kotlinx.serialization.json.internal.JsonDecodingException: Expected class kotlinx.serialization.json.JsonArray as the serialized body of kotlin.collections.ArrayList, but had class kotlinx.serialization.json.JsonObject kotlinx.serialization.json.internal.JsonDecodingException: Expected class kotlinx.serialization.json.JsonArray as the serialized body of kotlin.collections.ArrayList, but had class kotlinx.serialization.json.JsonObject at kotlinx.serialization.json.internal.JsonExceptionsKt.JsonDecodingException(JsonExceptions.kt:24) at kotlinx.serialization.json.internal.AbstractJsonTreeDecoder.beginStructure(TreeJsonDecoder.kt:330) at kotlinx.serialization.json.internal.JsonTreeDecoder.beginStructure(TreeJsonDecoder.kt:259) at kotlinx.serialization.internal.AbstractCollectionSerializer.merge(CollectionSerializers.kt:29) at kotlinx.serialization.internal.AbstractCollectionSerializer.deserialize(CollectionSerializers.kt:43) at kotlinx.serialization.json.internal.PolymorphicKt.decodeSerializableValuePolymorphic(Polymorphic.kt:61) at kotlinx.serialization.json.internal.AbstractJsonTreeDecoder.decodeSerializableValue(TreeJsonDecoder.kt:52) at kotlinx.serialization.json.internal.TreeJsonDecoderKt.readJson(TreeJsonDecoder.kt:25) at kotlinx.serialization.json.Json.decodeFromJsonElement(Json.kt:117) at fix-protocol-version-1.13.0.mirai2.jar//xyz.cssxsh.mirai.tool.UnidbgFetchQsign.requestToken(UnidbgFetchQsign.kt:208) at fix-protocol-version-1.13.0.mirai2.jar//xyz.cssxsh.mirai.tool.UnidbgFetchQsign.access$requestToken(UnidbgFetchQsign.kt:16) at fix-protocol-version-1.13.0.mirai2.jar//xyz.cssxsh.mirai.tool.UnidbgFetchQsign$qSecurityGetSign$1.invokeSuspend(UnidbgFetchQsign.kt:160) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
2024-07-05 02:22:24 I/Bot.3153064533: Loaded account secrets from local cache. 2024-07-05 02:22:25 I/UnidbgFetchQsign: Bot(3153064533) initialize by https://qsign.trpgbot.com 2024-07-05 02:22:26 I/UnidbgFetchQsign: Bot(3153064533) register, 注册成功了您嘞! 2024-07-05 02:22:26 I/UnidbgFetchQsign: Bot(3153064533) initialize complete 2024-07-05 02:22:27 I/Bot.3153064533: Loaded account secrets from local cache. 2024-07-05 02:22:32 I/Bot.3153064533: Loaded account secrets from local cache. 2024-07-05 02:22:33 I/UnidbgFetchQsign: Bot(3153064533) destroy, IAA 云天明 章北海 赵怡然 Login failed: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. 2024-07-05 02:22:33 E/console: net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. net.mamoe.mirai.network.BotAuthorizationException: BotAuthorization(BotAuthorization.byPassword(<ERASED>)) threw an exception during authorization process. See cause below. at net.mamoe.mirai.internal.network.components.SsoProcessorImpl.login(SsoProcessor.kt:263) at net.mamoe.mirai.internal.network.handler.CommonNetworkHandler$StateConnecting$startState$2.invokeSuspend(CommonNetworkHandler.kt:247) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) Suppressed: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(3153064533), code=16, title=登录失败, message=你的用户身份已失效,为保证账号安全,请你重新登录。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl.doLogin(SsoProcessor.kt:490) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$SlowLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) ... 5 more Suppressed: java.lang.IllegalStateException: Fast login failed: Error(bot=Bot(3153064533), code=16, title=登录失败, message=你的用户身份已失效,为保证账号安全,请你重新登录。, errorInfo=) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$FastLoginImpl.doLogin(SsoProcessor.kt:528) at net.mamoe.mirai.internal.network.components.SsoProcessorImpl$FastLoginImpl$doLogin$1.invokeSuspend(SsoProcessor.kt) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) ... 5 more Caused by: [CIRCULAR REFERENCE: net.mamoe.mirai.network.WrongPasswordException: Error(bot=Bot(3153064533), code=16, title=登录失败, message=你的用户身份已失效,为保证账号安全,请你重新登录。, errorInfo=)] 2024-07-05 02:22:33 I/Bot.3153064533: Bot cancelled: Bot closed
-
@warren39 重新登呀……如果是冻结的话解冻就好了,虽然我测试新号不冻
但是新号具有一套独立的风控规则,会导致冻结,但这里我不便于透露如何绕过这个风控规则,我只能说不会因为sign冻结。
-
@zhaodice 明白,感谢答复~
-