I'm writing about the whole lot... and mostly the map keys
.
You will find a file in this thread (post 28 dated 2015) which are (said to be) the public keys for all VAG cars by each area and this is where you will see the firmware public keys as well as the rest.
http://turbo-quattro.com/archive/index.php/t-19874.html
For Seat they are all the same.... least last time I looked. The FEC is the SWAP. Metafile2.txt keys once decoded and processed are the same as the one on post 700 read off a unit and that's the one I used to test the reversing engineering methodology on Metafile2.txt map files and it works, but of no use if you haven't got the primary key since you can't sign anything you edit. An older version of the VAG firmware is suppose to ignore these signatures. Some people try / do to move back to the older release. These are Audi people with older DVD based systems.
I used Hex Editor Neo to look at file linked above. It gives the DataKey. FECKey and MetaInfoKey. All public keys. For Seat you get this bank of codes back for each of them as I recall:
9a 49 9b 04 8b ae bf ac 83 3f de 81 ba 80 30 93
05 b6 6f ed 54 59 c3 8f 60 f6 10 a9 aa 5a 19 10
05 17 05 8f ea 49 d3 75 e3 f9 e1 54 4e 17 ee c9
c3 c1 dd 7d 30 16 de b1 55 45 fd 9e 18 00 51 22
d6 a1 33 10 95 c0 dd cf 43 a1 c2 fe c0 bc aa 1c
fe 48 49 25 89 9e dd 71 b0 d4 08 cf 16 bf 10 e2
e1 bc 70 a3 52 f2 e6 54 0b 60 05 5a a7 52 ec 4a
83 65 f7 68 19 66 f4 d5 46 c7 38 b1 6b 5a 1f 13
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03
1e 0b 93 73 dc b4 93 b6 12 ce 09 c4 03 e9 21 fc
9b 4e 97 ce 55 c5 b4 c0 80 ad 17 2d ca 91 4d c1
87 45 52 ca 4a 95 96 9e 61 ff c3 24 a5 91 5b d1
83 80 85 90 8f 99 8f 76 ba 5f b2 09 86 db 86 c1
b5 89 b9 58 75 4e d5 d5 aa 08 af 2f 16 3e 33 a6
c6 46 77 dd 32 e0 98 f0 ec f9 14 6b af 35 05 3c
23 aa 8b a8 76 fb 2d 0c 6e d7 2f 0b b3 dc 77 6e
b8 74 14 1c 95 c1 6f ff 0c bb 4a e9 ee 70 a2 3c
Basically if you are so inclined you can take those keys plus any download file in any of those areas run it through to validate using the reversing engineering methodology in post 700. So you can test the public keys. It doesn't get you any further forward thou it just carries out the procedure that would be executed in the unit to validate the signature.
Your best bet is to read the thread from 2.5 years ago onto June 2017 to work out why some people had MIB1 success with buying a new SD card off ebay and others didn't. It's probably there somewhere and also MIB1 cards stopped being able to be updated as well last June for some people you will see that. Whatever the old card MIB1 workaround was it doesn't work for everyone and it also stops working for some people. There are a lot of silent people on this thread that pop up from time to time looking for a MIB1 solution but haven't got one. MIB2 card one does exist thou.