You can use
openssl dgst -sha256 <file>
Tested on LibreSSL 2.6.4 on macOS 10.14 (Mojave).
Prior to Mojave you can use openssl sha -sha256 <file> or openssl sha256 <file>.
To check command line options for the openssl sha command: openssl sha -help.
Copy the mpkg from inside the downloaded disk image onto your Desktop.
Right click the mpkg file and choose Show Package Contents, then open the Contents folder.
Open distribution.dist with a text editor.
Remove lines 13 to 18.
Save the file and open the mpkg normally.
OS X ships with a shasum command.
> which shasum
You can use:
> shasum -a 256 <file>
> shasum --help
Usage: shasum [OPTION]... [FILE]...
Print or check SHA checksums.
With no FILE, or when FILE is -, read standard input.
-a, --algorithm 1 (default), 224, 256, 384, 512, 512224, 512256
-b, --binary ...
Open up the Terminal and enter the command:
diskutil cs list
Or with APFS starting with 10.13
diskutil apfs list
With APFS the FileVault setup utility also shows health and this status:
You will see an output listing at least one Logical Volume Group, with a Logical Volume Family and Logical Volume nested below.
There is be a ...
No, you aren't doing anything wrong. Apple doesn't allow you to paste into certain secure dialog boxes. It's a feature, not a bug. (It makes a brute force hack of the dialog box more difficult.)
You can paste the password into the command line if you mount the secure image using hdiutil.
Open Terminal and type:
hdiutil attach /path/to/imagefile -...
22 hours is very long indeed. I have encrypted a 1TB drive in less time before.
The encryption is handled by a "live background process". "This
process continues seamlessly across reboots. The logical volume
remains usable at all times."
from man page > diskutil > encryptVolume
Maybe this daemon hangs or simply halted because the drive is not ...
You want to run diskutil coreStorage unlockVolume <UUID>, where the UUID is the Logical Volume UUID associated with your encrypted disk, /dev/disk3. You can get the lvUUID by running diskutil cs list in the terminal and looking for the output related to /dev/disk3. The identifier is a long string that would look something like this 'B807C2A0-577F-...
You could put it in an encrypted disk image.
You can create an encrypted disk image in Disk Utility:
Open Disk Utility.
Go to File > New Image > Blank Image (Cmd+N).
Enter a filename, and choose a location. You can also choose the size of the disk image. Make sure to set Encryption to either 128 or 256 bit AES encryption (256 bit is more secure than 128 ...
On OS X 10.11.1 the output diskutil cs list shows encryption progress as:
+-- Logical Volume Group 19B060CE-52A6-4102-9F3D-E6108BD91316
Name: My harddrive
Size: 499113885696 B (499.1 GB)
Free Space: 18972672 B (19.0 MB)
Just bumped into this issue too, if you change password via
Settings > Users & Groups > Change Password ...
you will be prompted twice, once for the File Vault original password and again for the new account password. However if you change the password via
Settings > Security & Privacy > Change Password ...
both will be updated, noting ...
I wrote a very tiny AppleScript application which allows you to paste passwords even where its not allowed by tricking the system into thinking that you're typing on your keyboard. The downside: it takes space in your Dock.
You can encrypt any (individual) file using OpenSSL through Terminal. This is very useful if you are planning on doing a journal in a Word Document, or even a TextEdit file where it's just one long document. The benefit here is that it's lightening fast as you are only encrypting/decrypting a single file.
So, let's assume that on your Desktop we have your ...
The best thing you can do is creating a new admin user and inspecting the assaulted main user/the system.
Boot to Recovery Mode (hold cmdR while booting).
Unlock and mount the main encrypted volume either with Disk Utility or Terminal:
#list all CoreStorage items
diskutil cs list
#unlock the locked Logical Volume (replace lvUUID by the UUID found above. ...
No, the backups will not be encrypted automatically, but it's very easy to enable for directly attached disks. Just check "Encrypt Backup Disk" in the Time Machine disk selection settings.
If you're backing up to another Mac, you can use Disk Utility on that Mac to erase non-boot drives and put an encrypted partition on them:
It seems strange OS X didn't present you the recovery key. Try:
sudo fdesetup changerecovery -personal
This awesome blog has probably all the info you desire. Look for the section "Managing individual and institutional recovery keys". You can use your Filevault2 password to change the recovery key. And you will have to use an Administrator account.
This is an example workflow to encrypt an USB thumbdrive with HSF+ (Journaled) with diskutil using the command line.
Assuming you start with a MS-DOS formatted USB stick.
Step 1: List all currently mounted disks diskutil list:
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
I understand that you're running into issues, so this is going to be more for others looking for info on this topic. Encrypting non-boot volumes should be a relatively easy process in OS X 10.8.x and later.
To encrypt a non-boot volume:
Right-click on the volume you want to encrypt
Select the Encrypt… command
When prompted, enter a password and (...
i like to do it this way.
while true; do diskutil cs list | grep 'Conversion Progress' ; sleep 30; done
will print out an updated progress every 30 seconds so you can just leave it running and glance over and instantly see where the progress is up to without having to run the command again.
To answer your first question about the keychain and whether you should encrypt backups: the passwords in your keychain are already encrypted, that's why you always have to type a password (by default your login password) to show stored passwords. So there's no immediate need to encrypt.
Of course, you could add Time Machine encryption to provide a further ...
Features (copied from iTunes app store):
PGMail is an app that implements the OpenPGP standard (RFC 4880) and
allows the user to create and manage both public and private (RSA and
DSA) PGP keys and send and receive PGP encrypted messages.
PGP Keys and Messages can be passed to iPGMail several ways:
From the iOS ...
Apple securely transmits and stores the data to the cloud by using secure tokens for authentication - as officially stated in the iCloud security and privacy overview1 and the iCloud design guide2.
Apple also states they they will "never provide encryption keys to any third parties", which of course is not entirely true due to the Patriot Act3.
After a bit of messing about, it turns out that there is a better compromise which doesn't seem to be clearly documented anywhere obvious, so I thought I'd share it here. I don't believe this is a duplicate but I'm happy to see this question closed if I've missed something.
The cost of the solution (which may be unacceptable to some) is that you need to ...
I had a similar problem today. I installed osxfuse and ntfs-3g via Homebrew, but I didn't install the kernel extension. I got a similar error message trying to mount an NTFS drive in RW mode. After installing the osxfuse kernel extension (instructions are available via brew info osxfuse), the error went away. Strangely, it didn't happen the first time I ...
You can also use gpgtools (https://gpgtools.org) it is got all the possible GPG tools you are probably going to need (they also have a gpg plugin for Apple Mail) and adds Services for signing/encrypting/decrypting/etc. to the contextual menu (right-click->Services).
I asked after this while attending WWDC 2015 and was told that the "Encryption Paused" issue was addressed in 10.10.3.
The root cause was a problem with resizing the CoreStorage volume during the encryption process. When the CoreStorage volume was unable to grow, the encryption was paused and could not resume until the resize issue was addressed.
To fix ...
Actually your mac is capable of encrypting that fast (perhaps you're confusing it with encryption+compression).
Your processor has a special Intel AES-NI instruction set, specifically designed to optimize encryption speed. Looking at some performance benchmarks for that processor, the AES test performs at a whopping 8.87 GB/s multi-core and 2.94 GB/s ...
Often a service center need access to the Mac to verify if the problems are solved. You can do a few things.
The most important thing first. Make a backup from all your data before you give your Mac to the service center.
Turn on FileVault. It encrypts the harddisk.
Make a second user and provide these details to the service center so they can test.
Yes, you can do this using the built-in Disk Images of Mac OS X. A disk image (or DMG file) is a file which, when opened, presents itself as a removable Mac OS X volume, similar to a removable hard drive. Many OS X applications are deployed on disk images. If you encrypt your home directory using FileVault, you're creating a spare bundle disk image.
You can ...
John Siracusa's detailed Lion review covers the new FileVault disk encryption feature in great detail:
To summarise, the new system is "volume" based. This means that not all volumes can be or are encrypted. The Lion recovery partition for example is not encrypted. Non Mac ...
The system keychain is stored in /Library/Keychains/System.keychain and the key to unlock it is stored in /var/db/SystemKey (its default file permissions are readable by root only). The location of these files is referenced in the security-checksystem script (from the security_systemkeychain source). It is even possible to test to automatic locking/unlocking ...