similar to: [PATH 9/12] VTPM mini-os: New stubdom applications

Since the vTPM implementations are being incorproated into Xen and possibly upstream Linux, I would like to see if this protocol change could be added before we have significant legacy implementations. If not, I still think it would be useful as either a v2 or negotiated protocol change. The current vTPM protocol is a copy of the network protocol. This was likely done for ease of implementation,

What will follow soon are updates to vtpmd, vtpm_manager, xm, xl, mini-os, and new vtpm and vtpm manager stub domains. The first patch I''d like to submit upgrades vtpmd to version 0.7.4 This patch does the following: -add checks to configure to check for cmake (required by berlios 0.7.4) -removes all of the 0.5.1 patches -adds a single patch for 0.7.4 -cleans up the makefile, should

Ian, this one is special just for you. I''m sending it as an attachment because my email client will mangle it. This patch will remove the cmake dependency from xen prior to autoconf stubdom This patch applies ontop of [VTPM v7 3/8] vtpm/vtpmmgr and required libs to stubdom/Makefile You can apply it to your tree by doing the following: git rebase -i <VTPM v7 3/8 revision>

The default make targets in the top level makefile set DESTDIR which gets applied when the stubdom makefile tries to do a make install within gmp to install libgmp.a to the cross root. Ian, do you want to apply this to your tree and commit the whole thing or would you prefer I roll out a fresh new patch set with all updates applied? Signed-off-by: Matthew Fioravante

The following are a set of patches to run the berlios tpm emulator 0.6.1 in a mini-os domain, called vtpm-stubdom. Documentation on how to use this domain is located at stubdom/vtpm/README. The following are a series of patches that enable this domain and also add significant stability improvements to the entire vTPM subsystem, including the original method of using vtpmd as a process.

Hi community, there are some problems to start vTPM vtpm-stubdom following docs/misc/vtpm.txt. When I start vtpm-stbdom, the vtpmmgr-stubdom will print out: === ERROR[VTPM]: LoadKey failure: Unrecognized uuid! 69743ae0-9d4a-4ad6-9819-e602085b6792 ERROR[VTPM]: Failed to load key ERROR in vtpmmgr_LoadHashKey at vtpm_cmd_handler.c:78 code: TPM_BAD_PARAMETER. === I start vtpmmgr-stubdom with

Hi community, there are some problems to start vTPM vtpm-stubdom following docs/misc/vtpm.txt. When I start vtpm-stbdom, the vtpmmgr-stubdom will print out: === ERROR[VTPM]: LoadKey failure: Unrecognized uuid! 69743ae0-9d4a-4ad6-9819-e602085b6792 ERROR[VTPM]: Failed to load key ERROR in vtpmmgr_LoadHashKey at vtpm_cmd_handler.c:78 code: TPM_BAD_PARAMETER. === I start vtpmmgr-stubdom with

Hey Timo, Just curious if you ever thought about supporting other than just OpenSSL? PolarSSL looks really interesting, has no major dependencies and is very lightweight compared to OpenSSL, GNUTLS or others... https://polarssl.org/ I guess it could be a lot of work, or not, anyway, I'm just curious... -- Best regards, */Charles/*

I've got a first cut of the rebase here: git://github.com/gwd/sig-virt-xen out/update-4.4.1-rc1-ee81dda-RFC To build it, you'll need to download the polarssl tarball: http://xenbits.xen.org/xen-extfiles/polarssl-1.1.4-gpl.tgz And you'll need a tarball based on (unfortunately) a private tree, which you can find here: git://github.com/gwd/xen base/update-4.4.1-rc1-ee81dda-RFC This

See MAINTAINERS file Signed-off-by: Matthew Fioravante <matthew.fioravante@jhuapl.edu> diff --git a/MAINTAINERS b/MAINTAINERS index 094fe9e..f562efa 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -261,6 +261,21 @@ S: Supported F: tools/xentrace/ F: xen/common/trace.c +VTPM +M: Matthew Fioravante <matthew.fioravante@jhuapl.edu> +S: Supported +F: tools/vtpm +F:

On Mon, Dec 22, 2014 at 9:30 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: > Although the cryptography is now separated from the rest of the logic in > tinc, it is not really replaceable, since only OpenSSL is supported. > However, there is also a new protocol in tinc 1.1, which uses Ed25519 > and ChaCha-Poly1305. The code for those algorithms is included in tinc, > so the

I've tried my best searching for whether this question has already been posted to tinc listservs, so apologies if this is a repeat question. Is it possible to use tinc with SSL implementations besides OpenSSL, e.g. the PolarSSL or YaSSL/cyassl libraries used on embedded distros like OpenWRT? Thank you. -- Ben West http://gowasabi.net ben at gowasabi.net 314-246-9434 -------------- next

This patch fixes IO deadlocks in the vtpm hotplug scripts. Signed off by: Matthew Fioravante matthew.fioravante@jhuapl.edu --- Changed since previous: * rebased off of latest xen stable * replaced instances of gawk with awk diff --git a/tools/hotplug/Linux/vtpm b/tools/hotplug/Linux/vtpm --- a/tools/hotplug/Linux/vtpm +++ b/tools/hotplug/Linux/vtpm @@ -1,22 +1,18 @@ #!/bin/bash +export

Signed-off-by: Matthew Fioravante <matthew.fioravante@jhuapl.edu> --- stubdom/configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/stubdom/configure.ac b/stubdom/configure.ac index db44d4a..384a94a 100644 --- a/stubdom/configure.ac +++ b/stubdom/configure.ac @@ -18,7 +18,7 @@ m4_include([../m4/depends.m4]) # Enable/disable stub domains

Hi all, I'm wondering if the GPL-2.0 licensed mbedTLS (that's the version in OpenWrt) is 'compatible' with NUT binaries (not including the Python or Perl binaries which aren't used in OpenWrt) which is GPL 2.1+ AIUI. Because mbedTLS is the default library for OpenWrt and NSS is not yet in OpenWrt, and because OpenSSL is considered incompatible (I seem to recall reading that

Add support for mapping hardware io memory into domains via domain config files. The syntax is iomem=[PAGE,NUM_PAGES] Signed off by Matthew Fioravante: matthew.fioravante@jhuapl.edu --- Changes from previous * Rebased onto latest xen-unstable * Rewrote the feature to mimic the style used by iports and irqs in current libxl * Updated xl.cfg manpage * removed the redundant "allow"

Hi, Is it possible to compile tinc against polarssl ? Perry

So it looks like I was basing my patches off of this tree git://xenbits.xen.org/xen-unstable.git which is not actually xen-unstable. I rebased and reworked my patches off of the correct tree git://xenbits.xen.org/xen.git What follows are the vtpmd, vtpm_manager, and libxl patches. All of the mini-os patches apply cleanly to the latest xen so I won''t be resubmitting those unless you all

flight 15155 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/15155/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386 4 xen-build fail REGR. vs. 15130 build-i386-oldkern 4 xen-build fail REGR. vs. 15130 Tests which are failing intermittently

I want to install tpm emulator simulating the TPM hardware in Xen platform. But compiling tpm emulator brings such error.My kernel is 2.6.16. #make ; make install ......... Building modules, stage 2. MODPOST *** Warning: "__stack_chk_fail" [/root/xen-3.0.2/tools/vtpm/tpm_emulator/tpm_emulator.ko] undefined! CC /root/xen-3.0.2/tools/vtpm/tpm_emulator/tpm_emulator.mod.o LD [M]