CipherShed Forum

This is really a humble suggestion of what environment to target first. If it is naive or ignorant, just briefly state to that effect and I will shut up.

It occurs to me that it might be most expeditious in the first release to target only what I call "posix" - i.e., linux + BSD & similar - this also gives you OSX-command-line and maybe Windows-plus-Cygwin-command-line. Maybe also limit it to file-container-only including hidden volume within that container.

My thinking is that pinning down the toolchain(s) for the initial targets might be more straightforward this way. By using autotools + maybe gcc (or clang), it seems to be that you could rapidly come to a non controversial solution.

It's completely beside the point that I personally couldn't give a fork about Windows ever. I swear it is

It could easily be that the prospect is just too disgusting to too many people, and that it is felt it would give a bad impression of the project from the beginning, or that it really wouldn't save enough time-to-initial-release to be significant in the grand scheme of things.

fnj wrote:It's completely beside the point that I personally couldn't give a fork about Windows ever. I swear it is
.

TrueCrypt was originally conceived and designed as a windows solution. It would be product suicide to drop support.

TrueCrypt was originally conceived and designed as a windows solution. It would be product suicide to drop support.

+1 Furthermore, while many (most?) devs might be Unix-based OS people, most end-users and organisations run on Windows. If we want to make our software accessible to the most people, Windows should probably be the primary target.

Personally, I don't waste my time on OS specific projects anymore. I probably care more about Gnu/Linux than any other platform, but I'm not going to make the mistake of spending a ton of my efforts on Linux-only solutions anymore. It has to be Linux, Windows, Mac (gag!), and hopefully even Android. iOS can go suck an egg until they can comply with GPL3