policy and pylib/packet cmac/160 bit hmac support

[Mark Atwood]

We don't have a policy against 3p Python modules.
On the other hand, I'm not a fan of importing the entire cheese shop.
On the other other hand, I usually pull in the gpsd Python module on machines I'm running ntpd on.
On the other other other hand, can we have a Python binding on the C crypto routines that ntpd uses?


..𐑥𐑸𐑒
Mark Atwood <mark.atwood at ntpsec.org>
Project Manager of the NTPsec Project
+1-206-604-2198


On Thu, Oct 31, 2019, at 13:00, James Browning via devel wrote:
> After looking at devel/HACKING, I do not see a policy on including
> external python modules.
> 
> The came up because I have a merge request (!1044), which adds support
> for RIPEMD160, SHA-1, and AES128CMAC. The CMAC implementation currently
> requires the pycryptodome[1] module.
> 
> If external modules are not allowed, then eventually someone will need
> to implement a substitute.
> 
> [1] https://pycryptodome.readthedocs.io/
> _______________________________________________
> devel mailing list
> devel at ntpsec.org
> http://lists.ntpsec.org/mailman/listinfo/devel
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20191123/91a9169d/attachment.htm>