You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current codebase includes examples of insecure, recommended, and secure code patterns for various Sealevel attacks. However, these examples lack comments that clearly identify which code sections are insecure, recommended, or secure. This issue proposes adding detailed comments to each program to help developers easily understand and differentiate between these patterns. This will enhance the educational value of the repository and prevent potential confusion.
The text was updated successfully, but these errors were encountered:
I have created a PR that adds comments to the 0-signer-authorization program. The comments clearly identify the insecure, recommended, and secure code patterns in the examples. You can find the PR here: #38.
I've added detailed comments to all programs and submitted pull requests. These comments clearly highlight insecure, recommended, and secure code patterns within the examples, contributing to the educational value of this repository.
The current codebase includes examples of insecure, recommended, and secure code patterns for various Sealevel attacks. However, these examples lack comments that clearly identify which code sections are insecure, recommended, or secure. This issue proposes adding detailed comments to each program to help developers easily understand and differentiate between these patterns. This will enhance the educational value of the repository and prevent potential confusion.
The text was updated successfully, but these errors were encountered: