sd4l-user — General discussion and support questions

Re: [SD4L-user] Container timeout.

[Hans-Ulrich J. <han...@t-...>]

Hello,

thanks for your kind evaluation of SD4L. As concerns your question,
the requested feature could be added to the next version of SD4L.
It might be possible but certainly would be very tricky to do this
in a cron job. The difficult part would be to correctly determine
the idle time of the mounted volume. Especially, when databases
are involved, the idle time might even not be deduced from the
timestamps of all files in the container. On the other hand, the
kernel driver could start a timer which is reset to zero every
time he is asked to read or write from/to the container.

I don't know whether mysql holds an open connection to its files.
This, however, seems not unlikely. SD4L offers the possibility to
brutally unmount a container despite open files hold by some
processes. The method is to kill all processes holding open files
in the container. But I won't recommend this in normal situations
because it exposes you to the danger of data loss.

Best regards
Ulrich

Plutocrat wrote:
> First of all, great job on Scramdisk 4 Linux. I've been using Truecrypt on Windows for several years, so when a client asked me about encryption on his Linux server, I instantly thought of Truecrypt. However there was no pre-built package for Centos/RHEL, so I spent several days struggling to get truecrypt to compile, crashing the server, recovering from kernel panics, etc. 
> 
> Then I found scramdisk 4 linux which took me approximately 20 seconds to install. Enough said. 
> 
> OK now to my question. One of the features of truecrypt that my client liked was the feature to timeout a container after a period of inactivity. I believe this also was a feature of scramdisk for windows. Is this feature likely to make it into SD4L? 
> 
> If not, is there a sneaky way I can do this with a shell script? (eg fire off a cron job once an hour which checks a value, and then sdumounts a given container or not depending on what it finds? 
> 
> Just to make things more difficult, the container in this instance is holding a mysql database, so I'm not sure if that would affect things ... does mysql hold open a connection to the database files even when the tables aren't being accessed? 
> 
> Cheers ... 
> 
> -------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services
> for just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> SD4L-user mailing list
> SD4...@li...
> https://lists.sourceforge.net/lists/listinfo/sd4l-user
> 

[SD4L-user] Container timeout.

[Plutocrat <plu...@gm...>]

First of all, great job on Scramdisk 4 Linux. I've been using Truecrypt on Windows for several years, so when a client asked me about encryption on his Linux server, I instantly thought of Truecrypt. However there was no pre-built package for Centos/RHEL, so I spent several days struggling to get truecrypt to compile, crashing the server, recovering from kernel panics, etc. 

Then I found scramdisk 4 linux which took me approximately 20 seconds to install. Enough said. 

OK now to my question. One of the features of truecrypt that my client liked was the feature to timeout a container after a period of inactivity. I believe this also was a feature of scramdisk for windows. Is this feature likely to make it into SD4L? 

If not, is there a sneaky way I can do this with a shell script? (eg fire off a cron job once an hour which checks a value, and then sdumounts a given container or not depending on what it finds? 

Just to make things more difficult, the container in this instance is holding a mysql database, so I'm not sure if that would affect things ... does mysql hold open a connection to the database files even when the tables aren't being accessed? 

Cheers ... 

[SD4L-user] ScramDisk for Linux 1.2-0 released

[Hans-Ulrich J. <han...@t-...>]

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

[SD4L-user] ScramDisk for Linux 1.1-0 released

[Hans-Ulrich J. <han...@t-...>]

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

Re: [SD4L-user] New (Linux) User Problems with Scramdisk for Linux 1.0-2

[Hans-Ulrich J. <han...@t-...>]

Hi,

Millen, Stewart wrote:
> Update: I just opened one of the Truecrypt-compatible containers I had
> created (but wouldn't 
> mount) that was 2.0 gigabytes in size using TrueCrypt (for Windows).
> However, it told me 
> that the container was unformatted, and offered to format it for me.
> 
> So it seems that within-container file formats are indeed the problem.
> Whatever Scramdisk 
> is using to format (or to read formats) of anything else other than
> FAT12 isn't working, 
> 
> Stewart
> 

at least your problem with 2.0 GB containers is due a bug in SD4L.
The other problems seem to be also caused by another bug in SD4L.
The relevant bugs are described in trackers 1772346 and 1772347.
Tomorrow or the day after tomorrow version 1.1-0 will be released
which fixes these bugs. Would you please give SD4L 1.1-0 a try?

Best regards
Ulrich

Re: [SD4L-user] New (Linux) User Problems with Scramdisk for Linux 1.0-2

[Millen, S. <smm...@ea...>]

Update: I just opened one of the Truecrypt-compatible containers I had
created (but wouldn't=20
mount) that was 2.0 gigabytes in size using TrueCrypt (for Windows).
However, it told me=20
that the container was unformatted, and offered to format it for me.

So it seems that within-container file formats are indeed the problem.
Whatever Scramdisk=20
is using to format (or to read formats) of anything else other than
FAT12 isn't working,=20

Stewart

> ______________________________________________=20
> From: 	Millen, Stewart =20
> Sent:	Wednesday, August 22, 2007 5:50 PM
> To:	'sd4...@li...'
> Subject:	New (Linux) User Problems with Scramdisk for Linux 1.0-2
>=20
> I'm a long-time Windows user of Scramdisk and have now purchased a
> Linux box (Dell) with
> Ubuntu Feisty 7.04, determined to make the switch to Linux.
>=20
> I downloaded the deb file for Ubuntu 7.04, and also (when told it
> needed the Trolltech libqt3-mt
> dependency) the libqt3-mt library from the Ubuntu software universe:
>=20
> http://packages.ubuntu.com/feisty/libs/libqt3-mt
>=20
> After I did this, SD4L installed and opened apparently succesfully.
> But what I'm seeing is:
>=20
> a) I can create and open small (like floppy size, 1.4 megabyte)
> containers created by either
> SD4L or legacy Windows Scramdisk OK.
>=20
> b) I can open small (1 megabyte) containers created with TrueCrypt (on
> a Windows machine)=20
> OK, irregardless of the algorithms chosen.
>=20
> c) Containers larger than floppy sized (I've tried down to 500
> megabytes) cause the=20
> OS to lock up completely requiring a hard reboot after entering the
> password and trying
> to mount. This is irregardless of the hash algorithm,  encryption
> algorithm, or file format=20
> chosen. It is also irregardless of whether the containers were created
> with SD4L or=20
> whether they were created by TrueCrypt on a Windows machine.
>=20
> d) When walking away from a container creation for "large" containers,
> sometimes I come
> back to the desktop seeing that SD4L has closed in the process of
> container generation.=20
> When attempting to create containers bigger than 2 gigabytes, I always
> get containers of=20
> 2.0 gigabytes irregardless of the size chosen. Needless to say, all
> these freeze up the OS=20
> when I try to mount them as per above.
>=20
> I see on the Ubuntu forums that one other user has complained about
> not being able to=20
> mount containers, and I also see here there is a problem with
> containers larger than 2=20
> gigabytes. However, apparently some users are succesfully creating and
> using containers
> up to 2 gigabytes, which I can not.
>=20
> So...(and remember I'm a complete Linux newbie)...is there some other
> library or dependency
> that I've not fulfilled? Do I need to install something else? What am
> I doing wrong?
>=20
>=20

[SD4L-user] New (Linux) User Problems with Scramdisk for Linux 1.0-2

[Millen, S. <smm...@ea...>]

I'm a long-time Windows user of Scramdisk and have now purchased a Linux
box (Dell) with
Ubuntu Feisty 7.04, determined to make the switch to Linux.

I downloaded the deb file for Ubuntu 7.04, and also (when told it needed
the Trolltech libqt3-mt
dependency) the libqt3-mt library from the Ubuntu software universe:

http://packages.ubuntu.com/feisty/libs/libqt3-mt

After I did this, SD4L installed and opened apparently succesfully. But
what I'm seeing is:

a) I can create and open small (like floppy size, 1.4 megabyte)
containers created by either
SD4L or legacy Windows Scramdisk OK.

b) I can open small (1 megabyte) containers created with TrueCrypt (on a
Windows machine)=20
OK, irregardless of the algorithms chosen.

c) Containers larger than floppy sized (I've tried down to 500
megabytes) cause the=20
OS to lock up completely requiring a hard reboot after entering the
password and trying
to mount. This is irregardless of the hash algorithm,  encryption
algorithm, or file format=20
chosen. It is also irregardless of whether the containers were created
with SD4L or=20
whether they were created by TrueCrypt on a Windows machine.

d) When walking away from a container creation for "large" containers,
sometimes I come
back to the desktop seeing that SD4L has closed in the process of
container generation.=20
When attempting to create containers bigger than 2 gigabytes, I always
get containers of=20
2.0 gigabytes irregardless of the size chosen. Needless to say, all
these freeze up the OS=20
when I try to mount them as per above.

I see on the Ubuntu forums that one other user has complained about not
being able to=20
mount containers, and I also see here there is a problem with containers
larger than 2=20
gigabytes. However, apparently some users are succesfully creating and
using containers
up to 2 gigabytes, which I can not.

So...(and remember I'm a complete Linux newbie)...is there some other
library or dependency
that I've not fulfilled? Do I need to install something else? What am I
doing wrong?

[SD4L-user] ScramDisk for Linux 1.0-2 released

[Hans-Ulrich J. <han...@t-...>]

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

[SD4L-user] ScramDisk for Linux 1.0-1 released

[Hans-Ulrich J. <han...@t-...>]

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

[SD4L-user] ScramDisk for Linux 1.0-0 released

[Hans-Ulrich J. <han...@t-...>]

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

Re: [SD4L-user] Spoke too soon...

[Hans-Ulrich J. <han...@t-...>]

Hi Steve,

SD4L is absolutely blind to what files are copied
to or from a container. If you could reproduce this
odd behaviour I would be very interested to here under
what circumstances you get failures. If the behaviour
depends only the mounted container it could be that
it was mounted read only in some cases because the
container file was not writable by the user who did
the mount. Does that help?

Best regards
Ulrich

[SD4L-user] Spoke too soon...

[Steve K <ste...@ya...>]

Well heck.

When it comes to actually using SD4L, it seems that I am either 
missing something basic, or the program is not quite ready for 
use.  Containers created with vfat, ext2, and ext3 on my machine,
all behave very oddly:  They seem to have minds of their own, 
whimsically deciding which files they will and will not allow 
to be copied into them, and once files are added, again there 
seems to be a random factor in whether the files are readable 
by applications or not.  The only aspect that seems to be
entirely
stable and functional, is the ability of SD4L to mount existing
fat32 containers created under Windows with the original SD in 
read-only mode.

But I will keep tinkering with the program here in hope that 
I will discover that I am doing something wrong, and of course, 
I will be trying out revisions as they are released. 

:o)

