Skip to content

🔑 Add client cert auth#616

Open
tobiasKaminsky wants to merge 3 commits into
masterfrom
clientCert
Open

🔑 Add client cert auth#616
tobiasKaminsky wants to merge 3 commits into
masterfrom
clientCert

Conversation

@tobiasKaminsky

@tobiasKaminsky tobiasKaminsky commented Dec 19, 2023 •
edited
Loading

Copy link
Copy Markdown
Member

This adds 8080 to be used with client cert auth.
selfsigned-cli.p12 needs to be imported in browser's chain.

Password is empty.
@tobiasKaminsky
Add client cert auth
2dbc0de 
Signed-off-by: tobiasKaminsky <tobias@kaminsky.me>
@tobiasKaminsky tobiasKaminsky mentioned this pull request Dec 21, 2023
Closed
3 tasks
@AndyScherzinger AndyScherzinger changed the title Add client cert auth Jan 18, 2024
@tobiasKaminsky
add legacy p12 for older Android versions
3310ded 
Signed-off-by: tobiasKaminsky <tobias@kaminsky.me>
@nickvergessen

nickvergessen commented Jan 25, 2024

Copy link
Copy Markdown
Member

Can we name the files in a way that it's clear they are "localhost development" only, otherwise we will get useless h1 reports again
@tobiasKaminsky

tobiasKaminsky commented Jan 26, 2024

Copy link
Copy Markdown
Member Author

Sure.
For my understanding the entire shallow-server/CI is for localhost dev or dev only.

What about something like"dev test key"?
@nickvergessen

nickvergessen commented Jan 26, 2024

Copy link
Copy Markdown
Member

For my understanding the entire shallow-server/CI is for localhost dev or dev only.

Yes, we all know. But script kiddies searching repos for BEGIN PRIVATE KEY do not know what shallow server means. it could be a production thing.

What about something like"dev test key"?

👍🏼
@tobiasKaminsky
make more clear that this is for testing purpose only
d043632 
Signed-off-by: tobiasKaminsky <tobias@kaminsky.me>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants

@tobiasKaminsky @nickvergessen