There are still 5 reports from clang analyzer.
They are either false positives or (in the test code) 'easy-to-read'
programming by purpose (easy to get rid of, but absolutely no need to do).
Tim
From 5e8bd25a38ffb4b72ab85b6c855720bd9e35ec04 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tim Rühsen?=
Da
I fixed some compiler warnings that came up with my standard gcc flags,
nothing serious.
BTW, the code uses some gcc extensions which are not compatible through
compilers and/or systems:
- pointer arithmetic with void *
- function pointer and void * assignments
- gcc variadic macro extensions
FYI
On Wednesday 21 January 2015 21:39:30 Yawning Angel wrote:
> On Wed, 21 Jan 2015 15:26:56 -0500
>
> David Goulet wrote:
> > > +/*
> > > + * Using TCP Fast Open (TFO) uses sendto() instead of connect()
> > > with 'flags'
> > > + * set to MSG_FASTOPEN. Without this code, using TFO simply
> > > bypa
On Wednesday 14 January 2015 09:01:40 David Goulet wrote:
> On 13 Jan (15:25:35), Tim Ruehsen wrote:
> > Hi,
> >
> > I tried to torify my wget-like application
> > (https://github.com/rockdaboot/mget) and after some struggling I found
> > that
> > TFO
Upps, I made a last second failure...
Here is the amended (and working) patch.
Tim
On Wednesday 14 January 2015 14:55:58 Tim Ruehsen wrote:
> Hi,
>
> no answer yet, so I created a first 'works for me' patch to let torified TFO
> aware clients not leak silently.
>
&g
Hi,
no answer yet, so I created a first 'works for me' patch to let torified TFO
aware clients not leak silently.
(I hope I am on the right list here)
Please review and apply|comment.
Tim
On Tuesday 13 January 2015 15:25:35 Tim Ruehsen wrote:
> Hi,
>
> I tried to
Hi,
I tried to torify my wget-like application
(https://github.com/rockdaboot/mget) and after some struggling I found that
TFO is enabled by default (where available).
I guess, the problem is TFO not using connect() but sendto().
Please enlighten me, what I can do (despite turning off TFO).
I
