similar to: ssh-keygen(1) misinfo: English prose entropy 0.6 - 1.3 b/char!

>Trolling is such fun, isn't it? I was trying to making merriment, not to provoke emotional responses. I am conflicted on publicly responding, but decided to clarify just in case your confusion is shared by others with better impulse control. Unfortunately, an unchallenged statement made in the company or under the scrutiny of experts is often assumed true, which is really the original

The pursuit projection packages ppr is an excellent contribution to R. It is great for one-to-three ridge fits, often somewhat intuitive, and for multi-ridge fits, where it at least describes a lot of variance. Like many folk, I need to report the fits obtained from ppr to the greater, outside, non-R world. It is fairly obvious how to use the terms alpha and beta to report on

You want multiple IP Addresses for email if you are hosting more than one domain. The reason is, everyone now checks for reverse DNS with email so you need a different public IP Address for each email domain. This way, all the reverse DNS translations will be unique. For apache, you can have multiple websites sharing the same IP Address as long as you don''t do anything with SSL. SSL

Does anyone know why the weblog at http://weblog.rubyonrails.org/ is often messed up, with the first or first and second topics left-shifted and melded with the Rails logo, the Live Search box and the page''s menu? This happens on all my boxes that run Internet Explorer 6 (IE6). I checked it on Firefox and the page appears correctly. While it''s easy to argue "just use

On Wed, 29 Mar 2023, Chris Rapier wrote: > I was wondering if there was something specific to the internal chacha20 > cipher as opposed to OpenSSL implementation. > > I can't just change the block size because it breaks compatibility. I can do > something like as a hack (though it would probably be better to do it with the > compat function): > > if

I'm hardly an expert on this, but if I remember correctly, the rekey rate for good security is mostly dependent on the cipher block size. I left my reference books at home; so, I can't come up with a reference for you, but I would take Chris' "I'm deeply unsure of what impact that would have on the security of the cipher" comment seriously and switch to a cipher with a

> If you encrypt something twice with different keys,you can decrypt it with > both keys - but mathematically, there is another > key of a similar length that can decrypt that message equally well. The probability that the result is strong is increased (consider the case where 1/1000 keys is weak). Also, if you do a bit more work, you can come up with something like 3des. [mod: Now

That's true for block ciphers, but ChaCha20+poly1305 is a stream cipher. On Wed, 29 Mar 2023, Robinson, Herbie wrote: > > I?m hardly an expert on this, but if I remember correctly, the rekey rate > for good security is mostly dependent on the cipher block size.? I left my > reference books at home; so, I can?t come up with a reference for you, but I > would take Chris?

I was wondering if there was something specific to the internal chacha20 cipher as opposed to OpenSSL implementation. I can't just change the block size because it breaks compatibility. I can do something like as a hack (though it would probably be better to do it with the compat function): if (strstr(enc->name, "chacha")) *max_blocks = (u_int64_t)1 << (16*2);

Ah, with an internal block size [Is that what one calls it?] of 64 bytes. From: Damien Miller <djm at mindrot.org> Sent: Wednesday, March 29, 2023 3:08 PM To: Robinson, Herbie <Herbie.Robinson at stratus.com> Cc: Chris Rapier <rapier at psc.edu>; Christian Weisgerber <naddy at mips.inka.de>; openssh-unix-dev at mindrot.org Subject: RE: [EXTERNAL] Re: ChaCha20 Rekey

Hi, I was discussing the common practice of disk eradication used by many firms for security. I was thinking this may be a useful feature of ZFS to have an option to eradicate data as its removed, meaning after the last reference/snapshot is done and a block is freed, then write the eradication patterns back to the removed blocks. By any chance, has this been discussed or considered before?

For the encryption functionality in the ZFS filesystem we use AES in CCM or GCM mode at the block level to provide confidentiality and authentication. There is also a SHA256 checksum per block (of the ciphertext) that forms a Merkle tree of all the blocks in the pool. Note that I have to store the full IV in the block. A block here is a ZFS block which is any power of two from 512 bytes to

(Sorry, third time -- last one, promise, just giving it a subject line!) OK, a second machine hosted at the same hosting company has also apparently been hacked. Since 2 of out of 3 machines hosted at that company have now been hacked, but this hasn't happened to any of the other 37 dedicated servers that I've got hosted at other hosting companies (also CentOS, same version or almost),