xref: /freebsd/contrib/file/magic/Magdir/gnu (revision 43a5ec4eb41567cc92586503212743d89686d78f)
1b6cee71dSXin LI
2b6cee71dSXin LI#------------------------------------------------------------------------------
3*43a5ec4eSXin LI# $File: gnu,v 1.24 2021/04/26 15:56:00 christos Exp $
4b6cee71dSXin LI# gnu:  file(1) magic for various GNU tools
5b6cee71dSXin LI#
6b6cee71dSXin LI# GNU nlsutils message catalog file format
7b6cee71dSXin LI#
8b6cee71dSXin LI# GNU message catalog (.mo and .gmo files)
9b6cee71dSXin LI
1058a0f0d0SEitan Adler# Update: Joerg Jenderek
1158a0f0d0SEitan Adler# URL: https://www.gnu.org/software/gettext/manual/html_node/MO-Files.html
1258a0f0d0SEitan Adler# Reference: ftp://ftp.gnu.org/pub/gnu/gettext/gettext-0.19.8.tar.gz/
1358a0f0d0SEitan Adler#	gettext-0.19.8.1/gettext-runtime/intl/gmo.h
1458a0f0d0SEitan Adler# Note: maybe call it like "GNU translation gettext machine object"
15b6cee71dSXin LI0	string		\336\22\4\225	GNU message catalog (little endian),
1658a0f0d0SEitan Adler#0	ulelong	0x950412DE		GNU-format message catalog data
1758a0f0d0SEitan Adler# TODO: write lines in such a way that code can also be called for big endian variant
1858a0f0d0SEitan Adler#>0	use		gettext-object
1958a0f0d0SEitan Adler#0	name		gettext-object
2058a0f0d0SEitan Adler>4	ulelong		x		revision
2158a0f0d0SEitan Adler!:mime	application/x-gettext-translation
2258a0f0d0SEitan Adler# mo extension is also used for Easeus Partition Master PE32 executable module
2358a0f0d0SEitan Adler# like ConvertFatToNTFS.mo
2458a0f0d0SEitan Adler!:ext	gmo/mo
2558a0f0d0SEitan Adler# only found three revision combinations 0.0 0.1 1.1 as unsigned 32-bit
2658a0f0d0SEitan Adler# major revision
2758a0f0d0SEitan Adler>4	ulelong/0xFFff	x		%u.
2858a0f0d0SEitan Adler# minor revision
2958a0f0d0SEitan Adler>4	ulelong&0x0000FFff	x	\b%u
3058a0f0d0SEitan Adler>>8	ulelong		x		\b, %u message
3158a0f0d0SEitan Adler# plural s
3258a0f0d0SEitan Adler>>8	ulelong		>1		\bs
3358a0f0d0SEitan Adler# size of hashing table
3458a0f0d0SEitan Adler#>20	ulelong		x		\b, %u hash
3558a0f0d0SEitan Adler#>20	ulelong		>1		\bes
36*43a5ec4eSXin LI#>24	ulelong		x		at %#x
37*43a5ec4eSXin LI# for revision x.0 offset of table with originals is 1Ch if directly after header
3858a0f0d0SEitan Adler>4	ulelong&0x0000FFff	=0
39*43a5ec4eSXin LI>>12	ulelong		!0x1C		\b, at %#x string table
4058a0f0d0SEitan Adler# but for x.1 table offset i found is 30h. That means directly after bigger header
4158a0f0d0SEitan Adler>4	ulelong&0x0000FFff	>0
42*43a5ec4eSXin LI>>12	ulelong		!0x30		\b, at %#x string table
4358a0f0d0SEitan Adler# The following variables are only used in .mo files with minor revision >= 1
4458a0f0d0SEitan Adler# number of system dependent segments
4558a0f0d0SEitan Adler#>>28	ulelong		x		\b, %u segment
4658a0f0d0SEitan Adler#>>28	ulelong		>1		\bs
4758a0f0d0SEitan Adler# offset of table describing system dependent segments
48*43a5ec4eSXin LI#>>32	ulelong		x		at %#x
4958a0f0d0SEitan Adler# number of system dependent strings pairs
5058a0f0d0SEitan Adler>>36	ulelong		x		\b, %u sysdep message
5158a0f0d0SEitan Adler>>36	ulelong		>1		\bs
5258a0f0d0SEitan Adler# offset of table with start offsets of original sysdep strings
53*43a5ec4eSXin LI#>>40	ulelong		x		\b, at %#x sysdep strings
5458a0f0d0SEitan Adler# offset of table with start offsets of translated sysdep strings
55*43a5ec4eSXin LI#>>44	ulelong		x		\b, at %#x sysdep translations
56*43a5ec4eSXin LI# >>(44.l)	ulelong	x		%#x chars
57*43a5ec4eSXin LI# >>>&0		ulelong	x		at %#x
5858a0f0d0SEitan Adler# >>>>(&-4)	string	x		"%s"
5958a0f0d0SEitan Adler# string table after big header
60*43a5ec4eSXin LI#>>48	ubequad		x		\b, string table %#llx
6158a0f0d0SEitan Adler#
6258a0f0d0SEitan Adler# 0th string length seems to be always 0
6358a0f0d0SEitan Adler#>(12.l)	ulelong	x		\b, %u chars
64*43a5ec4eSXin LI#>>&0		ulelong	x		at %#x
65*43a5ec4eSXin LI# if 1st string length positive inspect offset and string
6658a0f0d0SEitan Adler#>(12.l+8)	ulelong	>0		\b, %u chars
67*43a5ec4eSXin LI#>>&0		ulelong	x		at %#x
68*43a5ec4eSXin LI# if 2nd string length positive inspect offset and string
6958a0f0d0SEitan Adler# >(12.l+16)	ulelong	>0		\b, %u chars
70*43a5ec4eSXin LI# >>&0		ulelong	x		at %#x
7158a0f0d0SEitan Adler# skip newline byte
7258a0f0d0SEitan Adler#>>>(&-4)	ubyte	=0x0A
7358a0f0d0SEitan Adler#>>>>&0		string	x		"%s"
7458a0f0d0SEitan Adler#>>>(&-4)	ubyte	!0x0A
7558a0f0d0SEitan Adler#>>>>&-1		string	x		'%s'
7658a0f0d0SEitan Adler# offset of table with translation strings
77*43a5ec4eSXin LI#>16	ulelong		x		\b, at %#x translation table
7858a0f0d0SEitan Adler# check translation 0 length and offset
7958a0f0d0SEitan Adler>(16.l)		ulelong	>0
8058a0f0d0SEitan Adler>>&0		ulelong	x
8158a0f0d0SEitan Adler# translation 0 seems to be often Project-Id with name and version
8258a0f0d0SEitan Adler>>>(&-4)	string	x		\b, %s
8358a0f0d0SEitan Adler# trans. 1 with bytes >= 1 unlike icoutils-0.31.0\po\en@boldquot.gmo with 1 NL
8458a0f0d0SEitan Adler>(16.l+8)	ulelong	>1
8558a0f0d0SEitan Adler>>&0		ulelong	x
8658a0f0d0SEitan Adler>>>(&-4)	ubyte	!0x0A
8758a0f0d0SEitan Adler>>>>&-1		string	x		'%s'
8858a0f0d0SEitan Adler# 1 New Line like in tar-1.29\po\de.gmo
8958a0f0d0SEitan Adler>>>(&-4)	ubyte	=0x0A
9058a0f0d0SEitan Adler>>>>&0		ubyte	!0x0A
9158a0f0d0SEitan Adler>>>>>&-1	string	x		'%s'
9258a0f0d0SEitan Adler# 2nd New Line like in parted-3.1\po\de.gmo
9358a0f0d0SEitan Adler>>>>&0		ubyte	=0x0A
9458a0f0d0SEitan Adler>>>>>&0		string	x		'%s'
95b6cee71dSXin LI
96b6cee71dSXin LI0	string		\225\4\22\336	GNU message catalog (big endian),
9758a0f0d0SEitan Adler#0	ubelong	0x950412DE		GNU-format message catalog data
9858a0f0d0SEitan Adler!:mime	application/x-gettext-translation
9958a0f0d0SEitan Adler!:ext	gmo/mo
10058a0f0d0SEitan Adler# TODO: for big endian use same code as for little endian
10158a0f0d0SEitan Adler#>0	use		\^gettext-object
10258a0f0d0SEitan Adler# DEBUG code
103*43a5ec4eSXin LI#>16	ubelong		x		\b, at %#x translation table
104*43a5ec4eSXin LI#>(16.L)		ubelong	x		%#x chars
105*43a5ec4eSXin LI#>>&0		ubelong	x		at %#x
10658a0f0d0SEitan Adler# unexpected value HERE!
107*43a5ec4eSXin LI#>>>(&-4)	ubequad	x		%#llx
10858a0f0d0SEitan Adler#
109b6cee71dSXin LI>4	beshort		x		revision %d.
110b6cee71dSXin LI>6	beshort		>0		\b%d,
111b6cee71dSXin LI>>8	belong		x		%d messages,
112b6cee71dSXin LI>>36	belong		x		%d sysdep messages
113b6cee71dSXin LI>6	beshort		=0		\b%d,
114b6cee71dSXin LI>>8	belong		x		%d messages
115b6cee71dSXin LI
116b6cee71dSXin LI
117b6cee71dSXin LI# GnuPG
118b6cee71dSXin LI# The format is very similar to pgp
119b6cee71dSXin LI0	string          \001gpg                 GPG key trust database
120b6cee71dSXin LI>4	byte            x                       version %d
121b6cee71dSXin LI# Note: magic.mime had 0x8501 for the next line instead of 0x8502
122b6cee71dSXin LI0	beshort		0x8502			GPG encrypted data
123b6cee71dSXin LI!:mime	text/PGP # encoding: data
124b6cee71dSXin LI
12558a0f0d0SEitan Adler# Update: Joerg Jenderek
12658a0f0d0SEitan Adler# Note:	PGP and GPG use same data structure.
12758a0f0d0SEitan Adler#	So recognition is now done by ./pgp with start test for byte 0x99
128b6cee71dSXin LI# This magic is not particularly good, as the keyrings don't have true
129b6cee71dSXin LI# magic. Nevertheless, it covers many keyrings.
13058a0f0d0SEitan Adler# 0	ubeshort-0x9901	<2
13158a0f0d0SEitan Adler# >3	byte		4
13258a0f0d0SEitan Adler# >>4	bedate		x		GPG key public ring, created %s
13358a0f0d0SEitan Adler# !:mime application/x-gnupg-keyring
134a5d223e6SXin LI
135b6cee71dSXin LI# Symmetric encryption
136b6cee71dSXin LI0	leshort		0x0d8c
137b6cee71dSXin LI>4	leshort		0x0203
138b6cee71dSXin LI>>2	leshort		0x0204		GPG symmetrically encrypted data (3DES cipher)
139b6cee71dSXin LI>>2	leshort		0x0304		GPG symmetrically encrypted data (CAST5 cipher)
140b6cee71dSXin LI>>2	leshort		0x0404		GPG symmetrically encrypted data (BLOWFISH cipher)
141b6cee71dSXin LI>>2	leshort		0x0704		GPG symmetrically encrypted data (AES cipher)
142b6cee71dSXin LI>>2	leshort		0x0804		GPG symmetrically encrypted data (AES192 cipher)
143b6cee71dSXin LI>>2	leshort		0x0904		GPG symmetrically encrypted data (AES256 cipher)
144b6cee71dSXin LI>>2	leshort		0x0a04		GPG symmetrically encrypted data (TWOFISH cipher)
145b6cee71dSXin LI>>2	leshort		0x0b04		GPG symmetrically encrypted data (CAMELLIA128 cipher)
146b6cee71dSXin LI>>2	leshort		0x0c04		GPG symmetrically encrypted data (CAMELLIA192 cipher)
147b6cee71dSXin LI>>2	leshort		0x0d04		GPG symmetrically encrypted data (CAMELLIA256 cipher)
148b6cee71dSXin LI
149b6cee71dSXin LI
150b6cee71dSXin LI# GnuPG Keybox file
15148c779cdSXin LI# <https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blob;f=kbx/keybox-blob.c;hb=HEAD>
152b6cee71dSXin LI# From: Philipp Hahn <hahn@univention.de>
153b6cee71dSXin LI0	belong	32
154b6cee71dSXin LI>4	byte	1
155b6cee71dSXin LI>>8	string	KBXf	GPG keybox database
156b6cee71dSXin LI>>>5	byte	1	version %d
157b6cee71dSXin LI>>>16	bedate	x	\b, created-at %s
158b6cee71dSXin LI>>>20	bedate	x	\b, last-maintained %s
159b6cee71dSXin LI
160b6cee71dSXin LI
161b6cee71dSXin LI# From: James Youngman <jay@gnu.org>
162b6cee71dSXin LI# gnu find magic
163b6cee71dSXin LI0	string	\0LOCATE	GNU findutils locate database data
164b6cee71dSXin LI>7	string	>\0		\b, format %s
165b6cee71dSXin LI>7	string	02		\b (frcode)
166b6cee71dSXin LI
167b6cee71dSXin LI# Files produced by GNU gettext
168b6cee71dSXin LI
169b6cee71dSXin LI# gettext message catalogue
1705f0216bdSXin LI0	search/1024	\nmsgid
1715f0216bdSXin LI>&0	search/1024	\nmsgstr	GNU gettext message catalogue text
1725f0216bdSXin LI!:strength +100
173b6cee71dSXin LI!:mime text/x-po
174