Skip to main content

App - Security & Validation

Security contexts, permission checks, script signing, and hash verification.

Subsystem Metrics​

  • Total Documented Functions: 29
  • Functions Exercised in Tests: 0
  • Platform-Divergent Implementations: 0
  • Component Source Files: 6

Source Files​

View all 6 source files in this subsystem
Source FilePath
ApiSecurity.hApp/include/security/ApiSecurity.h
FuzzyTokens.hApp/include/security/FuzzyTokens.h
JunkCode.hApp/include/security/JunkCode.h
SecurityContext.hApp/include/security/SecurityContext.h
FuzzyTokens.cppApp/security/FuzzyTokens.cpp
SecurityContext.cppApp/security/SecurityContext.cpp

Function Reference​

1. callCheckSetBasicFlag​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

FORCEINLINE void callCheckSetBasicFlag(unsigned int flags);
PropertyValue
Return TypeFORCEINLINE void
ModifiersNone
Source LocationApp/include/security/ApiSecurity.h:65
SubsystemApp - Security & Validation

How it Works Internally​

Executes callCheckSetBasicFlag within App - Security & Validation. Coordinates interactions with addFlagFast.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: addFlagFast.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on callCheckSetBasicFlag.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


2. callCheckSetApiFlag​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

FORCEINLINE void callCheckSetApiFlag(unsigned int flags);
PropertyValue
Return TypeFORCEINLINE void
ModifiersNone
Source LocationApp/include/security/ApiSecurity.h:92
SubsystemApp - Security & Validation

How it Works Internally​

Executes callCheckSetApiFlag within App - Security & Validation. Coordinates interactions with addFlagSafe.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: addFlagSafe.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on callCheckSetApiFlag.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


3. callCheckNop​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

FORCEINLINE void callCheckNop(unsigned int flags);
PropertyValue
Return TypeFORCEINLINE void
ModifiersNone
Source LocationApp/include/security/ApiSecurity.h:98
SubsystemApp - Security & Validation

How it Works Internally​

Declaration or inline method for callCheckNop.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on callCheckNop.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


4. getUnicodeDllName​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

WCHAR* getUnicodeDllName(const UNICODE_STRING& str) const;
PropertyValue
Return TypeWCHAR*
Modifiersinline const
Source LocationApp/include/security/ApiSecurity.h:172
SubsystemApp - Security & Validation

How it Works Internally​

Executes getUnicodeDllName within App - Security & Validation.

  • Control Flow & Execution: Iterative loop processing, Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on getUnicodeDllName.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


5. rbxGetNtdll​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HMODULE rbxGetNtdll();
PropertyValue
Return TypeHMODULE
Modifiersinline
Source LocationApp/include/security/ApiSecurity.h:189
SubsystemApp - Security & Validation

How it Works Internally​

This gets the location of ntdll using the documented parts of the PE format. The intent is to make it harder for anyone who wants to hook GetModuleHandle. This is not foolproof as the PEB or PEB pointer could be modified.

  • Control Flow & Execution: Iterative loop processing, Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: __readfsdword, getUnicodeDllName, _wcsnicmp, min.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on rbxGetNtdll.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


6. detectDllByExceptionChain​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

FORCEINLINE uint32_t detectDllByExceptionChain(void* addrOfChain, unsigned int kFlags);
PropertyValue
Return TypeFORCEINLINE uint32_t
ModifiersNone
Source LocationApp/include/security/ApiSecurity.h:278
SubsystemApp - Security & Validation

How it Works Internally​

  • C *nextHandler | + C *handler() + 8 *handler() | + 8 scopeTable + 4 state | + 4 tryLevel +00 saved ebp | +00 saved ebp - 4 return address | - 4 return address - 8 first arg | - 8 first arg -xx last arg | -xx last arg This will get generated in some functions that don't have try-catch blocks. Basically if something could throw, objects might need to be destroyed. fs:[0] also contains a pointer to nextHandler, but is out of place in the middle of a function. The list will always have a size of at least 2 -- the entry in ntdll and the entry we started with. There is a case with boost::threads, as these get created with msvcr's threadstartex (after ntdll rtlInitThread). However, boost::threads will have three exception handlers in the boost code before getting into msvcr.
  • Control Flow & Execution: Iterative loop processing, Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on detectDllByExceptionChain.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


7. generateCallInfo​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

FORCEINLINE void generateCallInfo(void* addrOfFirstArg, std::vector<CallChainInfo>& info);
PropertyValue
Return TypeFORCEINLINE void
ModifiersNone
Source LocationApp/include/security/ApiSecurity.h:324
SubsystemApp - Security & Validation

