Kazumasa Omote

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 Takahiro Shinagawa

> Home > Persons > Kazumasa Omote

Publications

2009
[c12]
- view
  authority control:
- export record
  dblp key:
  - conf/securware/HiranoSEHOTHMKOKY09
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/securware/HiranoSEHOTHMKOKY09
Manabu Hirano, Takahiro Shinagawa, Hideki Eiraku, Shoichi Hasegawa, Kazumasa Omote, Kouichi Tanimoto, Takashi Horie, Seiji Mune, Kazuhiko Kato, Takeshi Okuda, Eiji Kawai, Suguru Yamaguchi:
A Two-Step Execution Mechanism for Thin Secure Hypervisors. SECURWARE 2009: 129-135
[c11]
- view
  authority control:
- export record
  dblp key:
  - conf/vee/ShinagawaETOHHHKOKKCSK09
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/vee/ShinagawaETOHHHKOKKCSK09
Takahiro Shinagawa, Hideki Eiraku, Kouichi Tanimoto, Kazumasa Omote, Shoichi Hasegawa, Takashi Horie, Manabu Hirano, Kenichi Kourai, Yoshihiro Oyama, Eiji Kawai, Kenji Kono, Shigeru Chiba, Yasushi Shinjo, Kazuhiko Kato:
BitVisor: a thin hypervisor for enforcing i/o device security. VEE 2009: 121-130
2008
[c9]
- view
  authority control:
- export record
  dblp key:
  - conf/apscc/HiranoSEHOTHKOKY08
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/apscc/HiranoSEHOTHKOKY08
Manabu Hirano, Takahiro Shinagawa, Hideki Eiraku, Shoichi Hasegawa, Kazumasa Omote, Kouichi Tanimoto, Takashi Horie, Kazuhiko Kato, Takeshi Okuda, Eiji Kawai, Suguru Yamaguchi:
Introducing Role-Based Access Control to a Secure Virtual Machine Monitor: Security Policy Enforcement Mechanism for Distributed Computers. APSCC 2008: 1225-1230

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.