search for: crytograph

...gt;> I have to different proposals, and wanted to gauge which would be preferred: > > >> 1. Use xxhash instead. > I'd lean towards this option as we already have a copy of xxHash in lib/Support (llvm/Support/xxhash.h). We use it for computing the --build-id in lld as fast/non-crytographic hash variant and has proven to outperform other candidates (e.g. CityHash). Vedant, what do you mean with unsupported? -- Davide "There are no solved problems; there are only problems that are more or less solved" -- Henri Poincare

Hi, Does FASTIPSec in FreeBSD use OCF framework ? Where can I find more documentation ? I wish to run cryptographic algorithms after setting a VPN. What command should I use to run a particular crytographic algorithm (e.g. 3DES etc.) Where can I find all such information ? -- Regards, Bubble

...ms are, including EXTERNAL. It just proxies stuff. If Dovecot claims to support SASL EXTERNAL but does not handle it, that that is a bit of a WTF. It would be tremendous to have true EXTERNAL support all through, i personally really like EXTERNAL, i would rather have some password-protected crytographically secured certificates in my local store, and have client certificates in all the IoT devices, than have to mess around with the OAUTH that the major players press forward, for example. Thanks, and Ciao from Germany, --steffen | |Der Kragenbaer, The moon bear, |der holt sich mu...

Hi again, This is just out of pure curiosity: I came across the documentation of the various random generators in R and saw that the entropy-based kernel random generator available on Linux, Solaris and some other OSes is not by default available. (This generators random values based on the entropy associated with all IO that is handled by the kernel -- this includes TCP/IP packets.) There

...f a WTF. </div> <div> </div> <div> It would be tremendous to have true EXTERNAL support all through, </div> <div> i personally really like EXTERNAL, i would rather have some </div> <div> password-protected crytographically secured certificates in my </div> <div> local store, and have client certificates in all the IoT devices, </div> <div> than have to mess around with the OAUTH that the major players </div> <div> press forward, for example....

I've been working on improving the startup performance of lldb, and ran into an issue with llvm::HashString. It works a character at a time, which creates a long dependency chain in the processor. On the other hand, the function is very short, which probably works well for short identifiers. I don't know how the mix of identifier length seen by lldb compares with that seen by

Now that v2.0.0 is only waiting for people to report bugs (and me to figure out how to fix them), I've finally had time to start doing what I actually came here (Portugal Telecom/SAPO) to do. :) The idea is to have dbox and mdbox support saving attachments (or MIME parts in general) to separate files, which with some magic gives a possibility to do single instance attachment storage. Comments