Skip to content
Snippets Groups Projects

Fix/remove plus

Closed Fix/remove plus
fix/remove-plus into dev
2 unresolved threads
Closed Tobias Grasmeyer requested to merge fix/remove-plus into dev
2 unresolved threads

Removed all "+" signs from references. Weblinks are working now.

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
content/docs/refs.md
15 ###### [ABB20]
16 16 [E. Alkim, P. S. L. M. Barreto, N. Bindel, J. Krämer, P. Longa, and J. E. Ricardini. The lattice-based digital signature scheme qtesla. In M. Conti, J. Zhou, E. Casalicchio, and A. Spognardi, editors, Applied Cryptography and Network Security, pages 441–460. Springer International Publishing, 2020](https://eprint.iacr.org/2019/085.pdf)
17 17
18 ###### [ABB+20]
18 ###### [ABB20]
19 19 [N. Aragon, P. Barreto, S. Bettaieb, L. Bidoux, O. Blazy, J. C. Deneuville, P. Gaborit, S. Gueron, T. Guneysu, C. A. Melchor, et al.2020. BIKE: bit flipping key encapsulation (22 Oct 2020)](https://bikesuite.org/files/v4.1/BIKE_Spec.2020.10.22.1.pdf)
20 20
21 21 ###### [ABBC10]
22 22 [T. Acar, M. Belenkiy, M. Bellare, and D. Cash. Cryptographic agility and its relation to circular encryption. 2010.](https://eprint.iacr.org/2010/117)
23 23
24 ###### [ABD+21]
24 ###### [ABD21]
25 25 [R. Avanzi, J. Bos, L. Ducas, E. Kiltz, T. Lepoint, V. Lyubashevsky, J. M. Schanck,P. Schwabe, G. Seiler, and D. Stehlé. 2021. CRYSTALS-Kyber algorithm specifi-cations and supporting documentation (version 3.01).NIST PQC Round 3(31Jan 2021)](https://pq-crystals.org/kyber/data/kyber-specification-round3-20210131.pdf)
26 26
27 ###### [ABF+ 17]
27 ###### [ABF 17]
  • Nouri Alnahawi
    Nouri Alnahawi @fbi1426 started a thread on the diff
    • content/docs/agility/development.md
    15 15 - [PQFabric: A Permissioned Blockchain Secure from Both Classical and Quantum Attacks](https://arxiv.org/abs/2010.06571) Proposes a redesign of Fabric's credential-management procedures and related specifications in order to incorporate hybrid digital signatures, protecting against both classical and quantum attacks using one classical and one quantum-safe signature. [[HPDM20]](../../refs#hpdm20)
    16 16 - [Public Key Infrastructure and Crypto Agility Concept for Intelligent Transportation Systems](http://www.thinkmind.org/index.php?view=article&articleid=vehicular_2015_1_30_30028) This paper proposes a multi-domain PKI architecture for intelligent transportation systems, which considers the necessities of road infrastructure authorities and vehicle manufacturers, today. [[UWK15]](../../refs#uwk15)
    17 17 - Eval crypto libs
    18 - [Comparing the Usability of Cryptographic APIs](https://ieeexplore.ieee.org/document/7958576) This paper is the first to examine both how and why the design and resulting usability of different cryptographic libraries affects the security of code written with them. [[ABF+ 17]](../../refs#abf+ 17)
    18 - [Comparing the Usability of Cryptographic APIs](https://ieeexplore.ieee.org/document/7958576) This paper is the first to examine both how and why the design and resulting usability of different cryptographic libraries affects the security of code written with them. [[ABF17]](../../refs#abf17)
    • Nouri Alnahawi
      Nouri Alnahawi @fbi1426
      Suggested change
      18 - [Comparing the Usability of Cryptographic APIs](https://ieeexplore.ieee.org/document/7958576) This paper is the first to examine both how and why the design and resulting usability of different cryptographic libraries affects the security of code written with them. [[ABF17]](../../refs#abf17)
      18 - [Comparing the Usability of Cryptographic APIs](https://ieeexplore.ieee.org/document/7958576) This paper is the first to examine both how and why the design and resulting usability of different cryptographic libraries affects the security of code written with them. [[ABF+17]](../../refs#abf17)
      Edited by Nouri Alnahawi
    • Please register or sign in to reply
  • Nouri Alnahawi
    Nouri Alnahawi @fbi1426

    The functionality is now ok, but the references are unfortunately not. Removing the "+" was only intended for the ref links, not for the actual visible text. The "+" is part of the citation based on the chosen citation style (alpha). Removing the "+" implies missing authors, who where only identifiable through the "+" sign in the citation text.

    Compare: [ABF+ 17] should become [ABF+17] whereas we have [ABF17]

    This means only A B and F are the authors, which is false! There's one more author G, implied by the "+".

    Original full reference: [ABF+ 17] should become [ABF+17] whereas we have [ABF 17]

    Y. Acar, M. Backes, S. Fahl, S. Garfinkel, D. Kim, M. L. Mazurek, and C. Stransky. Comparing the Usability of Cryptographic APIs. In 2017 IEEE Symposium on Security and Privacy (SP), pages 154–171, San Jose, CA, USA, May 2017. IEEE, doi:10.1109/SP.2017.52

  • Tobias Grasmeyer
    Tobias Grasmeyer @isttogras
    Author
    • Didn't we try to fix it because markup does not understand "+"?
    • For the anchor to work I have to use the same text in refs, which means there we will have a different anchor text than the one displayed in the individual sections.
  • Tobias Grasmeyer closed

    closed

    • Please register or sign in to reply