-
Notifications
You must be signed in to change notification settings - Fork 269
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
Welcome to use automatic RSA signature JS tool, 3KB size🎉😊🎉 #164
Comments
Closing as spam |
@diafygi Think of it as SPAM and it will always be. However, it can not be denied that it can operate normally, safely and reliably 😊. I have upgraded my support for PKCS#8,I believe that this code has been able to adapt to complex and changeable environments. There is no denying that the signature part is the most tedious and error-prone part of gethttpsforfree entire request process. This tool has successfully helped me to request a certificate and is simpler and faster than ever before. In addition, I studied README. I think adding optional auto-signature function can help to operate quickly and avoid human errors. And because this feature is optional, users can choose not to provide private keys, just as before. I wonder if I want to submit a PR, but the source code of uncompressed RSA libraries may be quite large, only about 30 KB after compression. |
In addition, I found that adding 1 to line 302 was very difficult to understand. I know it's because the positive integer increases by 0x00, but as long as the first four digits of the value are less than 0x8, it won't increase this. So it can be solved by replacing the 0x00 at the beginning, which seems to be better understood. Line 302 in bd24e41
|
Welcome to use automatic RSA signature JS tool, 3KB size🎉😊🎉
欢迎使用RSA自动签名JS工具,3KB大小🎉😊🎉
Signature operation is too cumbersome for each manual update of certificates. Especially when there are many domain names.
每次手动更新证书时签名操作太繁琐。尤其是域名很多的情况下。
This JS code will free your hands from the need to jump from window to window to sign manually. But only RSA certificates are supported, ECC is not supported.
这段JS代码将解放你的双手, 不用在多个窗口之间跳来跳去进行手动签名了。但仅支持RSA证书,不支持ECC。
How to use
如何使用
Step1. Open https://gethttpsforfree.com/.
Step1. 打开 https://gethttpsforfree.com/页面。
Step2. Copy the following code to the browser console for execution.
Step2. 复制下面的代码到浏览器控制台里面执行。
Step3. According to the normal process operation in the page, fill in the private key, all signature operations will be completed automatically in the middle of the page.
Step3. 按页面中的正常流程操作,填写好私钥,中途所有签名操作都会自动完成。
Why did you write this tool?
为什么编写这个工具
I used fszlin/certes to write a C# client to apply for a multi-domain name certificate, but often operated until the end of the library always throws out the request error message, but every time I use gethttpsforfree manually, I can complete the application at one time. So I'm going to discard certes and just use gethttpsforfree.
我使用了fszlin/certes来编写了一个C#客户端用来申请多域名证书,但经常操作到最后这个库老是抛出申请错误信息,无奈每次手动用gethttpsforfree都能一次性完成申请。所以我就准备丢弃certes,仅仅使用gethttpsforfree。
But every time gethttpsforfreeissues multiple domain names, the signature operation is too tired. Copy to copy. Because I implemented an RSA signature function in xiangyuecn/Recorder of my H5 repository some time ago, I took it directly and installed the auto-signature function on gethttpsforfree.
但gethttpsforfree每次签发多个域名时签名操作太累了,复制来复制去,由于前段时间在我的H5录音库xiangyuecn/Recorder内实现了一个RSA签名功能,因此直接拿过来给gethttpsforfree安装上了自动签名功能。
3KB? Not only 3KB
3KB?并非只有3KB
The tool uses my integrated ztest-rsa.js. It contains: CryptoJS v3.1.2 SHA256; Tom Wu's RSA Library, which has modified some bugs in RSA source code and provided sign method. These two sources can be downloaded and integrated by themselves.
工具内使用了我整合的ztest-rsa.js。里面包含了:CryptoJS v3.1.2的SHA256;Tom Wu的RSA库,已修改RSA源码内的部分bug和提供sign方法。可自行下载这两个源码自己整合。
This code has too many limitations and no desire to submit PR. This library shuts down wiki.
本代码功能局限性太大,没有提交PR的欲望。这个库又关闭了wiki。
The text was updated successfully, but these errors were encountered: