search for: aes_instruction_set

...rformance improvement? Just upgrade Samba to some version patched with Metze stuffs or is there also some drivers to be compiled and loaded into Kernel? The hardware seems to be included directly in CPU: https://en.wikipedia.org/wiki/Cryptographic_accelerator gave me: https://en.wikipedia.org/wiki/AES_instruction_set Then looking for my own desktop CPU I found that page from Intel where there is a line for "Intel® AES New Instructions" near the bottom: http://ark.intel.com/products/63697/Intel-Core-i7-3930K-Processor-12M-Cache-up-to-3_80-GHz Cheers, mathias > > Volker > > -- > SerN...

Howdy, <this messages is cross posted in freebsd-security and freebsd-net> I'm seeking current cryptographic coprocessors supported in FreeBSD 8.x. By perusing through the crypto-dev (and subsequently referenced) man page(s) I found this list: Hifn 7751/7951/7811/7955/7956 crypto accelerator SafeNet 1141/1741 Bluesteel 5501/5601 Broadcom

hello tincers, when I on battery on my notebook, running powertop, I get nic:<tinc-net-name> as the most power consuption resource in my notebook just after the screen. This happens no matter if I have traffic or not. I am not really sure that if this is really a tinc fault or a tap/tun implementation that never sleeps. any advice? -------------- next part -------------- An HTML

...some drivers to be compiled and loaded into Kernel? I believe Metze's patches require OpenSSL, but he needs to comment on that. > The hardware seems to be included directly in CPU: > https://en.wikipedia.org/wiki/Cryptographic_accelerator > gave me: > https://en.wikipedia.org/wiki/AES_instruction_set Yep. Samba does not use that directly but utilizes some crypto library. Given that there's dozens of "standard" crypto libraries out there with varying algorithm/hardware/nameit support, it's a bit difficult to implement for general use.... https://xkcd.com/927/ Volker -- SerN...

...ogram, Anaconda, uses by default XTS mode (aes-xts-plain64) snap... I also found a notion in the forums that maybe only aes-cbc is using aes-ni [3] and that could mean that after a install aes-ni is not used at all. Does anyone know about this or has experiences? [1] http://en.wikipedia.org/wiki/AES_instruction_set [2] https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption.html [3] http://forum.centos.org/modules/newbb/viewtopic.php?topic_id=38226&forum=56&post_id=166657#forumpost166657 -- Kind Regards, Markus Falb ---...

From RHEL docs: "The default implementation of LUKS in Red Hat Enterprise Linux is AES 128 with a SHA256 hashing. Ciphers that are available are: AES - Advanced Encryption Standard - FIPS PUB 197 Twofish (A 128-bit Block Cipher) Serpent cast5 - RFC 2144 cast6 - RFC 2612" My question is: What will be the performance impact on my Celeron 1.73 GHz CPU and/or hdd

I disabled client signing from the client side, via OS X's global nsmb.conf file: https://discussions.apple.com/message/30282470#30282470 The performance was back to over 600 MB/s, as compared to 60 MB/s with signing. It just seems a bit weird to me that Apple, in response to the Badlock bug, would have changed the OS X client default to something with such drastic performance implications,