[apache/incubator-teaclave] DCAP deployment improvement (Issue #698)

[He Sun <no...@github.com.INVALID>]

<!--
  Thank you for suggesting an idea to make Teaclave better.
  Please fill in as much of the template below as you're able.
-->

### 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.toml`s in `config`, `docker` and `tests/fixtures` respectively.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/698
You are receiving this because you are subscribed to this thread.

Message ID: <ap...@github.com>

Re: [apache/incubator-teaclave] DCAP deployment improvement (Issue #698)

["Hiroki (Haobin) Chen" <no...@github.com.INVALID>]

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

```rust
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.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/698#issuecomment-1633510398
You are receiving this because you are subscribed to this thread.

Message ID: <ap...@github.com>

Re: [apache/incubator-teaclave] DCAP deployment improvement (Issue #698)

[He Sun <no...@github.com.INVALID>]

Besides, there are many issues about the DCAP attestation:
#667

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/698#issuecomment-1590539476
You are receiving this because you are subscribed to this thread.

Message ID: <ap...@github.com>