View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004927 | GNUnet | GNS | public | 2017-02-26 23:53 | 2019-02-28 11:17 |
| Reporter | Christian Grothoff | Assigned To | schanzen | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | Git master | ||||
| Target Version | 0.11.0 | Fixed in Version | 0.11.0 | ||
| Summary | 0004927: pad GNS responses | ||||
| Description | DKG made a good argument for padding all replies to a fixed multiple of some block size, i.e. 128 bytes. | ||||
| Tags | No tags attached. | ||||
|
|
Note that there is an EDNS(0) extension for padding, so we do not need to invent a new record type for padding. |
|
|
Wonder if we should bother padding pure PKEY replies, as those all will be one size, so maybe having that one (common) GNS-specific non-128-multiple would make sense. |
|
|
resolved in 1981ffec4ad18287efe8ab693390e1d498de05bf The serialized record set is padded to the next power of 2. There is not actually a padding record added as we do not (want to) support EDNS0 anyway. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-02-26 23:53 | Christian Grothoff | New Issue | |
| 2017-02-26 23:54 | Christian Grothoff | Note Added: 0011865 | |
| 2017-02-26 23:55 | Christian Grothoff | Note Added: 0011866 | |
| 2018-06-24 17:14 | schanzen | Assigned To | => schanzen |
| 2018-06-24 17:14 | schanzen | Status | new => assigned |
| 2018-06-24 18:07 | schanzen | Status | assigned => resolved |
| 2018-06-24 18:07 | schanzen | Resolution | open => fixed |
| 2018-06-24 18:07 | schanzen | Fixed in Version | => Git master |
| 2018-06-24 18:07 | schanzen | Note Added: 0013071 | |
| 2019-02-16 11:55 | Christian Grothoff | Fixed in Version | Git master => 0.11.0 |
| 2019-02-28 11:17 | Christian Grothoff | Status | resolved => closed |
