microsoft security monthly quality rollup

There are two entries in the Event Log for each of the communication cases: - One Schannel info event (code 36867), with the message: 'Creating an SSL Client credential.' - Then an SChannel error event (code 36871), with the message: 'A fatal error occurred while creatingĪn SSL Client credential. SCHANNEL tracing does not give us too many clues. Wireshark traces show that no communication is going through the TCP/IP channel, so it seems to be a problem of the SChannel API. Just the TCP/IP connection that gets created, no data is transmitted, and the connection gets closed almost immediately. Our server trace files and Wireshark network traces show, that the TLS handshaking does not even start, it's The Print Spooler service (runningĪs LOCAL SYSTEM) cannot build a secure TCP/IP channel to a local IP address and port. Security Monthly Quality Rollup for Windows Server 2008 R2 for 圆4-based Systems (KB4467107) Once it is installed, the HTTPS connection cannot be created. The problem start happenning when the following Microsoft hotfix gets installed: 2018-11 Our customers want to disable TLS 1.0 and TLS 1.1, and enable only TLS 1.2 for security reasons (TLS protocols Normally it works fine, the HTTPS connection can be established.

The HTTPS connection is encrypted by using the SCHANNEL API of Microsoft. This componentĬommunicates with our local Windows service using HTTPS connections, using the loopback network adapter. Our product has a component registered its DLL in the Print Spooler service, filtering TCP/IP print events.

Microsoft security monthly quality rollup