This resource needs to be known more. Not gonna lie.
Really useful.
1 Like
not really, they can just use whatever youāre using to decrypt it or just make a decrypter themselves by reading your encryptor script
1 Like
Seems that link is invalid. Hereās a working link to Parallel Luau.
Additionally, the main difference between coroutines/tasks vs Parallel Luau is that the lua thread created using coroutines/tasks has to wait-in-line for the thread scheduled before it to yield or die; meanwhile, this is all happening on the same OS-thread. Parallel Luau utilizes >1 OS-threads, which balances the load more evenly.
See: Parallel Luau | Roblox Creator Documentation
2 Likes
Iām going to write a wrapper function for this (with authentication and key derivation handled automatically) and see how it goes.
1 Like
Upcoming update
Well, I quitted the forumā¦ a little bit but Iām back.
So excited to announce that this resource has been rewritten from scratch and the library will suffer a lot of changes:
-
bytestype will be superseded bybuffers which are better for its easy management and performance. - AES library will now contain constructors for a new data type:
AesCipherwhich performs better at encrypting and/or decrypting a lot of small and large files and doesnāt run key expansion every time it is needed. - LUTs will be optimized for more direct calculations and also giving some resistance to side-channel attacks.
- Block cipher modes of operation now will have their own space at
Aes.modesand each of them no longer impact performance. Custom modes can be added as well.
At performance, this library improved the code a lot so it can now process large ammounts of data in a quite short time. Luau Native Code support and Parallel Scripting can be easily ported so it can get even faster than ever! Thus, making this the fastest and most suitable AES library for Roblox.
Some quick tests (ECB mode):
| Plaintext size | Encryption av. time | Decryption av. time |
|---|---|---|
| 16 bytes | 0.000037 |
0.000043 |
| 32 bytes | 0.000054 |
0.000059 |
| 80 bytes | 0.000095 |
0.000115 |
| 1600 bytes (1.6 KB) | 0.000981 |
0.001284 |
| 3200 bytes | 0.002089 |
0.001939 |
| 160000 bytes (160 KB) | 0.100983 |
0.103678 |
| 1000000 bytes (1 MB) | 0.586153 |
0.641533 |
| 5000000 bytes (5 MB) | 2.964735 |
2.918804 |
| 10000000 bytes (10 MB) | 5.991347 |
5.897557 |
This update will be released when buffers are oficially added to Roblox. Meanwhile I would love to hear some feedback from you. Stay tuned!
5 Likes
Really excited to see this come out!
4 Likes
Do you think you could do test-release for the newer version (if it is complete) so we can give some feedback?
2 Likes
I can send you the preview version via DM.
2 Likes
Any updates on when this will be expected to release?
Also, would you be able to add an option for padding?
(Another note: using luaās and/or is slightly faster than luauās if/then)
1 Like
Itās been 7 months, I donāt think there will be one mate
1 Like
Huge update released
This is an update of the asset. Please change to latest version: huge changes are going to affect old API when using require(id).
-
AesCipherobject superseeded old encryption and decryption functions, allowing for more customization, efficiency, organization and developer-friendly environment. -
bytespseudo-type doesnāt work anymore, please cast data tostrings or the modernbuffers. - Documentation can be found in the module.
Please comment if you have any issues with this new version. 
1 Like
Nice work. Small correction to the AES.spec script: The last ācheckā in the āshould decrypt properlyā section has an Encrypt instead of Decrypt. Would also be nice if you included some examples using different Aes.pads options. 
1 Like
Since it is CTR mode, it would not cause much problems as this mode is symmetric. Thanks for noticing that.
Iām currently looking for that type of documentation.
That is the decision of the user who finds what algorithm is the most suitable for them and the rest is automatic.
1 Like
I love this, but Iād absolutely love it if i could encrypt strings with it outputting another string instead of a buffer :/.
Its mildly infuriating having to serialize & deserialize my the buffer that it returns.
Yes, it is reasonable. However this library is made like this for preventing unnecessary conversions since it works with buffers and is the most effective way to store binary data both for speed and memory.
When encrypting, you usually get some gibberish and converting them to strings may cause problems related to invalid UTF-8 encoding. Thatās why buffers make more sense to use in this case.