RickSKy

我想会不会是tftp协议引起的，服务端返回数据包时，源端口会进行改变；即C（客户端）向S（服务端）的69端口发送一个文件请求包，这个文件请求包中UDP的源端口号为C的TID（假设C选择4845作为它的TID），目标端口为69（这个时候由于请求还未接受，所以这次请求的UDP包中目标端口不是TID）。S收到这个请求后，将另外采用一个UDP端口（应该另启动了一个UDP Socket）假设为4849来回复这个请求的ACK。这样，这个回复的UDP包的源端口就是S的TID（=4849），目标就是C的UDP端口（TID=4845）。以后，这次请求的后续所有包都在端口为4845和4849中来往。 看代码逻辑，server的chain如果没有指定address，udp是直接进行listen；理论上源ip改变，数据包可以回去（事实也如此）；后面c发送ack时，目的端口不再是69，看代码也没新建listen，按理ack应该正确返回给S哦 这个listen是按五元组建立的么 还是 按目的地址，但按目的地址的话，通信应该是正常的哦；没调试代码，所以理论上请教下

maybe sspi = "0.4.0" is better than rsasl， it has no enviroment dependence for building， and supports linux、mac、windows； I have done some work for this， but only support exchange 2007，...

Can rsasl be build for any platform？I found it depend on gsasl-sys. If rsasl has no building enviroment dependence， it will be nice. I haven't used rsasl, and not sure...

the smtp mode of microsoft exchange only supports ntlm authentication.

what i do is just cross compile rustpython (https://github.com/RustPython/RustPython)

The session of a Windows system user does not have a desktop station, therefore it is not possible to take screenshots.

I want to encapsulate the use of LOCALES.lookup_with_args in a Linux service. Sometimes, due to programming negligence, the name of the arguments may be written incorrectly, but this will not...

The mentioned try_ function has left me a bit confused. Does the library provide such a function? Could you please provide an example? Thank you.

I am confused and trying to upgrade GitLab 15.6 to 16.11. I followed the official instructions for the upgrade (referencing https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/?current=15.6.0&distro=docker&edition=ce). Since there is no 16.1.6 version available, I upgraded...