Title: Feature Request: Safe/reliable crypto.KeyObject and webcrypto.CryptoKey detection in userland · Issue #38611 · nodejs/node · GitHub
Open Graph Title: Feature Request: Safe/reliable crypto.KeyObject and webcrypto.CryptoKey detection in userland · Issue #38611 · nodejs/node
X Title: Feature Request: Safe/reliable crypto.KeyObject and webcrypto.CryptoKey detection in userland · Issue #38611 · nodejs/node
Description: Currently there are no public methods for checking for KeyObject and CryptoKey objects. Having reliable checks for these would be very nice to have for userland code that wants to support these types of objects in their code. It seems th...
Open Graph Description: Currently there are no public methods for checking for KeyObject and CryptoKey objects. Having reliable checks for these would be very nice to have for userland code that wants to support these typ...
X Description: Currently there are no public methods for checking for KeyObject and CryptoKey objects. Having reliable checks for these would be very nice to have for userland code that wants to support these typ...
Opengraph URL: https://github.com/nodejs/node/issues/38611
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Feature Request: Safe/reliable crypto.KeyObject and webcrypto.CryptoKey detection in userland","articleBody":"Currently there are no public methods for checking for `KeyObject` and `CryptoKey` objects. Having reliable checks for these would be very nice to have for userland code that wants to support these types of objects in their code.\r\n\r\nIt seems there are already internal methods for achieving this, but I'm not sure why they are not currently exposed to userland. I was thinking maybe something like how `Buffer` handles this: `KeyObject.isKeyObject()` and `CryptoKey.isCryptoKey()`. The former is currently pretty easy to do in userland since it's just doing an `instanceof` check, but the latter checks \"private\" symbols, which is not as easy/ideal for userland (although I guess at least currently `instanceof CryptoKey` would work?). Either way, having these encapsulated in helper methods would help insulate changes to the checking logic, should it ever change.\r\n\r\n","author":{"url":"https://github.com/mscdex","@type":"Person","name":"mscdex"},"datePublished":"2021-05-09T16:20:04Z","url":"https://github.com/nodejs/node/issues/38611"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react-reconciler,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@d5750093facf |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:e96350fe-e765-9751-96e1-1fbda830ae05 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 8E28:325E01:9CF66:D3F8F:6AED3372 |
| html-safe-nonce | e6bbafc18ccbb39e5e9b4db429f90fe35a0644b9c557fc1ece3212a82d71504d |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4RTI4OjMyNUUwMTo5Q0Y2NjpEM0Y4Rjo2QUVEMzM3MiIsInZpc2l0b3JfaWQiOiIxODcwNDExNDA1NDAzNjk4MDM1IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | f7dfd38a385984824b70b50597620758dae036e682753b596c62596d49ea2f30 |
| hovercard-subject-tag | issue:882503810 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/nodejs/node/38611/issue_layout |
| twitter:image | https://opengraph.githubassets.com/829993219a1fff02bd630d4a5b8850b33668357847c8d055677e616e981cc411/nodejs/node/issues/38611 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/829993219a1fff02bd630d4a5b8850b33668357847c8d055677e616e981cc411/nodejs/node/issues/38611 |
| og:image:alt | Currently there are no public methods for checking for KeyObject and CryptoKey objects. Having reliable checks for these would be very nice to have for userland code that wants to support these typ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | mscdex |
| hostname | github.com |
| expected-hostname | github.com |
| None | e51d0b7b5ab34b1688c05b54c3ed17b8658b2fa9bca973a9c740683ccb12cf4a |
| turbo-cache-control | no-preview |
| go-import | github.com/nodejs/node git https://github.com/nodejs/node.git |
| octolytics-dimension-user_id | 9950313 |
| octolytics-dimension-user_login | nodejs |
| octolytics-dimension-repository_id | 27193779 |
| octolytics-dimension-repository_nwo | nodejs/node |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 27193779 |
| octolytics-dimension-repository_network_root_nwo | nodejs/node |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 59ebb7b901cc154ecc179a44f266fcf69f343b30 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width