Extension Encryption by xHector1337 · Pull Request #791 · rapid7/metasploit-payloads

xHector1337 · 2026-02-02T15:02:21Z

Extension Encryption: Encryption Manager

This PR creates the basic encryption manager, and start wiring decryption logic inside metsrv.

Coverage:

Initialization of Extension Encryption Manager inside the server setup
Insertion of an extension if flagged as ENCRYPTABLE and if it was load by ReflectiveLoader
Decryption of extension if command handler is within extension mem space
Decryption of scheduler event handler if handler is within extension mem space

At the moment the default CryptographicManager is the a "debug" manager that will just force metsrv to rewrite the same bytes to the extension memory space, this chained with a testing extension loaded with the ENCRYPTABLE flag set to true will be used as first PoC to ensure writing the memory will not cause any issue for extension loaded with ReflectiveLoader.

…mand handling

… setup

… files

…r handling

…extension-encryption/manager

…tion/manager Collaboration Extension Encryption

…_process_inline

dledda-r7 · 2026-02-10T18:19:50Z

+				dprintf("[SCHEDULER] scheduler_waitable_thread( 0x%08X ), calling extensionFindDecrypt");
+				if (extensionFindDecrypt(entry->routine)) {
+					dprintf("[SCHEDULER] scheduler_waitable_thread ( 0x%08X ), decryption of the extension failed");
+					//break;


Yeah we need to think what to do here, make sense to break i guess

dledda-r7 · 2026-02-10T18:21:18Z

+	BOOL bInitialized;
+	LPVOID lpCryptoContext;
+	LPCSTR lpCryptoParams;
+	BOOL bNeedsRefresh;
+	DWORD (*initialize)(LPVOID* lpCryptoContext, LPVOID lpParams);
+	DWORD (*encrypt)(LPVOID lpDataIn, DWORD dwDataInSize, LPVOID lpDataOut, DWORD dwDataOutSize);
+	DWORD (*decrypt)(LPVOID lpDataIn, DWORD dwDataInSize, LPVOID lpDataOut, DWORD dwDataOutSize);
+	DWORD (*refresh)(LPVOID lpCryptoContext, LPVOID lpParams);


Make sense here to keep track of what type of Cryptographic Manager we have created, holding the ENUM should be enough

dledda-r7 · 2026-02-10T18:23:59Z

+			ret = ReadProcessMemory(GetCurrentProcess(), (unsigned char*)ExtensionLoc + i, lpTempBufferRead, diff, &ByteCounter);
+			if (!ret || ByteCounter != diff) {
+				dprintf("[extension_encryption][extension_encryption_decrypt] ReadProcessMemory failed with error 0x%x", GetLastError());
+				bError = TRUE;
+				break;
+			}
+			if (!g_ExtensionEncryptionManager->cryptoManager.decrypt(lpTempBufferRead, diff, lpTempBufferWrite, BUFFER_SIZE)) {
+				dprintf("[extension_encryption][extension_encryption_decrypt] CryptographicManager decrypt failed.");
+				ret = FALSE;
+				bError = TRUE;
+				break;
+			}
+			ret = WriteProcessMemory(GetCurrentProcess(), (unsigned char*)ExtensionLoc + i, lpTempBufferWrite, diff, &ByteCounter);
+			if (!ret || ByteCounter != diff) {
+				dprintf("[extension_encryption][extension_encryption_decrypt] WriteProcessMemory failed with error 0x%x", GetLastError());
+				bError = TRUE;
+				break;
+			}


I am really curious about running this on a real extension, wondering if ReadProcessMemory and WriteProcessMemory works as expected. With the DEBUG Cryptographic Manager we should just write the same bytes, this seems like a good testing example

I will test it as soon as I can and let you know. Thanks for your reviews!

…the scheduler and command_process_inline

…actor add function

dledda-r7 · 2026-03-05T12:05:55Z

Side note for future me: BEFORE LANDING

Pass every function to use the win api

…tion/manager-2 Fix base address, refactor add function

xHector1337 · 2026-03-22T06:46:03Z

[2500] [LOAD EXTENSION] Adding command ID to response: 1072
[2500] [LOAD EXTENSION] Adding command ID to response: 1071
[2500] [LOAD EXTENSION] Adding command ID to response: 1077
[2500] [LOAD EXTENSION] Adding command ID to response: 1069
[2500] [LOAD EXTENSION] Adding command ID to response: 1068
[2500] [LOAD EXTENSION] Adding command ID to response: 1067
[2500] [LOAD EXTENSION] Adding command ID to response: 1012
[2500] [LOAD EXTENSION] Adding command ID to response: 1013
[2500] [LOAD EXTENSION] Adding command ID to response: 1015
[2500] [LOAD EXTENSION] Adding command ID to response: 1010
[2500] [LOAD EXTENSION] Adding command ID to response: 1005
[2500] [LOAD EXTENSION] Adding command ID to response: 1007
[2500] [LOAD EXTENSION] Adding command ID to response: 1006
[2500] [LOAD EXTENSION] Adding command ID to response: 1016
[2500] [LOAD EXTENSION] Adding command ID to response: 1014
[2500] [LOAD EXTENSION] Adding command ID to response: 1004
[2500] [LOAD EXTENSION] Adding command ID to response: 1003
[2500] [LOAD EXTENSION] Adding command ID to response: 1011
[2500] [LOAD EXTENSION] Adding command ID to response: 1001
[2500] [LOAD EXTENSION] Adding command ID to response: 1008
[2500] [LOAD EXTENSION] Adding command ID to response: 1009
[2500] [LOAD EXTENSION] Adding command ID to response: 1031
[2500] [LOAD EXTENSION] Adding command ID to response: 1030
[2500] [LOAD EXTENSION] Adding command ID to response: 1029
[2500] [LOAD EXTENSION] Adding command ID to response: 1028
[2500] [LOAD EXTENSION] Adding command ID to response: 4
[2500] [extension_encryption][extension_encryption_add] Adding extension
[2500] [extension_encryption][extension_encryption_add] .text section of the extension is found!
[2500] [extension_encryption][extension_encryption_add] lpExtensionStatus->bEncryptable: 1
[2500] [extension_encryption][extension_encryption_add] lpExtensionStatus->bEncrypted: 0
[2500] [extension_encryption][extension_encryption_add] lpExtensionStatus->lpLoc: 00000000008D1000
[2500] [extension_encryption][extension_encryption_add] lpExtensionStatus->dwSize: 323376
[2500] [extension_encryption][extension_encryption_add] lpExtensionStatus->dwLastUsedTime: 326078
[2500] [extension_encryption][extension_encryption_add] Added extension text section at 00000000008D1000 of size 323376
[2500] [extension_encryption][extension_encryption_add] Function exiting

DebugString: "[27e8] [DISPATCH] Packet type for 1072 is 0"
DebugString: "[27e8] [DISPATCH] executing request handler 1072"
DebugString: "[27e8] [DISPATCH] Calling extensionFindDecrypt for command 1072"
DebugString: "[27e8] [extension_encryption][extension_encryption_get] Getting extension."
DebugString: "[27e8] [extension_encryption][extension_encryption_get] Function exiting."
DebugString: "[27e8] [COMMAND] Decryption successful for command 1072"

Copilot

Pull request overview

Adds an “Extension Encryption Manager” to metsrv and wires it into extension load and dispatch paths so extensions flagged as encryptable can be tracked and (de)crypted around handler execution.

Changes:

Add extension_encryption.{c,h} implementing a global extension encryption manager (debug + RC4 managers) and routines to add/find/(de)crypt extensions.
Initialize the manager during server setup; register encryptable, reflectively-loaded extensions during core_loadlib.
Attempt decryption before running extension handlers in the command dispatcher and scheduler; periodically encrypt unused extensions.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 11 comments.

Show a summary per file

File	Description
c/meterpreter/workspace/metsrv/metsrv.vcxproj	Adds new extension encryption source/header to the build.
c/meterpreter/workspace/metsrv/metsrv.vcxproj.filters	Adds new files to Visual Studio filters.
c/meterpreter/source/metsrv/server_setup.c	Initializes the Extension Encryption Manager during server setup.
c/meterpreter/source/metsrv/remote_dispatch.c	Registers encryptable, reflectively-loaded extensions with the manager.
c/meterpreter/source/metsrv/base.c	Attempts extension decryption before handler execution; triggers “encrypt unused” after command handling.
c/meterpreter/source/metsrv/scheduler.c	Attempts extension decryption before scheduled routine execution.
c/meterpreter/source/metsrv/extension_encryption.h	Declares manager/status structs and public APIs.
c/meterpreter/source/metsrv/extension_encryption.c	Implements manager initialization, extension tracking, and (de)cryption routines.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-16T15:38:38Z

+					if (!extensionFindDecryptVal || extensionFindDecryptVal == EXTENSION_ENCRYPTION_EXTENSION_NOT_ENCRYPTABLE) {
+						dprintf("[COMMAND] Decryption successful for command %u", commandId);
+					}
+					else {
+						dprintf("[COMMAND] Decryption failed for command %u", commandId);
+						//break;
+					}
 					serverContinue = command->request.inline_handler(remote, packet, &result) && serverContinue;
 					dprintf("[DISPATCH] executed %u, continue %s", commandId, serverContinue ? "yes" : "no");
 				}
 				else
 				{
 					dprintf("[DISPATCH] executing request handler %u", commandId);
+					dprintf("[DISPATCH] Calling extensionFindDecrypt for command %u", commandId);
+					extensionFindDecryptVal = extensionFindDecrypt(command->request.handler);
+					if (!extensionFindDecryptVal || extensionFindDecryptVal == EXTENSION_ENCRYPTION_EXTENSION_NOT_ENCRYPTABLE) {
+						dprintf("[COMMAND] Decryption successful for command %u", commandId);
+					}
+					else {
+						dprintf("[COMMAND] Decryption failed for command %u", commandId);
+						//break;
+					}
 					result = command->request.handler(remote, packet);


If extensionFindDecrypt() reports a decryption failure, the handler is still invoked. For handlers located inside an encrypted extension, this risks executing encrypted bytes (crash/undefined behavior). Consider short-circuiting the dispatch when decryption fails (except for "not encryptable" / "not found" cases), and avoid logging "Decryption successful" unless the return code indicates success.

Suggested change

if (!extensionFindDecryptVal || extensionFindDecryptVal == EXTENSION_ENCRYPTION_EXTENSION_NOT_ENCRYPTABLE) {

dprintf("[COMMAND] Decryption successful for command %u", commandId);

}

else {

dprintf("[COMMAND] Decryption failed for command %u", commandId);

//break;

}

serverContinue = command->request.inline_handler(remote, packet, &result) && serverContinue;

dprintf("[DISPATCH] executed %u, continue %s", commandId, serverContinue ? "yes" : "no");

}

