Date: Tue, 26 Apr 2022 15:15:22 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 263586] security/py-pycrypto: not compatible with python 3.8 Message-ID: <bug-263586-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263586 Bug ID: 263586 Summary: security/py-pycrypto: not compatible with python 3.8 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: sunpoet@FreeBSD.org Reporter: amdmi3@FreeBSD.org Assignee: sunpoet@FreeBSD.org Flags: maintainer-feedback?(sunpoet@FreeBSD.org) - pycrypto is no longer maintained (see https://www.pycrypto.org/) - it's also not compatible with python 3.8, for instance it uses time.clock= () (https://github.com/pycrypto/pycrypto/blob/master/lib/Crypto/Random/_UserFr= iendlyRNG.py#L77) not present in python 3.8 (which results in problems such as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263585) So: - The port should be marked DEPRECATED - time.clock() call should be replaced with something compatible, for the t= ime being For instance, this may work: self._clock_es.feed(struct.pack('=3DQ', time.monotonic_ns())) Instead of fractional part of time.clock() converted to 4 bytes, it feeds 8 bytes of monotonic time with nanosecond precision, which should be even more random. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263586-7788>