Matthias Wachs

Name: dblp XML data dump
Creator: Schloss Dagstuhl - Leibniz Center for Informatics
Published: 1993
License: https://creativecommons.org/publicdomain/zero/1.0/
Keywords: dblp, XML, computer science, scholarly publications, metadata

◀ ▶ joint publications with Christian Grothoff

> Home > Persons > Matthias Wachs

Publications

2018
[j2]
- view
  authority control:
- export record
  dblp key:
  - journals/compsec/GrothoffWEA18
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/journals/compsec/GrothoffWEA18
Christian Grothoff, Matthias Wachs, Monika Ermert, Jacob Appelbaum:
Toward secure name resolution on the internet. Comput. Secur. 77: 694-708 (2018)
2014
[c5]
- view
  authority control:
- export record
  dblp key:
  - conf/cans/WachsSG14
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/cans/WachsSG14
Matthias Wachs, Martin Schanzenbach, Christian Grothoff:
A Censorship-Resistant, Privacy-Enhancing and Fully Decentralized Name System. CANS 2014: 127-142
[c4]
- view
  authority control:
- export record
  dblp key:
  - conf/p2p/WachsOG14
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/p2p/WachsOG14
Matthias Wachs, Fabian Oehlmann, Christian Grothoff:
Automatic transport selection and resource allocation for resilient communication in decentralised networks. P2P 2014: 1-5
2013
[c3]
- view
  authority control:
- export record
  dblp key:
  - conf/fps/WachsSG13
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/fps/WachsSG13
Matthias Wachs, Martin Schanzenbach, Christian Grothoff:
On the Feasibility of a Censorship Resistant Decentralized Name System. FPS 2013: 19-30
2012
[c2]
- view
  authority control:
- export record
  dblp key:
  - conf/crisis/WachsGT12
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/crisis/WachsGT12
Matthias Wachs, Christian Grothoff, Ramakrishna Thurimella:
Partitioning the Internet. CRiSIS 2012: 1-8

manage site settings

To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.