425 karma · joined April 20, 2013
VeraCrypt 1.0 was released in May,2013[2]. One year prior.
[1] http://truecrypt.sourceforge.net
[2] https://sourceforge.net/u/yanpas/veracrypt/ci/VeraCrypt_1.0b...
VeraCrypt binary application can unlock TrueCrypt volumes but CAN NOT create them.The application has a setting to default to TrueCrypt volumes and hence if all you do is unlocking your TrueCrypt volumes,you can conveniently use VeraCrypt to unlock your TrueCrypt volumes.
I think it will be better if you switch to VeraCrypt and set this option.Alternative "native linux" tool you could use to manage your TrueCrypt volumes in linux is zuluCrypt[3].
EncFS has its own issues[1] and there are a number of new projects that seeks to replace it and SiriKali[2] is a GUI tool to manage all these newer tools.
[1] https://defuse.ca/audits/encfs.htm
How about Qt's management of QObjects through QObject's parent/child relationship?[1]
1. All the crypto stuff is done by the kernel and hence they are not responsible for it.
2. Most of work that goes into setting up the kernel to manage an encrypted drive is done by a tool called cryptsetup and they are not responsible for it.
3. The part where they are responsible for lives entirely in the root's space and hence they are not susceptible to security issues that arises when trying to cross a privileged user/unprivileged user boundary.
The reason why TrueCrypt/VeraCrypt in windows specifically have so much problems is because they are doing everything themselves.
They have less problems in linux because they delegate user data encryption/decryption to the kernel and they cross normal user privileges to root's privileges using sudo.
Performance of a VeraCrypt volume will degrade only if you use multiple ciphers.
TrueCrypt,VeraCrypt,zuluCrypt,tcplay,cryptsetup among others use this infrastructure to do user data encryption/decryption.
What these project do is parse a volume header on a volume to get crypto properties and then pass them to dm-crypt for it to do everything else.
The difference between a TrueCrypt volume,a VeraCrypt volume and a LUKS volume is in how their crypto properties are stored on the header and dm-crypt is not aware of any of these projects.
Once you know crypto properties of a volume,you can skip all these projects and go straight to dm-crypt and manually create the encryption mapper using dmsetup. All the necessary information about an open encryption mapper looks like below:
[root@ink mtz]# dmsetup --showkeys table
zuluCrypt-500-NAAN-luks.img-2363596225: 0 16384 crypt aes-xts-plain64 afaeef82a6a823e226b0f22289404f1eac5b262b5d1984b7de9328cb571dd3f3 0 7:0 4096 1 allow_discards
[root@ink mtz]#The current UI was not designed recently and hence shouldn't be used against current FOSS UI designers.
I think lack of resources is the primary reason why the UI hasnt changed to reflect what is currently considered hip.
First argument to realloc takes a pointer of type "void star" and you passed in a pointer of type "int star" without casting it and this suggests you did the casts out of habit and i think its time to break the habit :-)
ps: had to write "void star" because the "star" character was not showing up for some reason.
http://pubs.opengroup.org/onlinepubs/7908799/xsh/realloc.htm...
Their biggest difference with a traditional bank is that their "bank" accounts are tied to phone numbers.
Once they have your money,you can do money transactions more or less the same way you do with a debit/credit card.
You can also have your "bank" accounts on these companies tied to a "bank" account from a traditional bank and you can move your money back and forth between them.
I think calling the service "M-Pesa" is misleading since a lot of other people are offering the same service.
Here in Tanzania,
"M-Pesa" is the name for the service offered by vodafone,a mobile communications company.
"Tigo Pesa" is the name for the same service offered by tigo,a mobile communication company.
"Airtel money" is the name for the same service offered by airtel,a mobile communication company.
"EzyPesa" is the name for the same service offered by zantel,a mobile communication company.
For the above reasons,i generally call the service offered by these companies as "a banking service managed by mobile phone companies".
"Sim banking" is the name of the service offered by a "traditional" bank called crdb[1] so a more generalized name that accommodates both traditional banks and cellular network operator banks is in need.
Most traditional banks are also offering the same service.
The only thing they all have in common from the user's perspective is that the services are offered through ussd codes[1] meaning they are not tied to mobile phones and they work with any device that supports ussd codes.
I have an application called ussd-gui[4][3] that i use to manage by money at vodafone "bank" using a mobile broadband modem on my linux system.
[1] http://crdbbank.com/tz/alternative-banking/simbanking.html
[2] https://en.wikipedia.org/wiki/Unstructured_Supplementary_Ser...
[3] https://github.com/mhogomchungu/ussd-gui/blob/master/icons/u...
Look for documentation of header backups and you will see it speaks of only two headers,the header for the outer volume and the header for the hidden volume.
[1] https://www.truecrypt71a.com/documentation/technical-details...
LUKS advantages over TrueCrypt is that it can support up to 8 different passwords and each password security can be fine tuned by a changeable pbkdf2 iteration count that is set per password.
TrueCrypt on-disk format advantages over LUKS is that it can support two volumes(outer one and hidden one) and its header is completely hidden since its encrypted.LUKS volume header is unencrypted and hence visible.
With a LUKS based encrypted volume,its possible to mimic a hidden header on a device through the usage of a "detached header" but this is a property of tools that manage LUKS volumes and not of a LUKS volume on disk-format.It is also possible to mimic a hidden volume through a plain dm-crypt volume at a non zero offset but this is also a property of a tool that manages LUKS volume and not of a LUKS volume format.
When it comes to binary applications,zuluCrypt is better than TrueCrypt because it supports TrueCrypt on-disk format together with other formats and it also supports multiple hidden volumes through the use of plain dm-crypt volumes.
zuluCrypt also supports LUKS volumes with a detached header and this is more or less like TrueCrypt volume that requires a password and a keyfile(the detached header will act as a keyfile in this case).
zuluCrypt also supports plain dm-crypt volumes at a none zero offset and this means it can have more than one "hidden volumes" although it does not offer protection of these hidden volumes.
zuluCrypt[1] is another option if you are on linux.
Its GPL licensed and exists in a lot of distribution's repositories(Will appear in debian and ubuntu repositories shortly)
It supports TrueCrypt volumes,VeraCrypt volumes and LUKS volumes.
Also,access to block devices requires root's privileges by default.
cryptsetup and tcplay works in both linux and dragonfly bsd because dragonfly bsd has the necessary libdevmapper API[4]
[1] https://gitlab.com/cryptsetup/cryptsetup/blob/master/README....
[2] https://github.com/bwalex/tc-play
[3] https://en.wikipedia.org/wiki/Dm-crypt
[4] http://leaf.dragonflybsd.org/mailarchive/kernel/2011-07/msg0...
https://igurublog.wordpress.com/2012/11/05/gnome-et-al-rotti...
I am one of those (lucky??)people who sometimes gain awareness of themselves dreaming and have the ability to control the dream.
Being aware of oneself dreaming and knowing fully well that i can simply get out of it when i choose to simply by waking myself up gives me a sense of peace and control that i have never felt in real life.
lxqt_wallet supports 3 backends: kwallet,libsecret and internal one that gives the behavior i explained above.
Each backend has its pro and cons and the project lets the user pick which one works best for them.
There need to be a general purpose secure storage system that can accommodate users who wish to not have their secrets that are meant to be used by only one application be exposed to all other applications.
In GNOME,the wallet is opened by the login manager and that means all the contents of the wallet are available to all processes run from the logged in user account.
KDE refused to have the above behavior of the login manager opening the wallet and hence after login,there must be atleast one application that will have to open the wallet and then the behavior will be the same as libsecret.
Lots of people who use these two storage systems are not aware of the above.
I dont like the above behavior as i want each application to manage its own private wallet and i created lxqt_wallet[1] to give me the behavior i want.
The project also supports libsecret and KWallet for those who prefer these backends.
In my zuluCrypt project[1],i started with no options because i thought the default options for each supported format was "good enough for everybody" and not long afterwards,the more frequently requested feature was to add more options.
I think more options is good.
I would go with uint64_t
as it documents "ticks" as a variable that can not hold negative values and also doubles its range of positive values.
Its the new shiny thing.
isnt it better to write that as:
const char* response = "HTTP/1.1 200 OK\nContent-Type: text/html\n\nlol"; ?
Having the string in a writable buffer when you have no intention of modifying the string seems like not a very good idea.
Any decent compiler will evaluate "strlen(response)" at compile time and hence there will be no run time penalty here.
"LUKS" stands for "linux unified key setup" and it is an "on-disk format" and its reference implementation is found in cryptsetup[1]
LUKS on-disk format is supported in windows through doxbox[2]
cryptsetup also supports TrueCrypt,the on-disk format.
people usually say "LUKS" when they mean cryptsetup as it makes no difference to them but i think its important to know the difference.
[1] https://gitlab.com/cryptsetup/cryptsetup/wikis/Specification