xmlservice: my service (software) is removed continuously after a Windows 10 update on a laptop / client

I have a service that runs in my clients' notebooks that use my software (Xmlservice)
I install this service from an installation project as an output file.
When Microsoft releases the update (for example, 1803 or later), this hosted service will be removed from the client and my software will no longer work. I have to do a new installation from my software.
This is how my service is hosted:

    void OpenHost()
    {
       const string strAdrHttp = "http://localhost:port/XmlService"
       Uri() adrbase = { new Uri(strAdrHttp) };

            _svcHost = new ServiceHost(typeof(SealedClassinHere), adrbase);

            var mBehave = new ServiceMetadataBehavior { HttpGetEnabled = true };
            _svcHost.Description.Behaviors.Add(mBehave);

            var httpb = new WSHttpBinding
            {
                ReaderQuotas =
                {
                    MaxArrayLength = 10485760, MaxStringContentLength = 2524288
                }, //max 10MB compressed transport
                MaxBufferPoolSize = 2524288,
                MaxReceivedMessageSize = 2524288,
                Security = { Mode = SecurityMode.None, Message = { ClientCredentialType = 
                MessageCredentialType.None } }
            };

            _svcHost.AddServiceEndpoint(typeof(IService), httpb, strAdrHttp);

            _svcHost.AddServiceEndpoint(typeof(IMetadataExchange),
            MetadataExchangeBindings.CreateMexHttpBinding(), "mex");

            _svcHost.Open();
     }

tls: the client wants us to use his SSL certificate on our server

He is not a system administrator here. So please forgive ignorance.
I have read the Q / A suggested here:

My question is:
How do I obtain an SSL Certificate from my client (even if it is created for use with multiple names) and apply it to my server?

Here is my situation.
We have an AWS instance / DB that serves a site we create for a customer.
The site is in: subdomain.domain.com. We have our own SSL on that.
The customer has created a C name that points to our site / domain name, therefore:

subdomain.ofclientsdomain.com -> subdomain.ofourdomain.com

The browser throws a warning using its Cname URL.

The client asked if you can send me YOUR Certificate.

I don't know how that would be done. I have never had someone send me their Certificate.

Should I go back to the approved solution in the linked question / solution and tell them to create a certificate with our two domains? If so, how does that apply? Since it is my server?
Thank you
James

Transmit client cameras from the server side

There is a way to view the specific client camera from the server (using RawImage ..) and the synchronization view. I tried RenderTextue, but I didn't find a solution for that.

tls: server that sends RST after the Hello client

We face an intermittent TLS handshake problem when connecting from a C ++ client (Openssl 1.0.2e) to a Java server (Java 7). The problem is observed in the load test after having about 100 sessions sending concise requests, that also on the Linux platform. The server is sending an RST message immediately after the "Hello Client" message. On the client side, the SSL_CTX object is created with TLSv1_2_client_method (). On the server side, the context instance is created by invoking SSLContext.getInstance ("TLSv1.2"). We are also limiting the protocol enabled to TLSv1.2 on the server side. When this problem is observed, we have noticed that the Client Greeting Protocol in Wireshark as "TLSv1", in all other cases (SUCCESS), the Client Greeting Protocol is shown as TLSv1.2.

I also understand that the version number of the Handshake layer is important and any server compatible with TLS1.2 MUST accept any value {03, XX} as the version number of the registration layer for ClientHello according to RFC5246. But every time the fault is observed, the record layer is "TLSv1 Record Layer: Handshake Protocol: Client Hello". In the case of a successful link protocol, the registration layer is "TLSv1.2 Record Layer: Handshake Protocol: Client Hello". The customer greeting message for both cases is provided below, keep in mind that the encryption sets and the signature algorithm are the same in both cases.

Customer greeting message when a problem occurs:

Transport Layer Security
TLSv1 Record Layer: Handshake Protocol: Client Hello
    Content Type: Handshake (22)
    Version: TLS 1.0 (0x0301)
    Length: 358
    Handshake Protocol: Client Hello
        Handshake Type: Client Hello (1)
        Length: 354
        Version: TLS 1.2 (0x0303)
        Random: 44e153eb9aa960e39e7dd4c01fbc1cc3770d95e0d70d6aac…
            GMT Unix Time: Aug 15, 2006 10:26:11.000000000 India Standard Time
            Random Bytes: 9aa960e39e7dd4c01fbc1cc3770d95e0d70d6aac83f458ab…
        Session ID Length: 0
        Cipher Suites Length: 228
        Cipher Suites (114 suites)
            Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)
            Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)
            Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028)
            Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024)
            Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)
            Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)
            Cipher Suite: TLS_DH_DSS_WITH_AES_256_GCM_SHA384 (0x00a5)
            Cipher Suite: TLS_DHE_DSS_WITH_AES_256_GCM_SHA384 (0x00a3)
            Cipher Suite: TLS_DH_RSA_WITH_AES_256_GCM_SHA384 (0x00a1)
            Cipher Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f)
            Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x006b)
            Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 (0x006a)
            Cipher Suite: TLS_DH_RSA_WITH_AES_256_CBC_SHA256 (0x0069)
            Cipher Suite: TLS_DH_DSS_WITH_AES_256_CBC_SHA256 (0x0068)
            Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
            Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
            Cipher Suite: TLS_DH_RSA_WITH_AES_256_CBC_SHA (0x0037)
            Cipher Suite: TLS_DH_DSS_WITH_AES_256_CBC_SHA (0x0036)
            Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0088)
            Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA (0x0087)
            Cipher Suite: TLS_DH_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0086)
            Cipher Suite: TLS_DH_DSS_WITH_CAMELLIA_256_CBC_SHA (0x0085)
            Cipher Suite: TLS_ECDH_anon_WITH_AES_256_CBC_SHA (0xc019)
            Cipher Suite: TLS_DH_anon_WITH_AES_256_GCM_SHA384 (0x00a7)
            Cipher Suite: TLS_DH_anon_WITH_AES_256_CBC_SHA256 (0x006d)
            Cipher Suite: TLS_DH_anon_WITH_AES_256_CBC_SHA (0x003a)
            Cipher Suite: TLS_DH_anon_WITH_CAMELLIA_256_CBC_SHA (0x0089)
            Cipher Suite: TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384 (0xc032)
            Cipher Suite: TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02e)
            Cipher Suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384 (0xc02a)
            Cipher Suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384 (0xc026)
            Cipher Suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA (0xc00f)
            Cipher Suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA (0xc005)
            Cipher Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d)
            Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d)
            Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
            Cipher Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0084)
            Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)
            Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)
            Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027)
            Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023)
            Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)
            Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)
            Cipher Suite: TLS_DH_DSS_WITH_AES_128_GCM_SHA256 (0x00a4)
            Cipher Suite: TLS_DHE_DSS_WITH_AES_128_GCM_SHA256 (0x00a2)
            Cipher Suite: TLS_DH_RSA_WITH_AES_128_GCM_SHA256 (0x00a0)
            Cipher Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e)
            Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (0x0067)
            Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 (0x0040)
            Cipher Suite: TLS_DH_RSA_WITH_AES_128_CBC_SHA256 (0x003f)
            Cipher Suite: TLS_DH_DSS_WITH_AES_128_CBC_SHA256 (0x003e)
            Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
            Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
            Cipher Suite: TLS_DH_RSA_WITH_AES_128_CBC_SHA (0x0031)
            Cipher Suite: TLS_DH_DSS_WITH_AES_128_CBC_SHA (0x0030)
            Cipher Suite: TLS_DHE_RSA_WITH_SEED_CBC_SHA (0x009a)
            Cipher Suite: TLS_DHE_DSS_WITH_SEED_CBC_SHA (0x0099)
            Cipher Suite: TLS_DH_RSA_WITH_SEED_CBC_SHA (0x0098)
            Cipher Suite: TLS_DH_DSS_WITH_SEED_CBC_SHA (0x0097)
            Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0045)
            Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA (0x0044)
            Cipher Suite: TLS_DH_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0043)
            Cipher Suite: TLS_DH_DSS_WITH_CAMELLIA_128_CBC_SHA (0x0042)
            Cipher Suite: TLS_ECDH_anon_WITH_AES_128_CBC_SHA (0xc018)
            Cipher Suite: TLS_DH_anon_WITH_AES_128_GCM_SHA256 (0x00a6)
            Cipher Suite: TLS_DH_anon_WITH_AES_128_CBC_SHA256 (0x006c)
            Cipher Suite: TLS_DH_anon_WITH_AES_128_CBC_SHA (0x0034)
            Cipher Suite: TLS_DH_anon_WITH_SEED_CBC_SHA (0x009b)
            Cipher Suite: TLS_DH_anon_WITH_CAMELLIA_128_CBC_SHA (0x0046)
            Cipher Suite: TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256 (0xc031)
            Cipher Suite: TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02d)
            Cipher Suite: TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256 (0xc029)
            Cipher Suite: TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 (0xc025)
            Cipher Suite: TLS_ECDH_RSA_WITH_AES_128_CBC_SHA (0xc00e)
            Cipher Suite: TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA (0xc004)
            Cipher Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c)
            Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c)
            Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
            Cipher Suite: TLS_RSA_WITH_SEED_CBC_SHA (0x0096)
            Cipher Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0041)
            Cipher Suite: TLS_RSA_WITH_IDEA_CBC_SHA (0x0007)
            Cipher Suite: TLS_ECDHE_RSA_WITH_RC4_128_SHA (0xc011)
            Cipher Suite: TLS_ECDHE_ECDSA_WITH_RC4_128_SHA (0xc007)
            Cipher Suite: TLS_ECDH_anon_WITH_RC4_128_SHA (0xc016)
            Cipher Suite: TLS_DH_anon_WITH_RC4_128_MD5 (0x0018)
            Cipher Suite: TLS_ECDH_RSA_WITH_RC4_128_SHA (0xc00c)
            Cipher Suite: TLS_ECDH_ECDSA_WITH_RC4_128_SHA (0xc002)
            Cipher Suite: TLS_RSA_WITH_RC4_128_SHA (0x0005)
            Cipher Suite: TLS_RSA_WITH_RC4_128_MD5 (0x0004)
            Cipher Suite: TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA (0xc012)
            Cipher Suite: TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA (0xc008)
            Cipher Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016)
            Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013)
            Cipher Suite: TLS_DH_RSA_WITH_3DES_EDE_CBC_SHA (0x0010)
            Cipher Suite: TLS_DH_DSS_WITH_3DES_EDE_CBC_SHA (0x000d)
            Cipher Suite: TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA (0xc017)
            Cipher Suite: TLS_DH_anon_WITH_3DES_EDE_CBC_SHA (0x001b)
            Cipher Suite: TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA (0xc00d)
            Cipher Suite: TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA (0xc003)
            Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
            Cipher Suite: TLS_DHE_RSA_WITH_DES_CBC_SHA (0x0015)
            Cipher Suite: TLS_DHE_DSS_WITH_DES_CBC_SHA (0x0012)
            Cipher Suite: TLS_DH_RSA_WITH_DES_CBC_SHA (0x000f)
            Cipher Suite: TLS_DH_DSS_WITH_DES_CBC_SHA (0x000c)
            Cipher Suite: TLS_DH_anon_WITH_DES_CBC_SHA (0x001a)
            Cipher Suite: TLS_RSA_WITH_DES_CBC_SHA (0x0009)
            Cipher Suite: TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA (0x0014)
            Cipher Suite: TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA (0x0011)
            Cipher Suite: TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA (0x0019)
            Cipher Suite: TLS_RSA_EXPORT_WITH_DES40_CBC_SHA (0x0008)
            Cipher Suite: TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (0x0006)
            Cipher Suite: TLS_DH_anon_EXPORT_WITH_RC4_40_MD5 (0x0017)
            Cipher Suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5 (0x0003)
            Cipher Suite: TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff)
        Compression Methods Length: 1
        Compression Methods (1 method)
            Compression Method: null (0)
        Extensions Length: 85
        Extension: ec_point_formats (len=4)
            Type: ec_point_formats (11)
            Length: 4
            EC point formats Length: 3
            Elliptic curves point formats (3)
                EC point format: uncompressed (0)
                EC point format: ansiX962_compressed_prime (1)
                EC point format: ansiX962_compressed_char2 (2)
        Extension: supported_groups (len=28)
            Type: supported_groups (10)
            Length: 28
            Supported Groups List Length: 26
            Supported Groups (13 groups)
                Supported Group: secp256r1 (0x0017)
                Supported Group: secp521r1 (0x0019)
                Supported Group: brainpoolP512r1 (0x001c)
                Supported Group: brainpoolP384r1 (0x001b)
                Supported Group: secp384r1 (0x0018)
                Supported Group: brainpoolP256r1 (0x001a)
                Supported Group: secp256k1 (0x0016)
                Supported Group: sect571r1 (0x000e)
                Supported Group: sect571k1 (0x000d)
                Supported Group: sect409k1 (0x000b)
                Supported Group: sect409r1 (0x000c)
                Supported Group: sect283k1 (0x0009)
                Supported Group: sect283r1 (0x000a)
        Extension: session_ticket (len=0)
            Type: session_ticket (35)
            Length: 0
            Data (0 bytes)
        Extension: signature_algorithms (len=32)
            Type: signature_algorithms (13)
            Length: 32
            Signature Hash Algorithms Length: 30
            Signature Hash Algorithms (15 algorithms)
                Signature Algorithm: rsa_pkcs1_sha512 (0x0601)
                    Signature Hash Algorithm Hash: SHA512 (6)
                    Signature Hash Algorithm Signature: RSA (1)
                Signature Algorithm: SHA512 DSA (0x0602)
                    Signature Hash Algorithm Hash: SHA512 (6)
                    Signature Hash Algorithm Signature: DSA (2)
                Signature Algorithm: ecdsa_secp521r1_sha512 (0x0603)
                    Signature Hash Algorithm Hash: SHA512 (6)
                    Signature Hash Algorithm Signature: ECDSA (3)
                Signature Algorithm: rsa_pkcs1_sha384 (0x0501)
                    Signature Hash Algorithm Hash: SHA384 (5)
                    Signature Hash Algorithm Signature: RSA (1)
                Signature Algorithm: SHA384 DSA (0x0502)
                    Signature Hash Algorithm Hash: SHA384 (5)
                    Signature Hash Algorithm Signature: DSA (2)
                Signature Algorithm: ecdsa_secp384r1_sha384 (0x0503)
                    Signature Hash Algorithm Hash: SHA384 (5)
                    Signature Hash Algorithm Signature: ECDSA (3)
                Signature Algorithm: rsa_pkcs1_sha256 (0x0401)
                    Signature Hash Algorithm Hash: SHA256 (4)
                    Signature Hash Algorithm Signature: RSA (1)
                Signature Algorithm: SHA256 DSA (0x0402)
                    Signature Hash Algorithm Hash: SHA256 (4)
                    Signature Hash Algorithm Signature: DSA (2)
                Signature Algorithm: ecdsa_secp256r1_sha256 (0x0403)
                    Signature Hash Algorithm Hash: SHA256 (4)
                    Signature Hash Algorithm Signature: ECDSA (3)
                Signature Algorithm: SHA224 RSA (0x0301)
                    Signature Hash Algorithm Hash: SHA224 (3)
                    Signature Hash Algorithm Signature: RSA (1)
                Signature Algorithm: SHA224 DSA (0x0302)
                    Signature Hash Algorithm Hash: SHA224 (3)
                    Signature Hash Algorithm Signature: DSA (2)
                Signature Algorithm: SHA224 ECDSA (0x0303)
                    Signature Hash Algorithm Hash: SHA224 (3)
                    Signature Hash Algorithm Signature: ECDSA (3)
                Signature Algorithm: rsa_pkcs1_sha1 (0x0201)
                    Signature Hash Algorithm Hash: SHA1 (2)
                    Signature Hash Algorithm Signature: RSA (1)
                Signature Algorithm: SHA1 DSA (0x0202)
                    Signature Hash Algorithm Hash: SHA1 (2)
                    Signature Hash Algorithm Signature: DSA (2)
                Signature Algorithm: ecdsa_sha1 (0x0203)
                    Signature Hash Algorithm Hash: SHA1 (2)
                    Signature Hash Algorithm Signature: ECDSA (3)
        Extension: heartbeat (len=1)
            Type: heartbeat (15)
            Length: 1
            Mode: Peer allowed to send requests (1)

Customer Hello when the handshake is successful:

TLSv1.2 Record Layer: Handshake Protocol: Client Hello
Content Type: Handshake (22)
Version: TLS 1.0 (0x0301)
Length: 358
Handshake Protocol: Client Hello
    Handshake Type: Client Hello (1)
    Length: 354
    Version: TLS 1.2 (0x0303)
    Random: b2e7fe85a0e4403ae4fec4d698094b919375f9afed8efff4…
    Session ID Length: 0
    Cipher Suites Length: 228
    Cipher Suites (114 suites)
        Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)
        Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)
        Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028)
        Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024)
        Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)
        Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)
        Cipher Suite: TLS_DH_DSS_WITH_AES_256_GCM_SHA384 (0x00a5)
        Cipher Suite: TLS_DHE_DSS_WITH_AES_256_GCM_SHA384 (0x00a3)
        Cipher Suite: TLS_DH_RSA_WITH_AES_256_GCM_SHA384 (0x00a1)
        Cipher Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f)
        Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x006b)
        Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 (0x006a)
        Cipher Suite: TLS_DH_RSA_WITH_AES_256_CBC_SHA256 (0x0069)
        Cipher Suite: TLS_DH_DSS_WITH_AES_256_CBC_SHA256 (0x0068)
        Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
        Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
        Cipher Suite: TLS_DH_RSA_WITH_AES_256_CBC_SHA (0x0037)
        Cipher Suite: TLS_DH_DSS_WITH_AES_256_CBC_SHA (0x0036)
        Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0088)
        Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA (0x0087)
        Cipher Suite: TLS_DH_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0086)
        Cipher Suite: TLS_DH_DSS_WITH_CAMELLIA_256_CBC_SHA (0x0085)
        Cipher Suite: TLS_ECDH_anon_WITH_AES_256_CBC_SHA (0xc019)
        Cipher Suite: TLS_DH_anon_WITH_AES_256_GCM_SHA384 (0x00a7)
        Cipher Suite: TLS_DH_anon_WITH_AES_256_CBC_SHA256 (0x006d)
        Cipher Suite: TLS_DH_anon_WITH_AES_256_CBC_SHA (0x003a)
        Cipher Suite: TLS_DH_anon_WITH_CAMELLIA_256_CBC_SHA (0x0089)
        Cipher Suite: TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384 (0xc032)
        Cipher Suite: TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02e)
        Cipher Suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384 (0xc02a)
        Cipher Suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384 (0xc026)
        Cipher Suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA (0xc00f)
        Cipher Suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA (0xc005)
        Cipher Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d)
        Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d)
        Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
        Cipher Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0084)
        Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)
        Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)
        Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027)
        Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023)
        Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)
        Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)
        Cipher Suite: TLS_DH_DSS_WITH_AES_128_GCM_SHA256 (0x00a4)
        Cipher Suite: TLS_DHE_DSS_WITH_AES_128_GCM_SHA256 (0x00a2)
        Cipher Suite: TLS_DH_RSA_WITH_AES_128_GCM_SHA256 (0x00a0)
        Cipher Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e)
        Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (0x0067)
        Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 (0x0040)
        Cipher Suite: TLS_DH_RSA_WITH_AES_128_CBC_SHA256 (0x003f)
        Cipher Suite: TLS_DH_DSS_WITH_AES_128_CBC_SHA256 (0x003e)
        Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
        Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
        Cipher Suite: TLS_DH_RSA_WITH_AES_128_CBC_SHA (0x0031)
        Cipher Suite: TLS_DH_DSS_WITH_AES_128_CBC_SHA (0x0030)
        Cipher Suite: TLS_DHE_RSA_WITH_SEED_CBC_SHA (0x009a)
        Cipher Suite: TLS_DHE_DSS_WITH_SEED_CBC_SHA (0x0099)
        Cipher Suite: TLS_DH_RSA_WITH_SEED_CBC_SHA (0x0098)
        Cipher Suite: TLS_DH_DSS_WITH_SEED_CBC_SHA (0x0097)
        Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0045)
        Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA (0x0044)
        Cipher Suite: TLS_DH_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0043)
        Cipher Suite: TLS_DH_DSS_WITH_CAMELLIA_128_CBC_SHA (0x0042)
        Cipher Suite: TLS_ECDH_anon_WITH_AES_128_CBC_SHA (0xc018)
        Cipher Suite: TLS_DH_anon_WITH_AES_128_GCM_SHA256 (0x00a6)
        Cipher Suite: TLS_DH_anon_WITH_AES_128_CBC_SHA256 (0x006c)
        Cipher Suite: TLS_DH_anon_WITH_AES_128_CBC_SHA (0x0034)
        Cipher Suite: TLS_DH_anon_WITH_SEED_CBC_SHA (0x009b)
        Cipher Suite: TLS_DH_anon_WITH_CAMELLIA_128_CBC_SHA (0x0046)
        Cipher Suite: TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256 (0xc031)
        Cipher Suite: TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02d)
        Cipher Suite: TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256 (0xc029)
        Cipher Suite: TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 (0xc025)
        Cipher Suite: TLS_ECDH_RSA_WITH_AES_128_CBC_SHA (0xc00e)
        Cipher Suite: TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA (0xc004)
        Cipher Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c)
        Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c)
        Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
        Cipher Suite: TLS_RSA_WITH_SEED_CBC_SHA (0x0096)
        Cipher Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0041)
        Cipher Suite: TLS_RSA_WITH_IDEA_CBC_SHA (0x0007)
        Cipher Suite: TLS_ECDHE_RSA_WITH_RC4_128_SHA (0xc011)
        Cipher Suite: TLS_ECDHE_ECDSA_WITH_RC4_128_SHA (0xc007)
        Cipher Suite: TLS_ECDH_anon_WITH_RC4_128_SHA (0xc016)
        Cipher Suite: TLS_DH_anon_WITH_RC4_128_MD5 (0x0018)
        Cipher Suite: TLS_ECDH_RSA_WITH_RC4_128_SHA (0xc00c)
        Cipher Suite: TLS_ECDH_ECDSA_WITH_RC4_128_SHA (0xc002)
        Cipher Suite: TLS_RSA_WITH_RC4_128_SHA (0x0005)
        Cipher Suite: TLS_RSA_WITH_RC4_128_MD5 (0x0004)
        Cipher Suite: TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA (0xc012)
        Cipher Suite: TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA (0xc008)
        Cipher Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016)
        Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013)
        Cipher Suite: TLS_DH_RSA_WITH_3DES_EDE_CBC_SHA (0x0010)
        Cipher Suite: TLS_DH_DSS_WITH_3DES_EDE_CBC_SHA (0x000d)
        Cipher Suite: TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA (0xc017)
        Cipher Suite: TLS_DH_anon_WITH_3DES_EDE_CBC_SHA (0x001b)
        Cipher Suite: TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA (0xc00d)
        Cipher Suite: TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA (0xc003)
        Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
        Cipher Suite: TLS_DHE_RSA_WITH_DES_CBC_SHA (0x0015)
        Cipher Suite: TLS_DHE_DSS_WITH_DES_CBC_SHA (0x0012)
        Cipher Suite: TLS_DH_RSA_WITH_DES_CBC_SHA (0x000f)
        Cipher Suite: TLS_DH_DSS_WITH_DES_CBC_SHA (0x000c)
        Cipher Suite: TLS_DH_anon_WITH_DES_CBC_SHA (0x001a)
        Cipher Suite: TLS_RSA_WITH_DES_CBC_SHA (0x0009)
        Cipher Suite: TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA (0x0014)
        Cipher Suite: TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA (0x0011)
        Cipher Suite: TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA (0x0019)
        Cipher Suite: TLS_RSA_EXPORT_WITH_DES40_CBC_SHA (0x0008)
        Cipher Suite: TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (0x0006)
        Cipher Suite: TLS_DH_anon_EXPORT_WITH_RC4_40_MD5 (0x0017)
        Cipher Suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5 (0x0003)
        Cipher Suite: TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff)
    Compression Methods Length: 1
    Compression Methods (1 method)
        Compression Method: null (0)
    Extensions Length: 85
    Extension: ec_point_formats (len=4)
        Type: ec_point_formats (11)
        Length: 4
        EC point formats Length: 3
        Elliptic curves point formats (3)
            EC point format: uncompressed (0)
            EC point format: ansiX962_compressed_prime (1)
            EC point format: ansiX962_compressed_char2 (2)
    Extension: supported_groups (len=28)
        Type: supported_groups (10)
        Length: 28
        Supported Groups List Length: 26
        Supported Groups (13 groups)
            Supported Group: secp256r1 (0x0017)
            Supported Group: secp521r1 (0x0019)
            Supported Group: brainpoolP512r1 (0x001c)
            Supported Group: brainpoolP384r1 (0x001b)
            Supported Group: secp384r1 (0x0018)
            Supported Group: brainpoolP256r1 (0x001a)
            Supported Group: secp256k1 (0x0016)
            Supported Group: sect571r1 (0x000e)
            Supported Group: sect571k1 (0x000d)
            Supported Group: sect409k1 (0x000b)
            Supported Group: sect409r1 (0x000c)
            Supported Group: sect283k1 (0x0009)
            Supported Group: sect283r1 (0x000a)
    Extension: session_ticket (len=0)
        Type: session_ticket (35)
        Length: 0
        Data (0 bytes)
    Extension: signature_algorithms (len=32)
        Type: signature_algorithms (13)
        Length: 32
        Signature Hash Algorithms Length: 30
        Signature Hash Algorithms (15 algorithms)
            Signature Algorithm: rsa_pkcs1_sha512 (0x0601)
                Signature Hash Algorithm Hash: SHA512 (6)
                Signature Hash Algorithm Signature: RSA (1)
            Signature Algorithm: SHA512 DSA (0x0602)
                Signature Hash Algorithm Hash: SHA512 (6)
                Signature Hash Algorithm Signature: DSA (2)
            Signature Algorithm: ecdsa_secp521r1_sha512 (0x0603)
                Signature Hash Algorithm Hash: SHA512 (6)
                Signature Hash Algorithm Signature: ECDSA (3)
            Signature Algorithm: rsa_pkcs1_sha384 (0x0501)
                Signature Hash Algorithm Hash: SHA384 (5)
                Signature Hash Algorithm Signature: RSA (1)
            Signature Algorithm: SHA384 DSA (0x0502)
                Signature Hash Algorithm Hash: SHA384 (5)
                Signature Hash Algorithm Signature: DSA (2)
            Signature Algorithm: ecdsa_secp384r1_sha384 (0x0503)
                Signature Hash Algorithm Hash: SHA384 (5)
                Signature Hash Algorithm Signature: ECDSA (3)
            Signature Algorithm: rsa_pkcs1_sha256 (0x0401)
                Signature Hash Algorithm Hash: SHA256 (4)
                Signature Hash Algorithm Signature: RSA (1)
            Signature Algorithm: SHA256 DSA (0x0402)
                Signature Hash Algorithm Hash: SHA256 (4)
                Signature Hash Algorithm Signature: DSA (2)
            Signature Algorithm: ecdsa_secp256r1_sha256 (0x0403)
                Signature Hash Algorithm Hash: SHA256 (4)
                Signature Hash Algorithm Signature: ECDSA (3)
            Signature Algorithm: SHA224 RSA (0x0301)
                Signature Hash Algorithm Hash: SHA224 (3)
                Signature Hash Algorithm Signature: RSA (1)
            Signature Algorithm: SHA224 DSA (0x0302)
                Signature Hash Algorithm Hash: SHA224 (3)
                Signature Hash Algorithm Signature: DSA (2)
            Signature Algorithm: SHA224 ECDSA (0x0303)
                Signature Hash Algorithm Hash: SHA224 (3)
                Signature Hash Algorithm Signature: ECDSA (3)
            Signature Algorithm: rsa_pkcs1_sha1 (0x0201)
                Signature Hash Algorithm Hash: SHA1 (2)
                Signature Hash Algorithm Signature: RSA (1)
            Signature Algorithm: SHA1 DSA (0x0202)
                Signature Hash Algorithm Hash: SHA1 (2)
                Signature Hash Algorithm Signature: DSA (2)
            Signature Algorithm: ecdsa_sha1 (0x0203)
                Signature Hash Algorithm Hash: SHA1 (2)
                Signature Hash Algorithm Signature: ECDSA (3)
    Extension: heartbeat (len=1)
        Type: heartbeat (15)
        Length: 1
        Mode: Peer allowed to send requests (1)

When this problem occurs (that is, SSL_do_handshake () fails) SSL_get_error returns SSL_ERROR_SYSCALL, but ERR_get_error () returns 0. We call these two methods immediately after SSL_do_handshake ().

I appreciate your help as this goes for some time.

Authentication: use of WinSCP to connect the Windows client to the Linux server

I am trying to understand how to configure an SFTP connection between Windows 7 PCs (yes, these PCs will be compatible for part of next year) to a Linux server. I think I finally get it, but it's the place to put things and how to really connect what I'm not following.

I am testing all this in a test lab before these new Linux servers come out. I have generated a couple of keys. I gave the public key to the test server administrator, who placed it in /root/.ssh/authorized_keys (Is this the correct location?) On the Linux server.

I have placed my private key in Users user .ssh keyname.ppk on my Windows PC. Is that correct?

And now I'm trying to write a test batch script that will create a .dat file with my connection command, my PUT and GET commands, and that WinSCP will call to connect to that server and execute those commands. If I can make this work, I will use this same batch code and the WinSCP call in several different scripts that currently use FTP, not SFTP.

What I'm not sure how to do is how to connect. I have the call to my .dat file –

winscp /script=tempsftp.dat

But my current authentication method is to use a username / password combination: here is the first line of the .dat file:

open sftp://username:password@servername -hostkey="ssh-ed25519 xxxxxxxxxxxx"        

… but username / password authentication will not be available to me. So how do I connect only with the key pair? Is there a particular line that I need to write instead? open sftp line to connect?

User journey: Are the customer service agent and the client two different people or different roles?

Are & # 39; People & # 39; and & # 39; Roles & # 39; different in each scenario?

Although I read about roles and characters, I am a little confused on this subject with the context in which I am working.

Scenario: one day Bruce(Client) discovers that his water heater is broken and calls the company XYZ for repair. John(Customer service agent) receives the call and assigns Move(Technician) to install a water heater.

John, Bruce and Bob are these 3 people? Or are 3 different user roles that interact with the XYZ service considered?

What is your standard procedure if your client was hit by malware?

Do you suspend them immediately to avoid further damage? What is your PCOS? … | Read the rest of https://www.webhostingtalk.com/showthread.php?t=1787212&goto=newpost

client – How do I move the location of the blockchain file in Windows?

Go to Settings> Options and click on the Reset Options Button. Note that this will erase all the options shown there, so write down what they are so you can configure your options again later.

In the dialog that appears, click Yes and Bitcoin Core will close. Now go to the Bitcoin data directory and copy everything wherever you want it to be. The data directory in Windows is located at %APPDATA%Bitcoin. Move the contents of the data directory to the location where you want the Bitcoin Core data to be.

