Skip to content

User interface chokes with 200+ certificates #51

@laurivosandi

Description

@laurivosandi

Current approach is pretty naive - all signed certificates and accompanying metadata and code snippets are inserted into DOM tree which makes even Chrome choke.

For development/testing run this with autosign allowed from localhost:

for j in $(seq 1 500); do
  openssl genrsa -out /tmp/host_key.pem 1024
  openssl req -new -sha384 -subj "/CN=$(cat /dev/urandom | tr -dc 'a-z0-9' | fold -w 15 | head -n 1)" \
    -key /tmp/host_key.pem \
    -out /tmp/host_req.pem
  curl --cert-status -f -L -H "Content-type: application/pkcs10" \
    --data-binary @/tmp/host_req.pem \
    -o /tmp/host_cert.pem \
    'http://127.0.1.1:8080/api/request/?wait=yes\&autosign=yes'
done

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions