@xnox
In my case, this is on a TI AM3352 processor. The key config item is:
CONFIG_HW_RANDOM_OMAP=m
TI's docs indicate that the following is important:
CONFIG_CRYPTO_DEV_OMAP_SHAM=y
And these may be related:
CONFIG_CRYPTO_DEV_OMAP_AES=y
CONFIG_CRYPTO_SHA256_ARM=y
CONFIG_CRYPTO_SHA512_ARM=y
I
@teward
No, I'm not sure whether it's an nginx bug.
openssl packages were updated; nginx package is at the same version.
Basically, it looks like an openssl call that previously succeeded (and
probably gave questionable responses) now has become a blocking call
that doesn't return until sufficie
@racb
I'm not sure that I would consider it normal or expected, though, for
system services to suddenly stop working due to regular updates, and for
a server to suddenly become unreachable and unresponsive just because it
was updated.
On the other hand, it's certainly not desirable for a system t
3 matches
Mail list logo
