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

DCAP deployment improvement #698

Open
henrysun007 opened this issue Jun 7, 2023 · 2 comments
Open

DCAP deployment improvement #698

henrysun007 opened this issue Jun 7, 2023 · 2 comments
Labels

Comments

@henrysun007
Copy link
Contributor

Motivation & problem statement

The deployment for DCAP attestation is not well supported. runtime.config.toml and build.config.toml have to be modified manually. There are three runtime.config.tomls in config, docker and tests/fixtures respectively.

@henrysun007
Copy link
Contributor Author

henrysun007 commented Jun 14, 2023

Besides, there are many issues about the attestation:
#667
#634
#548
#469
#459
#452

More documents are needed about the attestation. The attesation also needs improvement.

@hiroki-chen
Copy link
Contributor

Hi @henrysun007, I noticed that the port for attestation is hardcoded as 443 in attestation/src/service.rs:

let addrs = url.socket_addrs(|| match url.scheme() {
    "https" => Some(443), // Fixed port.
    _ => None,
})?;

Is it possible for us to change the binding port? Sometimes 443 on the local machine is already in use for other services so that we cannot deploy DCAP.

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

No branches or pull requests

2 participants