Skip to content

Add support for PEM encoded keys#53

Open
mat813 wants to merge 1 commit intoKijewski:mainfrom
mat813:pem
Open

Add support for PEM encoded keys#53
mat813 wants to merge 1 commit intoKijewski:mainfrom
mat813:pem

Conversation

@mat813
Copy link
Copy Markdown

@mat813 mat813 commented Mar 28, 2026

In a project I have, I need to input the private key in a GitLab protected CI/CD pipeline variable, and in GitLab, variables are entered in a web text input field, so copy and pasting the current "binary" key file is not working.

I thought of converting it to base64, and then converting it back in my pipeline but it was kind of kludgy, and it then hit me that is what the PEM format is all about, having a simple header/footer, and the encoded content in base64 inside.

I don't think I changed the zipsign-api public API, so it should not break any existing code when upgrading.

A quick cargo build -r on main and on the pem branch tells me this adds ~21kB to the resulting cli:

-rwxrwxr-x 2 mat mat 1041032 Mar 28 19:37 target/release/zipsign
-rwxrwxr-x 2 mat mat 1062056 Mar 28 19:37 target/release/zipsign

@Kijewski
Copy link
Copy Markdown
Owner

Thank you, I like it, seems like a good feature to me! I'll review your PR on Monday.

@mat813
Copy link
Copy Markdown
Author

mat813 commented Mar 29, 2026

fixed fmt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants