Last night, I was planning to do some web development, and when I created my new VPS, I just felt like it was quite a tedious process either manually copying-pasting SSL certs around or deploying CertBot to allocate new ones for me. My life would be easier if there is some sort of SSL certificates management and distribution system.

Although I didn't really search these keywords on Google, I can promise that they definitely exist on the web. Nevertheless, I want to write one myself, because it has been such a long period since last time I wrote something in Rust.

It has been a long time since my last reverse engineering on macOS, and that was about Netease Cloud Music. 

But I always write that in Objective-C, perhaps I should try something different, let's say, Rust.

1. Compile a .dylib that macOS recognises
2. Build a Constructor Function that Invokes on dylib Loading
3. All I need is a dlsym
   1. Find the Symbol You Want
   2. Casting to Function Pointer
4. Compile and Hook

1. Compile a .dylib that macOS recognises

The first step is to tell cargo that what we need is a library

cargo new --lib exploit

And cargo will create these files for us.

exploit
├── Cargo.toml
└── src
    └── lib.rs

However, if we compile this project, the output library has a suffix .rlib. which suggests that this is a Rust library. Yet we need a dylib that macOS recognises.

Therefore the hint for producing a .dylib library should be added in Cargo.toml, which is shown below.

[lib]
crate-type = ["dylib"]

This tells cargo out crate type is a dylib, which satisfies the format requirements of macOS dynamic library.

Generate WebP images for JPG / PNG files on-the-fly with Rust! webp_server_rs

Speaking of switching to WebP image, at the first glance, I just did it in a very naive approach.

Then @Nova wrote a Node.JS server that can serve JPG/PNGs as WebP format on-the-fly. You can find that at n0vad3v/webp_server.

A few days ago, @Nova and @Benny rewrite the WebP Server in Golang, webp-sh/webp_server_go. 

And that looks really promising, the size of the webp server, according to its description, had greatly reduced from 43 MB to 15 MB, and it is a single binary instead of webp_server with node_modules.

I cloned that project and added a tiny feature. However, I just found that although it is absolutely easy to implement the tiny feature, there is a potential design issue with the `fasthttp` module. In order to get everything work, it took me about 4 hours to debug on it.

Finally, it turned out to be a pointer of an internal variable (ctx.Request.uri, or so) was directly returned from ctx.Path(), and if users invoke ctx.SendFile(filepath), the ctx.Request.uri will be set to filepath, which will also propagate to all variables that hold the shared value of ctx.Path(). You may visit my previous blog post for details.

Well, in aforementioned blog post, I said that it would be better if it was written in Rust. Now, let's make it come true and push the WebP server even further.

There are some comparisons among n0vad3v/webp_server, webp-sh/webp_server_go and webp_server_rs.

As for size,

• webp_server(nodejs) with node_modules takes 43 MB
• webp-server(go) has reduced to 15 MB, and it's single binary
• webp-server(Rust) pushes that even further, only 3.6 MB on macOS and 6.4 MB on Linux

In terms of convenience, you can just download the binary file and run if you choose either webp-server(go) or webp-server(Rust). However, webp_server(nodejs) requires pm2 to run.

Performance, to be honest, I haven't got time to run some benchmarks on them. But IMHO it (webp-server(Rust)) should be as fast as golang version.

Rust 并不能像 Python 那样有全局的 Package（当然，现在就算是写 Python，也很少有谁一上来就往全局环境里安装 Package 了），于是 Rust 要想单独运行一个引用了第三方库的 Rust script 时，就必须用 Cargo 创建一个 project。

绝大多数时候这个倒也是能接受啦，但是有时真的只是想在一边测试一个小的 function 或者验证一下自己的想法。如果直接在 working-in-progress 的 project 里写的话，就可能

1. 不得不配合已有的部分做一些 error handling
2. 或者手工测试到该条代码路径上
3. 又或者写上相应的 unit test

显然只是想快速验证一下的话，上面三种方式都有不便之处。如果单独再用 cargo new 一个 project 的话，也不是不行，但是懒（

在用 Code Runner（对你来说也许是 VSCode 之类的）的时候，直接新建一个 Rust file 开始写会相对方便。假如我们的 Rust script 叫 example.rs，那么要引入第三方 crate 的话，比如引用 regex，我们可以用这样的语法，

// cargo-deps: regex="1"

如果要控制 crate 的 feature 之类的，则可以写

// cargo-deps: opencv = {version = "0.28", default-features = false, features = ["opencv-41", "contrib"]}

虽然并不能实现 Python 那样的全局 package，但是我们可以用代码扫描 exmaple.rs 里面所有的 // cargo-deps: {:dependency}，然后自动生成一个 example 目录和相应的 Cargo.toml 文件，接着将 example.rs 文件复制到 example/src/main.rs， 最后自动调用 cargo run～