Talk:FileVault

message: This page seems somewhat outdated. Sparse bundles could be mentioned . Also, are there any cryptographic enhancements in Leopard?  —Preceding unsigned comment added by 81.191.62.46 (talk) 20:14, 20 November 2007 (UTC)
thread_title: Update

message: Perhaps VileFault should be mentioned? --SakJur (talk) 14:44, 20 February 2011 (UTC)
thread_title:  VileFault 

message: It would appear that the second, third and fourth paragraphs of this section (regarding FileVault and its encryption algorithms and use of recovery keys) are original research, or at the very least, make a lot of points without any citations to back up the information presented.  It would be useful to have supporting citations for these sections to bolster the veracity of what is being said here. Scaredpoet (talk) 21:23, 14 September 2011 (UTC)
replies: text: Agreed, this should be removed until it has been rectified- at the very least it is inaccurate, and written in a personal mannor 49.196.40.75 (talk) 07:38, 2 February 2012 (UTC)
thread_title:  Criticisms/Security: Original Research? 

message: The fourth paragraph uses editorial language, such as "glaring" and "unbearably long," which is not sourced and adds little to the article.
:I've edited the section to separate out the 1st generation issues and remove editorial terms.--agr (talk) 19:52, 2 November 2011 (UTC)
thread_title:  Criticisms/Security: NPOV 

message: In light of the following links, I feel the entirety of this section is wrong and should be revised: 
http://csrc.nist.gov/groups/STM/cavp/documents/aes/XTSVS.pdf
http://axelkenzo.ru/downloads/1619-2007-NIST-Submission.pdf
http://csrc.nist.gov/publications/nistpubs/800-38E/nist-sp-800-38E.pdf
I.e., the appellation "XTS- AES 128 encryption" refers to a tweakable bloc cypher, optimized for sector-based storages. The number "128" refers to the block size, not the key size! FileVault should still use a 256bit encryption key. (I currently have no confirmation of this, other than what is discussed in the aforementioned references.)  — Preceding unsigned comment added by Trimtabo (talk • contribs) 20:19, 23 November 2011 (UTC)
replies: text: You are right, Apple mixes up block size and key size themselves here here (for Panther) and here (for Mountain Lion) but they are correct here. I added a reference to the article.2pem (talk) 17:55, 21 January 2013 (UTC)
thread_title:  Criticisms 

message: Subsection added. 
For selected points: detail, with photographic evidence, is within an answer in Ask Different. Readers may treat this as complementary to Apple's technical white paper. The up-votes signify confidence from external sources, but probably not enough to treat the material as encyclopaedic for Wikipedia. 
Grahamperrin (talk) 06:57, 5 September 2012 (UTC)
thread_title:  Starting the OS with FileVault 2 without a user account 

message: The recovery key is not encoded in base32, which only includes [A-Z] and [2-7] according to base32. The referenced paper is wrong on this. See for example  and  which includes non-base32 character 8 and 9. If somebody knows what encoding this is, please add it to the article. 2pem (talk) 11:01, 9 February 2013 (UTC)
thread_title:  Recovery key not encoded base32 

message: Hello fellow Wikipedians,
I have just modified one external link on FileVault. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20080514160137/http://citp.princeton.edu.nyud.net/pub/coldboot.pdf to http://citp.princeton.edu.nyud.net/pub/coldboot.pdf
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 13:20, 31 December 2016 (UTC)
thread_title:  External links modified