search for: padlock

Hi! I try to load an module that it is found in curent /lib/modules/`uname -r` tree ... root at sevcenco: ~ # ls -l /lib/modules/`uname -r`/kernel/drivers/crypto/padlock-* -rwxr--r-- 1 root root 14296 Mar 16 19:37 /lib/modules/2.6.38-0.el5.elrepo/kernel/drivers/crypto/padlock-aes.ko -rwxr--r-- 1 root root 10808 Mar 16 19:37 /lib/modules/2.6.38-0.el5.elrepo/kernel/drivers/crypto/padlock-sha.ko but if i try : root at sevcenco: ~ # modprobe -v padlock-aes.ko FATAL:...

I was wondering if someone with more familiarity with MC on X86 could consider looking into adding support for the hyphenated versions of the VIA Padlock instructions? If anyone is up for it there are details within these two bug reports.. http://www.llvm.org/bugs/show_bug.cgi?id=8556 http://www.llvm.org/bugs/show_bug.cgi?id=10266 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

...ed 69MB/s 3) openssl tests have even better results 4) openssh can transfer AES256 encrypted information at < 27MB/s (and worse with HDD encryption) It is better with openssh 5.x, than 4.6, but still I see no reason why results are so bad... Please, could someone explain? I don't believe, padlock is used properly... Jan

On Jan 16, 2013, at 10:07 AM, Brad Smith <brad at comstyle.com> wrote: > I was wondering if someone with more familiarity with MC > on X86 could consider looking into adding support for > the hyphenated versions of the VIA Padlock instructions? Take a look at llvm/lib/Target/X86InstrSystem.td perhaps. -- Stephen Checkoway

Hi all, There is a feature very common in PBX called PADLOCK , and I'd like to set up it on Asterisk 1.6. I have seen it in the internet but such scripts never work to me. I am trying to do something like that:Create a password and associate it with the callerid: exten => _*11*xxxx,1,Set(DB(CADASTRA/${CALLERID(num)})=${EXTEN:4}) Create a flag in orde...

I have a zpool that consists for a two-drive mirror. The two times I took the zpool offline, I had to resilver one of the drives (the same drive both times) when I imported it back. All drives in the pool show no read, write, or checksum errors and are new, so I'm looking to a software problem before hardware. Both drives are encrypted geli devices. I tried to reproduce the error with 1GB

...500, Stephen Checkoway wrote: > > On Jan 16, 2013, at 10:07 AM, Brad Smith <brad at comstyle.com> wrote: > > > I was wondering if someone with more familiarity with MC > > on X86 could consider looking into adding support for > > the hyphenated versions of the VIA Padlock instructions? > > > Take a look at llvm/lib/Target/X86InstrSystem.td perhaps. I had already found that, but I wouldn't be asking if it was that straightforward. I thought I would try something like the following.. Index: lib/Target/X86/X86InstrSystem.td ===========================...

...and connecting with ssh to an rsync server. I can connect just fine and the files go with no problem. I'm going from a RedHat 7.3 with rsync version 2.4.6 protocol version 24 to a RedHat 7.3 rsync version 2.5.4 protocol version 26 This is the command I am running from the client server (padlock is the rsync server): rsync -vvaz -e ssh /usr/local/cvsroot/ padlock:"/usr/local/cvsroot" Should I get rsync logs on padlock? A 'yes' or 'no' will do. If it's 'yes' then it's something dumb on my end and I will do some more digging. Oh, yes, I have RTFM...

