- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 96 for Kommunikation (0.12 sec)
-
docs/de/docs/tutorial/security/index.md
### OAuth 1 Es gab ein OAuth 1, das sich stark von OAuth2 unterscheidet und komplexer ist, da es direkte Spezifikationen enthält, wie die Kommunikation verschlüsselt wird. Heutzutage ist es nicht sehr populär und wird kaum verwendet. OAuth2 spezifiziert nicht, wie die Kommunikation verschlüsselt werden soll, sondern erwartet, dass Ihre Anwendung mit HTTPS bereitgestellt wird. /// tip | Tipp
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 10:49:48 UTC 2025 - 5.1K bytes - Viewed (0) -
docs/de/docs/deployment/https.md
Mithilfe des Zertifikats entscheiden der Client und der TLS-Terminierungsproxy dann, **wie der Rest der TCP-Kommunikation verschlüsselt werden soll**. Damit ist der **TLS-Handshake** abgeschlossen. Danach verfügen der Client und der Server über eine **verschlüsselte TCP-Verbindung**, via TLS. Und dann können sie diese Verbindung verwenden, um die eigentliche **HTTP-Kommunikation** zu beginnen.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun May 11 13:37:26 UTC 2025 - 13.6K bytes - Viewed (0) -
docs/de/docs/deployment/concepts.md
Das ist immer noch wahr. Um also **mehrere Prozesse** gleichzeitig zu haben, muss es einen **einzelnen Prozess geben, der einen Port überwacht**, welcher dann die Kommunikation auf irgendeine Weise an jeden Workerprozess überträgt. ### Arbeitsspeicher pro Prozess
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun May 11 13:37:26 UTC 2025 - 20.6K bytes - Viewed (0) -
android/guava/src/com/google/common/base/Ascii.java
/** * Enquiry: A communication control character used in data communication systems as a request for * a response from a remote station. It may be used as a "Who Are You" (WRU) to obtain * identification, or may be used to obtain station status, or both. * * @since 8.0 */ public static final byte ENQ = 5; /**
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Mon Mar 17 20:26:29 UTC 2025 - 21.7K bytes - Viewed (0) -
docs/en/docs/deployment/https.md
Then, using the certificate, the client and the TLS Termination Proxy **decide how to encrypt** the rest of the **TCP communication**. This completes the **TLS Handshake** part. After this, the client and the server have an **encrypted TCP connection**, this is what TLS provides. And then they can use that connection to start the actual **HTTP communication**.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 19:34:08 UTC 2025 - 14.3K bytes - Viewed (0) -
src/main/java/jcifs/ntlmssp/NtlmFlags.java
* the server. */ int NTLMSSP_REQUEST_TARGET = 0x00000004; /** * Specifies that communication across the authenticated channel * should carry a digital signature (message integrity). */ int NTLMSSP_NEGOTIATE_SIGN = 0x00000010; /** * Specifies that communication across the authenticated channel * should be encrypted (message confidentiality). */
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 5.5K bytes - Viewed (0) -
src/main/java/jcifs/smb1/ntlmssp/NtlmFlags.java
* the server. */ int NTLMSSP_REQUEST_TARGET = 0x00000004; /** * Specifies that communication across the authenticated channel * should carry a digital signature (message integrity). */ int NTLMSSP_NEGOTIATE_SIGN = 0x00000010; /** * Specifies that communication across the authenticated channel * should be encrypted (message confidentiality). */
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 5.1K bytes - Viewed (0) -
src/test/java/jcifs/smb1/smb1/NetShareEnumResponseTest.java
data[15] = 0x00; // type = 0 data[16] = 40; data[17] = 0; data[18] = 0; data[19] = 0; // remark offset // Entry 2: IPC$, type 3 (IPC), remark "Inter-Process Communication" System.arraycopy("IPC$".getBytes(StandardCharsets.US_ASCII), 0, data, 20, 4); data[34] = 0x03; data[35] = 0x00; // type = 3 data[36] = 60; data[37] = 0; data[38] = 0;
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Thu Aug 14 05:31:44 UTC 2025 - 5.4K bytes - Viewed (0) -
src/main/java/jcifs/dcerpc/ndr/NdrObject.java
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA */ package jcifs.dcerpc.ndr; /** * Base class for NDR (Network Data Representation) objects used in DCE/RPC communication. * This abstract class defines the interface for encoding and decoding NDR data types. */ public abstract class NdrObject { /** * Default constructor for NDR object */ public NdrObject() {
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 1.7K bytes - Viewed (0) -
src/main/java/jcifs/smb1/dcerpc/ndr/NdrObject.java
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA */ package jcifs.smb1.dcerpc.ndr; /** * Base class for NDR (Network Data Representation) objects used in DCE/RPC communication. * This abstract class defines the interface for encoding and decoding NDR data types. */ public abstract class NdrObject { /** * Default constructor for NDR object */ public NdrObject() {
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 1.7K bytes - Viewed (0)