<br><div class="gmail_quote">On Fri, Jun 4, 2010 at 5:44 PM, Niels Horn <span dir="ltr"><<a href="mailto:niels.horn@gmail.com">niels.horn@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div class="h5"><br>
</div></div>Heinz,<br>
<br>
I agree that upstream should fix this, but reading the posts from both<br>
sides it might take a while before one of them gives in and admits<br>
that they should act. :)<br>
<br>
My "solution" (OK, it's more of a hack...) was suggested thinking of<br>
situations where people _need_ to get EncFS running on 13.1 to access<br>
data etc...<br>
Not a solution for the SlackBuild, definitely!<br>
<div><div></div><div class="h5"><br>
Niels<br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
<a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
<br>
</div></div></blockquote></div><br>This is exactly why I wrote to the list. I didn't realize until after upgrading to 13.1 that I wouldn't be able to access my encrypted files. (And those files are pretty important to me...which is why they were encrypted in the first place.) I still have Slackware 13.0 in a VM that I can use to decrypt the folders, but that's really cumbersome and I was hoping someone might know an easier and more permanent solution. <br>