X-Git-Url: https://de.git.xonotic.org/?a=blobdiff_plain;f=qcsrc%2Fserver%2Fextensions.qh;h=b72a0500013dc8402a8257d8febd4baef1bd6f75;hb=1194c6af3ef2abc72d7aaced018398ca43f860e4;hp=33973f8e0480e6f44ff6703d484eebe3d9caa4c7;hpb=085647522d27ce3fe59a351d050d9cb9ac4be81b;p=xonotic%2Fxonotic-data.pk3dir.git

diff --git a/qcsrc/server/extensions.qh b/qcsrc/server/extensions.qh
index 33973f8e0..b72a05000 100644
--- a/qcsrc/server/extensions.qh
+++ b/qcsrc/server/extensions.qh
@@ -574,10 +574,8 @@ float(float a) tan = #475; // returns tangent value (which is simply sin(a)/cos(
 //changing the cvar or returning from progs is UNDEFINED. Writing to autocvar
 //globals is UNDEFINED. Accessing autocvar globals after cvar_set()ing that
 //cvar is IMPLEMENTATION DEFINED (an implementation may either yield the
-//previous, or the current, value). Whether autocvar globals, after restoring
-//a savegame, have the cvar's current value, or the original value at time of
-//saving, is UNDEFINED. Restoring a savegame however must not restore the
-//cvar values themselves. Writing to an autocvar global is NOT ALLOWED.
+//previous, or the current, value). Writing to an autocvar global is NOT
+//ALLOWED.
 //In case the cvar does NOT exist, then it is automatically created with the
 //value of the autocvar initializer, if given. This is possible with e.g.
 //frikqcc and fteqcc the following way:
@@ -2311,3 +2309,15 @@ float JOINTTYPE_HINGE2 = 5; // hinge2; uses origin (anchor), angles (axis1), vel
 //description:
 //various physics properties can be defined in an entity and are executed via
 //ODE
+
+//DP_CRYPTO
+//idea: divVerent
+//darkplaces implementation: divVerent
+//field definitions: (SVQC)
+.string crypto_keyfp; // fingerprint of CA key the player used to authenticate, or string_null if not verified
+.string crypto_mykeyfp; // fingerprint of CA key the server used to authenticate to the player, or string_null if not verified
+.string crypto_idfp; // fingerprint of ID used by the player entity, or string_null if not identified
+.string crypto_encryptmethod; // the string "AES128" if encrypting, and string_null if plaintext
+.string crypto_signmethod; // the string "HMAC-SHA256" if signing, and string_null if plaintext
+// there is no field crypto_myidfp, as that info contains no additional information the QC may have a use for
+//description: