<div dir="auto"><div>Thanks Michal...</div><div dir="auto"><br></div><div dir="auto">Thus the _only_ way to deliver the data reliably through stunnel is some application-level integrity protocol?</div><div dir="auto">I believed that many people use stunnel for wide variety of applications and so they should succeed in workarounding this trouble. Maybe I am missing something about the well-known good practice of stunnel usage?..</div><div dir="auto"><br></div><div dir="auto">Michael<br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Thu, May 28, 2020, 10:14 Michał Trojnara <<a href="mailto:Michal.Trojnara@stunnel.org">Michal.Trojnara@stunnel.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div>
    <p>Hi Michael,</p>
    <p>No, there is no portable way of implementing this feature.  In
      fact, the OS kernel only notifies server applications (including
      stunnel) about a new incoming connection *after* the three-way TCP
      handshake has completed.<br>
    </p>
    <p>Some more details:<br>
<a href="https://groups.google.com/forum/#!topic/comp.protocols.tcp-ip/vk7uY5dkdpY" target="_blank" rel="noreferrer">https://groups.google.com/forum/#!topic/comp.protocols.tcp-ip/vk7uY5dkdpY</a></p>
    <p>Best regards,<br>
          Mike<br>
    </p>
    <div>On 5/28/2020 2:04 AM, Michael S.
      Chusovitin wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="auto">Dear stunnel users,
        <div dir="auto"><br>
        </div>
        <div dir="auto">please advise how to solve the following:</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">- an Application connects to stunnel-client
          (installed at the same machine);</div>
        <div dir="auto">- stunnel-client tries to connect to
          stunnel-server (remote), fails and sends RST to the App;</div>
        <div dir="auto">- but the App has already sent some datagrams to
          stunnel-client during TIMEOUTconnect period and they aren't
          transferred to stunnel-server.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Is there any way to make stunnel-client delay
          its ACK to the App until the connection to stunnel-server is
          established?</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Thanks!</div>
        <div dir="auto"><br>
        </div>
      </div>
      <br>
      <fieldset></fieldset>
      <pre>_______________________________________________
stunnel-users mailing list
<a href="mailto:stunnel-users@stunnel.org" target="_blank" rel="noreferrer">stunnel-users@stunnel.org</a>
<a href="https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users" target="_blank" rel="noreferrer">https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users</a>
</pre>
    </blockquote>
  </div>

_______________________________________________<br>
stunnel-users mailing list<br>
<a href="mailto:stunnel-users@stunnel.org" target="_blank" rel="noreferrer">stunnel-users@stunnel.org</a><br>
<a href="https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users" rel="noreferrer noreferrer" target="_blank">https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users</a><br>
</blockquote></div></div></div>