else

{

dprintf("[DISPATCH] executing request handler %u", commandId);

dprintf("[DISPATCH] Calling extensionFindDecrypt for command %u", commandId);

extensionFindDecryptVal = extensionFindDecrypt(command->request.handler);

if (!extensionFindDecryptVal || extensionFindDecryptVal == EXTENSION_ENCRYPTION_EXTENSION_NOT_ENCRYPTABLE) {

dprintf("[COMMAND] Decryption successful for command %u", commandId);

}

else {

dprintf("[COMMAND] Decryption failed for command %u", commandId);

//break;

}

result = command->request.handler(remote, packet);

if (!extensionFindDecryptVal) {

dprintf("[COMMAND] Decryption successful for command %u", commandId);

serverContinue = command->request.inline_handler(remote, packet, &result) && serverContinue;

dprintf("[DISPATCH] executed %u, continue %s", commandId, serverContinue ? "yes" : "no");

}

else if (extensionFindDecryptVal == EXTENSION_ENCRYPTION_EXTENSION_NOT_ENCRYPTABLE

|| extensionFindDecryptVal == EXTENSION_ENCRYPTION_EXTENSION_NOT_FOUND) {

dprintf("[COMMAND] Decryption not required for command %u", commandId);

serverContinue = command->request.inline_handler(remote, packet, &result) && serverContinue;

dprintf("[DISPATCH] executed %u, continue %s", commandId, serverContinue ? "yes" : "no");

}

else {

dprintf("[COMMAND] Decryption failed for command %u with error %u", commandId, extensionFindDecryptVal);

result = extensionFindDecryptVal;

}

}

