Date: Fri, 21 Apr 2017 19:45:04 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-geom@FreeBSD.org Subject: [Bug 218512] Geli arbitrarily prevents setting passphrases Message-ID: <bug-218512-14739-F3OFhvet1A@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-218512-14739@https.bugs.freebsd.org/bugzilla/> References: <bug-218512-14739@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218512 --- Comment #10 from Frank <fhriley@gmail.com> --- (In reply to Alexander Motin from comment #9) It's not paranoia at all. If you don't specify -i, the iterations are not s= et to -1, they are computed and passed in. When setting passphrases on a set of disks, freenas serializes that process, but what if I wanted to parallelize= it? geli is happily computing iterations on the cpus when another task happens = to come in. One or more of the iterations end up getting computed differently = that what it is currently set to and subsequently causing one or more passphrase changes to fail. This is but one of many scenarios of how this could really happen. Of course, I thought of all this when I made my changes, and I added tests = to test those changes. But I suppose it's the state of software these days to = make the easy fix for the specific use case I care about. This will be my last comment on this as I am not a committer to freebsd, but if I were, I would label the commit as incomplete. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218512-14739-F3OFhvet1A>