...to load specific OpenSSL engines. Furthermore in the future OpenSSL is said to be supoorting a "default engine", so that applications will not need to specify them themselves. What I'm trying to say, I'm not at all sure if this patch I sent was the way to go, I simply wanted my Padlock support to work :) -- Andreas [ http://unstable.nl | xmpp:andreas@unstable.nl ] [ callto:ils.seconix.com/andreas@unstable.nl ] -------------- next part -------------- A non-text attachment was scrubbed... Name: niet beschikbaar Type: application/pgp-signat...

I got roughly the same performance results when I use the openssl speed test with and without a hifn 7956 cryto card Here's what I did: After the card is plugged in, kldload hifn; kldload cryptodev; I got the message: hifn0 mem 0xfc8f0000-0xfc8f7ffff, 0xfc8f0000-0xfc8f7ffff, 0xfc8f0000-0xfc8f7ffff irg 28 at device 3.0 on pci1 hifn0: Hifn 7956, rev 0, 32KB dram, pll=0x800<pci clk, 4x

In a virtualized environment running Xen or VMware, can the guest operating systems utilize hardware crypto acceleration such as the "PadLock" AES acceleration built into VIA CPUs? (Wasn't able to find this info in any of ~400 Google hits, so I'm shooting it out a bit to let as many as possible benefit from the answer.)

In a virtualized environment running Xen or VMware, can the guest operating systems utilize hardware crypto acceleration such as the "PadLock" AES acceleration built into VIA CPUs? (Wasn't able to find this info in any of ~400 Google hits, so I'm shooting it out a bit to let as many as possible benefit from the answer.)

In a virtualized environment running Xen or VMware, can the guest operating systems utilize hardware crypto acceleration such as the "PadLock" AES acceleration built into VIA CPUs? (Wasn't able to find this info in any of ~400 Google hits, so I'm shooting it out a bit to let as many as possible benefit from the answer.)

...er. > I can connect just fine and the files go with no problem. > > I'm going from a > RedHat 7.3 with rsync version 2.4.6 protocol version 24 > to a > RedHat 7.3 rsync version 2.5.4 protocol version 26 > > This is the command I am running from the client server (padlock is the > rsync server): > > rsync -vvaz -e ssh /usr/local/cvsroot/ padlock:"/usr/local/cvsroot" > > Should I get rsync logs on padlock? > > A 'yes' or 'no' will do. If it's 'yes' then it's something dumb on my end > and I will do...

...n requirements are: >> >> - The interface should be very easy to use. Linux, at least, will >> want to use it extremely early in boot as part of kernel ASLR. This >> means that PCI and ACPI will not work. > > How do non-virtual systems get entropy this early? RDRAND/Padlock? Truerand? > Could hypervisors and simulators simply make sure these work? > If RDRAND is available, then Linux, at least, will use it. The rest are too complicated for early use. Linux on x86 plays some vaguely clever games with rdtsc and poking at the i8254 port. I think that these tric...

...n requirements are: >> >> - The interface should be very easy to use. Linux, at least, will >> want to use it extremely early in boot as part of kernel ASLR. This >> means that PCI and ACPI will not work. > > How do non-virtual systems get entropy this early? RDRAND/Padlock? Truerand? > Could hypervisors and simulators simply make sure these work? > If RDRAND is available, then Linux, at least, will use it. The rest are too complicated for early use. Linux on x86 plays some vaguely clever games with rdtsc and poking at the i8254 port. I think that these tric...

...ficant speed improvement. OTOH if no crypto engine is available, nothing bad happens and default software crypto routines are used. This patch is used in SUSE Linux OpenSSH package and proved to work (at least it didn't break anything) both with and without crypto engines. Tested also with VIA PadLock crypto engine (patches for OpenSSL are at http://www.logix.cz/michal/devel/padlock/ ) Would you consider including it in the official OpenSSH release? Thanks! Michal Ludvig -- SUSE Labs mludvig at suse.cz (+420) 296.545.396 http://www.suse.cz Personal homepage http://w...

...port 139 machine mocha rejected the password change: Error was : User has insufficient privilege. Failed to change password for johnr The password is correct and the accounts on NT are set up to allow password changing. On the NT machine in the Event Security Log an event with an icon of a little padlock appears with the USER field of ANONYMOUS! I have straced the system calls and I can see the string "johnr" inside a packet being sent to "mocha". This used to work some time ago. It also happens on a machine running 2.0.7. I have searched for this problem and discovered it ha...

...n.pem and privkey.pem is what I should be using ? anythought how to force an iphone to reload cert ? actual cert was renewed 15/7, old/previous one expired earlier today ls /etc/letsencrypt/live/fqn.myserver/ cert.pem chain.pem fullchain.pem privkey.pem (if I open mailserver host in browser, padlock shows current/valid cert) -- Voytek

SuSE tries to feed me Wine V20050211 as a security fix for the recent WMF vulnerability. OTOH, WneHQ says that this is fixed in V0.9.6. Can anyone tell me how to specify to "YOU" (YaST Online Updater) that I most certainly don't want that 20050211 version? Not now -- not ever! I am now using V0.9.7. If I permit "YOU" to perform automatic updates I get clobbered by this