[ciphershed] Re: Reviewed some of the code
- From: Stephen R Guglielmo <srguglielmo@xxxxxxxxx>
- To: ciphershed@xxxxxxxxxxxxx
- Date: Thu, 26 Jun 2014 08:54:49 -0400
On Wed, Jun 25, 2014 at 3:22 PM, Bill Cox <waywardgeek@xxxxxxxxx> wrote:
> It looks like we will not be able to avoid the dependency on a
> 1993 version of
> Microsoft Visual C, but I think we can live with it.
Hm, that's annoying. What's the reason you found that we can't avoid
it? There has to be more recent open-source bootloaders that don't
depend on that? Can we look at grub (GPL'ed) or lilo (BSD licensed)?
> I also looked into code that has any E4M copyright.
--- SNIP ---
> Given the link to E4M, I would recommend we remove all of the E4M
> code from the system.
I would tend to agree. I know "development stopped" for a brief period
in the early history of TrueCrypt. Maybe some behind-closed-doors
agreement went down with SecurStar?
> After that, we
> still have a *lot* of code to rewrite due to migrating to a FOSS (preferably
> BSD) license.
> Mostly it's the wxWindows GUI code. Maybe we could do this in two major
> rewrites: first
> eliminate the E4M code and have a major release, and then rewrite the rest.
> There's also
> the issue of how to rewrite some of the crypto code. There are well
> reviewed BSD
> compatible versions for most of the crypto code we need, I think. As much
> fun as it would
> be, I'm not sure we need to write any actual encryption code.
I've actually already started playing with wxWidgets to design a new
GUI. I have enough time to write a few lines of code per day, but it's
a start, haha.
https://github.com/srguglielmo/CipherShed2
The idea is it could possibly be merged in down the road. If not, it's
just a learning experience for me regarding wxWidgets (which was
unfamiliar with previously).
Other related posts:
