[Libssh] Enhancements proposals

[Aris Adamantiadis]

Hello everybody

I am very sorry for being nonresponsive these last months. I had work, 
then holydays, then work, then studies, then procrastination that made I 
didn't take time to maintain libssh or even responding mails.
I realize this was a very bad thing for every libssh users because they 
would be thinking (at reason) they were in a sinking boat.
I still have plans for libssh. I began working on a C++ version, with a 
good OOP design that would make possible the kind of stuff Rodolphe 
Rocca explained (even if I haven't think about that functionnality 
before). The work stalled at this point, and I didn't want to add 
functionnalities to the 0.2 code since they were going to be rewritten.

More information about the C++ version: it would be the version 0.3.
I'd keep a small C stub layer to keep compatibility with C apps and 
previous work using libssh 0.2. So the C version as it is would 
deprecate (even if I'm certainly going to reuse most of the 10.000 lines 
already written).

Thus, I think a good action I have to make to repair my lack of 
attention is to install a correct bug manager (I think about mantis). 
That way, every bug report and feature request would be kept somewhere. 
Also, I promise working a day or two this week to address some of the 
known bugs and include the patches.

please excuse my apologies. I feel shameful about what (not) happened.

Aris
Norbert Kiesel a écrit :
> I think that all sounds promising.  However, my biggest problem right
> now is that libssh seems unmaintained.  I sent a couple of patches over
> 3 month ago w/o any reaction, and have not heard from Aris for a long
> time.
> 
> Aris, if you are still reading this mailing list: can you please respond
> and tell us what your plans wrt libssh are?
> 
> </nk>
> 
> On Wed, 2008-02-27 at 19:12 +0100, Rodolphe Rocca wrote:
>> Hello,
>>
>> I've been using libssh quite intensively and I have to say that it works 
>> quite well, especially since release 0.2.
>>
>> However I have a few concerns that I would like to see improved in this 
>> library.
>>
>> 1) It uses too many namespaces. OK, there is no namespace concept in C, 
>> but ideally function names should all start with the same prefix (ssh_ 
>> or libssh_).
>>
>> 2) Encryption and transport layers should be independent :
>> ideally it should be possible to use the encryption layer without having 
>> to use the transport layer, or at least libssh should provide some 
>> transport hooks (send/recv function pointers) that developers may use to 
>> set their own transport functions instead of the ones provided by libssh.
>>
>> 3) ssh_disconnect should not delete the SSH_SESSION : it mixes memory 
>> management with a connection management which is bad. It just makes 
>> memory management hard for developers. ssh_disconnect should only free 
>> SSH_SESSION local data that cannot be reused (like encryption data), but 
>> options especially should remain attached to the SSH_SESSION, in such a 
>> way that it should be possible to chain ssh_disconnect and ssh_connect 
>> on the same SSH_SESSION.
>>
>> 4) I would to see ssh_cleanup renamed to ssh_free but it's just comsmetics
>>
>> Please tell what you think about that.
>>
>> Regards,
>>
>> Rodolphe
>>
>> _______________________________________________
>> Libssh mailing list
>> Libssh at cerkinfo.be
>> http://www.cerkinfo.be/cgi-bin/mailman/listinfo/libssh
>>
> 
> 
> _______________________________________________
> Libssh mailing list
> Libssh at cerkinfo.be
> http://www.cerkinfo.be/cgi-bin/mailman/listinfo/libssh