How it Works Internally​

Executes generateCallInfo within App - Security & Validation. Coordinates interactions with push_back, CallChainInfo.

  • Control Flow & Execution: Iterative loop processing, Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: push_back, CallChainInfo.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on generateCallInfo.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


8. detectDllByExceptionChainStack​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

FORCEINLINE uint32_t detectDllByExceptionChainStack(void* addrOfFirstArg, unsigned int kFlags);
PropertyValue
Return TypeFORCEINLINE uint32_t
ModifiersNone
Source LocationApp/include/security/ApiSecurity.h:345
SubsystemApp - Security & Validation

How it Works Internally​

Executes detectDllByExceptionChainStack within App - Security & Validation.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on detectDllByExceptionChainStack.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


9. detectDllByExceptionChainTeb​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

FORCEINLINE uint32_t detectDllByExceptionChainTeb(unsigned int kFlags);
PropertyValue
Return TypeFORCEINLINE uint32_t
ModifiersNone
Source LocationApp/include/security/ApiSecurity.h:355
SubsystemApp - Security & Validation

How it Works Internally​

not all functions add an exception handler to the chain, so the stack based method doesn't always work.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: __readfsdword.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on detectDllByExceptionChainTeb.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


10. detectDllByExceptionChainTeb​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

FORCEINLINE uint32_t detectDllByExceptionChainTeb(unsigned int kFlags);
PropertyValue
Return TypeFORCEINLINE uint32_t
ModifiersNone
Source LocationApp/include/security/ApiSecurity.h:360
SubsystemApp - Security & Validation

How it Works Internally​

Executes detectDllByExceptionChainTeb within App - Security & Validation.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on detectDllByExceptionChainTeb.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


11. detectDllByExceptionChainStack​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

FORCEINLINE uint32_t detectDllByExceptionChainStack(void* addrOfFirstArg, unsigned int kFlags);
PropertyValue
Return TypeFORCEINLINE uint32_t
ModifiersNone
Source LocationApp/include/security/ApiSecurity.h:364
SubsystemApp - Security & Validation

How it Works Internally​

Executes detectDllByExceptionChainStack within App - Security & Validation.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on detectDllByExceptionChainStack.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


12. generateCallInfo​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

FORCEINLINE void generateCallInfo(void* addrOfFirstArg, std::vector<CallChainInfo>& info);
PropertyValue
Return TypeFORCEINLINE void
ModifiersNone
Source LocationApp/include/security/ApiSecurity.h:368
SubsystemApp - Security & Validation

How it Works Internally​

Executes generateCallInfo within App - Security & Validation.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on generateCallInfo.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


13. addFlagFast​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void addFlagFast(unsigned long long flags);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationApp/include/security/FuzzyTokens.h:42
SubsystemApp - Security & Validation

How it Works Internally​

Executes addFlagFast within App - Security & Validation.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on addFlagFast.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


14. addFlagSafe​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void addFlagSafe(unsigned long long flags);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationApp/include/security/FuzzyTokens.h:52
SubsystemApp - Security & Validation

How it Works Internally​

Executes addFlagSafe within App - Security & Validation. Coordinates interactions with lock.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: RAII mutex lock acquisition (scoped_lock); Thread mutual exclusion locking (boost::mutex).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: lock.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on addFlagSafe.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


15. getPrev​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

long long getPrev();
PropertyValue
Return Typelong long
Modifiersunsigned
Source LocationApp/include/security/FuzzyTokens.h:58
SubsystemApp - Security & Validation

How it Works Internally​

Executes getPrev within App - Security & Validation.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on getPrev.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


16. setLastTag​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void setLastTag(unsigned long long tag);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationApp/include/security/FuzzyTokens.h:73
SubsystemApp - Security & Validation

How it Works Internally​

Executes setLastTag within App - Security & Validation.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on setLastTag.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


17. junk​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void junk();
PropertyValue
Return Typevoid
Modifiersinline
Source LocationApp/include/security/JunkCode.h:11
SubsystemApp - Security & Validation

How it Works Internally​

Declaration or inline method for junk.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on junk.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


18. requirePermission​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void requirePermission(Permissions permission, const char* operation = 0) const;
PropertyValue
Return Typevoid
Modifiersconst
Source LocationApp/include/security/SecurityContext.h:69
SubsystemApp - Security & Validation

How it Works Internally​

Throws an exception if the current thread's Context doesn't have the requested Role

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: C++ exception throw on invalid state or failure; Standard runtime error exception formulation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).
  • Key Internal Calls: isInRole, runtime_error, identity, operation.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on requirePermission.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


