[PR] Create 2024-05-31-podling-teaclave-report-june-2024.md [incubator-teaclave-website]
DemesneGH opened a new pull request, #25: URL: https://github.com/apache/incubator-teaclave-website/pull/25 Will sync to https://cwiki.apache.org/confluence/display/INCUBATOR/June2024#teaclave before 05 June. If you have any comments please feel free to reply on this PR, thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] dependabot[bot] opened a new pull request, #24: Bump semver from 5.7.1 to 5.7.2 in /site
dependabot[bot] opened a new pull request, #24: URL: https://github.com/apache/incubator-teaclave-website/pull/24 Bumps [semver](https://github.com/npm/node-semver) from 5.7.1 to 5.7.2. Release notes Sourced from https://github.com/npm/node-semver/releases;>semver's releases. v5.7.2 https://github.com/npm/node-semver/compare/v5.7.1...v5.7.2;>5.7.2 (2023-07-10) Bug Fixes https://github.com/npm/node-semver/commit/2f8fd41487acf380194579ecb6f8b1bbfe116be0;>2f8fd41 https://redirect.github.com/npm/node-semver/pull/585;>#585 better handling of whitespace (https://redirect.github.com/npm/node-semver/issues/585;>#585) (https://github.com/joaomoreno;>@joaomoreno, https://github.com/lukekarrys;>@lukekarrys) Changelog Sourced from https://github.com/npm/node-semver/blob/v5.7.2/CHANGELOG.md;>semver's changelog. https://github.com/npm/node-semver/compare/v5.7.1...v5.7.2;>5.7.2 (2023-07-10) Bug Fixes https://github.com/npm/node-semver/commit/2f8fd41487acf380194579ecb6f8b1bbfe116be0;>2f8fd41 https://redirect.github.com/npm/node-semver/pull/585;>#585 better handling of whitespace (https://redirect.github.com/npm/node-semver/issues/585;>#585) (https://github.com/joaomoreno;>@joaomoreno, https://github.com/lukekarrys;>@lukekarrys) 5.7 Add minVersion method 5.6 Move boolean loose param to an options object, with backwards-compatibility protection. Add ability to opt out of special prerelease version handling with the includePrerelease option flag. 5.5 Add version coercion capabilities 5.4 Add intersection checking 5.3 Add minSatisfying method 5.2 Add prerelease(v) that returns prerelease components 5.1 Add Backus-Naur for ranges Remove excessively cute inspection methods 5.0 Remove AMD/Browserified build artifacts Fix ltr and gtr when using the * range Fix for range * with a prerelease identifier Commits https://github.com/npm/node-semver/commit/f8cc313550691a50d9662d8c94f0c033717efd7d;>f8cc313 chore: release 5.7.2 https://github.com/npm/node-semver/commit/2f8fd41487acf380194579ecb6f8b1bbfe116be0;>2f8fd41 fix: better handling of whitespace (https://redirect.github.com/npm/node-semver/issues/585;>#585) https://github.com/npm/node-semver/commit/deb5ad51bf58868fa243c1683775305fe9e0e365;>deb5ad5 chore: @npmcli/template-osshttps://github.com/4;>@4.16.0 See full diff in https://github.com/npm/node-semver/compare/v5.7.1...v5.7.2;>compare view Maintainer changes This version was pushed to npm by https://www.npmjs.com/~lukekarrys;>lukekarrys, a new releaser for semver since your current version. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/incubator-teaclave-website/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go
[GitHub] [incubator-teaclave-website] henrysun007 merged pull request #23: Update the official website
henrysun007 merged PR #23: URL: https://github.com/apache/incubator-teaclave-website/pull/23 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] henrysun007 opened a new pull request, #23: Update the official website
henrysun007 opened a new pull request, #23: URL: https://github.com/apache/incubator-teaclave-website/pull/23 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] dependabot[bot] opened a new pull request, #22: Bump http-cache-semantics from 4.1.0 to 4.1.1 in /site
dependabot[bot] opened a new pull request, #22: URL: https://github.com/apache/incubator-teaclave-website/pull/22 Bumps [http-cache-semantics](https://github.com/kornelski/http-cache-semantics) from 4.1.0 to 4.1.1. Commits https://github.com/kornelski/http-cache-semantics/commit/24496504352199caf360d1b4d4a01efdc8a7249e;>2449650 Update mocha https://github.com/kornelski/http-cache-semantics/commit/560b2d8ef452bbba20ffed69dc155d63ac757b74;>560b2d8 Don't use regex to trim whitespace https://github.com/kornelski/http-cache-semantics/commit/b1bdb92638426fab978f31e1330b6833015cabf0;>b1bdb92 Remove linting package zoo https://github.com/kornelski/http-cache-semantics/commit/c20dc7eeca608339143857953ee7ed9343fe6d3d;>c20dc7e Cache 308 See full diff in https://github.com/kornelski/http-cache-semantics/compare/v4.1.0...v4.1.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/incubator-teaclave-website/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] superajun-wsj merged pull request #21: Add JavaEnclave Download link
superajun-wsj merged PR #21: URL: https://github.com/apache/incubator-teaclave-website/pull/21 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] henrysun007 merged pull request #20: Upload meetup notes
henrysun007 merged PR #20: URL: https://github.com/apache/incubator-teaclave-website/pull/20 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] dependabot[bot] opened a new pull request, #19: Bump luxon from 1.24.1 to 1.28.1 in /site
dependabot[bot] opened a new pull request, #19: URL: https://github.com/apache/incubator-teaclave-website/pull/19 Bumps [luxon](https://github.com/moment/luxon) from 1.24.1 to 1.28.1. Changelog Sourced from https://github.com/moment/luxon/blob/master/CHANGELOG.md;>luxon's changelog. Changelog 3.2.0 (2022-12-29) Allow timeZone to be specified as an intl option Fix for diff's handling of end-of-month when crossing leap years (https://github-redirect.dependabot.com/moment/luxon/issues/1340;>#1340) Add Interval.toLocaleString() (https://github-redirect.dependabot.com/moment/luxon/issues/1320;>#1320) 3.1.1 (2022-11-28) Add Settings.twoDigitCutoffYear 3.1.0 (2022-10-31) Add Duration.rescale 3.0.4 (2022-09-24) Fix quarters in diffs (https://github-redirect.dependabot.com/moment/luxon/issues/1279;>#1279) Export package.json in package (https://github-redirect.dependabot.com/moment/luxon/issues/1239;>#1239) 3.0.2 (2022-08-28) Lots of doc changes Added DateTime.expandFormat Added support for custom conversion matrices in Durations 3.0.1 (2022-07-09) Add DateTime.parseFormatForOpts 3.0.0 (2022-07-09) Add default as an option for specifying a zone, and change system to really mean the system zone (breaking change) 2.5.0 (2022-07-09) Support for ESM-style node imports Fix Wednesday parsing for RFC 850 strings Increase number of digits allowed in ISO durations 2.4.0 (2022-05-08) Add support for parsing the ISO zone extension, like 2022-05-08T20:42:00.000-04:00[America/New_York] Add an extendedZone option to toISO() and toISOTime Improvements to DateTime.isInDST() Fix for parsing in Vietnames (and probably other languages) 2.3.2 (2022-04-17) ... (truncated) Commits https://github.com/moment/luxon/commit/16a1aa3ee95a80a7e9c4ccbc740c378064449ec4;>16a1aa3 bump to 1.38.1 https://github.com/moment/luxon/commit/612e0c778d2dedb947f3e5160c46601688ea4959;>612e0c7 fix rfc2822 regex https://github.com/moment/luxon/commit/9dcec8c32f76d9dac295d73b42e3958643a883ae;>9dcec8c bump to 1.28.0 https://github.com/moment/luxon/commit/a0f42a284330781df0bbef1fcb9e47f09575b818;>a0f42a2 Fixed small typo (https://github-redirect.dependabot.com/moment/luxon/issues/952;>#952) https://github.com/moment/luxon/commit/307b13584937452f60206a8d03382ebbc658e447;>307b135 Docs typo on dst weirdness (https://github-redirect.dependabot.com/moment/luxon/issues/962;>#962) https://github.com/moment/luxon/commit/1f99fdd36c60a5c93cd778861515e2f369e27ea5;>1f99fdd fix ISO year-ordinal strings with offsets (https://github-redirect.dependabot.com/moment/luxon/issues/966;>#966) https://github.com/moment/luxon/commit/e0c8f874304cd4ecc3944bdcff3d8f8c27102a18;>e0c8f87 .toSeconds() returns seconds.milliseconds (https://github-redirect.dependabot.com/moment/luxon/issues/944;>#944) https://github.com/moment/luxon/commit/2d66ce457b6207321cf3d230ccefbcee990e7e5d;>2d66ce4 Clarify toFormat docs (https://github-redirect.dependabot.com/moment/luxon/issues/938;>#938) https://github.com/moment/luxon/commit/043f2b9a217a855b760a04ea3a25015ff6d83a42;>043f2b9 bump to 1.27.0 https://github.com/moment/luxon/commit/6ae05240092473ef4499c346c6b660c34c2d02fa;>6ae0524 update node install instructions. Closes https://github-redirect.dependabot.com/moment/luxon/issues/682;>#682 Additional commits viewable in https://github.com/moment/luxon/compare/1.24.1...1.28.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this m
[GitHub] [incubator-teaclave-website] henrysun007 merged pull request #18: Update contributors
henrysun007 merged PR #18: URL: https://github.com/apache/incubator-teaclave-website/pull/18 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] henrysun007 commented on pull request #18: Update contributors
henrysun007 commented on PR #18: URL: https://github.com/apache/incubator-teaclave-website/pull/18#issuecomment-1375351885 @mssun I merged this PR as you did not respond for days. The website is also updated. Please tell me if you have any suggestions. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] dependabot[bot] opened a new pull request, #17: Bump express from 4.17.1 to 4.18.2 in /site
dependabot[bot] opened a new pull request, #17: URL: https://github.com/apache/incubator-teaclave-website/pull/17 Bumps [express](https://github.com/expressjs/express) from 4.17.1 to 4.18.2. Release notes Sourced from https://github.com/expressjs/express/releases;>express's releases. 4.18.2 Fix regression routing a large stack in a single route deps: body-parser@1.20.1 deps: qs@6.11.0 perf: remove unnecessary object clone deps: qs@6.11.0 4.18.1 Fix hanging on large stack of sync routes 4.18.0 Add root option to res.download Allow options without filename in res.download Deprecate string and non-integer arguments to res.status Fix behavior of null/undefined as maxAge in res.cookie Fix handling very large stacks of sync middleware Ignore Object.prototype values in settings through app.set/app.get Invoke default with same arguments as types in res.format Support proper 205 responses using res.send Use http-errors for res.format error deps: body-parser@1.20.0 Fix error message for json parse whitespace in strict Fix internal error when inflated body exceeds limit Prevent loss of async hooks context Prevent hanging when request already read deps: depd@2.0.0 deps: http-errors@2.0.0 deps: on-finished@2.4.1 deps: qs@6.10.3 deps: raw-body@2.5.1 deps: cookie@0.5.0 Add priority option Fix expires option to reject invalid dates deps: depd@2.0.0 Replace internal eval usage with Function constructor Use instance methods on process to check for listeners deps: finalhandler@1.2.0 Remove set content headers that break response deps: on-finished@2.4.1 deps: statuses@2.0.1 deps: on-finished@2.4.1 Prevent loss of async hooks context deps: qs@6.10.3 deps: send@0.18.0 Fix emitted 416 error missing headers property Limit the headers removed for 304 response deps: depd@2.0.0 deps: destroy@1.2.0 deps: http-errors@2.0.0 deps: on-finished@2.4.1 ... (truncated) Changelog Sourced from https://github.com/expressjs/express/blob/master/History.md;>express's changelog. 4.18.2 / 2022-10-08 Fix regression routing a large stack in a single route deps: body-parser@1.20.1 deps: qs@6.11.0 perf: remove unnecessary object clone deps: qs@6.11.0 4.18.1 / 2022-04-29 Fix hanging on large stack of sync routes 4.18.0 / 2022-04-25 Add root option to res.download Allow options without filename in res.download Deprecate string and non-integer arguments to res.status Fix behavior of null/undefined as maxAge in res.cookie Fix handling very large stacks of sync middleware Ignore Object.prototype values in settings through app.set/app.get Invoke default with same arguments as types in res.format Support proper 205 responses using res.send Use http-errors for res.format error deps: body-parser@1.20.0 Fix error message for json parse whitespace in strict Fix internal error when inflated body exceeds limit Prevent loss of async hooks context Prevent hanging when request already read deps: depd@2.0.0 deps: http-errors@2.0.0 deps: on-finished@2.4.1 deps: qs@6.10.3 deps: raw-body@2.5.1 deps: cookie@0.5.0 Add priority option Fix expires option to reject invalid dates deps: depd@2.0.0 Replace internal eval usage with Function constructor Use instance methods on process to check for listeners deps: finalhandler@1.2.0 Remove set content headers that break response deps: on-finished@2.4.1 deps: statuses@2.0.1 deps: on-finished@2.4.1 Prevent loss of async hooks context deps: qs@6.10.3 deps: send@0.18.0 ... (truncated) Commits https://github.com/expressjs/express/commit/8368dc178af16b91b576c4c1d135f701a0007e5d;>8368dc1 4.18.2 https://github.com/expressjs/express/commit/61f40491222dbede653b9938e6a4676f187aab44;>61f4049 docs: replace Freenode with Libera Chat https://github.com/expressjs/express/commit/bb7907b932afe3a19236a642f6054b6c8f7349a0;>bb7907b build: Node.js@18.10 https://github.com/expressjs/express/commit/f56ce73186e885a938bfdb3d3d1005a58e6ae12b;>f56ce73 build: supertest@6.3.0 https://github.com/expressjs/express/commit/24b3dc551670ac4fb0cd5a2bd5ef643c9525e60f;>24b3dc5 deps: qs@6.11.0 https://github.com/expressjs/express/commit/689d175b8b39d8860b81d723233fb83d15201827;>689d175 deps: body-parser@1.20.1 https://github.com/expressjs/express/commit/340be0f79afb9b3176afb76235aa7f92acbd5050;>340be0f build: eslint@8.24.0 https://github.com/expressjs/express/commit/33e8dc303af9277f8a7e4f46abfdcb5e72f6797b;>33e8dc3 docs: use Node.js name style https:
[GitHub] [incubator-teaclave-website] dependabot[bot] opened a new pull request, #16: Bump qs from 6.5.2 to 6.5.3 in /site
dependabot[bot] opened a new pull request, #16: URL: https://github.com/apache/incubator-teaclave-website/pull/16 Bumps [qs](https://github.com/ljharb/qs) from 6.5.2 to 6.5.3. Changelog Sourced from https://github.com/ljharb/qs/blob/main/CHANGELOG.md;>qs's changelog. 6.5.3 [Fix] parse: ignore __proto__ keys (https://github-redirect.dependabot.com/ljharb/qs/issues/428;>#428) [Fix] utils.merge`: avoid a crash with a null target and a truthy non-array source [Fix] correctly parse nested arrays [Fix] stringify: fix a crash with strictNullHandling and a custom filter/serializeDate (https://github-redirect.dependabot.com/ljharb/qs/issues/279;>#279) [Fix] utils: merge: fix crash when source is a truthy primitive no options are provided [Fix] when parseArrays is false, properly handle keys ending in [] [Fix] fix for an impossible situation: when the formatter is called with a non-string value [Fix] utils.merge: avoid a crash with a null target and an array source [Refactor] utils: reduce observable [[Get]]s [Refactor] use cached Array.isArray [Refactor] stringify: Avoid arr = arr.concat(...), push to the existing instance (https://github-redirect.dependabot.com/ljharb/qs/issues/269;>#269) [Refactor] parse: only need to reassign the var once [Robustness] stringify: avoid relying on a global undefined (https://github-redirect.dependabot.com/ljharb/qs/issues/427;>#427) [readme] remove travis badge; add github actions/codecov badges; update URLs [Docs] Clean up license text so it’s properly detected as BSD-3-Clause [Docs] Clarify the need for arrayLimit option [meta] fix README.md (https://github-redirect.dependabot.com/ljharb/qs/issues/399;>#399) [meta] add FUNDING.yml [actions] backport actions from main [Tests] always use String(x) over x.toString() [Tests] remove nonexistent tape option [Dev Deps] backport from main Commits https://github.com/ljharb/qs/commit/298bfa55d6db00ddea78dd0333509aadf9bb3077;>298bfa5 v6.5.3 https://github.com/ljharb/qs/commit/ed0f5dcbef4b168a8ae299d78b1e4a2e9b1baf1f;>ed0f5dc [Fix] parse: ignore __proto__ keys (https://github-redirect.dependabot.com/ljharb/qs/issues/428;>#428) https://github.com/ljharb/qs/commit/691e739cfa40cd42604dc05a54e6154371a429ab;>691e739 [Robustness] stringify: avoid relying on a global undefined (https://github-redirect.dependabot.com/ljharb/qs/issues/427;>#427) https://github.com/ljharb/qs/commit/1072d57d38a690e1ad7616dced44390bffedcbb2;>1072d57 [readme] remove travis badge; add github actions/codecov badges; update URLs https://github.com/ljharb/qs/commit/12ac1c403aaa04d1a34844f514ed9f9abfb76e64;>12ac1c4 [meta] fix README.md (https://github-redirect.dependabot.com/ljharb/qs/issues/399;>#399) https://github.com/ljharb/qs/commit/0338716b09fdbd4711823eeb0a14e556a2498e7a;>0338716 [actions] backport actions from main https://github.com/ljharb/qs/commit/5639c20ce0a7c1332200a3181339331483e5a3a1;>5639c20 Clean up license text so it’s properly detected as BSD-3-Clause https://github.com/ljharb/qs/commit/51b8a0b1b213596dd1702b837f5e7dec2229793d;>51b8a0b add FUNDING.yml https://github.com/ljharb/qs/commit/45f675936e742d92fac8d4dae5cfc385c576a977;>45f6759 [Fix] fix for an impossible situation: when the formatter is called with a no... https://github.com/ljharb/qs/commit/f814a7f8f2af059f8158f7e4b2bf8b46aeb62cd3;>f814a7f [Dev Deps] backport from main Additional commits viewable in https://github.com/ljharb/qs/compare/v6.5.2...v6.5.3;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this maj
[GitHub] [incubator-teaclave-website] dependabot[bot] opened a new pull request, #15: Bump decode-uri-component from 0.2.0 to 0.2.2 in /site
dependabot[bot] opened a new pull request, #15: URL: https://github.com/apache/incubator-teaclave-website/pull/15 Bumps [decode-uri-component](https://github.com/SamVerschueren/decode-uri-component) from 0.2.0 to 0.2.2. Release notes Sourced from https://github.com/SamVerschueren/decode-uri-component/releases;>decode-uri-component's releases. v0.2.2 Prevent overwriting previously decoded tokens 980e0bf https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.1...v0.2.2;>https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.1...v0.2.2 v0.2.1 Switch to GitHub workflows 76abc93 Fix issue where decode throws - fixes https://github-redirect.dependabot.com/SamVerschueren/decode-uri-component/issues/6;>#6 746ca5d Update license (https://github-redirect.dependabot.com/SamVerschueren/decode-uri-component/issues/1;>#1) 486d7e2 Tidelift tasks a650457 Meta tweaks 66e1c28 https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.1;>https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.1 Commits https://github.com/SamVerschueren/decode-uri-component/commit/a0eea469d26eb0df668b081672cdb9581feb78eb;>a0eea46 0.2.2 https://github.com/SamVerschueren/decode-uri-component/commit/980e0bf09b64d94f1aa79012f895816c30ffd152;>980e0bf Prevent overwriting previously decoded tokens https://github.com/SamVerschueren/decode-uri-component/commit/3c8a373dd4837e89b3f970e01295dd03e1405a33;>3c8a373 0.2.1 https://github.com/SamVerschueren/decode-uri-component/commit/76abc939783fe3900fadb7d384a74d324d5557f3;>76abc93 Switch to GitHub workflows https://github.com/SamVerschueren/decode-uri-component/commit/746ca5dcb6667c5d364e782d53c542830e4c10b9;>746ca5d Fix issue where decode throws - fixes https://github-redirect.dependabot.com/SamVerschueren/decode-uri-component/issues/6;>#6 https://github.com/SamVerschueren/decode-uri-component/commit/486d7e26d3a8c0fbe860fb651fe1bc98c2f2be30;>486d7e2 Update license (https://github-redirect.dependabot.com/SamVerschueren/decode-uri-component/issues/1;>#1) https://github.com/SamVerschueren/decode-uri-component/commit/a65045724e6234acef87f31da499d4807b20b134;>a650457 Tidelift tasks https://github.com/SamVerschueren/decode-uri-component/commit/66e1c2834c0e189201cb65196ec3101372459b02;>66e1c28 Meta tweaks See full diff in https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.2;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for t
[GitHub] [incubator-teaclave-website] dependabot[bot] opened a new pull request, #13: Bump ansi-html and webpack-dev-server in /site
dependabot[bot] opened a new pull request, #13: URL: https://github.com/apache/incubator-teaclave-website/pull/13 Removes [ansi-html](https://github.com/Tjatse/ansi-html). It's no longer used after updating ancestor dependency [webpack-dev-server](https://github.com/webpack/webpack-dev-server). These dependencies need to be updated together. Removes `ansi-html` Updates `webpack-dev-server` from 3.11.0 to 3.11.3 Release notes Sourced from https://github.com/webpack/webpack-dev-server/releases;>webpack-dev-server's releases. v3.11.3 https://github.com/webpack/webpack-dev-server/compare/v3.11.2...v3.11.3;>3.11.3 (2021-11-08) Bug Fixes replace ansi-html with ansi-html-community (https://github-redirect.dependabot.com/webpack/webpack-dev-server/issues/4011;>#4011) (https://github.com/webpack/webpack-dev-server/commit/4fef67b997a2bd09b46beb779c185ad8f85e3e1a;>4fef67b) v3.11.2 https://github.com/webpack/webpack-dev-server/compare/v3.11.1...v3.11.2;>3.11.2 (2021-01-13) Bug Fixes cli arguments for serve command (https://github.com/webpack/webpack-dev-server/commit/a5fe3372e306e3c90a5e63e452e3e9ee9a745875;>a5fe337) v3.11.1 https://github.com/webpack/webpack-dev-server/compare/v3.11.0...v3.11.1;>3.11.1 (2020-12-29) Bug Fixes the open option works using webpack serve without value (https://github-redirect.dependabot.com/webpack/webpack-dev-server/issues/2948;>#2948) (https://github.com/webpack/webpack-dev-server/commit/4837dc92b944f8b4cdd7d6e3420367cf338e7f75;>4837dc9) vulnerable deps (https://github-redirect.dependabot.com/webpack/webpack-dev-server/issues/2949;>#2949) (https://github.com/webpack/webpack-dev-server/commit/78dde50f520c8b78de14272a4ae4cee1281bf2e3;>78dde50) Changelog Sourced from https://github.com/webpack/webpack-dev-server/blob/v3.11.3/CHANGELOG.md;>webpack-dev-server's changelog. https://github.com/webpack/webpack-dev-server/compare/v3.11.2...v3.11.3;>3.11.3 (2021-11-08) Bug Fixes replace ansi-html with ansi-html-community (https://github-redirect.dependabot.com/webpack/webpack-dev-server/issues/4011;>#4011) (https://github.com/webpack/webpack-dev-server/commit/4fef67b997a2bd09b46beb779c185ad8f85e3e1a;>4fef67b) https://github.com/webpack/webpack-dev-server/compare/v3.11.1...v3.11.2;>3.11.2 (2021-01-13) Bug Fixes cli arguments for serve command (https://github.com/webpack/webpack-dev-server/commit/a5fe3372e306e3c90a5e63e452e3e9ee9a745875;>a5fe337) https://github.com/webpack/webpack-dev-server/compare/v3.11.0...v3.11.1;>3.11.1 (2020-12-29) Bug Fixes the open option works using webpack serve without value (https://github-redirect.dependabot.com/webpack/webpack-dev-server/issues/2948;>#2948) (https://github.com/webpack/webpack-dev-server/commit/4837dc92b944f8b4cdd7d6e3420367cf338e7f75;>4837dc9) vulnerable deps (https://github-redirect.dependabot.com/webpack/webpack-dev-server/issues/2949;>#2949) (https://github.com/webpack/webpack-dev-server/commit/78dde50f520c8b78de14272a4ae4cee1281bf2e3;>78dde50) Commits https://github.com/webpack/webpack-dev-server/commit/aa3cddcf6eb2347704870f0e0cf33bc211e2a378;>aa3cddc chore(release): 3.11.3 https://github.com/webpack/webpack-dev-server/commit/4fef67b997a2bd09b46beb779c185ad8f85e3e1a;>4fef67b fix: replace ansi-html with ansi-html-community (https://github-redirect.dependabot.com/webpack/webpack-dev-server/issues/4011;>#4011) https://github.com/webpack/webpack-dev-server/commit/5cb545fdc64c9d4b8e557ca86e597db93b3f93f3;>5cb545f chore(release): 3.11.2 https://github.com/webpack/webpack-dev-server/commit/a5fe3372e306e3c90a5e63e452e3e9ee9a745875;>a5fe337 fix: cli arguments for serve command https://github.com/webpack/webpack-dev-server/commit/7e70eeea457a6a154709bd6069c05855f12f7842;>7e70eee chore(release): 3.11.1 https://github.com/webpack/webpack-dev-server/commit/78dde50f520c8b78de14272a4ae4cee1281bf2e3;>78dde50 fix: vulnerable deps (https://github-redirect.dependabot.com/webpack/webpack-dev-server/issues/2949;>#2949) https://github.com/webpack/webpack-dev-server/commit/4837dc92b944f8b4cdd7d6e3420367cf338e7f75;>4837dc9 fix: the open option works using webpack serve without value (https://github-redirect.dependabot.com/webpack/webpack-dev-server/issues/2948;>#2948) See full diff in https://github.com/webpack/webpack-dev-server/compare/v3.11.0...v3.11.3;>compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabo
[GitHub] [incubator-teaclave-website] dependabot[bot] opened a new pull request, #14: Bump axios and @vssue/api-github-v3 in /site
dependabot[bot] opened a new pull request, #14: URL: https://github.com/apache/incubator-teaclave-website/pull/14 Bumps [axios](https://github.com/axios/axios) and [@vssue/api-github-v3](https://github.com/meteorlxy/vssue). These dependencies needed to be updated together. Updates `axios` from 0.18.1 to 0.21.4 Release notes Sourced from https://github.com/axios/axios/releases;>axios's releases. v0.21.4 Fixes and Functionality: Fixing JSON transform when data is stringified. Providing backward compatibility and complying to the JSON RFC standard (https://github-redirect.dependabot.com/axios/axios/pull/4020;>#4020) Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub: https://github.com/gfortaine;>Guillaume Fortaine https://github.com/kawanet;>Yusuke Kawasaki https://github.com/DigitalBrainJS;>Dmitriy Mozgovoy v0.21.3 Fixes and Functionality: Fixing response interceptor not being called when request interceptor is attached (https://github-redirect.dependabot.com/axios/axios/pull/4013;>#4013) Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub: https://github.com/nerdbeere;>Julian Hollmann v0.21.2 Fixes and Functionality: Updating axios requests to be delayed by pre-emptive promise creation (https://github-redirect.dependabot.com/axios/axios/pull/2702;>#2702) Adding synchronous and runWhen options to interceptors api (https://github-redirect.dependabot.com/axios/axios/pull/2702;>#2702) Updating of transformResponse (https://github-redirect.dependabot.com/axios/axios/pull/3377;>#3377) Adding ability to omit User-Agent header (https://github-redirect.dependabot.com/axios/axios/pull/3703;>#3703) Adding multiple JSON improvements (https://github-redirect.dependabot.com/axios/axios/pull/3688;>#3688, https://github-redirect.dependabot.com/axios/axios/pull/3763;>#3763) Fixing quadratic runtime and extra memory usage when setting a maxContentLength (https://github-redirect.dependabot.com/axios/axios/pull/3738;>#3738) Adding parseInt to config.timeout (https://github-redirect.dependabot.com/axios/axios/pull/3781;>#3781) Adding custom return type support to interceptor (https://github-redirect.dependabot.com/axios/axios/pull/3783;>#3783) Adding security fix for ReDoS vulnerability (https://github-redirect.dependabot.com/axios/axios/pull/3980;>#3980) Internal and Tests: Updating build dev dependancies (https://github-redirect.dependabot.com/axios/axios/pull/3401;>#3401) Fixing builds running on Travis CI (https://github-redirect.dependabot.com/axios/axios/pull/3538;>#3538) Updating follow rediect version (https://github-redirect.dependabot.com/axios/axios/pull/3694;>#3694, https://github-redirect.dependabot.com/axios/axios/pull/3771;>#3771) Updating karma sauce launcher to fix failing sauce tests (https://github-redirect.dependabot.com/axios/axios/pull/3712;>#3712, https://github-redirect.dependabot.com/axios/axios/pull/3717;>#3717) Updating content-type header for application/json to not contain charset field, according do RFC 8259 (https://github-redirect.dependabot.com/axios/axios/pull/2154;>#2154) Fixing tests by bumping karma-sauce-launcher version (https://github-redirect.dependabot.com/axios/axios/pull/3813;>#3813) Changing testing process from Travis CI to GitHub Actions (https://github-redirect.dependabot.com/axios/axios/pull/3938;>#3938) Documentation: Updating documentation around the use of AUTH_TOKEN with multiple domain endpoints (https://github-redirect.dependabot.com/axios/axios/pull/3539;>#3539) Remove duplication of item in changelog (https://github-redirect.dependabot.com/axios/axios/pull/3523;>#3523) Fixing gramatical errors (https://github-redirect.dependabot.com/axios/axios/pull/2642;>#2642) Fixing spelling error (https://github-redirect.dependabot.com/axios/axios/pull/3567;>#3567) Moving gitpod metion (https://github-redirect.dependabot.com/axios/axios/pull/2637;>#2637) Adding new axios documentation website link (https://github-redirect.dependabot.com/axios/axios/pull/3681;>#3681, https://github-redirect.dependabot.com/axios/axios/pull/3707;>#3707) Updating documentation around dispatching requests (https://github-redirect.dependabot.com/axios/axios/pull/3772;>#3772) ... (truncated) Changelog Sourced from https://github.com/axios/axios/blob/v0.21.4/CHANGELOG.md;>axios's changelog. 0.21.4 (September 6, 2021) Fixes and Functionality: Fixing JSON transform when data is stringified. Providing backward compatability and complying to the JSON RFC standard (https://github-redirect.dependabot.com/axios
[GitHub] [incubator-teaclave-website] mssun merged pull request #12: Bump terser from 4.6.13 to 4.8.1 in /site
mssun merged PR #12: URL: https://github.com/apache/incubator-teaclave-website/pull/12 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] dependabot[bot] opened a new pull request, #12: Bump terser from 4.6.13 to 4.8.1 in /site
dependabot[bot] opened a new pull request, #12: URL: https://github.com/apache/incubator-teaclave-website/pull/12 Bumps [terser](https://github.com/terser/terser) from 4.6.13 to 4.8.1. Changelog Sourced from https://github.com/terser/terser/blob/master/CHANGELOG.md;>terser's changelog. v4.8.1 (backport) Security fix for RegExps that should not be evaluated (regexp DDOS) v4.8.0 Support for numeric separators (million = 1_000_000) was added. Assigning properties to a class is now assumed to be pure. Fixed bug where yield wasn't considered a valid property key in generators. v4.7.0 A bug was fixed where an arrow function would have the wrong size arguments object is now considered safe to retrieve properties from (useful for length, or 0) even when pure_getters is not set. Fixed erroneous const declarations without value (which is invalid) in some corner cases when using collapse_vars. Commits See full diff in https://github.com/terser/terser/commits;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/incubator-teaclave-website/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] mssun merged pull request #11: Bump eventsource from 1.0.7 to 1.1.1 in /site
mssun merged PR #11: URL: https://github.com/apache/incubator-teaclave-website/pull/11 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] dependabot[bot] opened a new pull request, #11: Bump eventsource from 1.0.7 to 1.1.1 in /site
dependabot[bot] opened a new pull request, #11: URL: https://github.com/apache/incubator-teaclave-website/pull/11 Bumps [eventsource](https://github.com/EventSource/eventsource) from 1.0.7 to 1.1.1. Changelog Sourced from https://github.com/EventSource/eventsource/blob/master/HISTORY.md;>eventsource's changelog. https://github.com/EventSource/eventsource/compare/v1.1.0...v1.1.1;>1.1.1 Do not include authorization and cookie headers on redirect to different origin (https://github-redirect.dependabot.com/EventSource/eventsource/pull/273;>#273 Espen Hovlandsdal) https://github.com/EventSource/eventsource/compare/v1.0.7...v1.1.0;>1.1.0 Improve performance for large messages across many chunks (https://github-redirect.dependabot.com/EventSource/eventsource/pull/130;>#130 Trent Willis) Add createConnection option for http or https requests (https://github-redirect.dependabot.com/EventSource/eventsource/pull/120;>#120 Vasily Lavrov) Support HTTP 302 redirects (https://github-redirect.dependabot.com/EventSource/eventsource/pull/116;>#116 Ryan Bonte) Prevent sequential errors from attempting multiple reconnections (https://github-redirect.dependabot.com/EventSource/eventsource/pull/125;>#125 David Patty) Add new to correct test (https://github-redirect.dependabot.com/EventSource/eventsource/pull/101;>#111 Stéphane Alnet) Fix reconnections attempts now happen more than once (https://github-redirect.dependabot.com/EventSource/eventsource/pull/136;>#136 Icy Fish) Commits https://github.com/EventSource/eventsource/commit/aa7a40843a978f42c0babdec125bf9e0a83bf515;>aa7a408 1.1.1 https://github.com/EventSource/eventsource/commit/56d489ef853a891deca121bbd463c732fee94dce;>56d489e chore: rebuild polyfill https://github.com/EventSource/eventsource/commit/4a951e58b04118c9c4d3da3d27d454972a1b4b8d;>4a951e5 docs: update history for 1.1.1 https://github.com/EventSource/eventsource/commit/f9f6416567bff62c1af2f4314be51d9870e94bc2;>f9f6416 fix: strip sensitive headers on redirect to different origin https://github.com/EventSource/eventsource/commit/9dd06876ab43af37c3313c679fbdc7f722293a0d;>9dd0687 1.1.0 https://github.com/EventSource/eventsource/commit/49497ba7107a7a94d7dbc73b6e5cc0117f8606e8;>49497ba Update history for 1.1.0 (https://github-redirect.dependabot.com/EventSource/eventsource/issues/146;>#146) https://github.com/EventSource/eventsource/commit/3a3853793f63eb5dab9d863504817a9d37b992e6;>3a38537 Update history for https://github-redirect.dependabot.com/EventSource/eventsource/issues/136;>#136 https://github.com/EventSource/eventsource/commit/46fe04e03e54f4129a28bf75b3a1e5f4ab68b52a;>46fe04e Merge pull request https://github-redirect.dependabot.com/EventSource/eventsource/issues/136;>#136 from icy-fish/master https://github.com/EventSource/eventsource/commit/9a4190f65e761ee672d786a6d01c60392950064b;>9a4190f Fix issue: reconnection only happends for 1 time after connection drops https://github.com/EventSource/eventsource/commit/61e1b19c8616aa151835a4ae599b299afb574ebf;>61e1b19 test: destroy both proxied request and response on close Additional commits viewable in https://github.com/EventSource/eventsource/compare/v1.0.7...v1.1.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unles
[GitHub] [incubator-teaclave-website] mssun merged pull request #10: Bump lodash from 4.17.15 to 4.17.21 in /site
mssun merged PR #10: URL: https://github.com/apache/incubator-teaclave-website/pull/10 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] mssun merged pull request #9: Bump postcss from 7.0.30 to 7.0.39 in /site
mssun merged PR #9: URL: https://github.com/apache/incubator-teaclave-website/pull/9 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] mssun merged pull request #8: Bump async from 2.6.3 to 2.6.4 in /site
mssun merged PR #8: URL: https://github.com/apache/incubator-teaclave-website/pull/8 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] dependabot[bot] opened a new pull request, #10: Bump lodash from 4.17.15 to 4.17.21 in /site
dependabot[bot] opened a new pull request, #10: URL: https://github.com/apache/incubator-teaclave-website/pull/10 Bumps [lodash](https://github.com/lodash/lodash) from 4.17.15 to 4.17.21. Commits https://github.com/lodash/lodash/commit/f299b52f39486275a9e6483b60a410e06520c538;>f299b52 Bump to v4.17.21 https://github.com/lodash/lodash/commit/c4847ebe7d14540bb28a8b932a9ce1b9ecbfee1a;>c4847eb Improve performance of toNumber, trim and trimEnd on large input strings https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c;>3469357 Prevent command injection through _.template's variable option https://github.com/lodash/lodash/commit/ded9bc66583ed0b4e3b7dc906206d40757b4a90a;>ded9bc6 Bump to v4.17.20. https://github.com/lodash/lodash/commit/63150ef7645ac07961b63a86490f419f356429aa;>63150ef Documentation fixes. https://github.com/lodash/lodash/commit/00f0f62a979d2f5fa0287c06eae70cf9a62d8794;>00f0f62 test.js: Remove trailing comma. https://github.com/lodash/lodash/commit/846e434c7a5b5692c55ebf5715ed677b70a32389;>846e434 Temporarily use a custom fork of lodash-cli. https://github.com/lodash/lodash/commit/5d046f39cbd27f573914768e3b36eeefcc4f1229;>5d046f3 Re-enable Travis tests on 4.17 branch. https://github.com/lodash/lodash/commit/aa816b36d402a1ad9385142ce7188f17dae514fd;>aa816b3 Remove /npm-package. https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056;>d7fbc52 Bump to v4.17.19 Additional commits viewable in https://github.com/lodash/lodash/compare/4.17.15...4.17.21;>compare view Maintainer changes This version was pushed to npm by https://www.npmjs.com/~bnjmnt4n;>bnjmnt4n, a new releaser for lodash since your current version. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/incubator-teaclave-website/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] dependabot[bot] opened a new pull request, #8: Bump async from 2.6.3 to 2.6.4 in /site
dependabot[bot] opened a new pull request, #8: URL: https://github.com/apache/incubator-teaclave-website/pull/8 Bumps [async](https://github.com/caolan/async) from 2.6.3 to 2.6.4. Changelog Sourced from https://github.com/caolan/async/blob/v2.6.4/CHANGELOG.md;>async's changelog. v2.6.4 Fix potential prototype pollution exploit (https://github-redirect.dependabot.com/caolan/async/issues/1828;>#1828) Commits https://github.com/caolan/async/commit/c6bdaca4f9175c14fc655d3783c6af6a883e6514;>c6bdaca Version 2.6.4 https://github.com/caolan/async/commit/8870da9d5022bab310413041b4079e10db3980b7;>8870da9 Update built files https://github.com/caolan/async/commit/4df6754ef4e96a742956df8782fee27242a2ea12;>4df6754 update changelog https://github.com/caolan/async/commit/8f7f90342a6571ba1c197d747ebed30c368096d2;>8f7f903 Fix prototype pollution vulnerability (https://github-redirect.dependabot.com/caolan/async/issues/1828;>#1828) See full diff in https://github.com/caolan/async/compare/v2.6.3...v2.6.4;>compare view Maintainer changes This version was pushed to npm by https://www.npmjs.com/~hargasinski;>hargasinski, a new releaser for async since your current version. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/incubator-teaclave-website/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] dependabot[bot] opened a new pull request, #9: Bump postcss from 7.0.30 to 7.0.39 in /site
dependabot[bot] opened a new pull request, #9: URL: https://github.com/apache/incubator-teaclave-website/pull/9 Bumps [postcss](https://github.com/postcss/postcss) from 7.0.30 to 7.0.39. Release notes Sourced from https://github.com/postcss/postcss/releases;>postcss's releases. 7.0.39 Reduce package size. Backport nanocolors to picocolors migration. 7.0.38 Update Processor#version. 7.0.37 Backport chalk to nanocolors migration. 7.0.36 Backport ReDoS vulnerabilities from PostCSS 8. 7.0.35 Add https://github.com/postcss/postcss/wiki/PostCSS-8-for-end-users;>migration guide link to PostCSS 8 error text. 7.0.34 Fix compatibility with postcss-scss 2. 7.0.33 Add error message for PostCSS 8 plugins. 7.0.32 Fix error message (by https://github.com/admosity;>@admosity). 7.0.31 Use only the latest source map annotation (by https://github.com/emzoumpo;>@emzoumpo). Changelog Sourced from https://github.com/postcss/postcss/blob/7.0.39/CHANGELOG.md;>postcss's changelog. 7.0.39 Reduce package size. Backport nanocolors to picocolors migration. 7.0.38 Update Processor#version. 7.0.37 Backport chalk to nanocolors migration. 7.0.36 Backport ReDoS vulnerabilities from PostCSS 8. 7.0.35 Add migration guide link to PostCSS 8 error text. 7.0.34 Fix compatibility with postcss-scss 2. 7.0.33 Add error message for PostCSS 8 plugins. 7.0.32 Fix error message (by https://github.com/admosity;>@admosity). 7.0.31 Use only the latest source map annotation (by Emmanouil Zoumpoulakis). Commits https://github.com/postcss/postcss/commit/e17c1ef7623a71be5732432ca8499bc9928aa08d;>e17c1ef Release 7.0.39 version https://github.com/postcss/postcss/commit/6791bd3d5f7ab27ad36dc075033a5beb4bdbfe9e;>6791bd3 Reduce npm package https://github.com/postcss/postcss/commit/44c581a55a9aab339ee319aa67c264b02c4a6448;>44c581a Replace nanocolors with picocolors https://github.com/postcss/postcss/commit/8ba21fd8f4c3bff146b8a71d2d12f31435444394;>8ba21fd Remove eslint-ci https://github.com/postcss/postcss/commit/3994c4aa3ce1835c9b36ae17ab94e45c21b56fb2;>3994c4a Release 7.0.38 version https://github.com/postcss/postcss/commit/6944e1dd808da66cee4ebf287c66c6aa0fc5c2a0;>6944e1d Remove development keys from package.json https://github.com/postcss/postcss/commit/4dd0af024a915bd12d2d53990c5a4fa4129563d5;>4dd0af0 Release 7.0.37 version https://github.com/postcss/postcss/commit/8408eb4105755c43dbf09a000fd2f1308f240232;>8408eb4 Add compilation step https://github.com/postcss/postcss/commit/0c680639c3d717b4c8c0b2b2a9d1799fbf239a76;>0c68063 Move tests to GitHub Actions https://github.com/postcss/postcss/commit/98b61ba5b46622de48bb2592583757ab846212ad;>98b61ba Replace chalk to nanocolors Additional commits viewable in https://github.com/postcss/postcss/compare/7.0.30...7.0.39;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the P
[GitHub] [incubator-teaclave-website] mssun merged pull request #7: Bump minimist from 1.2.5 to 1.2.6 in /site
mssun merged PR #7: URL: https://github.com/apache/incubator-teaclave-website/pull/7 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] dependabot[bot] opened a new pull request, #7: Bump minimist from 1.2.5 to 1.2.6 in /site
dependabot[bot] opened a new pull request, #7: URL: https://github.com/apache/incubator-teaclave-website/pull/7 Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6. Commits https://github.com/substack/minimist/commit/7efb22a518b53b06f5b02a1038a88bd6290c2846;>7efb22a 1.2.6 https://github.com/substack/minimist/commit/ef88b9325f77b5ee643ccfc97e2ebda577e4c4e2;>ef88b93 security notice for additional prototype pollution issue https://github.com/substack/minimist/commit/c2b981977fa834b223b408cfb860f933c9811e4d;>c2b9819 isConstructorOrProto adapted from PR https://github.com/substack/minimist/commit/bc8ecee43875261f4f17eb20b1243d3ed15e70eb;>bc8ecee test from prototype pollution PR See full diff in https://github.com/substack/minimist/compare/1.2.5...1.2.6;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/incubator-teaclave-website/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: [apache/incubator-teaclave] [Website] Incorrect archive link (Issue #599)
Fixed and rendered. Thanks! -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/599#issuecomment-1009424456 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave] [Website] Incorrect archive link (Issue #599)
Closed #599. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/599#event-5869287311 You are receiving this because you are subscribed to this thread. Message ID:
Re: [apache/incubator-teaclave] [Website] Incorrect archive link (Issue #599)
Fixed in this commit: https://github.com/apache/incubator-teaclave-website/commit/1921d33ab1cbe52e4a0045cb2200544b010808f2 The updated page will be rendered soon. -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/599#issuecomment-1009372462 You are receiving this because you are subscribed to this thread. Message ID:
[apache/incubator-teaclave] [Website] Incorrect archive link (Issue #599)
There is a minor bug that appears on the `community` webpage. The following `Archive` linked to `commit mail-list` not the `dev` dev@teaclave.apache.org: A list for discussion on Teaclave development including design proposal, release announcements, meetup schedules, and commnity voting, etc. [mailto:dev-subscr...@teaclave.apache.org?subject=Subscribe; rel="noreferrer" data-ss1641849516="1">Subscribe | mailto:dev-unsubscr...@teaclave.apache.org?subject=Unsubscribe; rel="noreferrer" data-ss1641849516="1">Unsubscribe | https://lists.apache.org/list.html?comm...@teaclave.apache.org; target="_blank" rel="noopener noreferrer" data-ss1641849516="1">Archive] -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/599 You are receiving this because you are subscribed to this thread. Message ID:
[GitHub] [incubator-teaclave-website] mssun merged pull request #6: Rww branch
mssun merged pull request #6: URL: https://github.com/apache/incubator-teaclave-website/pull/6 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] mssun commented on pull request #5: add developing Teaclave SGX Application doc
mssun commented on pull request #5: URL: https://github.com/apache/incubator-teaclave-website/pull/5#issuecomment-906826539 Squashed and merged. Thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] mssun merged pull request #5: add developing Teaclave SGX Application doc
mssun merged pull request #5: URL: https://github.com/apache/incubator-teaclave-website/pull/5 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] ya0guang commented on a change in pull request #5: add developing Teaclave SGX Application doc
ya0guang commented on a change in pull request #5:
URL:
https://github.com/apache/incubator-teaclave-website/pull/5#discussion_r695803212
##
File path:
site/blog/2021-08-13-developing-sgx-application-with-teaclave-sgx-sdk.md
##
@@ -269,32 +269,90 @@ pub fn intersection(nums1: Vec, nums2: Vec) ->
Vec {
}
```
-需要调用该函数时，在 `say_something` 中添加：
+考虑一个比较现实的场景，两个用户分别将自己的向量作为参数传入 enclave 中进行计算，这时候数据需要从不可信代码区域复制到可信代码区域。
+首先，需要在 `Enclave.edl` 文件中修改 `say_something` 函数的定义，输入参数为两个用户的向量指针以及对应的大小。
+```edl
+public sgx_status_t say_something([in, size=len1] size_t* num1, size_t len1,
+ [in, size=len2] size_t* num2, size_t len2);
+```
+
+接着，在 `app.c` 文件中声明需要求交集的数组以及大小并仿照示例调用 `say_something`。
+
+```c
+size_t nums1[10] = {0,1,2,3,4,5,6,7,8,9};
+size_t nums2[10] = {5,6,7,8,9,10,11,12,13,14};
+size_t len1 = sizeof(nums1);
+size_t len2 = sizeof(nums2);
+
+sgx_ret = say_something(global_eid,
+_ret,
+nums1,
+len1,
+nums2,
+len2);
+```
+
+回到 `enclave/src/lib.rs`，`say_something` 传进来的是两个向量的起始地址以及大小。
```rust
-println!("\nTry intersection for our own");
-let nums1: Vec = vec![1, 2, 3, 4, 5];
-let nums2: Vec = vec![4, 5, 6, 7, 8];
-let vec: Vec = intersection(nums1, nums2);
-println!("intersection set is {:?}", vec);
+pub extern "C" fn say_something(nums1: *mut usize, len1: usize, nums2: *mut
usize, len2: usize) -> sgx_status_t
+```
+由于数据是从非安全区复制到安全区的，还需要对 `intersection`
函数进行部分改写。传进来的参数是向量指针，以指针地址为起始地址，根据大小参数限制迭代范围并获得一个用于循环的序号变量 `i`，在 `for` 循环中使用
`offset` 偏移指针，解引用它，读出 `nums1` 和 `nums2` 的元素值。
+```rust
+pub fn intersection(nums1: *mut usize, len1: usize, nums2: *mut usize, len2:
usize) -> Vec {
+use std::collections::HashSet;
+let mut set: HashSet = HashSet::new();
+let mut vec: Vec = Vec::new();
+
+for i in 0..len1/mem::size_of::() {
+let mut val_nums1 = 0;
+unsafe {
+val_nums1 = *nums1.offset(i as isize);
+}
+set.insert(val_nums1);
+}
+
Review comment:
这里应该也可以使用`std::slice::from_raw_parts`来构建一个`&[]`。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org
For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] RMheng commented on a change in pull request #5: add developing Teaclave SGX Application doc
RMheng commented on a change in pull request #5: URL: https://github.com/apache/incubator-teaclave-website/pull/5#discussion_r694511314 ## File path: site/blog/2021-08-13-developing-sgx-application-with-teaclave-sgx-sdk.md ## @@ -0,0 +1,331 @@ +--- +title: 使用 Teaclave SGX SDK 开发 SGX 应用 +date: 2021-08-13 +author: Wenwen Ruan +--- + +[[TOC]] + + +## Teaclave SGX SDK应用开发环境简介以及搭建 + +Intel SGX (软件防护扩展，Software Guard Extension) 提供了在一个安全的 enclave（飞地）中执行代码的能力，enclave 可以提供一个隔离的可信执行环境，在操作系统、BIOS 和虚拟机监控器等系统软件均不可信的情况下，仍然对 enclave 内部的代码和数据提供保护，保障用户的关键数据和代码的机密性和完整性。 + +但如果 Intel SGX 程序仍然使用 C/C++ 这类内存不安全的语言开发的话，就会和传统软件一样面临着传统的内存破坏漏洞。对于 enclave 来说，受到的危害会更为严重，因为 enclave 中保存的多是机密数据和代码。Teaclave SGX 的主要目标就是通过使用高效的内存安全语言 —— Rust 来支持 enclave 应用程序的开发，从而在保证 Intel SGX enclave 内存安全的同时不会带来显著的性能开销。 + +Teaclave SGX SDK 内部结构分为三层： + ++ 最底层是使用 C/C++ 和汇编实现的 Intel SGX SDK。 ++ 中间层是 Rust 对 C/C++ 的 FFI (Foreign function Interfaces, 外部函数接口)。 ++ 最高层是 Teaclave SGX SDK。 + + + +Teaclave SGX SDK 应用程序开发者在进行开发时就只需要基于最上层的 Teaclave SGX SDK 来进行开发，底层的实现对于开发者来说是透明的。本文将从开发者的角度介绍基于 Teaclave SGX SDK 开发自己的应用程序的过程。 + +### 准备条件 + ++ Ubuntu16.04 或者 18.04 或者 20.04 (Teaclave SGX SDK v1.1.3 中增加了对 Ubuntu 20.04 的支持) ++ docker 环境 + +*本文基于 Teaclave SGX SDK v1.1.3 提交哈希值：d107bd0718f723221750a4f2973451b386cbf9d2* + + +### 基于 docker 配置 Teaclave SGX SDK 开发环境 + +首先需要用户机器 CPU 支持 Intel SGX 并且在 BIOS 上开启了 Intel SGX 支持。用户可以通过 [SGX-hardware项目](https://github.com/ayeks/SGX-hardware) 或者在 [Intel 官网](https://www.intel.com/content/www/us/en/products/details/processors.html) 中搜索自己的 CPU 型号查看是否支持 Intel SGX。下图以 Intel Core i7-7700K 处理器为例，如下图所示，该机型支持 SGX。 + + + +当确定 CPU 支持 Intel SGX 之后，还需要开启 BIOS 中的 SGX 选项。CPU 上的 SGX 选项可能有 `enabled` 或者 `software controlled`。具有 `enabled` 选项的主机直接在 BIOS 上选择 `enabled` 即可，而`software controlled` 表示 SGX 的开启需要由软件触发，还需通过 Intel 官方提供的 [sgx-software-enable](https://github.com/intel/sgx-software-enable) 开启。下载好 `sgx-software-enable` 之后，运行 `Makefile` 编译生成可执行代码 `sgx_enable` ，执行 `sudo ./sgx_enable` 顺利运行后重启主机，即可顺利开启 Intel SGX。 + +硬件条件准备完毕之后，还需要安装 [Linux SGX 驱动](https://download.01.org/intel-sgx/sgx-linux/2.10/distro/ubuntu16.04-server/sgx_linux_x64_driver_2.6.0_602374c.bin) ，安装完毕之后需要确认 `/dev/isgx` 的存在。 Review comment: 感谢comments，已经根据comments进行了修改 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] RMheng commented on a change in pull request #5: add developing Teaclave SGX Application doc
RMheng commented on a change in pull request #5:
URL:
https://github.com/apache/incubator-teaclave-website/pull/5#discussion_r692627892
##
File path:
site/blog/2021-08-13-developing-sgx-application-with-teaclave-sgx-sdk.md
##
@@ -0,0 +1,331 @@
+---
+title: 使用 Teaclave SGX SDK 开发 SGX 应用
+date: 2021-08-13
+author: Wenwen Ruan
+---
+
+[[TOC]]
+
+
+## Teaclave SGX SDK应用开发环境简介以及搭建
+
+Intel SGX (软件防护扩展，Software Guard Extension) 提供了在一个安全的
enclave（飞地）中执行代码的能力，enclave 可以提供一个隔离的可信执行环境，在操作系统、BIOS 和虚拟机监控器等系统软件均不可信的情况下，仍然对
enclave 内部的代码和数据提供保护，保障用户的关键数据和代码的机密性和完整性。
+
+但如果 Intel SGX 程序仍然使用 C/C++ 这类内存不安全的语言开发的话，就会和传统软件一样面临着传统的内存破坏漏洞。对于 enclave
来说，受到的危害会更为严重，因为 enclave 中保存的多是机密数据和代码。Teaclave SGX 的主要目标就是通过使用高效的内存安全语言 ——
Rust 来支持 enclave 应用程序的开发，从而在保证 Intel SGX enclave 内存安全的同时不会带来显著的性能开销。
+
+Teaclave SGX SDK 内部结构分为三层：
+
++ 最底层是使用 C/C++ 和汇编实现的 Intel SGX SDK。
++ 中间层是 Rust 对 C/C++ 的 FFI (Foreign function Interfaces, 外部函数接口)。
++ 最高层是 Teaclave SGX SDK。
+
+
+
+Teaclave SGX SDK 应用程序开发者在进行开发时就只需要基于最上层的 Teaclave SGX SDK
来进行开发，底层的实现对于开发者来说是透明的。本文将从开发者的角度介绍基于 Teaclave SGX SDK 开发自己的应用程序的过程。
+
+### 准备条件
+
++ Ubuntu16.04 或者 18.04 或者 20.04 (Teaclave SGX SDK v1.1.3 中增加了对 Ubuntu 20.04
的支持)
++ docker 环境
+
+*本文基于 Teaclave SGX SDK v1.1.3 提交哈希值：d107bd0718f723221750a4f2973451b386cbf9d2*
+
+
+### 基于 docker 配置 Teaclave SGX SDK 开发环境
+
+首先需要用户机器 CPU 支持 Intel SGX 并且在 BIOS 上开启了 Intel SGX 支持。用户可以通过
[SGX-hardware项目](https://github.com/ayeks/SGX-hardware) 或者在 [Intel
官网](https://www.intel.com/content/www/us/en/products/details/processors.html)
中搜索自己的 CPU 型号查看是否支持 Intel SGX。下图以 Intel Core i7-7700K 处理器为例，如下图所示，该机型支持 SGX。
+
+
+
+当确定 CPU 支持 Intel SGX 之后，还需要开启 BIOS 中的 SGX 选项。CPU 上的 SGX 选项可能有 `enabled` 或者
`software controlled`。具有 `enabled` 选项的主机直接在 BIOS 上选择 `enabled` 即可，而`software
controlled` 表示 SGX 的开启需要由软件触发，还需通过 Intel 官方提供的
[sgx-software-enable](https://github.com/intel/sgx-software-enable) 开启。下载好
`sgx-software-enable` 之后，运行 `Makefile` 编译生成可执行代码 `sgx_enable` ，执行 `sudo
./sgx_enable` 顺利运行后重启主机，即可顺利开启 Intel SGX。
+
+硬件条件准备完毕之后，还需要安装 [Linux SGX
驱动](https://download.01.org/intel-sgx/sgx-linux/2.10/distro/ubuntu16.04-server/sgx_linux_x64_driver_2.6.0_602374c.bin)
，安装完毕之后需要确认 `/dev/isgx` 的存在。
+
+下载 Teaclave SGX SDK 以及支持编译 SGX 设备的 docker image。
+
+`$ https://github.com/apache/incubator-teaclave-sgx-sdk`
+
+`$ docker pull baiduxlab/sgx-rust`
+
+启动一个 docker，并且把 Teaclave SGX SDK 项目目录映射到 docker 中。
+
+`$ docker run -v /your/absolute/path/to/incubator-teaclave-sgx-sdk:/root/sgx
-ti --device /dev/isgx baiduxlab/sgx-rust`
+
+在运行的 docker container 中启动 aesm 服务，**White list update request successful for
Version** 语句意味着启动成功。
+
+bash
+root@docker:/# LD_LIBRARY_PATH=/opt/intel/sgx-aesm-service/aesm/
/opt/intel/sgx-aesm-service/aesm/aesm_service &
+aesm_service[17]: [ADMIN]White List update requested
+aesm_service[17]: Failed to load QE3: 0x4004
+aesm_service[17]: The server sock is 0x56096ab991c0
+aesm_service[17]: [ADMIN]White list update request successful for Version: 103
+
+
+执行 Teaclave SGX SDK 中的简单实例 helloworld ，检查是否正常运行。
+
+```bash
+root@docker:~# cd sgx/samplecode/helloworld/
+root@docker:~/sgx/samplecode/helloworld# make
+root@docker:~/sgx/samplecode/helloworld# cd bin/
+root@docker:~/sgx/samplecode/helloworld/bin# ./app
+[+] global_eid: 2
+This is normal world string passed into enclave!
+This is a Rust string!
+[+] say_something success ...
+```
+至此，我们已经成功在自己的机器上跑起来了 Teaclave SGX SDK 的 helloworld 示例啦！
+
+## Teaclave SGX SDK 示例 helloworld 剖析
+
+接下来，我们通过阅读 helloworld 这个简单的例子来理解 Teaclave SGX SDK 应用程序的组织结构和运行方式。
+
+### helloworld 目录结构
+
+```tree
+helloworld/
+├── app
+│ ├── app.c
+│ └── app.h
+├── bin
+│ └── readme.txt
+├── enclave
+│ ├── Cargo.toml
+│ ├── Enclave.config.xml
+│ ├── Enclave.edl
+│ ├── Enclave.lds
+│ ├── Enclave_private.pem
+│ ├── Makefile
+│ ├── src
+│ │ └── lib.rs
+│ ├── x86_64-unknown-linux-sgx.json
+│ └── Xargo.toml
+├── lib
+│ └── readme.txt
+└── Makefile
+```
+
+helloworld 的目录结构和 Intel SGX 的
[SampleEnclave](https://github.com/intel/linux-sgx/blob/HEAD/SampleCode/SampleEnclave)
目录结构非常类似。
++ app 目录中存放的是不可信部分代码，包括 `main` 函数以及 `OCALL` 函数具体逻辑实现。
++ enclave 目录中存放的是可信部分代码，主要是 `ECALL` 函数具体逻辑实现。
++ 不同于 SGX ，应用安全区的代码实现位于 **`src/lib.rs`**, 该文件是整个 `helloworld` 文件夹中唯一使用
Rust 编写的文件，程序员可以在该文件中增加需要的功能。
++ 另外，enclave 文件夹下多了 `Cargo.toml`, `src/lib.rs`,
`x86_64-unknown-linux-sgx.json`, `Xargo.toml`：
++ **`Cargo.toml`**: 项目清单文件，包括项目名称、项目版本以及依赖项等。
++ **`x86_64-unknown-linux-sgx.json`** 和 **`Xargo.toml`**
描述了用于项目交叉编译的信息。
+
+### 重要代码文件解析
+
++ **`Enclave.edl`** \
+该文件规定了 Enclave 边界 `ECALL/OCALL` 的定义。
+
+```edl
+enclave {
+from "sgx_tstd.edl" import *;
+from "sgx_stdio.edl" import *;
+from "sgx_backtrace.edl" import *;
+from "sgx_tstdc.edl" import *;
+
+
[GitHub] [incubator-teaclave-website] ya0guang commented on a change in pull request #5: add developing Teaclave SGX Application doc
ya0guang commented on a change in pull request #5:
URL:
https://github.com/apache/incubator-teaclave-website/pull/5#discussion_r692174904
##
File path:
site/blog/2021-08-13-developing-sgx-application-with-teaclave-sgx-sdk.md
##
@@ -0,0 +1,331 @@
+---
+title: 使用 Teaclave SGX SDK 开发 SGX 应用
+date: 2021-08-13
+author: Wenwen Ruan
+---
+
+[[TOC]]
+
+
+## Teaclave SGX SDK应用开发环境简介以及搭建
+
+Intel SGX (软件防护扩展，Software Guard Extension) 提供了在一个安全的
enclave（飞地）中执行代码的能力，enclave 可以提供一个隔离的可信执行环境，在操作系统、BIOS 和虚拟机监控器等系统软件均不可信的情况下，仍然对
enclave 内部的代码和数据提供保护，保障用户的关键数据和代码的机密性和完整性。
+
+但如果 Intel SGX 程序仍然使用 C/C++ 这类内存不安全的语言开发的话，就会和传统软件一样面临着传统的内存破坏漏洞。对于 enclave
来说，受到的危害会更为严重，因为 enclave 中保存的多是机密数据和代码。Teaclave SGX 的主要目标就是通过使用高效的内存安全语言 ——
Rust 来支持 enclave 应用程序的开发，从而在保证 Intel SGX enclave 内存安全的同时不会带来显著的性能开销。
+
+Teaclave SGX SDK 内部结构分为三层：
+
++ 最底层是使用 C/C++ 和汇编实现的 Intel SGX SDK。
++ 中间层是 Rust 对 C/C++ 的 FFI (Foreign function Interfaces, 外部函数接口)。
++ 最高层是 Teaclave SGX SDK。
+
+
+
+Teaclave SGX SDK 应用程序开发者在进行开发时就只需要基于最上层的 Teaclave SGX SDK
来进行开发，底层的实现对于开发者来说是透明的。本文将从开发者的角度介绍基于 Teaclave SGX SDK 开发自己的应用程序的过程。
+
+### 准备条件
+
++ Ubuntu16.04 或者 18.04 或者 20.04 (Teaclave SGX SDK v1.1.3 中增加了对 Ubuntu 20.04
的支持)
++ docker 环境
+
+*本文基于 Teaclave SGX SDK v1.1.3 提交哈希值：d107bd0718f723221750a4f2973451b386cbf9d2*
+
+
+### 基于 docker 配置 Teaclave SGX SDK 开发环境
+
+首先需要用户机器 CPU 支持 Intel SGX 并且在 BIOS 上开启了 Intel SGX 支持。用户可以通过
[SGX-hardware项目](https://github.com/ayeks/SGX-hardware) 或者在 [Intel
官网](https://www.intel.com/content/www/us/en/products/details/processors.html)
中搜索自己的 CPU 型号查看是否支持 Intel SGX。下图以 Intel Core i7-7700K 处理器为例，如下图所示，该机型支持 SGX。
+
+
+
+当确定 CPU 支持 Intel SGX 之后，还需要开启 BIOS 中的 SGX 选项。CPU 上的 SGX 选项可能有 `enabled` 或者
`software controlled`。具有 `enabled` 选项的主机直接在 BIOS 上选择 `enabled` 即可，而`software
controlled` 表示 SGX 的开启需要由软件触发，还需通过 Intel 官方提供的
[sgx-software-enable](https://github.com/intel/sgx-software-enable) 开启。下载好
`sgx-software-enable` 之后，运行 `Makefile` 编译生成可执行代码 `sgx_enable` ，执行 `sudo
./sgx_enable` 顺利运行后重启主机，即可顺利开启 Intel SGX。
+
+硬件条件准备完毕之后，还需要安装 [Linux SGX
驱动](https://download.01.org/intel-sgx/sgx-linux/2.10/distro/ubuntu16.04-server/sgx_linux_x64_driver_2.6.0_602374c.bin)
，安装完毕之后需要确认 `/dev/isgx` 的存在。
+
+下载 Teaclave SGX SDK 以及支持编译 SGX 设备的 docker image。
+
+`$ https://github.com/apache/incubator-teaclave-sgx-sdk`
+
+`$ docker pull baiduxlab/sgx-rust`
+
+启动一个 docker，并且把 Teaclave SGX SDK 项目目录映射到 docker 中。
+
+`$ docker run -v /your/absolute/path/to/incubator-teaclave-sgx-sdk:/root/sgx
-ti --device /dev/isgx baiduxlab/sgx-rust`
+
+在运行的 docker container 中启动 aesm 服务，**White list update request successful for
Version** 语句意味着启动成功。
+
+bash
+root@docker:/# LD_LIBRARY_PATH=/opt/intel/sgx-aesm-service/aesm/
/opt/intel/sgx-aesm-service/aesm/aesm_service &
+aesm_service[17]: [ADMIN]White List update requested
+aesm_service[17]: Failed to load QE3: 0x4004
+aesm_service[17]: The server sock is 0x56096ab991c0
+aesm_service[17]: [ADMIN]White list update request successful for Version: 103
+
+
+执行 Teaclave SGX SDK 中的简单实例 helloworld ，检查是否正常运行。
+
+```bash
+root@docker:~# cd sgx/samplecode/helloworld/
+root@docker:~/sgx/samplecode/helloworld# make
+root@docker:~/sgx/samplecode/helloworld# cd bin/
+root@docker:~/sgx/samplecode/helloworld/bin# ./app
+[+] global_eid: 2
+This is normal world string passed into enclave!
+This is a Rust string!
+[+] say_something success ...
+```
+至此，我们已经成功在自己的机器上跑起来了 Teaclave SGX SDK 的 helloworld 示例啦！
+
+## Teaclave SGX SDK 示例 helloworld 剖析
+
+接下来，我们通过阅读 helloworld 这个简单的例子来理解 Teaclave SGX SDK 应用程序的组织结构和运行方式。
+
+### helloworld 目录结构
+
+```tree
+helloworld/
+├── app
+│ ├── app.c
+│ └── app.h
+├── bin
+│ └── readme.txt
+├── enclave
+│ ├── Cargo.toml
+│ ├── Enclave.config.xml
+│ ├── Enclave.edl
+│ ├── Enclave.lds
+│ ├── Enclave_private.pem
+│ ├── Makefile
+│ ├── src
+│ │ └── lib.rs
+│ ├── x86_64-unknown-linux-sgx.json
+│ └── Xargo.toml
+├── lib
+│ └── readme.txt
+└── Makefile
+```
+
+helloworld 的目录结构和 Intel SGX 的
[SampleEnclave](https://github.com/intel/linux-sgx/blob/HEAD/SampleCode/SampleEnclave)
目录结构非常类似。
++ app 目录中存放的是不可信部分代码，包括 `main` 函数以及 `OCALL` 函数具体逻辑实现。
++ enclave 目录中存放的是可信部分代码，主要是 `ECALL` 函数具体逻辑实现。
++ 不同于 SGX ，应用安全区的代码实现位于 **`src/lib.rs`**, 该文件是整个 `helloworld` 文件夹中唯一使用
Rust 编写的文件，程序员可以在该文件中增加需要的功能。
++ 另外，enclave 文件夹下多了 `Cargo.toml`, `src/lib.rs`,
`x86_64-unknown-linux-sgx.json`, `Xargo.toml`：
++ **`Cargo.toml`**: 项目清单文件，包括项目名称、项目版本以及依赖项等。
++ **`x86_64-unknown-linux-sgx.json`** 和 **`Xargo.toml`**
描述了用于项目交叉编译的信息。
+
+### 重要代码文件解析
+
++ **`Enclave.edl`** \
+该文件规定了 Enclave 边界 `ECALL/OCALL` 的定义。
+
+```edl
+enclave {
+from "sgx_tstd.edl" import *;
+from "sgx_stdio.edl" import *;
+from "sgx_backtrace.edl" import *;
+from "sgx_tstdc.edl" import *;
+
+
[GitHub] [incubator-teaclave-website] RMheng commented on a change in pull request #5: add developing Teaclave SGX Application doc
RMheng commented on a change in pull request #5:
URL:
https://github.com/apache/incubator-teaclave-website/pull/5#discussion_r692031826
##
File path:
site/blog/2021-08-13-developing-sgx-application-with-teaclave-sgx-sdk.md
##
@@ -0,0 +1,331 @@
+---
+title: 使用 Teaclave SGX SDK 开发 SGX 应用
+date: 2021-08-13
+author: Wenwen Ruan
+---
+
+[[TOC]]
+
+
+## Teaclave SGX SDK应用开发环境简介以及搭建
+
+Intel SGX (软件防护扩展，Software Guard Extension) 提供了在一个安全的
enclave（飞地）中执行代码的能力，enclave 可以提供一个隔离的可信执行环境，在操作系统、BIOS 和虚拟机监控器等系统软件均不可信的情况下，仍然对
enclave 内部的代码和数据提供保护，保障用户的关键数据和代码的机密性和完整性。
+
+但如果 Intel SGX 程序仍然使用 C/C++ 这类内存不安全的语言开发的话，就会和传统软件一样面临着传统的内存破坏漏洞。对于 enclave
来说，受到的危害会更为严重，因为 enclave 中保存的多是机密数据和代码。Teaclave SGX 的主要目标就是通过使用高效的内存安全语言 ——
Rust 来支持 enclave 应用程序的开发，从而在保证 Intel SGX enclave 内存安全的同时不会带来显著的性能开销。
+
+Teaclave SGX SDK 内部结构分为三层：
+
++ 最底层是使用 C/C++ 和汇编实现的 Intel SGX SDK。
++ 中间层是 Rust 对 C/C++ 的 FFI (Foreign function Interfaces, 外部函数接口)。
++ 最高层是 Teaclave SGX SDK。
+
+
+
+Teaclave SGX SDK 应用程序开发者在进行开发时就只需要基于最上层的 Teaclave SGX SDK
来进行开发，底层的实现对于开发者来说是透明的。本文将从开发者的角度介绍基于 Teaclave SGX SDK 开发自己的应用程序的过程。
+
+### 准备条件
+
++ Ubuntu16.04 或者 18.04 或者 20.04 (Teaclave SGX SDK v1.1.3 中增加了对 Ubuntu 20.04
的支持)
++ docker 环境
+
+*本文基于 Teaclave SGX SDK v1.1.3 提交哈希值：d107bd0718f723221750a4f2973451b386cbf9d2*
+
+
+### 基于 docker 配置 Teaclave SGX SDK 开发环境
+
+首先需要用户机器 CPU 支持 Intel SGX 并且在 BIOS 上开启了 Intel SGX 支持。用户可以通过
[SGX-hardware项目](https://github.com/ayeks/SGX-hardware) 或者在 [Intel
官网](https://www.intel.com/content/www/us/en/products/details/processors.html)
中搜索自己的 CPU 型号查看是否支持 Intel SGX。下图以 Intel Core i7-7700K 处理器为例，如下图所示，该机型支持 SGX。
+
+
+
+当确定 CPU 支持 Intel SGX 之后，还需要开启 BIOS 中的 SGX 选项。CPU 上的 SGX 选项可能有 `enabled` 或者
`software controlled`。具有 `enabled` 选项的主机直接在 BIOS 上选择 `enabled` 即可，而`software
controlled` 表示 SGX 的开启需要由软件触发，还需通过 Intel 官方提供的
[sgx-software-enable](https://github.com/intel/sgx-software-enable) 开启。下载好
`sgx-software-enable` 之后，运行 `Makefile` 编译生成可执行代码 `sgx_enable` ，执行 `sudo
./sgx_enable` 顺利运行后重启主机，即可顺利开启 Intel SGX。
+
+硬件条件准备完毕之后，还需要安装 [Linux SGX
驱动](https://download.01.org/intel-sgx/sgx-linux/2.10/distro/ubuntu16.04-server/sgx_linux_x64_driver_2.6.0_602374c.bin)
，安装完毕之后需要确认 `/dev/isgx` 的存在。
+
+下载 Teaclave SGX SDK 以及支持编译 SGX 设备的 docker image。
+
+`$ https://github.com/apache/incubator-teaclave-sgx-sdk`
+
+`$ docker pull baiduxlab/sgx-rust`
+
+启动一个 docker，并且把 Teaclave SGX SDK 项目目录映射到 docker 中。
+
+`$ docker run -v /your/absolute/path/to/incubator-teaclave-sgx-sdk:/root/sgx
-ti --device /dev/isgx baiduxlab/sgx-rust`
+
+在运行的 docker container 中启动 aesm 服务，**White list update request successful for
Version** 语句意味着启动成功。
+
+bash
+root@docker:/# LD_LIBRARY_PATH=/opt/intel/sgx-aesm-service/aesm/
/opt/intel/sgx-aesm-service/aesm/aesm_service &
+aesm_service[17]: [ADMIN]White List update requested
+aesm_service[17]: Failed to load QE3: 0x4004
+aesm_service[17]: The server sock is 0x56096ab991c0
+aesm_service[17]: [ADMIN]White list update request successful for Version: 103
+
+
+执行 Teaclave SGX SDK 中的简单实例 helloworld ，检查是否正常运行。
+
+```bash
+root@docker:~# cd sgx/samplecode/helloworld/
+root@docker:~/sgx/samplecode/helloworld# make
+root@docker:~/sgx/samplecode/helloworld# cd bin/
+root@docker:~/sgx/samplecode/helloworld/bin# ./app
+[+] global_eid: 2
+This is normal world string passed into enclave!
+This is a Rust string!
+[+] say_something success ...
+```
+至此，我们已经成功在自己的机器上跑起来了 Teaclave SGX SDK 的 helloworld 示例啦！
+
+## Teaclave SGX SDK 示例 helloworld 剖析
+
+接下来，我们通过阅读 helloworld 这个简单的例子来理解 Teaclave SGX SDK 应用程序的组织结构和运行方式。
+
+### helloworld 目录结构
+
+```tree
+helloworld/
+├── app
+│ ├── app.c
+│ └── app.h
+├── bin
+│ └── readme.txt
+├── enclave
+│ ├── Cargo.toml
+│ ├── Enclave.config.xml
+│ ├── Enclave.edl
+│ ├── Enclave.lds
+│ ├── Enclave_private.pem
+│ ├── Makefile
+│ ├── src
+│ │ └── lib.rs
+│ ├── x86_64-unknown-linux-sgx.json
+│ └── Xargo.toml
+├── lib
+│ └── readme.txt
+└── Makefile
+```
+
+helloworld 的目录结构和 Intel SGX 的
[SampleEnclave](https://github.com/intel/linux-sgx/blob/HEAD/SampleCode/SampleEnclave)
目录结构非常类似。
++ app 目录中存放的是不可信部分代码，包括 `main` 函数以及 `OCALL` 函数具体逻辑实现。
++ enclave 目录中存放的是可信部分代码，主要是 `ECALL` 函数具体逻辑实现。
++ 不同于 SGX ，应用安全区的代码实现位于 **`src/lib.rs`**, 该文件是整个 `helloworld` 文件夹中唯一使用
Rust 编写的文件，程序员可以在该文件中增加需要的功能。
++ 另外，enclave 文件夹下多了 `Cargo.toml`, `src/lib.rs`,
`x86_64-unknown-linux-sgx.json`, `Xargo.toml`：
++ **`Cargo.toml`**: 项目清单文件，包括项目名称、项目版本以及依赖项等。
++ **`x86_64-unknown-linux-sgx.json`** 和 **`Xargo.toml`**
描述了用于项目交叉编译的信息。
+
+### 重要代码文件解析
+
++ **`Enclave.edl`** \
+该文件规定了 Enclave 边界 `ECALL/OCALL` 的定义。
+
+```edl
+enclave {
+from "sgx_tstd.edl" import *;
+from "sgx_stdio.edl" import *;
+from "sgx_backtrace.edl" import *;
+from "sgx_tstdc.edl" import *;
+
+
[GitHub] [incubator-teaclave-website] ya0guang commented on a change in pull request #5: add developing Teaclave SGX Application doc
ya0guang commented on a change in pull request #5: URL: https://github.com/apache/incubator-teaclave-website/pull/5#discussion_r690730153 ## File path: site/blog/2021-08-13-developing-sgx-application-with-teaclave-sgx-sdk.md ## @@ -0,0 +1,331 @@ +--- +title: 使用 Teaclave SGX SDK 开发 SGX 应用 +date: 2021-08-13 +author: Wenwen Ruan +--- + +[[TOC]] + + +## Teaclave SGX SDK应用开发环境简介以及搭建 + +Intel SGX (软件防护扩展，Software Guard Extension) 提供了在一个安全的 enclave（飞地）中执行代码的能力，enclave 可以提供一个隔离的可信执行环境，在操作系统、BIOS 和虚拟机监控器等系统软件均不可信的情况下，仍然对 enclave 内部的代码和数据提供保护，保障用户的关键数据和代码的机密性和完整性。 Review comment: ……除了CPU之外的……均不可信 ## File path: site/blog/2021-08-13-developing-sgx-application-with-teaclave-sgx-sdk.md ## @@ -0,0 +1,331 @@ +--- +title: 使用 Teaclave SGX SDK 开发 SGX 应用 +date: 2021-08-13 +author: Wenwen Ruan +--- + +[[TOC]] + + +## Teaclave SGX SDK应用开发环境简介以及搭建 + +Intel SGX (软件防护扩展，Software Guard Extension) 提供了在一个安全的 enclave（飞地）中执行代码的能力，enclave 可以提供一个隔离的可信执行环境，在操作系统、BIOS 和虚拟机监控器等系统软件均不可信的情况下，仍然对 enclave 内部的代码和数据提供保护，保障用户的关键数据和代码的机密性和完整性。 Review comment: > ……除了CPU之外的……均不可信 建议顺便一句话介绍SGX和enclave **是什么** ## File path: site/blog/2021-08-13-developing-sgx-application-with-teaclave-sgx-sdk.md ## @@ -0,0 +1,331 @@ +--- +title: 使用 Teaclave SGX SDK 开发 SGX 应用 +date: 2021-08-13 +author: Wenwen Ruan +--- + +[[TOC]] + + +## Teaclave SGX SDK应用开发环境简介以及搭建 + +Intel SGX (软件防护扩展，Software Guard Extension) 提供了在一个安全的 enclave（飞地）中执行代码的能力，enclave 可以提供一个隔离的可信执行环境，在操作系统、BIOS 和虚拟机监控器等系统软件均不可信的情况下，仍然对 enclave 内部的代码和数据提供保护，保障用户的关键数据和代码的机密性和完整性。 + +但如果 Intel SGX 程序仍然使用 C/C++ 这类内存不安全的语言开发的话，就会和传统软件一样面临着传统的内存破坏漏洞。对于 enclave 来说，受到的危害会更为严重，因为 enclave 中保存的多是机密数据和代码。Teaclave SGX 的主要目标就是通过使用高效的内存安全语言 —— Rust 来支持 enclave 应用程序的开发，从而在保证 Intel SGX enclave 内存安全的同时不会带来显著的性能开销。 + +Teaclave SGX SDK 内部结构分为三层： + ++ 最底层是使用 C/C++ 和汇编实现的 Intel SGX SDK。 ++ 中间层是 Rust 对 C/C++ 的 FFI (Foreign function Interfaces, 外部函数接口)。 ++ 最高层是 Teaclave SGX SDK。 + + + +Teaclave SGX SDK 应用程序开发者在进行开发时就只需要基于最上层的 Teaclave SGX SDK 来进行开发，底层的实现对于开发者来说是透明的。本文将从开发者的角度介绍基于 Teaclave SGX SDK 开发自己的应用程序的过程。 + +### 准备条件 + ++ Ubuntu16.04 或者 18.04 或者 20.04 (Teaclave SGX SDK v1.1.3 中增加了对 Ubuntu 20.04 的支持) ++ docker 环境 + +*本文基于 Teaclave SGX SDK v1.1.3 提交哈希值：d107bd0718f723221750a4f2973451b386cbf9d2* + + +### 基于 docker 配置 Teaclave SGX SDK 开发环境 + +首先需要用户机器 CPU 支持 Intel SGX 并且在 BIOS 上开启了 Intel SGX 支持。用户可以通过 [SGX-hardware项目](https://github.com/ayeks/SGX-hardware) 或者在 [Intel 官网](https://www.intel.com/content/www/us/en/products/details/processors.html) 中搜索自己的 CPU 型号查看是否支持 Intel SGX。下图以 Intel Core i7-7700K 处理器为例，如下图所示，该机型支持 SGX。 + + + +当确定 CPU 支持 Intel SGX 之后，还需要开启 BIOS 中的 SGX 选项。CPU 上的 SGX 选项可能有 `enabled` 或者 `software controlled`。具有 `enabled` 选项的主机直接在 BIOS 上选择 `enabled` 即可，而`software controlled` 表示 SGX 的开启需要由软件触发，还需通过 Intel 官方提供的 [sgx-software-enable](https://github.com/intel/sgx-software-enable) 开启。下载好 `sgx-software-enable` 之后，运行 `Makefile` 编译生成可执行代码 `sgx_enable` ，执行 `sudo ./sgx_enable` 顺利运行后重启主机，即可顺利开启 Intel SGX。 + +硬件条件准备完毕之后，还需要安装 [Linux SGX 驱动](https://download.01.org/intel-sgx/sgx-linux/2.10/distro/ubuntu16.04-server/sgx_linux_x64_driver_2.6.0_602374c.bin) ，安装完毕之后需要确认 `/dev/isgx` 的存在。 Review comment: 这个驱动是不是只针对Ubuntu 16.04 server的？前面提到了对于Ubuntu其他版本的支持，如果是的话建议注明或者介绍其他如何找到对应版本的驱动。 ## File path: site/blog/2021-08-13-developing-sgx-application-with-teaclave-sgx-sdk.md ## @@ -0,0 +1,331 @@ +--- +title: 使用 Teaclave SGX SDK 开发 SGX 应用 +date: 2021-08-13 +author: Wenwen Ruan +--- + +[[TOC]] + + +## Teaclave SGX SDK应用开发环境简介以及搭建 + +Intel SGX (软件防护扩展，Software Guard Extension) 提供了在一个安全的 enclave（飞地）中执行代码的能力，enclave 可以提供一个隔离的可信执行环境，在操作系统、BIOS 和虚拟机监控器等系统软件均不可信的情况下，仍然对 enclave 内部的代码和数据提供保护，保障用户的关键数据和代码的机密性和完整性。 + +但如果 Intel SGX 程序仍然使用 C/C++ 这类内存不安全的语言开发的话，就会和传统软件一样面临着传统的内存破坏漏洞。对于 enclave 来说，受到的危害会更为严重，因为 enclave 中保存的多是机密数据和代码。Teaclave SGX 的主要目标就是通过使用高效的内存安全语言 —— Rust 来支持 enclave 应用程序的开发，从而在保证 Intel SGX enclave 内存安全的同时不会带来显著的性能开销。 + +Teaclave SGX SDK 内部结构分为三层： + ++ 最底层是使用 C/C++ 和汇编实现的 Intel SGX SDK。 ++ 中间层是 Rust 对 C/C++ 的 FFI (Foreign function Interfaces, 外部函数接口)。 ++ 最高层是 Teaclave SGX SDK。 + + + +Teaclave SGX SDK 应用程序开发者在进行开发时就只需要基于最上层的 Teaclave SGX SDK 来进行开发，底层的实现对于开发者来说是透明的。本文将从开发者的角度介绍基于 Teaclave SGX SDK 开发自己的应用程序的过程。 + +### 准备条件 + ++ Ubuntu16.04 或者 18.04 或者 20.04 (Teaclave SGX SDK v1.1.3 中增加了对 Ubuntu 20.04 的支持) ++ docker 环境 + +*本文基于 Teaclave SGX SDK v1.1.3 提交哈希值：d107bd0718f723221750a4f2973451b386cbf9d2* + + +### 基于 docker 配置 Teaclave SGX SDK 开发环境 + +首先需要用户机器 CPU 支持 Intel SGX 并且在 BIOS 上开启了 Intel SGX 支持。用户可以通过 [SGX-hardware项目](https://github.com/ayeks/SGX-hardware) 或者在 [Intel 官网](https://www.intel.com/content/www/us/en/products/details/processors.html) 中搜索自己的 CPU 型号查看是否支持 Intel SGX。下图以 Intel Core i7-7700K 处理器为例，
[GitHub] [incubator-teaclave-website] ya0guang commented on a change in pull request #5: add developing Teaclave SGX Application doc
ya0guang commented on a change in pull request #5: URL: https://github.com/apache/incubator-teaclave-website/pull/5#discussion_r690734576 ## File path: site/blog/2021-08-13-developing-sgx-application-with-teaclave-sgx-sdk.md ## @@ -0,0 +1,331 @@ +--- +title: 使用 Teaclave SGX SDK 开发 SGX 应用 +date: 2021-08-13 +author: Wenwen Ruan +--- + +[[TOC]] + + +## Teaclave SGX SDK应用开发环境简介以及搭建 + +Intel SGX (软件防护扩展，Software Guard Extension) 提供了在一个安全的 enclave（飞地）中执行代码的能力，enclave 可以提供一个隔离的可信执行环境，在操作系统、BIOS 和虚拟机监控器等系统软件均不可信的情况下，仍然对 enclave 内部的代码和数据提供保护，保障用户的关键数据和代码的机密性和完整性。 + +但如果 Intel SGX 程序仍然使用 C/C++ 这类内存不安全的语言开发的话，就会和传统软件一样面临着传统的内存破坏漏洞。对于 enclave 来说，受到的危害会更为严重，因为 enclave 中保存的多是机密数据和代码。Teaclave SGX 的主要目标就是通过使用高效的内存安全语言 —— Rust 来支持 enclave 应用程序的开发，从而在保证 Intel SGX enclave 内存安全的同时不会带来显著的性能开销。 + +Teaclave SGX SDK 内部结构分为三层： + ++ 最底层是使用 C/C++ 和汇编实现的 Intel SGX SDK。 ++ 中间层是 Rust 对 C/C++ 的 FFI (Foreign function Interfaces, 外部函数接口)。 ++ 最高层是 Teaclave SGX SDK。 + + + +Teaclave SGX SDK 应用程序开发者在进行开发时就只需要基于最上层的 Teaclave SGX SDK 来进行开发，底层的实现对于开发者来说是透明的。本文将从开发者的角度介绍基于 Teaclave SGX SDK 开发自己的应用程序的过程。 + +### 准备条件 + ++ Ubuntu16.04 或者 18.04 或者 20.04 (Teaclave SGX SDK v1.1.3 中增加了对 Ubuntu 20.04 的支持) ++ docker 环境 + +*本文基于 Teaclave SGX SDK v1.1.3 提交哈希值：d107bd0718f723221750a4f2973451b386cbf9d2* + + +### 基于 docker 配置 Teaclave SGX SDK 开发环境 + +首先需要用户机器 CPU 支持 Intel SGX 并且在 BIOS 上开启了 Intel SGX 支持。用户可以通过 [SGX-hardware项目](https://github.com/ayeks/SGX-hardware) 或者在 [Intel 官网](https://www.intel.com/content/www/us/en/products/details/processors.html) 中搜索自己的 CPU 型号查看是否支持 Intel SGX。下图以 Intel Core i7-7700K 处理器为例，如下图所示，该机型支持 SGX。 + + + +当确定 CPU 支持 Intel SGX 之后，还需要开启 BIOS 中的 SGX 选项。CPU 上的 SGX 选项可能有 `enabled` 或者 `software controlled`。具有 `enabled` 选项的主机直接在 BIOS 上选择 `enabled` 即可，而`software controlled` 表示 SGX 的开启需要由软件触发，还需通过 Intel 官方提供的 [sgx-software-enable](https://github.com/intel/sgx-software-enable) 开启。下载好 `sgx-software-enable` 之后，运行 `Makefile` 编译生成可执行代码 `sgx_enable` ，执行 `sudo ./sgx_enable` 顺利运行后重启主机，即可顺利开启 Intel SGX。 + +硬件条件准备完毕之后，还需要安装 [Linux SGX 驱动](https://download.01.org/intel-sgx/sgx-linux/2.10/distro/ubuntu16.04-server/sgx_linux_x64_driver_2.6.0_602374c.bin) ，安装完毕之后需要确认 `/dev/isgx` 的存在。 Review comment: 这个驱动是不是只针对Ubuntu 16.04 server的？前面提到了对于Ubuntu其他版本的支持，如果是的话建议注明或者介绍其他如何找到对应版本的驱动。 ## File path: site/blog/2021-08-13-developing-sgx-application-with-teaclave-sgx-sdk.md ## @@ -0,0 +1,331 @@ +--- +title: 使用 Teaclave SGX SDK 开发 SGX 应用 +date: 2021-08-13 +author: Wenwen Ruan +--- + +[[TOC]] + + +## Teaclave SGX SDK应用开发环境简介以及搭建 + +Intel SGX (软件防护扩展，Software Guard Extension) 提供了在一个安全的 enclave（飞地）中执行代码的能力，enclave 可以提供一个隔离的可信执行环境，在操作系统、BIOS 和虚拟机监控器等系统软件均不可信的情况下，仍然对 enclave 内部的代码和数据提供保护，保障用户的关键数据和代码的机密性和完整性。 + +但如果 Intel SGX 程序仍然使用 C/C++ 这类内存不安全的语言开发的话，就会和传统软件一样面临着传统的内存破坏漏洞。对于 enclave 来说，受到的危害会更为严重，因为 enclave 中保存的多是机密数据和代码。Teaclave SGX 的主要目标就是通过使用高效的内存安全语言 —— Rust 来支持 enclave 应用程序的开发，从而在保证 Intel SGX enclave 内存安全的同时不会带来显著的性能开销。 + +Teaclave SGX SDK 内部结构分为三层： + ++ 最底层是使用 C/C++ 和汇编实现的 Intel SGX SDK。 ++ 中间层是 Rust 对 C/C++ 的 FFI (Foreign function Interfaces, 外部函数接口)。 ++ 最高层是 Teaclave SGX SDK。 + + + +Teaclave SGX SDK 应用程序开发者在进行开发时就只需要基于最上层的 Teaclave SGX SDK 来进行开发，底层的实现对于开发者来说是透明的。本文将从开发者的角度介绍基于 Teaclave SGX SDK 开发自己的应用程序的过程。 + +### 准备条件 + ++ Ubuntu16.04 或者 18.04 或者 20.04 (Teaclave SGX SDK v1.1.3 中增加了对 Ubuntu 20.04 的支持) ++ docker 环境 + +*本文基于 Teaclave SGX SDK v1.1.3 提交哈希值：d107bd0718f723221750a4f2973451b386cbf9d2* + + +### 基于 docker 配置 Teaclave SGX SDK 开发环境 + +首先需要用户机器 CPU 支持 Intel SGX 并且在 BIOS 上开启了 Intel SGX 支持。用户可以通过 [SGX-hardware项目](https://github.com/ayeks/SGX-hardware) 或者在 [Intel 官网](https://www.intel.com/content/www/us/en/products/details/processors.html) 中搜索自己的 CPU 型号查看是否支持 Intel SGX。下图以 Intel Core i7-7700K 处理器为例，如下图所示，该机型支持 SGX。 + + + +当确定 CPU 支持 Intel SGX 之后，还需要开启 BIOS 中的 SGX 选项。CPU 上的 SGX 选项可能有 `enabled` 或者 `software controlled`。具有 `enabled` 选项的主机直接在 BIOS 上选择 `enabled` 即可，而`software controlled` 表示 SGX 的开启需要由软件触发，还需通过 Intel 官方提供的 [sgx-software-enable](https://github.com/intel/sgx-software-enable) 开启。下载好 `sgx-software-enable` 之后，运行 `Makefile` 编译生成可执行代码 `sgx_enable` ，执行 `sudo ./sgx_enable` 顺利运行后重启主机，即可顺利开启 Intel SGX。 + +硬件条件准备完毕之后，还需要安装 [Linux SGX 驱动](https://download.01.org/intel-sgx/sgx-linux/2.10/distro/ubuntu16.04-server/sgx_linux_x64_driver_2.6.0_602374c.bin) ，安装完毕之后需要确认 `/dev/isgx` 的存在。 + +下载 Teaclave SGX SDK 以及支持编译 SGX 设备的 docker image。 + +`$ https://github.com/apache/incubator-teaclave-sgx-sdk` + +`$ docker pull baiduxlab/sgx-rust` + +启动一个 docker，并且把 Teaclave SGX SDK 项目目录映射到 docker 中。 + +`$ docker run -v /your/absolute/path/to/incubator-teaclave-sgx-sdk:/root/sgx -ti --device /dev/isgx baiduxlab/sgx-rust` + +在运行的 docker container 中启动
[GitHub] [incubator-teaclave-website] ya0guang commented on a change in pull request #5: add developing Teaclave SGX Application doc
ya0guang commented on a change in pull request #5: URL: https://github.com/apache/incubator-teaclave-website/pull/5#discussion_r690730153 ## File path: site/blog/2021-08-13-developing-sgx-application-with-teaclave-sgx-sdk.md ## @@ -0,0 +1,331 @@ +--- +title: 使用 Teaclave SGX SDK 开发 SGX 应用 +date: 2021-08-13 +author: Wenwen Ruan +--- + +[[TOC]] + + +## Teaclave SGX SDK应用开发环境简介以及搭建 + +Intel SGX (软件防护扩展，Software Guard Extension) 提供了在一个安全的 enclave（飞地）中执行代码的能力，enclave 可以提供一个隔离的可信执行环境，在操作系统、BIOS 和虚拟机监控器等系统软件均不可信的情况下，仍然对 enclave 内部的代码和数据提供保护，保障用户的关键数据和代码的机密性和完整性。 Review comment: > ……除了CPU之外的……均不可信 建议顺便一句话介绍SGX和enclave **是什么** -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] ya0guang commented on a change in pull request #5: add developing Teaclave SGX Application doc
ya0guang commented on a change in pull request #5: URL: https://github.com/apache/incubator-teaclave-website/pull/5#discussion_r690730153 ## File path: site/blog/2021-08-13-developing-sgx-application-with-teaclave-sgx-sdk.md ## @@ -0,0 +1,331 @@ +--- +title: 使用 Teaclave SGX SDK 开发 SGX 应用 +date: 2021-08-13 +author: Wenwen Ruan +--- + +[[TOC]] + + +## Teaclave SGX SDK应用开发环境简介以及搭建 + +Intel SGX (软件防护扩展，Software Guard Extension) 提供了在一个安全的 enclave（飞地）中执行代码的能力，enclave 可以提供一个隔离的可信执行环境，在操作系统、BIOS 和虚拟机监控器等系统软件均不可信的情况下，仍然对 enclave 内部的代码和数据提供保护，保障用户的关键数据和代码的机密性和完整性。 Review comment: ……除了CPU之外的……均不可信 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] mssun commented on a change in pull request #5: add developing Teaclave SGX Application doc
mssun commented on a change in pull request #5: URL: https://github.com/apache/incubator-teaclave-website/pull/5#discussion_r688226671 ## File path: site/blog/2021-08-13-developing-SGX-Application-with-Teaclave-SGX-SDK.md ## @@ -0,0 +1,350 @@ +--- +title: 使用 Teaclave SGX SDK 开发 SGX 应用 +date: 2021-08-13 +author: Wenwen Ruan +--- + + +- [1 Teaclave SGX SDK应用开发环境简介以及搭建](#1-teaclave-sgx-sdk应用开发环境简介以及搭建) +- [1.1 准备条件](#11-准备条件) +- [1.2 硬件模式+docker真实执行](#12-硬件模式docker真实执行) +- [2 一个简单的 Rust SGX 程序：helloworld](#2-一个简单的-rust-sgx-程序helloworld) +- [2.1 helloworld 目录结构](#21-helloworld-目录结构) +- [2.2 重要代码文件解析](#22-重要代码文件解析) +- [2.3 编译后的代码目录](#23-编译后的代码目录) +- [3 开发者如何开发自己的 Rust SGX Application](#3-开发者如何开发自己的-rust-sgx-application) +- [3.1 添加自定义的函数](#31-添加自定义的函数) +- [3.2 调用 Teaclave SGX SDK 提供的 `crate`](#32-调用-teaclave-sgx-sdk-提供的-crate) +- [4 总结](#4-总结) +- [5 一些小tip](#5-一些小tip) +- [6 参考](#6-参考) + + Review comment: You can use `[[toc]]` in vuepress. (https://v1.vuepress.vuejs.org/guide/markdown.html#table-of-contents) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] RMheng opened a new pull request #5: add developing Teaclave SGX Application doc
RMheng opened a new pull request #5: URL: https://github.com/apache/incubator-teaclave-website/pull/5 add developing SGX Application with Teaclave SGX SDK Chinese doc. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] mssun commented on pull request #4: Add Crust Network project
mssun commented on pull request #4: URL: https://github.com/apache/incubator-teaclave-website/pull/4#issuecomment-810462628 Merged, thanks. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] mssun merged pull request #4: Add Crust Network project
mssun merged pull request #4: URL: https://github.com/apache/incubator-teaclave-website/pull/4 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] zikunfan opened a new pull request #4: Add Crust Network project
zikunfan opened a new pull request #4: URL: https://github.com/apache/incubator-teaclave-website/pull/4 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] mssun merged pull request #3: Update 2021-03-15-welcome-rust-optee-trustzone-sdk.md
mssun merged pull request #3: URL: https://github.com/apache/incubator-teaclave-website/pull/3 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] qinkunbao opened a new pull request #3: Update 2021-03-15-welcome-rust-optee-trustzone-sdk.md
qinkunbao opened a new pull request #3: URL: https://github.com/apache/incubator-teaclave-website/pull/3 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] mssun merged pull request #2: Update 2020-10-22-announcing-teaclave-0.1.0.md
mssun merged pull request #2: URL: https://github.com/apache/incubator-teaclave-website/pull/2 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] qinkunbao opened a new pull request #2: Update 2020-10-22-announcing-teaclave-0.1.0.md
qinkunbao opened a new pull request #2: URL: https://github.com/apache/incubator-teaclave-website/pull/2 Fix some typos. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Teaclave Website
Site's looking pretty nice so far! On Sun, 24 May 2020 at 16:30, Furkan KAMACI wrote: > > Hi Mingshen, > > Thanks for initiating this! > > Kind Regards, > Furkan KAMACI > > On Mon, May 25, 2020 at 12:18 AM Mingshen Sun wrote: > > > Hi, I just added the blog feature in our website: > > https://teaclave.apache.org/blog/ > > > > Right now, only previous podling reports are posted. Later, we can add > > more articles such as release note, background knowledge, design > > choice, case studies, and community activities. Thanks! > > > > On Sat, May 16, 2020 at 12:24 PM Felix Cheung > > wrote: > > > > > > Great! > > > > > > > > > From: Mingshen Sun > > > Sent: Friday, May 15, 2020 6:44:48 PM > > > To: dev@teaclave.apache.org > > > Subject: Re: Teaclave Website > > > > > > Thank you. I've also added community and contributors pages to the > > website. > > > > > > On Fri, May 15, 2020 at 6:18 PM Furkan KAMACI > > wrote: > > > > > > > > Hi, > > > > > > > > Thanks for your effort on the website! I see that the ASF Sponsorship > > URL > > > > is not right. So, I've created a PR for it. > > > > > > > > Kind Regards, > > > > Furkan KAMACI > > > > > > > > > > > > > > > > On Sat, May 16, 2020 at 1:35 AM Felix Cheung < > > felixcheun...@hotmail.com> > > > > wrote: > > > > > > > > > This is great - you might want to add links to mail archive (dev@) > > and a > > > > > page on the community (people) > > > > > > > > > > > > https://incubator.apache.org/guides/sites.html#creating_a_good_podling_site > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > From: Mingshen Sun > > > > > Sent: Thursday, May 14, 2020 5:55:35 PM > > > > > To: dev@teaclave.apache.org > > > > > Subject: Re: Teaclave Website > > > > > > > > > > Hi folks, > > > > > > > > > > I have setup a website for Teaclave: https://teaclave.apache.org/ > > > > > > > > > > Currently, the site generator can automatically fetch docs from our > > > > > main repository. The source code can be found here: > > > > > https://github.com/apache/incubator-teaclave-website/. > > > > > > > > > > I'll include more information in this website. Feel free to comment > > > > > and help me to improve the website. Thanks. > > > > > > > > > > > > > > > On Wed, May 13, 2020 at 6:39 PM Furkan KAMACI < > > furkankam...@gmail.com> > > > > > wrote: > > > > > > > > > > > > Hi Mingshen, > > > > > > > > > > > > Great! > > > > > > > > > > > > Kind Regards, > > > > > > Furkan KAMACI > > > > > > > > > > > > On Thu, May 14, 2020 at 4:38 AM Mingshen Sun > > wrote: > > > > > > > > > > > > > Great, I can access this repo now. It takes about 1h to > > propagate the > > > > > rule. > > > > > > > > > > > > > > On Wed, May 13, 2020 at 6:19 PM Mingshen Sun > > wrote: > > > > > > > > > > > > > > > > I have created a new repo (apache/incubator-teaclave-website) > > for > > > > > > > > hosting sources and pages here [1]. > > > > > > > > > > > > > > > > It appears in GitHub immediately > > > > > > > > (https://github.com/apache/incubator-teaclave-website). > > However, I > > > > > > > > don't have access to this repo now. I'm not sure whether it > > takes > > > > > some > > > > > > > > time to propagate the access control rule to GitHub or I need > > to > > > > > > > > submit a ticket to INFRA for help. > > > > > > > > > > > > > > > > [1] https://gitbox.apache.org/setup/newrepo.html. > > > > > > > > > > > > > > > > On Wed, May 13, 2020 at 3:45 PM Furkan KAMACI < > > > > > furkanka
Re: Teaclave Website
Hi Mingshen, Thanks for initiating this! Kind Regards, Furkan KAMACI On Mon, May 25, 2020 at 12:18 AM Mingshen Sun wrote: > Hi, I just added the blog feature in our website: > https://teaclave.apache.org/blog/ > > Right now, only previous podling reports are posted. Later, we can add > more articles such as release note, background knowledge, design > choice, case studies, and community activities. Thanks! > > On Sat, May 16, 2020 at 12:24 PM Felix Cheung > wrote: > > > > Great! > > > > > > From: Mingshen Sun > > Sent: Friday, May 15, 2020 6:44:48 PM > > To: dev@teaclave.apache.org > > Subject: Re: Teaclave Website > > > > Thank you. I've also added community and contributors pages to the > website. > > > > On Fri, May 15, 2020 at 6:18 PM Furkan KAMACI > wrote: > > > > > > Hi, > > > > > > Thanks for your effort on the website! I see that the ASF Sponsorship > URL > > > is not right. So, I've created a PR for it. > > > > > > Kind Regards, > > > Furkan KAMACI > > > > > > > > > > > > On Sat, May 16, 2020 at 1:35 AM Felix Cheung < > felixcheun...@hotmail.com> > > > wrote: > > > > > > > This is great - you might want to add links to mail archive (dev@) > and a > > > > page on the community (people) > > > > > > > > > https://incubator.apache.org/guides/sites.html#creating_a_good_podling_site > > > > > > > > > > > > > > > > > > > > > > > > From: Mingshen Sun > > > > Sent: Thursday, May 14, 2020 5:55:35 PM > > > > To: dev@teaclave.apache.org > > > > Subject: Re: Teaclave Website > > > > > > > > Hi folks, > > > > > > > > I have setup a website for Teaclave: https://teaclave.apache.org/ > > > > > > > > Currently, the site generator can automatically fetch docs from our > > > > main repository. The source code can be found here: > > > > https://github.com/apache/incubator-teaclave-website/. > > > > > > > > I'll include more information in this website. Feel free to comment > > > > and help me to improve the website. Thanks. > > > > > > > > > > > > On Wed, May 13, 2020 at 6:39 PM Furkan KAMACI < > furkankam...@gmail.com> > > > > wrote: > > > > > > > > > > Hi Mingshen, > > > > > > > > > > Great! > > > > > > > > > > Kind Regards, > > > > > Furkan KAMACI > > > > > > > > > > On Thu, May 14, 2020 at 4:38 AM Mingshen Sun > wrote: > > > > > > > > > > > Great, I can access this repo now. It takes about 1h to > propagate the > > > > rule. > > > > > > > > > > > > On Wed, May 13, 2020 at 6:19 PM Mingshen Sun > wrote: > > > > > > > > > > > > > > I have created a new repo (apache/incubator-teaclave-website) > for > > > > > > > hosting sources and pages here [1]. > > > > > > > > > > > > > > It appears in GitHub immediately > > > > > > > (https://github.com/apache/incubator-teaclave-website). > However, I > > > > > > > don't have access to this repo now. I'm not sure whether it > takes > > > > some > > > > > > > time to propagate the access control rule to GitHub or I need > to > > > > > > > submit a ticket to INFRA for help. > > > > > > > > > > > > > > [1] https://gitbox.apache.org/setup/newrepo.html. > > > > > > > > > > > > > > On Wed, May 13, 2020 at 3:45 PM Furkan KAMACI < > > > > furkankam...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > > > Hi Mingshen, > > > > > > > > > > > > > > > > Sure! Feel free to ask if you have any questions. > > > > > > > > > > > > > > > > Kind Regards, > > > > > > > > Furkan KAMACI > > > > > > > > > > > > > > > > On Thu, May 14, 2020 at 1:04 AM Mingshen Sun < > ms...@apache.org> > > > > wrote: > > > > > > > > > &g
Re: Teaclave Website
Hi, I just added the blog feature in our website: https://teaclave.apache.org/blog/ Right now, only previous podling reports are posted. Later, we can add more articles such as release note, background knowledge, design choice, case studies, and community activities. Thanks! On Sat, May 16, 2020 at 12:24 PM Felix Cheung wrote: > > Great! > > > From: Mingshen Sun > Sent: Friday, May 15, 2020 6:44:48 PM > To: dev@teaclave.apache.org > Subject: Re: Teaclave Website > > Thank you. I've also added community and contributors pages to the website. > > On Fri, May 15, 2020 at 6:18 PM Furkan KAMACI wrote: > > > > Hi, > > > > Thanks for your effort on the website! I see that the ASF Sponsorship URL > > is not right. So, I've created a PR for it. > > > > Kind Regards, > > Furkan KAMACI > > > > > > > > On Sat, May 16, 2020 at 1:35 AM Felix Cheung > > wrote: > > > > > This is great - you might want to add links to mail archive (dev@) and a > > > page on the community (people) > > > > > > https://incubator.apache.org/guides/sites.html#creating_a_good_podling_site > > > > > > > > > > > > > > > > > > From: Mingshen Sun > > > Sent: Thursday, May 14, 2020 5:55:35 PM > > > To: dev@teaclave.apache.org > > > Subject: Re: Teaclave Website > > > > > > Hi folks, > > > > > > I have setup a website for Teaclave: https://teaclave.apache.org/ > > > > > > Currently, the site generator can automatically fetch docs from our > > > main repository. The source code can be found here: > > > https://github.com/apache/incubator-teaclave-website/. > > > > > > I'll include more information in this website. Feel free to comment > > > and help me to improve the website. Thanks. > > > > > > > > > On Wed, May 13, 2020 at 6:39 PM Furkan KAMACI > > > wrote: > > > > > > > > Hi Mingshen, > > > > > > > > Great! > > > > > > > > Kind Regards, > > > > Furkan KAMACI > > > > > > > > On Thu, May 14, 2020 at 4:38 AM Mingshen Sun wrote: > > > > > > > > > Great, I can access this repo now. It takes about 1h to propagate the > > > rule. > > > > > > > > > > On Wed, May 13, 2020 at 6:19 PM Mingshen Sun wrote: > > > > > > > > > > > > I have created a new repo (apache/incubator-teaclave-website) for > > > > > > hosting sources and pages here [1]. > > > > > > > > > > > > It appears in GitHub immediately > > > > > > (https://github.com/apache/incubator-teaclave-website). However, I > > > > > > don't have access to this repo now. I'm not sure whether it takes > > > some > > > > > > time to propagate the access control rule to GitHub or I need to > > > > > > submit a ticket to INFRA for help. > > > > > > > > > > > > [1] https://gitbox.apache.org/setup/newrepo.html. > > > > > > > > > > > > On Wed, May 13, 2020 at 3:45 PM Furkan KAMACI < > > > furkankam...@gmail.com> > > > > > wrote: > > > > > > > > > > > > > > Hi Mingshen, > > > > > > > > > > > > > > Sure! Feel free to ask if you have any questions. > > > > > > > > > > > > > > Kind Regards, > > > > > > > Furkan KAMACI > > > > > > > > > > > > > > On Thu, May 14, 2020 at 1:04 AM Mingshen Sun > > > wrote: > > > > > > > > > > > > > > > Thanks for asking, Furkan. > > > > > > > > > > > > > > > > I did some research on how to deploy a website under the Apache > > > > > > > > infrastructure. There are several options > > > > > > > > (https://infra.apache.org/project-site.html). Since we are > > > mainly > > > > > > > > working on GitHub, I think the GitHub pages fit our needs. We > > > can use > > > > > > > > .asf.yml to configure the deployment > > > > > > > > ( > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+
Re: Teaclave Website
Great! From: Mingshen Sun Sent: Friday, May 15, 2020 6:44:48 PM To: dev@teaclave.apache.org Subject: Re: Teaclave Website Thank you. I've also added community and contributors pages to the website. On Fri, May 15, 2020 at 6:18 PM Furkan KAMACI wrote: > > Hi, > > Thanks for your effort on the website! I see that the ASF Sponsorship URL > is not right. So, I've created a PR for it. > > Kind Regards, > Furkan KAMACI > > > > On Sat, May 16, 2020 at 1:35 AM Felix Cheung > wrote: > > > This is great - you might want to add links to mail archive (dev@) and a > > page on the community (people) > > > > https://incubator.apache.org/guides/sites.html#creating_a_good_podling_site > > > > > > > > > > > > From: Mingshen Sun > > Sent: Thursday, May 14, 2020 5:55:35 PM > > To: dev@teaclave.apache.org > > Subject: Re: Teaclave Website > > > > Hi folks, > > > > I have setup a website for Teaclave: https://teaclave.apache.org/ > > > > Currently, the site generator can automatically fetch docs from our > > main repository. The source code can be found here: > > https://github.com/apache/incubator-teaclave-website/. > > > > I'll include more information in this website. Feel free to comment > > and help me to improve the website. Thanks. > > > > > > On Wed, May 13, 2020 at 6:39 PM Furkan KAMACI > > wrote: > > > > > > Hi Mingshen, > > > > > > Great! > > > > > > Kind Regards, > > > Furkan KAMACI > > > > > > On Thu, May 14, 2020 at 4:38 AM Mingshen Sun wrote: > > > > > > > Great, I can access this repo now. It takes about 1h to propagate the > > rule. > > > > > > > > On Wed, May 13, 2020 at 6:19 PM Mingshen Sun wrote: > > > > > > > > > > I have created a new repo (apache/incubator-teaclave-website) for > > > > > hosting sources and pages here [1]. > > > > > > > > > > It appears in GitHub immediately > > > > > (https://github.com/apache/incubator-teaclave-website). However, I > > > > > don't have access to this repo now. I'm not sure whether it takes > > some > > > > > time to propagate the access control rule to GitHub or I need to > > > > > submit a ticket to INFRA for help. > > > > > > > > > > [1] https://gitbox.apache.org/setup/newrepo.html. > > > > > > > > > > On Wed, May 13, 2020 at 3:45 PM Furkan KAMACI < > > furkankam...@gmail.com> > > > > wrote: > > > > > > > > > > > > Hi Mingshen, > > > > > > > > > > > > Sure! Feel free to ask if you have any questions. > > > > > > > > > > > > Kind Regards, > > > > > > Furkan KAMACI > > > > > > > > > > > > On Thu, May 14, 2020 at 1:04 AM Mingshen Sun > > wrote: > > > > > > > > > > > > > Thanks for asking, Furkan. > > > > > > > > > > > > > > I did some research on how to deploy a website under the Apache > > > > > > > infrastructure. There are several options > > > > > > > (https://infra.apache.org/project-site.html). Since we are > > mainly > > > > > > > working on GitHub, I think the GitHub pages fit our needs. We > > can use > > > > > > > .asf.yml to configure the deployment > > > > > > > ( > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories > > > > > > > ). > > > > > > > > > > > > > > Let me try to start with a simple one with essential information > > and > > > > > > > later polishing details. > > > > > > > > > > > > > > On Wed, May 13, 2020 at 9:55 AM Furkan KAMACI < > > > > furkankam...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > As far as I know, there is not a website created for Teaclave > > yet. > > > > Is > > > > > > > there > > > > > > > > any progress for it? > > > > > > > > > > > > > > > > Kind Regards, > > > > > > > > Furkan KAMACI > > > > > > > > > > > > > > > > - > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Teaclave Website
Thank you. I've also added community and contributors pages to the website. On Fri, May 15, 2020 at 6:18 PM Furkan KAMACI wrote: > > Hi, > > Thanks for your effort on the website! I see that the ASF Sponsorship URL > is not right. So, I've created a PR for it. > > Kind Regards, > Furkan KAMACI > > > > On Sat, May 16, 2020 at 1:35 AM Felix Cheung > wrote: > > > This is great - you might want to add links to mail archive (dev@) and a > > page on the community (people) > > > > https://incubator.apache.org/guides/sites.html#creating_a_good_podling_site > > > > > > > > > > > > From: Mingshen Sun > > Sent: Thursday, May 14, 2020 5:55:35 PM > > To: dev@teaclave.apache.org > > Subject: Re: Teaclave Website > > > > Hi folks, > > > > I have setup a website for Teaclave: https://teaclave.apache.org/ > > > > Currently, the site generator can automatically fetch docs from our > > main repository. The source code can be found here: > > https://github.com/apache/incubator-teaclave-website/. > > > > I'll include more information in this website. Feel free to comment > > and help me to improve the website. Thanks. > > > > > > On Wed, May 13, 2020 at 6:39 PM Furkan KAMACI > > wrote: > > > > > > Hi Mingshen, > > > > > > Great! > > > > > > Kind Regards, > > > Furkan KAMACI > > > > > > On Thu, May 14, 2020 at 4:38 AM Mingshen Sun wrote: > > > > > > > Great, I can access this repo now. It takes about 1h to propagate the > > rule. > > > > > > > > On Wed, May 13, 2020 at 6:19 PM Mingshen Sun wrote: > > > > > > > > > > I have created a new repo (apache/incubator-teaclave-website) for > > > > > hosting sources and pages here [1]. > > > > > > > > > > It appears in GitHub immediately > > > > > (https://github.com/apache/incubator-teaclave-website). However, I > > > > > don't have access to this repo now. I'm not sure whether it takes > > some > > > > > time to propagate the access control rule to GitHub or I need to > > > > > submit a ticket to INFRA for help. > > > > > > > > > > [1] https://gitbox.apache.org/setup/newrepo.html. > > > > > > > > > > On Wed, May 13, 2020 at 3:45 PM Furkan KAMACI < > > furkankam...@gmail.com> > > > > wrote: > > > > > > > > > > > > Hi Mingshen, > > > > > > > > > > > > Sure! Feel free to ask if you have any questions. > > > > > > > > > > > > Kind Regards, > > > > > > Furkan KAMACI > > > > > > > > > > > > On Thu, May 14, 2020 at 1:04 AM Mingshen Sun > > wrote: > > > > > > > > > > > > > Thanks for asking, Furkan. > > > > > > > > > > > > > > I did some research on how to deploy a website under the Apache > > > > > > > infrastructure. There are several options > > > > > > > (https://infra.apache.org/project-site.html). Since we are > > mainly > > > > > > > working on GitHub, I think the GitHub pages fit our needs. We > > can use > > > > > > > .asf.yml to configure the deployment > > > > > > > ( > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories > > > > > > > ). > > > > > > > > > > > > > > Let me try to start with a simple one with essential information > > and > > > > > > > later polishing details. > > > > > > > > > > > > > > On Wed, May 13, 2020 at 9:55 AM Furkan KAMACI < > > > > furkankam...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > As far as I know, there is not a website created for Teaclave > > yet. > > > > Is > > > > > > > there > > > > > > > > any progress for it? > > > > > > > > > > > > > > > > Kind Regards, > > > > > > > > Furkan KAMACI > > > > > > > > > > > > > > > > - > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
[GitHub] [incubator-teaclave-website] mssun merged pull request #1: Fixed ASF sponsorship URL.
mssun merged pull request #1: URL: https://github.com/apache/incubator-teaclave-website/pull/1 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Teaclave Website
Hi, Thanks for your effort on the website! I see that the ASF Sponsorship URL is not right. So, I've created a PR for it. Kind Regards, Furkan KAMACI On Sat, May 16, 2020 at 1:35 AM Felix Cheung wrote: > This is great - you might want to add links to mail archive (dev@) and a > page on the community (people) > > https://incubator.apache.org/guides/sites.html#creating_a_good_podling_site > > > > > > From: Mingshen Sun > Sent: Thursday, May 14, 2020 5:55:35 PM > To: dev@teaclave.apache.org > Subject: Re: Teaclave Website > > Hi folks, > > I have setup a website for Teaclave: https://teaclave.apache.org/ > > Currently, the site generator can automatically fetch docs from our > main repository. The source code can be found here: > https://github.com/apache/incubator-teaclave-website/. > > I'll include more information in this website. Feel free to comment > and help me to improve the website. Thanks. > > > On Wed, May 13, 2020 at 6:39 PM Furkan KAMACI > wrote: > > > > Hi Mingshen, > > > > Great! > > > > Kind Regards, > > Furkan KAMACI > > > > On Thu, May 14, 2020 at 4:38 AM Mingshen Sun wrote: > > > > > Great, I can access this repo now. It takes about 1h to propagate the > rule. > > > > > > On Wed, May 13, 2020 at 6:19 PM Mingshen Sun wrote: > > > > > > > > I have created a new repo (apache/incubator-teaclave-website) for > > > > hosting sources and pages here [1]. > > > > > > > > It appears in GitHub immediately > > > > (https://github.com/apache/incubator-teaclave-website). However, I > > > > don't have access to this repo now. I'm not sure whether it takes > some > > > > time to propagate the access control rule to GitHub or I need to > > > > submit a ticket to INFRA for help. > > > > > > > > [1] https://gitbox.apache.org/setup/newrepo.html. > > > > > > > > On Wed, May 13, 2020 at 3:45 PM Furkan KAMACI < > furkankam...@gmail.com> > > > wrote: > > > > > > > > > > Hi Mingshen, > > > > > > > > > > Sure! Feel free to ask if you have any questions. > > > > > > > > > > Kind Regards, > > > > > Furkan KAMACI > > > > > > > > > > On Thu, May 14, 2020 at 1:04 AM Mingshen Sun > wrote: > > > > > > > > > > > Thanks for asking, Furkan. > > > > > > > > > > > > I did some research on how to deploy a website under the Apache > > > > > > infrastructure. There are several options > > > > > > (https://infra.apache.org/project-site.html). Since we are > mainly > > > > > > working on GitHub, I think the GitHub pages fit our needs. We > can use > > > > > > .asf.yml to configure the deployment > > > > > > ( > > > > > > > > > > https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories > > > > > > ). > > > > > > > > > > > > Let me try to start with a simple one with essential information > and > > > > > > later polishing details. > > > > > > > > > > > > On Wed, May 13, 2020 at 9:55 AM Furkan KAMACI < > > > furkankam...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > As far as I know, there is not a website created for Teaclave > yet. > > > Is > > > > > > there > > > > > > > any progress for it? > > > > > > > > > > > > > > Kind Regards, > > > > > > > Furkan KAMACI > > > > > > > > > > > > > - > > > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > For additional commands, e-mail: dev-h...@teaclave.apache.org > >
[GitHub] [incubator-teaclave-website] kamaci opened a new pull request #1: Fixed ASF sponsorship URL.
kamaci opened a new pull request #1: URL: https://github.com/apache/incubator-teaclave-website/pull/1 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
Re: Teaclave Website
This is great - you might want to add links to mail archive (dev@) and a page on the community (people) https://incubator.apache.org/guides/sites.html#creating_a_good_podling_site From: Mingshen Sun Sent: Thursday, May 14, 2020 5:55:35 PM To: dev@teaclave.apache.org Subject: Re: Teaclave Website Hi folks, I have setup a website for Teaclave: https://teaclave.apache.org/ Currently, the site generator can automatically fetch docs from our main repository. The source code can be found here: https://github.com/apache/incubator-teaclave-website/. I'll include more information in this website. Feel free to comment and help me to improve the website. Thanks. On Wed, May 13, 2020 at 6:39 PM Furkan KAMACI wrote: > > Hi Mingshen, > > Great! > > Kind Regards, > Furkan KAMACI > > On Thu, May 14, 2020 at 4:38 AM Mingshen Sun wrote: > > > Great, I can access this repo now. It takes about 1h to propagate the rule. > > > > On Wed, May 13, 2020 at 6:19 PM Mingshen Sun wrote: > > > > > > I have created a new repo (apache/incubator-teaclave-website) for > > > hosting sources and pages here [1]. > > > > > > It appears in GitHub immediately > > > (https://github.com/apache/incubator-teaclave-website). However, I > > > don't have access to this repo now. I'm not sure whether it takes some > > > time to propagate the access control rule to GitHub or I need to > > > submit a ticket to INFRA for help. > > > > > > [1] https://gitbox.apache.org/setup/newrepo.html. > > > > > > On Wed, May 13, 2020 at 3:45 PM Furkan KAMACI > > wrote: > > > > > > > > Hi Mingshen, > > > > > > > > Sure! Feel free to ask if you have any questions. > > > > > > > > Kind Regards, > > > > Furkan KAMACI > > > > > > > > On Thu, May 14, 2020 at 1:04 AM Mingshen Sun wrote: > > > > > > > > > Thanks for asking, Furkan. > > > > > > > > > > I did some research on how to deploy a website under the Apache > > > > > infrastructure. There are several options > > > > > (https://infra.apache.org/project-site.html). Since we are mainly > > > > > working on GitHub, I think the GitHub pages fit our needs. We can use > > > > > .asf.yml to configure the deployment > > > > > ( > > > > > > > https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories > > > > > ). > > > > > > > > > > Let me try to start with a simple one with essential information and > > > > > later polishing details. > > > > > > > > > > On Wed, May 13, 2020 at 9:55 AM Furkan KAMACI < > > furkankam...@gmail.com> > > > > > wrote: > > > > > > > > > > > > Hi All, > > > > > > > > > > > > As far as I know, there is not a website created for Teaclave yet. > > Is > > > > > there > > > > > > any progress for it? > > > > > > > > > > > > Kind Regards, > > > > > > Furkan KAMACI > > > > > > > > > > - > > > > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > > > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org > > For additional commands, e-mail: dev-h...@teaclave.apache.org > > > > - To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
