dblp keys for Matthias Krause 0001

Matthias Krause 0001

Keys

# of data records = 77

homepages/90/2046-1 journals/tosc/HamannMKM22 conf/sacrypt/Hamann0M19 journals/iacr/Hamann019 journals/ccds/HamannKMZ18 journals/ccds/HamannK18 journals/tosc/HamannKM17 journals/iacr/Krause17 journals/iacr/Hamann0MZ17 journals/iacr/Hamann0M17 journals/iacr/Hamann0M16 journals/iacr/Krause15 journals/iacr/Hamann015 conf/sicherheit/ArmknechtH014 conf/semweb/KastenSA013 conf/asiacrypt/ArmknechtFKLSS11 conf/sacrypt/KrauseH11 journals/iacr/KrauseH11 books/cu/10/0001WCH10 journals/iacr/KrauseAF10 conf/sacrypt/KrauseS09 conf/dagstuhl/0001S09 journals/mst/Krause07 journals/cc/Krause06 conf/fse/KrauseS06 conf/icalp/ArmknechtK06 conf/dagstuhl/2006P6111 conf/dagstuhl/KrauseMPR06 conf/dagstuhl/KrausePRM06 journals/iandc/KrauseSW05 conf/indocrypt/ArmknechtKS05 journals/jcss/DammKMW04 journals/cpc/KrauseS03 conf/crypto/ArmknechtK03 conf/eurocrypt/Krause02 conf/stacs/Krause02 journals/cc/KrauseL01 conf/acisp/ZennerKL01 conf/fsttcs/ForsterKLMSS01 conf/stacs/KrauseL01 journals/eccc/ECCC-TR01-078 journals/iacr/Krause01 journals/tcs/HofmeisterKS00 conf/latin/KrauseS00 journals/eccc/ECCC-TR00-003 journals/eccc/ECCC-TR00-014 conf/icalp/KrauseSW99 journals/eccc/ECCC-TR99-011 journals/cc/KrauseP98 journals/tcs/KrauseP97 conf/cocoon/HofmeisterKS97 journals/tcs/Krause96 journals/mst/KrauseW95 conf/focs/KrauseP95 conf/stacs/Krause95 journals/eccc/ECCC-TR95-009 journals/eik/DammKMW94 conf/fuzzy/NissenK94 conf/stoc/KrauseP94 journals/eccc/ECCC-TR94-023 journals/iandc/HromkovicKMW92 journals/ita/KrauseMW92 journals/ita/Krause92 conf/stacs/DammKMW92 tr/trier/MI92-01 journals/iandc/Krause91 journals/iandc/WaackK91 journals/tcs/KrauseMW91 conf/coco/Krause91 conf/focs/KrauseW91 conf/mfcs/Krause90 phd/dnb/Krause89 conf/coco/KrauseMW89 conf/fct/KrauseW89 conf/ifip/KrauseMW89 journals/eik/Krause88 conf/mfcs/KrauseMW88

a service of  Schloss Dagstuhl - Leibniz Center for Informatics

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.