Opened 2 years ago
Last modified 5 months ago
#31450 new enhancement
Add functionalities for GRS attack to linear_rank_metric.py
| Reported by: | gh-MaaikevLeuken | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | sage-9.8 |
| Component: | coding theory | Keywords: | rank code |
| Cc: | gh-MaaikevLeuken | Merged in: | |
| Authors: | Maaike van Leuken | Reviewers: | |
| Report Upstream: | N/A | Work issues: | |
| Branch: | u/gh-MaaikevLeuken/add_low_rank_parity_check_codes (Commits, GitHub, GitLab) | Commit: | a9a274e70ef9d8eb63e40859e086f0c08f02ad66 |
| Dependencies: | Stopgaps: |
Status badges
Description
To perform the GRS attack described by Gaborit et al. in "On the complexity of the rank syndrome decoding problem", functionalities need to be added to AbstractLinearRankMetricCode to:
- Find an error vector of a certain rank.
- Apply the canonical projection to a element in the extended field.
- Find a subspace of the extended field of given dimension.
- Apply the GRS algorithm.
Change History (7)
comment:1 Changed 22 months ago by
| Milestone: | sage-9.3 → sage-9.4 |
|---|
comment:2 Changed 21 months ago by
| Branch: | → u/gh-MaaikevLeuken/add_low_rank_parity_check_codes |
|---|---|
| Commit: | → 8c927685ac8684f940a3aea0591a3dc85e819e33 |
New commits:
| 8c92768 | Added Low Rank Parity Check codes and added functionalities for linear_rank_metric
|
comment:3 Changed 21 months ago by
| Commit: | 8c927685ac8684f940a3aea0591a3dc85e819e33 → a9a274e70ef9d8eb63e40859e086f0c08f02ad66 |
|---|
Branch pushed to git repo; I updated commit sha1. New commits:
| a9a274e | Improved formatting.
|
comment:4 Changed 19 months ago by
| Milestone: | sage-9.4 → sage-9.5 |
|---|
comment:5 Changed 13 months ago by
| Milestone: | sage-9.5 → sage-9.6 |
|---|
comment:6 Changed 10 months ago by
| Milestone: | sage-9.6 → sage-9.7 |
|---|
comment:7 Changed 5 months ago by
| Milestone: | sage-9.7 → sage-9.8 |
|---|
Note: See
TracTickets for help on using
tickets.
Sage development has entered the release candidate phase for 9.3. Setting a new milestone for this ticket based on a cursory review of ticket status, priority, and last modification date.