### 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

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**.

     * 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).
     */

    * 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).
    */

        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;

 * 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() {

 * 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() {

 */
package jcifs.ntlmssp.av;

/**
 * NTLMSSP AV pair representing channel binding information for enhanced security.
 * Used to bind NTLM authentication to specific communication channels.
 *
 * @author mbechler
 */
public class AvChannelBindings extends AvPair {

    /**
     * Constructs an AV channel bindings pair
     * @param channelBindingHash the channel binding hash value

import jcifs.smb.SmbNamedPipe;
import jcifs.smb.SmbPipeHandleInternal;
import jcifs.util.Encdec;

/**
 * DCE/RPC handle implementation for named pipe communications.
 * This class provides DCE/RPC communication over SMB named pipes.
 */
public class DcerpcPipeHandle extends DcerpcHandle {

    /* This 0x20000 bit is going to get chopped! */

    private final DcerpcHandle handle;
    private boolean opened;

    /**
     * Creates a new SAM policy handle.
     *
     * @param handle the DCE/RPC handle for communication
     * @param server the server name (null defaults to local server)
     * @param access the desired access rights
     * @throws IOException if an I/O error occurs during handle creation
     */