You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 4, 2024. It is now read-only.
A current point of contention for scripters - especially ones with special needs for whitelisting - definitely suffer from lack of standardization on this front.
Synapse makes the standard algorithm AES-GCM, Script-Ware claims to be AES-CTR - I was unable to find documentation for Krnl, Fluxus, and Oxygen U to confirm theirs.
Some AES implementations hold the random IV in the text returned in order to reduce it to one payload instead of requiring two sets of data in order to function, but other forms do not.
The text was updated successfully, but these errors were encountered:
In addition, certain AES algorithms are more open to attacks than others. This also needs to be looked into and then standardized according to the most secure and/or performant algorithm.
A current point of contention for scripters - especially ones with special needs for whitelisting - definitely suffer from lack of standardization on this front.
UNC declares it as
crypt.decrypt(data: string, key: string, IV: string?): string
,Synapse as:
syn.crypt.decrypt(data: string, key: string): string
, andScript-Ware as:
crypt.decrypt(data: string, key: string, iv: string, mode: string)
despite existing documentation saying otherwise.Synapse makes the standard algorithm AES-GCM, Script-Ware claims to be AES-CTR - I was unable to find documentation for Krnl, Fluxus, and Oxygen U to confirm theirs.
Some AES implementations hold the random IV in the text returned in order to reduce it to one payload instead of requiring two sets of data in order to function, but other forms do not.
The text was updated successfully, but these errors were encountered: