В® LUKS Manager | Encrypts data on the fly (AES by default)
LUKS Manager
Version: 2.4
Last update of the program in the header:24.05.2012
For the operation of the program requires root user rights.
Description:
LUKS Manager encrypts virtual folder on the fly using AES (by default).
With this program you can create, delete, mount and unmount disks dynamically.
This package contains (untranslatable =)):
A statically compiled and stripped version of cryptsetup for the ARM using the tools provided by the Guardianproject.
A statically compiled and stripped version of mkdosfs from dosfstools package for the ARM7.
A bash shell script called "luks" that does volume management.
And a native java app that provides a GUI interface to the luks script, a basic file explorer and simple text editor.
To take full advantage of the program, you must have:
no program is not redistributed. It creates a file on a flash drive with the extension*** .vol size specified at creation of the virtual folders. And it keeps it all the Old encrypted. But she had a program, a file that installs as a virtual disk, it becomes available as / mnt / sdcard / *** (Where *** file name *** .vol)
You open a file from your computer?
FreeOTFE
Software for Windows, which allows you to work directly with a computer file*** .vol.
Push:
It is a copy of a similar program for Windows - TrueCrypt, estesstvenno with simpler functionality, but the idea is similar.
In spite of statements to the effect that the program is not on most runoff firmware on my Samsung Galaxy S II in the sink and the drain firmware kernel as root with the full functionality of the program is running.
Developer: Nemesis] [
Homepage: http://nemesis2.qx.net/
Android Market: market: // search / q = pname:? com.nemesis2.luksmanager
Android Market Web: https://market.android.com/details?id=com.n...is2.luksmanager
Download:
LUKS_Manager_2.4.apk
LUKS_Manager_2.3.apk(810.1 KB)
Post has been editedNetstranger - 15.10.12, 09:41
Version: 2.4
Last update of the program in the header:24.05.2012
 |
For the operation of the program requires root user rights.
Description:
LUKS Manager encrypts virtual folder on the fly using AES (by default).
With this program you can create, delete, mount and unmount disks dynamically.
This package contains (untranslatable =)):
A statically compiled and stripped version of cryptsetup for the ARM using the tools provided by the Guardianproject.
A statically compiled and stripped version of mkdosfs from dosfstools package for the ARM7.
A bash shell script called "luks" that does volume management.
And a native java app that provides a GUI interface to the luks script, a basic file explorer and simple text editor.
To take full advantage of the program, you must have:
- Root access
- Have a kernel that supports secure dm-crypt modes (CONFIG_DM_CRYPT) and loopback
- Busybox
- Superuser
no program is not redistributed. It creates a file on a flash drive with the extension*** .vol size specified at creation of the virtual folders. And it keeps it all the Old encrypted. But she had a program, a file that installs as a virtual disk, it becomes available as / mnt / sdcard / *** (Where *** file name *** .vol)
You open a file from your computer?
FreeOTFE
Software for Windows, which allows you to work directly with a computer file*** .vol.
Push:
It is a copy of a similar program for Windows - TrueCrypt, estesstvenno with simpler functionality, but the idea is similar.
In spite of statements to the effect that the program is not on most runoff firmware on my Samsung Galaxy S II in the sink and the drain firmware kernel as root with the full functionality of the program is running.
What is TrueCrypt
TrueCrypt - a computer program for encryption "on the flyВ» (On-the-fly encryption) for 32- and Microsoft Windows NT 5 families of 64-bit operating systems and newer (GUI-interface), Linux and Mac OS X. It allows you to create virtual encrypted logical drive, which is stored as a file. Use can also be completely TrueCrypt encrypt partition hard disk or other storage medium such as a floppy disk or USB flash memory. All stored data is fully encrypted TrueCrypt volume, including file names and directories. Mounted TrueCrypt volume similar to the usual logical drive, so you can work with it using ordinary tools check and defragmentation of the file system.
Developer: Nemesis] [
Homepage: http://nemesis2.qx.net/
Android Market: market: // search / q = pname:? com.nemesis2.luksmanager
Android Market Web: https://market.android.com/details?id=com.n...is2.luksmanager
Additional Information
Russian interface: Not
Download:
LUKS_Manager_2.4.apk
Past versions
LUKS_Manager_2.3.apk(810.1 KB)Post has been editedNetstranger - 15.10.12, 09:41
List of changes
Version 2.3:
Major rewrite to the luks shell script and GUI app to support user defined volume locations.
Encryption cipher and keysize are now user definable. (Kernel support required)
Moved storage of volume information from /mnt/sdcard/luks/.data to /data/data/com.nemesis2.luksmanager/.data
Prompts to upgrade if loop device files are found in SDCard .data directory.
Removed top level restriction on file explorer activity.
Default file system changed from EXT4 to EXT2.
FAT file system support now enabled by default.
Added volume mount and unmount desktop shortcuts.
Added notification when volumes are mounted. (Can be toggled off in preferences)
Added landscape support to the main and volume edit activities.
Added basic SDcard support to install binaries routine.
(Fixes java.lang.NullPointerException on binary install.)
Added toggle to disable binary hash checks on startup. This enables
customized luks scripts and / or binaries.
Small fix to application initialization. (Hopefully fixes odd reboot
issue on some devices)
Attempts to unmount volumes on ACTION_SHUTDOWN and MEDIA_EJECT broadcasts.
Additional checks and error handling if no volumes exist.
Additional error handling in luks script during volume mounting and creation.
Added required BusyBox applet checks on startup.
About Dialog additions / changes.
Small text changes (formatting and typo fixes).
Post has been editedNetstranger - 11.11.11, 12:04
Version 2.3:
Major rewrite to the luks shell script and GUI app to support user defined volume locations.
Encryption cipher and keysize are now user definable. (Kernel support required)
Moved storage of volume information from /mnt/sdcard/luks/.data to /data/data/com.nemesis2.luksmanager/.data
Prompts to upgrade if loop device files are found in SDCard .data directory.
Removed top level restriction on file explorer activity.
Default file system changed from EXT4 to EXT2.
FAT file system support now enabled by default.
Added volume mount and unmount desktop shortcuts.
Added notification when volumes are mounted. (Can be toggled off in preferences)
Added landscape support to the main and volume edit activities.
Added basic SDcard support to install binaries routine.
(Fixes java.lang.NullPointerException on binary install.)
Added toggle to disable binary hash checks on startup. This enables
customized luks scripts and / or binaries.
Small fix to application initialization. (Hopefully fixes odd reboot
issue on some devices)
Attempts to unmount volumes on ACTION_SHUTDOWN and MEDIA_EJECT broadcasts.
Additional checks and error handling if no volumes exist.
Additional error handling in luks script during volume mounting and creation.
Added required BusyBox applet checks on startup.
About Dialog additions / changes.
Small text changes (formatting and typo fixes).
Cheyndzhlogi previous versions
Version 2.2:
Recompiled lm.crypsetup binary under android-ndk-r6b.
Hopefully this will stop segfaults on various devices.
Version 2.1:
Added widget:
When volumes are mounted the widget will turn red and display the number of currently mounted volumes.
A single touch unmounts all volumes.
Rewrote luks script and internal routines to use busybox all the time to avoid toolbox / busybox symlink conflicts.
Added the ability to password protect the create / remove buttons, volume properties and preferences dialog.
Improved error handling in luks script on mount.
Added additional scripts: pre-mount and pre-unmount.
Added volume management Activity.
Volume mount points are now user defineable.
The volumes loopback device is now user definable.
Added an internal file editor (to edit bash scripts).
(Editor can be used outside of LUKS Manager to edit files).
Fixed Force Close when mounting with a blank password.
Version 2.0:
Added Preferences Activity.
Now allows FAT formatted volumes.
(Works w / FreeOTFE on windows)
Improved error handling / cleanup on failed volume creation.
Added lm.mkdosfs binary to assets.
The lm.mkdosfs binary is sha1 hashed and replaced if out-dated or changed.
Remove Binaries nows includes the lm.mkdosfs binary.
Added additional menu options to Activities.
Increased debug logging and added system probe.
(Do not enable for normal usage!)
Added option to launch Explorer on volume mount.
Redirected stderr to stdout using redirectErrorStream.
Added validation checks to volume creation. (Non-blank, sanitize filename).
Moved to dp units instead of pixels for display scaling.
Fixed a few items that needed to be .destroyed (oops).
SD Card path fix (typo fix).
File Explorer now saves / recalls list view position on directory changes and when opening files.
About Dialog updates.
Added run script on mount / unmount:<volume>.mount.sh and<volume>.unmount.sh
Added su / root check on startup.
Version 1.9:
Renamed cryptsetup to lm.cryptsetup to avoid overwriting pre-existing copies.
LUKS script will use cryptsetup if it exists, solves Samsung Galaxy S2 issues.
(Users will need to manually restore the cryptsetup binary if it was overwritten!)
Added sanity checks to File Explorer. (Path / mnt / sdcard must exist)
File Explorer now saves and restores path on rotation change.
Moved about html to assets file instead of an inline string.
Version 1.8:
Removed Internet Access Permission.
The cryptsetup binary is no longer UPX compressed in an attempt to improve compatibility.
The cryptsetup and luks binaries are now sha1 hashed and replaced if outdated or changed.
"Unmount All" has been moved to an AsyncTask.
When mounted all volumes will get chmod 777 applied recursively to avoid file permission issues.
Numerous improvements and changes to the internal file explorer.
Slight wording changes to activity titles and About Dialog.
Added change log to About Dialog.
Version 1.7:
Added file explorer
Updated the About Dialog
First Market Release
Version 1.6:
Updated and optimized the icon and background images
Updated the About Dialog
Updated failure logging to syslog
Version 1.5:
Now quotes passwords (oops)
Spaces in volume names are converted to underscores: _
About dialog updated
Version 1.4:
Code refactoring
Added about / homepage menu items
Added "Remove Binaries" to remove / system / bin files: luks and cryptsetup
Added explore menu option to explore to volume location (requires Astro Filemanager)
Added background
Version 1.3:
Moved binaries into apk and added extractor / binary installer
Version 1.2:
First public release
Recompiled lm.crypsetup binary under android-ndk-r6b.
Hopefully this will stop segfaults on various devices.
Version 2.1:
Added widget:
When volumes are mounted the widget will turn red and display the number of currently mounted volumes.
A single touch unmounts all volumes.
Rewrote luks script and internal routines to use busybox all the time to avoid toolbox / busybox symlink conflicts.
Added the ability to password protect the create / remove buttons, volume properties and preferences dialog.
Improved error handling in luks script on mount.
Added additional scripts: pre-mount and pre-unmount.
Added volume management Activity.
Volume mount points are now user defineable.
The volumes loopback device is now user definable.
Added an internal file editor (to edit bash scripts).
(Editor can be used outside of LUKS Manager to edit files).
Fixed Force Close when mounting with a blank password.
Version 2.0:
Added Preferences Activity.
Now allows FAT formatted volumes.
(Works w / FreeOTFE on windows)
Improved error handling / cleanup on failed volume creation.
Added lm.mkdosfs binary to assets.
The lm.mkdosfs binary is sha1 hashed and replaced if out-dated or changed.
Remove Binaries nows includes the lm.mkdosfs binary.
Added additional menu options to Activities.
Increased debug logging and added system probe.
(Do not enable for normal usage!)
Added option to launch Explorer on volume mount.
Redirected stderr to stdout using redirectErrorStream.
Added validation checks to volume creation. (Non-blank, sanitize filename).
Moved to dp units instead of pixels for display scaling.
Fixed a few items that needed to be .destroyed (oops).
SD Card path fix (typo fix).
File Explorer now saves / recalls list view position on directory changes and when opening files.
About Dialog updates.
Added run script on mount / unmount:<volume>.mount.sh and<volume>.unmount.sh
Added su / root check on startup.
Version 1.9:
Renamed cryptsetup to lm.cryptsetup to avoid overwriting pre-existing copies.
LUKS script will use cryptsetup if it exists, solves Samsung Galaxy S2 issues.
(Users will need to manually restore the cryptsetup binary if it was overwritten!)
Added sanity checks to File Explorer. (Path / mnt / sdcard must exist)
File Explorer now saves and restores path on rotation change.
Moved about html to assets file instead of an inline string.
Version 1.8:
Removed Internet Access Permission.
The cryptsetup binary is no longer UPX compressed in an attempt to improve compatibility.
The cryptsetup and luks binaries are now sha1 hashed and replaced if outdated or changed.
"Unmount All" has been moved to an AsyncTask.
When mounted all volumes will get chmod 777 applied recursively to avoid file permission issues.
Numerous improvements and changes to the internal file explorer.
Slight wording changes to activity titles and About Dialog.
Added change log to About Dialog.
Version 1.7:
Added file explorer
Updated the About Dialog
First Market Release
Version 1.6:
Updated and optimized the icon and background images
Updated the About Dialog
Updated failure logging to syslog
Version 1.5:
Now quotes passwords (oops)
Spaces in volume names are converted to underscores: _
About dialog updated
Version 1.4:
Code refactoring
Added about / homepage menu items
Added "Remove Binaries" to remove / system / bin files: luks and cryptsetup
Added explore menu option to explore to volume location (requires Astro Filemanager)
Added background
Version 1.3:
Moved binaries into apk and added extractor / binary installer
Version 1.2:
First public release
Post has been editedNetstranger - 11.11.11, 12:04
Ie it repartition internal memory (or flash drive) and makes a hidden partition that fully encrypts? Or something I did not catch up?
Posted 11-11-2011, 13:14:
I looked at wikipedia
The cap would be, but it is not clear to everyone is: 3
Posted 11-11-2011, 13:14:
I looked at wikipedia
TrueCrypt - a computer program for encryption "on the flyВ» (On-the-fly encryption) for 32- and Microsoft Windows NT 5 families of 64-bit operating systems and newer (GUI-interface), Linux and Mac OS X.It lets you create a virtual encrypted logical drive, which is stored as a file. Use can also be completely TrueCrypt encrypt partition hard disk or other storage medium such as a floppy disk or USB flash memory. All stored data is fully encrypted TrueCrypt volume, including file names and directories. Mounted TrueCrypt volume similar to the usual logical drive, so you can work with it using ordinary tools check and defragmentation of the file system.
The cap would be, but it is not clear to everyone is: 3
Niter43,
thanks, he added.
No, no it does not redistribute. It creates a file on a flash drive with the extension ***. Vol size specified when creating virtual folder. And it keeps it all the Old encrypted. But she had a program, a file that installs as a virtual disk, it becomes available as / mnt / sdcard / *** (where *** filename ***. Vol)
thanks, he added.
No, no it does not redistribute. It creates a file on a flash drive with the extension ***. Vol size specified when creating virtual folder. And it keeps it all the Old encrypted. But she had a program, a file that installs as a virtual disk, it becomes available as / mnt / sdcard / *** (where *** filename ***. Vol)
questions:
1. The mount is on the commissioning resp. Teams from the program or have avtozapros after loading devices?
2. The behavior of the connection of yusb? - as seen from dekstopov After entering the password (mount the file system devaysa)?
3. The speed of access?
4. CPU load when the encrypted volume operations?
And in general, what kind of crap - the linux kernel since time immemorial supports transparent encryption built-in. In android still can not be the issue to establish regular means.
to access via wi-fi, I think, it is seen as a mounted directory.
Post has been editedmemfis - 11.11.11, 19:12
1. The mount is on the commissioning resp. Teams from the program or have avtozapros after loading devices?
2. The behavior of the connection of yusb? - as seen from dekstopov After entering the password (mount the file system devaysa)?
3. The speed of access?
4. CPU load when the encrypted volume operations?
And in general, what kind of crap - the linux kernel since time immemorial supports transparent encryption built-in. In android still can not be the issue to establish regular means.
to access via wi-fi, I think, it is seen as a mounted directory.
Post has been editedmemfis - 11.11.11, 19:12
memfis @ 11.11.2011, 20:11
1. The mount is on the commissioning resp. Teams from the program or have avtozapros after loading devices?
2. The behavior of the connection of yusb? - as seen from dekstopov After entering the password (mount the file system devaysa)?
3. The speed of access?
4. CPU load when the encrypted volume operations?
And in general, what kind of crap - the linux kernel since time immemorial supports transparent encryption built-in. In android still can not be the issue to establish regular means.
2. The behavior of the connection of yusb? - as seen from dekstopov After entering the password (mount the file system devaysa)?
3. The speed of access?
4. CPU load when the encrypted volume operations?
And in general, what kind of crap - the linux kernel since time immemorial supports transparent encryption built-in. In android still can not be the issue to establish regular means.
1. Autoplay is, but only a program. We'll have to go into it and mount push button and enter the password
2. When connected by USB of going avtodismaunting.
3. The speed of access, according to developers, any fraction of a second is not different from the speed of access to the file which is not in an encrypted disk
4. did not measure.
Well, that's such crap, obviously standard means it will hit the security that Google is not allowed ...
In general, the site has developed a website where there is a forum, where he was very active talks with the users of the program and manages noticed bugs. So if you have something to say and to offer concrete. Please refer to and you and all will be better if the program will be popular and will support a variety of devices and features =)
Posted 12-11-2011, 14:55:
memfis @ 11.11.2011, 20:11
to access via wi-fi, I think, it is seen as a mounted directory.
Yes exactly
Another remarked that in the MTP connection is pre-mounted, is available for reading and writing with the company! Very comfortably.
To take full advantage of the program, you must have:
Root access
Have a kernel that supports secure dm-crypt modes (CONFIG_DM_CRYPT) and loopback
Busybox
Superuser
Root access
Have a kernel that supports secure dm-crypt modes (CONFIG_DM_CRYPT) and loopback
Busybox
Superuser
:-):-)
Smartphone
Fingers.
:-)
Post has been editedcontradictor - 24.11.11, 17:31
Put. Creates and mounts a disk, but to work with the content "on the fly" does not work - probably not enough rights applications. Those. move files to the disk I can (only Ruth eksplrerom), and open the file directly from a disk of any program - no, although the file is copied from the disk to read perfectly.
Anything you can do about it?
Anything you can do about it?
I think it is necessary to pass on the forum program and there to describe the device, the firmware and the problem. I have a case, but I can run any program, although sometimes when I upload feature to them did not have access rights, until you do remaunt ...
The program requires something from the root. What is it, how to do it and whether it is dangerous for the PDA?
Netstranger , Thanks for the tip. Indeed, after remounting disk files viewed and edited. The only condition - the file system should only be ext2 (phone Samsung Galxy Note).
fly2
Look in the header firmware for your phone, how to get Ruth.
fly2
Look in the header firmware for your phone, how to get Ruth.
I do not quite understand the impossibility of access to the file after he was thrown into a folder that is mounted under the container until dismantled / mounted container again.
This is a feature or a bug is?
This is a feature or a bug is?
Tell me, please, what could be. After watching several video files from the mounted container, prog rigidly locked - it is not possible to unmount the container can not be removed (the folder is), you can not get out of the Programs in - it hangs in treei says there are mounted container. In general, until the Restart body. Maybe someone knows a similar prog? Thank.
As far as I understand, unfortunately, there is a moment when what the program leaves a trace after using the file, and the system does not unmount a while. Not sure what the best option to reboot out of the situation, as you can break the file system or the file itself. You just have to wait and every half an hour to try, or to forget it himself then he let go ... in the forum poster has already been written about it. Solutions as there are none, it features ext
Indeed, after remounting disk files viewed and edited. The only condition - the file system should only be ext2 (phone Samsung Galxy Note).
A similar problem on the same device. You can mount disks with FAT and EXT2, but the normal operation of any program with just ext2. FAT files can be manipulated only by root explorer, but can not be opened in other programs. A ext2 does not support any windows (from the box) or OTFE Explorer.
More mounts to the European coding - Russian file names are converted to question.
At the office. forum thereon this issue topic
Post has been editedOoma - 18.02.12, 21:18
Ooma @ 18.02.2012, 22:12
A ext2 does not support any windows (from the box) or OTFE Explorer
Mount ext2 drive on the device, run the samba-service on the device and then easily work from windows with the contents of the disc.
Ooma @ 18.02.2012, 22:12
More mounts to the European coding - Russian file names are converted to question
I have no such problem
©savagemessiahzine.com2005-2020 All rights reserved.
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement