AACS Keys - A program revealing all AACS Keys needed to decrypt (HD DVD and Blu-ray) - Page 7

arnezami · 15th April 2007, 19:54

Nice

.

Please check if the Bus Key is filled (don't post it) and whether the Volume ID MACs are exactly the same (don't post it).

Also fot Bluray: is the sha-1 hash the correct one? (according to the KenD00's new specs that is)

mrazzido · 15th April 2007, 20:35

Quote:

Originally Posted by arnezami

Nice

.

Please check if the Bus Key is filled (don't post it) and whether the Volume ID MACs are exactly the same (don't post it).

Also fot Bluray: is the sha-1 hash the correct one? (according to the KenD00's new specs that is)

For bluray .

SHA-1 is the correct one !

and Buskey is Filled :-)

PepsiLee2001 · 16th April 2007, 07:31

Quote:

Originally Posted by arnezami

I'm also working on BDAV support. But I have a problem. Maybe somebody else can help me here

.

I have a blu-ray BDAV, but aacskeys can't get any info from it.

message as follow:
C:\aacskeys>aacskeys.exe i v
Error opening Media Key File i:\AACS\MKBROM.AACS

Blu-ray BDAV file structure as follow,
\AACS\MKB_RW.inf
\AACS\AACS_av\CPSUnit00001.cci
\AACS\AACS_av\Unit_Key_RW.inf

Thanks a lot!!!!!!

arnezami · 16th April 2007, 18:23

Quote:

Originally Posted by PepsiLee2001

I have a blu-ray BDAV, but aacskeys can't get any info from it.

message as follow:
C:\aacskeys>aacskeys.exe i v
Error opening Media Key File i:\AACS\MKBROM.AACS

Blu-ray BDAV file structure as follow,
\AACS\MKB_RW.inf
\AACS\AACS_av\CPSUnit00001.cci
\AACS\AACS_av\Unit_Key_RW.inf

Thanks a lot!!!!!!

Because I haven't been able to figure out this problem the program isn't looking for BDAV files yet.

I really need help on this.

arnezami

PepsiLee2001 · 17th April 2007, 02:58

Quote:

Originally Posted by arnezami

Because I haven't been able to figure out this problem the program isn't looking for BDAV files yet.

If any thing I can do, I will do it.
Just let me know how to do.

Boing99 · 17th April 2007, 04:34

Quote:

Originally Posted by arnezami

Ok. I'm quite busy extending/improving aacskeys.

My new version now uses a proper Hk/Hv combination and supports Bus Key calculation (which was quite some work) and because of that it now supports Volume ID MACs (for both BD and HD DVD). It also supports TKF MAC now (for checking if a VUK is correct, which is a HD-DVD-only feature btw). It also outputs the SHA-1 hash of the Title Key File (or CPS Unit Key file for BD according to new specs by KenD00's decrypter).

Since you are being so thorough about it you may also be interested in verifying the various signatures in AACS files, using the AACS public keys. I have not seen them posted anywhere else before, so here they are (in decimal format, the same format used in the AACS specs):

Code:

#define AACS_CC_PUB_X "686795158131444840350934441718292981749606298444"
#define AACS_CC_PUB_Y "667926496774724305600543583224894590551199207"
#define AACS_LA_PUB_X "569519044145899916876682500420440111695939635058"
#define AACS_LA_PUB_Y "111297986001312168148180416490690086062371334695"

Quote:

Originally Posted by arnezami

I'm also working on BDAV support. But I have a problem. Maybe somebody else can help me here

.

I need to extract the Binding Nonce. There is a command for that (which should work after AACS-Auth). The problem is in this command an address needs to be filled: LBA Extend. But I have no idea what to put there... Sure it has to be the same address the Binding Nonce was written to but how do I get this information??

The specs say "For BDRecordable Disc, the Binding Nonce shall be stored in the User Control Data associated with the first logical Sector of the CPS Unit Key File and should be non-zero value.". I assume that "first logical sector" is the same as the "LBA (Logical Block Address) Extent". The term "extent" usually refers to a consecutive range of sectors or blocks. As for how to get this: you have two options: either implement a simple UDF 2.5 reader/handler yourself and get the starting block number of the CPS Unit Key file right out of the directory structure. Or try to get it from the OS, in an OS-specific way using some file/directory query function. I don't know how to do this for Windows, but others may be able to help with that, or just google for it.

arnezami · 17th April 2007, 06:20

Quote:

Originally Posted by Boing99

Since you are being so thorough about it you may also be interested in verifying the various signatures in AACS files, using the AACS public keys. I have not seen them posted anywhere else before, so here they are (in decimal format, the same format used in the AACS specs):

Code:

#define AACS_CC_PUB_X "686795158131444840350934441718292981749606298444"
#define AACS_CC_PUB_Y "667926496774724305600543583224894590551199207"
#define AACS_LA_PUB_X "569519044145899916876682500420440111695939635058"
#define AACS_LA_PUB_Y "111297986001312168148180416490690086062371334695"

Yeah I might aswell do that too. Cool find btw.

Where did you get that? I haven't really spend much time searching for it but couldn't find it either (in mem). Must have missed it. Although I guessed its in every device and player so somebody would find it sooner or later. Changing this inside a Software Player would also allow us to let the Player do pretty much everything we want: thus potentially revealing all (and even still unused) keys inside the player (like all Device Keys and/or Sequence Keys).

Quote:

Originally Posted by Boing99

The specs say "For BDRecordable Disc, the Binding Nonce shall be stored in the User Control Data associated with the first logical Sector of the CPS Unit Key File and should be non-zero value.". I assume that "first logical sector" is the same as the "LBA (Logical Block Address) Extent". The term "extent" usually refers to a consecutive range of sectors or blocks. As for how to get this: you have two options: either implement a simple UDF 2.5 reader/handler yourself and get the starting block number of the CPS Unit Key file right out of the directory structure. Or try to get it from the OS, in an OS-specific way using some file/directory query function. I don't know how to do this for Windows, but others may be able to help with that, or just google for it.

Yeah. The problem is I haven't got a BluRay player/burner AND I haven't got BDAV discs. So this makes it pretty much impossible for me to test things. Maybe I will make a small proggy so somebody that does have the above can try out different addresses and see what happens.

But only after I finished the implementation of automatic Device/Processing Key detection: this is gonna be a very cool and powerful feature

and will be very useful for future attempts by "Key Finders" (aka hackers) to check if they have found a Key among (tons of) possible keys.

Regards,

arnezami

19th April 2007, 03:27

Just incase anyone didn't know.. AnyDVD HD 6.1.3.6 is now capable of decrypting Blu-Ray titles from mounted .iso images created with "dd" on the PS3 in Linux.

HyperHacker · 20th April 2007, 01:09

There was a thread about that. It's just using a database of keys.

20th April 2007, 16:12

I don't think it's using a database of keys.

The discs I tried it on was Casino Royale (AUS) which is different to EUR/GER and USA, and also Sky High (AUS).

No database i've seen includes keys for these discs.

FoxDisc · 20th April 2007, 18:40

Quote:

Originally Posted by MickJT

I don't think it's using a database of keys.
The discs I tried it on was Casino Royale (AUS) which is different to EUR/GER and USA, and also Sky High (AUS).
No database i've seen includes keys for these discs.

You didn't read the thread HyperHacker sent you to. It explains that AnyDVD doesn't need its database if you use it with an original disc, and you won't have ever seen their database. AnyDVD uses its own database as a backup, which lets it decrypt files mounted as an ISO or just copied off the original disc.

arnezami · 21st April 2007, 12:51

I'm really busy implementing stuff into aacskeys.

Here is something to test:

http://www.sendspace.com/file/f0lh56

Its now supports automatic Device/Processing Key detection

.

But it needs to be tested. If anyone has Device Keys (from our "old" Software Players which are going to be revoked anyway so you can release them if you like) then please test them and see if they are recognized as such.

In the file "ProcessingDeviceKeysSimple.txt" you can simply throw your Device/Processing Keys. If they work on a disc then aacskeys should be able to recognize that.

Here is what I put in for testing:

Code:

DEADBEAFDEADBEAFDEADBEAFDEADBEAF
DEEDDEEDDEEDDEEDDEEDDEEDDEEDDEED
12345678123456781234567812345678
87654321876543218765432187654321
AA856A1BA814AB99FFDEBA6AEFBE1C04
DEADBEAFDEADBEAFDEADBEAFDEADBEAF
DEEDDEEDDEEDDEEDDEEDDEEDDEEDDEED
12345678123456781234567812345678
87654321876543218765432187654321
09F911029D74E35BD84156C5635688C0
DEADBEAFDEADBEAFDEADBEAFDEADBEAF
DEEDDEEDDEEDDEEDDEEDDEEDDEEDDEED
12345678123456781234567812345678
87654321876543218765432187654321

Since it starts trying keys from the top it will detect the Device Key (released by ATARI Vampire) first (the one starting with AA85). If you remove or change that key it will find the Processing Key. If you remove or change that one too it doesn't find any working key and aborts.

In order for this to work on a new disc you need to find possible Keys (of course getting these is the hard part) and use aacskeys with these Keys on the new disc (or alternatively : copy the AACS directory from your new disc to a root dir of one of your HDDs and let aacskeys operate on that drive letter. Or mount these files/disc as an ISO. This will prevent wear and tear on your disc/drive).

More will follow (like input of volume id/HPK) but this I had to get out so somebody can (hopefully) confirm its working.

arnezami

PS. As for speed: you will notice it takes quite a lot of time to test many keys. The current version isn't build for speed. There are several ways to speed it up (eg precomputation due to similarity in shapes of subsets) and shortcuts (like only trying a few C-values and ignoring others). In other words: you can't scan (full) memdumps with this program.

awhitehead · 23rd April 2007, 05:40

No worky

Older version of aacskeys happily works with my current test disk (Total Recall):

Code:

C:\aacs>.\aacskeys.exe  i v
Processing key:               09F911029D74E35BD84156C5635688C0
Encrypted C-value:            B7422BF12E30C7308B66B877E376058D
Corresponding uv:             00000001

Decrypted C-value:            50D497E0D724A42B08E010619D3B6DD7
Media key:                    50D497E0D724A42B08E010619D3B6DD6

Encrypted verification data:  9ED2A5E1116D544F0338E74E8A4F9A0B
Decr verif data should be:    0123456789ABCDEF
Decrypted verification data:  0123456789ABCDEF07D27BEAF4FBDC72

AGID:                         00

Host certificate from:        Power DVD 7.1
Host certificate (Hcert):     0200005CFFFF0000000C00006E3DEB679B9A16AD
                              FAA8E30878767BA6EB2A9B415385AD1181B4446C
                              31E9A5DD2AB808B364FF15885BAC490964318C9B
                              F8029FCF76F688A54FBDA03F6D9332EF04E5A613
                              12DA85880A4D9CBB79D8602E
Host Private Key (Hpriv):     4737676058D7029452514F0AB186DC4CCA8C578F
Host Nonce (Hn):              2923BE84E16CD6AE529049F1F1BBE9EBB3A6DB3C

Drive certificate (Dcert):    ########################################
                              ########################################
                              ########################################
                              ########################################
                              ########################
Drive Nonce (Dn):             ########################################

Drive key point (Dv):         ########################################
                              ########################################
Drive key signature (Dsig):   ########################################
                              ########################################

Host key (Hk):                0000000000000000000000000000000000000000
Host key point (Hv):          8E9B0E3CF41FA7DA3A829F604122EA4ED5261AA4
                              7570CE0BB9061A66FAF92C4A7D98ACC171CBF19B
Host key signature (Hsig):    ########################################
                              ########################################

Bus key (BK):                 ################################

Volume ID:                    4000922B7BCD3536AC5CD7FA41FD0000
Voluem ID MAC:                ################################

Volume Unique Key:            F51EAABB7CD2E2ED05A6BE00126D4AA6
Title Key File MAC:           232F941592CBE19FF50865356153DEA7

Encrypted Title Key 1:        8D2F4E37CF6525FA88877BFFF77F5F50
Encrypted Title Key 2:        032609ADE9C4FB6B9C8F19E1BF3A8056
Encrypted Title Key 3:        25D499F134D0F546F346814C0E142D6C
Encrypted Title Key 4:        8C03F7420B47ECF1C6A2BEE7174E416E

[64 encrypted and decrypted title keys snipped]

With the newer version of aacskeys I get the following:
(ProcessingDeviceKeysSimpletxt as shipped)

Code:

C:\aacs\aacskeys.new>.\aacskeys.exe  i v

Could not find a Processing Key or Device Key resulting in the Media Key.

Aborting...

C:\aacs\aacskeys.new>

If I go ahead and edit ProcessingDeviceKeysSimple.txt to just contain a single line:
09F911029D74E35BD84156C5635688C0
(Processing key that works with older version of aacskeys and this disk), I still get the same error message.

Hope this helps.

System in question is Windows XP, Pan European release (?), English locale. Xbox 360 HD-DVD drive connected over USB.

Are there any other tests I can run?

arnezami · 23rd April 2007, 06:10

Quote:

Originally Posted by awhitehead

No worky

Older version of aacskeys happily works with my current test disk (Total Recall):

Code:

C:\aacs>.\aacskeys.exe  i v
Processing key:               09F911029D74E35BD84156C5635688C0
Encrypted C-value:            B7422BF12E30C7308B66B877E376058D
Corresponding uv:             00000001

Decrypted C-value:            50D497E0D724A42B08E010619D3B6DD7
Media key:                    50D497E0D724A42B08E010619D3B6DD6

Encrypted verification data:  9ED2A5E1116D544F0338E74E8A4F9A0B
Decr verif data should be:    0123456789ABCDEF
Decrypted verification data:  0123456789ABCDEF07D27BEAF4FBDC72

AGID:                         00

Host certificate from:        Power DVD 7.1
Host certificate (Hcert):     0200005CFFFF0000000C00006E3DEB679B9A16AD
                              FAA8E30878767BA6EB2A9B415385AD1181B4446C
                              31E9A5DD2AB808B364FF15885BAC490964318C9B
                              F8029FCF76F688A54FBDA03F6D9332EF04E5A613
                              12DA85880A4D9CBB79D8602E
Host Private Key (Hpriv):     4737676058D7029452514F0AB186DC4CCA8C578F
Host Nonce (Hn):              2923BE84E16CD6AE529049F1F1BBE9EBB3A6DB3C

Drive certificate (Dcert):    ########################################
                              ########################################
                              ########################################
                              ########################################
                              ########################
Drive Nonce (Dn):             ########################################

Drive key point (Dv):         ########################################
                              ########################################
Drive key signature (Dsig):   ########################################
                              ########################################

Host key (Hk):                0000000000000000000000000000000000000000
Host key point (Hv):          8E9B0E3CF41FA7DA3A829F604122EA4ED5261AA4
                              7570CE0BB9061A66FAF92C4A7D98ACC171CBF19B
Host key signature (Hsig):    ########################################
                              ########################################

Bus key (BK):                 ################################

Volume ID:                    4000922B7BCD3536AC5CD7FA41FD0000
Voluem ID MAC:                ################################

Volume Unique Key:            F51EAABB7CD2E2ED05A6BE00126D4AA6
Title Key File MAC:           232F941592CBE19FF50865356153DEA7

Encrypted Title Key 1:        8D2F4E37CF6525FA88877BFFF77F5F50
Encrypted Title Key 2:        032609ADE9C4FB6B9C8F19E1BF3A8056
Encrypted Title Key 3:        25D499F134D0F546F346814C0E142D6C
Encrypted Title Key 4:        8C03F7420B47ECF1C6A2BEE7174E416E

[64 encrypted and decrypted title keys snipped]

With the newer version of aacskeys I get the following:
(ProcessingDeviceKeysSimpletxt as shipped)

Code:

C:\aacs\aacskeys.new>.\aacskeys.exe  i v

Could not find a Processing Key or Device Key resulting in the Media Key.

Aborting...

C:\aacs\aacskeys.new>

If I go ahead and edit ProcessingDeviceKeysSimple.txt to just contain a single line:
09F911029D74E35BD84156C5635688C0
(Processing key that works with older version of aacskeys and this disk), I still get the same error message.

Hope this helps.

System in question is Windows XP, Pan European release (?), English locale. Xbox 360 HD-DVD drive connected over USB.

Are there any other tests I can run?

Ok. Thanks. What happens if you remove the file: ProcessingDeviceKeysSimple.txt altogether? Do you get a different error message? Or does it crash?

Do others have the same problem here? Please test it.

(btw it works fine on my system and I don't see (yet) why it would not work with yours)

arnezami

awhitehead · 23rd April 2007, 06:10

BTW, I have a couple of suggestions for aacskeys....

There are many revisions of it out there by now, so maybe implementing some sort of versioning as maybe the first line of the output would make sense. In the above post I refer to "older" aacskeys, but I have no idea which particular build it is. This would make your life easier with bug reports, etc.

If you add a way of adding comments to ProcessingDeviceKeysSimple.txt (ie lines that will not be processed by the aacskeys, say lines that start with # or ; ), it would probably be useful for key management, etc.

arnezami · 23rd April 2007, 06:16

Quote:

Originally Posted by awhitehead

BTW, I have a couple of suggestions for aacskeys....

There are many revisions of it out there by now, so maybe implementing some sort of versioning as maybe the first line of the output would make sense. In the above post I refer to "older" aacskeys, but I have no idea which particular build it is. This would make your life easier with bug reports, etc.

If you add a way of adding comments to ProcessingDeviceKeysSimple.txt (ie lines that will not be processed by the aacskeys, say lines that start with # or ; ), it would probably be useful for key management, etc.

You're right about the versions. Here is the same new version again (now called v0.2). No changes but the output of the version nr:

http://www.sendspace.com/file/vdnfzt

Please read my previous post. You may have missed it.

arnezami

PS. Regarding the extension of the text file: this is the "Simple" version and is for people thinking they might have found a new key. So they can just throw in possible keys...

arnezami · 23rd April 2007, 06:46

I have made some changes so it gives more info. Hopefully this will clarify where the problem lies:

aacskeys v0.2.2

Please to others too: try this on different discs. Thanks

.

PepsiLee2001 · 23rd April 2007, 08:54

Quote:

Originally Posted by arnezami

I have made some changes so it gives more info. Hopefully this will clarify where the problem lies:
aacskeys v0.2.2
Please to others too: try this on different discs. Thanks

.

Does this version support BDAV disc?

Error message as follow,

Code:

C:\aacskeys_v0.2.2>aacskeys.exe m v
aacskeys v0.2.2

Error opening Media Key File m:\AACS\MKBROM.AACS

arnezami · 23rd April 2007, 18:41

Ok. I now got the automatic Device Key detection working thanks to someone "lending me a hand"

. Thanks. You know who you are

.

I'm still going to (more methodically) check whether its really accurate but it looks very good now.

Screenshot of usage for new aacskeys version:

Anyway. Version 0.2.4 now supports volume id input too. This is going to be very handy when (well technically: if) we find the new Processing Key(s) without having a working HPK yet.

aacskeys v0.2.4

For the other problem (that awhitehead posted): anyone please test this new version (just run it) and post your results

Regards,

arnezami

@PepsiLee2001: no this version doesn't support BDAV yet. Please read my last posts about this.

[edit] Small update: turned on something that wasn't supposed to stay turned off.

PS. If/when the new Processing/Device Key is found and released you can use fetchvid to retrieve the Volume ID of a new disc and then use it as input for aacskeys.

awhitehead · 24th April 2007, 04:24

Quote:

Originally Posted by arnezami

For the other problem (that awhitehead posted): anyone please test this new version (just run it) and post your results

Both 0.2.2 and 0.2.4 work for me now, both without the .txt file, and with it, if it contains a valid device or processing key. 0.2 didn't like the presence of .txt file, but works without it.

Tested with US release of "Syriana"

20th April 2007, 01:09	#129 \| Link
HyperHacker Resident DRM Hater Join Date: Oct 2006 Location: International waters Posts: 242	There was a thread about that. It's just using a database of keys. __________________ Because Moogles pwn.

21st April 2007, 12:51	#132 \| Link
arnezami Registered User Join Date: Sep 2006 Posts: 390	I'm really busy implementing stuff into aacskeys. Here is something to test: http://www.sendspace.com/file/f0lh56 Its now supports automatic Device/Processing Key detection . But it needs to be tested. If anyone has Device Keys (from our "old" Software Players which are going to be revoked anyway so you can release them if you like) then please test them and see if they are recognized as such. In the file "ProcessingDeviceKeysSimple.txt" you can simply throw your Device/Processing Keys. If they work on a disc then aacskeys should be able to recognize that. Here is what I put in for testing: Code: DEADBEAFDEADBEAFDEADBEAFDEADBEAF DEEDDEEDDEEDDEEDDEEDDEEDDEEDDEED 12345678123456781234567812345678 87654321876543218765432187654321 AA856A1BA814AB99FFDEBA6AEFBE1C04 DEADBEAFDEADBEAFDEADBEAFDEADBEAF DEEDDEEDDEEDDEEDDEEDDEEDDEEDDEED 12345678123456781234567812345678 87654321876543218765432187654321 09F911029D74E35BD84156C5635688C0 DEADBEAFDEADBEAFDEADBEAFDEADBEAF DEEDDEEDDEEDDEEDDEEDDEEDDEEDDEED 12345678123456781234567812345678 87654321876543218765432187654321 Since it starts trying keys from the top it will detect the Device Key (released by ATARI Vampire) first (the one starting with AA85). If you remove or change that key it will find the Processing Key. If you remove or change that one too it doesn't find any working key and aborts. In order for this to work on a new disc you need to find possible Keys (of course getting these is the hard part) and use aacskeys with these Keys on the new disc (or alternatively : copy the AACS directory from your new disc to a root dir of one of your HDDs and let aacskeys operate on that drive letter. Or mount these files/disc as an ISO. This will prevent wear and tear on your disc/drive). More will follow (like input of volume id/HPK) but this I had to get out so somebody can (hopefully) confirm its working. arnezami PS. As for speed: you will notice it takes quite a lot of time to test many keys. The current version isn't build for speed. There are several ways to speed it up (eg precomputation due to similarity in shapes of subsets) and shortcuts (like only trying a few C-values and ignoring others). In other words: you can't scan (full) memdumps with this program. Last edited by arnezami; 21st April 2007 at 16:09.

23rd April 2007, 06:46	#137 \| Link
arnezami Registered User Join Date: Sep 2006 Posts: 390	I have made some changes so it gives more info. Hopefully this will clarify where the problem lies: aacskeys v0.2.2 Please to others too: try this on different discs. Thanks . Last edited by arnezami; 23rd April 2007 at 06:55.

23rd April 2007, 18:41	#139 \| Link
arnezami Registered User Join Date: Sep 2006 Posts: 390	Ok. I now got the automatic Device Key detection working thanks to someone "lending me a hand" . Thanks. You know who you are . I'm still going to (more methodically) check whether its really accurate but it looks very good now. Screenshot of usage for new aacskeys version: Anyway. Version 0.2.4 now supports volume id input too. This is going to be very handy when (well technically: if) we find the new Processing Key(s) without having a working HPK yet. aacskeys v0.2.4 For the other problem (that awhitehead posted): anyone please test this new version (just run it) and post your results Regards, arnezami @PepsiLee2001: no this version doesn't support BDAV yet. Please read my last posts about this. [edit] Small update: turned on something that wasn't supposed to stay turned off. PS. If/when the new Processing/Device Key is found and released you can use fetchvid to retrieve the Volume ID of a new disc and then use it as input for aacskeys. Last edited by arnezami; 23rd April 2007 at 21:53.

15th April 2007, 19:54	#121 \| Link
arnezami Registered User Join Date: Sep 2006 Posts: 390	Nice . Please check if the Bus Key is filled (don't post it) and whether the Volume ID MACs are exactly the same (don't post it). Also fot Bluray: is the sha-1 hash the correct one? (according to the KenD00's new specs that is)

19th April 2007, 03:27	#128 \| Link
MickJT Guest Posts: n/a	Just incase anyone didn't know.. AnyDVD HD 6.1.3.6 is now capable of decrypting Blu-Ray titles from mounted .iso images created with "dd" on the PS3 in Linux.

20th April 2007, 16:12	#130 \| Link
MickJT Guest Posts: n/a	I don't think it's using a database of keys. The discs I tried it on was Casino Royale (AUS) which is different to EUR/GER and USA, and also Sky High (AUS). No database i've seen includes keys for these discs.

23rd April 2007, 06:10	#135 \| Link
awhitehead Registered User Join Date: Jan 2007 Location: Tel-Aviv, Israel Posts: 185	BTW, I have a couple of suggestions for aacskeys.... There are many revisions of it out there by now, so maybe implementing some sort of versioning as maybe the first line of the output would make sense. In the above post I refer to "older" aacskeys, but I have no idea which particular build it is. This would make your life easier with bug reports, etc. If you add a way of adding comments to ProcessingDeviceKeysSimple.txt (ie lines that will not be processed by the aacskeys, say lines that start with # or ; ), it would probably be useful for key management, etc.