Start Bitcoin Core again. You will be asked to choose the data directory. Choose a custom data directory and configure it wherever you moved the data directory. Then set your options again.

Kerberos client authentication for a systemd service

I am running a web server (in this case, air flow) on an Ubuntu 18.04 machine that needs to access a SQL Server database that is in the / AD domain.

Q: How can I use the Kerberos ticket / credentials on the web server when running as a systemd service?

Running from shell:

airflow@airflow:~$ kinit airflow@EXAMPLE.COM
Password for airflow@EXAMPLE.COM:
airflow@airflow:~$ klist -A
Ticket cache: KEYRING:persistent:478604841:478604841
Default principal: airflow@EXAMPLE.COM

Valid starting       Expires              Service principal
11/08/2019 22:34:41  11/09/2019 08:34:41  krbtgt/EXAMPLE.COM@EXAMPLE.COM
        renew until 11/09/2019 08:34:41
airflow@airflow:~$ airflow webserver

Result: the web server successfully connects to SQL Server through Kerberos

Side note: after running the web server as indicated above, klist Show the SQL server SPN:

airflow@airflow:~$ klist
Ticket cache: KEYRING:persistent:478604841:478604841
Default principal: airflow@EXAMPLE.COM

Valid starting       Expires              Service principal
11/08/2019 23:00:22  11/09/2019 09:00:18  MSSQLSvc/dbserver.example.com:1433@EXAMPLE.COM
        renew until 11/15/2019 23:00:14
11/08/2019 23:00:18  11/09/2019 09:00:18  krbtgt/EXAMPLE.COM@EXAMPLE.COM
        renew until 11/15/2019 23:00:14

Kinit then starts the service

airflow@airflow:~$ kinit airflow@EXAMPLE.COM
airflow@airflow:~$ sudo service airflow-webserver start
airflow@airflow:~$ journalctl -u airflow-webserver.service -xe

Departure

Nov 08 18:12:11 airflow airflow(54723):   File "/home/EXAMPLE.COM/airflow/.pyenv/versions/3.7.4/lib/python3.7/site-packages/sqlalchemy/engine/default.py", line 481, in connect
Nov 08 18:12:11 airflow airflow(54723):     return self.dbapi.connect(*cargs, **cparams)
Nov 08 18:12:11 airflow airflow(54723): sqlalchemy.exc.DBAPIError: (pyodbc.Error) ('HY000', '(HY000) (Microsoft)(ODBC Driver 17 for SQL Server)SSPI Provider: No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_478604841) (851968) (SQLDriverConnect)')
Nov 08 18:12:11 airflow airflow(54723): (Background on this error at: http://sqlalche.me/e/dbapi)

/etc/krb5.conf

(libdefaults)
        default_realm = EXAMPLE.COM
        dns_lookup_realm = true
        dns_lookup_kdc = true
        ticket_lifetime = 24h
        renew_lifetime = 7d
        forwardable = true
        ccache_type = 5
        default_ccache_name = KEYRING:persistent:%{uid}
        default_client_keytab_name = /home/%d/%u.keytab
(realms)
        EXAMPLE.COM = {
                kdc = exampledc1.example.com
                kdc = exampledc2.example.com
        }

(domain_realm)
        .example.com = EXAMPLE.COM
        example.com = EXAMPLE.COM

/etc/systemd/system/airflow-webserver.service

(Unit)
Description=Airflow web server daemon
After=network.target

(Service)
EnvironmentFile=/etc/sysconfig/airflow
User=airflow
Group=airflow
Type=simple
ExecStart = /home/EXAMPLE.COM/airflow/.pyenv/versions/3.7.4/bin/airflow webserver
Restart=on-failure
RestartSec=5s

(Install)
WantedBy=multi-user.target

admin – Magento 2: How to add a field in the client group create / edit form in the backend?

I want to add a custom field (Boolean value selection) to the customer group form in the backend.

I created the following add-in for that, Field is added to the form, but it does not reflect the value in the editing form, nor does it save the value for the new group.

yesno = $yesno;
    }

    /**
     * Get form HTML
     *
     * @return string
     */
    public function aroundGetFormHtml (
        MagentoCustomerBlockAdminhtmlGroupEditForm $subject,
        Closure $proceed
    ) {

        $form = $subject->getForm();
        if (is_object($form)) {
            $fieldset = $form->addFieldset('pricegroup', ('legend' => __('Pricegroup')));
            $fieldset->addField(
                'is_pricegroup',
                'select',
                (
                    'name' => 'is_pricegroup',
                    'label' => __('Is Pricegroup'),
                    'id' => 'is_pricegroup',
                    'title' => __('Is Pricegroup'),
                    'values' => $this->yesno->toOptionArray(),
                    'required' => false,
                )
            );

            $subject->setForm($form);
        }

        return $proceed();
    }
}