I'm not sure if this would be enough for you but would an anonymous
remailer or gist service reached via the tor network provide you with
sufficient safety?

Bill.


On Fri, 14 Jan 2022 at 13:29, Red M via libssh2-devel <
libssh2-devel@lists.haxx.se> wrote:

> Re: performance
> In my testing libssh is 20-25% slower than libssh2. I can publish more
> about this figure soon but not only is it slower, it consumes more cycles
> to get the same job done.
>
> Another thing to note is that libssh does not fully implement
> async/nonblocking IO for SCP and SFTP, making it an incomplete API.
>
> Additionally while I'd like to provide patches for such features I am not
> able to sign my commits, as I will not drop my pseudonym simply for someone
> else's benefit.
>
>
> On Thu, 6 Jan 2022, 3:18 am Will Cosgrove via libssh2-devel, <
> libssh2-devel@lists.haxx.se> wrote:
>
>> Yes, we use SecureZeroMemory() and memset_s().
>>
>> Will
>>
>> > On Jan 5, 2022, at 7:05 AM, Andreas Schneider <a...@cryptomilk.org>
>> wrote:
>> >
>> > On Tuesday, January 4, 2022 6:05:05 PM CET Will Cosgrove via
>> libssh2-devel
>> > wrote:
>> >> We do zero some sensitive data, but could be reviewed for completeness.
>> >
>> > I don't know how you exactly zero sensitive data, but be aware that if
>> you do:
>> >
>> > memset()
>> > free()
>> >
>> > The optimizer will optimize away the memset(). You either use
>> explicit_bzero()
>> > or protect the memset() with additional assembler code. There is also
>> > memset_s() or memset_secure() on some platforms.
>> >
>> >
>> >       Andreas
>> >
>> > --
>> > Andreas Schneider                 a...@cryptomilk.org
>> > GPG-ID:     8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D
>> >
>> >
>>
>> --
>> libssh2-devel mailing list
>> libssh2-devel@lists.haxx.se
>> https://lists.haxx.se/listinfo/libssh2-devel
>>
> --
> libssh2-devel mailing list
> libssh2-devel@lists.haxx.se
> https://lists.haxx.se/listinfo/libssh2-devel
>
-- 
libssh2-devel mailing list
libssh2-devel@lists.haxx.se
https://lists.haxx.se/listinfo/libssh2-devel

Reply via email to