Here are some blogs on the topic.
http://wikis.sun.com/display/CryptoPerf/Using+the+UltraSPARC+cryptographic+accelerators
Solaris 10
# /usr/sfw/bin/openssl engine -c -t
# cc -fast*-I /usr/sfw/include -L /usr/sfw/lib -lcrypto* aes_test.c -o
aes_test.out
http://blogs.oracle.com/DanX/entry/spar
All,
Version: 1.1.rc5
Solaris x86 on ZFS
Shared Folder
Bug, renamed a folder with sub folders (Maildir format)
After the rename the subscriptions file is own by the person who
renamed the folders, and access is owner rw only.
Instead it should be the same as dovecot-shared which would genera
working well except for subscriptions file perms being changed,
when the file is updated.
The aim is for ~XX-Shared/ to be listed as just another folder for those who
have access and all of its sub folders.
Thanks
Damon.
On Tue, 2008-05-27 at 00:17 +1000, Damon Atkins wrote:
/ Bug, renamed a
In the old days NFS Shared Path had a static handle (ie a number),
normal based on some number pulled out of the file system/inode.
To fix (well work around) a security issue, for about 10+ years now,
when a NFS server reboots, it generates a new random handle for the NFS
Share. (sever may gen
NFS Security 101 for NFSv2 and v3 (NOT NFSv4 a long time ago I was part
of the discussion group for NFSv4 spec the short comings of v2 and v3
have been fixed)
SRV: Server Exports File System /abc/123 access only to host=xyz.domain.com
XYZ: Client Mount mount's SRV:/abc/123
SRV: "mountd" gets a
Original Message by Edgar
I was part of the discussion group for NFSv4 spec
the short comings of v2 and v3 have been fixed
I'm a bit surprised by this. Which "discussion group"?
The RFC, one for NFSv4.0
NFSD (v2/v3) is stateless other than the information provid
I'm quite aware of all this. What I was asking for were those "security issues"
that you claim to be solved>by randomizing the inode-to-filehandle-relationship on every
server reboot.
I have not really wanted to spell it out.
The following is mainly about NFSv2/v3.
Client requests a File Han
Just keep in mine Signed Emails, the email contents needs to be
present back to the client as it came, so the client says the email has
not been altered.
Some interesting reading on SHA256 checksum
http://blogs.sun.com/bonwick/entry/zfs_dedup
http://blogs.sun.com/darren/entry/improving_zfs_dedup_performance_via
ZFS has support for compression on the file system ( lzjb | gzip |
gzip-N | zle ). gzip eats CPU even at levels as low as 3.
From the zfs man page
The lzjb compression algorithm is optimized for performance while
providing decent data compression. You can specify the gzip level by
using th
10 matches
Mail list logo