19. hasPermission​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool hasPermission(Permissions permission);
PropertyValue
Return Typebool
ModifiersNone
Source LocationApp/include/security/SecurityContext.h:90
SubsystemApp - Security & Validation

How it Works Internally​

Executes hasPermission within App - Security & Validation. Coordinates interactions with isInRole.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: isInRole.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on hasPermission.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


20. Security::teaDecrypt​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

long long Security::teaDecrypt(unsigned long long inTag);
PropertyValue
Return Typelong long
Modifiersunsigned
Source LocationApp/security/FuzzyTokens.cpp:6
SubsystemApp - Security & Validation

How it Works Internally​

Executes teaDecrypt within App - Security & Validation. Coordinates interactions with Algorithm.

  • Control Flow & Execution: Iterative loop processing, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: Algorithm.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on teaDecrypt.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


21. Security::teaEncrypt​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

long long Security::teaEncrypt(unsigned long long inTag);
PropertyValue
Return Typelong long
Modifiersunsigned
Source LocationApp/security/FuzzyTokens.cpp:29
SubsystemApp - Security & Validation

How it Works Internally​

Executes teaEncrypt within App - Security & Validation.

  • Control Flow & Execution: Iterative loop processing, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on teaEncrypt.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


22. ClientFuzzySecurityToken::crypt​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

long long ClientFuzzySecurityToken::crypt();
PropertyValue
Return Typelong long
Modifiersunsigned
Source LocationApp/security/FuzzyTokens.cpp:61
SubsystemApp - Security & Validation

How it Works Internally​

Executes crypt within App - Security & Validation. Coordinates interactions with lock, teaEncrypt.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: RAII mutex lock acquisition (scoped_lock); Thread mutual exclusion locking (boost::mutex).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: lock, teaEncrypt.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on crypt.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


23. ignoreFlags​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

: ignoreFlags(ignoreFlags);
PropertyValue
Return Type:
ModifiersNone
Source LocationApp/security/FuzzyTokens.cpp:72
SubsystemApp - Security & Validation

How it Works Internally​

Executes ignoreFlags within App - Security & Validation.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on ignoreFlags.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


24. ServerFuzzySecurityToken::decrypt​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

long long ServerFuzzySecurityToken::decrypt(unsigned long long inTag);
PropertyValue
Return Typelong long
Modifiersunsigned
Source LocationApp/security/FuzzyTokens.cpp:80
SubsystemApp - Security & Validation

How it Works Internally​

There is current some difficult to find bug that allows one security packet to be dropped or not sent. This scheme was not designed to make this case easy.

  • Control Flow & Execution: Iterative loop processing, Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: teaDecrypt, teaEncrypt.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on decrypt.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


25. Context::isInRole​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool Context::isInRole(Identities identity, Permissions p);
PropertyValue
Return Typebool
ModifiersNone
Source LocationApp/security/SecurityContext.cpp:10
SubsystemApp - Security & Validation

How it Works Internally​

Executes isInRole within App - Security & Validation. Coordinates interactions with defined, RBXASSERT.

  • Control Flow & Execution: Conditional branching, Multi-case state dispatch, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: defined, RBXASSERT.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on isInRole.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


26. Context::current​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

Context& Context::current();
PropertyValue
Return TypeContext&
ModifiersNone
Source LocationApp/security/SecurityContext.cpp:41
SubsystemApp - Security & Validation

How it Works Internally​

Executes current within App - Security & Validation. Coordinates interactions with ptr, get, anonymous, reset.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: ptr, get, anonymous, reset.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on current.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


27. Context::tssCleanup​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Context::tssCleanup(Context*);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationApp/security/SecurityContext.cpp:53
SubsystemApp - Security & Validation

How it Works Internally​

Declaration or inline method for tssCleanup.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on tssCleanup.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


28. Context::ptr​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

boost::thread_specific_ptr<Context>& Context::ptr();
PropertyValue
Return Typeboost::thread_specific_ptr&lt;Context&gt;&
ModifiersNone
Source LocationApp/security/SecurityContext.cpp:59
SubsystemApp - Security & Validation

How it Works Internally​

Executes ptr within App - Security & Validation. Coordinates interactions with value.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: value.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on ptr.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


29. current​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

: current(identity);
PropertyValue
Return Type:
ModifiersNone
Source LocationApp/security/SecurityContext.cpp:67
SubsystemApp - Security & Validation

How it Works Internally​

Executes current within App - Security & Validation. Coordinates interactions with ptr, get, reset.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: ptr, get, reset.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on current.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.