Your Freedom - HOMENEWSDOWNLOADSACCOUNTDOCS & FAQFORUMS

 

Latest News

10-09-19

YF back on Google Play

We have been able to resolve the issues with Google and YF is again available on Google Play. You ca...

01-02-19

Bitcoin payments available again

We have been able to fix the Bitcoin payment issue, and you should now be able again to pay with Bit...

22-01-19

New login on web page

We have changed the way you log in to the web site -- just in case you are wondering. The old way wa...

 
Pas connecté.
    26-08-04

  • New Client 20040826-01
    • Fixed broken HTTP connection code that made connection via proxies requiring authentication fail.
    • Introduced re-keying. Server and client will now negotiate new encryption keys every 5 minutes. Intercepting them is no good if you don't have the password, and the password is never sent in the clear. This does now raise the safety level of the "HTTPS" connection method roughly to that of wireless LAN with LEAP or PEAP, and way beyond normal WEP. (HTTP payload encryption will come soon.)
    • Added French language file (thanks Philippe Guntz!).
    • Better proxy debugging (HTTPS only).
    • Fixed potential race condition that could lead to some streams just not opening properly. "Dropping frame for non-existing connection" should no longer appear when a stream is refused because the server could not open the connection to the remote end.
    • Fixed formatting of connection configuration panel.
    • Rewrote the stream sendq code to reduce resource consumption.
    • Fixed a problem in HTTP connection code that could cause problems with the downlink connection, depending on configuration.
    • Update status panel when connection closes.
    • Make connection statistics propagation to graphical front-end less resource intensive.
    • Use less threads in stream code to save on memory usage.
    • Tuned some pooling parameters.
    • Removed silly "SEND UDP TO SERVER" message that could occur on busy clients -- it wasn't even telling the truth, the message was not thread-safe.
    • Other minor optimizations in the HTTP connection code.

 
   Acceptable Use  | Data Protection Statement