You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(1) |
Dec
|
2006 |
Jan
|
Feb
|
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: Hans-Ulrich J. <han...@t-...> - 2011-02-14 22:09:16
|
Hello, the stable version 2.1-0 of ScramDisk for Linux has been released. It now supports TrueCrypt 7 containers. Moreover, some bugs have been fixed. Packages for Debian 5.0 and 6.0, Fedora 14, SUSE 11.3 and Ubuntu 10.04, and 10.10 are provided for i386 and AMD64 (or x86_64 respectively) architectures. The kernel version is part of the filename of binary packages and must match the kernel version of the system it is installed on. The architecture i386 or x86_64 in the filename should also match the architecture of the distribution on which it is installed. Best regards Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2009-09-18 20:57:02
|
See my reply to the identical question on sd4l-user list. Niall Murphy wrote: > Hi, > > Maybe you can help me. I'm trying to evaluate what encryption solution would be best for my company's setup. > > We provide a computer that acts as a server for our customers, who have no physical interaction with the machine. > We need the data on this machine to be decrypted as it is needed by a number of services on-the-fly. > As we need to provide automatica authentication we either need to: > > Keep the parts of the filesystem required to boot up and allow an OpenVPN ssh session - permanently decrypted - so that we can remotely authenticate > or > Provide a usb key containing the secret key to our customer and read this key when the machine boots. > > Obviously the latter option involves more risk as someone intending on stealing the machine need only steal its acompanying usb key should the customer not keep it safe. Also, if the power were to go we need a way to automatically authenticate meaning the key would have to be paired with the machine at all times. > > We currently have OpenVPN set up on the machine we want to encrypt so that it keeps contacting us to tell us it is online and it initiates an OpenVPN connection with us when it does go online, so half the work is done in this regard. > > I was just wondering if your product would support custom authentication in this manner? and if you have any further suggestions, either on what files would have to remain decrypted for this to work, or what possible alternatives there may be. > > If you need any further description of the above please let me know. > > > Thanks. |
From: Niall M. <n.m...@ju...> - 2009-09-16 16:18:57
|
Hi, Maybe you can help me. I'm trying to evaluate what encryption solution would be best for my company's setup. We provide a computer that acts as a server for our customers, who have no physical interaction with the machine. We need the data on this machine to be decrypted as it is needed by a number of services on-the-fly. As we need to provide automatica authentication we either need to: Keep the parts of the filesystem required to boot up and allow an OpenVPN ssh session - permanently decrypted - so that we can remotely authenticate or Provide a usb key containing the secret key to our customer and read this key when the machine boots. Obviously the latter option involves more risk as someone intending on stealing the machine need only steal its acompanying usb key should the customer not keep it safe. Also, if the power were to go we need a way to automatically authenticate meaning the key would have to be paired with the machine at all times. We currently have OpenVPN set up on the machine we want to encrypt so that it keeps contacting us to tell us it is online and it initiates an OpenVPN connection with us when it does go online, so half the work is done in this regard. I was just wondering if your product would support custom authentication in this manner? and if you have any further suggestions, either on what files would have to remain decrypted for this to work, or what possible alternatives there may be. If you need any further description of the above please let me know. Thanks. -- Niall |
From: Hans-Ulrich J. <han...@t-...> - 2009-04-23 12:20:10
|
Hello, the stable version 2.0-0 of ScramDisk for Linux has been released. It now supports TrueCrypt 5 and 6 containers. The new features of handling partitioned containers or whole partitioned hard disks and of creating a swap space within a container and using such an encrypted swap space have been added. Moreover, some bugs have been fixed. Packages for CentOS 5.3, Debian 3.1, 4.0 and 5.0, Fedora 10, Mandriva 2009, SUSE 11.0 and 11.1 and Ubuntu 8.04 and 8.10 are provided for i386 and AMD64 architectures. Packages for Ubuntu 9.04 will follow soon. The kernel version is part of the filename of binary packages and must match the kernel version of the system it is installed on. The architecture i386 or x86_64 in the filename should also match the architecture of the distribution on which it is installed. Best regards Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2008-03-30 15:55:50
|
Hello Thomas, Thomas Irlet wrote: > Hello > > first of all, thank you for this nice piece of code. Works really fine, and > you also support the newest kernels. Good! > > What are your plan for the next future? I see two things, that would be of > benefit for this project: > 1. support for the new TrueCrypt formats (XTS, SHA-512, encrypted system > disk) > 2. getting the password from the bootloader to mount the boot partition > > 1. I could help in this point. I do not see special problems for that part. > Would you like me to help to realize this? > 2. I know two bootloaders, which could be used. The first is the bootloader > from TrueCrypt: If we could get the password from the bootloader, we could > realize a dual-boot system, with one partition with windows and one with > linux, both encrypted. The second possibility is to use the bootloader from > DiskCryptor (http://freed0m.org/), a very nice software for windows. > For this second point, my experience is not enough (can't help). What do you > think about the idea to get the password from the bootloader? > > Regards > Tom Thanks for volunteering to help in SD4L development. Your first point, except for encrypted system disks, is scheduled for version 2.0 which will be the next one (see tracker #1927950). Encrypted system disks are closely related to your second point. Without encrypted system disks getting the password from the boot loader makes no sense. Currently I'm not planning for a SD4L version which runs without a previously loaded Linux kernel which is how I understand encrypted system disks. I estimate this part to be considerably more difficult than getting the password from the boot loader. Furthermore, I would like to know whether you are not satisfied with TrueCrypt concerning this feature. Is there a special point in duplicating this? I have already committed SHA-512 support to the CVS repository. Moreover, I have working code which analyzes new TrueCrpyt containers with the XTS mode. My plan is to transfer this code with some modifications and additions into SD4L in order to open TrueCrypt 5 containers. Another consideration for version 2.0 is a solution of tracker #1849053 (opening containers with GPG keys). I suggest, we discuss in private how you could and like to help SD4L development. Best regards Ulrich |
From: Thomas I. <iks...@gm...> - 2008-03-27 17:20:43
|
Hello first of all, thank you for this nice piece of code. Works really fine, and you also support the newest kernels. Good! What are your plan for the next future? I see two things, that would be of benefit for this project: 1. support for the new TrueCrypt formats (XTS, SHA-512, encrypted system disk) 2. getting the password from the bootloader to mount the boot partition 1. I could help in this point. I do not see special problems for that part. Would you like me to help to realize this? 2. I know two bootloaders, which could be used. The first is the bootloader from TrueCrypt: If we could get the password from the bootloader, we could realize a dual-boot system, with one partition with windows and one with linux, both encrypted. The second possibility is to use the bootloader from DiskCryptor (http://freed0m.org/), a very nice software for windows. For this second point, my experience is not enough (can't help). What do you think about the idea to get the password from the bootloader? Regards Tom |
From: Hans-Ulrich J. <han...@t-...> - 2008-03-16 21:39:46
|
Hello, The stable version 1.3-0 of ScramDisk for Linux has been released. It has the new functionality of a container timeout. If activated on mounting a container, this container will be unmounted after it has been inactive for the configured time. The NTFS filesystem is now supported by ScramDisk for Linux. Moreover, some bugs have been fixed. Packages for CentOS 5, Debian 3.1 and 4.0, Fedora 7 and 8, Mandriva 2008.0, SuSE 10.2 and 10.3 and Ubuntu 7.04 and 7.10 are provided for i386 and AMD64 architectures. The kernel version is part of the filename of binary packages and must match the kernel version of the system it is installed on. The architecture i386 or x86_64 in the filename should also match the architecture of the distribution on which it is installed. Best regards Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2007-10-28 20:30:59
|
Hello, the stable version 1.2-0 of ScramDisk for Linux has been released. It has the new functionality of reformatting containers from ScramDisk to TrueCrypt format. Moreover, the documentation was extended to include some technical background on the container format. And, finally, six bugs have been fixed. This version is available for CentOS, Debian, Fedora, SuSE and Ubuntu distributions. It comprises a kernel driver scramdisk.ko (scramdisk.o for systems with kernel 2.4.x), the graphical user interface scramdisk and five small utilities sdcreate, sdchange, sdmount, sdreformat and sdumount. After a container has been mounted any data could be read from or written to the file system inside the container ransparently with help of the driver scramdiks.ko. By unmounting the container the file system becomes inaccessible again. This can be done by the Mount and Unmount buttons of the graphical user interface or by sdmount and sdumount. The kernel version is part of the filename of binary packages and must match the kernel version of the system it is installed on. The architecture i386 or x86_64 in the filename should also match the architecture of the distribution on which it is installed. Best regards Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2007-08-26 09:22:00
|
Hello, the stable version 1.1-0 of ScramDisk for Linux has been released. It has reworked the kernel driver and now handles input and output requests in separate kernel threads for each container. Thereby, input/output errors are fixed which occasionally occured in previous versions under heavy load. Moreover, handling of large containers of 2 GB and above has been fixed. Finally, the passphrase input lines for scramdisk containers are now restricted to 39 characters each. This was 40 characters previously. By this change full compatibility with the windows scramdisk v3.01r3c is achieved This version is available for CentOS, Debian, Fedora, SuSE and Ubuntu distributions. It comprises a kernel driver scramdisk.ko (scramdisk.o for systems with kernel 2.4.x), the graphical user interface scramdisk and four small utilities sdcreate, sdchange, sdmount and sdumount. After a container has been mounted any data could be read from or written to the file system inside the container ransparently with help of the driver scramdiks.ko. By unmounting the container the file system becomes inaccessible again. This can be done by the Mount and Unmount buttons of the graphical user interface or by sdmount and sdumount. The kernel version is part of the filename of binary packages and must match the kernel version of the system it is installed on. Best regards Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2007-07-15 19:00:39
|
Hello, the stable version 1.0-2 of ScramDisk for Linux has been released. It fixes two bugs and solves a small feature request. The bugs concern mounting of ext3 file systems with option 'auto' and unmounting from kernel if file system mount failed (Tracker 1746730 and 1750002). The new feature disables access right checks on block devices to be mounted as containers (Tracker 1750005). As version 1.0-0, version 1.0-2 opens and creates TrueCrypt containers as well as ScramDisk containers. The supported format of TrueCrypt containers is that of TrueCrypt version 4.1 or later using the LRW mode. Moreover, ScramDisk 1.0-2 can encrypt devices such as partitions on a hard disk or storage media entirely without indirection by a container file. Packages for CentOS 5, Debian 3.1 (Sarge) and 4.0 (Etch), Fedora 7 and Core6, SUSE 10.1 and 10.2 and Ubuntu 6.06, 6.10 and 7.04 are provided for i386 and AMD64 architectures. Best regards Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2007-04-15 15:05:56
|
Hello, the stable version 1.0-1 of ScramDisk for Linux has been released. It fixes two vulnerabilities by which a normal user could obtain root privileges. Now, for normal users, containers are mounted in a way such that the execution of programs with setuid-bit from within the container is inhibited. Moreover, version 1.0-1 forbids mounting a container on a mount point to which the user has no write access. This is so, because otherwise a normal user could mount his container over a system directory and thereby replace system files with his own ones. We advise every user of SD4L to update to version 1.0-1. As version 1.0-0, version 1.0-1 opens and creates TrueCrypt containers as well as ScramDisk containers. The supported format of TrueCrypt containers is that of TrueCrypt version 4.1 or later using the LRW mode. Moreover, ScramDisk 1.0-1 can encrypt devices such as partitions on a hard disk or storage media entirely without indirection by a container file. Packages for Debian 3.1 (Sarge) and 4.0 (Etch), Ubuntu 6.06 and 6.10, Fedora Core5 and Core6 and SUSE 9.3, 10.0, 10.1 and 10.2 are provided for i386 and AMD64 architectures. Best regards Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2007-03-11 10:22:06
|
Hello, The stable version 1.0-0 of ScramDisk for Linux has been released. It now opens and creates TrueCrypt containers as well as ScramDisk containers. The supported format of TrueCrypt containers is that of TrueCrypt version 4.1 or later using the LRW mode. Moreover, ScramDisk 1.0-0 can encrypt devices such as partitions on a hard disk or storage media entirely without indirection by a container file. Packages for Debian 3.1 (Sarge), Ubuntu 6.06 and 6.10, Fedora Core5 and Core6 and SUSE 9.3, 10.0, 10.1 and 10.2 are provided for i386 and AMD64 architectures. The sources are released as src.rpm and tar.gz archives. English and german documentation is provided in PDF format as in the previous release. For .deb and .rpm packages the kernel version is part of the file name. The kernel version for which the package has been built must match the version of the running kernel. Otherwise SD4L may not function properly or even may not install. Best regards Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2006-07-22 19:10:18
|
Hello, Scramdisk 0.9-1 has been released. It is a bugfix release which now builds on kernels up to 2.6.17. I've build packages for Debian 3.1 (kernel 2.6.8 and 2.4.27), Ubuntu 6.06, Fedora Core5 and SuSE 9.3, 10.0 and 10.1, the last three as well for AMD64 as for i386 architecture. The sources are released as src.rpm and tar.gz archives. English and german documentation is provided in PDF format as in the previous release. Best regards Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2006-04-09 13:29:36
|
Hello, Scramdisk 0.9-0 has been released. As in the last release I've build packages for Debian 3.1 (kernel 2.6.8 and 2.4.27) and SuSE 9.0, 9.2, 9.3 and 10.0. The sources are released as src.rpm and tar.gz archives and english and german documentation is provided in PDF format. Scramdisk 0.9-0 has the following new features: * An internationalization with a german translation. The language is chosen from the locale but may be overwritten by configuration. * An option -i/-info for the command line utility sdmount to print information on mounted containers like that displayed by the GUI. * An option -a/-all for the command line utility sdumount to unmount all mounted containers owned by the user. * The possibility for "brutal" unmounting of containers if files or directories within the container are still in use. In the GUI this is done by a pop up message box when normal unmounting fails. In the command line utility there is an option -b/--brutal for this purpose. * Bookmarks for the GUI which enable fast switching between up to 9 preconfigured pairs of container and mount point by the hotkeys Ctrl+1 to Ctrl+9. * The mount option "utf8" for containers with vfat file system is applied if the locale suggests that. This should help in conversion of non ascii characters in file names. Best regards Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2006-03-21 20:07:27
|
Hello, on March 1st I wrote to the list, but the mail seems to have been lost in the course of the sourceforge mailing list problems. So here it is again (with slight modifications due to the work done in the meantime): I'm preparing for SD4L 0.9 which, hopefully, will be released in the end of march. I've already added the following features: * Internationalization with a german translation The language is chosen from the locale but may be overwritten by configuration. * An option -i/-info for the command line utility sdmount to print information on mounted containers like that displayed by the GUI. * An option -a/-all for the command line utility sdumount to unmount all mounted containers owned by the user. * Bookmarks for the GUI which enable fast switching between up to 9 preconfigured pairs of container and mount point by the hotkeys Ctrl+1 to Ctrl+9. * The mount option "utf8" for containers with vfat file system if the locale suggests that. This should help in conversion of non ascii characters in file names. * The possibility for "brutal" unmounting of containers if files or directories within the container are still in use. I decided not to add a button or checkbox but merely to pop up a message box when normal unmounting fails. I would like to have some other opinions on this feature list. Moreover, let me know of any concerns regarding the stability which might be fixed in the course of the release. Regards, Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2006-03-01 20:55:24
|
Hello, I'm preparing for SD4L 0.9 which, hopefully, will be released in the end of march. I've already added the following features: * Internationalization with a german translation The language is chosen from the locale but may be overwritten by configuration. * An option -i/-info for the command line utility sdmount to print information on mounted containers like that displayed by the GUI. * An option -a/-all for the command line utility sdumount to unmount all mounted containers owned by the user. * Bookmarks for the GUI which enable fast switching between up to 9 preconfigured pairs of container and mount point by the hotkeys Ctrl+1 to Ctrl+9. In addition, I consider two more features: * The mount option "utf8" for containers with vfat file system if the locale suggests that. This should help in conversion of non ascii characters in file names. * The possibility for "brutal" unmounting of containers if files or directories within the container are still in use. For this I'm not yet decided wether to add a button or checkbox or merely to pop up a message box when normal unmounting fails. I would like to have some other opinions on this feature list. Moreover, let me know of any concerns regarding the stability which might be fixed in the course of the release. Regards, Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2005-11-13 17:44:33
|
Hello list, Scramdisk 0.8-5 has been released. I modified the package to build and install under Debian 3.1 with kernel 2.6 and SuSE 10.0. To this end I moved the creation of the scramdisk device files in /dev/scramdisk to the boot script. This is because the udevd might remove these files if they are only once created at installation time. I would be very grateful if some of you could install and test at least some of the released files. Best regards Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2005-10-09 13:40:20
|
Hello everybody! R Hannes Beinert wrote: > Hello and welcome, Chris! > Welcome Chris from me too! > --- Christopher Wagner <wa...@st...> wrote: >>It seems there's been very little development on this project. I saw a >>comment posted by Hans-Ulrich Juettner that stated he had made his own >>Linux kernel mode driver and interface for Scramdisk archives. ... > > Actually, your statement was probably more accurate prior to about April > of this year, however since then Ulrich has been kind enough to offer his > code to the SD4L project (which was really a project in name only prior to > that point). > > You will notice a recent file release on the summary page (v0.8.4, 02-Oct-05) > which comprises his working Linux Scramdisk driver, tools and documentation. > > I have been lax in updating the project webpage, and the project development > status to reflect the current situation. > It's probably your prerogative, Hannes, to update the project webpage. But feel free to ask me if I can contribute something to that task. >>... I'm highly >>interested in helping beta-test this, I don't have any real programming >>experience, but I'm interested to help move this along in any way I can. > > Any help or feedback you are willing to contribute would certainly be welcomed. > I certainly encourage you to download the current file release and try it out. > >>I also feel that adding support for DriveCrypt containers could go a long >>way to increasing interest in this project. > > I agree. In fact, there are a number of interesting avenues that one might > explore. However, one would first need to come up with a clear understanding > of the project's scope and purpose -- and how it fits into the larger body of > OTFE OSS currently available. Also, naturally, it would depend upon the > amount of developer interest. > > My initial goal for the SD4L project has been to generate/host a Linux driver > for Scramdisk containers, so that Linux would finally have the ability to > manipulate these containers. Thanks to Ulrich's development efforts I believe > this goal has largely been met. This development gives the encrypted Scramdisk > container a great deal more utility. The codebase which Ulrich has written > can also now be used as a stepping stone to OSX on the Macintosh. Once this > has been accomplished, the SD container will be portable between all major > contemporary platforms -- which would be a significant and valuable achievement. > I agree that support for Mac OS X would be a valuable achievement. There is even a friend of mine who asked whether it could be done. However, I have absolutely no experience with Mac OS X, to say nothing of the Darwin kernel. I believe, porting the Linux kernel driver to Darwin will be a major programming task. > Further efforts, however, would need to confront the inherent limitations of > the SD container structure. I honestly have no well-developed thoughts on > the wisdom of pursuing these issues. > >>Hans-Ulrich, feel free to get in contact with me at the above address and >>we can discuss beta-testing arrangements if you're still interested in >>doing that. Potentially, if the project maintainers for SD4L are choosing >>to abandon the project, perhaps we could continue it either under the same >>project name or another? > > I think it's fair to say that the project has moved forward slowly, and some > portions have been a bit neglected (mea culpa), but at the same time it *has* > moved forward thanks to Ulrich -- I have no intention to allow the project to > become abandoned, since I do feel it fulfills a useful function. > The project definitely needs more beta testing to make further progress. The release 0.8-4 was the result of a user having problems which turned out to be due to an SuSE online update patching the kernel. Testing the packages on the supported plattforms (SuSE and Debian up to now) and/or compiling and testing the sources on other distributions would be of great help. The said user got in touch with me by private mail. But I think such questions are better discussed openly on the mailing list. Moreover, we could use the sourceforge.net tracking system to report bugs. What do you think about that? > FWIW, I believe it would be useful to carry on any discussions on this list > regarding testing or further development -- that is its primary purpose! ;-) > > Thank you for your interest, Chris! > > Hannes. > Thanks to Chris from me too, especially for the beta-testing offer. Best regards Ulrich |
From: R H. B. <arg...@ya...> - 2005-10-09 01:06:32
|
Hello and welcome, Chris! --- Christopher Wagner <wa...@st...> wrote: > > It seems there's been very little development on this project. I saw a > comment posted by Hans-Ulrich Juettner that stated he had made his own > Linux kernel mode driver and interface for Scramdisk archives. ... Actually, your statement was probably more accurate prior to about April of this year, however since then Ulrich has been kind enough to offer his code to the SD4L project (which was really a project in name only prior to that point). You will notice a recent file release on the summary page (v0.8.4, 02-Oct-05) which comprises his working Linux Scramdisk driver, tools and documentation. I have been lax in updating the project webpage, and the project development status to reflect the current situation. > ... I'm highly > interested in helping beta-test this, I don't have any real programming > experience, but I'm interested to help move this along in any way I can. Any help or feedback you are willing to contribute would certainly be welcomed. I certainly encourage you to download the current file release and try it out. > I also feel that adding support for DriveCrypt containers could go a long > way to increasing interest in this project. I agree. In fact, there are a number of interesting avenues that one might explore. However, one would first need to come up with a clear understanding of the project's scope and purpose -- and how it fits into the larger body of OTFE OSS currently available. Also, naturally, it would depend upon the amount of developer interest. My initial goal for the SD4L project has been to generate/host a Linux driver for Scramdisk containers, so that Linux would finally have the ability to manipulate these containers. Thanks to Ulrich's development efforts I believe this goal has largely been met. This development gives the encrypted Scramdisk container a great deal more utility. The codebase which Ulrich has written can also now be used as a stepping stone to OSX on the Macintosh. Once this has been accomplished, the SD container will be portable between all major contemporary platforms -- which would be a significant and valuable achievement. Further efforts, however, would need to confront the inherent limitations of the SD container structure. I honestly have no well-developed thoughts on the wisdom of pursuing these issues. > Hans-Ulrich, feel free to get in contact with me at the above address and > we can discuss beta-testing arrangements if you're still interested in > doing that. Potentially, if the project maintainers for SD4L are choosing > to abandon the project, perhaps we could continue it either under the same > project name or another? I think it's fair to say that the project has moved forward slowly, and some portions have been a bit neglected (mea culpa), but at the same time it *has* moved forward thanks to Ulrich -- I have no intention to allow the project to become abandoned, since I do feel it fulfills a useful function. FWIW, I believe it would be useful to carry on any discussions on this list regarding testing or further development -- that is its primary purpose! ;-) Thank you for your interest, Chris! Hannes. __________________________________ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs |
From: Christopher W. <wa...@st...> - 2005-10-08 03:25:09
|
It seems there's been very little development on this project. I saw a comment posted by Hans-Ulrich Juettner that stated he had made his own Linux kernel mode driver and interface for Scramdisk archives. I'm highl= y interested in helping beta-test this, I don't have any real programming experience, but I'm interested to help move this along in any way I can.=20 I also feel that adding support for DriveCrypt containers could go a long way to increasing interest in this project. Hans-Ulrich, feel free to get in contact with me at the above address and we can discuss beta-testing arrangements if you're still interested in doing that. Potentially, if the project maintainers for SD4L are choosin= g to abandon the project, perhaps we could continue it either under the sam= e project name or another? - Chris |
From: Hans-Ulrich J. <han...@t-...> - 2005-05-08 13:45:25
|
Hello once more, is there anybody listening on the list? Hannes, if you get this mail please reply. Nearly two month ago, on March 16, I wrote: > Hello, > > like Hannes, I also felt the lack of Scramdisk for Linux > for many years. Two years ago I decided to do it myself. > Now I just finished a beta version including a kernel > driver (building with kernels 2.4 and 2.6) and a GUI for > handling containers built with Qt. It works for me on SuSE > 9.0, 9.1 and 9.2. The code will be put under the GPL and > I am looking for beta testers. > > There seems to be not much activity on the sourceforge.net > project Scramdisk 4 Linux yet. So I want to ask wether the > maintainers of the project would like to host or adopt my > developement. Of course I want to be engaged in further > developements and decisions on it. > > Please let me hear what you think about that. > > Best regards > Ulrich It would be nice, if my Scramdisk for Linux code could be published on the Sd4L project site. But even if this is not possible or not wanted let me know. Greetings Ulrich |
From: Hans-Ulrich J. <han...@t-...> - 2005-03-16 22:06:58
|
Hello, like Hannes, I also felt the lack of Scramdisk for Linux for many years. Two years ago I decided to do it myself. Now I just finished a beta version including a kernel driver (building with kernels 2.4 and 2.6) and a GUI for handling containers built with Qt. It works for me on SuSE 9.0, 9.1 and 9.2. The code will be put under the GPL and I am looking for beta testers. There seems to be not much activity on the sourceforge.net project Scramdisk 4 Linux yet. So I want to ask wether the maintainers of the project would like to host or adopt my developement. Of course I want to be engaged in further developements and decisions on it. Please let me hear what you think about that. Best regards Ulrich |
From: <or...@do...> - 2004-08-06 06:13:48
|
Hello! In a previous message you (The Thinker) write: > > Hello, just a suggestion. > > Scramdisk and Scramdisk volume format is de facto dead because of the > following: > > 1) There is no Windows XP application that can create Scramdisk containers > (closed-source Drivecrypt can only read Scramdisk containers, not write). > > 2) The format is limited to 32-bit sector count (IV, and other parameters > are hard-coded for 32-bits) therefore the container size is limited and > the format will have to be substantially reworked. Absolutely -- these are both very valid points. I am personally unaffected by the inability to use the SD containers on XP, so I never gave it much thought other than to assume that a client could be written at some point if there were interest. Similarly, my uses of SD are not such that the container size has ever become an issue. Your point is well-taken, however, in that SD would need some serious work for it to be optimally useful to users of modern hardware & software. It is clearly reasonable to ask whether it is worthwhile to update SD in this manner. On the other hand, I have always keenly felt the absence of a Linux driver for SD, making it impossible to transport data in SD containers. I do believe, at minimum, that this is worthwhile task. I am sure that I am not the only person to have archived SD containers, and I don't relish the idea that I will need to maintain a Windows box merely to ensure my access to these files. And, I suppose I have always had a soft spot for Scramdisk because of its very humble footprint, and its utilitarian design. > Here's the suggestion: If you are willing to create a driver for > a Windows OFTE program, why not help develop the Linux version of > TrueCrypt? TrueCrypt is the successor to E4M and in the Scramdisk > community it is also generally considered to be the true open-source > successor to Scramdisk. http://www.truecrypt.tk An interesting suggestion... ;-) Hannes. -- Email: or...@do... <*> PGP |
From: The T. <thi...@ly...> - 2004-08-05 13:14:10
|
Hello, just a suggestion. Scramdisk and Scramdisk volume format is de facto dead because of the following: 1) There is no Windows XP application that can create Scramdisk containers (closed-source Drivecrypt can only read Scramdisk containers, not write). 2) The format is limited to 32-bit sector count (IV, and other parameters are hard-coded for 32-bits) therefore the container size is limited and the format will have to be substantially reworked. Here's the suggestion: If you are willing to create a driver for a Windows OFTE program, why not help develop the Linux version of TrueCrypt? TrueCrypt is the successor to E4M and in the Scramdisk community it is also generally considered to be the true open-source successor to Scramdisk. http://www.truecrypt.tk -- _______________________________________________ Find what you are looking for with the Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10 |