NDN project issue tracking system: Issueshttps://redmine.named-data.net/https://redmine.named-data.net/favicon.ico?14759811232020-07-03T10:03:53ZNDN project issue tracking system
Redmine ndn-cxx - Feature #5121 (Code review): Reserve and enforce restriction for /localhost/identity na...https://redmine.named-data.net/issues/51212020-07-03T10:03:53ZAlex Afanasyev
<p>De facto, we have reserved <code>/localhost/identity</code> namespace for special uses: digest256 identity and HMAC "identity". However, these restrictions not actively enforced and may lead to issues.</p>
<p>Several restrictions to consider:</p>
<ul>
<li>key generation should fail if the prefix is <code>/localhost/identity</code></li>
<li>validation should fail if the identity type is not handled explicitly</li>
</ul>
<p>Current state:</p>
<pre><code>$ ndnsec-keygen /localhost/identity/digest-sha256
Bv0BXAdECAlsb2NhbGhvc3QICGlkZW50aXR5CA1kaWdlc3Qtc2hhMjU2CANLRVkI
CE8m2jAVbn8cCARzZWxmCAn9AAABcxWeW1gUCRgBAhkEADbugBVbMFkwEwYHKoZI
zj0CAQYIKoZIzj0DAQcDQgAEOlpvgzk4y6eiu6mlY3v9oE+BnCBjhz/cL2GSn3Px
g6jhI9g94fO3zIrGP6Jhu+1GMsexBvY2Z34SepI41AJQkRZkGwEDHDUHMwgJbG9j
YWxob3N0CAhpZGVudGl0eQgNZGlnZXN0LXNoYTI1NggDS0VZCAhPJtowFW5/HP0A
/Sb9AP4PMTk3MDAxMDFUMDAwMDAw/QD/DzIwNDAwNjI4VDE2NTkyNhdGMEQCIFFJ
6j/YQNg6+0Rk0yMk0JguIAb53JJdh7LiTKrxUxgmAiBNVLczrI+PGJTyGEsiJHZk
$ ndnsec-ls-identity -vvv
* /localhost/identity/digest-sha256
+->* /localhost/identity/digest-sha256/KEY/O%26%DA0%15n%7F%1C
+->* /localhost/identity/digest-sha256/KEY/O%26%DA0%15n%7F%1C/self/%FD%00%00%01s%15%9E%5BX
Certificate name:
/localhost/identity/digest-sha256/KEY/O%26%DA0%15n%7F%1C/self/%FD%00%00%01s%15%9E%5BX
Validity:
NotBefore: 19700101T000000
NotAfter: 20400628T165926
Public key bits:
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEOlpvgzk4y6eiu6mlY3v9oE+BnCBj
hz/cL2GSn3Pxg6jhI9g94fO3zIrGP6Jhu+1GMsexBvY2Z34SepI41AJQkQ==
Signature Information:
Signature Type: SignatureSha256WithEcdsa
Key Locator: Self-Signed Name=/localhost/identity/digest-sha256/KEY/O%26%DA0%15n%7F%1C
</code></pre>
<p>I also don't see anywhere restriction of <code>/localhost/identity/digest-sha256</code> certificate fetching. If validator encounters a packet with key locator /localhost/identity/digest-sha256, it still will try to fetch it.</p>
ndnSIM - Feature #5028 (New): Get the list of nodes and associated links inside fw/strategy.https://redmine.named-data.net/issues/50282019-10-14T11:06:18ZAnju K James
<p>We are using ndnSIM 2.7 to simulate the network in Ubuntu 18.04.2 LTS and stuck with the following requirement.</p>
<p>Requirement: Get the list of all nodes in topology and all the links associated with each node inside strategy.(NFD/daemon/fw). </p>
<p>Please let me know if there is an option to do so.</p>
NFD - Bug #4574 (New): Dysfunctional test cases in Face/TestTcpFactoryhttps://redmine.named-data.net/issues/45742018-04-06T16:18:17ZAlex Afanasyev
<p>CreateFace, UnsupportedCreateFace, and potentially other cases are checking nothing as they are asynchronous and event dispatch wasn't initiated.</p>
ndnSIM - Task #4557 (Feedback): Upgrade base NS-3 to just released ns-3.28https://redmine.named-data.net/issues/45572018-03-25T13:02:24ZAlex Afanasyev
<p>Hopefully, any major issues are fixed. 3.28 includes a few our patches (to src/wscript), so we no longer need a few customizations, including:</p>
<ul>
<li><code>05158549275e897c7d17922bdeada483b2b8ab11</code> (was backported from the dev branch of NS-3)</li>
<li><code>4ead9ac6dd96dd5e4ab9ad7818ddaad340af98a5</code> (need to double check, may be included as part of some commit in 3.28)</li>
<li><code>1768ce2d2a87de0fb86ce41e773f19830c811194</code></li>
<li><code>0ee5773f7f25ada802eb2e6143d53962aee3323b</code> (problem was fixed)</li>
<li><code>5185f469ecd64da1f987ae8e488e5a1575f2ce5a</code> (not sure if still needed)</li>
<li><code>51be84e4410f4f9d24d6d6958c2c9be5207ba36a</code> (was fixed)</li>
<li><code>88d4271681eff2315136c7c8167300e8270270ab</code> (not needed anymore)</li>
</ul>
<p>Commits to combine:</p>
<ul>
<li><code>4069e73cfe3daf1b2af2c854e727e94338729e05</code> and <code>ed0f3fba64d898f8fcf609a626a2278cb96f8aee</code></li>
</ul>
ndnSIM - Task #4142 (New): Addition of a new field to interest and data packet https://redmine.named-data.net/issues/41422017-06-21T05:45:59Zmadhurima buragohain
<p>Hi Alex, </p>
<p>I am trying to add a new field to a interest packet. I feel that there must be some easy way to add fields to a packet. I feel like the ndnSIM developers should have made some easy a bit easier to add fields to a packet. I am expecting a call to the StackHelper to add new fields. I look forward to this feature, because it would help a lot.</p>
ndnSIM - Task #4022 (New): multicast strategy does not work in AnnotatedTopologyReaderhttps://redmine.named-data.net/issues/40222017-03-28T05:08:34Zsyaiful ahdansyaifulahdan@gmail.com
<p>I am currently trying to implement a topology using AnnotatedTopologyReader in (ndnSIM 2.3), but when you want to implement using multicast forwarding strategy and bestroute, appdelay trace the same result, when I implementation topology with p2p exsmple: p2p.Install (nodes.Get ( 0), nodes.Get (1)); , Forwarding strategy can work, my question: does not support multicast topology in reader? whether there might be an error in the scenario that I created.</p>
<p>This is very important for me, I'm trying to implement a large topology that will be simulated, and it is impossible to use p2p, because each node using the coordinates. please give me advice ... thanks for all</p>
ndn-cxx - Task #3393 (New): Create infrastructure for documentation currently in ndn-cxx develope...https://redmine.named-data.net/issues/33932016-01-05T15:24:50ZAlex Afanasyev
<p>Jan 5, 2016 call decided to move ndn-cxx documentation to the ndn-cxx homepage. However, the documentation should go to a separate repository, so it can be quickly updated.</p>
NDN Specifications - Task #1747 (In Progress): Request IPv4 and IPv6 multicast addresses from IANAhttps://redmine.named-data.net/issues/17472014-07-08T23:09:25ZJunxiao Shi
<p>Request one IPv4 and one IPv6 multicast address from IANA for NDN-TLV communication over UDP multicast.</p>