Date: Fri, 01 Sep 2017 15:15:27 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 184013] [fusefs] truecrypt broken (probably fusefs issue) Message-ID: <bug-184013-3630-huJDwH6g4F@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-184013-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-184013-3630@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=3D184013 --- Comment #5 from jonathan derose <kb3ngb@gmail.com> --- i know it has been a while since i posted anything here, but give up was the last thing i did.. since then i've actually forked the code, and also moved, i have a working portfile for 11 i will put back here when i get my workstation power conne= cted later this week. the problem was with UFS; i forget what the exact thing was, as i looked at that long ago, but it wasn't going to be resolved easily and so i chose to focus on finding a common format that would work reasonably across macos, l= inux and FreeBSD. although my effort primarily targets working on FreeBSD, i also have maintained support for the other two. In the process, I completely rew= rote the file system detection/arbitration code used for FreeBSD to use a little magic now. th it's not simply the dumb version they had included; we try a little harder now...in fact the freebsd code for this task was little more = than a stub to be finished later...anyhow my solution was to change the default filesystem to the ext3fs provided by the kernel which works wonderfully, and i've also patched OSXfuse to work with it, and made it the default there, a= nd in the linux version. alper akcan was kind enough to accept my changes to osxfuse and pull them back in to his distribution. i've looked in to adding support for ZFS and i think it is very possible although it will take me so= me time and i'm rather swamped right now, i have a plan of attack, and i plan = on attacking it. for now i have a version up on github, at http://github.com/adouble42/nemesis-current and a more current working copy= on my internal gitweb accessible via tor at http://qpbt3kpraplo7ias.onion/?p=3Dnemesis.git;a=3Dsummary the onion link is probably more current by far than github, it also might require some monkeying around as it's what my current effort is. i've had to change the name of the project and strengthened some things such as the KDF, although i can easily change it to read existing containers with the old KDF iterations for the fellow from several years back, should he still have this issue. linux would have been using ext3 anyway so that would work just fine. the portfile pulls a known stable revision from my git and i plan on submit= ting it for review shortly. it is my intention to continue to maintain the fork,= at the time i answered this, had no idea i'd be going that far...should anyone see this that is or knows the right person to talk to regarding contributin= g a port please do reach out thanks tl;dr UFS is hopelessly broken or pointlessly at least as it is here; it's = an easier effort to rewrite core_freebsd to use zfs and ext3. my forks changes= in that respect should backport to the original as drop in; will attempt altho= ugh i do suggest giving the fork a chance. it was a lot of work to get this ba= ck on track and honestly moving forward seems the best idea given the amount of effort involved it seems slightly crazy not to improve the rest in order to= at least mitigate the effects of Moore's law. that's not to say compatibility = with existing data be damned , of course... http://github.com/adouble42/nemesis-current or http://qpbt3kpraplo7ias.onion/?p=3Dnemesis.git;a=3Dsummary onion more current portfile to follow --=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-184013-3630-huJDwH6g4F>