[Gambas-user] How to offer a new component to gambas?

[vuott at tutanota.com]

>>> I have never developed components in C for gambas

I suggest these links:
- http://www-e.uni-magdeburg.de/tboege/gambas/native_comp.pdf
- https://www.mail-archive.com/gambas-user@lists.sourceforge.net/msg29164.html




1 set 2021, 12:17 da carloskabronsete at gmail.com:

> I totally agree with your point of view.
>
> I am interested in contributing. This contribution does not have to be a component, it can be a farm project as long as gb.openssl does not have the appropriate functionalities.
>
> I can try to develop gb.openssl but I have the problem that I have never developed components in C for gambas and I have never developed in C with the openssl libraries. Both will give me problems and I need some time.
>
> I feel capable of doing it.
>
> Would you like to put those digest, pki, and encryption projects on the gambas farm? How to do that?
>
> Thanks for your time
>
> El mar, 31 ago 2021 a las 22:10, Tobias Boege via User (<> user at lists.gambas-basic.org> >) escribió:
>
>> On Tue, 31 Aug 2021, Carlos Kabronsete wrote:
>>  > - * Create complete PKI structures, Root CA, intermediateCA,
>>  > CrlDistributionPoint, Alternativenames, etc.
>>  > - * Manage X509 certificates. Client & Server certificates, ocsp,
>>  > codesigning, timestamp, S/mime.
>>  > - * Manage Pkcs12 certificates.
>>  > - * Manage private keys RSA, DSA, ECDH, ECDSA, X25519, ED449.
>>  > - * SSL/TLS client test.
>>  > - * Timestamps request, generation and verification.
>>  > =================================================
>>  > The second component is a gambas component that encrypts and decrypts files
>>  > or variables on the fly.
>>  > ==================================================
>>  > There is a third component is a gambas component that manage a complete
>>  > message digest.
>>  
>>  It sounds to me as if all that functionality should be available from
>>  gb.openssl (especially if you use precisely OpenSSL to implement it).
>>  
>>  Now, of course the problem is that gb.openssl is written in C, not in
>>  Gambas, so the barrier for you to contribute to it is higher, and in
>>  its current state gb.openssl does not yet provide even the primitives
>>  which you need to reimplement your components on top of it.
>>  
>>  Still, I think gb.openssl would be the right place for all of it.
>>  Especially because your components currently use Exec on the openssl
>>  binary all the time, when in an ideal world they would access the
>>  openssl library directly.
>>  
>>  It would be really nice to have someone take over development of
>>  gb.openssl. There are so many things missing, as your components
>>  exemplify (although ciphers _are_ implemented). I don't have time
>>  to do it and probably lack the best-practices knowledge in crypto-
>>  graphy anyway.
>>  
>>  Best,
>>  Tobias
>>  
>>  -- 
>>  "There's an old saying: Don't change anything... ever!" -- Mr. Monk
>>  
>>  ----[ >> http://gambaswiki.org/wiki/doc/netiquette>>  ]----
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gambas-basic.org/pipermail/user/attachments/20210901/679ce8b3/attachment.htm>