On Thu, Aug 31, 2017 at 04:18:42PM +0000, alexander.stef...@infineon.com wrote: > > I guess Alexander should be able to propose such subset. > > For scenario #1 you could probably come up with a list of commands > that are generally useful. But once you are restricted to those five > commands, you block iterative debugging of the "I see where the > problem might be, could you try to execute ..." fashion by requiring > the other person to patch and rebuild their kernel.
If the subset turns out to be wrong, it can be revisited. > For scenario #2 I see no chance to do that in a generic way. I could > maybe tell you what the commands in this mode currently look like for > Infineon TPMs, so that they can be whitelisted, but they might look > different in the future and they are certainly different for other > vendor's implementations. It's easy to check whether a command is vendor specific and allow to pass those through. /Jarkko ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ tpmdd-devel mailing list tpmdd-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
