Fixed parsing of armored PGP keys by removing a possible 'Charset' field that I had not expected before.

Bumping release to 1.0.12

Author: llavarello

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "gitxray"
-version = "1.0.11"
+version = "1.0.12"
 authors = [
   { name="Lucas Lavarello", email="[email protected]" },
 ]

src/gitxray/gitxray.py

@@ -19,7 +19,7 @@ def gitxray_cli():
 ░░██████                                                  ░░██████  
  ░░░░░░                                                    ░░░░░░   
 gitxray: X-Ray and analyze Github Repositories and their Contributors. Trust no one!
-v1.0.11 - Developed by Kulkan Security [www.kulkan.com] - Penetration testing by creative minds.
+v1.0.12 - Developed by Kulkan Security [www.kulkan.com] - Penetration testing by creative minds.
 """+"#"*gx_definitions.SCREEN_SEPARATOR_LENGTH)
 
     # Let's initialize a Gitxray context, which parses arguments and more.

src/gitxray/include/gx_ugly_openpgp_parser.py

@@ -114,6 +114,7 @@ def ugly_inhouse_openpgp_block(pgp_armored_input):
 
     # format the data a bit by removing unwanted strings and chars, also consider a potential Version
     base64_str = re.sub(r'-----BEGIN PGP SIGNATURE-----|-----BEGIN PGP PUBLIC KEY BLOCK-----', '', pgp_armored_input)
+    base64_str = re.sub(r'Charset: (.+)\r?\n?', '', base64_str)
     base64_str = re.sub(r'Version: (.+)\r?\n?', '', base64_str)
     base64_str = re.sub(r'Comment: (.+)\r?\n?', '', base64_str)
     base64_str = re.sub(r'-----END PGP SIGNATURE-----|-----END PGP PUBLIC KEY BLOCK-----', '', base64_str)