AlexGuo1998

Results 9 issues of AlexGuo1998

Hi, thanks for this awesome software! When I decode an image with RSTn markers, it shows: ``` Lum (Tbl #0), MCU=[0,1] [0x000068EC.7]: ZRL=[ 0] Val=[ -695] Coef=[00= DC] Data=[0x 75...

bug

I tried `png-parser` with `pal2`/`pal4`/`rgb48` images: ``` pngparser -v -s test.png ``` ... and they all fail. There are mainly 3 problems. --- For all images, `scanline_width` is incorrect, so...

## 你正在使用哪个版本的 V2Ray? 客户端:4.38.3 服务端:4.35.1(问题与服务端无关) ## 你的使用场景是什么? 反向代理,该客户端为想要供外网连接的机器 ## 你看到的异常现象是什么? 客户端无法连接服务器,仔细观察后发现是routing匹配域名时,因为使用了大写,导致没有匹配到域名,走了freedom ## 你期待看到的正常表现是怎样的? 客户端连接上服务端 ## 请附上你的配置 **服务端配置:**(与服务端无关,可以略过) ```javascript { "log": {"loglevel": "info"}, "reverse": { "portals": [ { "tag": "portal", "domain":...

bug
Welcome PR

If you want to change a character to `` in vim, you could type `r `. However in `vim-mode-plus`, this does nothing but hides the cursor (until re-open buffer). This...

bug

和 #22 相反,我是想要一个自动硬币兑换瓜子的功能,具体操作是: ``` POST https://api.live.bilibili.com/pay/v1/Exchange/coin2silver HTTP/1.1 ``` POST的Payload是 ``` num=x&platform=pc&csrf_token=****************** ``` 其中`num=x`的`x`就是兑换数量 成功的返回是 ``` {"code":0,"msg":"兑换成功","message":"兑换成功","data":{"silver":500}} ``` 超额的返回是 ``` {"code":403,"msg":"每天最多能兑换 50 个","message":"每天最多能兑换 50 个","data":[]} ``` 另外,要得到当前剩余的可兑换数量 ``` GET https://api.live.bilibili.com/pay/v1/Exchange/getStatus?platform=pc HTTP/1.1...

建议

On windows, we currently inspect the parent devnode to get `bus_type`: https://github.com/libusb/hidapi/blob/4ebce6b5059b086d05ca7e091ce04a5fd08ac3ac/windows/hid.c#L498-L552 However, some filtered HID device (e.g. [imbushuo/mac-precision-touchpad](https://github.com/imbushuo/mac-precision-touchpad)) whose parent is the filter driver, which don't have a correct...

Windows

**Describe the bug** When VsVim is enabled, unexpected padding is added to the sticky scroll area. **To Reproduce** Steps to reproduce the behavior: 1. Enable "sticky scroll" from Options -...

82 ('R') should be 72 ('H') here. Maybe some mistakes in refactoring: https://github.com/vidarh/SAM/commit/5a4b88b387316309ef7636fc332b5e66906d8694#diff-8e2c3c7e3979240badeac46c09c0dfd8R269 (Original https://github.com/s-macke/SAM/blob/bcf92b5c693cbaf25e26c17c1c1b0589b3647489/src/reciter.c#L492-L493) BTW, I'm trying to totally re-write reciter in C.

我们(记为A)接收上行消息时,为了保证安全,有时需要确保该消息是wxpusher(记为B)推送的。 比如“发送指令重启服务”的情况,不仅要保证该用户是已知的管理员用户,还要保证该POST的请求来源是wxpusher,而不是第三方。 建议wxpusher后台回调时增加一个签名(使用消息内容和appToken),这样只要第三方拿不到token,就无法伪造请求来源。 具体的实现方法,个人想法是: * B回调A时,在POST请求头中增加一个`sign`字段,该字段为`整条JSON内容 + "-" + appToken`用某种散列算法(`MD5`或者`SHA1`或者其他的算法)(记为`hash(...)`)进行签名 * A收到请求时,分两种情况: * 如果该回调地址只有一个app使用,则直接计算`hash(整条JSON内容 + "-" + appToken)`与`sign`比较,如果不相同则丢弃消息,相同则继续处理; * 如果有多个app使用同一个回调地址,则先解析消息内容得到`appId`,然后查得相应的`appToken`,再进行上面的处理 * 如果要防止重放攻击,A要进行额外的判断,如: * 整条消息是否在之前的x分钟内重复过?(只需判断sign是否重复过) * `time`字段和本地时间之差,是否在合理区间内?(小于x分钟) 这样既不会破坏旧的协议,也可以增加回调的安全性。希望这个建议能被采纳。