Print

Welcome to Smokey's Security Forums.

Guests have only limited access to the board and it's features, please consider registering to gain full access!

Registration is free and it only takes a few moments to complete.

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[warfish]

Hello everyone.

We have located and fixed the problem.
The fix is currently undergoing a testing stage and will be released with the next version later this week.

Thanks everyone for your cooperation in locating this bug.

Evgeny.

[warfish]

Hi, Wobble.

I was working on this problem ever since the first report in this topic, but i still can not reproduce it whatever i tried. However, eventually i came up with a solution to test and send it to another user with the same problem today but haven't received a reply yet.

If you would like to participate in testing, please contact me through jetico support email (support@jetico.com). In this case i will also need a bc.ko module, build on your system that causes a lock up.

In any case, i will keep you posted.
Evgeny.

[Wobble]

Being slightly crazy, I sat at the console and attempted to mount the volume again (after unmounting all important partitions!), and then took a photo of the resulting trace. Not sure if this is of any help, but hopefully it'll give some indication of where it crashed:

[attachment=0:2o85ygk9]BcCrash.jpg[/attachment:2o85ygk9]

Again, no actual access to bash. All I could do was attempt to sysrq to sync the remaining discs and unmount to safety.

[Wobble]

Hi,

I've just encountered what seems to be the same problem, although I'm running Ubuntu 8.10 instead of CentOS. I downloaded and compiled bcrypt-1.6-24 (i.e. make / make install), ran depmod, modprobe bc, and then finally attempted to use bcmount to mount a file-based bestcrypt volume.

The system then promptly hung. I lost all network contact with the machine, and when I went and looked at the machine itself, all keyboard / mouse input had frozen (and I couldn't switch out of X to get to a console) :/

Currently running:
Linux wobble 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux

-Wobble  

[warfish]

Hi, Al.

I managed to put together the testing environment you described, but i can't reproduce the problem. Does your system hangs up only when you're trying to mount encrypted block devices or with the regular file-based containers too?

Evgeny.

[almerindo]

Thank you
Al

[warfish]

Hello,

I am using Centos 5. The kernel is 2.6.18-92.1.22.el5PAE and I already tried switching to another terminal but nothing works and I have to press the power button

Al

Hi, Al.

We had a lot of problems with this particular setup before. CentOS distro adds it's own patches to stable kernels which makes some things rather hard to predict. I will get right on it asap.

Evgeny.

[almerindo]

Hello,

I am using Centos 5. The kernel is 2.6.18-92.1.22.el5PAE and I already tried switching to another terminal but nothing works and I have to press the power button

Al

[warfish]

Hi.

Dead lockup means a kernel specific problem. Please tell me which linux distro you are using and your kernel version (uname -a). Also, right after the lockup try to switch to another terminal (Alt+Ctrl+F1-F8, depending on your distro), login from there and do a 'dmesg|tail' command, and post the output here.

[almerindo]

Hello,

I've finally managed to install BestCrypt but I cannot use it just yet. I am trying creating a container on a USB pen ( I have tried on to different models with the same results) and every time I try to mount the USB, it asks for a password, i enter the password and the whole system hans and I have to proceed with a hard reboot. This is what I am doing:

[al@localhost ~]$ sudo bcnew -a rijndael /dev/sdb1
Password:
Warning: All data on specified block device will be lost! Continue? (y/[n]):y
Enter password:
Verify password:

Please do not forget to format the container

[al@localhost ~]$ sudo bcformat -t ext3 /dev/sdb1
Enter password:
mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
31360 inodes, 125152 blocks
0 blocks (0.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67371008
16 block groups
8192 blocks per group, 8192 fragments per group
1960 inodes per group
Superblock backups stored on blocks:
        8193, 24577, 40961, 57345, 73729

Writing inode tables: done                            
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 20 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.

[al@localhost ~]$ sudo bcmount -t ext3 /dev/sdb1
Password:



And after I enter the password, right or wrong the system freezes and he CAPS lock light on the laptop starts flashing.


Please let me know what I am doing wrong

Thank you
Al