Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CER-01 #1668

Closed
Tracked by #1654
victhorbi opened this issue Jan 9, 2025 · 1 comment
Closed
Tracked by #1654

CER-01 #1668

victhorbi opened this issue Jan 9, 2025 · 1 comment
Assignees
@claytonneal
Milestone
1.0.0

Comments

@victhorbi
Copy link
Collaborator

No description provided.

@victhorbi victhorbi mentioned this issue Jan 9, 2025
Open
33 tasks
@victhorbi victhorbi added this to the 1.0.0 milestone Jan 9, 2025
@claytonneal claytonneal self-assigned this Jan 17, 2025
@claytonneal
Copy link
Member

No need to implement this - as its fine for a receiver of a certificate to construct an invalid object - knowing they must call verify method. It is possible certificates will get modified in http transit - so needs to be a 2 step approach, deserialise, then validate. Also validate is part of thor dev kit and the convention we use.

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

@claytonneal claytonneal

Labels
None yet
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
2 participants
@claytonneal @victhorbi