[apache/incubator-teaclave] GPG error: The following signatures couldn't be verified (#471)

2021-01-26 Thread master-davidlee
when I run the last  command 
![image](https://user-images.githubusercontent.com/49427668/105863271-adc28a00-602b-11eb-83ef-1d0dfc5c6348.png)
I met an error 
![image](https://user-images.githubusercontent.com/49427668/105863327-bfa42d00-602b-11eb-86fd-9be814479865.png)


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

Re: [apache/incubator-teaclave] GPG error: The following signatures couldn't be verified (#471)

2021-01-26 Thread master-davidlee
And I use these 2 steps fixed it 
1. the first step is to take note of the public key, for example, there is the 
78BD65473CB3BD13
![image](https://user-images.githubusercontent.com/49427668/105863541-f417e900-602b-11eb-8b12-c5cb368edde7.png)
2. sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 
(public_key)
Then it should be fixed



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

Re: [apache/incubator-teaclave] C client SDK (#470)

2021-01-26 Thread Mingshen Sun
Thanks for the review! Merged.

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

Re: [apache/incubator-teaclave] C client SDK (#470)

2021-01-26 Thread Mingshen Sun
Merged #470 into master.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/470#event-4252163790

Re: [apache/incubator-teaclave] GPG error: The following signatures couldn't be verified (#471)

2021-01-26 Thread Mingshen Sun
I think this command will add the public key of Intel.  `$ wget -qO - 
https://download.01.org/intel-sgx/sgx_repo/ubuntu/intel-sgx-deb.key | sudo 
apt-key add -` . What did I missing? Any errors when adding the key for you?

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

Re: [apache/incubator-teaclave] some problem about sgx_ecdsa attentation (#469)

2021-01-26 Thread Mingshen Sun
Hi @xglreal, thanks for your question! Sorry, I couldn't help you if you cannot 
provide more detailed information. Like how did you setup the environment?

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

[apache/incubator-teaclave] Remove unused commented ubuntu 16.04 pipeline (#472)

2021-01-26 Thread Mingshen Sun
## Description

Remove unused commented ubuntu 16.04 pipeline
You can view, comment on, or merge this pull request online at:

  https://github.com/apache/incubator-teaclave/pull/472

-- Commit Summary --

  * Remove commented ubuntu 16.04 pipeline

-- File Changes --

M .drone.yml (275)

-- Patch Links --

https://github.com/apache/incubator-teaclave/pull/472.patch
https://github.com/apache/incubator-teaclave/pull/472.diff

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


[apache/incubator-teaclave] Start to use GitHub Action (#473)

2021-01-26 Thread Mingshen Sun
## Description

Previously we have in-house CI (Drone CI). However, this is not public to all 
contributors. This PR is start to use GitHub Action.  There are three jobs: 
building/testing in simulation mode, code format, code linting. It takes about 
30 minutes in GitHub Action. Though it's slow. It's better than nothing.

Since GitHub Action doesn't have SGX machine, we will consider to use 
self-host runners for GitHub later.
You can view, comment on, or merge this pull request online at:

  https://github.com/apache/incubator-teaclave/pull/473

-- Commit Summary --

  * Start to use GitHub Action

-- File Changes --

A .github/workflows/ci.yml (87)

-- Patch Links --

https://github.com/apache/incubator-teaclave/pull/473.patch
https://github.com/apache/incubator-teaclave/pull/473.diff

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


Re: [apache/incubator-teaclave] Start to use GitHub Action (#473)

2021-01-26 Thread Mingshen Sun
Here is a GitHub CI result from my repo: 
https://github.com/mssun/incubator-mesatee/actions/runs/513650440

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

Re: [apache/incubator-teaclave] Remove unused commented ubuntu 16.04 pipeline (#472)

2021-01-26 Thread Mingshen Sun
Merged #472 into master.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/472#event-4253407526

Re: [apache/incubator-teaclave] Start to use GitHub Actions (#473)

2021-01-26 Thread Mingshen Sun
Merged #473 into master.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/473#event-4253444904

Re: [apache/incubator-teaclave] GPG error: The following signatures couldn't be verified (#471)

2021-01-26 Thread master-davidlee
I remember this command returned OK, but the error still occurred but I have 
fixed it. Can you take look at the other error#463. It bothers me many days 
Thanks

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

Re: [apache/incubator-teaclave] Execute builtin_echo.py error (#463)

2021-01-26 Thread Mingshen Sun
Can you set the env var `export TEACLAVE_LOG=debug`? Then start the services 
with `docker-compose`. Please paste log here. Thanks.

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

Re: [apache/incubator-teaclave] Execute builtin_echo.py error (#463)

2021-01-26 Thread master-davidlee
![image](https://user-images.githubusercontent.com/49427668/105930272-569cd380-6084-11eb-80cb-be976ac3d886.png)
![image](https://user-images.githubusercontent.com/49427668/105930317-69170d00-6084-11eb-85e5-6e6c4abe36fd.png)
![image](https://user-images.githubusercontent.com/49427668/105930337-759b6580-6084-11eb-98c8-decc0fef7b08.png)
![image](https://user-images.githubusercontent.com/49427668/105930362-82b85480-6084-11eb-80b5-0510bcb6a856.png)
![image](https://user-images.githubusercontent.com/49427668/105930393-8ea41680-6084-11eb-9309-277468bd2a9c.png)
![image](https://user-images.githubusercontent.com/49427668/105930416-982d7e80-6084-11eb-8f01-5fdcda2bb80a.png)


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

Re: [apache/incubator-teaclave] Execute builtin_echo.py error (#463)

2021-01-26 Thread master-davidlee
it looks like right at the beginning, but something wrong after a while. Can 
you help me with that?  Thanks!

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

Re: [apache/incubator-teaclave] Execute builtin_echo.py error (#463)

2021-01-26 Thread Mingshen Sun
Seems that there're connection issues between containers (services) started by 
`docker-compose`. I don't know why.

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

Re: [apache/incubator-teaclave] Execute builtin_echo.py error (#463)

2021-01-26 Thread master-davidlee
Ok, I will try in the real TEE with another PC.And can I load my own machine 
learning model file use Teaclave?

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

Re: [apache/incubator-teaclave] Execute builtin_echo.py error (#463)

2021-01-26 Thread Mingshen Sun
> And can I load my own machine learning model file use Teaclave?

Sorry, I don't know how to answer this question. It's too general. Can you give 
me more detailed information?

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

Re: [apache/incubator-teaclave] Execute builtin_echo.py error (#463)

2021-01-26 Thread master-davidlee
Current Teaclave supports any python machine learning modules?  can I load a 
pickle-dumped machine learning model file in Teaclave and run it?
`import numpy as np

class Linear_Regression:
def __init__(self):
self._w = None

def fit(self, X, y, lr=0.01, epsilon=0.01, epoch=1000):
#训练数据
#将输入的X,y转换为numpy数组
X, y = np.asarray(X, np.float32), np.asarray(y, np.float32)
#给X增加一列常数项
X=np.hstack((X,np.ones((X.shape[0],1
#初始化w
self._w = np.zeros((X.shape[1],1)) 

for _ in range(epoch):
#随机选择一组样本计算梯度
random_num=np.random.choice(len(X))
x_random=X[random_num].reshape(1,2)
y_random=y[random_num]

gradient=(x_random.T)*(np.dot(x_random,self._w)-y_random)

#如果收敛,那么停止迭代
if (np.abs(self._w-lr*gradient)https://github.com/apache/incubator-teaclave/issues/463#issuecomment-768006278

[apache/incubator-teaclave] Add protected_fs feature to the crypto crate (#474)

2021-01-26 Thread Mingshen Sun
## Description

The `protected_fs_rs` crate should be used for the crypto on demand. For 
example, current client SDK doesn't provide any API related with the 
`protected_fs_rs`. With this PR, users can compile/use the Rust/C client SDK in 
other platform.

Teaclave File (i.e., `protected_fs_rs`) may be needed for the client SDK in the 
near future, but currently it cannot be compiled to other platform like 
`aarch64-apple-ios`.
You can view, comment on, or merge this pull request online at:

  https://github.com/apache/incubator-teaclave/pull/474

-- Commit Summary --

  * Add protected_fs feature

-- File Changes --

M cli/Cargo.toml (2)
M crypto/Cargo.toml (4)
M crypto/src/lib.rs (25)
M types/Cargo.toml (10)
M types/src/staged_file.rs (28)

-- Patch Links --

https://github.com/apache/incubator-teaclave/pull/474.patch
https://github.com/apache/incubator-teaclave/pull/474.diff

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