else

{

dprintf("[DISPATCH] executing request handler %u", commandId);

dprintf("[DISPATCH] Calling extensionFindDecrypt for command %u", commandId);

extensionFindDecryptVal = extensionFindDecrypt(command->request.handler);

if (!extensionFindDecryptVal) {

dprintf("[COMMAND] Decryption successful for command %u", commandId);

result = command->request.handler(remote, packet);

}

else if (extensionFindDecryptVal == EXTENSION_ENCRYPTION_EXTENSION_NOT_ENCRYPTABLE

|| extensionFindDecryptVal == EXTENSION_ENCRYPTION_EXTENSION_NOT_FOUND) {

dprintf("[COMMAND] Decryption not required for command %u", commandId);

result = command->request.handler(remote, packet);

}

else {

dprintf("[COMMAND] Decryption failed for command %u with error %u", commandId, extensionFindDecryptVal);

result = extensionFindDecryptVal;

}

Copilot · 2026-04-16T15:38:39Z

+		manager->lpCryptoParams = (LPCSTR)HeapAlloc(GetProcessHeap(), HEAP_ZERO_MEMORY, KEY_SIZE_RC4);
+		if (manager->lpCryptoParams == NULL) {
+			dprintf("[cryptographic_manager_rc4] HeapAlloc failed.");
+			return FALSE;
+		}
+		srand((unsigned int)GetTickCount());
+		for(int i = 0; i < KEY_SIZE_RC4; i++) {
+			((char*)manager->lpCryptoParams)[i] = (char)(rand() % 256);
+		}


RC4 key generation falls back to srand(GetTickCount()) + rand(), which is predictable and not suitable for generating cryptographic keys. If RC4 mode is intended to provide real confidentiality (not just a debug PoC), use a CSPRNG (e.g., BCryptGenRandom / RtlGenRandom) to fill lpCryptoParams.

Copilot · 2026-04-16T15:38:39Z

+				extensionFindDecryptValue = extensionFindDecrypt(entry->routine);
+				if (extensionFindDecryptValue && extensionFindDecryptValue != EXTENSION_ENCRYPTION_EXTENSION_NOT_ENCRYPTABLE) {
+					dprintf("[SCHEDULER] scheduler_waitable_thread ( 0x%08X ), decryption of the extension failed");
+					//break;


When extensionFindDecrypt() indicates a decryption failure, the code still calls entry->routine(...). If the routine lives in an encrypted .text section, this can lead to executing encrypted bytes (crash/undefined behavior). Only invoke the routine when decryption succeeded (or the handler isn't within an encryptable extension), and avoid logging "decrypted successfully" on failure.

Suggested change

//break;

break;

yeah, this'll be uncommented in following PRs.

Copilot · 2026-04-16T15:38:40Z

+	EnterCriticalSection(&g_ExtensionEncryptionManager->cs);
+	do {
+		dprintf("[extension_encryption][extension_encryption_add] Adding extension");
+		if (g_ExtensionEncryptionManager->dwExtensionsCount >= MAX_EXTENSIONS) {
+			BREAK_WITH_ERROR("[extension_encryption][extension_encryption_add] Maximum number of extensions reached.", ERROR_NOT_ENOUGH_MEMORY);
+		}
+
+		if (hLib == NULL || hLib == INVALID_HANDLE_VALUE) {
+			BREAK_WITH_ERROR("[extension_encryption][extension_encryption_add] Invalid parameters.", ERROR_INVALID_PARAMETER);
+		}


extension_encryption_add() enters the manager critical section but only calls LeaveCriticalSection on the success path. Any BREAK_WITH_ERROR(...) will break out of the loop and return while still holding the lock, causing deadlocks in all future extension-encryption operations. Restructure so the critical section is always released (e.g., a single LeaveCriticalSection after the do { ... } while (0) block).

this is a good catch!

Copilot · 2026-04-16T15:38:40Z

+	if (!bError) {
+		for (DWORD i = 0; i != ExtensionSize; i += diff) {
+			if ((ExtensionSize - i) < BUFFER_SIZE) {
+				diff = ExtensionSize - i;
+			}
+			ret = ReadProcessMemory(GetCurrentProcess(), (unsigned char*)ExtensionLoc + i, lpTempBufferRead, diff, &ByteCounter);
+			if (!ret || ByteCounter != diff) {
+				dprintf("[extension_encryption][extension_encryption_encrypt] ReadProcessMemory failed with error 0x%x", GetLastError());
+				break;
+			}
+			if (!g_ExtensionEncryptionManager->cryptoManager.encrypt(lpTempBufferRead, diff, lpTempBufferWrite, BUFFER_SIZE)) {
+				dprintf("[extension_encryption][extension_encryption_encrypt] CryptographicManager encrypt failed.");
+				ret = FALSE;
+				break;
+			}
+			ret = WriteProcessMemory(GetCurrentProcess(), (unsigned char*)ExtensionLoc + i, lpTempBufferWrite, diff, &ByteCounter);
+			if (!ret || ByteCounter != diff) {
+				dprintf("[extension_encryption][extension_encryption_encrypt] WriteProcessMemory failed with error 0x%x", GetLastError());
+				break;
+			}
+		}
+
+		lpExtensionStatus->dwLastUsedTime = GetTickCount();
+		lpExtensionStatus->bEncrypted = TRUE;
+	}


extension_encryption_encrypt() sets lpExtensionStatus->bEncrypted = TRUE even if the loop breaks early due to Read/Write/Crypto failure (those paths don't set bError). This can mark a partially-encrypted extension as "encrypted" and break subsequent decrypt/execute logic. Only flip bEncrypted (and update dwLastUsedTime) after a verified full success, and treat partial failures as errors.

this is a good catch as well!

Copilot · 2026-04-16T15:38:40Z

+		return EXTENSION_ENCRYPTION_EXTENSION_NOT_ENCRYPTABLE;
+	}
+
+	if (!extensionStatus->bEncrypted || !encryptionManager->decrypt(extensionStatus)) {


extensionFindDecrypt() currently returns EXTENSION_ENCRYPTION_DECRYPTION_ERROR when the extension is not encrypted because of if (!extensionStatus->bEncrypted || !decrypt(...)). This should be the opposite: if it's already decrypted, return success; only call decrypt() (and fail) when bEncrypted is true and decryption fails.

Suggested change

if (!extensionStatus->bEncrypted || !encryptionManager->decrypt(extensionStatus)) {

if (!extensionStatus->bEncrypted) {

return ERROR_SUCCESS;

}

if (!encryptionManager->decrypt(extensionStatus)) {

Copilot · 2026-04-16T15:38:41Z

-	} while (0);

+	} while (0);
+	extension_encryption_encrypt_unused();


command_handle calls extension_encryption_encrypt_unused() unconditionally. If InitExtensionEncryptionManager() failed (or was never called), extension_encryption_encrypt_unused() dereferences g_ExtensionEncryptionManager and will crash. Guard this call (or make extension_encryption_encrypt_unused() a no-op when the manager is NULL).

Suggested change

extension_encryption_encrypt_unused();

if (g_ExtensionEncryptionManager != NULL)

{

extension_encryption_encrypt_unused();

}

yeah good catch, we might not need the below suggestion if we do this. I'm not sure, I will take a look at it on VS.

Copilot · 2026-04-16T15:38:41Z

+			if(encryptionManager == NULL) {
+				dprintf("[SERVER] Extension Encryption Manager Initialization failed! proceeding without extension encryption.");


InitExtensionEncryptionManager() failure is logged as "proceeding without extension encryption", but other paths (e.g., command_handle -> extension_encryption_encrypt_unused) assume the manager exists and will dereference a NULL global. Either ensure init cannot fail here, or fully gate all extension-encryption calls on successful initialization.

Suggested change

if(encryptionManager == NULL) {

dprintf("[SERVER] Extension Encryption Manager Initialization failed! proceeding without extension encryption.");

if (encryptionManager == NULL)

{

dprintf("[SERVER] Extension Encryption Manager initialization failed, aborting server setup.");

break;

hmm, this is the tricky part. For now, we dont need it since every extension is not encryptable. But in the future, a similar mechanism can be implemented. What do you think @dledda-r7 ?

we should probably cover this edge case now

ok I will fix these on this weekend.

Copilot · 2026-04-16T15:38:41Z

+DWORD cryptographic_manager_rc4_encrypt(LPVOID lpDataIn, DWORD dwDataInSize, LPVOID lpDataOut, DWORD dwDataOutSize) {
+	RC4_CTX* ctx = (RC4_CTX*)g_ExtensionEncryptionManager->cryptoManager.lpCryptoContext;
+	if (ctx == NULL) {
+		dprintf("[cryptographic_manager_rc4_encrypt] lpCryptoContext is NULL.");
+		return 0;
+	}
+	if (dwDataOutSize < dwDataInSize) {
+		dprintf("[cryptographic_manager_rc4_encrypt] dwDataOutSize is smaller than dwDataInSize.");
+		return 0;
+	}
+	memcpy(lpDataOut, lpDataIn, dwDataInSize);
+	if (!RC4Cipher(ctx, (unsigned char*)lpDataOut, dwDataInSize)) {
+		dprintf("[cryptographic_manager_rc4_encrypt] RC4Cipher failed.");
+		return 0;
+	}
+	return dwDataInSize;


RC4 encryption/decryption uses a single RC4_CTX that is mutated by RC4Cipher. Because cryptographic_manager_rc4_encrypt() doesn't refresh/reset the context before each encryption, the keystream position depends on previous operations, making later decryptions (which do refresh in extension_encryption_decrypt) incorrect. Refresh/reset the RC4 context before both encrypt and decrypt operations (or use a per-operation/per-extension context) so encrypt/decrypt are reversible.

that's right, but I'm not sure about this. Imho we were calling the Initialiser before every cipher call, but I'm not sure.

that was a good catch

Copilot · 2026-04-16T15:38:41Z

+
+	EnterCriticalSection(&g_ExtensionEncryptionManager->cs);
+	ExtensionEncryptionStatus** extension_statuses = g_ExtensionEncryptionManager->extensionStatuses;
+	DWORD current_time = GetTickCount();
+	for (DWORD i = 0; i < g_ExtensionEncryptionManager->dwExtensionsCount; i++) {
+		ExtensionEncryptionStatus* status = extension_statuses[i];
+		if (status != NULL && status->bEncryptable && !status->bEncrypted) {
+			if (current_time - status->dwLastUsedTime > ENCRYPTION_UNUSED_COOLDOWN_MS) {
+				g_ExtensionEncryptionManager->encrypt(status);
+			}
+		}
+	}
+	LeaveCriticalSection(&g_ExtensionEncryptionManager->cs);


extension_encryption_encrypt_unused() assumes g_ExtensionEncryptionManager is non-NULL and immediately enters its critical section. If the manager wasn't initialized (or init failed), this will crash. Add a NULL check at the start and return early when the manager is unavailable.

Suggested change

EnterCriticalSection(&g_ExtensionEncryptionManager->cs);

ExtensionEncryptionStatus** extension_statuses = g_ExtensionEncryptionManager->extensionStatuses;

DWORD current_time = GetTickCount();

for (DWORD i = 0; i < g_ExtensionEncryptionManager->dwExtensionsCount; i++) {

ExtensionEncryptionStatus* status = extension_statuses[i];

if (status != NULL && status->bEncryptable && !status->bEncrypted) {

if (current_time - status->dwLastUsedTime > ENCRYPTION_UNUSED_COOLDOWN_MS) {

g_ExtensionEncryptionManager->encrypt(status);

}

}

}

LeaveCriticalSection(&g_ExtensionEncryptionManager->cs);

ExtensionEncryptionManager* encryptionManager = g_ExtensionEncryptionManager;

if (encryptionManager == NULL) {

return;

}

EnterCriticalSection(&encryptionManager->cs);

ExtensionEncryptionStatus** extension_statuses = encryptionManager->extensionStatuses;

DWORD current_time = GetTickCount();

for (DWORD i = 0; i < encryptionManager->dwExtensionsCount; i++) {

ExtensionEncryptionStatus* status = extension_statuses[i];

if (status != NULL && status->bEncryptable && !status->bEncrypted) {

if (current_time - status->dwLastUsedTime > ENCRYPTION_UNUSED_COOLDOWN_MS) {

encryptionManager->encrypt(status);

}

}

}

LeaveCriticalSection(&encryptionManager->cs);

nice. Gonna check the remaining ones later. @dledda-r7

… in extension encryption functions

…function

…in extension encryption, sync rc4 stream

…duler threads

…tion/manager-2 some other fixes

xHector1337 and others added 10 commits February 2, 2026 11:29

Add extension encryption manager

1554bc2

feat: extension encryption manager, wiring to library loading and com…

72214ad

…mand handling

fix: minor fixes in extension_encryption.c

b796d8b

feat: integrate Extension Encryption Manager into server setup

f7a0384

fix: streamline Extension Encryption Manager initialization in server…

e772f2e

… setup

fix: correct indentation for extension encryption includes in project…

a2b09b1

… files

fix: update extension count handling in extension encryption manager

24288ca

feat: enhance command processing with extension decryption support

094c1fe

feat: add get method to Extension Encryption Manager and improve erro…

f787835

…r handling

Add extension encryption manager

df37b63

xHector1337 force-pushed the add-extension-encryption-manager branch from b7248da to df37b63 Compare February 4, 2026 14:39

xHector1337 and others added 7 commits February 4, 2026 19:03

Merge branch 'add-extension-encryption-manager' into collab/feat/add-…

e37cf9c

…extension-encryption/manager

Merge pull request #2 from dledda-r7/collab/feat/add-extension-encryp…

7e2b157

…tion/manager Collaboration Extension Encryption

bug fix

14db760

revert the usage of GetTickCount in extension_encryption_encrypt

53441ce

add extensionFindDecrypt function

628ca94

add additional checks into extensionFindDecrypt and use it in command…

7559689

…_process_inline

modify the scheduler to make it work with extension encryption

3511b2f

dledda-r7 reviewed Feb 10, 2026

View reviewed changes

xHector1337 and others added 6 commits February 11, 2026 18:57

bug fix in extension_encryption_add

985727e

store CryptographicManagerType in ExtensionEncryptionManager

f82a4e7

use extension_encrypt_unused in the command handler

6141c1d

define a new error type for extensionFindDecrypt and implement it on …

524575c

…the scheduler and command_process_inline

update extension_encryption.c

699fee0

fix: using correct base address for extension encryption manager, ref…

41918bd

…actor add function

Merge pull request #3 from dledda-r7/collab/feat/add-extension-encryp…

b900afd

…tion/manager-2 Fix base address, refactor add function

xHector1337 marked this pull request as ready for review March 22, 2026 06:46

dledda-r7 requested a review from Copilot April 16, 2026 15:31

Copilot started reviewing on behalf of dledda-r7 April 16, 2026 15:31 View session

Copilot AI reviewed Apr 16, 2026

View reviewed changes

dledda-r7 and others added 6 commits April 16, 2026 11:43

fix: ensure proper handling of encryption status and error conditions…

ca3b916

… in extension encryption functions

fix: add null check for ExtensionEncryptionManager in unused encrypt …

9ab8ab1

…function

fix: enhance cryptographic manager initialization and error handling …

2e03b92

…in extension encryption, sync rc4 stream

fix: improve decryption error handling in command processing and sche…

5187695

…duler threads

Merge pull request #4 from dledda-r7/collab/feat/add-extension-encryp…

845714c

…tion/manager-2 some other fixes

bug fixes

8d71c52

-	if (!extensionStatus->bEncrypted || !encryptionManager->decrypt(extensionStatus)) {
+	if (!extensionStatus->bEncrypted) {
+		return ERROR_SUCCESS;
+	}
+	if (!encryptionManager->decrypt(extensionStatus)) {

		if(encryptionManager == NULL) {
		dprintf("[SERVER] Extension Encryption Manager Initialization failed! proceeding without extension encryption.");

Uh oh!

Conversation

xHector1337 commented Feb 2, 2026 • edited by dledda-r7 Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Extension Encryption: Encryption Manager

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

dledda-r7 commented Mar 5, 2026

Uh oh!

xHector1337 commented Mar 22, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

xHector1337 commented Feb 2, 2026 •

edited by dledda-r7

Loading