Gered
7f8a8f75e0
this is not actually recommended, as it _technically_ does "mess up" the sequence (1-3 zero-bytes are being encrypted along with your 1-3 remaining bytes in non-dword-sized data buffers, but those additional encrypted zero-bytes are not being given back to you at the end). however, in my opinion, this is quite unlikely to pose a problem for anyone. for dealing with PSO packets, i'm pretty sure all of those end up being dword-sized anyway, so no issue there. for encrypting and decrypting offline quest data, the compressed bin/dat data _could_ technically be non-dword-sized (as i actually encountered today) so you would otherwise need to pad the input data before calling crypt() anyway. and in this case you are not going to be using that very same Crypter instance to do any further encrypting/decrypting ... so it's actually no problem at all. so, to me, the convenience of having crypt() just automatically be able to deal with any arbitrary size of data was worthwhile. meh.
19 lines
370 B
TOML
19 lines
370 B
TOML
[package]
|
|
name = "psoutils"
|
|
version = "0.1.0"
|
|
authors = ["gered <gered@blarg.ca>"]
|
|
edition = "2018"
|
|
|
|
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
|
|
|
|
[dependencies]
|
|
byteorder = "1.4.3"
|
|
thiserror = "1.0.24"
|
|
encoding_rs = "0.8.28"
|
|
libc = "0.2.94"
|
|
|
|
[dev-dependencies]
|
|
claim = "0.5.0"
|
|
pretty-hex = "0.2.1"
|
|
tempfile = "3.2.0"
|