Steve K



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[SD4L-user] Just installed SD4L on Ubuntu

[Steve K <ste...@ya...>]

Hi!

Just a note of appreciation to the developers:  Bravo!

A couple of minutes after learning it existed, I installed 
Scramdisk_0.9-1_Ubuntu-6.06_2.6.15_i386.deb on my Ubuntu 
box.  And booted to the kernel in question:  I have not 
yet tested to see if a K7 kernel will accept the module(s)
SD4L loads, but from past experiments with encrypted filesystem 
installs, I am not optomistic.  This is not a great loss - 
frankly I notice no performance difference between the i386 and
AMD K7 optomized kernels, in the stuff I use the computer in 
question for.

The install was hassle free via the GDebi Package Installer, 
and SD4L appears to be working perfectly.  I created a 1 GB 
container using all default options, and it mounts, reads and
writes, unmounts, and mounts again with no problems.  I also 
have a couple of old FAT32 SD containers, and these mount and 
read OK as well.

Again, thanks for the way cool tool.  It fills a real gap in 
my system configuration.

:o)

Steve K



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[SD4L-user] Scramdisk 0.9-1 released

[Hans-Ulrich J. <han...@t-...>]

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

Re: [SD4L-user] Mount failed - No such file or directory

[Hans-Ulrich J. <han...@t-...>]

Hello maxl,

thank you for posting, you seem to have come up with a bug
in my kernel driver which hasn't manifested on the Linux
distributions I have built and tested Sd4L so far.

maxl wrote:
> Hello.
> I desperatly need help on this.
> I am in this linux 'adventure' for about two weeks, so everything that
> skips the "step by step" method transcends me.  :-)

(snip)

>   CC [M]  /home/user/Desktop/Scramdisk-0.9/driver/sddriver.o
> /home/user/Desktop/Scramdisk-0.9/driver/sddriver.c: In function
> ‘scramdisk_init’:
> /home/user/Desktop/Scramdisk-0.9/driver/sddriver.c:963: error: invalid
> type argument of ‘unary *’
> make[3]: *** [/home/user/Desktop/Scramdisk-0.9/driver/sddriver.o] Error 1
> make[2]: *** [_module_/home/user/Desktop/Scramdisk-0.9/driver] Error 2
> make[2]: Leaving directory `/usr/src/linux-headers-2.6.15-23-386'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/user/Desktop/Scramdisk-0.9/driver'
> make[1]: Entering directory `/home/user/Desktop/Scramdisk-0.9/utils'
> g++ -I. -I../crypto -I../driver -O2 -Wall -c -o sdcreate.o sdcreate.cpp
> <\snip>
> 

This error is the reason for your later problems. It's a bug
which hasn't shown in conjunction with older kernel versions
(the latest kernel version with which I built Sd4L is 2.6.13).

> and this:
> 
> <snip>
> make[1]: Entering directory `/home/user/Desktop/Scramdisk-0.9/docs'
> ps2pdf gui.eps gui.pdf
> ps2pdf create.eps create.pdf
> ps2pdf ppdialog.eps ppdialog.pdf
> ps2pdf config.eps config.pdf
> pdflatex scramdisk.tex && pdflatex scramdisk.tex
> /bin/sh: pdflatex: command not found
> make[1]: *** [scramdisk.pdf] Error 127
> make[1]: Leaving directory `/home/user/Desktop/Scramdisk-0.9/docs'
> make: *** [all] Error 2
> user@ubuntu:~/Desktop/Scramdisk-0.9$
> </snip>
> 

This error is due to the missing pdflatex in your system.
It merely means that you failed to build the documentation,
so you may ignore it. You may also install pdflatex on your
system in order to get rid of this error.

> 
> Reboot, than start SD4L in terminal- scramdisk (later I did a shortcut).
> 
> Program starts with a nice GUI, enter paht to container, and path to mount
> dir previously created;(/mnt/) or (/home/mnt/).
> 
> Click mount, enter the passfhrase and get this error:
> 
> "Mounting failed:"
> "No such file or directory"
> 
> I am not sure if this is related to those errors shown durin make, make
> install....
> 

Yes it is, you failed to build the kernel driver which is
necessary for mounting.

> FYI, I made a "test" sd4l container of 64MB (raw) but couldn't mount than
> went to windowsXP and formatted it with windows fat32 and it work in my
> windows system. Back to linux still couldn't mount it.
> 
> As a side note, the "options" window is not fitting in height, the screen
> of my laptop, and doesn't resize in order to show the bottom buttons!
> 

Thank you, for pointing this out. I thought it would fit on most
screens today when I enlarged the size in version 0.9.0. I shall
reduce it again in the next version.

I am going to install Ubuntu 6.06 on a free partition an will build
a new package with the bugs fixed. This, however, will take some weeks.
If you are in a hurry to get Sd4L running on your system I could
send you a patch with private mail. Of course, I would prefer to
test the bugfix myself at first before sending it out. Please, mail
me what you would like.

Best regards,
Ulrich

[SD4L-user] Mount failed - No such file or directory

[maxl <max...@gm...>]

Hello.
I desperatly need help on this.
I am in this linux 'adventure' for about two weeks, so everything that
skips the "step by step" method transcends me.  :-)

uname:Linux ubuntu 2.6.15-23-386 #1 PREEMPT Tue May 23 13:49:40 UTC 2006
i686 GNU/Linux
PIII 1GHz


After lots of google and forums reading I start as in the sd4L pdf
instructions by "installing" kernel sources in /usr/src/
also intalled kernel headers.

Than
make oldconfig
and
user@ubuntu:/usr/src/linux$ sudo make dep
*** Warning: make dep is unnecessary now.    (???)

Untar the scramdisk source to Desktop, cd Scramdisk-0.9, and run
'make'
During the make process I get these errors:

<snip>
	
  CC [M]  /home/user/Desktop/Scramdisk-0.9/driver/volume.o
  CC [M]  /home/user/Desktop/Scramdisk-0.9/driver/sddriver.o
/home/user/Desktop/Scramdisk-0.9/driver/sddriver.c: In function
‘scramdisk_init’:
/home/user/Desktop/Scramdisk-0.9/driver/sddriver.c:963: error: invalid
type argument of ‘unary *’
make[3]: *** [/home/user/Desktop/Scramdisk-0.9/driver/sddriver.o] Error 1
make[2]: *** [_module_/home/user/Desktop/Scramdisk-0.9/driver] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.15-23-386'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/user/Desktop/Scramdisk-0.9/driver'
make[1]: Entering directory `/home/user/Desktop/Scramdisk-0.9/utils'
g++ -I. -I../crypto -I../driver -O2 -Wall -c -o sdcreate.o sdcreate.cpp
<\snip>

and this:

<snip>
make[1]: Entering directory `/home/user/Desktop/Scramdisk-0.9/docs'
ps2pdf gui.eps gui.pdf
ps2pdf create.eps create.pdf
ps2pdf ppdialog.eps ppdialog.pdf
ps2pdf config.eps config.pdf
pdflatex scramdisk.tex && pdflatex scramdisk.tex
/bin/sh: pdflatex: command not found
make[1]: *** [scramdisk.pdf] Error 127
make[1]: Leaving directory `/home/user/Desktop/Scramdisk-0.9/docs'
make: *** [all] Error 2
user@ubuntu:~/Desktop/Scramdisk-0.9$
</snip>

than

make install

user@ubuntu:~/Desktop/Scramdisk-0.9$ sudo make install
Password:
list='crypto driver utils gui docs'; for subdir in $list; \
        do make -C $subdir install; done
make[1]: Entering directory `/home/user/Desktop/Scramdisk-0.9/crypto'
make[1]: Nothing to be done for `install'.
make[1]: Leaving directory `/home/user/Desktop/Scramdisk-0.9/crypto'
make[1]: Entering directory `/home/user/Desktop/Scramdisk-0.9/driver'
if ! test -d /lib/modules/scramdisk; then \
          mkdir -p /lib/modules/scramdisk; \
        fi && \
        install -m 644 scramdisk.ko /lib/modules/scramdisk && \
        cd /lib/modules/2.6.15-23-386/extra && \
        ln -s ../../scramdisk/scramdisk.ko scramdisk.ko && \
        depmod -F /boot/System.map-`uname -r`
install: cannot stat `scramdisk.ko': No such file or directory
make[1]: *** [install] Error 1
make[1]: Leaving directory `/home/user/Desktop/Scramdisk-0.9/driver'
make[1]: Entering directory `/home/user/Desktop/Scramdisk-0.9/utils'
mkdir -p /usr/bin
install -m 4755 sdcreate sdmount sdumount /usr/bin
install -m 755 sdchange /usr/bin
test -d /etc/scramdisk/ || mkdir -p /etc/scramdisk
test -d /usr/share/scramdisk/ || mkdir -p /usr/share/scramdisk
install -m 644 scramdiskrc /etc/scramdisk
if test -d /etc/init.d/boot.d; then \
          (install -m 755 scramdisk.init /etc/init.d/boot.scramdisk && \
           test -x /sbin/insserv && /sbin/insserv
/etc/init.d/boot.scramdisk); \
        elif test -d /etc/rcS.d; then \
          (install -m 755 scramdisk.init /etc/init.d/scramdisk && \
           test -x /usr/sbin/update-rc.d && \
           /usr/sbin/update-rc.d scramdisk start 80 S . stop 04 S .); \
        fi
 Adding system startup for /etc/init.d/scramdisk ...
   /etc/rcS.d/K04scramdisk -> ../init.d/scramdisk
   /etc/rcS.d/S80scramdisk -> ../init.d/scramdisk
./scramdisk.init start
Scramdisk not installed
make[1]: *** [install] Error 5
make[1]: Leaving directory `/home/user/Desktop/Scramdisk-0.9/utils'
make[1]: Entering directory `/home/user/Desktop/Scramdisk-0.9/gui'
cp -f "scramdisk" "/usr/bin/scramdisk"
strip "/usr/bin/scramdisk"
chmod 4755 /usr/bin/scramdisk
cp -f "change.png" "/usr/share/scramdisk/"
cp -f "create.png" "/usr/share/scramdisk/"
cp -f "mount.png" "/usr/share/scramdisk/"
cp -f "scramdisk.png" "/usr/share/scramdisk/"
cp -f "umount.png" "/usr/share/scramdisk/"
make[1]: Leaving directory `/home/user/Desktop/Scramdisk-0.9/gui'
make[1]: Entering directory `/home/user/Desktop/Scramdisk-0.9/docs'
test -d /usr/share/scramdisk || mkdir -p /usr/share/scramdisk
test -d /usr/share/doc/scramdisk || mkdir -p /usr/share/doc/scramdisk
install -m 644 index_en.html intro_en.html mount_en.html create_en.html
change_en.html config_en.html index_de.html intro_de.html mount_de.html
create_de.html change_de.html config_de.html gui.jpg create.jpg
ppdialog.jpg config.jpg gui_de.jpg create_de.jpg ppdialog_de.jpg
config_de.jpg /usr/share/scramdisk
install -m 644 scramdisk.pdf /usr/share/doc/scramdisk/scramdisk_en.pdf
install: cannot stat `scramdisk.pdf': No such file or directory
make[1]: *** [install] Error 1
make[1]: Leaving directory `/home/user/Desktop/Scramdisk-0.9/docs'
make: *** [install] Error 2
user@ubuntu:~/Desktop/Scramdisk-0.9$


Reboot, than start SD4L in terminal- scramdisk (later I did a shortcut).

Program starts with a nice GUI, enter paht to container, and path to mount
dir previously created;(/mnt/) or (/home/mnt/).

Click mount, enter the passfhrase and get this error:

"Mounting failed:"
"No such file or directory"

I am not sure if this is related to those errors shown durin make, make
install....

FYI, I made a "test" sd4l container of 64MB (raw) but couldn't mount than
went to windowsXP and formatted it with windows fat32 and it work in my
windows system. Back to linux still couldn't mount it.

As a side note, the "options" window is not fitting in height, the screen
of my laptop, and doesn't resize in order to show the bottom buttons!

TIA.

[SD4L-user] Scramdisk 0.9-0 released

[Hans-Ulrich J. <han...@t-...>]

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

[SD4L-user] SD4L

[The T. <thi...@ly...>]

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