<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">

<html lang="en">

<head>

<meta content="text/html; charset=utf-8" http-equiv="Content-Type">

<title>

GitLab

</title>

<style>img {

max-width: 100%; height: auto;

}

</style>

</head>

<body>

<div class="content">

<div>

<p dir="auto">TPMv2.0 is a completely different beast, but that doesn't in itself render the TPMv1.2 support obsolete.

The TPMv1.2 hardware is still in common use.</p>

<p dir="auto">The TPMv2.0 model still doesn't lend itself well to being exposed via PKCS#11, just as TPMv1.2 didn't. There is a different format for the PEM storage of wrapped keys, and there are different fields to be included in a TPMv2.0-capable update to the TPM URI draft, but I think it still makes sense to support them in the same way we do TPMv1.2.</p>

<p dir="auto">Sure, it sucks a bit that TPMv2.0 is so completely different — and it sucks that we have two separate TSS2 library implementations we might want to be able to use — but I think we should.</p>

</div>

</div>

<div class="footer" style="margin-top: 10px;">

<p style="font-size: small; color: #777777;">

—

<br>

Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/issues/101#note_111951506">view it on GitLab</a>.

<br>

You're receiving this email because of your account on gitlab.com.

If you'd like to receive fewer emails, you can

<a href="https://gitlab.com/sent_notifications/269edccade00c2a63adfaa43f235178a/unsubscribe">unsubscribe</a>

from this thread or

adjust your notification settings.

<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Issue","url":"https://gitlab.com/gnutls/gnutls/issues/101#note_111951506"}}</script>

</p>

</div>

</body>

</html>