Skip to content

Commit

Permalink
IDs not in link files...
Browse files Browse the repository at this point in the history
I didn't find the IDs in the link files so had to change the directions to accommodate.  

Discard this PR if this is because my in-toto software is out of date.  (However, if this is so perhaps change the directions to use * in the cp commands in place of the keyIDs...
  • Loading branch information
JustinCappos committed Mar 22, 2017
1 parent 20b8b30 commit 1a496df
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions demo/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -160,10 +160,10 @@ It's time to release our software now.
### Verify final product (client)
Let's first copy all relevant files into the `final_product` that is
our software package `demo-project.tar.gz` and the related metadata files `root.layout`,
`clone.[Bob's keyid].link`, `update-version.[Bob's keyid].link` and `package.[Carl's keyid].link`:
`clone.link`, `update-version.link` and `package.link`:
```shell
cd ..
cp owner_alice/root.layout functionary_bob/clone.0c6c50a1.link functionary_bob/update-version.0c6c50a1.link functionary_carl/package.c1ae1e51.link functionary_carl/demo-project.tar.gz final_product/
cp owner_alice/root.layout functionary_bob/clone.link functionary_bob/update-version.link functionary_carl/package.link functionary_carl/demo-project.tar.gz final_product/
```
And now run verification on behalf of the client:
```shell
Expand Down Expand Up @@ -248,4 +248,4 @@ The same script can be used to sequentially execute all commands listed above. J
```shell
# In the demo directory
python run_demo.py
```
```

0 comments on commit 1a496df

Please sign in to comment.