I've been working on a project that would be able to do this (one day - hopefully) on Windows, Linux, Solaris, and Mac OS X (Those being the platforms that I have.)
I'm not a crypto whiz and am having serious trouble finding enough information about how filesystems work in order to implement all of the required interfaces. Does anybody know where this information is, or should I look through Linux/BSD sources - and hope that BSD is applicable to OS X?
My current version is pretty much a library that allows you to like apps against it, but doesn't support native operation. The next release will add networking support, but I really need to go native to make it useful to people.
Also, can anybody help decrease the usefulness of the algorithm for decryption so that I can GPL the thing?
You can see what I've done from here.
I haven't been able to get Mozilla to work on Solaris, because I've only got the libstdc++.a file and I need.so. There are hundreds of sets of instructions for unpacking the archive and making a shared library out of it, and I've had a go myself, but there are exports that just don't seem to work properly on execution...
How did you do this, do you have any suggestions? Thanks in advance...
One other thing - M$ and Intel have always been really, really close. This has always been an advantage for both of them. But if M$ follows the WinCE 'other processor support' with more desktop OS support, does this mean that Intel's RedHat investment wasn't just to prevent RedHat distributions on Solaris etc, was there a real commitment to Linux?
And more importantly, is M$ really committed to other architectures - NT has always supported other processors, but M$ won't even compile its own applications for them - let alone anybody else. For one, I can't build an NT app on say, Alpha, without an Alpha PC - something I can't cost-justify.
Increasingly, as Windows and other apps have grown with non-assembler languages, the proportion of the code that's Intel-specific has to be pretty small by now.
I just can't see M$ being serious about more diverse architectures - they haven't been in the past.
Remember, m$ released Windows NT 8 years ago as being a cross-platform OS. Their basic philosophy appears to be that all platforms are supported in all languages (so long as they're running Windows and can't be recompiled to anything else.)
I don't get it. Why port a proprietary, m$ piece of code from one m$ compiler to another? If you wanted to port code, you'd probably want to port it to a ~different~ platform. Try porting it to JDK (This may involve removing several thousand lines of Win32 APIs, but it's worth it.)
Slashdot Mirror
I've been working on a project that would be able to do this (one day - hopefully) on Windows, Linux, Solaris, and Mac OS X (Those being the platforms that I have.)
I'm not a crypto whiz and am having serious trouble finding enough information about how filesystems work in order to implement all of the required interfaces. Does anybody know where this information is, or should I look through Linux/BSD sources - and hope that BSD is applicable to OS X?
My current version is pretty much a library that allows you to like apps against it, but doesn't support native operation. The next release will add networking support, but I really need to go native to make it useful to people.
Also, can anybody help decrease the usefulness of the algorithm for decryption so that I can GPL the thing? You can see what I've done from here.
- Malcolm
I haven't been able to get Mozilla to work on Solaris, because I've only got the libstdc++.a file and I need .so. There are hundreds of sets of instructions for unpacking the archive and making a shared library out of it, and I've had a go myself, but there are exports that just don't seem to work properly on execution...
How did you do this, do you have any suggestions?
Thanks in advance...
One other thing - M$ and Intel have always been really, really close. This has always been an advantage for both of them. But if M$ follows the WinCE 'other processor support' with more desktop OS support, does this mean that Intel's RedHat investment wasn't just to prevent RedHat distributions on Solaris etc, was there a real commitment to Linux? And more importantly, is M$ really committed to other architectures - NT has always supported other processors, but M$ won't even compile its own applications for them - let alone anybody else. For one, I can't build an NT app on say, Alpha, without an Alpha PC - something I can't cost-justify. Increasingly, as Windows and other apps have grown with non-assembler languages, the proportion of the code that's Intel-specific has to be pretty small by now. I just can't see M$ being serious about more diverse architectures - they haven't been in the past.
Remember, m$ released Windows NT 8 years ago as being a cross-platform OS. Their basic philosophy appears to be that all platforms are supported in all languages (so long as they're running Windows and can't be recompiled to anything else.)
I don't get it. Why port a proprietary, m$ piece of code from one m$ compiler to another? If you wanted to port code, you'd probably want to port it to a ~different~ platform. Try porting it to JDK (This may involve removing several thousand lines of Win32 APIs, but it's worth it.)