I followed Ken's instructions and things worked out OK. My embedded board
booted up and I got
xxx~$ tpm_version
TPM 1.2 Version Info:
Chip Version: 1.2.2.60
Spec Level: 2
Errata Revision: 1
TPM Vendor ID: WEC
TPM Version: 01010000
Manufacturer Info: 57454300
On Tue, Oct 7, 2014 at 11:16 AM, David Li <[email protected]> wrote:
> Hi Vicky,
> Yes, my tcsd is up and running.
> I downloaded tm-tools-1.3.8. The README file says I need to run:
>
> $ sh ./bootstrap.sh
>
> But I don't see bootstrap.sh script after unpacking the tar ball. Did I
> miss something?
>
> David
>
>
> On Mon, Oct 6, 2014 at 9:53 PM, Hon Ching Lo <[email protected]> wrote:
>
>> Hi David,
>>
>>
>> I would do the following:
>> 1) check to see if the tcsd process is running: ps -ef | grep tcsd
>> 2) download trousers-tpm-tools; compile and build it. Then, you can run
>> commands such as: tpm_version and tpm_takeownership etc.
>>
>>
>> Vicky
>>
>> On Mon, Oct 6, 2014 at 7:01 PM, David Li <[email protected]> wrote:
>>
>>> Hi Vicki,
>>>
>>> I managed to get tcsd started. But looking at the /var/log/messages, I
>>> am not sure if it's working properly on my embedded system:
>>>
>>> Oct 6 21:46:43 box local5.warn TCSD TDDL[1297]: TrouSerS ioctl: (25)
>>> Inappropriate ioctl for device
>>> Oct 6 21:46:43 box local5.info TCSD TDDL[1297]: TrouSerS Falling back
>>> to Read/Write device support.
>>> Oct 6 21:46:43 box local5.warn TCSD[1297]: TrouSerS Failed IPv6 socket:
>>> Address family not supported by protocol
>>> Oct 6 21:46:43 box local5.info TCSD[1300]: TrouSerS trousers 0.3.13:
>>> TCSD up and running.
>>>
>>> David
>>>
>>> On Thu, Oct 2, 2014 at 6:50 PM, Hon Ching Lo <[email protected]>
>>> wrote:
>>>
>>>> Hi David,
>>>>
>>>>
>>>> I've just recently become the maintainer for TrouSers. I primarily
>>>> test it on both RHEL and SLES. AFAIK, there isn't a complete list of
>>>> required steps on
>>>> all different distros.
>>>>
>>>>
>>>> Vicky
>>>>
>>>> On Thu, Oct 2, 2014 at 7:52 PM, David Li <[email protected]> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I am running tcsd in a customized Linux environment so there might be
>>>>> something different from standard RH or CentOS.
>>>>>
>>>>> I have already discovered that it requires an tss user in the tss
>>>>> group. I have also found that the /usr/local/etc/tcsd.conf needs to be
>>>>> owned by tss:tss too.
>>>>>
>>>>> Is there a complete list of required steps to start tcsd?
>>>>>
>>>>> David
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
>>>>> Reports
>>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>>>>
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>>>>> _______________________________________________
>>>>> TrouSerS-users mailing list
>>>>> [email protected]
>>>>> https://lists.sourceforge.net/lists/listinfo/trousers-users
>>>>>
>>>>>
>>>>
>>>
>>
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
TrouSerS-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/trousers-users
