Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basic Tutorial not working #24

Open
jbkoh opened this issue Sep 24, 2019 · 6 comments
Open

Basic Tutorial not working #24

jbkoh opened this issue Sep 24, 2019 · 6 comments

Comments

@jbkoh
Copy link

jbkoh commented Sep 24, 2019

Hi,

I am trying to learn WAVE for my projects. I just downloaded the release version 0.4.0, and ran ./waved to follow the instruction in README.md. However, it showed "Illegal instruction". I tried both with/without sudo. My OS is Ubuntu 18.04. I'd appreciate if you have any clue about this.

Thanks in advance.

@gtfierro
Copy link
Contributor

I think you are better off building from source, or trying different builds. There are a number of things that have changed between 0.4.0 and the current commit. On my fork I've tried to automate some builds that you can try (v0.5-alpha, for amd-linux64), but I also have a Makefile that you can use to see the instructions for building. You'll need godep installed to handle the dependencies.

@jbkoh jbkoh changed the title In waved, "Illegal instruction" Basic Tutorial not working Sep 24, 2019
@jbkoh
Copy link
Author

jbkoh commented Sep 25, 2019

@gtfierro Thanks for the advice. I successfully compiled waved and wv from the source code based on your Makefile. Now the entire Tutorial is working.

There is a small fix for the usability. waved and wv use different ports by default. I had to manually change the port in wave.toml in the release version.

Also, in the default wave.toml, "https://standalone.storage.bwave.io/v1" is defined for storage. What is it for and is it okay to leave it as it is?

@gtfierro
Copy link
Contributor

I guess those got changed at some point... they certainly used to be the same!

The storage is covered in detail in the USENIX Security paper. It is where WAVE stores attestations. The default value should work fine

@jbkoh
Copy link
Author

jbkoh commented Sep 25, 2019

Does it mean that all the attestations that I request are stored in https://standalone.storage.bwave.io/v1?

What should I do if I want to run a database by myself?

Also, currently storage.default seems to be activated and storage.vldm is commented out. What are the differences between them?

@gtfierro
Copy link
Contributor

Yes, they are all stored there. You can dig into the storage/ folder if you want to run a storage server yourself, but its likely not worth the trouble.

The paper documents the differences between the default and VLDM storage. The default one is activated so that you don't have to worry about this.

@jbkoh
Copy link
Author

jbkoh commented Sep 25, 2019

  • I can't find VLDM in the paper. Is it same as ULDM?
  • What is the "default" server? Sorry I couldn't locate its description in the paper either. I looked up evaluation to see how the authors evaluate VLDM with a baseline (which I thought was the default one,) but it's not there. Maybe I missed it as I just skimmed through it.
  • What's the plan to make the storage deployable? As a user, I'd prefer fully controlling my deployment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants