Split (1)

train · 21M rows

hexsha stringlengths 40 40	size int64 5 1.04M	ext stringclasses 6 values	lang stringclasses 1 value	max_stars_repo_path stringlengths 3 344	max_stars_repo_name stringlengths 5 125	max_stars_repo_head_hexsha stringlengths 40 78	max_stars_repo_licenses sequencelengths 1 11	max_stars_count int64 1 368k ⌀	max_stars_repo_stars_event_min_datetime stringlengths 24 24 ⌀	max_stars_repo_stars_event_max_datetime stringlengths 24 24 ⌀	max_issues_repo_path stringlengths 3 344	max_issues_repo_name stringlengths 5 125	max_issues_repo_head_hexsha stringlengths 40 78	max_issues_repo_licenses sequencelengths 1 11	max_issues_count int64 1 116k ⌀	max_issues_repo_issues_event_min_datetime stringlengths 24 24 ⌀	max_issues_repo_issues_event_max_datetime stringlengths 24 24 ⌀	max_forks_repo_path stringlengths 3 344	max_forks_repo_name stringlengths 5 125	max_forks_repo_head_hexsha stringlengths 40 78	max_forks_repo_licenses sequencelengths 1 11	max_forks_count int64 1 105k ⌀	max_forks_repo_forks_event_min_datetime stringlengths 24 24 ⌀	max_forks_repo_forks_event_max_datetime stringlengths 24 24 ⌀	content stringlengths 5 1.04M	avg_line_length float64 1.14 851k	max_line_length int64 1 1.03M	alphanum_fraction float64 0 1	lid stringclasses 191 values	lid_prob float64 0.01 1
b7ce6476e538ac9fafe66b1bae2dd4554d2198e6	4,381	md	Markdown	wdk-ddi-src/content/vmbuskernelmodeclientlibapi/nc-vmbuskernelmodeclientlibapi-evt_vmb_channel_restore_packet.md	jesweare/windows-driver-docs-ddi	a6e73cac25d8328115822ec266dabdf87d395bc7	[ "CC-BY-4.0", "MIT" ]	null	null	null	wdk-ddi-src/content/vmbuskernelmodeclientlibapi/nc-vmbuskernelmodeclientlibapi-evt_vmb_channel_restore_packet.md	jesweare/windows-driver-docs-ddi	a6e73cac25d8328115822ec266dabdf87d395bc7	[ "CC-BY-4.0", "MIT" ]	null	null	null	wdk-ddi-src/content/vmbuskernelmodeclientlibapi/nc-vmbuskernelmodeclientlibapi-evt_vmb_channel_restore_packet.md	jesweare/windows-driver-docs-ddi	a6e73cac25d8328115822ec266dabdf87d395bc7	[ "CC-BY-4.0", "MIT" ]	1	2021-12-08T21:34:31.000Z	2021-12-08T21:34:31.000Z	--- UID: NC:vmbuskernelmodeclientlibapi.EVT_VMB_CHANNEL_RESTORE_PACKET title: EVT_VMB_CHANNEL_RESTORE_PACKET (vmbuskernelmodeclientlibapi.h) description: The EvtVmbChannelRestorePacket callback function is invoked when the virtualization service provider (VSP) server endpoint must restore the state associated with a packet object. old-location: netvista\evt_vmb_channel_restore_packet.htm tech.root: netvista ms.assetid: 9C89CFCB-4B8A-40D3-B982-2F7836A636A3 ms.date: 05/02/2018 keywords: ["EVT_VMB_CHANNEL_RESTORE_PACKET callback function"] ms.keywords: EVT_VMB_CHANNEL_RESTORE_PACKET, EVT_VMB_CHANNEL_RESTORE_PACKET callback, EvtVmbChannelRestorePacket, EvtVmbChannelRestorePacket callback function [Network Drivers Starting with Windows Vista], PFN_VMB_CHANNEL_RESTORE_PACKET, PFN_VMB_CHANNEL_RESTORE_PACKET callback function pointer [Network Drivers Starting with Windows Vista], netvista.evt_vmb_channel_restore_packet, vmbuskernelmodeclientlibapi/EvtVmbChannelRestorePacket req.header: vmbuskernelmodeclientlibapi.h req.include-header: VmbusKernelModeClientLibApi.h req.target-type: Windows req.target-min-winverclnt: req.target-min-winversvr: req.kmdf-ver: req.umdf-ver: req.ddi-compliance: req.unicode-ansi: req.idl: req.max-support: req.namespace: req.assembly: req.type-library: req.lib: req.dll: req.irql: PASSIVE_LEVEL targetos: Windows req.typenames: f1_keywords: - EVT_VMB_CHANNEL_RESTORE_PACKET - vmbuskernelmodeclientlibapi/EVT_VMB_CHANNEL_RESTORE_PACKET topic_type: - APIRef - kbSyntax api_type: - UserDefined api_location: - VmbusKernelModeClientLibApi.h api_name: - PFN_VMB_CHANNEL_RESTORE_PACKET --- # EVT_VMB_CHANNEL_RESTORE_PACKET callback function ## -description <p class="CCE_Message">[Some information relates to pre-released product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.] The <i>EvtVmbChannelRestorePacket</i> callback function is invoked when the virtualization service provider (VSP) server endpoint must restore the state associated with a packet object. ## -parameters ### -param Channel [in] The channel on which the packet arrives. ### -param LibBuf [in] Pointer to packet object state internal to the Kernel Mode Client Library (KMCL). ### -param LibBufSize [in] Size of the <i>LibBuf</i> parameter, in bytes. ### -param SaveBuf [in] Pointer to transaction state specific to the VSP. ### -param SaveBufSize [in] Size of the <i>SaveBuf</i> parameter, in bytes. ## -returns <i>EvtVmbChannelRestorePacket</i> returns a status code. ## -remarks The <a href="/windows-hardware/drivers/ddi/vmbuskernelmodeclientlibapi/nf-vmbuskernelmodeclientlibapi-vmbserverchannelinitsetsaverestorepacketcallbacks">VmbServerChannelInitSetSaveRestorePacketCallbacks</a> function sets a callback function for restoring packets for each channel. In order to restore an in-flight packet object, the VSP must allocate a new packet by using the <a href="/windows-hardware/drivers/ddi/vmbuskernelmodeclientlibapi/nf-vmbuskernelmodeclientlibapi-vmbpacketallocate">VmbPacketAllocate</a> function. The VSP restores the packet to the previous state by passing <i>LibBuf</i> and <i>LibBufSize</i> to the <a href="/windows-hardware/drivers/ddi/vmbuskernelmodeclientlibapi/nf-vmbuskernelmodeclientlibapi-vmbpacketrestore">VmbPacketRestore</a> function. If the VSP provided any internal state for the transaction in the <i>EvtVmbChannelSavePacket</i> callback function, then this is provided in <i>SaveBuf</i>, and restored by the VSP. ## -see-also <a href="/windows-hardware/drivers/ddi/vmbuskernelmodeclientlibapi/nc-vmbuskernelmodeclientlibapi-evt_vmb_channel_restore_packet">EvtVmbChannelSavePacket</a> <a href="/windows-hardware/drivers/ddi/vmbuskernelmodeclientlibapi/nf-vmbuskernelmodeclientlibapi-vmbpacketallocate">VmbPacketAllocate</a> <a href="/windows-hardware/drivers/ddi/vmbuskernelmodeclientlibapi/nf-vmbuskernelmodeclientlibapi-vmbpacketrestore">VmbPacketRestore</a> <a href="/windows-hardware/drivers/ddi/vmbuskernelmodeclientlibapi/nf-vmbuskernelmodeclientlibapi-vmbserverchannelinitsetsaverestorepacketcallbacks">VmbServerChannelInitSetSaveRestorePacketCallbacks</a>	40.192661	438	0.805752	eng_Latn	0.511409
b7cf3077febe790e29b5a4944820e7a9ced651a3	3,420	md	Markdown	couchbase/README.md	vbarbaresi/integrations-core	ab26ab1cd6c28a97c1ad1177093a93659658c7aa	[ "BSD-3-Clause" ]	1	2021-01-28T01:45:37.000Z	2021-01-28T01:45:37.000Z	couchbase/README.md	vbarbaresi/integrations-core	ab26ab1cd6c28a97c1ad1177093a93659658c7aa	[ "BSD-3-Clause" ]	3	2021-01-27T04:56:40.000Z	2021-02-26T06:29:22.000Z	couchbase/README.md	vbarbaresi/integrations-core	ab26ab1cd6c28a97c1ad1177093a93659658c7aa	[ "BSD-3-Clause" ]	1	2021-04-07T16:58:27.000Z	2021-04-07T16:58:27.000Z	# Couchbase Integration ![Couchbase Bytes Read][1] ## Overview Identify busy buckets, track cache miss ratios, and more. This Agent check collects metrics like: - Hard disk and memory used by data - Current connections - Total objects - Operations per second - Disk write queue size And many more. ## Setup ### Installation The Couchbase check is included in the [Datadog Agent][2] package, so you don't need to install anything else on your Couchbase nodes. ### Configuration <!-- xxx tabs xxx --> <!-- xxx tab "Host" xxx --> #### Host To configure this check for an Agent running on a host: ##### Metric Collection 1. Edit the `couchbase.d/conf.yaml` file in the `conf.d/` folder at the root of your [Agent's configuration directory][3] to start collecting your Couchbase data. See the [sample couchbase.d/conf.yaml][4] for all available configuration options. ```yaml init_config: instances: ## @param server - string - required ## The server's url. # - server: http://localhost:8091 ``` 2. [Restart the Agent][5]. <!-- xxz tab xxx --> <!-- xxx tab "Containerized" xxx --> #### Containerized For containerized environments, see the [Autodiscovery Integration Templates][6] for guidance on applying the parameters below. ##### Metric collection \| Parameter \| Value \| \| -------------------- \| ------------------------------------ \| \| `<INTEGRATION_NAME>` \| `couchbase` \| \| `<INIT_CONFIG>` \| blank or `{}` \| \| `<INSTANCE_CONFIG>` \| `{"server": "http://%%host%%:8091"}` \| <!-- xxz tab xxx --> <!-- xxz tabs xxx --> ### Validation [Run the Agent's `status` subcommand][8] and look for `couchbase` under the Checks section. ## Data Collected ### Metrics See [metadata.csv][9] for a list of metrics provided by this integration. ### Events The Couchbase check emits an event to Datadog each time the cluster rebalances. ### Service Checks couchbase.can_connect:<br> Returns `Critical` if the Agent cannot connect to Couchbase to collect metrics. couchbase.by_node.cluster_membership:<br> Returns `Critical` if the node failed over. Returns `Warning` if the node is added to the cluster but is waiting for a rebalance. Returns `Ok` otherwise. couchbase.by_node.health:<br> Returns `Critical` if the node is unhealthy. Returns `Ok` otherwise. ## Troubleshooting Need help? Contact [Datadog support][10]. ## Further Reading - [Monitor key Couchbase metrics][11]. [1]: https://raw.githubusercontent.com/DataDog/integrations-core/master/couchbase/images/couchbase_graph.png [2]: https://app.datadoghq.com/account/settings#agent [3]: https://docs.datadoghq.com/agent/guide/agent-configuration-files/#agent-configuration-directory [4]: https://github.com/DataDog/integrations-core/blob/master/couchbase/datadog_checks/couchbase/data/conf.yaml.example [5]: https://docs.datadoghq.com/agent/guide/agent-commands/#start-stop-and-restart-the-agent [6]: https://docs.datadoghq.com/agent/kubernetes/integrations/ [7]: https://docs.datadoghq.com/agent/kubernetes/log/ [8]: https://docs.datadoghq.com/agent/guide/agent-commands/#agent-status-and-information [9]: https://github.com/DataDog/integrations-core/blob/master/couchbase/metadata.csv [10]: https://docs.datadoghq.com/help/ [11]: https://www.datadoghq.com/blog/monitoring-couchbase-performance-datadog	30.535714	245	0.693567	eng_Latn	0.58274
b7cf31305b8321952f2d4564d3116b4f03a63df8	158,799	md	Markdown	security-updates/SecurityBulletins/2011/ms11-081.md	MicrosoftDocs/security-updates.zh-tw	a7899f202a462bc504303f28e9c2a8d41cfa99a0	[ "CC-BY-4.0", "MIT" ]	3	2019-01-24T02:18:29.000Z	2020-05-19T20:17:25.000Z	security-updates/SecurityBulletins/2011/ms11-081.md	MicrosoftDocs/security-updates.zh-tw	a7899f202a462bc504303f28e9c2a8d41cfa99a0	[ "CC-BY-4.0", "MIT" ]	257	2017-12-11T09:12:37.000Z	2019-12-06T23:07:01.000Z	security-updates/SecurityBulletins/2011/ms11-081.md	MicrosoftDocs/security-updates.zh-tw	a7899f202a462bc504303f28e9c2a8d41cfa99a0	[ "CC-BY-4.0", "MIT" ]	5	2018-10-12T21:08:18.000Z	2021-11-15T11:25:34.000Z	--- TOCTitle: 'MS11-081' Title: 'Microsoft Security Bulletin MS11-081 - 重大' ms:assetid: 'ms11-081' ms:contentKeyID: 61238713 ms:date: '04/18/2014' ms:mtpsurl: 'https://technet.microsoft.com/zh-TW/library/ms11-081(v=Security.10)' --- Microsoft Security Bulletin MS11-081 - 重大 =========================================== Internet Explorer 積存安全性更新 (2586448) ------------------------------------------ 發行: 2011年10月11日 \| 更新: 2011年11月2日版本: 1.2 ### 一般資訊 #### 提要此安全性更新可解決 Internet Explorer 中八項未公開報告的弱點。最嚴重的弱點可能會在使用者以 Internet Explorer 檢視蓄意製作的網頁時，允許遠端執行程式碼。成功利用這類任一弱點的攻擊者可以取得與本機使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。對於 Windows 用戶端上的 Internet Explorer，此安全性更新的等級為「重大」；對於 Windows 伺服器上的 Internet Explorer，等級為「中度」。如需更多資訊，請參閱本節中的＜受影響及不受影響的軟體＞小節。此更新可修改 Internet Explorer 處理記憶體中物件的方式，以及 Internet Explorer 配置和存取記憶體的方式，以解決這些弱點。如需更多有關此弱點的資訊，請參閱下節＜弱點資訊＞下的特定弱點項目的＜常見問題集 (FAQ)＞小節。建議。大部分客戶都已啟用自動更新，並且不必須採取任何行動，因為安全性更新將自動下載和安裝。沒有啟用自動更新的客戶則必須檢查更新，並手動安裝更新。如需有關自動更新中特定設定選項的資訊，請參閱 [Microsoft 知識庫文件編號 294871](https://support.microsoft.com/kb/294871)。若是系統管理員和企業安裝，或是想要手動安裝此安全性更新的使用者，Microsoft 建議客戶使用更新管理軟體，立即套用更新，或使用 [Microsoft Update](https://go.microsoft.com/fwlink/?linkid=40747) 服務檢查更新。另請參閱本公告下文的＜偵測與部署工具及指南＞一節。已知問題。[Microsoft 知識庫文件編號 2586448](https://support.microsoft.com/kb/2586448) 中記載了客戶安裝此安全性更新時，可能會發生的目前已知問題。該文件並說明了解決這些問題的建議解決方案。目前已知問題和建議解決方案僅適用於此軟體的特定版本，本文會提供詳細文章的連結。 #### 受影響及不受影響的軟體下列軟體已經過測試判斷哪些版號或版本會受到影響。其他版本超過它們的支援週期或不受影響。若要瞭解您的軟體版本的支援週期，請造訪 [Microsoft 產品技術支援週期網站](https://go.microsoft.com/fwlink/?linkid=21742)。受影響的軟體 <p> </p> <table style="border:1px solid black;"> <tr class="thead"> <th style="border:1px solid black;" > 作業系統 </th> <th style="border:1px solid black;" > 元件 </th> <th style="border:1px solid black;" > 最大安全性影響 </th> <th style="border:1px solid black;" > 彙總嚴重性等級 </th> <th style="border:1px solid black;" > 此更新取代的公告 </th> </tr> <tr> <th style="border:1px solid black;" colspan="5"> Internet Explorer 6 </th> </tr> <tr> <td style="border:1px solid black;"> Windows XP Service Pack 3 </td> <td style="border:1px solid black;"> [Internet Explorer 6](https://www.microsoft.com/download/details.aspx?familyid=822f91f5-bf92-42c4-ad33-b971be37d772) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows XP Professional x64 Edition Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 6](https://www.microsoft.com/download/details.aspx?familyid=6260318c-e579-4cdf-93e3-4608892bc79e) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> Windows Server 2003 Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 6](https://www.microsoft.com/download/details.aspx?familyid=172c55f3-6249-4ba3-a4a4-677a03262ff3) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows Server 2003 x64 Edition Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 6](https://www.microsoft.com/download/details.aspx?familyid=f5a0a8db-34d4-4f0a-ab6b-7b2fb420ab91) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 Itanium 型系統的 Windows Server 2003 SP2 </td> <td style="border:1px solid black;"> [Internet Explorer 6](https://www.microsoft.com/download/details.aspx?familyid=5825cb4a-47d5-423f-b4c5-2d0fc50856c0) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <th style="border:1px solid black;" colspan="5"> Internet Explorer 7 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows XP Service Pack 3 </td> <td style="border:1px solid black;"> [Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=e942554d-6cb6-4e48-a876-3470671a95a2) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> Windows XP Professional x64 Edition Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=f04ad852-1418-4fc4-bd57-f47895bbf3a8) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows Server 2003 Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=6ffbdb93-7b92-4197-bb6c-5c305e8072a8) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> Windows Server 2003 x64 Edition Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=7379b3bf-6af0-43cb-bf8b-505e8563fc84) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 Itanium 型系統的 Windows Server 2003 SP2 </td> <td style="border:1px solid black;"> [Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=11c4878e-df58-4369-b9c0-cb0a230c92dd) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> Windows Vista Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=630335ac-5a30-46b4-acc1-c4d8bd289668) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows Vista x64 Edition Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=9aabd7a2-0b2f-4c42-a9cf-2ec69ae6b82d) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 32 位元系統的 Windows Server 2008 Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=5660e23c-13a3-4275-ac69-38f03f17491a)\\ </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows Server 2008 Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=415b1c59-f3dc-4f4f-b2eb-68692d6efc05)\\ </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 Itanium 型系統的 Windows Server 2008 Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=31e68c7f-4db5-463f-a315-92f574af080b) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <th style="border:1px solid black;" colspan="5"> Internet Explorer 8 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows XP Service Pack 3 </td> <td style="border:1px solid black;"> [Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=a911b5b0-5e46-4a37-83e7-595e20585c56) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> Windows XP Professional x64 Edition Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=67ebf641-1341-4642-96ba-bab5446d7b5d) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows Server 2003 Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=14ef20d4-3530-49b2-91b7-d278d9098023) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> Windows Server 2003 x64 Edition Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=b35c95f5-30b0-43a9-aa6a-6db63cab0dcb) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows Vista Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=76c8124e-81b9-4a6a-bd53-fbdaf45189aa) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> Windows Vista x64 Edition Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=3454940c-acc2-4e09-8154-075b4be1b697) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 32 位元系統的 Windows Server 2008 Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=bd144435-1afd-4d6e-a100-fbd613eee409)\\ </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows Server 2008 Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=b0c4949f-bce0-4255-a5f2-cf5ecf7416da)\\ </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 32 位元系統的 Windows 7 和適用於 32 位元系統的 Windows 7 Service Pack 1 </td> <td style="border:1px solid black;"> [Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=4de175be-bbb7-4912-ba4e-d6fe96606c9e) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows 7 和適用於 x64 型系統的 Windows 7 Service Pack 1 </td> <td style="border:1px solid black;"> [Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=16fd238e-6f65-4d38-88ae-2689817588e1) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows Server 2008 R2 和適用於 x64 型系統的 Windows Server 2008 R2 Service Pack 1 </td> <td style="border:1px solid black;"> [Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=8435781e-0f77-41d0-abb9-9b70f5b02d33)\\ </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 Itanium 型系統的 Windows Server 2008 R2 和適用於 Itanium 型系統的 Windows Server 2008 R2 Service Pack 1 </td> <td style="border:1px solid black;"> [Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=2676597e-c1d4-4397-8dc4-515ce3d0c5fd) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <th style="border:1px solid black;" colspan="5"> Internet Explorer 9 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows Vista Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 9](https://www.microsoft.com/download/details.aspx?familyid=7de276a3-a20d-49de-82b0-51cb22ad73af) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> Windows Vista x64 Edition Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 9](https://www.microsoft.com/download/details.aspx?familyid=3df0c31b-344a-4163-93d2-79df1653b339) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 32 位元系統的 Windows Server 2008 Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 9](https://www.microsoft.com/download/details.aspx?familyid=1a7f9855-20ce-4fe0-a903-bd1f145075df)\\ </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows Server 2008 Service Pack 2 </td> <td style="border:1px solid black;"> [Internet Explorer 9](https://www.microsoft.com/download/details.aspx?familyid=28a09e42-5865-48b2-af26-ebc8162c3286)\\ </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 32 位元系統的 Windows 7 和適用於 32 位元系統的 Windows 7 Service Pack 1 </td> <td style="border:1px solid black;"> [Internet Explorer 9](https://www.microsoft.com/download/details.aspx?familyid=b49876c7-7c65-4b6d-be9a-9f18be23037b) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows 7 和適用於 x64 型系統的 Windows 7 Service Pack 1 </td> <td style="border:1px solid black;"> [Internet Explorer 9](https://www.microsoft.com/download/details.aspx?familyid=cc0773f2-6099-4d55-9971-ee6546369c7f) </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows Server 2008 R2 和適用於 x64 型系統的 Windows Server 2008 R2 Service Pack 1 </td> <td style="border:1px solid black;"> [Internet Explorer 9](https://www.microsoft.com/download/details.aspx?familyid=646a9a56-c343-45cb-a255-303602aa5a64)\\ </td> <td style="border:1px solid black;"> 遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> <td style="border:1px solid black;"> [MS11-057](https://go.microsoft.com/fwlink/?linkid=221946) </td> </tr> </table> *\\Server Core 安裝不受影響。如果 Windows Server 2008 或 Windows Server 2008 R2 是使用 Server Core 安裝選項所安裝，則這項更新解決的弱點並不會影響受支援的 Windows Server 2008 或 Windows Server 2008 R2。如需此安裝選項的詳細資訊，請參閱 TechNet 文章：[管理 Server Core 安裝](https://technet.microsoft.com/en-us/library/ee441255(ws.10).aspx) (英文) 和[維護 Server Core 安裝](https://technet.microsoft.com/en-us/library/ff698994(ws.10).aspx) (英文)。請注意，Server Core 安裝選項不適用於某些 Windows Server 2008 和 Windows Server 2008 R2 版本；請參閱[比較 Server Core 安裝選項](https://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx) (英文)。與本安全性更新相關的常見問題集 (FAQ) ------------------------------------ 為何於 2010 年 11 月 2 日修訂此公告？* Microsoft 修訂此公告，是為了宣佈發行一個 Hotfix，來解決一項對 Internet Explorer 7 客戶構成影響的問題：安裝 KB2586448 安全性更新後，Internet Explorer 7 中部分下拉式清單和下拉式方塊不會顯示。如需更多關於此問題的資訊，以及套用 Hotfix 來解決問題的說明，請參閱 [Microsoft 知識庫文件編號 2586448](https://support.microsoft.com/kb/2586448)。何處可找到檔案資訊詳細資料？關於檔案資訊詳細資料的位置，請見＜安全性更新部署＞一節中的參考表。為何本次更新中仍然包含數個已回報的安全性弱點？因為解決這些弱點所需的修正作業位於相關檔案中，所以在本次更新中仍然提供對這些弱點的支援。客戶不需要安裝數個幾乎相同的更新，只需要安裝本更新即可。此更新程式是否包含功能上的任何安全性相關變更？是。除了本公告＜弱點資訊＞一節中列出的變更外，此更新還包含若干深度防禦更新，可協助改善 Internet Explorer 中的記憶體保護、框架及 Cookie 管理、Bing API 及 XSS 篩選器。什麼是深度防禦？就資訊安全而言，深度防禦指的是一種建構多層防線，以協助防堵攻擊者危害網路或系統安全性的一種方法。我所使用的軟體是這個安全性公告中討論的軟體之舊版。該怎麼辦？本公告所列出的受影響軟體版本已經過測試判斷哪些版本會受到影響。其他版本超出它們的支援週期。如需瞭解產品生命週期的相關資訊，請造訪 [Microsoft 支援週期](https://go.microsoft.com/fwlink/?linkid=21742)網站。使用此軟體舊版的客戶應優先考慮移轉至支援的版本，以避免因潛在的弱點而遭受攻擊。若要瞭解您的軟體版本的支援週期，請參閱[選擇一個產品檢視其支援週期資訊](https://go.microsoft.com/fwlink/?linkid=169555)。如需更多軟體版本 Service Pack 的相關資訊，請參閱[產品技術支援週期所支援的 Service Pack](https://go.microsoft.com/fwlink/?linkid=89213)。需要舊版軟體額外支援服務的客戶，請連絡 Microsoft 客戶小組人員、技術支援經理或適當的 Microsoft 協力廠商，以取得所需的額外支援。尚未簽訂聯盟、優先或授權合約的客戶，可以連絡當地的 Microsoft 銷售辦公室。如需連絡資訊，請造訪 [Microsoft 全球資訊](https://go.microsoft.com/fwlink/?linkid=33329)網站，在 \[Contact Information\] (連絡資訊) 清單中選擇國家，然後按一下 \[Go\] 看各地的連絡電話號碼。連絡時，請指明要連絡當地優先支援服務行銷經理。如需更多資訊，請參閱 [Microsoft 技術支援週期準則常見問答集](https://go.microsoft.com/fwlink/?linkid=169557)。 ### 弱點資訊嚴重性等級和弱點識別碼 ---------------------- 下列嚴重性等級是假設弱點可能造成的最嚴重影響而評定。在本安全性公告發行的 30 天內，如需弱點之易遭利用性與嚴重性等級和安全性影響之間對應關係的資訊，請參閱 [10 月份公告摘要](https://technet.microsoft.com/security/bulletin/ms11-oct)中的＜弱點入侵指數＞。如需更多資訊，請參閱 [Microsoft 弱點入侵指數](https://technet.microsoft.com/zh-tw/security/cc998259.aspx)。表 1 <p> </p> <table style="border:1px solid black;"> <caption> 依受影響軟體列出的弱點嚴重性等級和最大安全性影響 </caption> <tr class="thead"> <th style="border:1px solid black;" > 受影響的軟體 </th> <th style="border:1px solid black;" > Scroll 事件遠端執行程式碼弱點 - CVE-2011-1993 </th> <th style="border:1px solid black;" > OLEAuto32.dll 遠端執行程式碼弱點 - CVE-2011-1995 </th> <th style="border:1px solid black;" > Option 項目遠端執行程式碼弱點 - CVE-2011-1996 </th> <th style="border:1px solid black;" colspan="2"> OnLoad 事件遠端執行程式碼弱點 - CVE-2011-1997 </th> </tr> <tr> <th style="border:1px solid black;" colspan="6"> Internet Explorer 6 </th> </tr> <tr> <td style="border:1px solid black;"> Windows XP Service Pack 3 的 Internet Explorer 6 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 重大遠端執行程式碼 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 Windows XP Professional x64 Edition Service Pack 2 的 Internet Explorer 6 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 重大遠端執行程式碼 </td> </tr> <tr> <td style="border:1px solid black;"> Windows 2003 Service Pack 2 中的 Internet Explorer 6 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 中度遠端執行程式碼 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows Server 2003 x64 Edition Service Pack 2 的 Internet Explorer 6 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 中度遠端執行程式碼 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 Itanium 型系統的 Windows Server 2003 SP2 中的 Windows Internet Explorer 6 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 中度遠端執行程式碼 </td> </tr> <tr> <th style="border:1px solid black;" colspan="6"> Internet Explorer 7 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows XP Service Pack 3 的 Internet Explorer 7 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 Windows XP Professional x64 Edition Service Pack 2 的 Internet Explorer 7 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows 2003 Service Pack 2 中的 Internet Explorer 7 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <td style="border:1px solid black;"> Windows Server 2003 x64 Edition Service Pack 2 的 Internet Explorer 7 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 Itanium 型系統的 Windows Server 2003 SP2 中的 Windows Internet Explorer 7 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <td style="border:1px solid black;"> Windows Vista Service Pack 2 中的 Internet Explorer 7 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows Vista x64 Edition Service Pack 2 中的 Internet Explorer 7 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 32 位元系統的 Windows Server 2008 Service Pack 2 中的 Internet Explorer 7\\ </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows Server 2008 Service Pack 2 中的 Internet Explorer 7\\ </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 Itanium 型系統的 Windows Server 2008 Service Pack 2 中的 Internet Explorer 7 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <th style="border:1px solid black;" colspan="6"> Internet Explorer 8 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows XP Service Pack 3 的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <td style="border:1px solid black;"> Windows XP Professional x64 Edition Service Pack 2 的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows 2003 Service Pack 2 中的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <td style="border:1px solid black;"> Windows Server 2003 x64 Edition Service Pack 2 的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows Vista Service Pack 2 中的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <td style="border:1px solid black;"> Windows Vista x64 Edition Service Pack 2 中的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 32 位元系統的 Windows Server 2008 Service Pack 2 中的 Internet Explorer 8\* </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows Server 2008 Service Pack 2 中的 Internet Explorer 8\* </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 32 位元系統的 Windows 7 以及適用於 32 位元系統的 Windows 7 Service Pack 1 中的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows 7，以及適用於 x64 型系統的 Windows 7 Service Pack 1 中的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows Server 2008 R2，以及適用於 x64 型系統的 Windows Server 2008 R2 Service Pack 1 中的 Internet Explorer 8\\ </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 Itanium 型系統的 Windows Server 2008 R2 和適用於 Itanium 型系統的 Windows Server 2008 R2 Service Pack 1 中的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <th style="border:1px solid black;" colspan="6"> Internet Explorer 9 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 Windows Vista Service Pack 2 的 Internet Explorer 9 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 Windows Vista x64 Edition Service Pack 2 的 Internet Explorer 9 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 32 位元系統 Windows Server 2008 Service Pack 2 的 Internet Explorer 9\\ </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 x64 型系統 Windows Server 2008 Service Pack 2 的 Internet Explorer 9\\ </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 32 位元系統的 Windows 7 以及適用於 32 位元系統的 Windows 7 Service Pack 1 中的 Internet Explorer 9 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 x64 型系統 Windows 7 以及適用於 x64 型系統 Windows 7 Service Pack 1 的 Internet Explorer 9 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 x64 型系統 Windows Server 2008 R2，以及適用於 x64 型系統 Windows Server 2008 R2 Service Pack 1 的 Internet Explorer 9\\ </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;" colspan="2"> 不適用 </td> </tr> </table> *\\Server Core 安裝不受影響。如果 Windows Server 2008 或 Windows Server 2008 R2 是使用 Server Core 安裝選項所安裝，則這項更新解決的弱點並不會影響受支援的 Windows Server 2008 或 Windows Server 2008 R2。如需此安裝選項的詳細資訊，請參閱 TechNet 文章：[管理 Server Core 安裝](https://technet.microsoft.com/en-us/library/ee441255(ws.10).aspx) (英文) 和[維護 Server Core 安裝](https://technet.microsoft.com/en-us/library/ff698994(ws.10).aspx) (英文)。請注意，Server Core 安裝選項不適用於某些 Windows Server 2008 和 Windows Server 2008 R2 版本；請參閱[比較 Server Core 安裝選項](https://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx) (英文)。表 2* <p> </p> <table style="border:1px solid black;"> <caption> 依受影響軟體列出的弱點嚴重性等級和最大安全性影響 </caption> <tr class="thead"> <th style="border:1px solid black;" > 受影響的軟體 </th> <th style="border:1px solid black;" > Jscript9.dll 遠端執行程式碼弱點 - CVE-2011-1998 </th> <th style="border:1px solid black;" > SELECT 項目遠端執行程式碼弱點 - CVE-2011-1999 </th> <th style="border:1px solid black;" > Body 項目遠端執行程式碼弱點 - CVE-2011-2000 </th> <th style="border:1px solid black;" > 虛擬函式表損毀遠端執行程式碼弱點 - CVE-2011-2001 </th> <th style="border:1px solid black;" > 彙總嚴重性等級 </th> </tr> <tr> <th style="border:1px solid black;" colspan="6"> Internet Explorer 6 </th> </tr> <tr> <td style="border:1px solid black;"> Windows XP Service Pack 3 的 Internet Explorer 6 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 Windows XP Professional x64 Edition Service Pack 2 的 Internet Explorer 6 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr> <td style="border:1px solid black;"> Windows 2003 Service Pack 2 中的 Internet Explorer 6 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows Server 2003 x64 Edition Service Pack 2 的 Internet Explorer 6 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 Itanium 型系統的 Windows Server 2003 SP2 中的 Windows Internet Explorer 6 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr> <th style="border:1px solid black;" colspan="6"> Internet Explorer 7 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows XP Service Pack 3 的 Internet Explorer 7 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 Windows XP Professional x64 Edition Service Pack 2 的 Internet Explorer 7 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows 2003 Service Pack 2 中的 Internet Explorer 7 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr> <td style="border:1px solid black;"> Windows Server 2003 x64 Edition Service Pack 2 的 Internet Explorer 7 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 Itanium 型系統的 Windows Server 2003 SP2 中的 Windows Internet Explorer 7 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr> <td style="border:1px solid black;"> Windows Vista Service Pack 2 中的 Internet Explorer 7 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows Vista x64 Edition Service Pack 2 中的 Internet Explorer 7 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 32 位元系統的 Windows Server 2008 Service Pack 2 中的 Internet Explorer 7\\ </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows Server 2008 Service Pack 2 中的 Internet Explorer 7\\ </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 Itanium 型系統的 Windows Server 2008 Service Pack 2 中的 Internet Explorer 7 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr> <th style="border:1px solid black;" colspan="6"> Internet Explorer 8 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows XP Service Pack 3 的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr> <td style="border:1px solid black;"> Windows XP Professional x64 Edition Service Pack 2 的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows 2003 Service Pack 2 中的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr> <td style="border:1px solid black;"> Windows Server 2003 x64 Edition Service Pack 2 的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> Windows Vista Service Pack 2 中的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr> <td style="border:1px solid black;"> Windows Vista x64 Edition Service Pack 2 中的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 32 位元系統的 Windows Server 2008 Service Pack 2 中的 Internet Explorer 8\* </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows Server 2008 Service Pack 2 中的 Internet Explorer 8\* </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 32 位元系統的 Windows 7 以及適用於 32 位元系統的 Windows 7 Service Pack 1 中的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows 7，以及適用於 x64 型系統的 Windows 7 Service Pack 1 中的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 x64 型系統的 Windows Server 2008 R2，以及適用於 x64 型系統的 Windows Server 2008 R2 Service Pack 1 中的 Internet Explorer 8\\ </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 Itanium 型系統的 Windows Server 2008 R2 和適用於 Itanium 型系統的 Windows Server 2008 R2 Service Pack 1 中的 Internet Explorer 8 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr> <th style="border:1px solid black;" colspan="6"> Internet Explorer 9 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 Windows Vista Service Pack 2 的 Internet Explorer 9 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 Windows Vista x64 Edition Service Pack 2 的 Internet Explorer 9 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 32 位元系統 Windows Server 2008 Service Pack 2 的 Internet Explorer 9\\ </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 x64 型系統 Windows Server 2008 Service Pack 2 的 Internet Explorer 9\\ </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 32 位元系統的 Windows 7 以及適用於 32 位元系統的 Windows 7 Service Pack 1 中的 Internet Explorer 9 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr> <td style="border:1px solid black;"> 適用於 x64 型系統 Windows 7 以及適用於 x64 型系統 Windows 7 Service Pack 1 的 Internet Explorer 9 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大遠端執行程式碼 </td> <td style="border:1px solid black;"> 重大 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> 適用於 x64 型系統 Windows Server 2008 R2，以及適用於 x64 型系統 Windows Server 2008 R2 Service Pack 1 的 Internet Explorer 9\\ </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 不適用 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度遠端執行程式碼 </td> <td style="border:1px solid black;"> 中度 </td> </tr> </table> *\\Server Core 安裝不受影響。如果 Windows Server 2008 或 Windows Server 2008 R2 是使用 Server Core 安裝選項所安裝，則這項更新解決的弱點並不會影響受支援的 Windows Server 2008 或 Windows Server 2008 R2。如需此安裝選項的詳細資訊，請參閱 TechNet 文章：[管理 Server Core 安裝](https://technet.microsoft.com/en-us/library/ee441255(ws.10).aspx) (英文) 和[維護 Server Core 安裝](https://technet.microsoft.com/en-us/library/ff698994(ws.10).aspx) (英文)。請注意，Server Core 安裝選項不適用於某些 Windows Server 2008 和 Windows Server 2008 R2 版本；請參閱[比較 Server Core 安裝選項](https://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx) (英文)。 Scroll 事件遠端執行程式碼弱點 - CVE-2011-1993 --------------------------------------------- Internet Explorer 存取已刪除物件的方式中，存在遠端執行程式碼弱點。此弱點可能會損毀記憶體，使攻擊者有機會透過登入使用者的權限層級執行任意程式碼。若要在「一般性弱點」清單標準條目中檢視此弱點，請參閱 [CVE-2011-1993](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2011-1993) (英文)。 #### Scroll 事件遠端執行程式碼弱點 - CVE-2011-1993 的緩和因素緩和因素是指存在於預設狀態中的設定、共用設定或一般最佳作法，可能會減少弱點影響的嚴重性。下列緩和因素可能對您的狀況有所助益： - 攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。 - 成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。 - 根據預設值，Microsoft Outlook、Microsoft Outlook Express 及 Windows Mail 的所有支援版本會在 \[限制的網站\] 區域中開啟 HTML 電子郵件訊息，進而停用指令碼與 ActiveX 控制項，以協助降低攻擊者能夠利用此弱點執行惡意程式碼的風險。如果使用者按下電子郵件訊息中的連結，仍有可能因為網頁式攻擊而受此弱點遭利用的影響。 - 依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。此模式可緩和這項弱點。如需更多資訊，請參閱此弱點＜常見問題集＞關於 Internet Explorer 增強式安全性設定的部份。 #### Scroll 事件遠端執行程式碼弱點 - CVE-2011-1993 的因應措施因應措施指的是無法徹底修正弱點，但有助於在套用更新之前封鎖已知攻擊模式的設定變更。Microsoft 測試了下列因應措施和狀態，討論因應措施是否會降低功能： - 將 \[網際網路\] 及 \[近端內部網路\] 安全性區域設定為 \[高\]，可封鎖這些區域中的 ActiveX 控制項及動態指令碼處理* 只要將網際網路安全性區域設定變更為封鎖 ActiveX 控制項及動態指令碼處理，即可防範這個弱點遭到利用。做法是將瀏覽器的安全性設定為 \[高\]。若要在 Internet Explorer 中提高瀏覽器的安全層級，請執行下列步驟： 1. 在 Internet Explorer 的 \[工具\] 功能表，按一下 \[網際網路選項\]。 2. 在 \[網際網路選項\] 對話方塊中，按一下 \[安全性\] 索引標籤，再按 \[網際網路\] 圖示。 3. 在 \[此區域的安全性等級\] 下方，將滑桿移至 \[高\]。如此即可將您所造訪的所有網站都設定為 \[高\] 安全層級注意：如果沒有顯示滑桿，按一下 \[預設等級\]，再將滑桿移至 \[高\]。注意：設定為 \[高安全性\] 層級可能會使部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。如此一來，即使採用 \[高\] 設定，該網站仍可正確運作。因應措施的影響。封鎖 ActiveX 控制項和動態指令碼處理會產生副作用。許多網際網路及內部網路的網站使用 ActiveX 或動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用 ActiveX 控制項提供功能表、訂單、甚至是帳戶明細。封鎖 ActiveX 控制項或動態指令碼處理是一種通用設定，該設定會影響所有網際網路及內部網路網站。如果您不希望封鎖這些網站的 ActiveX 控制項或動態指令碼處理，請使用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域封鎖 ActiveX 控制項及動態指令碼處理之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 - 設定 Internet Explorer，以便在執行動態指令碼之前先行提示或停用網際網路及近端內部網路安全性區域內的動態指令碼只要將設定變更為在執行或停用網際網路及近端內部網路安全性區域內的動態指令碼之前先提示，即可防範這個弱點遭到利用。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，按一下 \[工具\] 功能表的 \[網際網路選項\] 2. 按一下 \[安全性\] 索引標籤 3. 按一下 \[網際網路\]，然後按 \[自訂等級\]。 4. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 5. 按一下 \[近端內部網路\]，然後按 \[自訂層級\]。 6. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 7. 按兩次 \[確定\] 回到 Internet Explorer。注意：在網際網路和近端內部網路安全性區域中停用動態指令碼，可能會導致部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。這樣就能讓網站正確運作。因應措施的影響。執行動態指令碼前先提示的設定會產生副作用。許多網際網路及內部網路的網站使用動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用動態指令碼提供功能表、訂單、甚至是帳戶明細。執行動態指令碼前先提示屬於通用設定，會影響所有網際網路及內部網路網站。使用這個因應措施的話，您會時常收到提示。每次出現提示時，如果您覺得可以信任該網站，請按一下 \[是\] 執行動態指令碼處理。如果您不要收到這些網站的提示，請改用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域執行 ActiveX 控制項及動態指令碼處理前會顯示提示之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 #### Scroll 事件遠端執行程式碼弱點 - CVE-2011-1993 的常見問題集這個弱點的範圍為何？這是遠端執行程式碼的弱點。成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。造成這個弱點的原因為何？當 Internet Explorer 嘗試存取已遭刪除的物件時，記憶體可能會遭到損壞，讓攻擊者可以透過登入使用者的權限層級執行任意程式碼。攻擊者可能會利用這項弱點採取什麼行動？成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。如果使用者以系統管理的使用者權限登入，成功利用此弱點的攻擊者可以取得受影響系統的完整控制權。攻擊者接下來將能安裝程式，檢視、變更或刪除資料，或建立具有完整使用者權限的新帳戶。攻擊者如何利用這項弱點？攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。因為這個弱點而承受風險的主要系統有哪些？常使用 Internet Explorer 的系統 (例如工作站或終端伺服器) 的風險最大。我用的是適用於 Windows Server 2003、Windows Server 2008 或 Windows Server 2008 R2 的 Internet Explorer。這樣是否會減輕此弱點的影響？是。依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。增強式安全性設定是一組預先設定好的 Internet Explorer 設定，可以降低使用者或系統管理員在伺服器下載及執行蓄意製作之網頁內容的可能性。對於您尚未新增至 Internet Explorer \[信任的網站\] 區域的網站，這是一種緩和因素。更新的作用何在？此更新會修改 Internet Explorer 處理記憶體中物件的方式，藉此解決此弱點。當安全性公告發行時，這項弱點是否已揭發出來？否。Microsoft 是經由協同合作的來源接獲有關這項弱點的訊息。當本安全性公告發行時，Microsoft 是否已接獲任何消息，指出這項弱點已遭有心人士利用？否。當本安全性公告初次發行時，Microsoft 尚未接到任何有關本弱點已公開用來攻擊客戶的消息。 OLEAuto32.dll 遠端執行程式碼弱點 - CVE-2011-1995 ------------------------------------------------ Internet Explorer 存取未正確初始化之物件的方式中，存在遠端執行程式碼的弱點。此弱點可能會損毀記憶體，使攻擊者有機會透過登入使用者的權限層級執行任意程式碼。若要在「一般性弱點」清單標準條目中檢視此弱點，請參閱 [CVE-2011-1995](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2011-1995) (英文)。 #### OLEAuto32.dll 遠端執行程式碼弱點 - CVE-2011-1995 的緩和因素緩和因素是指存在於預設狀態中的設定、共用設定或一般最佳作法，可能會減少弱點影響的嚴重性。下列緩和因素可能對您的狀況有所助益： - 攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。 - 成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。 - 根據預設值，Microsoft Outlook、Microsoft Outlook Express 及 Windows Mail 的所有支援版本會在 \[限制的網站\] 區域中開啟 HTML 電子郵件訊息，進而停用指令碼與 ActiveX 控制項，以協助降低攻擊者能夠利用此弱點執行惡意程式碼的風險。如果使用者按下電子郵件訊息中的連結，仍有可能因為網頁式攻擊而受此弱點遭利用的影響。 - 依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。此模式可緩和這項弱點。如需更多資訊，請參閱此弱點＜常見問題集＞關於 Internet Explorer 增強式安全性設定的部份。 #### OLEAuto32.dll 遠端執行程式碼弱點 - CVE-2011-1995 的因應措施因應措施指的是無法徹底修正弱點，但有助於在套用更新之前封鎖已知攻擊模式的設定變更。Microsoft 測試了下列因應措施和狀態，討論因應措施是否會降低功能： - 將 \[網際網路\] 及 \[近端內部網路\] 安全性區域設定為 \[高\]，可封鎖這些區域中的 ActiveX 控制項及動態指令碼處理只要將網際網路安全性區域設定變更為封鎖 ActiveX 控制項及動態指令碼處理，即可防範這個弱點遭到利用。做法是將瀏覽器的安全性設定為 \[高\]。若要在 Internet Explorer 中提高瀏覽器的安全層級，請執行下列步驟： 1. 在 Internet Explorer 的 \[工具\] 功能表，按一下 \[網際網路選項\]。 2. 在 \[網際網路選項\] 對話方塊中，按一下 \[安全性\] 索引標籤，再按 \[網際網路\] 圖示。 3. 在 \[此區域的安全性等級\] 下方，將滑桿移至 \[高\]。如此即可將您所造訪的所有網站都設定為 \[高\] 安全層級注意：如果沒有顯示滑桿，按一下 \[預設等級\]，再將滑桿移至 \[高\]。注意：設定為 \[高安全性\] 層級可能會使部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。如此一來，即使採用 \[高\] 設定，該網站仍可正確運作。因應措施的影響。封鎖 ActiveX 控制項和動態指令碼處理會產生副作用。許多網際網路及內部網路的網站使用 ActiveX 或動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用 ActiveX 控制項提供功能表、訂單、甚至是帳戶明細。封鎖 ActiveX 控制項或動態指令碼處理是一種通用設定，該設定會影響所有網際網路及內部網路網站。如果您不希望封鎖這些網站的 ActiveX 控制項或動態指令碼處理，請使用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域封鎖 ActiveX 控制項及動態指令碼處理之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 - 設定 Internet Explorer，以便在執行動態指令碼之前先行提示或停用網際網路及近端內部網路安全性區域內的動態指令碼只要將設定變更為在執行或停用網際網路及近端內部網路安全性區域內的動態指令碼之前先提示，即可防範這個弱點遭到利用。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，按一下 \[工具\] 功能表的 \[網際網路選項\] 2. 按一下 \[安全性\] 索引標籤 3. 按一下 \[網際網路\]，然後按 \[自訂等級\]。 4. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 5. 按一下 \[近端內部網路\]，然後按 \[自訂層級\]。 6. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 7. 按兩次 \[確定\] 回到 Internet Explorer。注意：在網際網路和近端內部網路安全性區域中停用動態指令碼，可能會導致部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。這樣就能讓網站正確運作。因應措施的影響。執行動態指令碼前先提示的設定會產生副作用。許多網際網路及內部網路的網站使用動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用動態指令碼提供功能表、訂單、甚至是帳戶明細。執行動態指令碼前先提示屬於通用設定，會影響所有網際網路及內部網路網站。使用這個因應措施的話，您會時常收到提示。每次出現提示時，如果您覺得可以信任該網站，請按一下 \[是\] 執行動態指令碼處理。如果您不要收到這些網站的提示，請改用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域執行 ActiveX 控制項及動態指令碼處理前會顯示提示之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 #### OLEAuto32.dll 遠端執行程式碼弱點 - CVE-2011-1995 的常見問題集這個弱點的範圍為何？這是遠端執行程式碼的弱點。成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。造成這個弱點的原因為何？當 Internet Explorer 嘗試存取未初始化的物件時，記憶體可能發生損毀，讓攻擊者可以透過登入使用者的權限層級執行任意程式碼。攻擊者可能會利用這項弱點採取什麼行動？成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。如果使用者以系統管理的使用者權限登入，成功利用此弱點的攻擊者可以取得受影響系統的完整控制權。攻擊者接下來將能安裝程式，檢視、變更或刪除資料，或建立具有完整使用者權限的新帳戶。攻擊者如何利用這項弱點？攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。因為這個弱點而承受風險的主要系統有哪些？常使用 Internet Explorer 的系統 (例如工作站或終端伺服器) 的風險最大。我用的是適用於 Windows Server 2003、Windows Server 2008 或 Windows Server 2008 R2 的 Internet Explorer。這樣是否會減輕此弱點的影響？是。依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。增強式安全性設定是一組預先設定好的 Internet Explorer 設定，可以降低使用者或系統管理員在伺服器下載及執行蓄意製作之網頁內容的可能性。對於您尚未新增至 Internet Explorer \[信任的網站\] 區域的網站，這是一種緩和因素。更新的作用何在？此更新會修改 Internet Explorer 處理記憶體中物件的方式，藉此解決此弱點。當安全性公告發行時，這項弱點是否已揭發出來？否。Microsoft 是經由協同合作的來源接獲有關這項弱點的訊息。當本安全性公告發行時，Microsoft 是否已接獲任何消息，指出這項弱點已遭有心人士利用？否。當本安全性公告初次發行時，Microsoft 尚未接到任何有關本弱點已公開用來攻擊客戶的消息。 Option 項目遠端執行程式碼弱點 - CVE-2011-1996 --------------------------------------------- Internet Explorer 存取已刪除物件的方式中，存在遠端執行程式碼弱點。此弱點可能會損毀記憶體，使攻擊者有機會透過登入使用者的權限層級執行任意程式碼。若要在「一般性弱點」清單標準條目中檢視此弱點，請參閱 [CVE-2011-1996](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2011-1996) (英文)。 #### Option 項目遠端執行程式碼弱點 - CVE-2011-1996 的緩和因素緩和因素是指存在於預設狀態中的設定、共用設定或一般最佳作法，可能會減少弱點影響的嚴重性。下列緩和因素可能對您的狀況有所助益： - 攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。 - 成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。 - 根據預設值，Microsoft Outlook、Microsoft Outlook Express 及 Windows Mail 的所有支援版本會在 \[限制的網站\] 區域中開啟 HTML 電子郵件訊息，進而停用指令碼與 ActiveX 控制項，以協助降低攻擊者能夠利用此弱點執行惡意程式碼的風險。如果使用者按下電子郵件訊息中的連結，仍有可能因為網頁式攻擊而受此弱點遭利用的影響。 - 依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。此模式可緩和這項弱點。如需更多資訊，請參閱此弱點＜常見問題集＞關於 Internet Explorer 增強式安全性設定的部份。 - Internet Explorer 9 不受這個弱點影響。 #### Option 項目遠端執行程式碼弱點 - CVE-2011-1996 的因應措施因應措施指的是無法徹底修正弱點，但有助於在套用更新之前封鎖已知攻擊模式的設定變更。Microsoft 測試了下列因應措施和狀態，討論因應措施是否會降低功能： - 將 \[網際網路\] 及 \[近端內部網路\] 安全性區域設定為 \[高\]，可封鎖這些區域中的 ActiveX 控制項及動態指令碼處理只要將網際網路安全性區域設定變更為封鎖 ActiveX 控制項及動態指令碼處理，即可防範這個弱點遭到利用。做法是將瀏覽器的安全性設定為 \[高\]。若要在 Internet Explorer 中提高瀏覽器的安全層級，請執行下列步驟： 1. 在 Internet Explorer 的 \[工具\] 功能表，按一下 \[網際網路選項\]。 2. 在 \[網際網路選項\] 對話方塊中，按一下 \[安全性\] 索引標籤，再按 \[網際網路\] 圖示。 3. 在 \[此區域的安全性等級\] 下方，將滑桿移至 \[高\]。如此即可將您所造訪的所有網站都設定為 \[高\] 安全層級注意：如果沒有顯示滑桿，按一下 \[預設等級\]，再將滑桿移至 \[高\]。注意：設定為 \[高安全性\] 層級可能會使部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。如此一來，即使採用 \[高\] 設定，該網站仍可正確運作。因應措施的影響。封鎖 ActiveX 控制項和動態指令碼處理會產生副作用。許多網際網路及內部網路的網站使用 ActiveX 或動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用 ActiveX 控制項提供功能表、訂單、甚至是帳戶明細。封鎖 ActiveX 控制項或動態指令碼處理是一種通用設定，該設定會影響所有網際網路及內部網路網站。如果您不希望封鎖這些網站的 ActiveX 控制項或動態指令碼處理，請使用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域封鎖 ActiveX 控制項及動態指令碼處理之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 - 設定 Internet Explorer，以便在執行動態指令碼之前先行提示或停用網際網路及近端內部網路安全性區域內的動態指令碼只要將設定變更為在執行或停用網際網路及近端內部網路安全性區域內的動態指令碼之前先提示，即可防範這個弱點遭到利用。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，按一下 \[工具\] 功能表的 \[網際網路選項\] 2. 按一下 \[安全性\] 索引標籤 3. 按一下 \[網際網路\]，然後按 \[自訂等級\]。 4. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 5. 按一下 \[近端內部網路\]，然後按 \[自訂層級\]。 6. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 7. 按兩次 \[確定\] 回到 Internet Explorer。注意：在網際網路和近端內部網路安全性區域中停用動態指令碼，可能會導致部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。這樣就能讓網站正確運作。因應措施的影響。執行動態指令碼前先提示的設定會產生副作用。許多網際網路及內部網路的網站使用動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用動態指令碼提供功能表、訂單、甚至是帳戶明細。執行動態指令碼前先提示屬於通用設定，會影響所有網際網路及內部網路網站。使用這個因應措施的話，您會時常收到提示。每次出現提示時，如果您覺得可以信任該網站，請按一下 \[是\] 執行動態指令碼處理。如果您不要收到這些網站的提示，請改用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域執行 ActiveX 控制項及動態指令碼處理前會顯示提示之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 #### Option 項目遠端執行程式碼弱點 - CVE-2011-1996 的常見問題集這個弱點的範圍為何？這是遠端執行程式碼的弱點。成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。造成這個弱點的原因為何？當 Internet Explorer 嘗試存取已遭刪除的物件時，記憶體可能會遭到損壞，讓攻擊者可以透過登入使用者的權限層級執行任意程式碼。攻擊者可能會利用這項弱點採取什麼行動？成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。如果使用者以系統管理的使用者權限登入，成功利用此弱點的攻擊者可以取得受影響系統的完整控制權。攻擊者接下來將能安裝程式，檢視、變更或刪除資料，或建立具有完整使用者權限的新帳戶。攻擊者如何利用這項弱點？攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。因為這個弱點而承受風險的主要系統有哪些？常使用 Internet Explorer 的系統 (例如工作站或終端伺服器) 的風險最大。更新的作用何在？此更新會修改 Internet Explorer 處理記憶體中物件的方式，藉此解決此弱點。當安全性公告發行時，這項弱點是否已揭發出來？否。Microsoft 是經由協同合作的來源接獲有關這項弱點的訊息。當本安全性公告發行時，Microsoft 是否已接獲任何消息，指出這項弱點已遭有心人士利用？否。當本安全性公告初次發行時，Microsoft 尚未接到任何有關本弱點已公開用來攻擊客戶的消息。 OnLoad 事件遠端執行程式碼弱點 - CVE-2011-1997 --------------------------------------------- Internet Explorer 存取已刪除物件的方式中，存在遠端執行程式碼弱點。此弱點可能會損毀記憶體，使攻擊者有機會透過登入使用者的權限層級執行任意程式碼。若要在「一般性弱點」清單標準條目中檢視此弱點，請參閱 [CVE-2011-1997](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2011-1997) (英文)。 #### OnLoad 事件遠端執行程式碼弱點 - CVE-2011-1997 的緩和因素緩和因素是指存在於預設狀態中的設定、共用設定或一般最佳作法，可能會減少弱點影響的嚴重性。下列緩和因素可能對您的狀況有所助益： - 在網頁型攻擊的案例中，攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。 - 成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。 - 根據預設值，Microsoft Outlook、Microsoft Outlook Express 及 Windows Mail 的所有支援版本會在 \[限制的網站\] 區域中開啟 HTML 電子郵件訊息，進而停用指令碼與 ActiveX 控制項，以協助降低攻擊者能夠利用此弱點執行惡意程式碼的風險。如果使用者按下電子郵件訊息中的連結，仍有可能因為網頁式攻擊而受此弱點遭利用的影響。 - 依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。此模式可緩和這項弱點。如需更多資訊，請參閱此弱點＜常見問題集＞關於 Internet Explorer 增強式安全性設定的部份。 - Internet Explorer 7、Internet Explorer 8 及 Internet Explorer 9 不受此弱點影響。 #### OnLoad 事件遠端執行程式碼弱點 - CVE-2011-1997 的因應措施因應措施指的是無法徹底修正弱點，但有助於在套用更新之前封鎖已知攻擊模式的設定變更。Microsoft 測試了下列因應措施和狀態，討論因應措施是否會降低功能： - 將 \[網際網路\] 及 \[近端內部網路\] 安全性區域設定為 \[高\]，可封鎖這些區域中的 ActiveX 控制項及動態指令碼處理只要將網際網路安全性區域設定變更為封鎖 ActiveX 控制項及動態指令碼處理，即可防範這個弱點遭到利用。做法是將瀏覽器的安全性設定為 \[高\]。若要在 Internet Explorer 中提高瀏覽器的安全層級，請執行下列步驟： 1. 在 Internet Explorer 的 \[工具\] 功能表，按一下 \[網際網路選項\]。 2. 在 \[網際網路選項\] 對話方塊中，按一下 \[安全性\] 索引標籤，再按 \[網際網路\] 圖示。 3. 在 \[此區域的安全性等級\] 下方，將滑桿移至 \[高\]。如此即可將您所造訪的所有網站都設定為 \[高\] 安全層級注意：如果沒有顯示滑桿，按一下 \[預設等級\]，再將滑桿移至 \[高\]。注意：設定為 \[高安全性\] 層級可能會使部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。如此一來，即使採用 \[高\] 設定，該網站仍可正確運作。因應措施的影響。封鎖 ActiveX 控制項和動態指令碼處理會產生副作用。許多網際網路及內部網路的網站使用 ActiveX 或動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用 ActiveX 控制項提供功能表、訂單、甚至是帳戶明細。封鎖 ActiveX 控制項或動態指令碼處理是一種通用設定，該設定會影響所有網際網路及內部網路網站。如果您不希望封鎖這些網站的 ActiveX 控制項或動態指令碼處理，請使用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域封鎖 ActiveX 控制項及動態指令碼處理之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 - 設定 Internet Explorer，以便在執行動態指令碼之前先行提示或停用網際網路及近端內部網路安全性區域內的動態指令碼只要將設定變更為在執行或停用網際網路及近端內部網路安全性區域內的動態指令碼之前先提示，即可防範這個弱點遭到利用。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，按一下 \[工具\] 功能表的 \[網際網路選項\] 2. 按一下 \[安全性\] 索引標籤 3. 按一下 \[網際網路\]，然後按 \[自訂等級\]。 4. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 5. 按一下 \[近端內部網路\]，然後按 \[自訂層級\]。 6. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 7. 按兩次 \[確定\] 回到 Internet Explorer。注意：在網際網路和近端內部網路安全性區域中停用動態指令碼，可能會導致部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。這樣就能讓網站正確運作。因應措施的影響。執行動態指令碼前先提示的設定會產生副作用。許多網際網路及內部網路的網站使用動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用動態指令碼提供功能表、訂單、甚至是帳戶明細。執行動態指令碼前先提示屬於通用設定，會影響所有網際網路及內部網路網站。使用這個因應措施的話，您會時常收到提示。每次出現提示時，如果您覺得可以信任該網站，請按一下 \[是\] 執行動態指令碼處理。如果您不要收到這些網站的提示，請改用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域執行 ActiveX 控制項及動態指令碼處理前會顯示提示之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 #### OnLoad 事件遠端執行程式碼弱點 - CVE-2011-1997 的常見問題集這個弱點的範圍為何？這是遠端執行程式碼的弱點。成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。造成這個弱點的原因為何？當 Internet Explorer 嘗試存取已遭刪除的物件時，記憶體可能會遭到損壞，讓攻擊者可以透過登入使用者的權限層級執行任意程式碼。攻擊者可能會利用這項弱點採取什麼行動？成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。如果使用者以系統管理的使用者權限登入，成功利用此弱點的攻擊者可以取得受影響系統的完整控制權。攻擊者接下來將能安裝程式，檢視、變更或刪除資料，或建立具有完整使用者權限的新帳戶。攻擊者如何利用這項弱點？攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。因為這個弱點而承受風險的主要系統有哪些？常使用 Internet Explorer 的系統 (例如工作站或終端伺服器) 的風險最大。我用的是適用於 Windows Server 2003、Windows Server 2008 或 Windows Server 2008 R2 的 Internet Explorer。這樣是否會減輕此弱點的影響？是。依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。增強式安全性設定是一組預先設定好的 Internet Explorer 設定，可以降低使用者或系統管理員在伺服器下載及執行蓄意製作之網頁內容的可能性。對於您尚未新增至 Internet Explorer \[信任的網站\] 區域的網站，這是一種緩和因素。更新的作用何在？此更新會修改 Internet Explorer 處理記憶體中物件的方式，藉此解決此弱點。當安全性公告發行時，這項弱點是否已揭發出來？否。Microsoft 是經由協同合作的來源接獲有關這項弱點的訊息。當本安全性公告發行時，Microsoft 是否已接獲任何消息，指出這項弱點已遭有心人士利用？否。當本安全性公告初次發行時，Microsoft 尚未接到任何有關本弱點已公開用來攻擊客戶的消息。 Jscript9.dll 遠端執行程式碼弱點 - CVE-2011-1998 ----------------------------------------------- Internet Explorer 存取未正確初始化之物件的方式中，存在遠端執行程式碼的弱點。此弱點可能會損毀記憶體，使攻擊者有機會透過登入使用者的權限層級執行任意程式碼。若要在「一般性弱點」清單標準條目中檢視此弱點，請參閱 [CVE-2011-1998](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2011-1998) (英文)。 #### Jscript9.dll 遠端執行程式碼弱點 - CVE-2011-1998 的緩和因素緩和因素是指存在於預設狀態中的設定、共用設定或一般最佳作法，可能會減少弱點影響的嚴重性。下列緩和因素可能對您的狀況有所助益： - 在網頁型攻擊的案例中，攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。 - 成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。 - 根據預設值，Microsoft Outlook、Microsoft Outlook Express 及 Windows Mail 的所有支援版本會在 \[限制的網站\] 區域中開啟 HTML 電子郵件訊息，進而停用指令碼與 ActiveX 控制項，以協助降低攻擊者能夠利用此弱點執行惡意程式碼的風險。如果使用者按下電子郵件訊息中的連結，仍有可能因為網頁式攻擊而受此弱點遭利用的影響。 - 依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。此模式可緩和這項弱點。如需更多資訊，請參閱此弱點＜常見問題集＞關於 Internet Explorer 增強式安全性設定的部份。 #### Jscript9.dll 遠端執行程式碼弱點 - CVE-2011-1998 的因應措施因應措施指的是無法徹底修正弱點，但有助於在套用更新之前封鎖已知攻擊模式的設定變更。Microsoft 測試了下列因應措施和狀態，討論因應措施是否會降低功能： - 將 \[網際網路\] 及 \[近端內部網路\] 安全性區域設定為 \[高\]，可封鎖這些區域中的 ActiveX 控制項及動態指令碼處理只要將網際網路安全性區域設定變更為封鎖 ActiveX 控制項及動態指令碼處理，即可防範這個弱點遭到利用。做法是將瀏覽器的安全性設定為 \[高\]。若要在 Internet Explorer 中提高瀏覽器的安全層級，請執行下列步驟： 1. 在 Internet Explorer 的 \[工具\] 功能表，按一下 \[網際網路選項\]。 2. 在 \[網際網路選項\] 對話方塊中，按一下 \[安全性\] 索引標籤，再按 \[網際網路\] 圖示。 3. 在 \[此區域的安全性等級\] 下方，將滑桿移至 \[高\]。如此即可將您所造訪的所有網站都設定為 \[高\] 安全層級注意：如果沒有顯示滑桿，按一下 \[預設等級\]，再將滑桿移至 \[高\]。注意：設定為 \[高安全性\] 層級可能會使部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。如此一來，即使採用 \[高\] 設定，該網站仍可正確運作。因應措施的影響。封鎖 ActiveX 控制項和動態指令碼處理會產生副作用。許多網際網路及內部網路的網站使用 ActiveX 或動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用 ActiveX 控制項提供功能表、訂單、甚至是帳戶明細。封鎖 ActiveX 控制項或動態指令碼處理是一種通用設定，該設定會影響所有網際網路及內部網路網站。如果您不希望封鎖這些網站的 ActiveX 控制項或動態指令碼處理，請使用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域封鎖 ActiveX 控制項及動態指令碼處理之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 - 設定 Internet Explorer，以便在執行動態指令碼之前先行提示或停用網際網路及近端內部網路安全性區域內的動態指令碼只要將設定變更為在執行或停用網際網路及近端內部網路安全性區域內的動態指令碼之前先提示，即可防範這個弱點遭到利用。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，按一下 \[工具\] 功能表的 \[網際網路選項\] 2. 按一下 \[安全性\] 索引標籤 3. 按一下 \[網際網路\]，然後按 \[自訂等級\]。 4. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 5. 按一下 \[近端內部網路\]，然後按 \[自訂層級\]。 6. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 7. 按兩次 \[確定\] 回到 Internet Explorer。注意：在網際網路和近端內部網路安全性區域中停用動態指令碼，可能會導致部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。這樣就能讓網站正確運作。因應措施的影響。執行動態指令碼前先提示的設定會產生副作用。許多網際網路及內部網路的網站使用動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用動態指令碼提供功能表、訂單、甚至是帳戶明細。執行動態指令碼前先提示屬於通用設定，會影響所有網際網路及內部網路網站。使用這個因應措施的話，您會時常收到提示。每次出現提示時，如果您覺得可以信任該網站，請按一下 \[是\] 執行動態指令碼處理。如果您不要收到這些網站的提示，請改用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域執行 ActiveX 控制項及動態指令碼處理前會顯示提示之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 #### Jscript9.dll 遠端執行程式碼弱點 - CVE-2011-1998 的常見問題集這個弱點的範圍為何？這是遠端執行程式碼的弱點。成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。造成這個弱點的原因為何？當 Internet Explorer 嘗試存取未初始化的物件時，記憶體可能發生損毀，讓攻擊者可以透過登入使用者的權限層級執行任意程式碼。攻擊者可能會利用這項弱點採取什麼行動？成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。如果使用者以系統管理的使用者權限登入，成功利用此弱點的攻擊者可以取得受影響系統的完整控制權。攻擊者接下來將能安裝程式，檢視、變更或刪除資料，或建立具有完整使用者權限的新帳戶。攻擊者如何利用這項弱點？攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站，並在該網站上執行作業。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。因為這個弱點而承受風險的主要系統有哪些？常使用 Internet Explorer 的系統 (例如工作站或終端伺服器) 的風險最大。我用的是適用於 Windows Server 2003、Windows Server 2008 或 Windows Server 2008 R2 的 Internet Explorer。這樣是否會減輕此弱點的影響？是。依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。增強式安全性設定是一組預先設定好的 Internet Explorer 設定，可以降低使用者或系統管理員在伺服器下載及執行蓄意製作之網頁內容的可能性。對於您尚未新增至 Internet Explorer \[信任的網站\] 區域的網站，這是一種緩和因素。更新的作用何在？此更新會修改 Internet Explorer 處理記憶體中物件的方式，藉此解決此弱點。當安全性公告發行時，這項弱點是否已揭發出來？否。Microsoft 是經由協同合作的來源接獲有關這項弱點的訊息。當本安全性公告發行時，Microsoft 是否已接獲任何消息，指出這項弱點已遭有心人士利用？否。當本安全性公告初次發行時，Microsoft 尚未接到任何有關本弱點已公開用來攻擊客戶的消息。 SELECT 項目遠端執行程式碼弱點 - CVE-2011-1999 --------------------------------------------- Internet Explorer 存取已解除參照之記憶體位址的方式中，存在遠端執行程式碼的弱點。此弱點可能會損毀記憶體，使攻擊者有機會透過登入使用者的權限層級執行任意程式碼。若要在「一般性弱點」清單標準條目中檢視此弱點，請參閱 [CVE-2011-1999](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2011-1999) (英文)。 #### Select 項目遠端執行程式碼弱點 - CVE-2011-1999 的緩和因素緩和因素是指存在於預設狀態中的設定、共用設定或一般最佳作法，可能會減少弱點影響的嚴重性。下列緩和因素可能對您的狀況有所助益： - 在網頁型攻擊的案例中，攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。 - 成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。 - 根據預設值，Microsoft Outlook、Microsoft Outlook Express 及 Windows Mail 的所有支援版本會在 \[限制的網站\] 區域中開啟 HTML 電子郵件訊息，進而停用指令碼與 ActiveX 控制項，以協助降低攻擊者能夠利用此弱點執行惡意程式碼的風險。如果使用者按下電子郵件訊息中的連結，仍有可能因為網頁式攻擊而受此弱點遭利用的影響。 - 依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。此模式可緩和這項弱點。如需更多資訊，請參閱此弱點＜常見問題集＞關於 Internet Explorer 增強式安全性設定的部份。 - Internet Explorer 6、Internet Explorer 7 和 Internet Explorer 9 並未受此弱點影響。 #### Select 項目遠端執行程式碼弱點 - CVE-2011-1999 的因應措施因應措施指的是無法徹底修正弱點，但有助於在套用更新之前封鎖已知攻擊模式的設定變更。Microsoft 測試了下列因應措施和狀態，討論因應措施是否會降低功能： - 將 \[網際網路\] 及 \[近端內部網路\] 安全性區域設定為 \[高\]，可封鎖這些區域中的 ActiveX 控制項及動態指令碼處理只要將網際網路安全性區域設定變更為封鎖 ActiveX 控制項及動態指令碼處理，即可防範這個弱點遭到利用。做法是將瀏覽器的安全性設定為 \[高\]。若要在 Internet Explorer 中提高瀏覽器的安全層級，請執行下列步驟： 1. 在 Internet Explorer 的 \[工具\] 功能表，按一下 \[網際網路選項\]。 2. 在 \[網際網路選項\] 對話方塊中，按一下 \[安全性\] 索引標籤，再按 \[網際網路\] 圖示。 3. 在 \[此區域的安全性等級\] 下方，將滑桿移至 \[高\]。如此即可將您所造訪的所有網站都設定為 \[高\] 安全層級注意：如果沒有顯示滑桿，按一下 \[預設等級\]，再將滑桿移至 \[高\]。注意：設定為 \[高安全性\] 層級可能會使部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。如此一來，即使採用 \[高\] 設定，該網站仍可正確運作。因應措施的影響。封鎖 ActiveX 控制項和動態指令碼處理會產生副作用。許多網際網路及內部網路的網站使用 ActiveX 或動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用 ActiveX 控制項提供功能表、訂單、甚至是帳戶明細。封鎖 ActiveX 控制項或動態指令碼處理是一種通用設定，該設定會影響所有網際網路及內部網路網站。如果您不希望封鎖這些網站的 ActiveX 控制項或動態指令碼處理，請使用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域封鎖 ActiveX 控制項及動態指令碼處理之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 - 設定 Internet Explorer，以便在執行動態指令碼之前先行提示或停用網際網路及近端內部網路安全性區域內的動態指令碼只要將設定變更為在執行或停用網際網路及近端內部網路安全性區域內的動態指令碼之前先提示，即可防範這個弱點遭到利用。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，按一下 \[工具\] 功能表的 \[網際網路選項\] 2. 按一下 \[安全性\] 索引標籤 3. 按一下 \[網際網路\]，然後按 \[自訂等級\]。 4. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 5. 按一下 \[近端內部網路\]，然後按 \[自訂層級\]。 6. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 7. 按兩次 \[確定\] 回到 Internet Explorer。注意：在網際網路和近端內部網路安全性區域中停用動態指令碼，可能會導致部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。這樣就能讓網站正確運作。因應措施的影響。執行動態指令碼前先提示的設定會產生副作用。許多網際網路及內部網路的網站使用動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用動態指令碼提供功能表、訂單、甚至是帳戶明細。執行動態指令碼前先提示屬於通用設定，會影響所有網際網路及內部網路網站。使用這個因應措施的話，您會時常收到提示。每次出現提示時，如果您覺得可以信任該網站，請按一下 \[是\] 執行動態指令碼處理。如果您不要收到這些網站的提示，請改用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域執行 ActiveX 控制項及動態指令碼處理前會顯示提示之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 #### Select 項目遠端執行程式碼弱點 - CVE-2011-1999 的常見問題集這個弱點的範圍為何？這是遠端執行程式碼的弱點。成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。造成這個弱點的原因為何？當 Internet Explorer 嘗試存取已解除參照的記憶體位址時，記憶體可能發生損毀，讓攻擊者可以透過登入使用者的權限層級執行任意程式碼。攻擊者可能會利用這項弱點採取什麼行動？成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。如果使用者以系統管理的使用者權限登入，成功利用此弱點的攻擊者可以取得受影響系統的完整控制權。攻擊者接下來將能安裝程式，檢視、變更或刪除資料，或建立具有完整使用者權限的新帳戶。攻擊者如何利用這項弱點？攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。因為這個弱點而承受風險的主要系統有哪些？常使用 Internet Explorer 的系統 (例如工作站或終端伺服器) 的風險最大。我用的是適用於 Windows Server 2003、Windows Server 2008 或 Windows Server 2008 R2 的 Internet Explorer。這樣是否會減輕此弱點的影響？是。依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。增強式安全性設定是一組預先設定好的 Internet Explorer 設定，可以降低使用者或系統管理員在伺服器下載及執行蓄意製作之網頁內容的可能性。對於您尚未新增至 Internet Explorer \[信任的網站\] 區域的網站，這是一種緩和因素。更新的作用何在？此更新會修改 Internet Explorer 配置及存取記憶體的方式，藉此解決此弱點。當安全性公告發行時，這項弱點是否已揭發出來？否。Microsoft 是經由協同合作的來源接獲有關這項弱點的訊息。當本安全性公告發行時，Microsoft 是否已接獲任何消息，指出這項弱點已遭有心人士利用？否。當本安全性公告初次發行時，Microsoft 尚未接到任何有關本弱點已公開用來攻擊客戶的消息。 Body 項目遠端執行程式碼弱點 - CVE-2011-2000 ------------------------------------------- Internet Explorer 存取已刪除物件的方式中，存在遠端執行程式碼弱點。此弱點可能會損毀記憶體，使攻擊者有機會透過登入使用者的權限層級執行任意程式碼。若要在「一般性弱點」清單標準條目中檢視此弱點，請參閱 [CVE-2011-2000](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2011-2000) (英文)。 #### Body 項目遠端執行程式碼弱點 - CVE-2011-2000 的緩和因素緩和因素是指存在於預設狀態中的設定、共用設定或一般最佳作法，可能會減少弱點影響的嚴重性。下列緩和因素可能對您的狀況有所助益： - 在網頁型攻擊的案例中，攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。 - 成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。 - 根據預設值，Microsoft Outlook、Microsoft Outlook Express 及 Windows Mail 的所有支援版本會在 \[限制的網站\] 區域中開啟 HTML 電子郵件訊息，進而停用指令碼與 ActiveX 控制項，以協助降低攻擊者能夠利用此弱點執行惡意程式碼的風險。如果使用者按下電子郵件訊息中的連結，仍有可能因為網頁式攻擊而受此弱點遭利用的影響。 - 依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。此模式可緩和這項弱點。如需更多資訊，請參閱此弱點＜常見問題集＞關於 Internet Explorer 增強式安全性設定的部份。 #### Body 項目遠端執行程式碼弱點 - CVE-2011-2000 的因應措施因應措施指的是無法徹底修正弱點，但有助於在套用更新之前封鎖已知攻擊模式的設定變更。Microsoft 測試了下列因應措施和狀態，討論因應措施是否會降低功能： - 將 \[網際網路\] 及 \[近端內部網路\] 安全性區域設定為 \[高\]，可封鎖這些區域中的 ActiveX 控制項及動態指令碼處理只要將網際網路安全性區域設定變更為封鎖 ActiveX 控制項及動態指令碼處理，即可防範這個弱點遭到利用。做法是將瀏覽器的安全性設定為 \[高\]。若要在 Internet Explorer 中提高瀏覽器的安全層級，請執行下列步驟： 1. 在 Internet Explorer 的 \[工具\] 功能表，按一下 \[網際網路選項\]。 2. 在 \[網際網路選項\] 對話方塊中，按一下 \[安全性\] 索引標籤，再按 \[網際網路\] 圖示。 3. 在 \[此區域的安全性等級\] 下方，將滑桿移至 \[高\]。如此即可將您所造訪的所有網站都設定為 \[高\] 安全層級注意：如果沒有顯示滑桿，按一下 \[預設等級\]，再將滑桿移至 \[高\]。注意：設定為 \[高安全性\] 層級可能會使部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。如此一來，即使採用 \[高\] 設定，該網站仍可正確運作。因應措施的影響。封鎖 ActiveX 控制項和動態指令碼處理會產生副作用。許多網際網路及內部網路的網站使用 ActiveX 或動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用 ActiveX 控制項提供功能表、訂單、甚至是帳戶明細。封鎖 ActiveX 控制項或動態指令碼處理是一種通用設定，該設定會影響所有網際網路及內部網路網站。如果您不希望封鎖這些網站的 ActiveX 控制項或動態指令碼處理，請使用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域封鎖 ActiveX 控制項及動態指令碼處理之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 - 設定 Internet Explorer，以便在執行動態指令碼之前先行提示或停用網際網路及近端內部網路安全性區域內的動態指令碼只要將設定變更為在執行或停用網際網路及近端內部網路安全性區域內的動態指令碼之前先提示，即可防範這個弱點遭到利用。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，按一下 \[工具\] 功能表的 \[網際網路選項\] 2. 按一下 \[安全性\] 索引標籤 3. 按一下 \[網際網路\]，然後按 \[自訂等級\]。 4. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 5. 按一下 \[近端內部網路\]，然後按 \[自訂層級\]。 6. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 7. 按兩次 \[確定\] 回到 Internet Explorer。注意：在網際網路和近端內部網路安全性區域中停用動態指令碼，可能會導致部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。這樣就能讓網站正確運作。因應措施的影響。執行動態指令碼前先提示的設定會產生副作用。許多網際網路及內部網路的網站使用動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用動態指令碼提供功能表、訂單、甚至是帳戶明細。執行動態指令碼前先提示屬於通用設定，會影響所有網際網路及內部網路網站。使用這個因應措施的話，您會時常收到提示。每次出現提示時，如果您覺得可以信任該網站，請按一下 \[是\] 執行動態指令碼處理。如果您不要收到這些網站的提示，請改用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域執行 ActiveX 控制項及動態指令碼處理前會顯示提示之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 #### Body 項目遠端執行程式碼弱點 - CVE-2011-2000 的常見問題集這個弱點的範圍為何？這是遠端執行程式碼的弱點。成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。造成這個弱點的原因為何？當 Internet Explorer 嘗試存取已遭刪除的物件時，記憶體可能會遭到損壞，讓攻擊者可以透過登入使用者的權限層級執行任意程式碼。攻擊者可能會利用這項弱點採取什麼行動？成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。如果使用者以系統管理的使用者權限登入，成功利用此弱點的攻擊者可以取得受影響系統的完整控制權。攻擊者接下來將能安裝程式，檢視、變更或刪除資料，或建立具有完整使用者權限的新帳戶。攻擊者如何利用這項弱點？攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。因為這個弱點而承受風險的主要系統有哪些？常使用 Internet Explorer 的系統 (例如工作站或終端伺服器) 的風險最大。我用的是適用於 Windows Server 2003、Windows Server 2008 或 Windows Server 2008 R2 的 Internet Explorer。這樣是否會減輕此弱點的影響？是。依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。增強式安全性設定是一組預先設定好的 Internet Explorer 設定，可以降低使用者或系統管理員在伺服器下載及執行蓄意製作之網頁內容的可能性。對於您尚未新增至 Internet Explorer \[信任的網站\] 區域的網站，這是一種緩和因素。更新的作用何在？此更新會修改 Internet Explorer 處理記憶體中物件的方式，藉此解決此弱點。當安全性公告發行時，這項弱點是否已揭發出來？否。Microsoft 是經由協同合作的來源接獲有關這項弱點的訊息。當本安全性公告發行時，Microsoft 是否已接獲任何消息，指出這項弱點已遭有心人士利用？否。當本安全性公告初次發行時，Microsoft 尚未接到任何有關本弱點已公開用來攻擊客戶的消息。虛擬函式表損毀遠端執行程式碼弱點 - CVE-2011-2001 ------------------------------------------------ Internet Explorer 存取已損毀之虛擬函式表的方式中，存在遠端執行程式碼的弱點。此弱點可能會損毀記憶體，使攻擊者有機會透過登入使用者的權限層級執行任意程式碼。若要在「一般性弱點」清單標準條目中檢視此弱點，請參閱 [CVE-2011-2001](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2011-2001) (英文)。 #### 虛擬函式表損毀遠端執行程式碼弱點 - CVE-2011-2001 的緩和因素緩和因素是指存在於預設狀態中的設定、共用設定或一般最佳作法，可能會減少弱點影響的嚴重性。下列緩和因素可能對您的狀況有所助益： - 攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。 - 成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。 - 根據預設值，Microsoft Outlook、Microsoft Outlook Express 及 Windows Mail 的所有支援版本會在 \[限制的網站\] 區域中開啟 HTML 電子郵件訊息，進而停用指令碼與 ActiveX 控制項，以協助降低攻擊者能夠利用此弱點執行惡意程式碼的風險。如果使用者按下電子郵件訊息中的連結，仍有可能因為網頁式攻擊而受此弱點遭利用的影響。 - 依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。此模式可緩和這項弱點。如需更多資訊，請參閱此弱點＜常見問題集＞關於 Internet Explorer 增強式安全性設定的部份。 #### 虛擬函式表損毀遠端執行程式碼弱點 - CVE-2011-2001 的因應措施因應措施指的是無法徹底修正弱點，但有助於在套用更新之前封鎖已知攻擊模式的設定變更。Microsoft 測試了下列因應措施和狀態，討論因應措施是否會降低功能： - 將 \[網際網路\] 及 \[近端內部網路\] 安全性區域設定為 \[高\]，可封鎖這些區域中的 ActiveX 控制項及動態指令碼處理只要將網際網路安全性區域設定變更為封鎖 ActiveX 控制項及動態指令碼處理，即可防範這個弱點遭到利用。做法是將瀏覽器的安全性設定為 \[高\]。若要在 Internet Explorer 中提高瀏覽器的安全層級，請執行下列步驟： 1. 在 Internet Explorer 的 \[工具\] 功能表，按一下 \[網際網路選項\]。 2. 在 \[網際網路選項\] 對話方塊中，按一下 \[安全性\] 索引標籤，再按 \[網際網路\] 圖示。 3. 在 \[此區域的安全性等級\] 下方，將滑桿移至 \[高\]。如此即可將您所造訪的所有網站都設定為 \[高\] 安全層級注意：如果沒有顯示滑桿，按一下 \[預設等級\]，再將滑桿移至 \[高\]。注意：設定為 \[高安全性\] 層級可能會使部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。如此一來，即使採用 \[高\] 設定，該網站仍可正確運作。因應措施的影響。封鎖 ActiveX 控制項和動態指令碼處理會產生副作用。許多網際網路及內部網路的網站使用 ActiveX 或動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用 ActiveX 控制項提供功能表、訂單、甚至是帳戶明細。封鎖 ActiveX 控制項或動態指令碼處理是一種通用設定，該設定會影響所有網際網路及內部網路網站。如果您不希望封鎖這些網站的 ActiveX 控制項或動態指令碼處理，請使用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域封鎖 ActiveX 控制項及動態指令碼處理之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 - 設定 Internet Explorer，以便在執行動態指令碼之前先行提示或停用網際網路及近端內部網路安全性區域內的動態指令碼只要將設定變更為在執行或停用網際網路及近端內部網路安全性區域內的動態指令碼之前先提示，即可防範這個弱點遭到利用。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，按一下 \[工具\] 功能表的 \[網際網路選項\] 2. 按一下 \[安全性\] 索引標籤 3. 按一下 \[網際網路\]，然後按 \[自訂等級\]。 4. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 5. 按一下 \[近端內部網路\]，然後按 \[自訂層級\]。 6. 在 \[設定\] 的 \[指令碼處理\] 區段中，按一下 \[Active Scripting\] 下的 \[提示\] 或 \[停用\]，然後按一下 \[確定\]。 7. 按兩次 \[確定\] 回到 Internet Explorer。注意：在網際網路和近端內部網路安全性區域中停用動態指令碼，可能會導致部分網站無法正確運作。如果變更這項設定之後，您在使用網站時遇到問題，而又確定該網站安全無虞能放心使用，便可將該網站加入信任的網站清單中。這樣就能讓網站正確運作。因應措施的影響。執行動態指令碼前先提示的設定會產生副作用。許多網際網路及內部網路的網站使用動態指令碼提供額外的功能。例如，線上電子商務網站或銀行網站會利用動態指令碼提供功能表、訂單、甚至是帳戶明細。執行動態指令碼前先提示屬於通用設定，會影響所有網際網路及內部網路網站。使用這個因應措施的話，您會時常收到提示。每次出現提示時，如果您覺得可以信任該網站，請按一下 \[是\] 執行動態指令碼處理。如果您不要收到這些網站的提示，請改用「將信任的網站加入 Internet Explorer \[信任的網站\] 區域」的步驟。將信任的網站加入 Internet Explorer \[信任的網站\] 區域。當您完成設定，使 Internet Explorer 在網際網路區域及近端內部網路區域執行 ActiveX 控制項及動態指令碼處理前會顯示提示之後，即可將信任的網站加入 Internet Explorer \[信任的網站\] 區域。之後您就可以依照平時習慣使用信任的網站，同時預防不信任網站的這類攻擊。我們建議您只將信任的網站加入 \[信任的網站\] 區域。若要如此做，請執行下列步驟： 1. 在 Internet Explorer 中，依序按一下 \[工具\] 及 \[網際網路選項\]，然後按一下 \[安全性\] 索引標籤。 2. 在 \[請選擇網頁內容區域來指定它的安全性設定\] 方塊中，按一下 \[信任的網站\]，然後按 \[網站\]。 3. 如果您要加入的網站不需要加密通道，請按一下滑鼠清除 \[此區域內的所有網站需要伺服器驗證 (https:)\] 核取方塊。 4. 在 \[將此網站加到該區域\] 方塊中，鍵入信任網站的 URL，然後按一下 \[新增\]。 5. 為每一個要加入此區域的網站重複以上步驟。 6. 按兩次 \[確定\] 接受所有變更，回到 Internet Explorer。注意：您可以加入任何您相信不會對您的系統進行惡意動作的網站。建議您加入 *\.windowsupdate.microsoft.com 與 \.update.microsoft.com* 這兩個網站。這些網站提供各項更新，並需要 ActiveX 控制項才能安裝更新。 #### 虛擬函式表損毀遠端執行程式碼弱點 - CVE-2011-2001 的常見問題集這個弱點的範圍為何？這是遠端執行程式碼的弱點。成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。系統上帳戶使用者權限較低的使用者，其受影響的程度比擁有系統管理權限的使用者要小。造成這個弱點的原因為何？當 Internet Explorer 嘗試存取已損毀的虛擬函式表時，可能會允許攻擊者可以透過登入使用者的權限層級執行任意程式碼。攻擊者可能會利用這項弱點採取什麼行動？成功利用此弱點的攻擊者可以取得與登入使用者相同的使用者權限。如果使用者以系統管理的使用者權限登入，成功利用此弱點的攻擊者可以取得受影響系統的完整控制權。攻擊者接下來將能安裝程式，檢視、變更或刪除資料，或建立具有完整使用者權限的新帳戶。攻擊者如何利用這項弱點？攻擊者可以針對這個經由 Internet Explorer 引起的弱點來設計並架設蓄意製作的網站，然後引誘使用者檢視該網站。一名攻擊者也可以嵌入一個 ActiveX 控制項，該控制項在內含 IE 轉譯引擎的應用程式或 Microsoft Office 文件中標示為「安全的初始化」。攻擊者也可能利用受侵害的網站，以及接受或裝載使用者提供內容或廣告的網站。這些網站可能含有經過蓄意製作並利用此弱點的內容。但是，攻擊者無法強迫使用者檢視受攻擊者控制的內容，而是引誘使用者自行前往。一般的做法是設法讓使用者按一下電子郵件訊息或即時訊息中通往攻擊者網站的連結，或開啟經由電子郵件傳送的附件。因為這個弱點而承受風險的主要系統有哪些？常使用 Internet Explorer 的系統 (例如工作站或終端伺服器) 的風險最大。我用的是適用於 Windows Server 2003、Windows Server 2008 或 Windows Server 2008 R2 的 Internet Explorer。這樣是否會減輕此弱點的影響？是。依照預設，Windows Server 2003、Windows Server 2008 和 Windows Server 2008 R2 上的 Internet Explorer 會以稱為[增強式安全性設定](https://technet.microsoft.com/en-us/library/dd883248(ws.10).aspx)的受限制模式執行。增強式安全性設定是一組預先設定好的 Internet Explorer 設定，可以降低使用者或系統管理員在伺服器下載及執行蓄意製作之網頁內容的可能性。對於您尚未新增至 Internet Explorer \[信任的網站\] 區域的網站，這是一種緩和因素。更新的作用何在？此更新會修改 Internet Explorer 處理記憶體中物件的方式，藉此解決此弱點。當安全性公告發行時，這項弱點是否已揭發出來？否。Microsoft 是經由協同合作的來源接獲有關這項弱點的訊息。當本安全性公告發行時，Microsoft 是否已接獲任何消息，指出這項弱點已遭有心人士利用？否。當本安全性公告初次發行時，Microsoft 尚未接到任何有關本弱點已公開用來攻擊客戶的消息。 ### 更新資訊偵測與部署工具及指南 -------------------- 資訊安全中心管理您必須部署到您組織中的伺服器、桌上型電腦及行動系統的軟體和安全性更新。如需更多資訊，請參閱 [TechNet 更新管理中心](https://go.microsoft.com/fwlink/?linkid=69903) (英文)。[Microsoft TechNet 資訊安全技術中心網站](https://go.microsoft.com/fwlink/?linkid=21132)提供了有關 Microsoft 產品安全性的其他資訊。安全性更新可從 [Microsoft Update](https://go.microsoft.com/fwlink/?linkid=40747) 以及 [Windows Update](https://go.microsoft.com/fwlink/?linkid=21130) 取得。安全性更新也可以從 [Microsoft 下載中心](https://go.microsoft.com/fwlink/?linkid=21129)取得。您也可以利用「安全性更新」("security update") 關鍵字搜尋輕易地找到安全性更新。最後，您可以從 [Microsoft Update Catalog](https://go.microsoft.com/fwlink/?linkid=96155) 下載安全性更新。Microsoft Update Catalog 提供透過 Windows Update 及 Microsoft Update 所公佈內容的搜尋式目錄，包括安全性更新、驅動程式和 Service Pack。只要以安全性公告編號 (例如：MS07-036) 執行搜尋，您就可新增所有適用的更新到置物籃 (包括同一項更新的不同語言)，再下載到您自選的資料夾中。如需更多關於 Microsoft Update Catalog 的相關資訊，請參閱 [Microsoft Update Catalog 常見問題集](https://go.microsoft.com/fwlink/?linkid=97900)。偵測與部署指南 Microsoft 針對安全性更新提供偵測和部署指南。本指南所含之建議和資訊，能幫助 IT 專業人員瞭解如何使用用於安全性更新的偵測和部署的各種工具。如需更多資訊，請參閱 [Microsoft 知識庫文件編號 961747](https://support.microsoft.com/kb/961747)。 Microsoft Baseline Security Analyzer Microsoft Baseline Security Analyzer (MBSA) 能讓系統管理員掃描本機和遠端系統，偵查任何缺少安全性更新以及一般安全性設定錯誤的狀況。如需更多有關 MBSA 的資訊，請造訪 [Microsoft Baseline Security Analyzer](https://www.microsoft.com/technet/security/tools/mbsahome.mspx)。以下表格提供此安全性更新的 MBSA 偵測摘要。 \| 軟體 \| MBSA \| \|----------------------------------------------------------------------------------------------------------------\|------\| \| Windows XP Service Pack 3 \| 是 \| \| Windows XP Professional x64 Edition Service Pack 2 \| 是 \| \| Windows Server 2003 Service Pack 2 \| 是 \| \| Windows Server 2003 x64 Edition Service Pack 2 \| 是 \| \| 適用於 Itanium 型系統的 Windows Server 2003 SP2 \| 是 \| \| Windows Vista Service Pack 2 \| 是 \| \| Windows Vista x64 Edition Service Pack 2 \| 是 \| \| 適用於 32 位元系統的 Windows Server 2008 Service Pack 2 \| 是 \| \| 適用於 x64 型系統的 Windows Server 2008 Service Pack 2 \| 是 \| \| 適用於 Itanium 型系統的 Windows Server 2008 Service Pack 2 \| 是 \| \| 適用於 32 位元系統的 Windows 7 和適用於 32 位元系統的 Windows 7 Service Pack 1 \| 是 \| \| 適用於 x64 型系統的 Windows 7 和適用於 x64 型系統的 Windows 7 Service Pack 1 \| 是 \| \| 適用於 x64 型系統的 Windows Server 2008 R2 和適用於 x64 型系統的 Windows Server 2008 R2 Service Pack 1 \| 是 \| \| 適用於 Itanium 型系統的 Windows Server 2008 R2 和適用於 Itanium 型系統的 Windows Server 2008 R2 Service Pack 1 \| 是 \| 注意：客戶若使用最新版 MBSA、Microsoft Update 和 Windows Server Update Services 所不支援的舊版軟體，請造訪 [Microsoft Baseline Security Analyzer](https://www.microsoft.com/technet/security/tools/mbsahome.mspx) 並參考＜舊版產品支援＞章節，了解如何以舊版工具建立完整的安全性更新偵測方式。 Windows Server Update Services Windows Server Update Services (WSUS) 可讓資訊技術管理員將最新的 Microsoft 產品更新部署到執行 Windows 作業系統的電腦。如需更多關於利用 Windows Server Update Services 部署安全性更新的資訊，請參閱 TechNet 文章：[Windows Server Update Services](https://technet.microsoft.com/en-us/wsus/default.aspx) (英文)。 Systems Management Server 以下表格提供本安全性更新的 SMS 偵測與部署摘要。 \| 軟體 \| 具備 ITMU 的 SMS 2003 \| Configuration Manager 2007 \| \|----------------------------------------------------------------------------------------------------------------\|-----------------------\|----------------------------\| \| Windows XP Service Pack 3 \| 是 \| 是 \| \| Windows XP Professional x64 Edition Service Pack 2 \| 是 \| 是 \| \| Windows Server 2003 Service Pack 2 \| 是 \| 是 \| \| Windows Server 2003 x64 Edition Service Pack 2 \| 是 \| 是 \| \| 適用於 Itanium 型系統的 Windows Server 2003 SP2 \| 是 \| 是 \| \| Windows Vista Service Pack 2 \| 是 \| 是 \| \| Windows Vista x64 Edition Service Pack 2 \| 是 \| 是 \| \| 適用於 32 位元系統的 Windows Server 2008 Service Pack 2 \| 是 \| 是 \| \| 適用於 x64 型系統的 Windows Server 2008 Service Pack 2 \| 是 \| 是 \| \| 適用於 Itanium 型系統的 Windows Server 2008 Service Pack 2 \| 是 \| 是 \| \| 適用於 32 位元系統的 Windows 7 和適用於 32 位元系統的 Windows 7 Service Pack 1 \| 是 \| 是 \| \| 適用於 x64 型系統的 Windows 7 和適用於 x64 型系統的 Windows 7 Service Pack 1 \| 是 \| 是 \| \| 適用於 x64 型系統的 Windows Server 2008 R2 和適用於 x64 型系統的 Windows Server 2008 R2 Service Pack 1 \| 是 \| 是 \| \| 適用於 Itanium 型系統的 Windows Server 2008 R2 和適用於 Itanium 型系統的 Windows Server 2008 R2 Service Pack 1 \| 是 \| 是 \| 注意：Microsoft 已於 2011 年 4 月 12 日停止支援 SMS 2.0。對於 SMS 2003，Microsoft 亦於 2011 年 4 月 12 日停止支援安全性更新盤點工具 (SUIT)。建議客戶升級為 [System Center Configuration Manager 2007](https://technet.microsoft.com/en-us/library/bb735860.aspx)。繼續使用 SMS 2003 Service Pack 3 的客戶，亦可選用 [Microsoft Updates 盤點工具](https://technet.microsoft.com/zh-tw/sms/bb676783.aspx) (ITMU)。 SMS 2003 可使用 Microsoft Update SMS 2003 盤點工具 (ITMU) 來偵測由 [Microsoft Update](https://go.microsoft.com/fwlink/?linkid=40747) 所提供，並由 [Windows Server Update Services](https://go.microsoft.com/fwlink/?linkid=50120) 支援的安全性更新。如需 SMS 2003 ITMU 的詳細資訊，請參閱 [Microsoft Updates SMS 2003 盤點工具](https://technet.microsoft.com/zh-tw/sms/bb676783.aspx) (英文)。如需更多關於 SMS 掃描工具的資訊，請參閱 [SMS 2003 軟體更新掃描工具](https://technet.microsoft.com/en-us/sms/bb676786.aspx) (英文)。另請參閱[適用於 Systems Management Server 2003 的下載](https://technet.microsoft.com/en-us/sms/bb676766.aspx) (英文)。 System Center Configuration Manager 2007 使用 WSUS 3.0 來偵測更新。如需更多關於 Configuration Manager 2007 軟體更新管理的資訊，請造訪 [System Center Configuration Manager 2007](https://technet.microsoft.com/en-us/library/bb735860.aspx) 網站。如需有關 SMS 的詳細資訊，請造訪 [SMS 網站。](https://go.microsoft.com/fwlink/?linkid=21158) 如需瞭解詳細相關資訊，請參閱 [Microsoft 知識庫文件編號 910723](https://support.microsoft.com/kb/910723)：每月發行之偵測與部署指導文件的摘要清單。 Update Compatibility Evaluator 和 Application Compatibility Toolkit 更新時常會寫入您應用程式執行所需的相同檔案和登錄設定。這可能會觸發不相容性，而拉長部署安全性更新的時間。您可以使用 [Application Compatibility Toolkit](https://www.microsoft.com/download/details.aspx?familyid=24da89e9-b581-47b0-b45e-492dd6da2971&displaylang=en) 隨附的 [Update Compatibility Evaluator](https://technet2.microsoft.com/windowsvista/en/library/4279e239-37a4-44aa-aec5-4e70fe39f9de1033.mspx?mfr=true) 元件，針對所安裝的應用程式簡化其測試和驗證 Windows 更新的過程。 Application Compatibility Toolkit (ACT) 包含必要的工具和文件，可讓您在環境中部署 Microsoft Windows Vista、Windows Update、Microsoft 安全性更新或新版 Windows Internet Explorer 之前，評估及減輕應用程式相容性問題。安全性更新部署 -------------- 受影響的軟體如需有關您使用系統的特定安全性更新資訊，請按下適當的連結： #### Windows XP (所有版本) 參考表下表包含此軟體的安全性更新資訊。您可以在本節的＜部署資訊＞小節中找到其他資訊。 <p> </p> <table style="border:1px solid black;"> <colgroup> <col width="50%" /> <col width="50%" /> </colgroup> <tbody> <tr class="odd"> <td style="border:1px solid black;"><strong>未來將包含於 Service Pack 中的內容</strong></td> <td style="border:1px solid black;">此問題的更新將包含在以後的 Service Pack 或更新彙總套件中</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>部署</strong></td> <td style="border:1px solid black;"></td> </tr> <tr class="odd"> <td style="border:1px solid black;">在沒有使用者介入的情況下安裝</td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows XP 的 Internet Explorer 6：<br /> WindowsXP-KB2586448-x86-ENU.exe /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 版本 Windows XP 的 Internet Explorer 6：<br /> WindowsServer2003.WindowsXP-KB2586448-x64-ENU.exe /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows XP 的 Internet Explorer 7：<br /> IE7-WindowsXP-KB2586448-x86-ENU.exe /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 版本 Windows XP 的 Internet Explorer 7：<br /> IE7-WindowsServer2003.WindowsXP-KB2586448-x64-ENU.exe /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows XP 的 Internet Explorer 8：<br /> IE8-WindowsXP-KB2586448-x86-ENU.exe /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 版本 Windows XP 的 Internet Explorer 8：<br /> IE8-WindowsServer2003.WindowsXP-KB2586448-x64-ENU.exe /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;">在不重新啟動的情況下安裝</td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows XP 的 Internet Explorer 6：<br /> WindowsXP-KB2586448-x86-ENU.exe /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 版本 Windows XP 的 Internet Explorer 6：<br /> WindowsServer2003.WindowsXP-KB2586448-x64-ENU.exe /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows XP 的 Internet Explorer 7：<br /> IE7-WindowsXP-KB2586448-x86-ENU.exe /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 版本 Windows XP 的 Internet Explorer 7：<br /> IE7-WindowsServer2003.WindowsXP-KB2586448-x64-ENU.exe /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows XP 的 Internet Explorer 8：<br /> IE8-WindowsXP-KB2586448-x86-ENU.exe /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 版本 Windows XP 的 Internet Explorer 8：<br /> IE8-WindowsServer2003.WindowsXP-KB2586448-x64-ENU.exe /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;">更新記錄檔</td> <td style="border:1px solid black;">適用於所有 Windows XP 支援版本的 Internet Explorer 6：<br /> KB2586448.log</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有 Windows XP 支援版本的 Internet Explorer 7：<br /> KB2586448-IE7.log</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有 Windows XP 支援版本的 Internet Explorer 8：<br /> KB2586448-IE8.log</td> </tr> <tr class="even"> <td style="border:1px solid black;">詳細資訊</td> <td style="border:1px solid black;">請參閱＜偵測與部署工具及指南＞小節</td> </tr> <tr class="odd"> <td style="border:1px solid black;"><strong>重新開機需求</strong></td> <td style="border:1px solid black;"></td> </tr> <tr class="even"> <td style="border:1px solid black;">需要重新開機？</td> <td style="border:1px solid black;">是，套用此安全性更新之後，您必須重新啟動系統。</td> </tr> <tr class="odd"> <td style="border:1px solid black;">Hotpatching</td> <td style="border:1px solid black;">不適用</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>移除資訊</strong></td> <td style="border:1px solid black;">適用於所有 Windows XP 支援版本的 Internet Explorer 6：使用 [控制台] 中的 [新增或移除程式] 工具，或是 %Windir%\$NTUninstallKB2586448$\Spuninst 資料夾中的 Spuninst.exe 公用程式</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有 Windows XP 支援版本的 Internet Explorer 7：<br /> 使用 [控制台] 中的 [新增或移除程式] 工具，或 %Windir%\ie7updates\KB2586448-IE7\spuninst 資料夾中的 Spuninst.exe 公用程式</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有 Windows XP 支援版本的 Internet Explorer 8：<br /> 使用 [控制台] 中的 [新增或移除程式] 工具，或 %Windir%\ie8updates\KB2586448-IE8\spuninst 資料夾中的 Spuninst.exe 公用程式</td> </tr> <tr class="odd"> <td style="border:1px solid black;"><strong>檔案資訊</strong></td> <td style="border:1px solid black;">請參閱 <a href="https://support.microsoft.com/kb/2586448">Microsoft 知識庫文件編號 2586448</a></td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>登錄機碼驗證</strong></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows XP 的 Internet Explorer 6：<br /> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2586448\Filelist</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 版本 Windows XP 的 Internet Explorer 6：<br /> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2586448\Filelist</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows XP 的 Internet Explorer 7：<br /> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP0\KB2586448-IE7\Filelist</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 版本 Windows XP 的 Internet Explorer 7：<br /> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP0\KB2586448-IE7\Filelist</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows XP 的 Internet Explorer 8：<br /> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP0\KB2586448-IE8\Filelist</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 版本 Windows XP 的 Internet Explorer 8：<br /> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP0\KB2586448-IE8\Filelist</td> </tr> </tbody> </table> 注意：對於受支援版本的 Windows XP Professional x64 Edition 的更新也適用於受支援版本的 Windows Server 2003 x64 Edition。 #### 部署資訊安裝更新程式當您安裝本安全性更新時，安裝程式會檢查系統上要更新的檔案先前是否曾用 Microsoft Hotfix 進行更新。如果您先前曾經安裝 Hotfix 更新其中一個檔案，安裝程式會將 RTMQFE、SP1QFE 或 SP2QFE 檔案複製到您的系統中。否則，安裝程式會將 RTMGDR、SP1GDR 或 SP2GDR 檔案複製到您的系統中。安全性更新可能沒有包含這些檔案的全部變種。如需更多有關這種行為的資訊，請參閱 [Microsoft 知識庫文件編號 824994](https://support.microsoft.com/kb/824994)。如需更多有關安裝程式的資訊，請參閱 [Microsoft 知識庫文件編號 832475](https://support.microsoft.com/kb/832475)。如需更多關於出現於本公告中術語的相關資訊 (如 hotfix)，請參閱 [Microsoft 知識庫文件編號 824684](https://support.microsoft.com/kb/824684)。這個安全性更新支援以下的安裝參數。 <p> </p> <table style="border:1px solid black;"> <caption> 支援的安全性更新安裝參數 </caption> <tr class="thead"> <th style="border:1px solid black;" > 參數 </th> <th style="border:1px solid black;" > 描述 </th> </tr> <tr> <td style="border:1px solid black;"> /help </td> <td style="border:1px solid black;"> 顯示命令列選項。 </td> </tr> <tr> <th style="border:1px solid black;" colspan="2"> 安裝模式 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /passive </td> <td style="border:1px solid black;"> 自動安裝模式。不需使用者互動，但會顯示安裝狀態。如果安裝結束時需要重新啟動，則會向使用者顯示對話方塊，其中的計時器會警告將在 30 秒後重新啟動電腦。 </td> </tr> <tr> <td style="border:1px solid black;"> /quiet </td> <td style="border:1px solid black;"> 無訊息模式。此模式與自動安裝模式相同，但是不會顯示狀態或錯誤訊息。 </td> </tr> <tr> <th style="border:1px solid black;" colspan="2"> 重新啟動選項 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /norestart </td> <td style="border:1px solid black;"> 安裝完成後不重新啟動。 </td> </tr> <tr> <td style="border:1px solid black;"> /forcerestart </td> <td style="border:1px solid black;"> 安裝完成後重新啟動電腦，並強制在關機時關閉其他應用程式，而且不會先儲存已開啟的檔案。 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /warnrestart\[:x\] </td> <td style="border:1px solid black;"> 出現含有計時器的對話方塊，警告使用者將在 x 秒後重新啟動電腦 (預設值是 30 秒)。旨在配合 /quiet 參數或 /passive 參數使用。 </td> </tr> <tr> <td style="border:1px solid black;"> /promptrestart </td> <td style="border:1px solid black;"> 顯示對話方塊，提示本機使用者允許重新啟動。 </td> </tr> <tr> <th style="border:1px solid black;" colspan="2"> 特殊選項 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /overwriteoem </td> <td style="border:1px solid black;"> 不先提示，直接覆寫 OEM 檔案。 </td> </tr> <tr> <td style="border:1px solid black;"> /nobackup </td> <td style="border:1px solid black;"> 不備份解除安裝所需的檔案。 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /forceappsclose </td> <td style="border:1px solid black;"> 當電腦關機時，強制其他程式結束。 </td> </tr> <tr> <td style="border:1px solid black;"> /log:path </td> <td style="border:1px solid black;"> 允許安裝記錄檔案重新導向。 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /integrate:path </td> <td style="border:1px solid black;"> 將更新程式整合到 Windows 原始檔。這些檔案位於參數中指定的路徑。 </td> </tr> <tr> <td style="border:1px solid black;"> /extract\[:path\] </td> <td style="border:1px solid black;"> 不啟動安裝程式，僅解壓縮檔案。 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /ER </td> <td style="border:1px solid black;"> 啟用延伸的錯誤報告。 </td> </tr> <tr> <td style="border:1px solid black;"> /verbose </td> <td style="border:1px solid black;"> 啟用詳細資訊記錄。在安裝時建立 %Windir%\\CabBuild.log。此記錄檔會詳細說明複製的檔案。使用這個參數可能會使安裝速度慢很多。 </td> </tr> </table> 注意：您可以在同一個命令中合併使用這些參數。為符合回溯相容性，安全性更新程式也支援舊版安裝程式使用的安裝參數。如需有關受支援安裝參數的詳細資訊，請參閱 [Microsoft 知識庫文件編號 262841](https://support.microsoft.com/kb/262841)。移除更新這個安全性更新支援以下的安裝參數。 <p> </p> <table style="border:1px solid black;"> <caption> 支援的 Spuninst.exe 參數 </caption> <tr class="thead"> <th style="border:1px solid black;" > 參數 </th> <th style="border:1px solid black;" > 描述 </th> </tr> <tr> <td style="border:1px solid black;"> /help </td> <td style="border:1px solid black;"> 顯示命令列選項。 </td> </tr> <tr> <th style="border:1px solid black;" colspan="2"> 安裝模式 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /passive </td> <td style="border:1px solid black;"> 自動安裝模式。不需使用者互動，但會顯示安裝狀態。如果安裝結束時需要重新啟動，則會向使用者顯示對話方塊，其中的計時器會警告將在 30 秒後重新啟動電腦。 </td> </tr> <tr> <td style="border:1px solid black;"> /quiet </td> <td style="border:1px solid black;"> 無訊息模式。此模式與自動安裝模式相同，但是不會顯示狀態或錯誤訊息。 </td> </tr> <tr> <th style="border:1px solid black;" colspan="2"> 重新啟動選項 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /norestart </td> <td style="border:1px solid black;"> 安裝完成後不重新啟動 </td> </tr> <tr> <td style="border:1px solid black;"> /forcerestart </td> <td style="border:1px solid black;"> 安裝完成後重新啟動電腦，並強制在關機時關閉其他應用程式，而且不會先儲存已開啟的檔案。 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /warnrestart\[:x\] </td> <td style="border:1px solid black;"> 出現含有計時器的對話方塊，警告使用者將在 x 秒後重新啟動電腦 (預設值是 30 秒)。旨在配合 /quiet 參數或 /passive 參數使用。 </td> </tr> <tr> <td style="border:1px solid black;"> /promptrestart </td> <td style="border:1px solid black;"> 顯示對話方塊，提示本機使用者允許重新啟動。 </td> </tr> <tr> <th style="border:1px solid black;" colspan="2"> 特殊選項 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /forceappsclose </td> <td style="border:1px solid black;"> 當電腦關機時，強制其他程式結束。 </td> </tr> <tr> <td style="border:1px solid black;"> /log:path </td> <td style="border:1px solid black;"> 允許安裝記錄檔案重新導向。 </td> </tr> </table> 確認已經套用更新 - Microsoft Baseline Security Analyzer 您可以使用 Microsoft Baseline Security Analyzer (MBSA) 工具確認受影響系統上是否已經套用安全性更新程式。如需詳細資訊，請參閱本公告前段的＜偵測與部署工具及指南＞一節。 - 檔案版本驗證由於 Microsoft Windows 的版本眾多，您電腦上實際執行的步驟可能會與此處描述的不同。如遇到不同的狀況，請參閱產品的說明文件以完成這些步驟。 1. 按一下 \[開始\]，然後按一下 \[搜尋\]。 2. 在 \[搜尋結果\] 窗格中，在 \[搜尋小幫手\] 下按一下 \[所有檔案和資料夾\]。 3. 在 \[部份或完整的檔案名稱\] 方塊中，輸入適當檔案資訊表中的檔案名稱，再按一下 \[搜尋\]。 4. 在檔案清單中，用滑鼠右鍵按一下適當檔案資訊表中的某個檔案名稱，再按 \[內容\]。注意：視系統所安裝的作業系統或程式的版本而定，檔案資訊表中列出的檔案未必會全部安裝。 5. 在 \[版本\] 索引標籤上，比較檔案版本與適當檔案資訊表中記錄的版本，判斷您系統上安裝的檔案版本。注意：在安裝時，檔案版本以外的屬性可能會變更。若要驗證是否成功套用更新程式，利用檔案資訊表比對其他檔案屬性並不是妥當的做法。此外，在某些情況下，檔案的名稱在安裝時可能會有所變更。如果缺少檔案或版本資訊，請採用其他可用的方法來驗證更新程式的安裝情形。 - 登錄機碼驗證您也可以查看本節「參考表」中所列的登錄機碼，確認此安全性更新所安裝的檔案。這些登錄機碼可能未包含完整的安裝檔案清單。而且，當系統管理員或 OEM 將安全性更新整合或匯集到 Windows 安裝原始檔時，可能無法正確建立這些登錄機碼。 #### Windows Server 2003 (所有版本) 參考表下表包含此軟體的安全性更新資訊。您可以在本節的＜部署資訊＞小節中找到其他資訊。 <p> </p> <table style="border:1px solid black;"> <tbody> <tr class="odd"> <td style="border:1px solid black;"><strong>未來將包含於 Service Pack 中的內容</strong></td> <td style="border:1px solid black;">此問題的更新將包含在以後的 Service Pack 或更新彙總套件中</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>部署</strong></td> <td style="border:1px solid black;"></td> </tr> <tr class="odd"> <td style="border:1px solid black;">在沒有使用者介入的情況下安裝</td> <td style="border:1px solid black;">所有受支援 32 位元版本 Windows Server 2003 的 Internet Explorer 6：<br /> WindowsServer2003-KB2586448-x86-ENU.exe /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 版本 Windows Server 2003 的 Internet Explorer 6：<br /> WindowsServer2003.WindowsXP-KB2586448-x64-ENU.exe /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 Itanium 版本 Windows Server 2003 的 Internet Explorer 6：<br /> WindowsServer2003-KB2586448-ia64-ENU.exe /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 32 位元版本 Windows Server 2003 的 Internet Explorer 7：<br /> IE7-WindowsServer2003-KB2586448-x86-ENU.exe /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 版本 Windows Server 2003 的 Internet Explorer 7：<br /> IE7-WindowsServer2003.WindowsXP-KB2586448-x64-ENU.exe /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 Itanium 版本 Windows Server 2003 的 Internet Explorer 7：<br /> IE7-WindowsServer2003-KB2586448-ia64-ENU.exe /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 32 位元版本 Windows Server 2003 的 Internet Explorer 8：<br /> IE8-WindowsServer2003-KB2586448-x86-ENU.exe /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 版本 Windows Server 2003 的 Internet Explorer 8：<br /> IE8-WindowsServer2003.WindowsXP-KB2586448-x64-ENU.exe /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;">在不重新啟動的情況下安裝</td> <td style="border:1px solid black;">所有受支援 32 位元版本 Windows Server 2003 的 Internet Explorer 6：<br /> WindowsServer2003-KB2586448-x86-ENU.exe /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 版本 Windows Server 2003 的 Internet Explorer 6：<br /> WindowsServer2003.WindowsXP-KB2586448-x64-ENU.exe /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 Itanium 版本 Windows Server 2003 的 Internet Explorer 6：<br /> WindowsServer2003-KB2586448-ia64-ENU.exe /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 32 位元版本 Windows Server 2003 的 Internet Explorer 7：<br /> IE7-WindowsServer2003-KB2586448-x86-ENU.exe /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 版本 Windows Server 2003 的 Internet Explorer 7：<br /> IE7-WindowsServer2003.WindowsXP-KB2586448-x64-ENU.exe /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 Itanium 版本 Windows Server 2003 的 Internet Explorer 7：<br /> IE7-WindowsServer2003-KB2586448-ia64-ENU.exe /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 32 位元版本 Windows Server 2003 的 Internet Explorer 8：<br /> IE8-WindowsServer2003-KB2586448-x86-ENU.exe /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 版本 Windows Server 2003 的 Internet Explorer 8：<br /> IE8-WindowsServer2003.WindowsXP-KB2586448-x64-ENU.exe /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;">更新記錄檔</td> <td style="border:1px solid black;">所有受支援 32 位元版本、x64 版本和 Itanium 版本 Windows Server 2003 的 Internet Explorer 6：<br /> KB2586448.log</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 32 位元版本、x64 版本和 Itanium 版本 Windows Server 2003 的 Internet Explorer 7：<br /> KB2586448-IE7.log</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本和 x64 版本 Windows Server 2003 的 Internet Explorer 8：<br /> KB2586448-IE8.log</td> </tr> <tr class="even"> <td style="border:1px solid black;">詳細資訊</td> <td style="border:1px solid black;">請參閱＜偵測與部署工具及指南＞小節</td> </tr> <tr class="odd"> <td style="border:1px solid black;"><strong>重新開機需求</strong></td> <td style="border:1px solid black;"></td> </tr> <tr class="even"> <td style="border:1px solid black;">需要重新開機？</td> <td style="border:1px solid black;">是，套用此安全性更新之後，您必須重新啟動系統。</td> </tr> <tr class="odd"> <td style="border:1px solid black;">HotPatching</td> <td style="border:1px solid black;">本安全性更新不支援 HotPatching。如需關於 Hotpatching 的詳細資訊，請參閱 <a href="https://support.microsoft.com/kb/897341">Microsoft 知識庫文件編號 897341</a>。</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>移除資訊</strong></td> <td style="border:1px solid black;">所有受支援 32 位元版本、x64 版本和 Itanium 版本 Windows Server 2003 的 Internet Explorer 6：<br /> 使用 [控制台] 中的 [新增或移除程式] 工具，或 %Windir%\$NTUninstallKB2586448$\Spuninst 資料夾中的 Spuninst.exe 公用程式</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 32 位元版本、x64 版本和 Itanium 版本 Windows Server 2003 的 Internet Explorer 7：<br /> 使用 [控制台] 中的 [新增或移除程式] 工具，或 %Windir%\ie7updates\KB2586448-IE7\spuninst 資料夾中的 Spuninst.exe 公用程式</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本和 x64 版本 Windows Server 2003 的 Internet Explorer 8：<br /> 使用 [控制台] 中的 [新增或移除程式] 工具，或 %Windir%\ie8updates\KB2586448-IE8\spuninst 資料夾中的 Spuninst.exe 公用程式</td> </tr> <tr class="odd"> <td style="border:1px solid black;"><strong>檔案資訊</strong></td> <td style="border:1px solid black;">請參閱 <a href="https://support.microsoft.com/kb/2586448">Microsoft 知識庫文件編號 2586448</a></td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>登錄機碼驗證</strong></td> <td style="border:1px solid black;">所有受支援 32 位元版本、x64 版本和 Itanium 版本 Windows Server 2003 的 Internet Explorer 6：<br /> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2586448\Filelist</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 32 位元版本、x64 版本和 Itanium 版本 Windows Server 2003 的 Internet Explorer 7：<br /> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP0\KB2586448-IE7\Filelist</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本和 x64 版本 Windows Server 2003 的 Internet Explorer 8：<br /> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP0\KB2586448-IE8\Filelist</td> </tr> </tbody> </table> 注意：適用於受支援版本的 Windows Server 2003 x64 Edition 的更新也適用於受支援版本的 Windows XP Professional x64 Edition。 #### 部署資訊安裝更新程式當您安裝本安全性更新時，安裝程式會檢查系統上要更新的檔案先前是否曾用 Microsoft Hotfix 進行更新。如果您先前曾經安裝 Hotfix 更新其中一個檔案，安裝程式會將 RTMQFE、SP1QFE 或 SP2QFE 檔案複製到您的系統中。否則，安裝程式會將 RTMGDR、SP1GDR 或 SP2GDR 檔案複製到您的系統中。安全性更新可能沒有包含這些檔案的全部變種。如需更多有關這種行為的資訊，請參閱 [Microsoft 知識庫文件編號 824994](https://support.microsoft.com/kb/824994)。如需更多有關安裝程式的資訊，請參閱 [Microsoft 知識庫文件編號 832475](https://support.microsoft.com/kb/832475)。如需更多關於出現於本公告中術語的相關資訊 (如 hotfix)，請參閱 [Microsoft 知識庫文件編號 824684](https://support.microsoft.com/kb/824684)。這個安全性更新支援以下的安裝參數。 <p> </p> <table style="border:1px solid black;"> <caption> 支援的安全性更新安裝參數 </caption> <tr class="thead"> <th style="border:1px solid black;" > 參數 </th> <th style="border:1px solid black;" > 描述 </th> </tr> <tr> <td style="border:1px solid black;"> /help </td> <td style="border:1px solid black;"> 顯示命令列選項。 </td> </tr> <tr> <th style="border:1px solid black;" colspan="2"> 安裝模式 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /passive </td> <td style="border:1px solid black;"> 自動安裝模式。不需使用者互動，但會顯示安裝狀態。如果安裝結束時需要重新啟動，則會向使用者顯示對話方塊，其中的計時器會警告將在 30 秒後重新啟動電腦。 </td> </tr> <tr> <td style="border:1px solid black;"> /quiet </td> <td style="border:1px solid black;"> 無訊息模式。此模式與自動安裝模式相同，但是不會顯示狀態或錯誤訊息。 </td> </tr> <tr> <th style="border:1px solid black;" colspan="2"> 重新啟動選項 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /norestart </td> <td style="border:1px solid black;"> 安裝完成後不重新啟動。 </td> </tr> <tr> <td style="border:1px solid black;"> /forcerestart </td> <td style="border:1px solid black;"> 安裝完成後重新啟動電腦，並強制在關機時關閉其他應用程式，而且不會先儲存已開啟的檔案。 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /warnrestart\[:x\] </td> <td style="border:1px solid black;"> 出現含有計時器的對話方塊，警告使用者將在 x 秒後重新啟動電腦 (預設值是 30 秒)。旨在配合 /quiet 參數或 /passive 參數使用。 </td> </tr> <tr> <td style="border:1px solid black;"> /promptrestart </td> <td style="border:1px solid black;"> 顯示對話方塊，提示本機使用者允許重新啟動。 </td> </tr> <tr> <th style="border:1px solid black;" colspan="2"> 特殊選項 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /overwriteoem </td> <td style="border:1px solid black;"> 不先提示，直接覆寫 OEM 檔案。 </td> </tr> <tr> <td style="border:1px solid black;"> /nobackup </td> <td style="border:1px solid black;"> 不備份解除安裝所需的檔案。 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /forceappsclose </td> <td style="border:1px solid black;"> 當電腦關機時，強制其他程式結束。 </td> </tr> <tr> <td style="border:1px solid black;"> /log:path </td> <td style="border:1px solid black;"> 允許安裝記錄檔案重新導向。 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /integrate:path </td> <td style="border:1px solid black;"> 將更新程式整合到 Windows 原始檔。這些檔案位於參數中指定的路徑。 </td> </tr> <tr> <td style="border:1px solid black;"> /extract\[:path\] </td> <td style="border:1px solid black;"> 不啟動安裝程式，僅解壓縮檔案。 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /ER </td> <td style="border:1px solid black;"> 啟用延伸的錯誤報告。 </td> </tr> <tr> <td style="border:1px solid black;"> /verbose </td> <td style="border:1px solid black;"> 啟用詳細資訊記錄。在安裝時建立 %Windir%\\CabBuild.log。此記錄檔會詳細說明複製的檔案。使用這個參數可能會使安裝速度慢很多。 </td> </tr> </table> 注意：您可以在同一個命令中合併使用這些參數。為符合回溯相容性，安全性更新程式也支援舊版安裝程式使用的安裝參數中的許多參數。如需有關受支援安裝參數的詳細資訊，請參閱 [Microsoft 知識庫文件編號 262841](https://support.microsoft.com/kb/262841)。移除更新這個安全性更新支援以下的安裝參數。 <p> </p> <table style="border:1px solid black;"> <caption> 支援的 Spuninst.exe 參數 </caption> <tr class="thead"> <th style="border:1px solid black;" > 參數 </th> <th style="border:1px solid black;" > 描述 </th> </tr> <tr> <td style="border:1px solid black;"> /help </td> <td style="border:1px solid black;"> 顯示命令列選項。 </td> </tr> <tr> <th style="border:1px solid black;" colspan="2"> 安裝模式 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /passive </td> <td style="border:1px solid black;"> 自動安裝模式。不需使用者互動，但會顯示安裝狀態。如果安裝結束時需要重新啟動，則會向使用者顯示對話方塊，其中的計時器會警告將在 30 秒後重新啟動電腦。 </td> </tr> <tr> <td style="border:1px solid black;"> /quiet </td> <td style="border:1px solid black;"> 無訊息模式。此模式與自動安裝模式相同，但是不會顯示狀態或錯誤訊息。 </td> </tr> <tr> <th style="border:1px solid black;" colspan="2"> 重新啟動選項 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /norestart </td> <td style="border:1px solid black;"> 安裝完成後不重新啟動。 </td> </tr> <tr> <td style="border:1px solid black;"> /forcerestart </td> <td style="border:1px solid black;"> 安裝完成後重新啟動電腦，並強制在關機時關閉其他應用程式，而且不會先儲存已開啟的檔案。 </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /warnrestart\[:x\] </td> <td style="border:1px solid black;"> 出現含有計時器的對話方塊，警告使用者將在 x 秒後重新啟動電腦 (預設值是 30 秒)。旨在配合 /quiet 參數或 /passive 參數使用。 </td> </tr> <tr> <td style="border:1px solid black;"> /promptrestart </td> <td style="border:1px solid black;"> 顯示對話方塊，提示本機使用者允許重新啟動。 </td> </tr> <tr> <th style="border:1px solid black;" colspan="2"> 特殊選項 </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> /forceappsclose </td> <td style="border:1px solid black;"> 當電腦關機時，強制其他程式結束。 </td> </tr> <tr> <td style="border:1px solid black;"> /log:path </td> <td style="border:1px solid black;"> 允許安裝記錄檔案重新導向。 </td> </tr> </table> 確認已經套用更新 - Microsoft Baseline Security Analyzer 您可以使用 Microsoft Baseline Security Analyzer (MBSA) 工具確認受影響系統上是否已經套用安全性更新程式。如需詳細資訊，請參閱本公告前段的＜偵測與部署工具及指南＞一節。 - 檔案版本驗證由於 Microsoft Windows 的版本眾多，您電腦上實際執行的步驟可能會與此處描述的不同。如遇到不同的狀況，請參閱產品的說明文件以完成這些步驟。 1. 按一下 \[開始\]，然後按一下 \[搜尋\]。 2. 在 \[搜尋結果\] 窗格中，在 \[搜尋小幫手\] 下按一下 \[所有檔案和資料夾\]。 3. 在 \[部份或完整的檔案名稱\] 方塊中，輸入適當檔案資訊表中的檔案名稱，再按一下 \[搜尋\]。 4. 在檔案清單中，用滑鼠右鍵按一下適當檔案資訊表中的某個檔案名稱，再按 \[內容\]。注意：視系統所安裝的作業系統或程式的版本而定，檔案資訊表中列出的檔案未必會全部安裝。 5. 在 \[版本\] 索引標籤上，比較檔案版本與適當檔案資訊表中記錄的版本，判斷您系統上安裝的檔案版本。注意：在安裝時，檔案版本以外的屬性可能會變更。若要驗證是否成功套用更新程式，利用檔案資訊表比對其他檔案屬性並不是妥當的做法。此外，在某些情況下，檔案的名稱在安裝時可能會有所變更。如果缺少檔案或版本資訊，請採用其他可用的方法來驗證更新程式的安裝情形。 - 登錄機碼驗證您也可以查看本節「參考表」中所列的登錄機碼，確認此安全性更新所安裝的檔案。這些登錄機碼可能未包含完整的安裝檔案清單。而且，當系統管理員或 OEM 將安全性更新整合或匯集到 Windows 安裝原始檔時，可能無法正確建立這些登錄機碼。 #### Windows Vista (所有版本) 參考表下表包含此軟體的安全性更新資訊。您可以在本節的＜部署資訊＞小節中找到其他資訊。 <p> </p> <table style="border:1px solid black;"> <tbody> <tr class="odd"> <td style="border:1px solid black;"><strong>未來將包含於 Service Pack 中的內容</strong></td> <td style="border:1px solid black;">此問題的更新將包含在以後的 Service Pack 或更新彙總套件中</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>部署</strong></td> <td style="border:1px solid black;"></td> </tr> <tr class="odd"> <td style="border:1px solid black;">在沒有使用者介入的情況下安裝</td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows Vista 的 Internet Explorer 7：<br /> Windows6.0-KB2586448-x86.msu /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 版本 Windows Vista 的 Internet Explorer 7：<br /> Windows6.0-KB2586448-x64.msu /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows Vista 的 Internet Explorer 8：<br /> IE8-Windows6.0-KB2586448-x86.msu /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 版本 Windows Vista 的 Internet Explorer 8：<br /> IE8-Windows6.0-KB2586448-x64.msu /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows Vista 的 Internet Explorer 9：<br /> IE9-Windows6.0-KB2586448-x86.msu /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 型版本 Windows Vista 的 Internet Explorer 9：<br /> IE9-Windows6.0-KB2586448-x64.msu /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;">在不重新啟動的情況下安裝</td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows Vista 的 Internet Explorer 7：<br /> Windows6.0-KB2586448-x86.msu /quiet /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 版本 Windows Vista 的 Internet Explorer 7：<br /> Windows6.0-KB2586448-x64.msu /quiet /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows Vista 的 Internet Explorer 8：<br /> IE8-Windows6.0-KB2586448-x86.msu /quiet /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 版本 Windows Vista 的 Internet Explorer 8：<br /> IE8-Windows6.0-KB2586448-x64.msu /quiet /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows Vista 的 Internet Explorer 9：<br /> IE9-Windows6.0-KB2586448-x86.msu /quiet /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 型版本 Windows Vista 的 Internet Explorer 9：<br /> IE9-Windows6.0-KB2586448-x64.msu /quiet /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;">詳細資訊</td> <td style="border:1px solid black;">請參閱＜偵測與部署工具及指南＞小節</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>重新開機需求</strong></td> <td style="border:1px solid black;"></td> </tr> <tr class="odd"> <td style="border:1px solid black;">需要重新開機？</td> <td style="border:1px solid black;">是，套用此安全性更新之後，您必須重新啟動系統。</td> </tr> <tr class="even"> <td style="border:1px solid black;">Hotpatching</td> <td style="border:1px solid black;">不適用</td> </tr> <tr class="odd"> <td style="border:1px solid black;"><strong>移除資訊</strong></td> <td style="border:1px solid black;">WUSA.exe 不支援更新的解除安裝。如要解除安裝 WUSA 所安裝的更新程式，請按一下 [控制台]，然後按一下 [安全性]。在 Windows Update 下，按一下 [檢視安裝的更新] 並從更新清單中選取。</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>檔案資訊</strong></td> <td style="border:1px solid black;">請參閱 <a href="https://support.microsoft.com/kb/2586448">Microsoft 知識庫文件編號 2586448</a></td> </tr> <tr class="odd"> <td style="border:1px solid black;"><strong>登錄機碼驗證</strong></td> <td style="border:1px solid black;"><strong>注意：</strong>登錄機碼不存在，無法驗證此更新是否存在。</td> </tr> </tbody> </table> #### 部署資訊安裝更新程式當您安裝本安全性更新時，安裝程式會檢查系統上要更新的檔案先前是否曾用 Microsoft Hotfix 進行更新。如需更多關於出現於本公告中術語的相關資訊 (如 hotfix)，請參閱 [Microsoft 知識庫文件編號 824684](https://support.microsoft.com/kb/824684)。這個安全性更新支援以下的安裝參數。支援的安全性更新安裝參數 \| 參數 \| 描述 \| \|-------------------\|--------------------------------------------------------------------------------------------\| \| /?, /h, /help \| 顯示受支援參數的說明。 \| \| /quiet \| 不顯示狀態或錯誤訊息。 \| \| /norestart \| 與 /quiet 結合使用時，系統在安裝後將不會重新啟動，即使需要重新啟動以完成安裝時亦如此。 \| 注意：如需 wusa.exe 安裝程式的詳細資訊，請參閱 [Microsoft 知識庫文件編號 934307](https://support.microsoft.com/kb/934307)。確認已經套用更新 - Microsoft Baseline Security Analyzer 您可以使用 Microsoft Baseline Security Analyzer (MBSA) 工具確認受影響系統上是否已經套用安全性更新程式。如需詳細資訊，請參閱本公告前段的＜偵測與部署工具及指南＞一節。 - 檔案版本驗證由於 Microsoft Windows 的版本眾多，您電腦上實際執行的步驟可能會與此處描述的不同。如遇到不同的狀況，請參閱產品的說明文件以完成這些步驟。 1. 按一下 \[開始\]，然後在 \[開始搜尋\] 方塊中輸入更新檔案名稱。 2. 當該檔案出現在 \[程式\] 下方時，在檔案名稱上按一下滑鼠右鍵，然後按一下 \[內容\]。 3. 在 \[一般\] 索引標籤下，將檔案大小與公告 KB 文件提供的檔案資訊表進行比對。注意：視作業系統版本或系統所安裝的程式而定，檔案資訊表中列出的檔案未必會全部安裝。 4. 您也可以按一下 \[詳細資料\] 索引標籤，然後將檔案版本與修改日期等資訊與公告 KB 文件提供的檔案資訊表進行比對。注意：在安裝時，檔案版本以外的屬性可能會變更。若要驗證是否成功套用更新程式，利用檔案資訊表比對其他檔案屬性並不是妥當的做法。此外，在某些情況下，檔案的名稱在安裝時可能會有所變更。如果缺少檔案或版本資訊，請採用其他可用的方法來驗證更新程式的安裝情形。 5. 最後，您也可以按一下 \[以前的版本\] 索引標籤，將舊版檔案的檔案資訊，與檔案的新或更新版本之檔案資訊進行比對。 #### Windows Server 2008 (所有版本) 參考表下表包含此軟體的安全性更新資訊。您可以在本節的＜部署資訊＞小節中找到其他資訊。 <p> </p> <table style="border:1px solid black;"> <tbody> <tr class="odd"> <td style="border:1px solid black;"><strong>未來將包含於 Service Pack 中的內容</strong></td> <td style="border:1px solid black;">此問題的更新將包含在以後的 Service Pack 或更新彙總套件中</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>部署</strong></td> <td style="border:1px solid black;"></td> </tr> <tr class="odd"> <td style="border:1px solid black;">在沒有使用者介入的情況下安裝</td> <td style="border:1px solid black;">所有受支援 32 位元版本之 Windows Server 2008 中的 Internet Explorer 7：<br /> Windows6.0-KB2586448-x86.msu /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 版本之 Windows Server 2008 中的 Internet Explorer 7：<br /> Windows6.0-KB2586448-x64.msu /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 Itanium 版本之 Windows Server 2008 中的 Internet Explorer 7：<br /> Windows6.0-KB2586448-ia64.msu /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 32 位元版本之 Windows Server 2008 中的 Internet Explorer 8：<br /> IE8-Windows6.0-KB2586448-x86.msu /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 版本之 Windows Server 2008 中的 Internet Explorer 8：<br /> IE8-Windows6.0-KB2586448-x64.msu /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows Server 2008 的 Internet Explorer 9：<br /> IE9-Windows6.0-KB2586448-x86.msu /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 型版本 Windows Server 2008 的 Internet Explorer 9：<br /> IE9-Windows6.0-KB2586448-x64.msu /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;">在不重新啟動的情況下安裝</td> <td style="border:1px solid black;">所有受支援 32 位元版本之 Windows Server 2008 中的 Internet Explorer 7：<br /> Windows6.0-KB2586448-x86.msu /quiet /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 版本之 Windows Server 2008 中的 Internet Explorer 7：<br /> Windows6.0-KB2586448-x64.msu /quiet /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 Itanium 版本之 Windows Server 2008 中的 Internet Explorer 7：<br /> Windows6.0-KB2586448-ia64.msu /quiet /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 32 位元版本之 Windows Server 2008 中的 Internet Explorer 8：<br /> IE8-Windows6.0-KB2586448-x86.msu /quiet /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 版本之 Windows Server 2008 中的 Internet Explorer 8：<br /> IE8-Windows6.0-KB2586448-x64.msu /quiet /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows Server 2008 的 Internet Explorer 9：<br /> IE9-Windows6.0-KB2586448-x86.msu /quiet /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 型版本 Windows Server 2008 的 Internet Explorer 9：<br /> IE9-Windows6.0-KB2586448-x64.msu /quiet /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;">詳細資訊</td> <td style="border:1px solid black;">請參閱＜偵測與部署工具及指南＞小節</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>重新開機需求</strong></td> <td style="border:1px solid black;"></td> </tr> <tr class="odd"> <td style="border:1px solid black;">需要重新開機？</td> <td style="border:1px solid black;">是，套用此安全性更新之後，您必須重新啟動系統。</td> </tr> <tr class="even"> <td style="border:1px solid black;">HotPatching</td> <td style="border:1px solid black;">不適用。</td> </tr> <tr class="odd"> <td style="border:1px solid black;"><strong>移除資訊</strong></td> <td style="border:1px solid black;">WUSA.exe 不支援更新的解除安裝。如要解除安裝 WUSA 所安裝的更新程式，請按一下 [控制台]，然後按一下 [安全性]。在 Windows Update 下，按一下 [檢視安裝的更新] 並從更新清單中選取。</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>檔案資訊</strong></td> <td style="border:1px solid black;">請參閱 <a href="https://support.microsoft.com/kb/2586448">Microsoft 知識庫文件編號 2586448</a></td> </tr> <tr class="odd"> <td style="border:1px solid black;"><strong>登錄機碼驗證</strong></td> <td style="border:1px solid black;"><strong>注意：</strong>登錄機碼不存在，無法驗證此更新是否存在。</td> </tr> </tbody> </table> #### 部署資訊安裝更新程式當您安裝本安全性更新時，安裝程式會檢查系統上要更新的檔案先前是否曾用 Microsoft Hotfix 進行更新。如需更多關於出現於本公告中術語的相關資訊 (如 hotfix)，請參閱 [Microsoft 知識庫文件編號 824684](https://support.microsoft.com/kb/824684)。這個安全性更新支援以下的安裝參數。支援的安全性更新安裝參數 \| 參數 \| 描述 \| \|-------------------\|--------------------------------------------------------------------------------------------\| \| /?, /h, /help \| 顯示受支援參數的說明。 \| \| /quiet \| 不顯示狀態或錯誤訊息。 \| \| /norestart \| 與 /quiet 結合使用時，系統在安裝後將不會重新啟動，即使需要重新啟動以完成安裝時亦如此。 \| 注意：如需 wusa.exe 安裝程式的詳細資訊，請參閱 [Microsoft 知識庫文件編號 934307](https://support.microsoft.com/kb/934307)。確認已經套用更新 - Microsoft Baseline Security Analyzer 您可以使用 Microsoft Baseline Security Analyzer (MBSA) 工具確認受影響系統上是否已經套用安全性更新程式。如需詳細資訊，請參閱本公告前段的＜偵測與部署工具及指南＞一節。 - 檔案版本驗證由於 Microsoft Windows 的版本眾多，您電腦上實際執行的步驟可能會與此處描述的不同。如遇到不同的狀況，請參閱產品的說明文件以完成這些步驟。 1. 按一下 \[開始\]，然後在 \[開始搜尋\] 方塊中輸入更新檔案名稱。 2. 當該檔案出現在 \[程式\] 下方時，在檔案名稱上按一下滑鼠右鍵，然後按一下 \[內容\]。 3. 在 \[一般\] 索引標籤下，將檔案大小與公告 KB 文件提供的檔案資訊表進行比對。注意：視作業系統版本或系統所安裝的程式而定，檔案資訊表中列出的檔案未必會全部安裝。 4. 您也可以按一下 \[詳細資料\] 索引標籤，然後將檔案版本與修改日期等資訊與公告 KB 文件提供的檔案資訊表進行比對。注意：在安裝時，檔案版本以外的屬性可能會變更。若要驗證是否成功套用更新程式，利用檔案資訊表比對其他檔案屬性並不是妥當的做法。此外，在某些情況下，檔案的名稱在安裝時可能會有所變更。如果缺少檔案或版本資訊，請採用其他可用的方法來驗證更新程式的安裝情形。 5. 最後，您也可以按一下 \[以前的版本\] 索引標籤，將舊版檔案的檔案資訊，與檔案的新或更新版本之檔案資訊進行比對。 #### Windows 7 (所有版本) 參考表下表包含此軟體的安全性更新資訊。您可以在本節的＜部署資訊＞小節中找到其他資訊。 <p> </p> <table style="border:1px solid black;"> <tbody> <tr class="odd"> <td style="border:1px solid black;"><strong>未來將包含於 Service Pack 中的內容</strong></td> <td style="border:1px solid black;">此問題的更新將包含在以後的 Service Pack 或更新彙總套件中</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>部署</strong></td> <td style="border:1px solid black;"></td> </tr> <tr class="odd"> <td style="border:1px solid black;">在沒有使用者介入的情況下安裝</td> <td style="border:1px solid black;">所有受支援 32 位元版本 Windows 7 的 Internet Explorer 8：<br /> Windows6.1-KB2586448-x86.msu /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 型版本 Windows 7 的 Internet Explorer 8：<br /> Windows6.1-KB2586448-x64.msu /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows 7 的 Internet Explorer 9：<br /> IE9-Windows6.1-KB2586448-x86.msu /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 型版本 Windows 7 的 Internet Explorer 9：<br /> IE9-Windows6.1-KB2586448-x64.msu /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;">在不重新啟動的情況下安裝</td> <td style="border:1px solid black;">所有受支援 32 位元版本 Windows 7 的 Internet Explorer 8：<br /> Windows6.1-KB2586448-x86.msu /quiet /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 型版本 Windows 7 的 Internet Explorer 8：<br /> Windows6.1-KB2586448-x64.msu /quiet /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 32 位元版本 Windows 7 的 Internet Explorer 9：<br /> IE9-Windows6.1-KB2586448-x86.msu /quiet /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">適用於所有受支援 x64 型版本 Windows 7 的 Internet Explorer 9：<br /> IE9-Windows6.1-KB2586448-x64.msu /quiet /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;">詳細資訊</td> <td style="border:1px solid black;">請參閱＜偵測與部署工具及指南＞小節</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>重新開機需求</strong></td> <td style="border:1px solid black;"></td> </tr> <tr class="odd"> <td style="border:1px solid black;">需要重新開機？</td> <td style="border:1px solid black;">是，套用此安全性更新之後，您必須重新啟動系統。</td> </tr> <tr class="even"> <td style="border:1px solid black;">Hotpatching</td> <td style="border:1px solid black;">不適用</td> </tr> <tr class="odd"> <td style="border:1px solid black;"><strong>移除資訊</strong></td> <td style="border:1px solid black;">若要解除安裝由 WUSA 所安裝的更新程式，請使用 /Uninstall 安裝參數，或按一下 [控制台] 和 [系統及安全性]，然後在 Windows Update 項下，按一下 [檢視安裝的更新] 並從更新清單中選取。</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>檔案資訊</strong></td> <td style="border:1px solid black;">請參閱 <a href="https://support.microsoft.com/kb/2586448">Microsoft 知識庫文件編號 2586448</a></td> </tr> <tr class="odd"> <td style="border:1px solid black;"><strong>登錄機碼驗證</strong></td> <td style="border:1px solid black;"><strong>注意：</strong>登錄機碼不存在，無法驗證此更新是否存在。</td> </tr> </tbody> </table> #### 部署資訊安裝更新程式當您安裝本安全性更新時，安裝程式會檢查系統上要更新的檔案先前是否曾用 Microsoft Hotfix 進行更新。如需更多關於出現於本公告中術語的相關資訊 (如 hotfix)，請參閱 [Microsoft 知識庫文件編號 824684](https://support.microsoft.com/kb/824684)。這個安全性更新支援以下的安裝參數。支援的安全性更新安裝參數 \| 參數 \| 描述 \| \|------------------------------------\|--------------------------------------------------------------------------------------------\| \| /?, /h, /help \| 顯示受支援參數的說明。 \| \| /quiet \| 不顯示狀態或錯誤訊息。 \| \| /norestart \| 與 /quiet 結合使用時，系統在安裝後將不會重新啟動，即使需要重新啟動以完成安裝時亦如此。 \| \| /warnrestart:<秒數> \| 與 /quiet 結合使用時，安裝程式會在重新啟動前先警告使用者。 \| \| /promptrestart \| 與 /quiet 結合使用時，安裝程式會在重新啟動前提示。 \| \| /forcerestart \| 與 /quiet 結合使用時，安裝程式會強制關閉應用程式並重新啟動電腦。 \| \| /log:<檔案名稱> \| 啟用記錄至特定檔案。 \| \| /extract:<目的地> \| 解壓縮套件內容到目的地資料夾。 \| \| /uninstall /kb:<KB 編號> \| 解除安裝安全性更新。 \| 注意：如需 wusa.exe 安裝程式的詳細資訊，請參閱 TechNet 文章＜Windows 7 的其他變更＞中的[Windows Update 獨立安裝程式](https://technet.microsoft.com/zh-tw/library/dd871148(ws.10).aspx)。確認已經套用更新 - Microsoft Baseline Security Analyzer 您可以使用 Microsoft Baseline Security Analyzer (MBSA) 工具確認受影響系統上是否已經套用安全性更新程式。如需詳細資訊，請參閱本公告前段的＜偵測與部署工具及指南＞一節。 - 檔案版本驗證由於 Microsoft Windows 的版本眾多，您電腦上實際執行的步驟可能會與此處描述的不同。如遇到不同的狀況，請參閱產品的說明文件以完成這些步驟。 1. 按一下 \[開始\]，然後在 \[搜尋\] 方塊中輸入更新檔案名稱。 2. 當該檔案出現在 \[程式\] 下方時，在檔案名稱上按一下滑鼠右鍵，然後按一下 \[內容\]。 3. 在 \[一般\] 索引標籤下，將檔案大小與公告 KB 文件提供的檔案資訊表進行比對。注意：視作業系統版本或系統所安裝的程式而定，檔案資訊表中列出的檔案未必會全部安裝。 4. 您也可以按一下 \[詳細資料\] 索引標籤，然後將檔案版本與修改日期等資訊與公告 KB 文件提供的檔案資訊表進行比對。注意：在安裝時，檔案版本以外的屬性可能會變更。若要驗證是否成功套用更新程式，利用檔案資訊表比對其他檔案屬性並不是妥當的做法。此外，在某些情況下，檔案的名稱在安裝時可能會有所變更。如果缺少檔案或版本資訊，請採用其他可用的方法來驗證更新程式的安裝情形。 5. 最後，您也可以按一下 \[以前的版本\] 索引標籤，將舊版檔案的檔案資訊，與檔案的新或更新版本之檔案資訊進行比對。 #### Windows Server 2008 R2 (所有版本) 參考表下表包含此軟體的安全性更新資訊。您可以在本節的＜部署資訊＞小節中找到其他資訊。 <p> </p> <table style="border:1px solid black;"> <tbody> <tr class="odd"> <td style="border:1px solid black;"><strong>未來將包含於 Service Pack 中的內容</strong></td> <td style="border:1px solid black;">此問題的更新將包含在以後的 Service Pack 或更新彙總套件中</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>部署</strong></td> <td style="border:1px solid black;"></td> </tr> <tr class="odd"> <td style="border:1px solid black;">在沒有使用者介入的情況下安裝</td> <td style="border:1px solid black;">所有受支援 x64 型版本之 Windows Server 2008 R2 中的 Internet Explorer 8：<br /> Windows6.1-KB2586448-x64.msu /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 Itanium 型版本之 Windows Server 2008 R2 中的 Internet Explorer 8：<br /> Windows6.1-KB2586448-ia64.msu /quiet</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 型版本之 Windows Server 2008 R2 中的 Internet Explorer 9：<br /> IE9-Windows6.1-KB2586448-x64.msu /quiet</td> </tr> <tr class="even"> <td style="border:1px solid black;">在不重新啟動的情況下安裝</td> <td style="border:1px solid black;">所有受支援 x64 型版本之 Windows Server 2008 R2 中的 Internet Explorer 8：<br /> Windows6.1-KB2586448-x64.msu /quiet /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 Itanium 型版本之 Windows Server 2008 R2 中的 Internet Explorer 8：<br /> Windows6.1-KB2586448-ia64.msu /quiet /norestart</td> </tr> <tr class="even"> <td style="border:1px solid black;"></td> <td style="border:1px solid black;">所有受支援 x64 型版本之 Windows Server 2008 R2 中的 Internet Explorer 9：<br /> IE9-Windows6.1-KB2586448-x64.msu /quiet /norestart</td> </tr> <tr class="odd"> <td style="border:1px solid black;">詳細資訊</td> <td style="border:1px solid black;">請參閱＜偵測與部署工具及指南＞小節</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>重新開機需求</strong></td> <td style="border:1px solid black;"></td> </tr> <tr class="odd"> <td style="border:1px solid black;">需要重新開機？</td> <td style="border:1px solid black;">是，套用此安全性更新之後，您必須重新啟動系統。</td> </tr> <tr class="even"> <td style="border:1px solid black;">Hotpatching</td> <td style="border:1px solid black;">不適用</td> </tr> <tr class="odd"> <td style="border:1px solid black;"><strong>移除資訊</strong></td> <td style="border:1px solid black;">若要解除安裝由 WUSA 所安裝的更新程式，請使用 /Uninstall 安裝參數，或按一下 [控制台] 和 [系統及安全性]，然後在 Windows Update 項下，按一下 [檢視安裝的更新] 並從更新清單中選取。</td> </tr> <tr class="even"> <td style="border:1px solid black;"><strong>檔案資訊</strong></td> <td style="border:1px solid black;">請參閱 <a href="https://support.microsoft.com/kb/2586448">Microsoft 知識庫文件編號 2586448</a></td> </tr> <tr class="odd"> <td style="border:1px solid black;"><strong>登錄機碼驗證</strong></td> <td style="border:1px solid black;"><strong>注意：</strong>登錄機碼不存在，無法驗證此更新是否存在。</td> </tr> </tbody> </table> #### 部署資訊安裝更新程式當您安裝本安全性更新時，安裝程式會檢查系統上要更新的檔案先前是否曾用 Microsoft Hotfix 進行更新。如需更多關於出現於本公告中術語的相關資訊 (如 hotfix)，請參閱 [Microsoft 知識庫文件編號 824684](https://support.microsoft.com/kb/824684)。這個安全性更新支援以下的安裝參數。支援的安全性更新安裝參數 \| 參數 \| 描述 \| \|------------------------------------\|--------------------------------------------------------------------------------------------\| \| /?, /h, /help \| 顯示受支援參數的說明。 \| \| /quiet \| 不顯示狀態或錯誤訊息。 \| \| /norestart \| 與 /quiet 結合使用時，系統在安裝後將不會重新啟動，即使需要重新啟動以完成安裝時亦如此。 \| \| /warnrestart:<秒數> \| 與 /quiet 結合使用時，安裝程式會在重新啟動前先警告使用者。 \| \| /promptrestart \| 與 /quiet 結合使用時，安裝程式會在重新啟動前提示。 \| \| /forcerestart \| 與 /quiet 結合使用時，安裝程式會強制關閉應用程式並重新啟動電腦。 \| \| /log:<檔案名稱> \| 啟用記錄至特定檔案。 \| \| /extract:<目的地> \| 解壓縮套件內容到目的地資料夾。 \| \| /uninstall /kb:<KB 編號> \| 解除安裝安全性更新。 \| 注意：如需 wusa.exe 安裝程式的詳細資訊，請參閱 TechNet 文章＜Windows 7 的其他變更＞中的[Windows Update 獨立安裝程式](https://technet.microsoft.com/zh-tw/library/dd871148(ws.10).aspx)。確認已經套用更新 - Microsoft Baseline Security Analyzer 您可以使用 Microsoft Baseline Security Analyzer (MBSA) 工具確認受影響系統上是否已經套用安全性更新程式。如需詳細資訊，請參閱本公告前段的＜偵測與部署工具及指南＞一節。 - 檔案版本驗證由於 Microsoft Windows 的版本眾多，您電腦上實際執行的步驟可能會與此處描述的不同。如遇到不同的狀況，請參閱產品的說明文件以完成這些步驟。 1. 按一下 \[開始\]，然後在 \[開始搜尋\] 方塊中輸入更新檔案名稱。 2. 當該檔案出現在 \[程式\] 下方時，在檔案名稱上按一下滑鼠右鍵，然後按一下 \[內容\]。 3. 在 \[一般\] 索引標籤下，將檔案大小與公告 KB 文件提供的檔案資訊表進行比對。注意：視作業系統版本或系統所安裝的程式而定，檔案資訊表中列出的檔案未必會全部安裝。 4. 您也可以按一下 \[詳細資料\] 索引標籤，然後將檔案版本與修改日期等資訊與公告 KB 文件提供的檔案資訊表進行比對。注意：在安裝時，檔案版本以外的屬性可能會變更。若要驗證是否成功套用更新程式，利用檔案資訊表比對其他檔案屬性並不是妥當的做法。此外，在某些情況下，檔案的名稱在安裝時可能會有所變更。如果缺少檔案或版本資訊，請採用其他可用的方法來驗證更新程式的安裝情形。 5. 最後，您也可以按一下 \[以前的版本\] 索引標籤，將舊版檔案的檔案資訊，與檔案的新或更新版本之檔案資訊進行比對。 ### 其他資訊 #### 感謝 Microsoft [感謝](https://go.microsoft.com/fwlink/?linkid=21127)下列人士協助我們一同保護我們的客戶： - 感謝 McAfee Labs 的 Vishwas Sharma 回報 Scroll 事件遠端執行程式碼弱點 (CVE-2011-1993) - 感謝 [Greplin](https://www.greplin.com) 的 David Bloom 回報 OLEAuto32.dll 遠端執行程式碼弱點 (CVE-2011-1995) - 感謝 Ivan Fratric 與 [TippingPoint 的](https://www.tippingpoint.com)[Zero Day Initiative](https://www.zerodayinitiative.com) 合作回報 Option 項目遠端執行程式碼弱點 (CVE-2011-1996) - 感謝 [GWSlabs](https://www.gwslabs.com) 與 [VeriSign iDefense Labs](https://labs.idefense.com) 合作回報 OnLoad 事件遠端執行程式碼弱點 (CVE-2011-1997) - 感謝 [Greplin](https://www.greplin.com) 的 David Bloom 回報 Jscript9.dll 遠端執行程式碼弱點 (CVE-2011-1998) - 感謝 Ivan Fratric 與 [TippingPoint 的](https://www.tippingpoint.com)[Zero Day Initiative](https://www.zerodayinitiative.com) 合作回報 Select 項目遠端執行程式碼弱點 (CVE-2011-1999) - 感謝 Sebastian Apelt 與 [TippingPoint 的](https://www.tippingpoint.com)[Zero Day Initiative](https://www.zerodayinitiative.com) 合作回報 Body 項目遠端執行程式碼弱點 (CVE-2011-2000) - 感謝匿名研究人員與[TippingPoint 的](https://www.tippingpoint.com)[Zero Day Initiative](https://www.zerodayinitiative.com)合作回報虛擬函式表損毀遠端執行程式碼弱點 (CVE-2011-2001) - 感謝 [Google Inc.](https://www.google.com) 的 Eduardo Vela Nava 與 [Greplin](https://www.greplin.com) 的 David Bloom 協助我們解決本公告中所含之深度防禦變更的問題。 - 感謝 [Soroush Dalili](https://www.secproject.com) 協助我們解決本公告中所含之深度防禦變更的問題 - 感謝 [Google Inc.](https://www.google.com) 的 Billy Rios 協助我們解決本公告中所含之深度防禦變更的問題。 #### Microsoft 主動保護計畫 (MAPP) 為了增強客戶的安全性保護，Microsoft 將在每月發行安全性更新之前，提前向重要安全性軟體提供者提供弱點資訊。安全性軟體提供者可利用此弱點資訊，透過其安全性軟體或裝置 (如防毒軟體、網路入侵偵測系統、或主機入侵預防系統)，為客戶提供更新的保護措施。如果要判斷是否有安全性軟體提供者的主動保護可用，請造訪由 [Microsoft 主動保護計畫 (MAPP) 合作夥伴](https://go.microsoft.com/fwlink/?linkid=215201) (英文) 上列出的計畫合作夥伴所提供的主動保護計畫網站。 #### 支援 - 美國及加拿大地區客戶可洽詢[安全性支援](https://go.microsoft.com/fwlink/?linkid=21131)或 1-866-PCSAFETY 以取得技術支援。與安全性更新有關的支援電話不另外收費。如需更多可用支援選項的資訊，請參閱 [Microsoft 技術支援](https://support.microsoft.com/)。 - 不同國家的客戶，可以從當地的 Microsoft 分公司取得支援。與安全性更新有關的支援電話不另外收費。如需如何連絡 Microsoft 瞭解技術支援問題的詳細資訊，請造訪[國際化支援網站](https://go.microsoft.com/fwlink/?linkid=21155)。 #### 免責聲明 Microsoft 知識庫 (Microsoft Knowledge Base) 中的資訊係以其「現狀」提供，並不提供任何形式之擔保。Microsoft 不做任何明示或默示的責任擔保，包括適售性以及適合某特定用途之擔保責任。無論任何情況下的損害，Microsoft Corporation 及其供應商皆不負任何法律責任，包括直接、間接、偶發、衍生性、所失業務利益或特殊損害。即使 Microsoft Corporation 及其供應商已被告知此類損害的可能性亦不負任何責任。某些地區不允許排除及限制衍生性或附隨損害賠償責任，因此前述限制不適用於這些地區。 #### 修訂 - V1.0 (2011 年 10 月 11 日)：公告發行。 - V1.1 (2011 年 10 月 12 日)：在＜提要＞的＜已知問題＞下新增 Microsoft 知識庫文件編號 2586448 的連結。 - V1.2 (2011 年 11 月 2 日)：宣佈發行一個 Hotfix，來解決安裝 KB2586448 安全性更新後對 Internet Explorer 7 客戶構成影響的一項問題。如需詳細資訊，請參閱更新常見問題集。 Built at 2014-04-18T01:50:00Z-07:00	33.501899	562	0.69804	yue_Hant	0.887831
b7d14f92b8168cacb1f9c052683ed33f9b18fdf6	931	md	Markdown	README.md	hardliner66/CommandLineHere	996666f844df3f0ba861942d00bff49e91a4b1af	[ "MIT" ]	1	2020-12-02T23:25:58.000Z	2020-12-02T23:25:58.000Z	README.md	hardliner66/CommandLineHere	996666f844df3f0ba861942d00bff49e91a4b1af	[ "MIT" ]	null	null	null	README.md	hardliner66/CommandLineHere	996666f844df3f0ba861942d00bff49e91a4b1af	[ "MIT" ]	null	null	null	# CommandLineHere Small AutoHotKey Script to create "open here" keybinds for tools i use. # Installation Download the exe and put into autostart. # Current Keybindings \| keybind \| effect \| comments \| \|---------------------\|-----------------------\|-----------------------------------------------------\| \| Windows + C \| Open Windows Terminal \| If Windows Terminal is not found, open a cmd window \| \| Shift + Windows + C \| Open vscode \| \| \| Ctrl + Windows + C \| Open onivim2 \| If onivim2 is not found, open vscode \| \| Ctrl + Shift + M \| Open Sublime Merge \| \| # Current Remaps \| from \| to \| \|-------------\|-----------\| \| Caps Lock \| Escape \| \| Scroll Lock \| Caps Lock \|	46.55	102	0.403867	eng_Latn	0.729426
b7d1ae178e30d5255f65f6da4320994100b8c8ad	1,323	md	Markdown	README.md	KhazanGu/QiNiuObjectStore	328f44c504ae0e7465da71c2134ffb8caa67daaa	[ "MIT" ]	null	null	null	README.md	KhazanGu/QiNiuObjectStore	328f44c504ae0e7465da71c2134ffb8caa67daaa	[ "MIT" ]	null	null	null	README.md	KhazanGu/QiNiuObjectStore	328f44c504ae0e7465da71c2134ffb8caa67daaa	[ "MIT" ]	null	null	null	# KZQiNiuObjectStore [![CI Status](https://img.shields.io/travis/KhazanGu/KZQiNiuObjectStore.svg?style=flat)](https://travis-ci.org/KhazanGu/KZQiNiuObjectStore) [![Version](https://img.shields.io/cocoapods/v/KZQiNiuObjectStore.svg?style=flat)](https://cocoapods.org/pods/KZQiNiuObjectStore) [![License](https://img.shields.io/cocoapods/l/KZQiNiuObjectStore.svg?style=flat)](https://cocoapods.org/pods/KZQiNiuObjectStore) [![Platform](https://img.shields.io/cocoapods/p/KZQiNiuObjectStore.svg?style=flat)](https://cocoapods.org/pods/KZQiNiuObjectStore) ## Description ### KZQiNiuObjectStore Upload data into QiNiu. The must parameters are host, bucket, accessKey, secretKey The customize parameters data, filePath, fileName, ### KZUploadToken Generate a token for user authorization ### KZUploadViaDataSplit Split data or file and upload ### KZUploadViaFormData Upload full data via formdata ## Requirements ## Installation ``` pod 'KZQiNiuObjectStore', :git => 'https://github.com/KhazanGu/KZQiNiuObjectStore.git' ``` ## Example To run the example project, clone the repo, and run `pod install` from the Example directory first. ## Author Khazan Gu, [email protected] ## License KZQiNiuObjectStore is available under the MIT license. See the LICENSE file for more info.	25.941176	139	0.755858	yue_Hant	0.510141
b7d1f96ddc3db60414a020873e62ffdfcb893451	1,289	md	Markdown	docs/standard-library/operator-greater-or-equal.md	Erikarts/cpp-docs.es-es	9fef104c507e48ec178a316218e1e581753a277c	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/standard-library/operator-greater-or-equal.md	Erikarts/cpp-docs.es-es	9fef104c507e48ec178a316218e1e581753a277c	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/standard-library/operator-greater-or-equal.md	Erikarts/cpp-docs.es-es	9fef104c507e48ec178a316218e1e581753a277c	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- title: operator>= ms.date: 11/04/2016 f1_keywords: - operator>= - std::>= - std.operator>= - '>=' - std.>= - std::operator>= helpviewer_keywords: - '>= operator, comparing specific objects' - operator >= - operator>= ms.assetid: 14fbebf5-8b75-4afa-a51b-3112d31c07cf ms.openlocfilehash: 0f7ed1fcf0c4e3290d110d9aa12b66289cb331f1 ms.sourcegitcommit: 6052185696adca270bc9bdbec45a626dd89cdcdd ms.translationtype: MT ms.contentlocale: es-ES ms.lasthandoff: 10/31/2018 ms.locfileid: "50459038" --- # <a name="operatorgt"></a>operator>= > [!NOTE] > Este tema se incluye en la documentación de Visual C++ como un ejemplo no funcional de los contenedores usados en la biblioteca estándar de C++. Para obtener más información, vea [Contenedores de la biblioteca estándar de C++](../standard-library/stl-containers.md). Sobrecarga operator>= para comparar dos objetos de la clase de plantilla [Container](../standard-library/sample-container-class.md). ## <a name="syntax"></a>Sintaxis ```cpp template <class Ty> bool operator>=( const Container <Ty>& left, const Container <Ty>& right); ``` ## <a name="return-value"></a>Valor devuelto Devuelve `!(left < right)`. ## <a name="see-also"></a>Vea también [\<sample container>](../standard-library/sample-container.md)<br/>	28.021739	268	0.723041	spa_Latn	0.438806
b7d33b41ae0905250bf41b1c757fb373307ad8b8	1,336	md	Markdown	com.ibm.streamsx.network/CHANGELOG.md	markheger/streamsx.network	2d127df59400cf061e720594c8e41890c69079a8	[ "Apache-2.0" ]	null	null	null	com.ibm.streamsx.network/CHANGELOG.md	markheger/streamsx.network	2d127df59400cf061e720594c8e41890c69079a8	[ "Apache-2.0" ]	null	null	null	com.ibm.streamsx.network/CHANGELOG.md	markheger/streamsx.network	2d127df59400cf061e720594c8e41890c69079a8	[ "Apache-2.0" ]	null	null	null	# Changes ========== ## v3.4.1 * [#204](https://github.com/IBMStreams/streamsx.network/issues/204) CHANGELOG.md added ## v3.4.0: * New operator com.ibm.streamsx.network.rtp::RtpDecode ## v3.3.1: * Globalization support: Translated messages updated ## v3.3.0: * PacketContentAssembler operator does not depend anymore on environment variable STREAMS_ADAPTERS_ISS_PAM_DIRECTORY at build and run time. The 'Packet Analysis Module (PAM)' library can be added to the application bundle and the location can be set with the parameters `pamLibrary` and `pamInclude`. * IPAddressLocation operator: New parameter `initOnTuple` added in order to initialize the operator with loading the geography files on the first tuple and not during operator startup. * IPAddressLocation operator supports dynamic loading of MaxMind database triggered by a tuple on control port. ## v3.2.2: * Added the static keyword to a couple of IPv6 helper functions ## v3.2.1: * Performance enhancements for the PacketDPDKSource. ## v3.1.0: * Support for newer version of DPDK, in support of RHEL7.4 and forward. * Additional CIDR functions to determine the range of addresses covered. * Improved IPFilter performance by avoiding needless creation of local list of IP addresses * IPFilter operator: Changed traces with WARN trace level to TRACE level.	34.25641	184	0.773952	eng_Latn	0.942953
b7d40ceb86ec77191a77ef7c95dd5ca82d521823	13,487	md	Markdown	articles/active-directory/develop/tutorial-blazor-webassembly.md	sbrienen/azure-docs.nl-nl	57573a8d40119c389ca398ef6eb1eacadb67c4c8	[ "CC-BY-4.0", "MIT" ]	null	null	null	articles/active-directory/develop/tutorial-blazor-webassembly.md	sbrienen/azure-docs.nl-nl	57573a8d40119c389ca398ef6eb1eacadb67c4c8	[ "CC-BY-4.0", "MIT" ]	null	null	null	articles/active-directory/develop/tutorial-blazor-webassembly.md	sbrienen/azure-docs.nl-nl	57573a8d40119c389ca398ef6eb1eacadb67c4c8	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- title: 'Zelfstudie: Gebruikers aanmelden en een beveiligde API aanroepen vanuit een Blazor WebAssembly-app' titleSuffix: Microsoft identity platform description: In deze zelfstudie meldt u gebruikers aan en roept u een beveiligde API aan met behulp van het Microsoft-identiteitsplatform in een Blazor WASM-app (WebAssembly). author: knicholasa ms.author: nichola ms.service: active-directory ms.subservice: develop ms.topic: tutorial ms.date: 10/16/2020 ms.openlocfilehash: f967b10d729c9c5486bbca9b643f48aaf558687c ms.sourcegitcommit: 9826fb9575dcc1d49f16dd8c7794c7b471bd3109 ms.translationtype: HT ms.contentlocale: nl-NL ms.lasthandoff: 11/14/2020 ms.locfileid: "94628064" --- # <a name="tutorial-sign-in-users-and-call-a-protected-api-from-a-blazor-webassembly-app"></a>Zelfstudie: Gebruikers aanmelden en een beveiligde API aanroepen vanuit een Blazor WebAssembly-app Blazor WASM (WebAssembly) is een app-framework met één pagina voor het bouwen van interactieve web-apps aan de clientzijde met .NET. In deze zelfstudie leert u hoe u verificatie kunt implementeren en gegevens kunt ophalen uit Microsoft Graph in een Blazor WASM-app, met behulp van het Microsoft-identiteitsplatform en door de app te registreren in Azure AD (Azure Active Directory). We hebben ook een [zelfstudie voor Blazor Server](tutorial-blazor-server.md). In deze zelfstudie leert u het volgende: > [!div class="checklist"] > > * Een nieuwe Blazor WebAssembly-app maken die is geconfigureerd om Azure AD (Active Directory) te gebruiken voor [verificatie en autorisatie](authentication-vs-authorization.md), met behulp van het Microsoft-identiteitsplatform > * Gegevens ophalen uit een beveiligde web-API, in dit geval [Microsoft Graph](https://docs.microsoft.com/graph/overview) ## <a name="prerequisites"></a>Vereisten * [NET Core 3.1 SDK](https://dotnet.microsoft.com/download/dotnet-core/3.1) * Een Azure AD-tenant waarmee u een app kunt registreren. Als u geen toegang hebt tot een Azure AD-tenant, kunt u er een maken door u te registreren bij het [Microsoft 365-programma voor ontwikkelaars](https://developer.microsoft.com/microsoft-365/dev-program) of door een [gratis Azure-account](https://azure.microsoft.com/free) te maken. ## <a name="register-the-app-in-the-azure-portal"></a>De app registreren in het Azure-portaal Elke app die gebruikmaakt van Azure Active Directory (Azure AD) voor verificatie moet geregistreerd zijn bij Azure AD. Volg de instructies in [Een toepassing registreren](quickstart-register-app.md) met de volgende specificaties: - Bij Ondersteunde accounttypen selecteert u Enkel accounts in deze organisatieadreslijst. - Kies in de vervolgkeuzelijst Omleidings-URI voor Web en voer `https://localhost:5001/authentication/login-callback` in. De standaardpoort voor een app die wordt uitgevoerd op Kestrel is 5001. Als de app beschikbaar is op een andere poort, geeft u dat poortnummer op in plaats van `5001`. Selecteer onder Verificatie > Impliciete toekenning de selectievakjes voor Toegangstokens en id-tokens en selecteer de knop Opslaan. ## <a name="create-the-app-using-the-net-core-cli"></a>De app maken met behulp van de .NET Core CLI Als u de app wilt maken, hebt u de nieuwste Blazor-sjablonen nodig. U kunt deze met de volgende opdracht installeren voor de .NET Core CLI: ```dotnetcli dotnet new --install Microsoft.AspNetCore.Components.WebAssembly.Templates::3.2.1 ``` Voer vervolgens de volgende opdracht uit om de toepassing te maken. Vervang de tijdelijke aanduidingen in de opdracht door de juiste informatie op de overzichtspagina van uw app en voer de opdracht uit in een opdrachtshell. De uitvoerlocatie die is opgegeven met de optie `-o\|--output` maakt een projectmap als deze nog niet bestaat, en gaat deel uitmaken van de naam van de app. ```dotnetcli dotnet new blazorwasm2 --auth SingleOrg --calls-graph -o {APP NAME} --client-id "{CLIENT ID}" --tenant-id "{TENANT ID}" ``` \| Tijdelijke aanduiding \| Azure-portaalnaam \| Voorbeeld \| \| ------------- \| ----------------------- \| -------------------------------------- \| \| `{APP NAME}` \| — \| `BlazorWASMSample` \| \| `{CLIENT ID}` \| (Client-)id van de app \| `41451fa7-0000-0000-0000-69eff5a761fd` \| \| `{TENANT ID}` \| (Tenant-)id van de map \| `e86c78e2-0000-0000-0000-918e0565a45e` \| ## <a name="test-the-app"></a>De app testen U kunt de app nu bouwen en uitvoeren. Wanneer u deze sjabloon-app uitvoert, moet u het Framework opgeven dat moet worden uitgevoerd met behulp van --framework. In deze zelfstudie wordt gebruikgemaakt van .NET Standard 2.1, maar de sjabloon biedt ook ondersteuning voor andere frameworks. ```dotnetcli dotnet run --framework netstandard2.1 ``` Ga in uw browser naar `https://localhost:5001`. Meld u aan met een Azure AD-gebruikersaccount om te zien hoe de app wordt uitgevoerd en gebruikers worden aangemeld via het Microsoft-identiteitsplatform. De onderdelen van deze sjabloon die aanmeldingen met Azure AD mogelijk maken via het Microsoft-identiteitsplatform, worden uitgelegd in het [ASP.NET.doc over dit onderwerp](/aspnet/core/blazor/security/webassembly/standalone-with-azure-active-directory#authentication-package). ## <a name="retrieving-data-from-microsoft-graph"></a>Gegevens ophalen uit Microsoft Graph [Microsoft Graph](/graph/overview) biedt een reeks API's die toegang bieden tot de Microsoft 365-gegevens van gebruikers in uw tenant. Door gebruik te maken van het Microsoft-identiteitsplatform als identiteitsprovider voor uw app krijgt u eenvoudig toegang tot deze gegevens, omdat Microsoft Graph rechtstreekse ondersteuning biedt voor de tokens die zijn uitgegeven door het Microsoft-identiteitsplatform. In deze sectie voegt u code toe om de e-mailberichten van aangemelde gebruikers weer te geven op de toepassingspagina Gegevens ophalen. Voordat u begint, moet u zich afmelden bij uw app, aangezien u wijzigingen aanbrengt in de vereiste machtigingen en uw huidige token daarvoor niet werkt. Als u dat nog niet hebt gedaan, voert u de app opnieuw uit en selecteert u Afmelden voordat u de onderstaande code bijwerkt. Nu gaat u de registratie en code van de app bijwerken om de e-mailberichten van een gebruiker op te halen, en de berichten weer te geven in de app. Voeg eerst de `Mail.Read` API-machtiging toe aan de app-registratie, zodat in Azure AD duidelijk is dat via de app toegang gaat worden aangevraagd tot de e-mail van de bijbehorende gebruikers. 1. Selecteer uw app onder App-registraties in het Azure-portaal. 1. Selecteer onder Beheren de optie API-machtigingen. 1. Selecteer Een machtiging toevoegen > Microsoft Graph. 1. Selecteer Gedelegeerde machtigingen, zoek en selecteer vervolgens de machtiging Mail.Read. 1. Selecteer Machtigingen toevoegen. Voeg vervolgens het volgende toe aan het .csproj-bestand van uw project in de ItemGroup netstandard2.1. Hierdoor kunt u in de volgende stap de aangepaste HttpClient maken. ```xml <PackageReference Include="Microsoft.Extensions.Http" Version="3.1.7" /> ``` Wijzig vervolgens de code zoals opgegeven in de volgende stappen. Met deze wijzigingen worden [toegangstokens](access-tokens.md) toegevoegd aan de uitgaande aanvragen die zijn verzonden naar de Microsoft Graph API. Dit patroon wordt gedetailleerder besproken in [Extra beveiligingsscenario’s voor ASP.NET Core Blazor WebAssembly](/aspnet/core/blazor/security/webassembly/additional-scenarios). Maak eerst een nieuw bestand met de naam GraphAuthorizationMessageHandler.cs met de volgende code. Deze handler wordt gebruikt om een toegangstoken toe te voegen voor de bereiken `User.Read` en `Mail.Read` voor uitgaande aanvragen naar de Microsoft Graph API. ```csharp using Microsoft.AspNetCore.Components; using Microsoft.AspNetCore.Components.WebAssembly.Authentication; public class GraphAPIAuthorizationMessageHandler : AuthorizationMessageHandler { public GraphAPIAuthorizationMessageHandler(IAccessTokenProvider provider, NavigationManager navigationManager) : base(provider, navigationManager) { ConfigureHandler( authorizedUrls: new[] { "https://graph.microsoft.com" }, scopes: new[] { "https://graph.microsoft.com/User.Read", "https://graph.microsoft.com/Mail.Read" }); } } ``` Vervang vervolgens de inhoud van de methode `Main` in Program.cs door de volgende code. De code maakt gebruik van de nieuwe `GraphAPIAuthorizationMessageHandler`, en `User.Read` en `Mail.Read` worden toegevoegd als standaardbereiken die worden aangevraagd via de app wanneer de gebruiker zich de eerste keer aanmeldt. ```csharp var builder = WebAssemblyHostBuilder.CreateDefault(args); builder.RootComponents.Add<App>("app"); builder.Services.AddScoped<GraphAPIAuthorizationMessageHandler>(); builder.Services.AddHttpClient("GraphAPI", client => client.BaseAddress = new Uri("https://graph.microsoft.com")) .AddHttpMessageHandler<GraphAPIAuthorizationMessageHandler>(); builder.Services.AddMsalAuthentication(options => { builder.Configuration.Bind("AzureAd", options.ProviderOptions.Authentication); options.ProviderOptions.DefaultAccessTokenScopes.Add("User.Read"); options.ProviderOptions.DefaultAccessTokenScopes.Add("Mail.Read"); }); await builder.Build().RunAsync(); ``` Vervang ten slotte de inhoud van de pagina FetchData.razor door de volgende code. Met deze code worden e-mailgegevens van gebruikers opgehaald uit de Microsoft Graph API en weergegeven als een lijst. De nieuwe `HttpClient` die gebruikmaakt van het juiste toegangstoken, wordt gemaakt in `OnInitializedAsync`, en wordt gebruikt om de aanvraag te verzenden naar de Microsoft Graph API. ```c# @page "/fetchdata" @using System.ComponentModel.DataAnnotations @using System.Text.Json.Serialization @using Microsoft.AspNetCore.Components.WebAssembly.Authentication @using Microsoft.Extensions.Logging @inject IAccessTokenProvider TokenProvider @inject IHttpClientFactory ClientFactory @inject IHttpClientFactory HttpClientFactory <p>This component demonstrates fetching data from a service.</p> @if (messages == null) { <p><em>Loading...</em></p> } else { <h1>Hello @userDisplayName !!!!</h1> <table class="table"> <thead> <tr> <th>Subject</th> <th>Sender</th> <th>Received Time</th> </tr> </thead> <tbody> @foreach (var mail in messages) { <tr> <td>@mail.Subject</td> <td>@mail.Sender</td> <td>@mail.ReceivedTime</td> </tr> } </tbody> </table> } @code { private string userDisplayName; private List<MailMessage> messages = new List<MailMessage>(); private HttpClient _httpClient; protected override async Task OnInitializedAsync() { _httpClient = HttpClientFactory.CreateClient("GraphAPI"); try { var dataRequest = await _httpClient.GetAsync("https://graph.microsoft.com/beta/me"); if (dataRequest.IsSuccessStatusCode) { var userData = System.Text.Json.JsonDocument.Parse(await dataRequest.Content.ReadAsStreamAsync()); userDisplayName = userData.RootElement.GetProperty("displayName").GetString(); } var mailRequest = await _httpClient.GetAsync("https://graph.microsoft.com/beta/me/messages?$select=subject,receivedDateTime,sender&$top=10"); if (mailRequest.IsSuccessStatusCode) { var mailData = System.Text.Json.JsonDocument.Parse(await mailRequest.Content.ReadAsStreamAsync()); var messagesArray = mailData.RootElement.GetProperty("value").EnumerateArray(); foreach (var m in messagesArray) { var message = new MailMessage(); message.Subject = m.GetProperty("subject").GetString(); message.Sender = m.GetProperty("sender").GetProperty("emailAddress").GetProperty("address").GetString(); message.ReceivedTime = m.GetProperty("receivedDateTime").GetDateTime(); messages.Add(message); } } } catch (AccessTokenNotAvailableException ex) { // Tokens are not valid - redirect the user to log in again ex.Redirect(); } } public class MailMessage { public string Subject; public string Sender; public DateTime ReceivedTime; } } ``` Start de app nu opnieuw. U ziet dat u wordt gevraagd de app toestemming te geven om uw e-mail te lezen. Dit wordt verwacht wanneer via een app het bereik `Mail.Read` wordt aangevraagd. Nadat u toestemming hebt gegeven, gaat u naar de pagina "Gegevens ophalen" om een e-mailbericht te lezen. :::image type="content" source="./media/tutorial-blazor-webassembly/final-app.png" alt-text="Schermafbeelding van de uiteindelijke app. Het bevat een kop met de tekst "Hello Nicholas" en er wordt een lijst met e-mailberichten van Nicholas weergegeven."::: ## <a name="next-steps"></a>Volgende stappen > [!div class="nextstepaction"] > [Best practices en aanbevelingen voor het Microsoft-identiteitsplatform](./identity-platform-integration-checklist.md)	54.825203	543	0.732483	nld_Latn	0.993146
b7d4c22aa1e2d175fb9258f14de1c1719552ca0c	915	md	Markdown	CHANGELOG.md	Tamschi/reserde	c82c7201210e9f7ce1b58cad388b79075a4d24f7	[ "ECL-2.0", "Apache-2.0", "MIT-0", "MIT" ]	1	2022-03-05T14:22:04.000Z	2022-03-05T14:22:04.000Z	CHANGELOG.md	Tamschi/reserde	c82c7201210e9f7ce1b58cad388b79075a4d24f7	[ "ECL-2.0", "Apache-2.0", "MIT-0", "MIT" ]	9	2021-08-16T14:21:11.000Z	2021-11-12T22:26:52.000Z	CHANGELOG.md	Tamschi/reserde	c82c7201210e9f7ce1b58cad388b79075a4d24f7	[ "ECL-2.0", "Apache-2.0", "MIT-0", "MIT" ]	null	null	null	# reserde Changelog <!-- markdownlint-disable no-trailing-punctuation --> ## 0.0.4 2021-10-21 - Revisions: - Corrected the `package.license` field in Cargo.toml. Sorry about that. ## 0.0.3 2021-10-21 - Features: - `-h` made alternate option to display help. (contributed by @scribe in #31 and #32) > This is implemented by switching to `structopt` for argument parsing. > Additionally, `--in` and `--out` now show valid choices with the `-h`/`--help` command. - Revisions: - Updated dependencies. ## 0.0.2 2021-08-01 - Breaking: - Increased minimum Rust version to 1.53. - Removed features switches. - `serde_taml` type inference changed, so `true` and `false` are interpreted as booleans even by default now. - Features: - Generally updated dependencies, which comes with newly supported input in at least some cases. ## 0.0.1 2020-08-26 Initial unstable release	21.27907	93	0.691803	eng_Latn	0.991212
b7d5fd5389ab00f0c22d6198b843716f0b166255	3,074	md	Markdown	articles/active-directory/manage-apps/scripts/powershell-export-apps-with-secrets-beyond-required.md	R0bes/azure-docs.de-de	24540ed5abf9dd081738288512d1525093dd2938	[ "CC-BY-4.0", "MIT" ]	63	2017-08-28T07:43:47.000Z	2022-02-24T03:04:04.000Z	articles/active-directory/manage-apps/scripts/powershell-export-apps-with-secrets-beyond-required.md	R0bes/azure-docs.de-de	24540ed5abf9dd081738288512d1525093dd2938	[ "CC-BY-4.0", "MIT" ]	704	2017-08-04T09:45:07.000Z	2021-12-03T05:49:08.000Z	articles/active-directory/manage-apps/scripts/powershell-export-apps-with-secrets-beyond-required.md	R0bes/azure-docs.de-de	24540ed5abf9dd081738288512d1525093dd2938	[ "CC-BY-4.0", "MIT" ]	178	2017-07-05T10:56:47.000Z	2022-03-18T12:25:19.000Z	--- title: 'PowerShell-Beispiel: Exportieren von Apps mit Geheimnissen und Zertifikaten, die nach dem erforderlichen Datum im Azure Active Directory-Mandanten ablaufen' description: PowerShell-Beispiel, das alle Apps im Azure Active Directory-Mandanten mit Geheimnissen und Zertifikaten exportiert, die nach dem erforderlichen Datum für die angegebenen Apps ablaufen services: active-directory author: mtillman manager: CelesteDG ms.service: active-directory ms.subservice: app-mgmt ms.workload: identity ms.topic: sample ms.date: 03/09/2021 ms.author: mtillman ms.reviewer: mifarca ms.openlocfilehash: 83d1bd108aada981921bdbe64b32da22b6397f90 ms.sourcegitcommit: 3bb9f8cee51e3b9c711679b460ab7b7363a62e6b ms.translationtype: HT ms.contentlocale: de-DE ms.lasthandoff: 06/14/2021 ms.locfileid: "112076670" --- # <a name="export-apps-with-secrets-and-certificates-expiring-beyond-the-required-date"></a>Exportieren von Apps mit Geheimnissen und Zertifikaten, die nach dem erforderlichen Datum ablaufen Mit diesem PowerShell-Skriptbeispiel werden alle App-Registrierungsgeheimnisse und -Zertifikate, die nach einem erforderlichen Zeitraum für die angegebenen Apps ablaufen, nicht interaktiv aus Ihrem Verzeichnis in eine CSV-Datei exportiert. [!INCLUDE [quickstarts-free-trial-note](../../../../includes/quickstarts-free-trial-note.md)] ## <a name="sample-script"></a>Beispielskript [!code-azurepowershell[main](~/powershell_scripts/application-management/export-apps-with-secrets-beyond-required.ps1 "Exports all apps with secrets and certificates expiring beyond the required date for the specified apps in your directory.")] ## <a name="script-explanation"></a>Erläuterung des Skripts Dieses Skript funktioniert nicht interaktiv. Der Administrator, der es verwendet, muss die Werte im Abschnitt „#PARAMETERS TO CHANGE“ durch die eigene App-ID, das Anwendungsgeheimnis, den Mandantennamen, den Ablaufzeitraum für die App-Anmeldeinformationen und den Pfad ersetzen, in den die CSV-Datei exportiert wird. Dieses Skript verwendet den [OAuth-Flow „Client_Credential“](../../develop/v2-oauth2-client-creds-grant-flow.md). Die Funktion „RefreshToken“ erstellt das Zugriffstoken basierend auf den Werten der Parameter, die vom Administrator geändert wurden. Mit dem Befehl „Add-Member“ werden die Spalten in der CSV-Datei erstellt. \| Get-Help \| Notizen \| \|---\|---\| \| [Invoke-WebRequest](/powershell/module/microsoft.powershell.utility/invoke-webrequest?view=powershell-7.1&preserve-view=true) \| Sendet HTTP- und HTTPS-Anforderungen an eine Webseite oder einen Webdienst. Er analysiert die Antwort und gibt Auflistungen von Links, Bildern und anderen wichtigen HTML-Elementen zurück. \| ## <a name="next-steps"></a>Nächste Schritte Weitere Informationen zum Azure AD PowerShell-Modul finden Sie in der [Übersicht über das Azure AD PowerShell-Modul](/powershell/azure/active-directory/overview). Weitere PowerShell-Beispiele für die Anwendungsverwaltung finden Sie unter [Azure AD PowerShell-Beispiele für die Anwendungsverwaltung](../app-management-powershell-samples.md).	65.404255	319	0.810995	deu_Latn	0.928725
b7d627fb9aa0234a2d5ff2634bd89c6d09460558	770	md	Markdown	Tutorials/Editors-Manual/Tips-and-Tricks/Tips-when-Working-with-Folders/index.md	sumitkharche/UmbracoDocs	de839c20818d4ed13776ecf17ed0145b6d7886a6	[ "MIT" ]	201	2015-08-24T22:15:42.000Z	2022-02-19T19:19:54.000Z	Tutorials/Editors-Manual/Tips-and-Tricks/Tips-when-Working-with-Folders/index.md	sumitkharche/UmbracoDocs	de839c20818d4ed13776ecf17ed0145b6d7886a6	[ "MIT" ]	2,451	2015-08-21T14:22:12.000Z	2022-03-31T19:54:23.000Z	Tutorials/Editors-Manual/Tips-and-Tricks/Tips-when-Working-with-Folders/index.md	sumitkharche/UmbracoDocs	de839c20818d4ed13776ecf17ed0145b6d7886a6	[ "MIT" ]	725	2015-08-26T00:54:49.000Z	2022-03-31T08:22:11.000Z	--- versionFrom: 8.0.0 versionTo: 9.0.0 --- # Refreshing the Tree View When editing content, the content tree will refresh itself when the content is saved. If the tree does not refresh or if multiple editors are working on the site, and you want to have their changes loaded into your content tree - you can do so by reloading parts of the content tree. To reload a section of the content tree: 1. Right-click on an item in the tree. 2. Choose Reload. The parent and child nodes are now reloaded and will reflect any new changes. ![Reload Tree](images/Reload.png) --- Prev: [Tips and Tricks](../../Tips-and-Tricks/index.md) &emsp; &emsp; &emsp; &emsp; &emsp; &emsp; &emsp; &emsp; &emsp; &emsp; &emsp; &emsp; Next: [Audit Trail](../Audit-Trail/index.md)	35	197	0.714286	eng_Latn	0.995075
b7d656eb59e7d75e65e415ba4e25006e4a304694	3,296	md	Markdown	articles/cognitive-services/text-analytics/text-analytics-resource-external-community.md	gliljas/azure-docs.sv-se-1	1efdf8ba0ddc3b4fb65903ae928979ac8872d66e	[ "CC-BY-4.0", "MIT" ]	null	null	null	articles/cognitive-services/text-analytics/text-analytics-resource-external-community.md	gliljas/azure-docs.sv-se-1	1efdf8ba0ddc3b4fb65903ae928979ac8872d66e	[ "CC-BY-4.0", "MIT" ]	null	null	null	articles/cognitive-services/text-analytics/text-analytics-resource-external-community.md	gliljas/azure-docs.sv-se-1	1efdf8ba0ddc3b4fb65903ae928979ac8872d66e	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- title: Externt & community-innehåll för API för textanalys titleSuffix: Azure Cognitive Services description: Partner Bloggar, YouTube-videor, utbildning för Azure Cognitive Services API för textanalys. services: cognitive-services author: aahill manager: nitinme ms.service: cognitive-services ms.subservice: text-analytics ms.topic: conceptual ms.date: 03/02/2019 ms.author: aahi ms.openlocfilehash: 4cdf58974cd8fa9d7813df7e970caea260409225 ms.sourcegitcommit: 58faa9fcbd62f3ac37ff0a65ab9357a01051a64f ms.translationtype: MT ms.contentlocale: sv-SE ms.lasthandoff: 04/29/2020 ms.locfileid: "78251312" --- # <a name="external--community-content-for-the-text-analytics-cognitive-service"></a>Externt & community-innehåll för tjänsten Textanalys kognitivt Länkar i den här artikeln leder dig till användbart webb innehåll som utvecklas och produceras av partner och personal med erfarenhet av att använda API för textanalys. ## <a name="blogs"></a>Bloggar + [API för textanalys ursprungligt meddelande (Azure-blogg)](https://blogs.technet.microsoft.com/machinelearning/2015/04/08/introducing-text-analytics-in-the-azure-ml-marketplace/) + [Använda Textanalys Key fras Cognitive Services API från PowerShell (AutomationNext-bloggen)](https://automationnext.wordpress.com/tag/text-analytics/) + [R-snabb tips: Microsoft Cognitive Services API för textanalys (R bloggare)](https://www.r-bloggers.com/r-quick-tip-microsoft-cognitive-services-text-analytics-api/) + [Sentiment analys i Logic app med hjälp av SQL Server data (TechNet blogg)](https://social.technet.microsoft.com/wiki/contents/articles/36074.logic-apps-with-azure-cognitive-service.aspx) + [Sentiment analys med Dynamics 365 CRM Online (MSDN-bloggen)](https://blogs.msdn.microsoft.com/geoffreyinnis/2016/07/11/sentiment-analysis-in-usd-with-cognitive-services-text-analytics/) + Power BI blogg: extrahering av nyckel fraser från Facebook-meddelanden: [del 1](https://community.powerbi.com/t5/Community-Blog/Text-Analytics-in-Power-BI-Extraction-of-key-phrases-from/ba-p/88483) och [del 2](https://community.powerbi.com/t5/Community-Blog/Text-Analytics-in-Power-BI-Extraction-of-key-phrases-from/ba-p/88487) + [Identifiera sentiment av kommentarer i en Yammer-grupp med MS Flow (Microsoft Tech community)](https://docs.microsoft.com/Yammer/integrate-yammer-with-other-apps/sentiment-analysis-flow-azure) ## <a name="videos"></a>Videoklipp + [Logic app för att identifiera sentiment och extrahera nyckel fraser från din text](https://www.youtube.com/watch?v=jVN9NObAzgk) + [Attitydanalys att använda Power BI och Microsoft Cognitive Services](https://www.youtube.com/watch?v=gJ1j3N7Y75k) + [Text analys extrahera nyckel fraser med Power BI och Microsoft Cognitive Services](https://www.youtube.com/watch?v=R_-1TB2BF14) ## <a name="next-steps"></a>Nästa steg Letar du efter information om en funktion eller ett användnings fall som vi inte avser? Överväg att begära eller rösta på det på [UserVoice](https://cognitive.uservoice.com/forums/555922-text-analytics). ## <a name="see-also"></a>Se även [StackOverflow: Azure API för textanalys](https://stackoverflow.com/questions/tagged/text-analytics-api) [StackOverflow: Azure Cognitive Services](https://stackoverflow.com/questions/tagged/microsoft-cognitive)	56.827586	329	0.795206	swe_Latn	0.509088
b7d6d202d2847c0d6a820733ffc77faea1c808b5	7,630	md	Markdown	docs/get-started/team/cloud-migration.md	Mdlglobal-atlassian-net/cloud-adoption-framework.pl-pl	b31574fe18f9931652451d5a381af8f5052f5e8b	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/get-started/team/cloud-migration.md	Mdlglobal-atlassian-net/cloud-adoption-framework.pl-pl	b31574fe18f9931652451d5a381af8f5052f5e8b	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/get-started/team/cloud-migration.md	Mdlglobal-atlassian-net/cloud-adoption-framework.pl-pl	b31574fe18f9931652451d5a381af8f5052f5e8b	[ "CC-BY-4.0", "MIT" ]	1	2020-05-28T15:57:35.000Z	2020-05-28T15:57:35.000Z	--- title: 'Wprowadzenie: Budowanie zespołu migracji w chmurze' description: Ten przewodnik ułatwia zespołowi migracji w chmurze zrozumienie zakresu, elementów dostarczanych i możliwości wymaganych do pomyślnej migracji do chmury. author: JanetCThomas ms.author: janet ms.service: cloud-adoption-framework ms.subservice: overview ms.topic: conceptual ms.date: 05/15/2020 ms.openlocfilehash: d6d1d60ce89aa6ab809bb413a0d56ecea5ceb352 ms.sourcegitcommit: 9a84c2dfa4c3859fd7d5b1e06bbb8549ff6967fa ms.translationtype: MT ms.contentlocale: pl-PL ms.lasthandoff: 05/21/2020 ms.locfileid: "83751823" --- # <a name="get-started-build-a-cloud-migration-team"></a>Wprowadzenie: Budowanie zespołu migracji w chmurze Zespoły migracji w chmurze to nowoczesne zespoły zespołów implementacji technicznej lub zespołów projektowych. Charakter chmury może wymagać większej struktury zespołu płynów. Niektóre zespoły migracji koncentrują się wyłącznie na migracji w chmurze, a inne koncentrują się na innowacjech korzystających z technologii chmurowych. Niektóre z nich obejmują szeroką wiedzę techniczną, która jest wymagana do ukończenia dużych wysiłków związanych z wdrażaniem, takich jak Pełna migracja centrów danych, a inne mają ściślejszy fokus techniczny i mogą poruszać się między projektami w celu osiągnięcia określonych celów, na przykład zespołu specjalistów ds. technologii, którzy ułatwiają konwertowanie maszyn wirtualnych SQL na wystąpienia usługi SQL PaaS. Bez względu na typ lub liczbę zespołów migracji w chmurze, te zespoły zwykle udostępniają wiedzę z dziedziny dla INFORMATYKów, analizy biznesowej lub partnerów implementacji. ## <a name="prerequisites"></a>Wymagania wstępne - [Utwórz konto platformy Azure](https://docs.microsoft.com/learn/modules/create-an-azure-account): pierwszy krok korzystania z platformy Azure to utworzenie konta. - [Azure Portal](https://docs.microsoft.com/learn/modules/tour-azure-portal): Zapoznaj się z Azure Portal funkcjami i usługami oraz Dostosuj Portal. - [Wprowadzenie do platformy Azure](https://docs.microsoft.com/learn/modules/welcome-to-azure): Rozpoczynanie pracy z platformą Azure. Utwórz i skonfiguruj pierwszą maszynę wirtualną w chmurze. - [Podstawy platformy Azure](https://docs.microsoft.com/learn/paths/azure-for-the-data-engineer): Poznaj koncepcje chmury, Poznaj zalety, Porównaj i Odróżnij podstawowe strategie oraz Poznaj zakres usług dostępnych na platformie Azure. - Zapoznaj się z [metodologią migrowania](../../migrate/index.md). ## <a name="minimum-scope"></a>Zakres minimalny Jądrem wszystkich działań związanych z wdrażaniem w chmurze jest zespół migracji w chmurze. Ten zespół udostępnia zmiany techniczne, które umożliwiają wdrażanie. W zależności od celów nakładu pracy ten zespół może obejmować różnorodną gamę członków zespołu, którzy obsługują szeroki zestaw zadań technicznych i służbowych. Zakres zespołu obejmuje co najmniej: - Racjonalizacja [cyfrowego podpisywania](../../digital-estate/index.md). - Przeglądanie, sprawdzanie poprawności i [przenoszenie zaległości migracji z priorytetami](../../migrate/migration-considerations/assess/release-iteration-backlog.md). - Wykonywanie [pierwszego obciążenia](../../digital-estate/rationalize.md#select-the-first-workload) jako możliwości uczenia się. ## <a name="deliverable"></a>Dostarcza Podstawowy element dostarczany z dowolnego zespołu migracji w chmurze to termin, wysoka jakość rozwiązań technicznych, które zostały opisane w planie wdrożenia, zgodnie z wymaganiami dotyczącymi zarządzania i rezultatami biznesowymi przy użyciu technologii, narzędzi i dostępnych rozwiązań do automatyzacji. ### <a name="ongoing-monthly-tasks"></a>Trwające miesięczne zadania - Nadzorowanie [procesów zarządzania zmianami](../../migrate/migration-considerations/prerequisites/technical-complexity.md). - Zarządzanie [zaległościami wersji i przebiegu](../../migrate/migration-considerations/assess/release-iteration-backlog.md). - Kompiluj i obsługuj przyjętą strefę docelową w połączeniu z wymaganiami dotyczącymi zarządzania. - Wykonaj zadania techniczne opisane w [zaległościach przebiegu](../../migrate/migration-considerations/assess/release-iteration-backlog.md). ### <a name="team-cadence"></a>Erze zespołu Firma Microsoft zaleca, aby zespoły zapewniające możliwość wdrażania chmury były przeznaczone do pracy w czasie pełnym. Najlepiej, jeśli te zespoły spotykają się codziennie w sposób samodzielny. Celem codziennych spotkań jest szybkie aktualizowanie zaległości i komunikowanie się, co zostało zakończone, co należy zrobić dzisiaj i jakie elementy są blokowane, wymagając dodatkowej obsługi zewnętrznej. Harmonogramy wydań i czasy trwania iteracji są unikatowe dla każdej firmy. Zakres od 1 do czterech tygodni dla iteracji prawdopodobnie jest średnim czasem trwania. Bez względu na iterację lub wydanie erze zaleca się, aby zespół zaspokajał wszystkie zespoły pomocnicze na końcu każdej wersji, aby komunikować się z wynikami wydania i zmieniać priorytet nadchodzących wysiłków. Jest również cenny do zaspokajania jako zespół na końcu każdego przebiegu, z centrum w [chmurze doskonałości](./cloud-center-of-excellence.md) lub [zespołem](./cloud-governance.md) nadzoru w chmurze, aby zachować zgodność z typowymi wysiłkami i potrzebami pomocy technicznej. Niektóre z zadań technicznych związanych z wdrażaniem w chmurze mogą stać się powtarzane. Członkowie zespołu powinni obrócić co 3 – miesiące, aby uniknąć problemów z zadowoleniem pracowników i zachować odpowiednie umiejętności. Rotacyjna siedziba w centrum rozwiązań w [chmurze doskonałości](./cloud-center-of-excellence.md) lub [zespołu nadzoru chmurowego](./cloud-governance.md) może zapewnić doskonałą okazję, aby pracownicy mogli korzystać z nowych innowacji. ## <a name="baseline-capability"></a>Możliwość linii bazowej W zależności od żądanych wyników działalności biznesowej wymagane jest, aby zapewnić możliwość korzystania z pełnych możliwości wdrażania chmury: - Realizatorów infrastruktury. - Inżynierowie DevOps. - Deweloperzy aplikacji. - Badacze danych. - Specjaliści platformy danych lub aplikacji. W celu zapewnienia optymalnej współpracy i wydajności zalecamy, aby zespoły rozwiązań w chmurze miały średni rozmiar zespołu sześciu osób. Zespoły te powinny być samodzielne z perspektywą wykonywania technicznego. Zdecydowanie zalecamy, aby te zespoły obejmowały również wiedzę na temat zarządzania projektami, z głębokiego środowiska Agile, Scrum lub innymi iteracyjnymi modelami. Ten zespół jest najbardziej efektywny, gdy jest zarządzany przy użyciu płaskiej struktury. ## <a name="out-of-scope"></a>Poza zakresem Może być konieczne dodatkowe wsparcie z istniejących pracowników działu IT. Może to być cenny współautor do wdrożenia w chmurze przez przeprowadzeniem brokera w chmurze i partnera na potrzeby innowacji i elastyczność biznesową. - [Centralne obowiązki IT](../../organize/central-it.md) ## <a name="whats-next"></a>Co dalej Przyjęcie jest doskonałe, ale nieregulowane wdrożenie może dawać nieoczekiwane wyniki. Wyrównaj do [zespołu ds. ładu w chmurze](./cloud-governance.md) , aby przyspieszyć wdrażanie i najlepsze rozwiązania, jednocześnie zmniejszając ryzyko biznesowe i techniczne. Te dwa zespoły tworzą saldo w ramach wysiłków związanych z wdrażaniem w chmurze, ale są uznawane za MVP, ponieważ mogą nie być trwałe. Każdy zespół ma wiele systemyów, jak przedstawiono na [wykresach odpowiedzialnych ](../../organize/raci-alignment.md), do których można się skontaktować. Dowiedz się więcej na temat [antywzorców organizacyjnych: silosów i fiefdoms](../../organize/fiefdoms-silos.md).	87.701149	750	0.818742	pol_Latn	0.999986
b7d70ffaf865eb73ff5bfebb6bede9de6d1d339e	19,926	md	Markdown	Firebase.Crashlytics/component/GettingStarted.md	lganderson/GoogleApisForiOSComponents	8c5df68e6352381a77f4c938e8d1ae84574ff202	[ "MIT" ]	null	null	null	Firebase.Crashlytics/component/GettingStarted.md	lganderson/GoogleApisForiOSComponents	8c5df68e6352381a77f4c938e8d1ae84574ff202	[ "MIT" ]	null	null	null	Firebase.Crashlytics/component/GettingStarted.md	lganderson/GoogleApisForiOSComponents	8c5df68e6352381a77f4c938e8d1ae84574ff202	[ "MIT" ]	1	2021-08-02T11:14:35.000Z	2021-08-02T11:14:35.000Z	# Get Started with Firebase Crashlytics for iOS ## Table of Content - [Get Started with Firebase Crashlytics for iOS](#get-started-with-firebase-crashlytics-for-ios) - [Table of Content](#table-of-content) - [Before you begin](#before-you-begin) - [Add Firebase to your app](#add-firebase-to-your-app) - [Configure Firebase in your app](#configure-firebase-in-your-app) - [Upgrade to Firebase Crashlytics from Firebase Crash Reporting](#upgrade-to-firebase-crashlytics-from-firebase-crash-reporting) - [Update project dependencies](#update-project-dependencies) - [Migrate logs](#migrate-logs) - [Set up manual initialization](#set-up-manual-initialization) - [Test your Firebase Crashlytics implementation](#test-your-firebase-crashlytics-implementation) - [Force a crash to test your implementation](#force-a-crash-to-test-your-implementation) - [Adjust your project's debug settings](#adjust-your-projects-debug-settings) - [Test it out](#test-it-out) - [Enable Crashlytics debug mode](#enable-crashlytics-debug-mode) - [Customize your Firebase Crashlytics crash reports](#customize-your-firebase-crashlytics-crash-reports) - [Enable opt-in reporting](#enable-opt-in-reporting) - [Add custom logs](#add-custom-logs) - [Add custom keys](#add-custom-keys) - [Set user IDs](#set-user-ids) - [Log non-fatal exceptions](#log-non-fatal-exceptions) - [Logs and custom keys](#logs-and-custom-keys) - [Performance considerations](#performance-considerations) - [What about NSExceptions?](#what-about-nsexceptions) - [Manage Crash Insights data](#manage-crash-insights-data) - [Extend Firebase Crashlytics with Cloud Functions](#extend-firebase-crashlytics-with-cloud-functions) - [Known issues](#known-issues) ## Before you begin * Enable Crashlytics: Click Set up Crashlytics in the [Firebase console][1]. ## Add Firebase to your app 1. Create a Firebase project in the [Firebase console][1], if you don't already have one. If you already have an existing Google project associated with your mobile app, click Import Google Project. Otherwise, click Create New Project. 2. Click Add Firebase to your iOS app and follow the setup steps. If you're importing an existing Google project, this may happen automatically and you can just [download the config file][2]. 3. When prompted, enter your app's bundle ID. It's important to enter the bundle ID your app is using; this can only be set when you add an app to your Firebase project. 4. At the end, you'll download a `GoogleService-Info.plist` file. You can [download this file][2] again at any time. ## Configure Firebase in your app Once you have your `GoogleService-Info.plist` file downloaded in your computer, do the following steps in Visual Studio: 1. Add `GoogleService-Info.plist` file to your app project. 2. Set `GoogleService-Info.plist` build action behaviour to `Bundle Resource` by Right clicking/Build Action. 3. Add the following line of code somewhere in your app, typically in your AppDelegate's `FinishedLaunching` method (don't forget to import `Firebase.Core` and `Firebase.Crashlytics` namespace): ```csharp App.Configure (); Crashlytics.Configure (); ``` --- # Upgrade to Firebase Crashlytics from Firebase Crash Reporting Crashlytics is the new, primary crash reporter for Firebase. If your app uses Firebase Crash Reporting, there's good news: Crashlytics offers enhanced crash reporting with nearly the same setup process you're used to, so upgrading is straightforward: 1. Update your project's dependencies. 2. Migrate any log calls, if you have them. 3. Set up manual initialization, if you used it. ## Update project dependencies To update your app's depencencies for Firebase Crashlytics, swap the Xamarin.Firebase.iOS.CrashReporting NuGet with the Xamarin.Firebase.iOS.Crashlytics NuGet and remove the Firebase Crash Reporting custom command: 1. In Visual Studio, do a double click on Packages folder and add the Xamarin.Firebase.iOS.Crashlytics NuGet. 2. Remove Xamarin.Firebase.iOS.CrashReporting NuGet by right clicking/Remove. 3. Open your app Project Options, go to Build > Custom Command and delete the Crash Reporting command: ``` sh ${ProjectDir}/scripts/FirebaseCrashReporting/xamarin_upload_symbols.sh -n ${ProjectName} -b ${TargetDir} -i ${ProjectDir}/Info.plist -p ${ProjectDir}/GoogleService-Info.plist -s ${ProjectDir}/service-account.json ``` ## Migrate logs If you used Firebase Crash Reporting custom logs, you have to update those for Firebase Crashlytics too: \| Firebase Crash Reporting \| Firebase Crashlytics \| \|--------------------------\|--------------------------------------------------------------------------------------------------\| \| CrashReporting.Log \| Logging.Log / Logging.LogCallerInformation <br /> Logging.NSLog / Logging.NSLogCallerInformation \| > ![warning_icon] _Note:_ _The string given to these methods must be an escaped string due it will be passed to a C function and it expects an escaped string. For example, if you want to print a %, you must type %%. Passing an unescaped string may cause the termination of your app._ ## Set up manual initialization Like Firebase Crash Reporting, the Firebase Crashlytics SDK automatically initializes Crashlytics as soon as you add it to your app. If instead you initialize reporting manually, Crashlytics has a way to do that as well: 1. Turn off automatic collection with a new key to your Info.plist file: * Key: `firebase_crashlytics_collection_enabled` * Value: `false` 2. Replace the Crash Reporting initialization call with one for Crashlytics: ```csharp // Delete Crash Reporting // CrashReporting.SharedInstance.CrashCollectionEnabled = true; // Add Crashlytics Fabric.Fabric.With (typeof (Crashlytics)); ``` --- # Test your Firebase Crashlytics implementation ## Force a crash to test your implementation You don't have to wait for a crash to know that Crashlytics is working. You can use the SDK to force a crash by adding the following code to your app: ```csharp using Firebase.Crashlytics; ... public override void ViewDidLoad () { base.ViewDidLoad (); var button = new UIButton (UIButtonType.RoundedRect) { Frame = new CGRect (0, 0, 100, 30), TranslatesAutoresizingMaskIntoConstraints = false }; button.SetTitle ("Crash", UIControlState.Normal); button.TouchUpInside += Button_TouchUpInside; View.AddSubview (button); button.AddConstraint (NSLayoutConstraint.Create (button, NSLayoutAttribute.CenterX, NSLayoutRelation.Equal, View, NSLayoutAttribute.CenterX, 1, 0)); button.AddConstraint (NSLayoutConstraint.Create (button, NSLayoutAttribute.CenterY, NSLayoutRelation.Equal, View, NSLayoutAttribute.CenterY, 1, 0)); } void Button_TouchUpInside (object sender, EventArgs e) { Crashlytics.SharedInstance.Crash (); } ``` ## Adjust your project's debug settings Crashlytics can’t capture crashes if your build attaches a debugger at launch. Adjust your build settings to change the project's debug information format: 1. In Visual Studio, open your app project settings. * _Mac:_ Go to Build > iOS Build * _Windows:_ Go to iOS Build 2. Select an iPhone platform. 2. Make sure that Strip native debugging symbols is unchecked. ## Test it out The code snippet above adds a button that crashes your app when pressed. For it to work, run the app without a debugger, the debugger interferes with Crashlytics: 1. Select a physical device and Debug configuration. 2. Run the app without debugging: * _Mac:_ Open Run menu > Start Without Debugging * _Windows:_ Open Build menu > Start Without Debugging The build process will upload the `dSYM` file of the app to Firebase in a background process. 3. Touch Crash button to crash the app. 4. Open your app once more to let the Crashlytics API report the crash. Your crash should show up in the Firebase console within 5 minutes. ## Enable Crashlytics debug mode If your forced crash didn't crash, crashed before you wanted it to, or you're experiencing some other issue with Crashlytics, you can enable Crashlytics debug mode to track down the problem: ```csharp public override bool FinishedLaunching (UIApplication application, NSDictionary launchOptions) { ... Fabric.Fabric.SharedSdk.Debug = true; ... return true; } ``` --- # Customize your Firebase Crashlytics crash reports Firebase Crashlytics can work with very little setup on your part—as soon as you add the SDK, Crashlytics gets to work sending crash reports to the Firebase console. For more fine-grained control of your crash reports, customize your Crashlytics SDK configuration. For example, you can enable opt-in reporting for privacy-minded users, add logs to track down pesky bugs, and more. ## Enable opt-in reporting By default, Firebase Crashlytics automatically collects crash reports for all your app's users. To give users more control over the data they send, you can enable opt-in reporting instead. To do that, you have to disable automatic collection and initialize Crashlytics only for opt-in users. 1. Turn off automatic collection with a new key to your Info.plist file: * Key: `firebase_crashlytics_collection_enabled` * Value: `false` 2. Enable collection for selected users by initializing Crashlytics at runtime: ```csharp Fabric.Fabric.With (typeof (Crashlytics)); ``` ## Add custom logs To give yourself more context for the events leading up to a crash, you can add custom Crashlytics logs to your app. Crashlytics associates the logs with your crash data and makes them visible in the Firebase console. Use `LogCallerInformation` and `NSLogCallerInformation` methods to help pinpoint issues. It automatically includes information about the C# filename, method, and line number associated with the log. You can optionally pass the class name to have a better log: * Debug builds: `NSLogCallerInformation` method passes through to `NSLog` method so you can see the output in Visual Studio and on the device. * Release builds: To improve performance, `LogCallerInformation` method silences all other output and will be only shown on Firebase Crashlytics dashboard when a crash occurs. ```csharp void Button_TouchUpInside (object sender, EventArgs e) { var data = new Dictionary<object, object> { { "A keyblade", "for a heartless" }, { "A heart", "for a nobody" } }; var nsData = NSDictionary.FromObjectsAndKeys (data.Values.ToArray (), data.Keys.ToArray (), data.Keys.Count); Logging.LogCallerInformation ($"Hi! Maybe, I'm about to crash! Here's some data: {nsData}", nameof (ViewController)); // or Logging.NSLogCallerInformation ($"Hi! Maybe, I'm about to crash! Here's some data: {nsData}", nameof (ViewController)); Crashlytics.SharedInstance.Crash (); } ``` Assuming that you are coding in a file named `MyViewController.cs`, the output will be: ``` MyViewController.cs: ViewController.Button_TouchUpInside line 47 $ Hi! Maybe I'm about to crash! Here's some data: { "A keyblade" = "for a heartless"; "A heart" = "for a nobody"; } ``` If you omit the second parameter of `NSLogCallerInformation` or `LogCallerInformation` method, the output will be: ``` MyViewController.cs: Button_TouchUpInside line 47 $ Hi! Maybe I'm about to crash! Here's some data: { "A keyblade" = "for a heartless"; "A heart" = "for a nobody"; } ``` > ![note_icon] _To avoid slowing down your app, Crashlytics limits logs to 64kB. Crashlytics deletes older log entries if a session's logs go over that limit._ > ![warning_icon] _Note:_ _The string given to these methods must be an escaped string due it will be passed to a C function and it expects an escaped string. For example, if you want to print a %, you must type %%. Passing an unescaped string may cause the termination of your app._ ## Add custom keys Custom keys help you get the specific state of your app leading up to a crash. You can associate arbitrary key/value pairs with your crash reports, and see them in the Firebase console: ```csharp void SetObjectValue (NSObject value, string key); void SetStringValue (string value, string key); void SetIntValue (int value, string key); void SetBoolValue (bool value, string key); void SetFloatValue (float value, string key); ``` Sometimes you need to change the existing key value. Call the same key, but replace the value, for example: ```csharp Crashlytics.SharedInstance.SetIntValue (3, "current_level"); Crashlytics.SharedInstance.SetStringValue ("logged_in", "last_UI_action"); ``` > ![note_icon] _Crashlytics supports a maximum of 64 key/value pairs. Once you reach this threshold, additional values are not saved. Each key/value pair can be up to 1 kB in size_ ## Set user IDs To diagnose an issue, it’s often helpful to know which of your users experienced a given crash. Crashlytics includes a way to anonymously identify users in your crash reports. To add user IDs to your reports, assign each user a unique identifier in the form of an ID number, token, or hashed value: ```csharp Crashlytics.SharedInstance.SetUserIdentifier ("123456789"); ``` If you ever need to clear a user identifier after you set it, reset the value to a blank string. ## Log non-fatal exceptions In addition to automatically reporting your app’s crashes, Crashlytics lets you log non-fatal exceptions. On iOS, you do that by recording `NSError` objects, which Crashlytics reports and groups much like crashes: ```csharp Crashlytics.SharedInstance.RecordError (error); ``` When using the `RecordError` method, it's important to understand the `NSError` structure and how Crashlytics uses the data to group crashes. Incorrect usage of the `RecordError` method can cause unpredicatable behavior and may require Crashlytics to limit reporting of logged errors for your app. An `NSError` object has three arguments: `NSString Domain`, `nint Code`, and `NSDictionary UserInfo`. Unlike fatal crashes, which are grouped via stack trace analysis, logged errors are grouped by the NSError `Domain` and `Code`. This is an important distinction between fatal crashes and logged errors. For example, logging an error such as: ```csharp var userInfo = new Dictionary<object, object> { { NSError.LocalizedDescriptionKey, NSBundle.MainBundle.LocalizedString ("The request failed.", null) }, { NSError.LocalizedFailureReasonErrorKey, NSBundle.MainBundle.LocalizedString ("The response returned a 404.", null) }, { NSError.LocalizedRecoverySuggestionErrorKey, NSBundle.MainBundle.LocalizedString ("Does this page exist?", null) }, { "ProductId", "123456" }, { "UserId", "Jane Smith" } }; var error = new NSError (new NSString ("SomeErrorDomain"), -1001, NSDictionary.FromObjectsAndKeys (userInfo.Values.ToArray (), userInfo.Keys.ToArray (), userInfo.Keys.Count)); ``` Creates a new issue that is grouped by `SomeErrorDomain` and `-1001`. Additional logged errors that use the same domain and code values will be grouped under this issue. > ![warning_icon] _Avoid using unique values, such as user ID, product ID, and timestamps in the domain and code fields. Using unique values in these fields causes a high cardinality of issues and may result in Crashlytics needing to limit the reporting of logged errors in your app. Unique values should instead be added to the `UserInfo` Dictionary object._ Data contained within the `UserInfo` object are converted to key-value pairs and displayed in the keys/logs section within an individual issue. ![note_icon] _Crashlytics only stores the most recent 8 exceptions in a given app session. If your app throws more than 8 exceptions in a session, older exceptions are lost._ ### Logs and custom keys Just like crash reports, you can embed logs and custom keys to add context to the NSError. However, there is a difference in what logs are attached to crashes versus logged errors. When a crash occurs and the app is relaunched, the logs Crashlytics retrieves from disk are those that were written right up to the time of the crash. When you log an NSError, the app does not immediately terminate. Because Crashlytics only sends the logged error report on the next app launch, and because Crashlytics must limit the amount of space allocated for logs on disk, it is possible to log enough after an NSError is recorded so that all relevant logs are rotated out by the time Crashlytics sends the report from the device. Keep this balance in mind when logging NSErrors and using `Log` and custom keys in your app. ### Performance considerations Keep in mind that logging an NSError can be fairly expensive. At the time you make the call, Crashlytics captures the current thread’s call stack using a process called stack unwinding. This process can be CPU and I/O intensive, particularly on architectures that support DWARF unwinding (arm64 and x86). After the unwind is complete, the information is written to disk synchronously. This prevents data loss if the next line were to crash. While it is safe to call this API on a background thread, remember that dispatching this call to another queue will lose the context of the current stack trace. ### What about NSExceptions? Crashlytics doesn’t offer a facility for logging/recording NSException instances directly. Generally speaking, the Cocoa and Cocoa Touch APIs are not exception-safe. That means the use of `@catch` in your Objective-C library code or in a third-party Objective-C code can have very serious unintended side-effects in your process, even when used with extreme care. You should never use `@catch` statements in your Objective-C code. Please refer to Apple’s [documentation][2] on the topic. ## Manage Crash Insights data Crash Insights helps you resolve issues by comparing your anonymized stack traces to traces from other Firebase apps and letting you know if your issue is part of a larger trend. For many issues, Crash Insights even provides resources to help you debug the crash. Crash Insights uses aggregated crash data to identify common stability trends. If you’d prefer not to share your app's data, you can opt-out of Crash Insights from the Crash Insights menu at the top of your Crashlytics issue list in the [Firebase console][1]. --- # Extend Firebase Crashlytics with Cloud Functions You can trigger a function in response to Crashlytics issue events including new issues, regressed issues, and velocity alerts. To learn more about this, please, read the following [documentation][3]. --- # Known issues * Error `Native linking failed, duplicate symbol '_main'` appears when you try to build for iPhoneSimulator. A workaround for this is to change the behavior of the Registrar: 1. Open your project settings 2. Go to Build tab 3. Select iOS Build option 4. Type `--registrar:static` in Additional mtouch arguments textbox 5. Click on Ok Don't forget to add this in Release and Debug configuration of iPhoneSimulator platform. <sub>_Portions of this page are modifications based on work created and [shared by Google](https://developers.google.com/readme/policies/) and used according to terms described in the [Creative Commons 3.0 Attribution License](http://creativecommons.org/licenses/by/3.0/). Click [here](https://firebase.google.com/docs/crashlytics/get-started) to see original Firebase documentation._</sub> [1]: https://console.firebase.google.com [2]: https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/Exceptions/Articles/ExceptionsAndCocoaFrameworks.html [3]: https://firebase.google.com/docs/crashlytics/extend-with-cloud-functions [note_icon]: https://cdn3.iconfinder.com/data/icons/UltimateGnome/22x22/apps/gnome-app-install-star.png [warning_icon]: https://cdn2.iconfinder.com/data/icons/freecns-cumulus/32/519791-101_Warning-20.png	53.854054	809	0.762521	eng_Latn	0.973979
b7d74c8f99c7391899744d74c319b77f9e821c34	824	md	Markdown	docs/plugin/install.md	comicChiii/minigame-adaptor	e68583d12e1e249fdd195df4a84054c34132b2cc	[ "Apache-2.0" ]	null	null	null	docs/plugin/install.md	comicChiii/minigame-adaptor	e68583d12e1e249fdd195df4a84054c34132b2cc	[ "Apache-2.0" ]	null	null	null	docs/plugin/install.md	comicChiii/minigame-adaptor	e68583d12e1e249fdd195df4a84054c34132b2cc	[ "Apache-2.0" ]	null	null	null	# 如何安装下载转换工具的核心模块。 [点我下载](https://dldir1.qq.com/WechatWebDev/plugins/BeefBallEngine-unitytool/1.0.0/UnityTool.unitypackage) 下载下来会是一个unitypackage，所以你马上就能想到你可以双击导入它。 ![image.png](./image/11.png) 接下来你可以看到在你的unity菜单栏出现了新的导出能力，就说明你已经成功安装好了导出工具了这时候选择扩展模块管理 ![image.png](./image/12.png) 以下这个新弹出的面板，是下载扩展导出模块的地方，在这里你可以选择下载你需要的导出能力，如后文会提到的NGUI导出能力或是代码导出能力。但这个时候我们暂不需要在这做任何事情。 ![image.png](./image/13.png) ------------------------------------------------------------ 回到菜单里选择导出，会弹出资源导出面板，后续的资源导出都会通过这个面板完成。 ![image.png](./image/14.png) 第一步你需要在这个面板里指定你的资源导出位置，你在这里可以选择快速创建一个引擎示例项目，将该项目作为你的导出路径。又或是你直接指定一个已存在的目录作为导出路径。 ![image.png](./image/15.png) 选择好路径之后，就可以开始进行导出了。可以看到导出面板里会出现几种导出模式供你选择。 ![image.png](./image/16.png) ------------------------------------------------------------ [下一节](./scene.md) 我们将会开始导出第一个场景	27.466667	104	0.674757	yue_Hant	0.516623
b7d790dc40fd68aa2d0cc219ada2cdba0f95efc2	2,541	md	Markdown	sccm/develop/reference/apps/sms_metereduser-server-wmi-class.md	sandytsang/SCCMdocs	d1e763c4dd6e2cf30f71ba6fb4d831302bfb9dea	[ "CC-BY-4.0", "MIT" ]	1	2021-05-26T07:48:10.000Z	2021-05-26T07:48:10.000Z	sccm/develop/reference/apps/sms_metereduser-server-wmi-class.md	sandytsang/SCCMdocs	d1e763c4dd6e2cf30f71ba6fb4d831302bfb9dea	[ "CC-BY-4.0", "MIT" ]	null	null	null	sccm/develop/reference/apps/sms_metereduser-server-wmi-class.md	sandytsang/SCCMdocs	d1e763c4dd6e2cf30f71ba6fb4d831302bfb9dea	[ "CC-BY-4.0", "MIT" ]	2	2021-03-26T20:01:43.000Z	2021-07-30T22:07:46.000Z	--- title: "SMS_MeteredUser Class" titleSuffix: "Configuration Manager" ms.custom: "" ms.date: "09/20/2016" ms.prod: "configuration-manager" ms.reviewer: "" ms.suite: "" ms.technology: - "configmgr-other" ms.tgt_pltfrm: "" ms.topic: "article" applies_to: - "System Center Configuration Manager (current branch)" ms.assetid: 368c8640-fb35-43bf-83c6-611c9fea173d searchScope: - ConfigMgr SDK caps.latest.revision: 8 author: "shill-ms" ms.author: "v-suhill" manager: "mbaldwin" --- # SMS_MeteredUser Server WMI Class The `SMS_MeteredUser` Windows Management Instrumentation (WMI) class is an SMS Provider server class, in System Center Configuration Manager, that lists users that have used metered applications. The following syntax is simplified from Managed Object Format (MOF) code and includes all inherited properties. ## Syntax ``` Class SMS_MeteredUser : SMS_BaseClass { String Domain; String FullName; UInt32 MeteredUserID; String UserName; }; ``` ## Methods The `SMS_MeteredUser` class does not define any methods. ## Properties `Domain` Data type: `String` Access type: Read/Write Qualifiers: None Domain to which the metered user belongs. `FullName` Data type: `String` Access type: Read/Write Qualifiers: None Fully qualified domain name of the user in domain\user format. `MeteredUserID` Data type: `UInt32` Access type: Read/Write Qualifiers: [key] ID for the metered user. `UserName` Data type: `String` Access type: Read/Write Qualifiers: None Name of the metered user. ## Remarks There are no special class qualifiers for this class. For more information about both the class qualifiers and the property qualifiers included in the Properties section, see [Configuration Manager Class and Property Qualifiers](../../../develop/reference/misc/class-and-property-qualifiers.md). This class is the source for the `MeteredUserID` foreign key used in other classes. ## Requirements ## Runtime Requirements For more information, see [Configuration Manager Server Runtime Requirements](../../../develop/core/reqs/server-runtime-requirements.md). ## Development Requirements For more information, see [Configuration Manager Server Development Requirements](../../../develop/core/reqs/server-development-requirements.md). ## See Also [Software Metering Server WMI Classes](../../../develop/reference/apps/software-metering-server-wmi-classes.md)	27.322581	298	0.720582	eng_Latn	0.896585
b7d7cb740603b4b1ccfd7da30f35ba2908f15af8	22	md	Markdown	README.md	dlarudgus20/newly-aha	4d80bf992af3d8e7a6ddcca3c38d5959059ec66f	[ "MIT" ]	2	2017-08-12T11:23:37.000Z	2017-08-12T17:11:52.000Z	README.md	dlarudgus20/newly-aha	4d80bf992af3d8e7a6ddcca3c38d5959059ec66f	[ "MIT" ]	null	null	null	README.md	dlarudgus20/newly-aha	4d80bf992af3d8e7a6ddcca3c38d5959059ec66f	[ "MIT" ]	null	null	null	# newly-aha newly-aha	7.333333	11	0.727273	eng_Latn	0.717492
b7d7ce377c3ec59093d090604032789eeacf1c8e	261	md	Markdown	pages/21.tech/hinge-topbase-tilted/tech.md	brickcamp/website	08a140b5b01006c46213dfdc216756d28b608974	[ "CC-BY-4.0" ]	null	null	null	pages/21.tech/hinge-topbase-tilted/tech.md	brickcamp/website	08a140b5b01006c46213dfdc216756d28b608974	[ "CC-BY-4.0" ]	null	null	null	pages/21.tech/hinge-topbase-tilted/tech.md	brickcamp/website	08a140b5b01006c46213dfdc216756d28b608974	[ "CC-BY-4.0" ]	null	null	null	--- title: "Hinge Top on Base (Tilted)" date: 14-09-2015 image: image.png cad: model.ldr taxonomy: part: ["3937", "3938"] partcount: 2 width: [2, stud] depth: [1.5, stud] height: [1, brick] function: stud_tilt stud_tilt_angle: [90, 0to90] ---	13.736842	35	0.624521	eng_Latn	0.178595
b7d98393fed5fd20fa9ea0e25552f6d6c4f71146	4,397	md	Markdown	README.md	node-co/hounddesk-api	6b6be70687b2a68daa6a1d3a99ca053f79df76d0	[ "MIT" ]	null	null	null	README.md	node-co/hounddesk-api	6b6be70687b2a68daa6a1d3a99ca053f79df76d0	[ "MIT" ]	null	null	null	README.md	node-co/hounddesk-api	6b6be70687b2a68daa6a1d3a99ca053f79df76d0	[ "MIT" ]	null	null	null	# 👋 Welcome to Hounddesk API Welcome to Hounddesk, we're an Open Source project from the [NodeCo](https://github.com/node-co) community. Our goal is to provide a better way to connect with your community. Our roadmap is under construction at the moment. <img src="https://avatars.githubusercontent.com/u/62183765?s=200&v=4" /> Join our community <a target="_blank" href="https://node-colombia.slack.com">![alt text](https://img.shields.io/badge/Slack-4A154B?style=for-the-badge&logo=slack&logoColor=white "Slack logo")</a> ## 🧑‍🤝‍🧑 Contributing Currently we're planning the project and preparing an early version, but no worries, you will be able to collaborate soon ! ## 🧰 Our Stack We are using many different technologies, but our main stack is Node.js using the following tools: \| Name \| Type \| \| ------------ \| :---------------------: \| \| Mongo \| Storage \| \| Google Cloud \| API hosting via GKE \| \| Firebase \| Authz \| \| Typescript \| Static type definitions \| \| Bugsnag \| API logs management \| ## 📘 Concepts Hounddesk is build around the concept of creating plugable modules in order to encourage low coupling (that means reducing the direct dependency for another component). # Hounddesk Authorization and Authentication Authentication and Authorization is one of the core modules of any application. For Hounddesk is not the exception, we want to be able to provide a secure system without compromising flexibility. We will leverage Hapi authentication strategy for that. ### Supported strategies: \| Name \| Type \| \| -------------------------------------------------------------------------------------------------- \| :--------------------------------: \| \| [@hounddesk/plugin-firebase-authz](https://www.npmjs.com/package/@hounddesk/plugin-firebase-authz) \| Authorization \| \| [@hounddesk/plugin-firebase-users](https://www.npmjs.com/package/@hounddesk/plugin-firebase-users) \| Authentication and User management \| \| [@hounddesk/password-policy](https://www.npmjs.com/package/@hounddesk/password-policy) \| Password policy \| ## ✏️ Notes Hounddesk core libraries are Open Source too! They are under the project [Bones](https://github.com/hounddesk/bones#readme) Hounddesk and Hounddesk core libraries are officially supported by [NodeCo Community](https://github.com/node-co) ## 💻 Installation This is a GitHub template repository created from our open source project [pkg-template](https://github.com/hounddesk/pkg-template) Before using, [download and install Node.js](https://nodejs.org/en/download/). Node.js 10.16.3 or higher is recommended. ## Available utilities enabled by default - TypeScript - Testing with [Jest](https://jestjs.io/) and [Tap reporter](https://www.npmjs.com/package/jest-tap-reporter) - TypeScript linting using eslint - TypeScript watch mode using ts-node-dev - Formatting using Prettier - Pre-commit hook using Husky (will run linter, formatting and unit tests before each commit) ## VSCode support - Format on save / type enabled by default using Prettier - Prettier extension configuration, [Read more](https://github.com/prettier/prettier-vscode) ## Conventions - Source folder: src - Output directory: dist - Sourcemaps enabled by default - Jest current file: Unit test debugging command for VSCode - Debug: Node debugging command for VSCode - All the eslint plugins are using the recommended defaults ## Available commands ### Start in development mode (watch mode with automatic restart) ```bash $ npm run dev ``` ### Build TypeScript ```bash $ npm run build ``` ### Build TypeScript in watch mode (without automatic restart) ```bash $ npm run build:watch ``` ### Run unit tests ```bash $ npm test ``` ### Run linter ```bash $ npm run lint ``` ### Run linter with auto fix ```bash $ npm run lint:fix ``` ### Run tests with coverage report ```bash $ npm run coverage ``` ## VSCode developer suggested extensions The following extensions works great alongside with this setup: - [Prettier](https://github.com/prettier/prettier-vscode) - [Jest](https://github.com/jest-community/vscode-jest) - once installed, enable the runner >> Jest > Start runner	32.813433	176	0.674778	eng_Latn	0.894949
b7da3968ff3102ee87b518bada405de8bf06f71e	8,590	md	Markdown	microsoft-365/compliance/archive-telegram-archiver-data.md	MicrosoftDocs/microsoft-365-docs-pr.pt-BR	88959f119be80545a0b854d261ba4acf2ac1e131	[ "CC-BY-4.0", "MIT" ]	29	2019-09-17T04:18:20.000Z	2022-03-20T18:51:42.000Z	microsoft-365/compliance/archive-telegram-archiver-data.md	MicrosoftDocs/microsoft-365-docs-pr.pt-BR	88959f119be80545a0b854d261ba4acf2ac1e131	[ "CC-BY-4.0", "MIT" ]	2	2022-02-09T06:48:15.000Z	2022-02-09T06:48:47.000Z	microsoft-365/compliance/archive-telegram-archiver-data.md	MicrosoftDocs/microsoft-365-docs-pr.pt-BR	88959f119be80545a0b854d261ba4acf2ac1e131	[ "CC-BY-4.0", "MIT" ]	3	2021-03-14T23:52:56.000Z	2021-05-31T14:02:38.000Z	--- title: Configurar um conector para arquivar dados de comunicações do Microsoft 365 f1.keywords: - NOCSH ms.author: markjjo author: markjjo manager: laurawi ms.date: '' audience: Admin ms.topic: how-to ms.service: O365-seccomp ms.localizationpriority: medium ms.collection: M365-security-compliance description: Os administradores podem configurar um conector teleMessage para importar e arquivar dados de comunicações do Microsoft 365. Isso permite que você arquive dados de fontes de dados de terceiros no Microsoft 365 para que você possa usar recursos de conformidade, como retenção legal, pesquisa de conteúdo e políticas de retenção para gerenciar os dados de terceiros da sua organização. ms.openlocfilehash: 753dba06ced9c3369054a1712371fb309c11671e ms.sourcegitcommit: d4b867e37bf741528ded7fb289e4f6847228d2c5 ms.translationtype: MT ms.contentlocale: pt-BR ms.lasthandoff: 10/06/2021 ms.locfileid: "60192314" --- # <a name="set-up-a-connector-to-archive-telegram-communications-data"></a>Configurar um conector para arquivar dados de comunicações do Telegram Use o conector TeleMessage no Centro de conformidade do Microsoft 365 para importar e arquivar chats, anexos, arquivos e mensagens e chamadas do Telegram excluídos. Depois de configurar e configurar um conector, ele se conecta à conta teleMessage da sua organização e importa a comunicação móvel dos funcionários usando o Arquivo Mortor do Telegram para caixas de correio em Microsoft 365. Depois que os dados do conector do Arquivamento do Telegram são armazenados em caixas de correio de usuário, você pode aplicar recursos de conformidade Microsoft 365 como Retenção de Litígio, Pesquisa de conteúdo e políticas de retenção Microsoft 365 dados de comunicação do Telegram. Por exemplo, você pode pesquisar a comunicação do Telegram usando a Pesquisa de Conteúdo ou associar a caixa de correio que contém os dados do conector do Arquivo morto do Telegram com um custodiante em uma Advanced eDiscovery caso. Usar um conector de Arquivamento do Telegram para importar e arquivar dados no Microsoft 365 pode ajudar sua organização a manter-se em conformidade com os regulamentos de governança corporativa e as políticas regulatórias. ## <a name="overview-of-archiving-telegram-communications-data"></a>Visão geral dos dados de comunicações do Telegram de arquivamento A visão geral a seguir explica o processo de uso de um conector para arquivar dados de comunicações do Microsoft 365. ![Fluxo de trabalho de arquivamento de comunicações do Telegram.](../media/TelegramConnectorWorkflow.png) 1. Sua organização trabalha com TeleMessage para configurar um conector de Arquivamento do Telegram. Para obter mais informações, consulte Ativando o Arquivo mortor de [telegrama de TeleMessage para Microsoft 365](https://www.telemessage.com/microsoft-365-activation-for-telegram-archiver/). 2. Em tempo real, os dados do Telegram da sua organização são copiados para o site do TeleMessage. 3. O conector do Arquivo Mortor do Telegram criado no Centro de conformidade do Microsoft 365 conecta-se ao site do TeleMessage todos os dias e transfere as mensagens de email das 24 horas anteriores para uma área segura do Azure Armazenamento no Microsoft Cloud. 4. O conector importa os itens de comunicação móvel para a caixa de correio de um usuário específico. Uma nova pasta chamada Arquivo mortor do Telegram será criada na caixa de correio do usuário específico e os itens serão importados para ela. O conector faz esse mapeamento usando o valor da propriedade endereço email do usuário. Cada mensagem de email contém essa propriedade, que é preenchida com o endereço de email de cada participante da mensagem de email. > Além do mapeamento automático do usuário usando o valor da propriedade endereço email do usuário, você também pode definir um mapeamento personalizado carregando um arquivo de mapeamento CSV. Esse arquivo de mapeamento deve conter o Número móvel do usuário e o endereço Microsoft 365 caixa de correio correspondente para cada usuário. Se você habilitar o mapeamento automático do usuário e fornecer um mapeamento personalizado, para cada item de email, o conector procurará primeiro o arquivo de mapeamento personalizado. Se ele não encontrar um usuário Microsoft 365 que corresponda ao número móvel de um usuário, o conector usará a propriedade endereço de email do usuário do item de email. Se o conector não encontrar um usuário Microsoft 365 no arquivo de mapeamento personalizado ou na propriedade de endereço de email do usuário do item de email, o item não será importado. ## <a name="before-you-set-up-a-connector"></a>Antes de configurar um conector - Order the [Telegram archiving service from TeleMessage](https://www.telemessage.com/mobile-archiver/order-mobile-archiver-for-o365/) and get a valid administration account for your organization. Você precisará entrar nessa conta quando criar o conector no centro de conformidade. - Registre todos os usuários que exigem arquivamento do Telegram na conta teleMessage. Ao registrar usuários, certifique-se de usar o mesmo endereço de email usado para sua conta Microsoft 365. - Instale o aplicativo de Arquivamento do Telegram nos telefones celulares de seus funcionários e ative-o. O aplicativo Desarmador do Telegram permite que eles se comuniquem e conversem com outros usuários do Telegram. - O usuário que cria um conector de Arquivamento do Telegram na Etapa 3 deve receber a função de Exportação de Importação de Caixa de Correio Exchange Online. Isso é necessário para adicionar conectores na página Conectores de dados no Centro de conformidade do Microsoft 365. Por padrão, essa função não é atribuída a nenhum grupo de funções no Exchange Online. Você pode adicionar a função Exportar Importação de Importação de Caixa de Correio ao grupo de função Gerenciamento da Organização Exchange Online. Ou você pode criar um grupo de funções, atribuir a função Exportar Importação de Caixa de Correio e adicionar os usuários apropriados como membros. Para obter mais informações, consulte as seções Criar grupos de [função](/Exchange/permissions-exo/role-groups#create-role-groups) ou [Modificar](/Exchange/permissions-exo/role-groups#modify-role-groups) grupos de função no artigo "Gerenciar grupos de funções em Exchange Online". - Esse conector de dados está disponível em GCC ambientes na nuvem Microsoft 365 Us Government. Aplicativos e serviços de terceiros podem envolver o armazenamento, a transmissão e o processamento dos dados do cliente da sua organização em sistemas de terceiros que estão fora da infraestrutura do Microsoft 365 e, portanto, não são cobertos pelos compromissos de conformidade e proteção de dados do Microsoft 365. A Microsoft não faz nenhuma representação de que o uso desse produto para se conectar a aplicativos de terceiros implica que esses aplicativos de terceiros são compatíveis com FEDRAMP. ## <a name="create-a-telegram-archiver-connector"></a>Criar um conector de arquivamento do Telegram Depois de concluir os pré-requisitos descritos na seção anterior, você pode criar o conector do Arquivo Mortor do Centro de conformidade do Microsoft 365. O conector usa as informações fornecidas para se conectar ao site teleMessage e transfere dados de comunicações do Telegram para as caixas de correio de usuário correspondentes no Microsoft 365. 1. Vá até <https://compliance.microsoft.com> e clique em Conectores de dados > T elegram Archiver. 2. Na página Descrição do produto do Arquivo do Telegram, clique em Adicionar conector. 3. Na página Termos de serviço, clique em Aceitar. 4. Na página Logon para TeleMessage, em Etapa 3, insira as informações necessárias nas caixas a seguir e clique em Próximo. - Nome de usuário: Seu nome de usuário teleMessage. - Senha: Sua senha teleMessage. 5. Depois que o conector for criado, você poderá fechar a janela pop-up e ir para a próxima página. 6. Na página Mapeamento de usuário, habilita o mapeamento automático do usuário. Para habilitar o mapeamento personalizado, carregue um arquivo CSV que contém as informações de mapeamento do usuário e clique em Próximo. 7. Revise suas configurações e clique em Concluir para criar o conector. 8. Vá até a guia Conectores na página Conectores de dados para ver o andamento do processo de importação do novo conector. ## <a name="known-issues"></a>Problemas conhecidos - Neste momento, não há suporte para importação de anexos ou itens maiores que 10 MB. O suporte para itens maiores estará disponível posteriormente.	103.493976	943	0.809197	por_Latn	0.999749
b7db7128237205f42f8c4c7f35bb7d0ecd844eb8	2,779	md	Markdown	README.md	zhangkn/SwiftDump2009	630499b9ccefec16561866236abf653fc9bb2a08	[ "Apache-2.0" ]	266	2020-07-05T19:27:59.000Z	2022-03-28T06:26:55.000Z	README.md	zhangkn/SwiftDump2009	630499b9ccefec16561866236abf653fc9bb2a08	[ "Apache-2.0" ]	4	2020-09-01T07:24:44.000Z	2022-03-04T06:28:01.000Z	README.md	zhangkn/SwiftDump2009	630499b9ccefec16561866236abf653fc9bb2a08	[ "Apache-2.0" ]	42	2020-07-06T02:02:29.000Z	2022-02-24T23:35:53.000Z	#### SwiftDump ##### [中文文档](./README_zh.md) SwiftDump is a command-line tool for retriving the Swift Object info from Mach-O file. Similar to [class-dump](https://github.com/nygard/class-dump/), but the difference is that SwiftDump focus on swift 5 objects. For Mach-O files mixed with Objective-C and swift, you can combine class-dump with SwiftDump. There is alos a [Frida](https://www.frida.re/) version named [FridaSwiftDump](https://github.com/neil-wu/FridaSwiftDump/). You can either use`SwiftDump` for a Mach-O file or `FridaSwiftDump` for a foreground running app. If you are curious about the Mach-O format, check the image at the bottom of this article. ![demo](./Doc/img_demo_result.jpg) #### Usage ``` Text USAGE: SwiftDump [--debug] [--arch <arch>] <file> [--version] ARGUMENTS: <file> MachO File OPTIONS: -d, --debug Show debug log. -a, --arch <arch> Choose architecture from a fat binary (only support x86_64/arm64). (default: arm64) -v, --version Version -h, --help Show help information. ``` * SwiftDump ./TestMachO > result.txt * SwiftDump -a x86_64 ./TestMachO > result.txt #### Features * Written entirely in swift, the project is tiny * Dump swift 5 struct/class/enum/protocol * Parse enum with payload case * Support inheritance and protocol * Since it is written in swift, the mangled names are demangled by swift's runtime function, such as `swift_getTypeByMangledNameInContext` and `swift_demangle_getDemangledName`. Thanks to the runtime function, SwiftDump can demangle complex type, such as RxSwift variable. For example, `RxSwift.Queue<(eventTime: Foundation.Date, event: RxSwift.Event<A.RxSwift.ObserverType.Element>)>` #### TODO * Parse swift function address * More #### Compile 1. Clone the repo 2. Open SwiftDump.xcodeproj with Xcode 3. Modify 'Signing & Capabilities' to use your own id 4. Build & Run The default Mach-O file path is `Demo/test`, you can change it in `Xcode - Product - Scheme - Edit Scheme - Arguments` (Tested on Xcode Version 11.5 (11E608c), MacOS 10.15.5) #### Credit * [Machismo](https://github.com/g-Off/Machismo) : Parsing of Mach-O binaries using swift. * [swift-argument-parser](https://github.com/apple/swift-argument-parser) : Straightforward, type-safe argument parsing for Swift. * [Swift metadata](https://knight.sc/reverse%20engineering/2019/07/17/swift-metadata.html) : High level description of all the Swift 5 sections that can show up in a Swift binary. #### License MIT #### Mach-O File Format The following image shows how SwiftDump parse swift types from file `Demo/test`. You can open this file with [MachOView](https://github.com/gdbinit/MachOView). ![demo](./Doc/macho.jpg)	34.308642	307	0.715725	eng_Latn	0.898189
b7dbd02d094b876fa3e94a224e61f3552bf4053e	915	md	Markdown	_posts/2015/03/2015-03-11-WAMP.md	ksami/ksami.github.io	3ffbc290927f35d819684708002d51f06a222805	[ "MIT" ]	null	null	null	_posts/2015/03/2015-03-11-WAMP.md	ksami/ksami.github.io	3ffbc290927f35d819684708002d51f06a222805	[ "MIT" ]	null	null	null	_posts/2015/03/2015-03-11-WAMP.md	ksami/ksami.github.io	3ffbc290927f35d819684708002d51f06a222805	[ "MIT" ]	null	null	null	--- layout: post date: 2015-03-11 15:33:00 title: WAMP tags: [programming, WAMP, server, networking] --- You may have heard of the LAMP stack which stands for Linux, Apache, MySQL, PHP, a very popular bunch of technologies for web servers. Linux for the OS, Apache for the web server itself, MySQL for the database, PHP for the server-side language. I tried [WAMP](http://www.wampserver.com/en/) yesterday, the Windows version of LAMP. It is available as just one installer and can be run with one click. I was honestly taken aback a little at the ease of installation and use after having had so much trouble struggling with servers in the past. Once WAMP is running, place your php/html files into `www` in the WAMP installation folder (default `C:\WAMP`) and, using your web browser, navigate to `localhost/filename`. So simple! I haven't tried the MySQL database part yet so new post when I do.	65.357143	297	0.753005	eng_Latn	0.994902
b7dbd75bcb9c6ce1c3998988e5ea856cab1bbe21	637	md	Markdown	README.md	TylerKirby/Phrontis	9e970221b14f0cf2660d221a090a028701249d7a	[ "MIT" ]	null	null	null	README.md	TylerKirby/Phrontis	9e970221b14f0cf2660d221a090a028701249d7a	[ "MIT" ]	null	null	null	README.md	TylerKirby/Phrontis	9e970221b14f0cf2660d221a090a028701249d7a	[ "MIT" ]	null	null	null	# Phrontis: Ancient Greek Companion App Phrontis is a mobile application that helps students of Ancient Greek master core vocabulary. The app provides flashcards for 20 units of Greek vocabulary. Each unit corresponds to a unit in the popular textbook Hansen and Quinn. Phrontis is built in React Native. It has an iOS version found [here](https://itunes.apple.com/us/app/phrontis/id1273389458?mt=8&ign-mpt=uo%3D4) and Android version [here](https://play.google.com/store/apps/details?id=com.phrontis&hl=en) The developement of Phrontis was funded by an Innovation in Education grant provided by Washington University in St. Louis.	79.625	237	0.799058	eng_Latn	0.975748
b7dd24c08bc56ecffa04098ed44df2890e120e50	4,381	md	Markdown	dev-itpro/api-reference/v2.0/resources/dynamics_purchaseReceipt.md	christianbraeunlich/dynamics365smb-devitpro-pb	564dbba9682ed01e7c0d7aee64db97dc1922637f	[ "CC-BY-4.0", "MIT" ]	null	null	null	dev-itpro/api-reference/v2.0/resources/dynamics_purchaseReceipt.md	christianbraeunlich/dynamics365smb-devitpro-pb	564dbba9682ed01e7c0d7aee64db97dc1922637f	[ "CC-BY-4.0", "MIT" ]	null	null	null	dev-itpro/api-reference/v2.0/resources/dynamics_purchaseReceipt.md	christianbraeunlich/dynamics365smb-devitpro-pb	564dbba9682ed01e7c0d7aee64db97dc1922637f	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- title: purchaseReceipt resource type description: A purchase receipt object in Dynamics 365 Business Central. author: SusanneWindfeldPedersen ms.topic: article ms.devlang: na ms.tgt_pltfrm: na ms.workload: na ms.date: 04/01/2021 ms.author: solsen --- # purchaseReceipt resource type [!INCLUDE[api_v2_note](../../../includes/api_v2_note.md)] <!-- START>DO_NOT_EDIT --> <!-- IMPORTANT:Do not edit any of the content between here and the END>DO_NOT_EDIT. --> Represents a purchase receipt in [!INCLUDE[prod_short](../../../includes/prod_short.md)]. > [!NOTE] > For information about enabling APIs for [!INCLUDE[prod_short](../../../includes/prod_short.md)] see [Enabling the APIs for Dynamics 365 Business Central](../enabling-apis-for-dynamics-nav.md). ## Methods \| Method \| Return Type\|Description \| \|:--------------------\|:-----------\|:-------------------------\| \|[GET purchaseReceipt](../api/dynamics_purchasereceipt_get.md)\|purchaseReceipt\|Gets a purchase receipt object.\| ## Navigation \| Navigation \|Return Type\| Description \| \|:----------\|:----------\|:-----------------\| \|[vendor](dynamics_vendor.md)\|vendor \|Gets the vendor of the purchaseReceipt.\| \|[countryRegion](dynamics_countryregion.md)\|countryRegion \|Gets the countryregion of the purchaseReceipt.\| \|[purchaseReceiptLines](dynamics_purchasereceiptline.md)\|purchaseReceiptLines \|Gets the purchasereceiptlines of the purchaseReceipt.\| \|[dimensionSetLines](dynamics_dimensionsetline.md)\|dimensionSetLines \|Gets the dimensionsetlines of the purchaseReceipt.\| ## Properties \| Property \| Type \|Description \| \|:-------------------\|:-------\|:---------------\| \|id\|GUID\|The unique ID of the purchase receipt. Non-editable.\| \|number\|string\|Specifies the number of the purchase receipt.\| \|invoiceDate\|date\|The invoice date .\| \|postingDate\|date\|The date that the purchase receipt is posted.\| \|dueDate\|date\|T he date the purchase receipt is due.\| \|vendorNumber\|string\|Specifies vendor's number.\| \|vendorName\|string\|Specifies vendor's name.\| \|payToName\|string\|Pay to name of the purchase receipt. \| \|payToContact\|string\|Pay to contact.\| \|payToVendorNumber\|string\|Pay to vendor number.\| \|shipToName\|string\|Ship to name.\| \|shipToContact\|string\|Ship to contact.\| \|buyFromAddressLine1\|string\|Buy from address line 1.\| \|buyFromAddressLine2\|string\|Buy from address line 2.\| \|buyFromCity\|string\|Buy from city.\| \|buyFromCountry\|string\|Buy from state.\| \|buyFromState\|string\|Buy from state.\| \|buyFromPostCode\|string\|Buy from country.\| \|shipToAddressLine1\|string\|Ship to address line 1.\| \|shipToAddressLine2\|string\|Ship to address line 2.\| \|shipToCity\|string\|Ship to city.\| \|shipToCountry\|string\|Ship to country.\| \|shipToState\|string\|Ship to state.\| \|shipToPostCode\|string\|Ship to post code.\| \|payToAddressLine1\|string\|Pay to address line 1.\| \|payToAddressLine2\|string\|Pay to address line 2.\| \|payToCity\|string\|Pay to address line 2.\| \|payToCountry\|string\|Pay to country.\| \|payToState\|string\|Pay to state.\| \|payToPostCode\|string\|Pay to post code.\| \|currencyCode\|string\|The default currency code for the purchase receipt.\| \|lastModifiedDateTime\|datetime\|The last datetime the purchase receipt was modified. Read-Only.\| ## JSON representation Here is a JSON representation of the purchaseReceipt resource. ```json { "id": "GUID", "number": "string", "invoiceDate": "date", "postingDate": "date", "dueDate": "date", "vendorNumber": "string", "vendorName": "string", "payToName": "string", "payToContact": "string", "payToVendorNumber": "string", "shipToName": "string", "shipToContact": "string", "buyFromAddressLine1": "string", "buyFromAddressLine2": "string", "buyFromCity": "string", "buyFromCountry": "string", "buyFromState": "string", "buyFromPostCode": "string", "shipToAddressLine1": "string", "shipToAddressLine2": "string", "shipToCity": "string", "shipToCountry": "string", "shipToState": "string", "shipToPostCode": "string", "payToAddressLine1": "string", "payToAddressLine2": "string", "payToCity": "string", "payToCountry": "string", "payToState": "string", "payToPostCode": "string", "currencyCode": "string", "lastModifiedDateTime": "datetime" } ``` <!-- IMPORTANT: END>DO_NOT_EDIT --> ## See Also [GET purchaseReceipt](../api/dynamics_purchaseReceipt_Get.md)	35.330645	194	0.709427	yue_Hant	0.542332
b7dd376f017b96bde9d6d9d38059df20bb66b202	2,432	markdown	Markdown	source/blog/2011-04-08-unbs-new-currie-center-fee.html.markdown	natanrolnik/blog-1	49c6e363da9654cca382ec71199f7ea365b9066f	[ "CC-BY-4.0" ]	1	2019-06-11T16:32:39.000Z	2019-06-11T16:32:39.000Z	source/blog/2011-04-08-unbs-new-currie-center-fee.html.markdown	BalestraPatrick/blog	998319646360d9caaf003c46fbb8df49bea2d0b5	[ "CC-BY-4.0" ]	null	null	null	source/blog/2011-04-08-unbs-new-currie-center-fee.html.markdown	BalestraPatrick/blog	998319646360d9caaf003c46fbb8df49bea2d0b5	[ "CC-BY-4.0" ]	null	null	null	--- title: "UNB's New Currie Center Fee" date: 2011-04-08 00:00 --- When the Conservative government released their budget last month, they capped a tuition increase at $200 because they decided that was all students could afford to pay. They didn't continue the Liberals' tuition freeze, but it could have been worse. However, the previous government had capped "tuition and ancillary fees", not just tuition. The Torries left the "and ancillary fees" out. Based on [how much the Torries appear to care about post-secondary education](/blog/parental-contributions-in-student-loans/), this omission seems to me like more of an oversight and less purposeful policy. At any rate, not capping ancillary fees makes the tuition increase cap effectively meaningless. UNB is planning on instituting a $150 Currie Center Fee at the Board of Governors meeting on Thursday. This almost doubles their $200 tuition increase to $350. An ancillary fee is supposed to provide extra services not currently offered and services not paid for by tuition. The new fee isn't going to be used to offer any new services to students; it's going to be used to cover the operating costs of the university, which is what tuition is used for. The Student Tech Fee is an excellent example of a worthy ancillary fee done right: it's collected from students, and then students have a huge say in how and where that fee is used. The Student Union asked UNB to hold a referendum on this fee, to give students a voice, and they said no. UNB is not willing to talk to students about this because in reality, this fee isn't for students. It's a cash-grab. The problem is, I have a hard time coming up with an alternative plan for the university. UNB is hurting financially; it has been hurting for years and we have a current structural deficit of millions of dollars a year. it can choose to either decrease costs by cutting a faculty, or it can increase revenue. University revenue comes from two main sources: tuition and an operating grant from the provincial government. University expenses are overwhelmingly salary. They can either get more money or fire people, losing our status as a comprehensive university. I hate to sound like a broken record, but this all comes back to the Conservative government. If they had given universities the money they need to operate, they wouldn't need to raise what is the second-highest tuition in Canada. (READMORE)	128	852	0.79523	eng_Latn	0.999931
b7dd986c1f4bd1c41d113c0eb1de8a656bdb945d	1,664	md	Markdown	README.md	banajbedi/topsis_banaj_101916008	445df6c81d65f659d4dbc52b18b77be71494a174	[ "MIT" ]	null	null	null	README.md	banajbedi/topsis_banaj_101916008	445df6c81d65f659d4dbc52b18b77be71494a174	[ "MIT" ]	null	null	null	README.md	banajbedi/topsis_banaj_101916008	445df6c81d65f659d4dbc52b18b77be71494a174	[ "MIT" ]	null	null	null	# TOPSIS Submitted By: Banaj Bedi. Type: Package. Title: TOPSIS method for multiple-criteria decision making (MCDM). Version: 1.1.1. <br> Date: 2022-02-26. <br> Description: Evaluation of alternatives based on multiple criteria using TOPSIS method.. --- ## What is TOPSIS? Technique for Order Preference by Similarity to Ideal Solution (TOPSIS) originated in the 1980s as a multi-criteria decision making method. TOPSIS chooses the alternative of shortest Euclidean distance from the ideal solution, and greatest distance from the negative-ideal solution. <br> ## How to install this package: ``` >> pip install topsis_banaj_101916008 ``` ### In Command Prompt ``` >> topsis data.csv "1,1,2,1,2" "+,+,-,-,+" result.csv ``` ## Input file (data.csv) The decision matrix should be constructed with each row representing a Model alternative, and each column representing a criterion like Accuracy, R<sup>2</sup>, Root Mean Squared Error, Correlation, and many more. ![image](https://user-images.githubusercontent.com/83486603/155836677-32ab8148-315c-42ff-b949-795dc881c059.png) Weights (`weights`) is not already normalised will be normalised later in the code. Information of benefit positive(+) or negative(-) impact criteria should be provided in `impacts`. <br> ## Output file (result.csv) ![image](https://user-images.githubusercontent.com/83486603/155836697-80af34db-ea1c-4deb-9bee-4e6c6be16cb4.png) <br> The output file contains columns of input file along with two additional columns having Topsis_score and Rank View package at: https://pypi.org/project/topsis-banaj-101916008/	27.278689	213	0.735577	eng_Latn	0.885461
b7ddceb5ab1380edb114adeb0c18e76eb82b4135	35	md	Markdown	README.md	akchama/card-match	c5e5a3e0b3eecc2e126001be8257717c4a6479e9	[ "Unlicense" ]	null	null	null	README.md	akchama/card-match	c5e5a3e0b3eecc2e126001be8257717c4a6479e9	[ "Unlicense" ]	null	null	null	README.md	akchama/card-match	c5e5a3e0b3eecc2e126001be8257717c4a6479e9	[ "Unlicense" ]	null	null	null	# card-match Unity game Card Match	11.666667	21	0.771429	eng_Latn	0.942498
b7deb17d543c311373d29ccdd56df1805dd2faab	5,900	md	Markdown	README.md	jaesimin/js-slang	153596c436998e4aa182a61be455febf77eb5510	[ "Apache-2.0" ]	null	null	null	README.md	jaesimin/js-slang	153596c436998e4aa182a61be455febf77eb5510	[ "Apache-2.0" ]	54	2021-05-25T07:15:51.000Z	2022-03-01T07:12:41.000Z	README.md	jaesimin/js-slang	153596c436998e4aa182a61be455febf77eb5510	[ "Apache-2.0" ]	null	null	null	Open-source implementations of the programming language Source. Source is a series of small subsets of JavaScript, designed for teaching university-level programming courses for computer science majors, following Structure and Interpretation of Computer Programs, JavaScript Adaptation (<https://source-academy.github.io/sicp/>). Usage ===== To build, ``` {.} $ git clone https://github.com/source-academy/js-slang.git $ cd js-slang $ yarn $ yarn build ``` To add \"js-slang\" to your PATH, build it as per the above instructions, then run ``` {.} $ cd dist $ npm link ``` If you do not wish to add \"js-slang\" to your PATH, replace \"js-slang\" with \"node dist/repl/repl.js\" in the following examples. To try out Source in a REPL, run ``` {.} $ js-slang -c [chapter] # default: 1 ``` You can set additional options: ``` {.} Usage: js-slang [PROGRAM_STRING] [OPTION] -c, --chapter=CHAPTER set the Source chapter number (i.e., 1-4) (default: 1) -v, --variant=VARIANT set the Source variant (i.e., default, interpreter, substituter, lazy, non-det, concurrent, wasm, gpu) (default: default) -h, --help display this help -e, --eval don't show REPL, only display output of evaluation ``` Currently, valid CHAPTER/VARIANT combinations are: * `--chapter=1 --variant=default` * `--chapter=1 --variant=wasm` * `--chapter=1 --variant=lazy` * `--chapter=1 --variant=substituter` * `--chapter=1 --variant=interpreter` * `--chapter=2 --variant=default` * `--chapter=2 --variant=lazy` * `--chapter=2 --variant=substituter` * `--chapter=2 --variant=interpreter` * `--chapter=3 --variant=default` * `--chapter=3 --variant=concurrent` * `--chapter=3 --variant=non-det` * `--chapter=3 --variant=interpreter` * `--chapter=4 --variant=default` * `--chapter=4 --variant=gpu` * `--chapter=4 --variant=interpreter` Hint: In `bash` you can take the `PROGRAM_STRING` out of a file as follows: ``` {.} $ js-slang -n --chapter=1 -e "$(< my_source_program.js)" ``` Documentation ============= Source is documented here: <https://source-academy.github.io/source/> ## Requirements * `bash`: known working version: GNU bash, version 5.0.16 * `latexmk`: Version 4.52c * `pdflatex`: known working versions * pdfTeX 3.14159265-2.6-1.40.18 (TeX Live 2017) To build the documentation, run ``` {.} $ git clone https://github.com/source-academy/js-slang.git $ cd js-slang $ yarn $ yarn install $ yarn jsdoc # to make the web pages in js-slang/docs/source $ cd docs/source_language_specs $ make # to make the PDF documents using LaTeX ``` Note: The documentation may not build on Windows, depending on your bash setup, [see above](https://github.com/source-academy/js-slang#requirements). Documentation on the Source libraries are generated from inline documentation in the library sources, a copy of which are kept in `docs/lib/.js`. The command `yarn jsdoc` generates the documentation and places it in the folder `docs/source`. The script `jsdoc` provides an installation command to deploy the documentation via `scp` to a web server: ``` {.} $ yarn jsdoc install ``` You can test the documentation using a local server: ``` {.} $ cd docs/source; python -m http.server 8000 ``` Documentation of libraries is displayed in autocomplete in the frontend. This documentation is generated by `./scripts/updateAutocompleteDocs.py` and placed in `src/editors/ace/docTooltip/.json` files. This script is run by `yarn build`prior to`tsc`. To add a Source variant to the frontend autocomplete, edit `src/editors/ace/docTooltip/index.ts` and`./scripts/updateAutocompleteDocs.py`. Testing ======= `js-slang` comes with an extensive test suite. To run the tests after you made your modifications, run `yarn test`. Regression tests are run automatically when you want to push changes to this repository. The regression tests are generated using `jest` and stored as snapshots in `src/\_\_tests\_\_`. After modifying `js-slang`, carefully inspect any failing regression tests reported in red in the command line. If you are convinced that the regression tests and not your changes are at fault, you can update the regression tests as follows: ``` {.} $ yarn test -- --updateSnapshot ``` Error messages ============== To enable verbose messages, have the statement `"enable verbose";` as the first line of your program. This also causes the program to be run by the interpreter. There are two main kinds of error messages: those that occur at runtime and those that occur at parse time. The first can be found in `interpreter-errors.ts`, while the second can be found in `rules/`. Each error subclass will have `explain()` and `elaborate()`. Displaying the error will always cause the first to be called; the second is only called when verbose mode is enabled. As such, `explain()` should be made to return a string containing the most basic information about what the error entails. Any additional details about the error message, including specifics and correction guides, should be left to `elaborate()`. Please remember to write test cases to reflect your added functionalities. The god of this repository is self-professed to be very particular about test cases. Using your js-slang in local Source Academy =========================================== A common issue when developing modifications to js-slang is how to test it using your own local frontend. Assume that you have built your own cadet-frontend locally, here is how you can make it use your own js-slang, instead of the one that the Source Academy team has deployed to npm. First, build and link your local js-slang: ``` {.} $ cd js-slang $ yarn build $ yarn link ``` Then, from your local copy of cadet-frontend: ``` {.} $ cd cadet-frontend $ yarn link "js-slang" ``` Then start the frontend and the new js-slang will be used.	34.104046	340	0.714237	eng_Latn	0.981729
b7df07524dc7420c2aa9f5a5d142df296d4b90ed	632	md	Markdown	README.md	Ideolys/fpark	b68e3003ecc75150c5f49b2032b9d522e37eb636	[ "Apache-2.0" ]	2	2020-07-31T07:41:55.000Z	2020-08-05T07:33:33.000Z	README.md	Ideolys/fpark	b68e3003ecc75150c5f49b2032b9d522e37eb636	[ "Apache-2.0" ]	10	2020-07-31T15:01:08.000Z	2021-11-17T09:25:10.000Z	README.md	Ideolys/fpark	b68e3003ecc75150c5f49b2032b9d522e37eb636	[ "Apache-2.0" ]	null	null	null	# Fpark > File server File server with batteries included : + Clusters + Containers + Authorization + Image compression + Image resizing on the fly + File encryption by design + File replication + Logger (included with rotation) ## Installation ### Node - Get the package ``` npm install fpark ``` - Create a config file ``` vi config.json ``` - Run ``` ./fpark start -c config.json ``` ### Systemd - Install ``` cd /tmp curl https://raw.githubusercontent.com/Ideolys/fpark/master/install.sh \| sudo bash ``` ### Documentation Find answers in [documentation](./doc/README.md) ## License Apache 2.0	11.924528	83	0.672468	eng_Latn	0.767731
b7df47ff38c829c92cffc92e85eb3aa8d2aa20a8	3,362	md	Markdown	README_zh.md	QvodSoldier/erda-infra	b1699f584b1e9a0b6ef6bc16c92200897b0276e1	[ "Apache-2.0" ]	null	null	null	README_zh.md	QvodSoldier/erda-infra	b1699f584b1e9a0b6ef6bc16c92200897b0276e1	[ "Apache-2.0" ]	null	null	null	README_zh.md	QvodSoldier/erda-infra	b1699f584b1e9a0b6ef6bc16c92200897b0276e1	[ "Apache-2.0" ]	null	null	null	# Erda Infra [![License](https://img.shields.io/badge/license-Apache%202-4EB1BA.svg)](https://www.apache.org/licenses/LICENSE-2.0.html) [![codecov](https://codecov.io/gh/erda-project/erda-infra/branch/develop/graph/badge.svg?token=SVROJLY8UK)](https://codecov.io/gh/erda-project/erda-infra) 翻译: [English](README.md) \| [简体中文](README_zh.md) Erda Infra 一套轻量级 Go 微服务框架，包含大量现成的模块和工具，能够快速构建起以模块化驱动的应用程序。一些 Go 项目基于该框架进行构建: * [Erda](https://github.com/erda-project/erda) ## 特性 * 以模块化设计方式来驱动应用系统实现，支持模块可插拔 * 统一配置读取，支持默认值、支持从文件、环境变量、命令行参数读取 * 统一模块的初始化、启动、关闭 * 统一管理模块间的依赖关系 * 支持模块间的依赖注入 * 包含大量现成的微模块 * 支持统一 gRPC 和 HTTP 接口设计、以及拦截器 * 提供快速构建模块的脚本 * 等等 ## 概念 * Service，服务，表示某个具体的功能 * Provider，服务的提供者，提供0个或多个 Service，也可以依赖0个或多个其他 Service，被依赖的 Service 由其他 Provider 提供 * ProviderDefine，提供 Provider 相关的元信息，比如：提供 Provider 的构造函数。通过 servicehub.RegisterProvider 来注册 Provider * Hub，是所有 Provider 的容器，管理所有已加载的 Provider 的生命周期所有已注册的 Provider 通过一份配置来确定是否加载，由 Hub 对已加载的 Provider 的进行初始化、启动、关闭等。 ![servicehub](./docs/servicehub.jpg) ## Provider 定义通过实现 servicehub.ProviderDefine 接口来定义一个模块，并通过 servicehub.RegisterProvider 函数进行注册。但更简单的是通过 servicehub.Spec 来描述一个模块，并通过 servicehub.Register 函数进行注册。 [例子](./base/servicehub/examples) ## Quick Start ```sh ➜ # create service interface ➜ ROOT_PATH=$(pwd) ➜ ${ROOT_PATH}/tools/protoc.sh protocol "examples/protocol/.proto" ➜ ➜ # create module ➜ mkdir -p examples/server/helloworld ➜ cd examples/server/helloworld ➜ ${ROOT_PATH}/tools/protoc.sh init "${ROOT_PATH}/examples/protocol/.proto" ➜ ➜ # implement the service interface in examples/server/helloworld directory ➜ ➜ cd ${ROOT_PATH}/examples/server ➜ ➜ # create main.go, like examples/server/main.go ➜ # create server.yaml, like examples/server/server.yaml ➜ ➜ go run main.go ``` [Hello World](./examples) $ [Server](./examples/server) \| [Client](./examples/client) $ ## 微模块该项目中已经封装了许多可用的模块，在 [providers/](./providers) 目录下可以找到。每一个模块下面，都有一个 examples 目录，包含了该模块的使用例子。 * elasticsearch，对 elasticsearch 客户端的封装，更方便的进行批量数据的写入 * etcd，对 etcd 客户端的封装 * etcd-mutex，利用 etcd 实现的分布式锁 * grpcserver，启动一个 gRPC server * grpcclient，统一管理 gRPC 客户端 * health，通过 httpserver 注册一个健康检查的接口 * httpserver，提供一个 HTTP server, 支持任意形式的处理函数、拦截器、参数绑定、参数校验等 * i18n，提供了国际化的支持，可以统一管理国际化文件、支持模版 * kafka，提供了访问 kafka 相关的能力，更方便地去批量消费和推送消息 * kubernetes，对 kubernetes 客户端的封装 * mysql，对 mysql 客户端的封装 * pprof，通过 httpserver 注册一些 pprof 相关的接口 * redis，对 redis 客户端的封装 * zk-master-election，通过 zookeeper 实现主从选举 * zookeeper，对 zookeeper 客户端的封装 * cassandra，对 Cassandra 客户端的封装 * serviceregister，封装提供统一注册 gRPC 和 HTTP 接口的能力 # 工具 protoc-gen-go-* 系列工具依赖 protobuf 编译器，参考 [protobuf](https://github.com/protocolbuffers/protobuf) 项目进行安装。也可以通过 Docker 容器来使用以下工具。 ```sh docker run --rm -ti -v $(pwd):/go \ registry.cn-hangzhou.aliyuncs.com/dice/erda-tools:1.0 protoc.sh usage ``` * protoc-gen-go-grpc，根据 .proto 文件，提供 gRPC server 和 client 支持 protoc-gen-go-http，根据 .proto 文件，对定义的 Service 提供 HTTP server 支持 protoc-gen-go-form，根据 .proto 文件，对定义的 Message 提供 HTTP form 编解码的支持 protoc-gen-go-client，根据 .proto 文件，编译统一的客户端，以及对应的 Provider protoc-gen-go-register，方便 Provider 注册 Service * protoc-gen-go-provider，根据 .proto 文件，生成实现 Service 的 Provider 模版，方便快速开发模块 protoc.sh，针对 protoc-gen-go-* 系列工具的封装，方便 Service 模块的开发 ## License Erda Infra is under the Apache 2.0 license. See the [LICENSE](/LICENSE) file for details.	31.420561	154	0.756098	yue_Hant	0.559966
b7df5dec5c8e8ffb13a932e080e70a98afe9b8c9	161	md	Markdown	docs/DG/ItemTextLengthLimitProperty.md	graphisoft-python/DGLib	66d8717eb4422b968444614ff1c0c6c1bf50d080	[ "Apache-2.0" ]	3	2019-07-15T10:54:54.000Z	2020-01-25T08:24:51.000Z	docs/DG/ItemTextLengthLimitProperty.md	graphisoft-python/DGLib	66d8717eb4422b968444614ff1c0c6c1bf50d080	[ "Apache-2.0" ]	null	null	null	docs/DG/ItemTextLengthLimitProperty.md	graphisoft-python/DGLib	66d8717eb4422b968444614ff1c0c6c1bf50d080	[ "Apache-2.0" ]	null	null	null	# Class ItemTextLengthLimitProperty ## Inherit * [ItemBase](ItemBase.md) ## Methods ``` SetMaxTextLength(self, int) -> None GetMaxTextLength(self) -> int ```	13.416667	35	0.708075	yue_Hant	0.908083
b7e00fa2a732bcbb1752d7ca5f50307de6ba76a3	6,320	md	Markdown	README.md	tecruz/AndroidBaseAppKotlinMvvm	190c850f82905ddfee73d02f7c8f4186b24006c5	[ "Apache-2.0" ]	null	null	null	README.md	tecruz/AndroidBaseAppKotlinMvvm	190c850f82905ddfee73d02f7c8f4186b24006c5	[ "Apache-2.0" ]	null	null	null	README.md	tecruz/AndroidBaseAppKotlinMvvm	190c850f82905ddfee73d02f7c8f4186b24006c5	[ "Apache-2.0" ]	1	2018-06-06T00:36:41.000Z	2018-06-06T00:36:41.000Z	# AndroidBaseAppKotlinMvvm Base reference for new Android projects (Kotlin&MVVM) [![Android CI](https://github.com/tecruz/AndroidBaseAppKotlinMvvm/actions/workflows/main.yml/badge.svg?branch=master)](https://github.com/tecruz/AndroidBaseAppKotlinMvvm/actions/workflows/main.yml) [![codecov](https://codecov.io/gh/tecruz/AndroidBaseAppKotlinMvvm/branch/master/graph/badge.svg)](https://codecov.io/gh/tecruz/AndroidBaseAppKotlinMvvm) [![Codacy Badge](https://api.codacy.com/project/badge/Grade/171640011f3749d19a8de24877237522)](https://app.codacy.com/app/tecruz/AndroidBaseAppKotlinMvvm?utm_source=github.com&utm_medium=referral&utm_content=tecruz/AndroidBaseAppKotlinMvvm&utm_campaign=badger) ![Alt text](screen.png?raw=true) You need to supply API keys for the various services the app uses. - Movie Db: https://developers.themoviedb.org/3 - Firebase: https://firebase.google.com/docs/crashlytics/get-started?platform=Android When you obtain the keys, you can provide them to the app by putting the following in the `local.properties` project root file: ```properties #Movie db API KEY movie.api.key=<insert> Firebase Include generated json file on your project ``` Moreover, to sign your app for release you should generate an upload key and keystore following the [official documentation](https://developer.android.com/studio/publish/app-signing#sign-apk). Append the information used to generate it into `local.properties` project root file following the structure: ```properties #Signing Config signing.key.alias = <insert> signing.key.password = <insert> signing.store.file = <insert> signing.store.password = <insert> ``` Libraries and tools included: - [Jetpack](https://developer.android.com/jetpack): - [Android KTX](https://developer.android.com/kotlin/ktx.html) - provide concise, idiomatic Kotlin to Jetpack and Android platform APIs. - [AndroidX](https://developer.android.com/jetpack/androidx) - major improvement to the original Android [Support Library](https://developer.android.com/topic/libraries/support-library/index), which is no longer maintained. - [Benchmark](https://developer.android.com/studio/profile/benchmark.html) - handles warmup, measures your code performance, and outputs benchmarking results to the Android Studio console. - [Data Binding](https://developer.android.com/topic/libraries/data-binding/) - allows you to bind UI components in your layouts to data sources in your app using a declarative format rather than programmatically. - [Lifecycle](https://developer.android.com/topic/libraries/architecture/lifecycle) - perform actions in response to a change in the lifecycle status of another component, such as activities and fragments. - [LiveData](https://developer.android.com/topic/libraries/architecture/livedata) - lifecycle-aware, meaning it respects the lifecycle of other app components, such as activities, fragments, or services. - [Navigation](https://developer.android.com/guide/navigation/) - helps you implement navigation, from simple button clicks to more complex patterns, such as app bars and the navigation drawer. - [Paging](https://developer.android.com/topic/libraries/architecture/paging/) - helps you load and display small chunks of data at a time. Loading partial data on demand reduces usage of network bandwidth and system resources. - [Room](https://developer.android.com/topic/libraries/architecture/room) - persistence library provides an abstraction layer over SQLite to allow for more robust database access while harnessing the full power of SQLite. - [ViewModel](https://developer.android.com/topic/libraries/architecture/viewmodel) - designed to store and manage UI-related data in a lifecycle conscious way. The ViewModel class allows data to survive configuration changes such as screen rotations. - [Coroutines](https://kotlinlang.org/docs/reference/coroutines-overview.html) - managing background threads with simplified code and reducing needs for callbacks. - [Dagger2](https://dagger.dev/) - dependency injector for replacement all FactoryFactory classes. - [Retrofit](https://square.github.io/retrofit/) - type-safe HTTP client. - [Coil](https://github.com/coil-kt/coil) - image loading library for Android backed by Kotlin Coroutines. - [Moshi](https://github.com/square/moshi) - makes it easy to parse JSON into Kotlin objects. - [Timber](https://github.com/JakeWharton/timber) - a logger with a small, extensible API which provides utility on top of Android's normal Log class. - [Stetho](http://facebook.github.io/stetho/) - debug bridge for applications via Chrome Developer Tools. ### Test dependencies - [UIAutomator](https://developer.android.com/training/testing/ui-automator) - a UI testing framework suitable for cross-app functional UI testing across system and installed apps. - [Espresso](https://developer.android.com/training/testing/espresso) - to write concise, beautiful, and reliable Android UI tests - [Robolectric](https://github.com/robolectric/robolectric) - industry-standard unit testing framework for Android. - [JUnit](https://github.com/junit-team/junit4) - a simple framework to write repeatable tests. It is an instance of the xUnit architecture for unit testing frameworks. - [Mockk](https://github.com/mockk/mockk) - provides DSL to mock behavior. Built from zero to fit Kotlin language. - [AndroidX](https://github.com/android/android-test) - the androidx test library provides an extensive framework for testing Android apps. ### Plugins - [Ktlint](https://github.com/pinterest/ktlint) - an anti-bikeshedding Kotlin linter with built-in formatter. - [Detekt](https://github.com/arturbosch/detekt) - a static code analysis tool for the Kotlin programming language. - [Spotless](https://github.com/diffplug/spotless) - a code formatter can do more than just find formatting errors. - [Versions](https://github.com/ben-manes/gradle-versions-plugin) - make easy to determine which dependencies have updates. - [SafeArgs](https://developer.android.com/guide/navigation/navigation-pass-data#Safe-args) - generates simple object and builder classes for type-safe navigation and access to any associated arguments. - [Jacoco](https://github.com/jacoco/jacoco) - code coverage library	85.405405	302	0.778323	eng_Latn	0.761403
b7e013c713e2a1ae8f37facf854e4d00f0527a91	2,457	md	Markdown	README.md	dsurgeons/glacier-backup	5dbe844a172b0065b7402a80d35298151017966b	[ "MIT" ]	1	2016-08-15T20:38:12.000Z	2016-08-15T20:38:12.000Z	README.md	dsurgeons/glacier-backup	5dbe844a172b0065b7402a80d35298151017966b	[ "MIT" ]	null	null	null	README.md	dsurgeons/glacier-backup	5dbe844a172b0065b7402a80d35298151017966b	[ "MIT" ]	null	null	null	# Glacier Backup This program builds on Amazon's own boto3 library for enabling backups to Amazon Glacier, while also maintaining a local, rotated copy using the excellent archive-rotator package to implement the generalized grandfather-father-son rotation methodology. Single files or directories are accepted, where directories are recursively tar'ed and compression is optional via the lzma xz format, which has excellent compression ratio and fast decompression speed. ## Usage The script is intended to run on a periodic basis via cron, [systemd timers](https://wiki.archlinux.org/index.php/Systemd/Timers), or any other scheduling mechanism. It is intended to run daily, and will keep local copies for 7 days, 4 weeks, and 12 months (technically, 4 7-day intervals and 12 4-week intervals). However, you can run it more often, just be aware that if you set it up eg. hourly, then the second tier of updates will be 7 hour intervals, and the third will be 4 7-hour intervals. In the future this may become configurable via commandline flags. Feel free to pull request. Here is an example invocation with cron executing every day at 1am, archiving and compressing the `/var/www/example.com` directory and saving it locally in `/backups/` under rotation. You can use [crontab-generator.org](http://crontab-generator.org/) to generate other configurations. 0 1 * * * /usr/local/glacer-backup --compress /var/www/example.com /backups/ You can use `glacier-backup --help` to view the options available to you. ## Tasks for getting information on uploaded vaults: ### Begin a vault inventory task: ``` aws glacier initiate-job --account-id - --vault-name my-vault --job-parameters '{"Type": "inventory-retrieval"}' ``` Make sure to replace vault-name with the name of your vault ### Check on a vault inventory task ``` aws glacier describe-job --account-id - --vault-name my-vault --job-id qtjE_VcVXWojWR9UkmTJ1kvtAzyRABKk3c2OYGD8HcC40X7K7LvhZxjZ-2X71TaH5LR5byKaXk_ONURpa2RG_kBQ2AHj ``` Replace the argument for the job ID you were passed in the first command, and replace the vault name with your vault name ### Get the result of a vault inventory task ``` aws glacier get-job-output --account-id - --vault-name my-vault --job-id zbxcm3Z_3z5UkoroF7SuZKrxgGoDc3RloGduS7Eg-RO47Yc6FxsdGBgf_Q2DK5Ejh18CnTS5XW4_XqlNHS61dsO4CnMW output.json ``` Replace the argument for the job ID you were passed in the first command, and replace the vault	59.926829	591	0.781441	eng_Latn	0.991728
b7e0a90f4c573197097fe9f9f87b88049a6d99e4	58	md	Markdown	content/author/johh/.meta.md	jonathan0902/Anax-Flat	dd73ed282eac2f70108b221df2de2a8438ca442e	[ "MIT" ]	null	null	null	content/author/johh/.meta.md	jonathan0902/Anax-Flat	dd73ed282eac2f70108b221df2de2a8438ca442e	[ "MIT" ]	null	null	null	content/author/johh/.meta.md	jonathan0902/Anax-Flat	dd73ed282eac2f70108b221df2de2a8438ca442e	[ "MIT" ]	null	null	null	--- name: Jonathan Hellberg mail: [email protected] ...	11.6	25	0.706897	vie_Latn	0.147534
b7e0b69b72bca947e9c4a37e46f596e0a568d978	5,856	md	Markdown	articles/supply-chain/master-planning/planning-optimization/infinite-capacity-planning.md	MicrosoftDocs/Dynamics-365-Operations.fr-fr	9f97b0553ee485dfefc0a57ce805f740f4986a7e	[ "CC-BY-4.0", "MIT" ]	2	2020-05-18T17:14:08.000Z	2021-04-20T21:13:46.000Z	articles/supply-chain/master-planning/planning-optimization/infinite-capacity-planning.md	MicrosoftDocs/Dynamics-365-Operations.fr-fr	9f97b0553ee485dfefc0a57ce805f740f4986a7e	[ "CC-BY-4.0", "MIT" ]	6	2017-12-13T18:31:58.000Z	2019-04-30T11:46:19.000Z	articles/supply-chain/master-planning/planning-optimization/infinite-capacity-planning.md	MicrosoftDocs/Dynamics-365-Operations.fr-fr	9f97b0553ee485dfefc0a57ce805f740f4986a7e	[ "CC-BY-4.0", "MIT" ]	1	2019-10-12T18:19:20.000Z	2019-10-12T18:19:20.000Z	--- title: Planification avec une capacité infinie description: Cette rubrique fournit des informations sur la planification de capacité infinie pour Planning Optimization. Elle décrit également les limitations actuelles des fonctionnalités. author: ChristianRytt ms.date: 09/21/2021 ms.topic: article ms.search.form: RouteInventProd audience: Application User ms.reviewer: kamaybac ms.search.region: Global ms.author: crytt ms.search.validFrom: 2021-06-09 ms.dyn365.ops.version: 10.0.22 ms.openlocfilehash: 9c1eef91bcf7d1ce6379e87417be5a8b3be069e5 ms.sourcegitcommit: 3b87f042a7e97f72b5aa73bef186c5426b937fec ms.translationtype: HT ms.contentlocale: fr-FR ms.lasthandoff: 09/29/2021 ms.locfileid: "7575630" --- # <a name="scheduling-with-infinite-capacity"></a>Planification avec une capacité infinie [!include [banner](../../includes/banner.md)] [!INCLUDE [preview-banner](../../includes/preview-banner.md)] La fonctionnalité Planification de capacité infinie pour Planning Optimization introduit une planification basée sur les informations d’itinéraire. Elle vous permet de planifier des tâches en fonction d’un large éventail de configurations d’itinéraires. La planification de Planning Optimization couvre les paramètres d’itinéraire fréquemment utilisés, y compris la séquence d’opérations d’itinéraire ou les exigences pour les ressources d’opérations d’itinéraire. ## <a name="turn-on-the-infinite-capacity-scheduling-feature"></a>Activer la fonction de planification de capacité infinie Avant de pouvoir utiliser cette fonctionnalité, vous devez l’activer sur votre système. Les administrateurs peuvent utiliser les paramètres de [gestion des fonctionnalités](../../../fin-ops-core/fin-ops/get-started/feature-management/feature-management-overview.md) pour vérifier le statut de la fonctionnalité et l’activer si nécessaire. Dans l’espace de travail Gestion des fonctionnalités, la fonctionnalité est répertoriée comme suit : - Module : Planification - Nom de la fonctionnalité : Planification des capacités infinies pour l’optimisation de la planification Pour plus d’informations sur cette fonctionnalité, voir [Planification avec sélection des ressources en fonction des capacités](capability-based-scheduling.md). ## <a name="added-functionality"></a>Fonctionnalité ajoutée La fonctionnalité Planification des capacités infinies pour Planning Optimization introduit une planification basée sur les informations d’itinéraire. Par conséquent, une configuration d’itinéraire peut être utilisée pour planifier les processus de production. Bien que cette fonctionnalité présente certaines limitations que la planification principale intégrée n’a pas, elle prend en charge la fonctionnalité la plus courante requise pour les scénarios de fabrication. La fonctionnalité considère à la fois les itinéraires simples et les réseaux d’itinéraires. En utilisant le champ Suivant sur une opération d’itinéraire, vous pouvez configurer des itinéraires complexes qui ont plusieurs points de départ et plusieurs opérations qui s’exécutent en parallèle. Le système prendra en compte les structures d’itinéraires complexes de ce type lors de la planification. De plus, la fonctionnalité prend en charge les opérations parallèles dans les itinéraires. En utilisant les options Principal et Secondaire dans le champ Priorité sur les opérations d’itinéraire, vous pouvez définir une structure d’itinéraire dans laquelle une opération d’itinéraire est l’opération principale et une autre opération est secondaire. Dans ce cas, le système prendra en compte la structure d’itinéraire lors de la planification. Au cours du processus de planification, le système prend également en compte les besoins en ressources qui sont spécifiés pour une opération. Le système utilise les besoins en ressources pour déterminer quelles ressources sont requises pour effectuer l’opération. Actuellement, la fonctionnalité Planification des capacités infinies pour l’optimisation de la planification prend en charge les types de besoins en ressources suivants : - Type de ressource - Ressource - Groupe de ressources - Capacité (Pour plus d’informations, voir [Planification avec sélection des ressources en fonction des capacités](capability-based-scheduling.md).) > [!NOTE] > Les exigences liées aux ressources humaines, telles que les compétences ou les exigences de certificat, ne sont pas encore prises en charge. La fonctionnalité prend également en charge les propriétés opérationnelles Temps de configuration et Durée. Lorsque vous définissez ces propriétés sur une opération d’itinéraire, le processus de planification crée les tâches de configuration et de traitement appropriées. En résumé, la planification de Planning Optimization prend en charge les scénarios les plus fréquemment utilisés. Vous pouvez créer l’itinéraire, ajouter des opérations principales et secondaires, définir les opérations suivantes, ajouter des besoins en ressources et ajouter une durée de configuration et une durée d’exécution. Le système prendra alors en compte ces informations lors de la planification. ## <a name="limitations"></a>Limitations Les limitations suivantes s’appliquent lorsque vous utilisez la planification pour Planning Optimization : - La fonctionnalité ne prend en charge qu’une capacité infinie. - La fonctionnalité ne prend pas en charge la fonctionnalité de chargement de ressources. - La fonctionnalité ne prend pas en compte les rebuts d’itinéraire. - La fonctionnalité prend en charge la Durée uniquement comme sélection de ressource principale. Notez que la fonctionnalité Planification de capacité infinie pour Planning Optimization est constamment améliorée. Microsoft prévoit d’introduire la prise en charge de paramètres de planification supplémentaires dans les prochaines versions.	84.869565	472	0.818477	fra_Latn	0.98596
b7e118a48ab4e8416589662c473340abae22bdc2	11,324	md	Markdown	docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks_stack_hci/aks_hci_gitops_basic/_index.md	dankuchem/azure_arc	c11d557f0558e130cd01eb4c85261745fc04c018	[ "CC-BY-4.0", "MIT" ]	1	2021-07-04T03:44:51.000Z	2021-07-04T03:44:51.000Z	docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks_stack_hci/aks_hci_gitops_basic/_index.md	QPC-database/azure_arc	148e952fa517c9a583c9ff0a28486791a14e5126	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks_stack_hci/aks_hci_gitops_basic/_index.md	QPC-database/azure_arc	148e952fa517c9a583c9ff0a28486791a14e5126	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- type: docs title: "Deploy GitOps configurations and perform basic GitOps flow on AKS on Azure Stack HCI as an Azure Arc Connected Cluster" linkTitle: "Deploy GitOps configurations and perform basic GitOps flow on AKS on Azure Stack HCI as an Azure Arc Connected Cluster" weight: 1 description: > --- ## Deploy GitOps configurations and perform basic GitOps flow on AKS on Azure Stack HCI as an Azure Arc Connected Cluster The following README will guide you on how to create GitOps configuration on an Azure Kubernetes Service (AKS) cluster that is running on Azure Stack HCI and which is projected as an Azure Arc connected cluster resource. In this guide, you will deploy & attach GitOps configuration to your cluster which will also include deploying an "Hello World" Azure Arc web application on your Kubernetes cluster. By doing so, you will be able to make real-time changes to the application and show how the GitOps flow takes effect. > Note: This guide assumes you already deployed an AKS cluster on Azure Stack HCI and connected it to Azure Arc. If you haven't, this repository offers you a way to do so in an automated fashion using [PowerShell](https://azurearcjumpstart.io/azure_arc_jumpstart/azure_arc_k8s/aks_stack_hci/aks_hci_powershell/). ## Prerequisites * Clone the Azure Arc Jumpstart repository ```shell git clone https://github.com/microsoft/azure_arc.git ``` * Fork the ["Hello Arc"](https://github.com/likamrat/hello_arc) demo application repository. * (Optional) Install the "Tab Auto Refresh" extension for your browser. This will help you to show the real-time changes on the application in an automated way. * [Microsoft Edge](https://microsoftedge.microsoft.com/addons/detail/odiofbnciojkpogljollobmhplkhmofe) * [Google Chrome](https://chrome.google.com/webstore/detail/tab-auto-refresh/jaioibhbkffompljnnipmpkeafhpicpd?hl=en) * [Mozilla Firefox](https://addons.mozilla.org/en-US/firefox/addon/tab-auto-refresh/) * As mentioned, this guide starts at the point where you already have a connected AKS cluster to Azure Arc that is running on Azure Stack HCI. ![Existing Azure Arc enabled Kubernetes cluster](./01.png) ![Existing Azure Arc enabled Kubernetes cluster](./02.png) * [Install or update Azure PowerShell modules](https://docs.microsoft.com/en-us/powershell/azure/install-az-ps?view=azps-5.6.0). Use the below command to check your current installed version. ```PowerShell Get-InstalledModule -Name Az -AllVersions \| select Name,Version ``` > Note: This guide combines automations that uses both Azure PowerShell Az modules as well as Azure CLI, however both of them can and will be run from a PowerShell window. * [Install or update Azure CLI to version 2.15.0 and above](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest). Use the below command to check your current installed version. ```shell az --version ``` * Enable subscription with the two resource providers for Azure Arc enabled Kubernetes. Registration is an asynchronous process, and registration may take approximately 10 minutes. ```PowerShell Register-AzResourceProvider -ProviderNamespace Microsoft.Kubernetes Register-AzResourceProvider -ProviderNamespace Microsoft.KubernetesConfiguration ``` You can monitor the registration process with the following commands: ```PowerShell Get-AzResourceProvider -ProviderNamespace Microsoft.Kubernetes Get-AzResourceProvider -ProviderNamespace Microsoft.KubernetesConfiguration ``` * Create Azure service principal (SP) To be able to complete the scenario and its related automation, an Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below PowerShell command. ```powershell Connect-AzAccount $sp = New-AzADServicePrincipal -DisplayName "<Unique SP Name>" -Role 'Contributor' ``` For example: ```powershell $sp = New-AzADServicePrincipal -DisplayName "<Unique SP Name>" -Role 'Contributor' ``` This command will return a secure string as shown below: ```shell Secret : System.Security.SecureString ServicePrincipalNames : {XXXXXXXXXXXXXXXXXXXXXXXXXXXX, http://AzureArcK8s} ApplicationId : XXXXXXXXXXXXXXXXXXXXXXXXXXXX ObjectType : ServicePrincipal DisplayName : AzureArcK8s Id : XXXXXXXXXXXXXXXXXXXXXXXXXXXX Type : ``` To expose the generated password use this code to export the secret: ```powershell $BSTR = [System.Runtime.InteropServices.Marshal]::SecureStringToBSTR($sp.Secret) $UnsecureSecret = [System.Runtime.InteropServices.Marshal]::PtrToStringAuto($BSTR) ``` > Note: It is optional but highly recommended to scope the SP to a specific [Azure subscription and resource group](https://docs.microsoft.com/en-us/powershell/module/az.resources/new-azadserviceprincipal?view=azps-5.4.0) * If you do not have the AksHci PowerShell module already, you will have to perform a clean installation. To install the AksHci PowerShell module remove any previous versions by running the below commands: ```powershell Install-Module -Name Az.Accounts -Repository PSGallery -RequiredVersion 2.2.4 Install-Module -Name Az.Resources -Repository PSGallery -RequiredVersion 3.2.0 Install-Module -Name AzureAD -Repository PSGallery -RequiredVersion 2.0.2.128 Install-Module -Name AksHci -Repository PSGallery Import-Module Az.Accounts Import-Module Az.Resources Import-Module AzureAD Import-Module AksHci Exit ``` * After this is done, close all PowerShell windows and verify the installation by tunning the following: ```powershell Get-Command -Module AksHci ``` ![Screenshot AksHci module installation](./03.png) ## Automation Flow For you to get familiar with the automation and deployment flow, below is an explanation. * User is editing the PowerShell script environment variables (1-time edit). These variables values are being used throughout the deployment of the Kubernetes GitOps configuration. * User is running the PowerShell script to enable and set up a GitOps configuration. Runtime script will: * Login to your Azure subscription using the SPN credentials. * Retrieve the cluster credentials (KUBECONFIG). * Use Helm to deploy NGINX ingress controller. * Create the GitOps configurations and deploy the Flux operator and Memcached on the Azure Arc connected cluster. * Deploy the ["Hello Arc"](https://github.com/likamrat/hello_arc) application along side an Ingress rule to make it available from outside the cluster. * User will kick the GitOps flow by making changes to the ["Hello Arc"](https://github.com/likamrat/hello_arc) application, this will be considered a new version by the Flux Operator. * The GitOps flow will pull the new version of the application and deploy new pods, upon committing the changes. * User will show rolling upgrade of the "Hello Arc" application as the GitOps flow is completed successfully. ## Azure Arc Kubernetes GitOps Configuration * Edit the environment variables in the [az_k8sconfig_aks_hci](https://github.com/microsoft/azure_arc/blob/main/azure_arc_k8s_jumpstart/aks_stack_hci/gitops/basic/az_k8sconfig_aks_hci.ps1) PowerShell script to match your parameters and run it using the ```.\az_k8sconfig_aks_hci.ps1``` command. > *Disclaimer: For the purpose of this guide, notice how the "git-poll-interval 3s" is set. The 3 seconds interval is useful for demo purposes since it will make the git-poll interval to rapidly track changes on the repository but it is recommended to have longer interval in your production environment (default value is 5min)* * Once the script will complete it's run, you will have the GitOps configuration created and all the resources deployed in your Kubernetes cluster running on Azure Stack HCI. > Note: that it takes few min for the configuration change it's Operator state status from "Pending" to Install. ![New GitOps configurations](./04.png) ![New GitOps configurations](./05.png) ![New GitOps configurations](./06.png) ## The "Hello Arc" Application & Components * Before kicking the GitOps flow, let's review the Kubernetes resources deployed by running few kubectl commands. * ```kubectl get pods -n prod``` - Will show the Flux operator, the Memcached pods and the "Hello Arc" application pods. * ```kubectl get pods -n cluster-mgmt``` - Will show the NGINX controller. * ```kubectl get svc -n prod``` - Will show NGINX controller Kubernetes Service (Type LoadBalancer). * ```kubectl get ing -n prod``` - Will show NGINX rule which will route the traffic to the "Hello Arc" application from outside the cluster. ![kubectl get pods -n prod](./07.png) ![kubectl get pods -n cluster-mgmt](./08.png) ![kubectl get svc -n prod](./09.png) ![kubectl get ing -n prod](./10.png) * The GitOps flow works as follow: 1. The Flux operator holds the "desired state" of the "Hello Arc" application, this are the configuration we deployed against the Azure Arc connected cluster. The operator "pulls" the state of the ["Hello Arc"](https://github.com/likamrat/hello_arc) application repository. 2. Changing the application which is consider to be a new version of it, will trigger the Flux operator to kick-in the GitOps flow. 3. A new Kubernetes pod with the new version of the application will be deployed on the cluster. Once the new pods is successfully deployed, the old one will be terminated (rolling upgrade). * To show the above flow, open 2 (ideally 3) side-by-side browser windows: * Run ```kubectl get pods -n prod -w``` command ![kubectl get pods -n prod -w](./11.png) * Your fork of the "Hello Arc" application repository. Open the [hello_arc.yaml](https://github.com/likamrat/hello_arc/blob/master/yaml/hello_arc.yaml) file. * The IP address of the Kubernetes Service seen using the ```kubectl get svc -n prod``` command. ![kubectl get svc -n prod](./12.png) * End result should look like that: ![Side-by-side view of terminal, "Hello Arc" GitHub repo and the application open in a web browser](./13.png) * As mentioned in the prerequisites section, it is optional but very recommended to configure the "Tab Auto Refresh" extension for your browser. If you did, in the "Hello Arc" application window, configure it to refresh every 2 seconds. ![Tab Auto Refresh](./14.png) * In the repository window showing the hello_arc.yaml file, change the text under "MESSAGE" section commit the change. Alternatively, you can open the fork repository in your IDE, make the change, commit and push it. ![Making a change to the "MESSAGE" section](./15.png) ![Making a change to the "MESSAGE" section and committing](./16.png) * Upon committing the changes, notice how the Kubernetes Pod rolling upgrade starts. Once the Pod is up & running, the new "Hello Arc" application version window will show the new message, showing the rolling upgrade is completed and the GitOps flow is successful. ![New Side-by-side view of terminal, "Hello Arc" GitHub repo and the application open in a web browser](./17.png)	52.425926	336	0.753886	eng_Latn	0.941999
b7e12e2dbd46c064c9acf4d724d0195a938a70cd	339	md	Markdown	README.md	HRausch16/health-insurance-risk-calculator	44ec6a55097a1f7a551135788d0899ed94fa930d	[ "MIT" ]	null	null	null	README.md	HRausch16/health-insurance-risk-calculator	44ec6a55097a1f7a551135788d0899ed94fa930d	[ "MIT" ]	null	null	null	README.md	HRausch16/health-insurance-risk-calculator	44ec6a55097a1f7a551135788d0899ed94fa930d	[ "MIT" ]	null	null	null	# health-insurance-risk-calculator Repository for "Health Insurance Risk Calculator Assignment" Name: Hannah Rausch Project: Health Insurance Risk Calculator Lewis Email: [email protected] All information is my own. Execution instructions: Open HTML file (index.html) with any browser window. Required files: index.html, index.css	33.9	76	0.820059	eng_Latn	0.725832
b7e14b4c2923da67a409941820a11bd7e7c2723d	14,172	md	Markdown	windows-driver-docs-pr/audio/wave-filters.md	scottnoone/windows-driver-docs	0d67834ab63cf2a8993bccdea23d1b0186a4aec6	[ "CC-BY-4.0", "MIT" ]	1	2021-11-30T20:31:06.000Z	2021-11-30T20:31:06.000Z	windows-driver-docs-pr/audio/wave-filters.md	scottnoone/windows-driver-docs	0d67834ab63cf2a8993bccdea23d1b0186a4aec6	[ "CC-BY-4.0", "MIT" ]	null	null	null	windows-driver-docs-pr/audio/wave-filters.md	scottnoone/windows-driver-docs	0d67834ab63cf2a8993bccdea23d1b0186a4aec6	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- title: Wave Filters description: Wave Filters ms.assetid: 9e364c8f-55c3-4ec9-a9ce-9ee0f6a0746b keywords: - audio filters WDK audio , wave - wave filters WDK audio - filters WDK audio , wave - wave-rendering filters WDK audio - wave-capture filters WDK audio - rendering wave audio WDK audio - capturing wave audio WDK audio - WaveRT filters WDK audio - WavePci filters WDK audio - WaveCyclic filters WDK audio - WaveRT, filter - WavePci, filter - audio devices, WaveCyclic - WaveCyclic, filter ms.date: 05/08/2018 ms.localizationpriority: medium --- # Wave Filters ## <span id="wave_filters"></span><span id="WAVE_FILTERS"></span> Wave filters represent devices that render and/or capture wave-formatted digital audio data. Applications typically access the capabilities of these devices either through the DirectSound API or through the Microsoft Windows multimedia waveOutXxx and waveInXxx functions. For information about the wave formats that WDM audio drivers can support, see [WAVEFORMATEX](/windows/desktop/api/mmreg/ns-mmreg-twaveformatex) and [WAVEFORMATEXTENSIBLE](/windows-hardware/drivers/ddi/ksmedia/ns-ksmedia-waveformatextensible). A wave-rendering filter receives as input a wave digital audio stream and outputs either an analog audio signal (to a set of speakers or external mixer) or a digital audio stream (to an S/PDIF connector, for example). A wave-capture filter receives as input either an analog audio signal (from a microphone or input jack) or a digital stream (from an S/PDIF connector, for example). The same filter outputs a wave stream containing digital-audio data. A single wave filter can perform both rendering and capture simultaneously. This type of filter might, for example, represent an audio device that can play audio through a set of speakers and record audio through a microphone at the same time. Alternately, the wave-rendering and wave-capture hardware might be represented as separate wave filters, as described in [Dynamic Audio Subdevices](dynamic-audio-subdevices.md). An audio adapter driver forms a wave filter by binding a wave miniport driver, which the hardware vendor implements as part of the adapter driver, with a wave port driver, which the system implements. The miniport driver handles all the hardware-specific operations for the wave filter, and the port driver manages all the generic wave-filter functions. The PortCls system driver (Portcls.sys) implements three wave port drivers: WaveRT, WavePci, and WaveCyclic. The three types of wave filter operate as follows: - A WaveRT filter allocates a buffer for wave data and makes that buffer directly accessible to the user-mode client. The buffer can consist of contiguous or noncontiguous blocks of memory, depending on the hardware capabilities of the wave device. The client accesses the buffer as a contiguous block of virtual memory. The buffer is cyclic, which means that when the device's read (for rendering) or write (for capture) pointer reaches the end of the buffer, it automatically wraps around to the beginning of the buffer. - A WavePci filter directly accesses the client's buffer. Although the client accesses the buffer as a single, contiguous block of virtual memory, the WavePci filter must access the buffer as a series of possibly noncontiguous memory blocks. Blocks containing successive portions of the rendering or capture stream are queued up at the device. When the device's read or write pointer reaches the end of one block, it moves to the beginning of the next block in the queue. - A WaveCyclic filter allocates a buffer consisting of a single, contiguous block of memory for use as its output (for rendering) or input (for capture) buffer. This buffer is cyclic. Because the buffer is not directly accessible to the client, the driver must copy data between the driver's cyclic buffer and the client's user-mode buffer. WaveRT is preferred over WavePci and WaveCyclic. WavePci and WaveCyclic were used with earlier versions of Windows. A WaveRT filter can represent an audio device that resides on a system bus, such as PCI or PCI Express. The primary advantage of a WaveRT filter over a WaveCyclic or WavePci filter is that a WaveRT filter allows a user-mode client to exchange audio data directly with the audio hardware. In contrast, WaveCyclic and WavePci filters both require periodic software intervention by the driver, which increases the latency of the audio stream. In addition, audio devices both with and without scatter/gather DMA capabilities can be represented as WaveRT filters. For more information, see the [A Wave Port Driver for Real-Time Audio Streaming](https://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/WaveRTport.doc) white paper. ### <span id="wavert_filter"></span><span id="WAVERT_FILTER"></span>WaveRT Filters A WaveRT filter is implemented as a port/miniport driver pair. In Windows Vista and later, a WaveRT filter factory creates a WaveRT filter as follows: - It instantiates a WaveRT miniport driver object. - It instantiates a WaveRT port driver object by calling [PcNewPort](/windows-hardware/drivers/ddi/portcls/nf-portcls-pcnewport) with GUID value CLSID\_PortWaveRT. - It calls the port driver's [IPort::Init](/windows-hardware/drivers/ddi/portcls/nf-portcls-iport-init) method to bind the miniport driver to the port driver. The code example in [Subdevice Creation](subdevice-creation.md) illustrates this process. The port and miniport drivers communicate with each other through their [IPortWaveRT](/windows-hardware/drivers/ddi/portcls/nn-portcls-iportwavert) and [IMiniportWaveRT](/windows-hardware/drivers/ddi/portcls/nn-portcls-iminiportwavert) interfaces. For more information, see the [A Wave Port Driver for Real-Time Audio Streaming](https://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/WaveRTport.doc) white paper. ### <span id="Information_for_previous_versions_of_Windows"></span><span id="information_for_previous_versions_of_windows"></span><span id="INFORMATION_FOR_PREVIOUS_VERSIONS_OF_WINDOWS"></span>Information for previous versions of Windows WaveCyclic Information for previous versions of Windows A WaveCyclic filter can represent an audio device that connects to a system bus, such as ISA, PCI, PCI Express, or PCMCIA. As the name "WavePci" implies, a WavePci filter usually represents a device that connects to a PCI bus, although, in principle, a WavePci device might instead connect to an ISA bus, for example. Unlike the simpler devices that are supported by WaveCyclic, a device supported by WavePci must have scatter/gather DMA capabilities. An audio device that resides on PCI bus but lacks scatter/gather DMA can be represented as a WaveCyclic filter but not as a WavePci filter. WavePci Information for previous versions of Windows A WavePci device is able to perform scatter/gather DMA transfers to or from buffers that can be located at arbitrary memory addresses and that begin and end with arbitrary byte alignments. In contrast, the DMA hardware for a WaveCyclic device requires only the ability to move data to or from a single buffer that the device's miniport driver allocates. A WaveCyclic miniport driver is free to allocate a cyclic buffer that meets the limited capabilities of its DMA channel. For example, the DMA channel for a typical WaveCyclic device might require a buffer that satisfies the following restrictions: - The buffer is located in a certain region of the physical address space. - The buffer is contiguous in physical as well as in virtual address space. - The buffer begins and ends on even four- or eight-byte boundaries. In return for this simplicity, however, a WaveCyclic device must rely on software copying of data to or from the cyclic buffer, whereas a WavePci device relies on the scatter/gather capabilities of its DMA hardware to avoid such copying. The IRPs that deliver wave audio data to a rendering device or retrieve data from a capture device are accompanied by data buffers, and each of these buffers contains a portion of the audio stream that is being rendered or captured. A WavePci device is able to access these buffers directly through its scatter/gather DMA engine, whereas a WaveCyclic device requires that the data be copied to its cyclic buffer from the IRP, or vice versa. ### <span id="wavepci_filter"></span><span id="WAVEPCI_FILTER"></span>WavePci Filters Note: WavePci Information for previous versions of Windows A WavePci filter is implemented as a port/miniport driver pair. A WavePci filter factory creates a WavePci filter as follows: - It instantiates a WavePci miniport driver object. - It instantiates a WavePci port driver object by calling [PcNewPort](/windows-hardware/drivers/ddi/portcls/nf-portcls-pcnewport) with GUID value CLSID\_PortWavePci. - It calls the port driver's [IPort::Init](/windows-hardware/drivers/ddi/portcls/nf-portcls-iport-init) method to bind the miniport driver to the port driver. The code example in [Subdevice Creation](subdevice-creation.md) illustrates this process. The port and miniport drivers communicate with each other through their [IPortWavePci](/windows-hardware/drivers/ddi/portcls/nn-portcls-iportwavepci) and [IMiniportWavePci](/windows-hardware/drivers/ddi/portcls/nn-portcls-iminiportwavepci) interfaces. For more information, see [Implementation Issues for WavePci Devices](implementation-issues-for-wavepci-devices.md). ### <span id="wavecyclic_filter"></span><span id="WAVECYCLIC_FILTER"></span>WaveCyclic Filters > [!NOTE] > Microsoft supports a diverse and inclusionary environment. Within this document, there are references to the word slave. Microsoft's Style Guide for Bias-Free Communications recognizes this as an exclusionary word. This wording is used as it is currently the wording used within the software. Note: WaveCyclic Information for previous versions of Windows A WaveCyclic filter is implemented as a port/miniport driver pair. A WaveCyclic filter factory creates a WaveCyclic filter as follows: - It instantiates a WaveCyclic miniport driver object. - It instantiates a WaveCyclic port driver object by calling [PcNewPort](/windows-hardware/drivers/ddi/portcls/nf-portcls-pcnewport) with GUID value CLSID\_PortWaveCyclic. - It calls the port driver's [IPort::Init](/windows-hardware/drivers/ddi/portcls/nf-portcls-iport-init) method to bind the miniport driver to the port driver. The code example in [Subdevice Creation](subdevice-creation.md) illustrates this process. The port and miniport drivers communicate with each other through their [IPortWaveCyclic](/windows-hardware/drivers/ddi/portcls/nn-portcls-iportwavecyclic) and [IMiniportWaveCyclic](/windows-hardware/drivers/ddi/portcls/nn-portcls-iminiportwavecyclic) interfaces. The WaveCyclic filter's cyclic buffer always consists of a contiguous block of virtual memory. The port driver's implementation of the [IDmaChannel::AllocateBuffer](/windows-hardware/drivers/ddi/portcls/nf-portcls-idmachannel-allocatebuffer) method always allocates a buffer that is contiguous in both physical and virtual memory address space. If, as mentioned previously, the WaveCyclic device's DMA engine imposes additional constraints on the buffer memory, the miniport driver is free to implement its own buffer-allocation method to meet these constraints. A WaveCyclic miniport driver that asks for a large buffer (for example, eight physically contiguous memory pages) should be prepared to settle for a smaller buffer size if the operating system denies the original request. An audio device might occasionally be unloaded and reloaded to rebalance system resources (see [Stopping a Device to Rebalance Resources](../kernel/stopping-a-device-to-rebalance-resources.md)). A WaveCyclic device with built-in, bus-mastering DMA hardware is called a master device. Alternatively, a WaveCyclic device can be a subordinate device with no built-in DMA-hardware capabilities. A subordinate device has to rely on the system DMA controller to perform any data transfers that it requires. For more information about master and subordinate devices, see [IDmaChannel](/windows-hardware/drivers/ddi/portcls/nn-portcls-idmachannel) and [IDmaChannelSlave](/windows-hardware/drivers/ddi/portcls/nn-portcls-idmachannelslave). A WaveCyclic miniport driver can implement its own DMA-channel object instead of using the default DMA-channel object, which is created by one of the port driver's NewXxxDmaChannel methods: [IPortWaveCyclic::NewMasterDmaChannel](/windows-hardware/drivers/ddi/portcls/nf-portcls-iportwavecyclic-newmasterdmachannel) [IPortWaveCyclic::NewSlaveDmaChannel](/windows-hardware/drivers/ddi/portcls/nf-portcls-iportwavecyclic-newslavedmachannel) The adapter driver's custom [IDmaChannel](/windows-hardware/drivers/ddi/portcls/nn-portcls-idmachannel) implementation can perform custom handling of data to meet special hardware constraints. For example, the Windows Multimedia functions use wave formats in which 16-bit samples are always signed values, but the audio-rendering hardware might be designed to use unsigned 16-bit values instead. In this case, the driver's custom [IDmaChannel::CopyTo](/windows-hardware/drivers/ddi/portcls/nf-portcls-idmachannel-copyto) method can be written to convert the signed source values to the unsigned destination values that the hardware requires. Although this technique can be useful for working around hardware-design flaws, it can also incur a significant cost in software overhead. For an example of a driver that implements its own DMA-channel object, see the Sb16 sample audio adapter in the WDK. If the constant OVERRIDE\_DMA\_CHANNEL is defined to be TRUE, the conditional compilation statements in the source code enable the implementation of a proprietary [IDmaChannel](/windows-hardware/drivers/ddi/portcls/nn-portcls-idmachannel) object, which the driver uses in place of the default IDmaChannel object from the IPortWaveCyclic::NewXxxDmaChannel call.	102.695652	784	0.804544	eng_Latn	0.994841
b7e15951fb21874d50cb85689e70ca276f8a3099	731	md	Markdown	README.md	tasad667023/CodeQuiz	cb81018eeb3c944b4c428ca24dcf171a070ad840	[ "MIT" ]	null	null	null	README.md	tasad667023/CodeQuiz	cb81018eeb3c944b4c428ca24dcf171a070ad840	[ "MIT" ]	null	null	null	README.md	tasad667023/CodeQuiz	cb81018eeb3c944b4c428ca24dcf171a070ad840	[ "MIT" ]	null	null	null	# CodeQuiz A website that is designed for users to take a quiz on different coding topics. The quiz is timed and based on the correct questions answered, user will be presented with a score. ## Assignment 4 : Code Quiz This assignment focuses on creating a website that ensures the user is presented with various multiple choice questions. The questions cover basic coding topics with four different answer options. This quiz is timed and a timer is presented to the user in the top right hand corner of the screen. The user is also given a score at the end of the quiz. Click to check out : https://github.com/tasad667023/CodeQuiz https://tasad667023.github.io/CodeQuiz/ ## Languages Used * HTML * CSS * JavaScript	43	352	0.774282	eng_Latn	0.999245
b7e1ab4e8c82e5c08a241741e49e69342d943b7e	4,696	md	Markdown	src/DeploymentManager/DeploymentManager/help/New-AzDeploymentManagerArtifactSource.md	cloudshellsystem/PS	eca21241a60cdef38b36523b0ad2a0f89cb7bbd1	[ "MIT" ]	1	2019-10-22T01:15:12.000Z	2019-10-22T01:15:12.000Z	src/DeploymentManager/DeploymentManager/help/New-AzDeploymentManagerArtifactSource.md	cloudshellsystem/PS	eca21241a60cdef38b36523b0ad2a0f89cb7bbd1	[ "MIT" ]	1	2019-10-23T23:03:12.000Z	2019-10-23T23:03:27.000Z	src/DeploymentManager/DeploymentManager/help/New-AzDeploymentManagerArtifactSource.md	cloudshellsystem/PS	eca21241a60cdef38b36523b0ad2a0f89cb7bbd1	[ "MIT" ]	1	2022-03-08T21:17:47.000Z	2022-03-08T21:17:47.000Z	--- external help file: Microsoft.Azure.PowerShell.Cmdlets.DeploymentManager.dll-Help.xml Module Name: Az.DeploymentManager online version: https://docs.microsoft.com/en-us/powershell/module/az.deploymentmanager/new-azdeploymentmanagerartifactsource schema: 2.0.0 --- # New-AzDeploymentManagerArtifactSource ## SYNOPSIS Creates an artifact source. ## SYNTAX ``` New-AzDeploymentManagerArtifactSource -ResourceGroupName <String> -Name <String> -Location <String> -SasUri <String> [-Tag <Hashtable>] [-ArtifactRoot <String>] [-DefaultProfile <IAzureContextContainer>] [-WhatIf] [-Confirm] [<CommonParameters>] ``` ## DESCRIPTION The New-AzDeploymentManagerArtifactSource cmdlet creates an artifact source. Specify the Name, ResourceGroupName and required properties. You can modify the returned object locally and then apply the changes to the artifact source by using the Set-AzDeploymentManagerArtifactSource cmdlet. The cmdlet returns an ArtifactSource object that has a ResourceId which can be referenced in the New-AzDeploymentManagerServiceTopology cmdlet so that artifacts required for a ServiceUnit resource, the Template and Parameters files, can be referenced from this location. ## EXAMPLES ### Example 1 ```powershell PS C:\> New-AzDeploymentManagerArtifactSource -ResourceGroupName ContosoResourceGroup -Name ContosoArtifactSource -Location "Central US" -SasUri "https://ContosoStorage.blob.core.windows.net/ContosoArtifacts?sasParameters" ``` Creates an artifact source in the ContosoResourceGroup with the name ContosoArtifactSource with Central US as the location of the resource. The SasUri property provides an Azure Storage SAS Uri to the storage container where the artifacts are stored. ## PARAMETERS ### -ArtifactRoot The optional directory offset under the storage container for the artifacts. ```yaml Type: System.String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -DefaultProfile The credentials, account, tenant, and subscription used for communication with Azure. ```yaml Type: Microsoft.Azure.Commands.Common.Authentication.Abstractions.Core.IAzureContextContainer Parameter Sets: (All) Aliases: AzContext, AzureRmContext, AzureCredential Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Location The location of the resource. ```yaml Type: System.String Parameter Sets: (All) Aliases: Required: True Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Name The name of the artifact source. ```yaml Type: System.String Parameter Sets: (All) Aliases: Required: True Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -ResourceGroupName The resource group. ```yaml Type: System.String Parameter Sets: (All) Aliases: Required: True Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -SasUri The SAS Uri to the Azure storage container where the artifacts are stored. ```yaml Type: System.String Parameter Sets: (All) Aliases: Required: True Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Tag A hash table which represents resource tags. ```yaml Type: System.Collections.Hashtable Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: True (ByPropertyName) Accept wildcard characters: False ``` ### -Confirm Prompts you for confirmation before running the cmdlet. ```yaml Type: System.Management.Automation.SwitchParameter Parameter Sets: (All) Aliases: cf Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -WhatIf Shows what would happen if the cmdlet runs. The cmdlet is not run. ```yaml Type: System.Management.Automation.SwitchParameter Parameter Sets: (All) Aliases: wi Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### CommonParameters This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216). ## INPUTS ### System.Collections.Hashtable ## OUTPUTS ### Microsoft.Azure.Commands.DeploymentManager.Models.PSArtifactSource ## NOTES ## RELATED LINKS	24.715789	314	0.789608	eng_Latn	0.567627
b7e1b4a14fa692cc11412d60b0bbd83ae24d4e72	2,127	md	Markdown	README.md	IanClark-fullStack/tech-blog	0611984a60c25af1fc013b60eee9e35f830a50bd	[ "MIT" ]	null	null	null	README.md	IanClark-fullStack/tech-blog	0611984a60c25af1fc013b60eee9e35f830a50bd	[ "MIT" ]	null	null	null	README.md	IanClark-fullStack/tech-blog	0611984a60c25af1fc013b60eee9e35f830a50bd	[ "MIT" ]	null	null	null	# Tech Blog ------ [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) ## Table of Contents ------ * [Description](#description) * [Installation](#installation) * [Usage](#usage) * [Questions & Contributions](#questions-contribute) ## Description ----- CMS blog, WordPress / Medium style full stack application. ![Deployed on Heroku](https://radiant-headland-18315.herokuapp.com/) Users who sign up and login to the site can subsequently view all published blog posts, add comments, and publish their own content. ![Express.js](https://img.shields.io/badge/express.js-%23404d59.svg?style=for-the-badge&logo=express&logoColor=%2361DAFB) ![MySQL](https://img.shields.io/badge/mysql-%2300f.svg?style=for-the-badge&logo=mysql&logoColor=white) ![NodeJS](https://img.shields.io/badge/node.js-6DA55F?style=for-the-badge&logo=node.js&logoColor=white) ![Sequelize](https://img.shields.io/badge/Sequelize-52B0E7?style=for-the-badge&logo=Sequelize&logoColor=white) ![NPM](https://img.shields.io/badge/NPM-%23000000.svg?style=for-the-badge&logo=npm&logoColor=white) ![TailwindCSS](https://img.shields.io/badge/tailwindcss-%2338B2AC.svg?style=for-the-badge&logo=tailwind-css&logoColor=white) ## Installation ---- After cloning the repo to your machine, open your terminal and cd into the project directory. Next, run: ``` mysql -u root -p; USE blog_db; SOURCE db/schema.sql; exit; ``` After authenticating with mySQL and selecting the project database, in the same terminal, run: ``` npm i npm run seeds npm start ``` ## Usage ----- After installing all dependencies, be sure to create a ".dotenv" file to hide credentials as you wish. Open your browser and navigate to localhost:3001, where you will be prompted to login or signup. The rest is easy! ![image](https://user-images.githubusercontent.com/90655370/142331372-64f6d41b-fbc4-496e-9b66-fa060e830d1e.png) ![image](https://user-images.githubusercontent.com/90655370/142330772-6e870442-49e0-4880-b053-382b99f01b51.png) ## Questions & Contact ------ Reach out [email protected]	36.672414	664	0.74095	eng_Latn	0.446254
b7e1ca6044e3fd4934385205ea7bbffcd44585da	3,239	md	Markdown	docs/relational-databases/server-management-objects-smo/sql-server-management-objects-smo-programming-guide.md	gmilani/sql-docs.pt-br	02f07ca69eae8435cefd74616a8b00f09c4d4f99	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/relational-databases/server-management-objects-smo/sql-server-management-objects-smo-programming-guide.md	gmilani/sql-docs.pt-br	02f07ca69eae8435cefd74616a8b00f09c4d4f99	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/relational-databases/server-management-objects-smo/sql-server-management-objects-smo-programming-guide.md	gmilani/sql-docs.pt-br	02f07ca69eae8435cefd74616a8b00f09c4d4f99	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- title: Guia de Programação do SQL Server Management Objects (SMO) ms.custom: seo-dt-2019 ms.date: 03/14/2017 ms.prod: sql ms.prod_service: database-engine ms.reviewer: '' ms.technology: '' ms.topic: reference helpviewer_keywords: - SMO [SQL Server] - SQL Server Management Objects - programming [SMO] ms.assetid: 4cde2b85-2a31-4cac-8d16-7a4196066193 author: markingmyname ms.author: maghan monikerRange: =azuresqldb-current\|\|=azure-sqldw-latest\|\|>=sql-server-2016\|\|=sqlallproducts-allversions\|\|>=sql-server-linux-2017\|\|=azuresqldb-mi-current ms.openlocfilehash: c06f91b30d4c108a2221f0b6c750dab60ed059bd ms.sourcegitcommit: 15fe0bbba963d011472cfbbc06d954d9dbf2d655 ms.translationtype: MT ms.contentlocale: pt-BR ms.lasthandoff: 11/14/2019 ms.locfileid: "74095382" --- # <a name="sql-server-management-objects-smo-programming-guide"></a>Guia de Programação do SQL Server Management Objects (SMO) [!INCLUDE[appliesto-ss-asdb-asdw-xxx-md](../../includes/appliesto-ss-asdb-asdw-xxx-md.md)] o SMO ([!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Management Objects) é uma coleção de objetos projetados para a programação de todos os aspectos do gerenciamento de [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. O [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Replication Management Objects (RMO) é uma coleção de objetos que encapsula o gerenciamento de replicação do [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. \|Tópico\|Descrição\| \|-----------\|-----------------\| \|[Guia de Introdução ao SMO](getting-started-in-smo.md)\|Fornece informações sobre como iniciar o desenvolvimento de um aplicativo SMO \|[Criando programas SMO](../../relational-databases/server-management-objects-smo/create-program/creating-smo-programs.md)<br /><br /> [Tarefas específicas de programação](../../relational-databases/server-management-objects-smo/tasks/programming-specific-tasks.md)\|Fornece informações sobre como programar os objetos SMO nos namespaces Microsoft.SqlServer.management, Microsoft.SqlServer.Management.NotificationServices, Microsoft.SqlServer.Management.Smo, Microsoft.SqlServer.Management.Smo.Agent, Microsoft.SqlServer.Management.Smo.Broker, Microsoft.SqlServer.Management.Smo.Mail, Microsoft.SqlServer.Management.Smo.RegisteredServers, Microsoft.SqlServer.Management.Smo.Wmi e Microsoft.SqlServer.Management.Trace.<br /><br /> Isso inclui as instruções para gravar programas que definem bancos de dados e gerenciam o [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Você pode usar SMO para criar bancos de dados, executar backups, criar trabalhos, configurar o [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], atribuir permissões e executar muitas outras tarefas administrativas.\| \|[Documentação do desenvolvedor de replicação](../../relational-databases/replication/concepts/replication-developer-documentation.md)\|Fornece informações sobre como programar os objetos RMO no namespace Microsoft.SqlServer.Replication.\| ## <a name="see-also"></a>Consulte também [Documentação do desenvolvedor de replicação](../../relational-databases/replication/concepts/replication-developer-documentation.md)	80.975	1,104	0.782649	por_Latn	0.641551
b7e4ebab4c7fa5c45a7be52b8cd77cfbfd431d2f	1,344	md	Markdown	G2/VisualStudio.md	sedc-codecademy/skwd9-net-05-oopcsharp	5deceac2a74b565bd50973a35dd19d0d588ad0a0	[ "MIT" ]	1	2021-03-22T16:39:01.000Z	2021-03-22T16:39:01.000Z	G2/VisualStudio.md	sedc-codecademy/skwd9-net-05-oopcsharp	5deceac2a74b565bd50973a35dd19d0d588ad0a0	[ "MIT" ]	null	null	null	G2/VisualStudio.md	sedc-codecademy/skwd9-net-05-oopcsharp	5deceac2a74b565bd50973a35dd19d0d588ad0a0	[ "MIT" ]	7	2021-03-22T20:01:41.000Z	2021-12-04T13:37:57.000Z	## How to install VS 2019 🎈 1. Download Visual Studio Community version from this link: [Visual Studio Community](https://visualstudio.microsoft.com/vs/) ![InstallStep0.1](https://github.com/sedc-codecademy/skwd9-net-05-oopcsharp/blob/main/img/01.png?raw=true) ![InstallStep0.2](https://github.com/sedc-codecademy/skwd9-net-05-oopcsharp/blob/main/img/02.png?raw=true) 2. Check ASP.NET and web development box ( For later subjects ) ![InstallStep1](https://github.com/sedc-codecademy/skwd9-net-05-oopcsharp/blob/main/img/03.png?raw=true) 4. Check the .NET desktop development box ![InstallStep2](https://github.com/sedc-codecademy/skwd9-net-05-oopcsharp/blob/main/img/04.png?raw=true) 6. Check .NET Core cross platform development ![InstallStep4](https://github.com/sedc-codecademy/skwd9-net-05-oopcsharp/blob/main/img/05.png?raw=true) 7. Click install and wait for the program to install 8. When it is installed open it and log in with a microsoft account ![InstallStep4](https://github.com/sedc-codecademy/skwd9-net-05-oopcsharp/blob/main/img/06.png?raw=true) ## Extra materials * [Rextester - An online tool for running C#](https://rextester.com/) * [DOT.NET Fiddle - An online tool for running C#](https://dotnetfiddle.net/) * [Git experience](https://docs.microsoft.com/en-us/visualstudio/ide/git-with-visual-studio?view=vs-2019)	48	106	0.763393	eng_Latn	0.254604
b7e5ee1f6542e555c07e850614269a1e5f32b5f7	260	md	Markdown	_posts/2016-06-01-my-first-post.md	navdeepdhamu/creative	c9fd3ff799be26ab8f4d4e629846cd53d3f4a8d2	[ "Apache-2.0" ]	null	null	null	_posts/2016-06-01-my-first-post.md	navdeepdhamu/creative	c9fd3ff799be26ab8f4d4e629846cd53d3f4a8d2	[ "Apache-2.0" ]	null	null	null	_posts/2016-06-01-my-first-post.md	navdeepdhamu/creative	c9fd3ff799be26ab8f4d4e629846cd53d3f4a8d2	[ "Apache-2.0" ]	null	null	null	--- layout: post title: My First Post! --- Start Bootstrap has everything you need to get your new website up and running in no time! All of the templates and themes on Start Bootstrap are open source, free to download, and easy to use. No strings attached!	32.5	214	0.757692	eng_Latn	0.99855
b7e6d514627e39a35c7bcc05e50a2ec417d92854	4,925	md	Markdown	articles/lab-services/use-command-line-start-stop-virtual-machines.md	ialeksander1/azure-docs.pt-br	d5a7a2c2d4a31282f49bd1e35036cb1939911974	[ "CC-BY-4.0", "MIT" ]	null	null	null	articles/lab-services/use-command-line-start-stop-virtual-machines.md	ialeksander1/azure-docs.pt-br	d5a7a2c2d4a31282f49bd1e35036cb1939911974	[ "CC-BY-4.0", "MIT" ]	null	null	null	articles/lab-services/use-command-line-start-stop-virtual-machines.md	ialeksander1/azure-docs.pt-br	d5a7a2c2d4a31282f49bd1e35036cb1939911974	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- title: Use ferramentas de linha de comando para iniciar e parar vMs Azure DevTest Labs description: Aprenda a usar ferramentas de linha de comando para iniciar e parar máquinas virtuais no Azure DevTest Labs. services: devtest-lab,virtual-machines,lab-services documentationcenter: na author: spelluru manager: femila ms.service: lab-services ms.workload: na ms.tgt_pltfrm: na ms.devlang: na ms.topic: article ms.date: 01/16/2020 ms.author: spelluru ms.openlocfilehash: fd643559a09d5c75aad9be5f35c653994c8488cf ms.sourcegitcommit: 2ec4b3d0bad7dc0071400c2a2264399e4fe34897 ms.translationtype: MT ms.contentlocale: pt-BR ms.lasthandoff: 03/27/2020 ms.locfileid: "76169243" --- # <a name="use-command-line-tools-to-start-and-stop-azure-devtest-labs-virtual-machines"></a>Use ferramentas de linha de comando para iniciar e parar as máquinas virtuais Azure DevTest Labs Este artigo mostra como usar o Azure PowerShell ou o Azure CLI para iniciar ou parar máquinas virtuais em um laboratório no Azure DevTest Labs. Você pode criar scripts PowerShell/CLI para automatizar essas operações. [!INCLUDE [updated-for-az](../../includes/updated-for-az.md)] ## <a name="overview"></a>Visão geral O Azure DevTest Labs é uma maneira de criar ambientes de dev/teste rápidos, fáceis e enxutos. Ele permite gerenciar custos, provisionar rapidamente VMs e minimizar desperdícios. Existem recursos incorporados no portal Azure que permitem configurar VMs em um laboratório para iniciar e parar automaticamente em momentos específicos. No entanto, em alguns cenários, você pode querer automatizar a partida e a parada de VMs a partir de scripts PowerShell/CLI. Ele lhe dá alguma flexibilidade para iniciar e parar máquinas individuais a qualquer momento em vez de em momentos específicos. Aqui estão algumas das situações em que executar essas tarefas usando scripts seria útil. - Ao usar um aplicativo de 3 níveis como parte de um ambiente de teste, os níveis precisam ser iniciados em uma seqüência. - Desligue uma VM quando um critério personalizado for cumprido para economizar dinheiro. - Use-o como uma tarefa dentro de um fluxo de trabalho ci/cd para iniciar no início do fluxo, usar as VMs como máquinas de construção, máquinas de teste ou infra-estrutura e, em seguida, parar as VMs quando o processo estiver concluído. Um exemplo disso seria a fábrica de imagens personalizadas com o Azure DevTest Labs. ## <a name="azure-powershell"></a>Azure PowerShell > [!NOTE] > O script a seguir usa o módulo Azure PowerShell Az. O script PowerShell a seguir inicia um VM em um laboratório. [Invoke-AzResourceAction](/powershell/module/az.resources/invoke-azresourceaction?view=azps-1.7.0) é o foco principal deste script. O parâmetro ResourceId é o id de recurso totalmente qualificado para o VM no laboratório. O parâmetro Ação é onde as opções Iniciar ou Parar são definidas dependendo do que for necessário. ```powershell # The id of the subscription $subscriptionId = "111111-11111-11111-1111111" # The name of the lab $devTestLabName = "yourlabname" # The name of the virtual machine to be started $vMToStart = "vmname" # The action on the virtual machine (Start or Stop) $vmAction = "Start" # Select the Azure subscription Select-AzSubscription -SubscriptionId $subscriptionId # Get the lab information $devTestLab = Get-AzResource -ResourceType 'Microsoft.DevTestLab/labs' -ResourceName $devTestLabName # Start the VM and return a succeeded or failed status $returnStatus = Invoke-AzResourceAction ` -ResourceId "$($devTestLab.ResourceId)/virtualmachines/$vMToStart" ` -Action $vmAction ` -Force if ($returnStatus.Status -eq 'Succeeded') { Write-Output "##[section] Successfully updated DTL machine: $vMToStart, Action: $vmAction" } else { Write-Error "##[error]Failed to update DTL machine: $vMToStart, Action: $vmAction" } ``` ## <a name="azure-cli"></a>CLI do Azure O [Azure CLI](/cli/azure/get-started-with-azure-cli?view=azure-cli-latest) é outra maneira de automatizar a partida e a parada das VMs do DevTest Labs. O Azure CLI pode ser [instalado](/cli/azure/install-azure-cli?view=azure-cli-latest) em diferentes sistemas operacionais. O script a seguir oferece comandos para iniciar e parar uma VM em um laboratório. ```azurecli # Sign in to Azure az login ## Get the name of the resource group that contains the lab az resource list --resource-type "Microsoft.DevTestLab/labs" --name "yourlabname" --query "[0].resourceGroup" ## Start the VM az lab vm start --lab-name yourlabname --name vmname --resource-group labResourceGroupName ## Stop the VM az lab vm stop --lab-name yourlabname --name vmname --resource-group labResourceGroupName ``` ## <a name="next-steps"></a>Próximas etapas Veja o artigo a seguir para usar o portal Azure para fazer essas operações: [Reiniciar uma VM](devtest-lab-restart-vm.md).	50.773196	397	0.770761	por_Latn	0.980026
b7e710fcb445e709ea57eeaee66d6f21ece86d96	115	md	Markdown	exercice_2/README.md	CDylan-source/revisions_jour_1	24da9aac01baad573769ef3ab17104e44f7f8e25	[ "Unlicense" ]	null	null	null	exercice_2/README.md	CDylan-source/revisions_jour_1	24da9aac01baad573769ef3ab17104e44f7f8e25	[ "Unlicense" ]	null	null	null	exercice_2/README.md	CDylan-source/revisions_jour_1	24da9aac01baad573769ef3ab17104e44f7f8e25	[ "Unlicense" ]	null	null	null	# revisions_jour_1 Projet de révision Exercice 2 : Le but ici est d'animer des svg avec un fond d'exercice d'algo.	23	63	0.773913	fra_Latn	0.962567
b7e757935b9cbc2187e70d83201af0a28b933811	636	md	Markdown	README.md	alekala/before-after	167b245d4e9c909cd07732232cf01893ff27e35f	[ "MIT" ]	null	null	null	README.md	alekala/before-after	167b245d4e9c909cd07732232cf01893ff27e35f	[ "MIT" ]	null	null	null	README.md	alekala/before-after	167b245d4e9c909cd07732232cf01893ff27e35f	[ "MIT" ]	null	null	null	# before-after ## USAGE main.py -t <image/folder> <input> ## EXAMPLES Individual images INPUT: main.py -t image before.jpg after.jpg OUTPUT: 1.png Folder INPUT: main.py -t folder images OUTPUT: 1.png, 2.png, 3.png, 4.png... Naming scheme for images inside the folder: (image number)(1=before, 2=after).jpg 11.jpg, 12.jpg 21.jpg, 22.jpg 31.jpg, 32.jpg 41.jpg, 42.jpg ## OPTIONS / ARGUMENTS (required) --type -t image/folder (optional) --language -l (default eng) fin/eng (optional) --output -o path to output folder (default ./)	17.189189	49	0.589623	eng_Latn	0.260505
b7e77e11ba02dac8a4c8dbe148d1e16e4c89381f	2,335	md	Markdown	src/docs/en/profile/introduction.md	bryan-robitaille/documentation-website	7a5425de5e68790bc0ea33993eee3680b2b4abc1	[ "MIT" ]	1	2019-07-11T15:28:35.000Z	2019-07-11T15:28:35.000Z	src/docs/en/profile/introduction.md	bryan-robitaille/documentation-website	7a5425de5e68790bc0ea33993eee3680b2b4abc1	[ "MIT" ]	null	null	null	src/docs/en/profile/introduction.md	bryan-robitaille/documentation-website	7a5425de5e68790bc0ea33993eee3680b2b4abc1	[ "MIT" ]	null	null	null	--- path: "/profile/introduction" subnav: "1/Profile/Profil/1" lang: "en" title: "Introduction" --- <helmet> <title> Profile - Introduction </title> </helmet> ## Introduction Similar to other services like Google, Facebook, and Github, the Profile-as-a-service (PAAS) allows a tell-me-once approach for setting common profile information across all Open Accessible Digital Workspace applications. Profile-as-a-service also leverages the GCaccount sign-on platform. PAAS can currently store a user's name, email, avatar, title, contact information, as well as organizational information. We built this service around the premise that the user is the authoratative source on their own information. Profile-as-a-serivce can still receive information from other sources. Any external information sources requires the user to validate any changes proposed by those sources (GCHR, PeopleSoft, etc.) before they take effect. ## Tech stack The Profile-as-a-service is architected on Apollo server and leverages Prisma and PostgreSQL for data storage. These technologies were chosen after performance testing other frameworks such as Python Django. * [Apollo Server](https://www.apollographql.com/docs/apollo-server/) * [Prisma](https://www.prisma.io/) * [PostgreSQL](https://www.postgresql.org/) ## Communication with other services Profile-as-a-service listens for specific events on the Message Queue that then trigger specific functions. For example, when a new user validates their account on GCaccount, a message is sent to the Message Queue specifying that there is a new user and it provides the information that was used during registration. Profile-as-a-serivce listens for this event, as well as other applications, and triggers the automatic creation of this user's profile with the information that was used during GCaccount registration. ## Authentication and authorization The Profile service relies on the GCaccount access token to ensure that information can only be accessed and modified by authorized individuals. The access token is the key to all Open Accessible Digital Workspace applications and contains information specific to the user and the application trying to access the data. This data is then used to determine if the user and/or application can gain access to read or modify the information.	70.757576	519	0.799572	eng_Latn	0.994413
b7e881d8423e742b53c067798d8dc8f84222d67c	175	md	Markdown	content/en/docs/Anka Build Cloud/Virtualization CLI/partials/license/accept-eula/_index.md	ChefAustin/docs	12916e3bb99ed74b5bf047c1e076d36427998137	[ "BSD-2-Clause" ]	null	null	null	content/en/docs/Anka Build Cloud/Virtualization CLI/partials/license/accept-eula/_index.md	ChefAustin/docs	12916e3bb99ed74b5bf047c1e076d36427998137	[ "BSD-2-Clause" ]	null	null	null	content/en/docs/Anka Build Cloud/Virtualization CLI/partials/license/accept-eula/_index.md	ChefAustin/docs	12916e3bb99ed74b5bf047c1e076d36427998137	[ "BSD-2-Clause" ]	null	null	null	```shell > sudo anka license accept-eula --help Usage: anka license accept-eula [OPTIONS] accept EULA (root privileges) Options: --help Show this message and exit. ```	17.5	41	0.708571	eng_Latn	0.57109
b7e89b3c4f89d9344dbd3638b055a3c6d4474d79	1,522	md	Markdown	content/04.seventh-day-adventist-hymnal/03.101-200/03.121-130/07.Infant-Holy,-Infant-Lowly/docs.md	GospelSounders/adventhymnals	d2108ab49d735b373c59901e5296c8819a1ad3f2	[ "Apache-2.0" ]	null	null	null	content/04.seventh-day-adventist-hymnal/03.101-200/03.121-130/07.Infant-Holy,-Infant-Lowly/docs.md	GospelSounders/adventhymnals	d2108ab49d735b373c59901e5296c8819a1ad3f2	[ "Apache-2.0" ]	1	2021-05-10T23:24:05.000Z	2021-05-10T23:24:05.000Z	content/04.seventh-day-adventist-hymnal/03.101-200/03.121-130/07.Infant-Holy,-Infant-Lowly/docs.md	GospelSounders/adventhymnals	d2108ab49d735b373c59901e5296c8819a1ad3f2	[ "Apache-2.0" ]	null	null	null	--- title: 127. Infant Holy, Infant Lowly - Seventh Day Adventist Hymnal metadata: description: \| SDAH 127. Infant Holy, Infant Lowly. 1. Infant holy, infant lowly, For His bed a cattle stall; Oxen lowing, little knowing Christ the babe is Lord of all; Swift are winging angels singing, Noels ringing, tidings bringing, Christ the babe is Lord of all, Christ the babe is Lord of all. keywords: \| SDAH, Seventh Day Adventist Hymnal, adventhymnals, advent hymnals, Infant Holy, Infant Lowly, Infant holy, infant lowly, author: Brian Onang'o --- #### Advent Hymnals ## 127. INFANT HOLY, INFANT LOWLY #### Seventh Day Adventist Hymnal ```txt 1. Infant holy, infant lowly, For His bed a cattle stall; Oxen lowing, little knowing Christ the babe is Lord of all; Swift are winging angels singing, Noels ringing, tidings bringing, Christ the babe is Lord of all, Christ the babe is Lord of all. 2. Flocks were sleeping, shepherds keeping Vigil till the morning new; Saw the glory, heard the story, Tidings of the gospel true; Thus rejoicing, free from sorrow, Praises voicing greet the morrow, Christ the babe was born for you, Christ the babe was born for you. ``` - \| - \| -------------\|------------\| Title \| Infant Holy, Infant Lowly \| Key \| \| Titles \| undefined \| First Line \| Infant holy, infant lowly, \| Author \| Year \| Composer\| \| Hymnal\| - \| Tune\| \| Metrical pattern \| \| # Stanzas \| \| Chorus \| \| Chorus Type \| \| Subjects \| \| Texts \| \| Print Texts \| Scripture Song \| \|	24.15873	291	0.696452	eng_Latn	0.982168
b7e92fad41adfe3d8d37e757b03ee373adb5aaf1	3,356	md	Markdown	under_the_wire/oracle/oracle14/explanation.md	bernardosequeir/CTFfiles	36a6ceba49d9a9019056d3669c5e8f84aa83b618	[ "MIT" ]	null	null	null	under_the_wire/oracle/oracle14/explanation.md	bernardosequeir/CTFfiles	36a6ceba49d9a9019056d3669c5e8f84aa83b618	[ "MIT" ]	5	2020-09-23T18:28:25.000Z	2020-09-23T18:28:41.000Z	under_the_wire/oracle/oracle14/explanation.md	bernardosequeir/CTFSolutions	503944617cb18826d12ab98fa33fd761e791328a	[ "MIT" ]	null	null	null	https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/default.aspx ```powershell PS C:\users\Oracle13\desktop> get-winevent -path .\security.evtx \| where {$_.ID -like "4727"} \| Format-List -Property * Message : A security-enabled global group was created. Subject: Security ID: S-1-5-21-2268727836-2773903800-2952248001-1621 Account Name: gamora Account Domain: UNDERTHEWIRE Logon ID: 0xBC24FF New Group: Security ID: S-1-5-21-2268727836-2773903800-2952248001-1626 Group Name: Galaxy Group Domain: UNDERTHEWIRE Attributes: SAM Account Name: Galaxy SID History: - Additional Information: Privileges: - Id : 4727 Version : 0 Qualifiers : Level : 0 Task : 13826 (...) PS C:\users\Oracle13\desktop> ls Directory: C:\users\Oracle13\desktop Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 8/30/2018 10:51 AM 0 88 -a---- 8/30/2018 5:52 AM 2166784 security.evtx ```	69.916667	164	0.195173	yue_Hant	0.404009
b7eaa8db4e96da5d3e4e4bf2e32577310e829065	38,912	md	Markdown	video/video.md	asad-awadia/knowledge	08f760af3d3a0474694cec079f68688ae9bae34d	[ "CC-BY-4.0" ]	null	null	null	video/video.md	asad-awadia/knowledge	08f760af3d3a0474694cec079f68688ae9bae34d	[ "CC-BY-4.0" ]	null	null	null	video/video.md	asad-awadia/knowledge	08f760af3d3a0474694cec079f68688ae9bae34d	[ "CC-BY-4.0" ]	null	null	null	# Video I share [YouTube playlists I made](https://www.youtube.com/channel/UCEKqrUfr_FMKIO9XSJS4vDw/playlists?view=1&sort=lad&flow=grid) (all but [Good Music](https://www.youtube.com/playlist?list=PL0nGxteCFLXYA1fsLmlWzY0Tyoo3c7tF-) are quite outdated). ## Inspiring editing - [Watchtower of Turkey](https://www.youtube.com/watch?v=z7yqtW4Isec) - Incredible. By Leonardo Dalessandri. - [The New iPad Pro — On Any Given Wednesday](https://www.youtube.com/watch?v=UR5ODc5Wbbo) - By Leonardo Dalessandri. - [My Pitch to Casey Neistat - From the CEO of Patreon](https://www.youtube.com/watch?v=jAI38B-3Hzc) - Awesome transitions. - [Wandering Down Under \| New Zealand, Australia](https://www.youtube.com/watch?v=vMDprf4rM_U) - [The sky is not the limit - Johnny FPV (2019)](https://www.youtube.com/watch?v=DYHUuJAle8A) - [Londoners](https://www.youtube.com/watch?v=jB0Ho8E5fHA) - [iPhone 12 - 6 Months Later](https://www.youtube.com/watch?v=ab5Oackjvv8) - [LEVA - YouTube](https://www.youtube.com/channel/UC6t1USQd5kZsY7AFACsdC9Q/videos) - [TikTok Remix Culture](https://twitter.com/Iameaschris/status/1391207396979007488) ([HN](https://news.ycombinator.com/item?id=27161011)) - [Parasite VFX reel](https://twitter.com/jimmycthatsme/status/1398707908259442693) - [Kendall Roy \| The City Surf](https://www.youtube.com/watch?v=DG-1VkPN128) - [Girl bosses in film](https://www.youtube.com/watch?v=roYPzlvRk2s) - [Beth Harmon being superior in Queen's Gambit](https://www.youtube.com/watch?v=MnjokzR8V7Q) - [Beth Harmon \| Unstoppable](https://www.youtube.com/watch?v=CZXQGUV9ZSQ) - [California Dreamin' - Once Upon A Time In Hollywood](https://www.youtube.com/watch?v=j76nnfv01ig) - [Succession (2021) \| Season 3 Official Trailer](https://www.youtube.com/watch?v=kevqiiYNFrc) - [Will & Louisa \| Don't forget about me](https://www.youtube.com/watch?v=kDvmNts2NsA) ## Favorite clips - [Carlos Cipa - Today and It's Gone](https://www.youtube.com/watch?v=26zJ1CLzsTk) ## Tools - [Streamable](https://streamable.com/) - Video publishing made easy. - [Around](https://www.around.co/) - Quick, high-impact video calls for a new era of work. - [Natron](https://natrongithub.github.io/) - Open Source Compositing Software for VFX and Motion Graphics. ([Code](https://github.com/NatronGitHub/Natron)) ## Notes - [In 'Mad Max: Fury Road' (2015) Margaret Sixel purposely removed frames in scenes to make you feel as anxious as Max.](https://twitter.com/Delivery_Pig/status/1395829946413690880) - [Hide self view in video calls to make them less draining. The brain uses a tremendous amount of energy looking at itself.](https://twitter.com/maccaw/status/1403129131622088704) ## Links - [Videvo](https://www.videvo.net/) - Free Stock Video Footage. - [H.264 is Magic (2016)](https://sidbala.com/h-264-is-magic/) ([HN](https://news.ycombinator.com/item?id=19997813)) - [Handy tip for trimming demo videos](https://gist.github.com/bvaughn/0da332982b650e188971b7955173a559) - [Gentle introduction to video technology, although it's aimed at software developers / engineers](https://github.com/leandromoreira/digital_video_introduction) ([HN](https://news.ycombinator.com/item?id=21593158)) - [How To Make A \$300 Camera Look Pro (2019)](https://www.youtube.com/watch?v=0wqUWYx3UrY) - [Puffer](https://github.com/StanfordSNR/puffer) - Stanford University research study about using machine learning to improve video-streaming algorithms. - [Alfalfa](https://github.com/excamera/alfalfa) - Purely functional video codec, used for ExCamera and Salsify. ([Web](https://snr.stanford.edu/salsify/)) - [Facebook Open-Sources PySlowFast Codebase for Video Understanding (2020)](https://medium.com/syncedreview/facebook-open-sources-pyslowfast-codebase-for-video-understanding-89200ff35267) - [FFmpeg](https://github.com/FFmpeg/FFmpeg) - Collection of libraries and tools to process multimedia content such as audio, video, subtitles and related metadata. ([Cheat sheet](https://github.com/yuanqing/ffmpeg-cheatsheet)) ([Rust FFmpeg](https://github.com/zmwangx/rust-ffmpeg)) - [ffmpeg-python](https://github.com/kkroening/ffmpeg-python) - Python bindings for FFmpeg. - [IPTV](https://github.com/iptv-org/iptv) - Collection of 8000+ publicly available IPTV channels from all over the world. - [Olive](https://github.com/olive-editor/olive) - Free non-linear video editor for Windows, macOS, and Linux. - [astiencoder](https://github.com/asticode/go-astiencoder) - Open source video encoder written in Go and based on ffmpeg C bindings. - [SVT-AV1](https://github.com/OpenVisualCloud/SVT-AV1) - Scalable Video Technology for AV1 (SVT-AV1 Encoder and Decoder). - [Decord](https://github.com/dmlc/decord) - Efficient video loader for deep learning with smart shuffling that's super easy to digest. - [How I teach classes remotely (2020)](http://blog.ifost.org.au/2020/03/how-i-teach-classes-remotely.html) ([HN](https://news.ycombinator.com/item?id=22612343)) - [NymphCast](https://github.com/MayaPosch/NymphCast) - Audio and video casting system with support for custom applications. - [Twilio Video React App](https://github.com/twilio/twilio-video-app-react) - Collaboration application built with the twilio-video.js SDK and React.js. - [Screen](https://videovillage.co/screen/) - Video player for video people. - [How Productivity Star Thomas Frank Reaches Millions on YouTube](https://superorganizers.substack.com/p/how-productivity-star-thomas-frank) - [Zoom](https://zoom.us/) - Video conferencing. - [Jitsi](https://meet.jit.si/) - Secure, Simple and Scalable Video Conferences. ([Code](https://github.com/jitsi/jitsi-meet)) ([Jibri - JItsi BRoadcasting Infrastructure](https://github.com/jitsi/jibri)) ([Jitsi Meet on Docker](https://github.com/jitsi/docker-jitsi-meet)) - [JaaS](https://jaas.8x8.vc/) - Jitsi as a Service. ([HN](https://news.ycombinator.com/item?id=25938999)) - [Film Grain Synthesis for AV1 Video Codec (2018)](https://norkin.org/pdf/DCC_2018_AV1_film_grain.pdf) ([Lobsters](https://lobste.rs/s/zkakuj/film_grain_synthesis_for_av1_video_codec)) - [video-summarizer](https://github.com/SoptikHa2/video-summarizer) - Summarizes videos into much shorter videos. Ideal for long lecture videos. - [Pangolin](https://github.com/stevenlovegrove/Pangolin) - Lightweight portable rapid development library for managing OpenGL display / interaction and abstracting video input. - [editly](https://github.com/mifi/editly) - Slick, declarative command line video editing. ([HN](https://news.ycombinator.com/item?id=23006794)) - [@cloudflare/stream-react](https://github.com/cloudflare/stream-react) - Official React component for Cloudflare Stream. - [VidGear](https://github.com/abhiTronix/vidgear) - High-performance cross-platform Video Processing Python framework powerpacked with unique trailblazing features. - [Invidio](https://invidio.us/) - Alternative front-end to YouTube. ([Code](https://github.com/iv-org/invidious)) - [Mux](https://mux.com/) - API-first platform, powered by data and designed by video experts to make beautiful video possible for every development team. - [Komposition](https://owickstrom.github.io/komposition/) - Video editor built for screencasters. - [Stremio](https://www.stremio.com/) - Modern media center that's a one-stop solution for your video entertainment. - [Pragli](https://pragli.com/) - Virtual office for remote teams. - [Online Town](https://theonline.town/) - Video-calling space that lets multiple people hold separate conversations in parallel. - [Vito: Behind the Scenes (2020)](https://vito.community/gallery/events/vito-insiders/sessions/57/videos/vito-behind-the-scenes) - [AppleALC](https://github.com/acidanthera/AppleALC) - Native macOS HD audio for not officially supported codecs. - [Fluent ffmpeg-API for node.js](https://github.com/fluent-ffmpeg/node-fluent-ffmpeg) - [TAGX](https://tagx.io/) - Enter a YouTube, Vimeo or Video link below to start tagging. - [VMAF - Video Multi-Method Assessment Fusion](https://github.com/Netflix/vmaf) - [Kimera](https://github.com/luigifreitas/kimera) - Low-latency hardware accelerated codec based video streaming utility. - [Wahay](https://github.com/digitalautonomy/wahay) - Easy-to-use, secure and decentralized conference calls. - [lbry.tv](https://lbry.tv/) - [slowmoVideo](https://github.com/slowmoVideo/slowmoVideo) - Tool that uses optical flow for generating slow-motion videos. - [Aegisub](https://github.com/Aegisub/Aegisub) - Cross-platform advanced subtitle editor. - [PL_MPEG](https://github.com/phoboslab/pl_mpeg) - Single file C library for decoding MPEG1 Video and MP2 Audio. - [Ask HN: Is it too late to start creating content on YouTube? (2020)](https://news.ycombinator.com/item?id=23444750) - [Cloudflare TV](https://cloudflare.tv/live) ([HN](https://news.ycombinator.com/item?id=23451334)) ([Article](https://blog.cloudflare.com/ladies-and-gentlemen-cloudflare-tv/)) - [VideoJS Plus](https://github.com/Pong420/videojs-plus) - Extension and skin for video.js. - [Daily.co](https://www.daily.co/) - 1-click video chat API. - [Thoughts on future of video & Zoom (2020)](https://twitter.com/gokulr/status/1269326413489815553) - [Unsilence](https://github.com/lagmoellertim/unsilence) - Console Interface and Library to remove silent parts of a media file. - [toobnix](https://toobnix.org/) - Federated video service. - [Briefing](https://brie.fi/ng) - Secure anonymous video conferencing. - [Talky](https://talky.io/) - Simple video chat and screen sharing for groups up to 6 people. - [Rav1e](https://github.com/xiph/rav1e) - AV1 encoder written in Rust and assembly. ([HN](https://news.ycombinator.com/item?id=23512161)) - [HN: FFmpeg 4.3 (2020)](https://news.ycombinator.com/item?id=23540704) - [Zipcall](https://zipcall.io/) - Peer to peer browser video calling platform with unmatched video quality and latency. ([Code](https://github.com/ianramzy/decentralized-video-chat)) - [MakeSpace](https://makespace.fun/) - Whole new way to be together, apart. ([HN](https://news.ycombinator.com/item?id=23571748)) - [Syncplay](https://github.com/Syncplay/syncplay) - Synchronize video playback across multiple instances of mpv, VLC, MPC-HC, MPC-BE and mplayer2 over the Internet. - [How I Record Educational Videos (2020)](https://kentcdodds.com/blog/how-i-record-educational-videos) - [Icebreaker](https://icebreaker.video/) - Online events that build community. - [What's In A GIF - Bit by Byte](http://matthewflickinger.com/lab/whatsinagif/bits_and_bytes.asp) - [Scrimba](https://scrimba.com/) - Learn to Code with Interactive Tutorials. ([HN](https://news.ycombinator.com/item?id=24579699)) - [room.sh](https://room.sh/) - Online meeting rooms with powerful collaboration tools. - [mmhmm](https://www.mmhmm.app/) - Clear, compelling communication for everyone. - [Building Cloudflare TV from scratch (2020)](https://blog.cloudflare.com/building-cloudflare-tv-from-scratch/) ([HN](https://news.ycombinator.com/item?id=23764596)) - [Analysis of YouTube Trending Videos of 2019 (US)](https://ammar-alyousfi.com/2020/youtube-trending-videos-analysis-2019-us) ([HN](https://news.ycombinator.com/item?id=23762180)) - [Kinoni](https://www.kinoni.com/) - Turn your phone into a wireless webcam. ([HN](https://news.ycombinator.com/item?id=23759926)) - [HN: YouTube deleted an electronics repair channel (2020)](https://news.ycombinator.com/item?id=23758547) - [Grain](https://www.grain.co/) - Record & share the best parts of Zoom video calls. - [Rewatch](https://rewatch.tv/) - Private & secure video channel for your team. Rewatch transcribes your videos and unlocks your team’s spoken knowledge, making it searchable and organized—all in one place. - [Video that keeps your team connected and inspired (2020)](https://blog.rewatch.tv/post/2020/07/08/connected-and-inspired/) - [ZmURL](https://zmurl.com/) - Host Delightful Zoom Events. - [DIY Video Hosting (2020)](https://tyler.io/diy-video-hosting/) ([HN](https://news.ycombinator.com/item?id=23894827)) - [Unscreen](https://www.unscreen.com/) - Automatically remove video backgrounds with ML. ([HN](https://news.ycombinator.com/item?id=24058341)) - [YouTube Storytelling: How To Make Videos that People Share (2020)](https://www.shopmoment.com/lessons/youtube-storytelling-how-to-make-videos-people-share-colin-and-samir) - [ESPFLIX](https://github.com/rossumur/espflix) - Free video streaming service that runs on a ESP32. ([HN](https://news.ycombinator.com/item?id=24150029)) - [Tella](https://www.tella.tv/) - Collaborative online video editor. ([HN](https://news.ycombinator.com/item?id=24158509)) - [Moving from YouTube to PeerTube (2020)](https://battlepenguin.com/tech/moving-from-youtube-to-peertube/) ([HN](https://news.ycombinator.com/item?id=24222661)) - [RedditVids](https://redditvids.com/) - Discover shared videos and live broadcasts from Reddit. - [FFmpeg: Step-by-Step Retro Video Filter (2020)](https://www.gariany.com/2020/08/ffmpeg-step-by-step-retro-video-filter/) - [YouTube Transcript](https://youtubetranscript.com/) - Read YouTube videos. - [Got Your Back](https://www.gotyourback.space/) - Collection of virtual backdrops for use in video call apps. - [Eulerian Video Magnification](https://people.csail.mit.edu/mrub/evm/) ([HN](https://news.ycombinator.com/item?id=24362525)) - [Create a Golang Video Streaming Server Using HLS (2020)](https://qvault.io/2020/09/04/golang-video-stream-server/) - [Clipchamp](https://clipchamp.com/en/) - Convert videos to MP4. Compress and edit videos. Record with your webcam and collect videos from others. - [Airmeet](https://www.airmeet.com/) - Virtual Events Platform for Communities & Enterprises. - [Tube Explorer](https://observablehq.com/@tomlarkworthy/random-place-on-youtube) - Technology that helps me find strange things on YouTube outside my filter bubble. - [How to Make an Actually Good Tutorial (2020)](https://www.youtube.com/watch?v=IrrdC_pkmGM) - [Tips for immersive video calls (2020)](https://www.benkuhn.net/vc/) ([HN](https://news.ycombinator.com/item?id=24610166)) - [m4vga-rs](https://github.com/cbiffle/m4vga-rs) - VGA-style video output for STM32F4 processors, in Rust. - [Tips for Running an Effective Virtual Offsite (2020)](https://blog.bearer.sh/tips-for-virtual-offsite/) - [Interactive Video Stylization Using Few-Shot Patch-Based Training](https://github.com/OndrejTexler/Few-Shot-Patch-Based-Training) - [Bitmovin](https://bitmovin.com/) - Adaptive streaming video infrastructure encoding and HTML5 player. - [screego/server](https://github.com/screego/server) - Screen sharing for developers. ([Web](https://app.screego.net/)) ([Docs](https://screego.net/#/)) - [Whereby](https://whereby.com/) - Video Meetings, Video Conferencing and Screen Sharing. Same meeting link every time. - [Calla](https://github.com/capnmidnight/Calla) - Virtual Meetups through Jitsi. ([Web](https://www.calla.chat/)) ([HN](https://news.ycombinator.com/item?id=24710948)) - [Livestorm](https://livestorm.co/) - Video Conferencing Software for Webinars and Online Meetings. - [FreeTube](https://freetubeapp.io/) - Private YouTube Client. ([Code](https://github.com/FreeTubeApp/FreeTube)) - [Vito Community](https://vi.to/) - Flexible, private, online spaces for groups. - [Things You Should Consider When Trying to Grow a YouTube Channel in 2020](https://blog.papercup.com/posts/things-you-should-consider-when-trying-to-grow-a-youtube-channel-in-2020/) - [Circles for Zoom](https://www.circlesforzoom.com/) - Get rid of the big Zoom window and turn each participant into a circle on your screen. - [Awesome YouTubers](https://github.com/JoseDeFreitas/awesome-youtubers) - Awesome YouTubers that teach about technology. - [Tools to create persistent room for team meetings (2020)](https://twitter.com/karrisaarinen/status/1317005954462920705) - [VideoAsk](https://www.videoask.com/) - Interact face-to-face with your audience & build stronger business relationships. - [Stream](https://www.stream.club/) - Virtual Class Platform. - [BigMarker](https://www.bigmarker.com/) - Modern, No-Download Webinar Software. - [Vowel](https://www.vowel.com/) - Plan, host, transcribe, search, and share your meetings. - [PeerTube](https://joinpeertube.org/) - Free and open-source, decentralized, federated video platform powered by ActivityPub and WebTorrent. ([Code](https://github.com/Chocobozzz/PeerTube)) ([Roadmap](https://joinpeertube.org/roadmap/)) ([HN](https://news.ycombinator.com/item?id=24856243)) ([HN 2](https://news.ycombinator.com/item?id=25707059)) - [FFmpeg Drawtext Filter for Overlays, Scrolling Text, Timestamps on Videos](https://ottverse.com/ffmpeg-drawtext-filter-dynamic-overlays-timecode-scrolling-text-credits/) ([HN](https://news.ycombinator.com/item?id=24865755)) - [vdx](https://github.com/yuanqing/vdx) - Intuitive CLI for processing video, powered by FFmpeg. ([HN](https://news.ycombinator.com/item?id=24866455)) - [LosslessCut](https://github.com/mifi/lossless-cut) - Swiss army knife of lossless video/audio editing. ([HN](https://news.ycombinator.com/item?id=24883030)) - [youtube-dl](https://youtube-dl.org/) - Command-line program to download videos from YouTube.com and a few more sites. ([Code](https://github.com/ytdl-org/youtube-dl)) ([Download YouTube Video in Go](https://github.com/kkdai/youtube)) ([Origins of the youtube-dl project](https://rg3.name/202011071352.html)) ([HN](https://news.ycombinator.com/item?id=25047818)) - [LiveGo](https://github.com/gwuhaolin/livego) - Simple and efficient live broadcast server in Go. - [node-ytdl-core](https://github.com/fent/node-ytdl-core) - YouTube video downloader in JavaScript. - [FFmpeg.wasm](https://github.com/ffmpegwasm/ffmpeg.wasm) - FFmpeg for browser and node, powered by WebAssembly. ([Web](https://ffmpegwasm.github.io/)) ([HN](https://news.ycombinator.com/item?id=28251801)) - [Frame.io](https://frame.io/) - Video Review and Collaboration Software. - [stream.new](https://stream.new/) - Add a video. Get a shareable link to stream it. ([Code](https://github.com/muxinc/stream.new)) - [Video.js](https://github.com/videojs/video.js) - HTML5 Video Player. - [Bubbles](https://www.usebubbles.com/) - Video and Screenshot Collaboration. - [Livepeer](https://livepeer.org/) - Decentralized video transcoding network built on the Ethereum blockchain. ([GitHub](https://github.com/livepeer)) ([Protocol](https://github.com/livepeer/protocol)) ([JS library](https://github.com/livepeer/livepeerjs)) - [go-livepeer](https://github.com/livepeer/go-livepeer) - Go implementation of the Livepeer protocol. - [Luma](https://lu.ma/) - Activate your community. Foster meaningful relationships with events, newsletters, and community analytics. ([GitHub](https://github.com/luma-team)) - [Stack Videos Horizontally, Vertically, in a Grid With FFmpeg (2020)](https://ottverse.com/stack-videos-horizontally-vertically-grid-with-ffmpeg/) ([HN](https://news.ycombinator.com/item?id=25022665)) - [DaVinci Resolve](https://www.blackmagicdesign.com/products/davinciresolve/) - Color correction and non-linear video editing application. - [YouTube Downloader](https://youtubedld.com/) - Free and efficient YouTube downloader. ([HN](https://news.ycombinator.com/item?id=25024849)) - [Gather.Town](https://gather.town/) - Spatial video chat for remote teams. ([HN](https://news.ycombinator.com/item?id=25039370)) - [Video Renderer](https://github.com/ThreadsStyling/video-renderer) - Unified interface for expressing rendering streams for ffmpeg and canvas. - [Vidar](https://github.com/clabe45/vidar) - Extendable video-editing framework for the browser. - [Milk Video](https://milk.video/) - Turn webinars into engaging highlights. - [RemoteWorkly](https://www.remoteworkly.co/) - Async Video Messaging. - [Calculate PSNR, VMAF, SSIM using FFmpeg (2020)](https://ottverse.com/calculate-psnr-vmaf-ssim-using-ffmpeg/) - [OTTVerse](https://ottverse.com/) - OTT Tech-focused publication. - [Create Vintage Videos Using FFmpeg in 4 Simple Steps (2020)](https://ottverse.com/create-vintage-videos-using-ffmpeg/) ([HN](https://news.ycombinator.com/item?id=25102401)) - [Auto-Editor](https://github.com/WyattBlue/auto-editor) - Command line application for automatically editing video and audio by analyzing where sections are silent and cutting them up. - [RIFE: Real-Time Intermediate Flow Estimation for Video Frame Interpolation](https://github.com/hzwer/arXiv2020-RIFE) - [FastoTV](https://github.com/fastogt/fastotv) - Open source IPTV player. - [libheif](https://github.com/strukturag/libheif) - HEIF and AVIF file format decoder and encoder. ([Web](https://www.libde265.org/)) - [FFsubsync](https://github.com/smacke/ffsubsync) - Automagically synchronize subtitles with video. - [TSDuck](https://github.com/tsduck/tsduck) - MPEG Transport Stream Toolkit. ([Web](https://tsduck.io/)) - [Superpeer](https://superpeer.com/) - Gives you the tools you need to have paid 1:1 video calls and livestreams with your audience and paid subscribers. - [Clappr](https://github.com/clappr/clappr) - Extensible media player for the web. ([Web](http://clappr.io/)) - [minih264](https://github.com/lieff/minih264) - Minimalistic H264/SVC encoder single header library. - [Cast All The Things](https://github.com/skorokithakis/catt) - Allows you to send videos from many, many online sources to your Chromecast. - [Boltstream](https://github.com/benwilber/boltstream) - Self-hosted full end-to-end live video streaming platform. ([HN](https://news.ycombinator.com/item?id=25328622)) - [AviSynth](https://avs-plus.net/) - Powerful tool for video post-production. It provides ways of editing and processing videos. ([Code](https://github.com/AviSynth/AviSynthPlus)) - [VEED](https://www.veed.io/) - Create, Edit & Share Videos Online for free. ([API](https://www.veed.io/api)) - [Along](https://along.video/) - Lets you make your best videos ever - with superpowers. - [DTube](https://d.tube/) - Full-featured video sharing website, decentralized. ([Code](https://github.com/dtube/dtube)) - [How Video Works](https://howvideo.works/) ([HN](https://news.ycombinator.com/item?id=25422003)) - [Life of a Pixel (2020)](https://www.youtube.com/watch?v=PwYxv-43iM4) - [JustWatch](https://www.justwatch.com/) - All your streaming services in one app. - [Overseerr](https://github.com/sct/overseerr) - Request management and media discovery tool for the Plex ecosystem. - [Why can’t you buy a good webcam? (2020)](https://vsevolod.net/good-webcams/) ([HN](https://news.ycombinator.com/item?id=25504771)) ([Lobsters](https://lobste.rs/s/hmwpil/why_can_t_you_buy_good_webcam)) - [Galene](https://galene.org/) - Videoconferencing server that is easy to deploy (just copy a few files and run the binary) and that requires moderate server resources. ([Code](https://github.com/jech/galene)) - [Kodi](https://kodi.tv/) - Open Source Home Theater Software. ([Code](https://github.com/xbmc/xbmc)) ([HN](https://news.ycombinator.com/item?id=29633079)) - [Starting Your Own YouTube Channel in 2021](https://www.youtube.com/watch?v=ml7Vme_aPn4) - [Perfect Media Server](https://perfectmediaserver.com/) - Knowledge and information about building an open-source media server. ([Code](https://github.com/IronicBadger/pms-wiki/)) ([HN](https://news.ycombinator.com/item?id=25619137)) - [MiniVideo](https://github.com/emericg/MiniVideo) - Multimedia framework developed from scratch in C/C++, bundled with test programs and a neat media analyzer. - [OpenPlayerJS](https://www.openplayerjs.com/) - Lightweight Media Player for Web. ([Code](https://github.com/openplayerjs/openplayerjs)) - [Netflix Open Content](https://opencontent.netflix.com/) - [Clowdr](https://clowdr.org/) - Virtual conferences for social good. ([GitHub](https://github.com/clowdr-app)) ([Code](https://github.com/clowdr-app/clowdr)) - [Chatmosphere](https://chatmosphere.cc/) - Make informal video calls more fun and dynamic. ([HN](https://news.ycombinator.com/item?id=25847871)) - [mebm](https://bwasti.github.io/mebm/) - Browser based video editor that supports animation of images and text overlays. ([Code](https://github.com/bwasti/mebm)) - [How to build a video editor (2020)](https://www.veed.io/blog/how-to-build-a-video-editor/) - [Mibo](https://getmibo.com/) - Video chat that feels like real life. ([HN](https://news.ycombinator.com/item?id=25858814)) - [CrowdNotifier - Decentralized Privacy-Preserving Presence Tracing](https://github.com/CrowdNotifier/documents) - [Visualization tool for live music performances](https://github.com/bartjoyce/video-app) - Built with C++. - [Gilfoyle](https://github.com/dreamvo/gilfoyle) - Cloud-native solution to embed media streaming in any application at any scale. - [Dreamvo](https://www.dreamvo.com/) - Free and open source video sharing for the 21th century. ([GitHub](https://github.com/dreamvo/)) - [you-tldr](https://you-tldr.com/) - Easy-to-read transcripts of YouTube videos. ([HN](https://news.ycombinator.com/item?id=26048946)) - [Plyr](https://plyr.io/) - Simple HTML5, YouTube and Vimeo player. ([Code](https://github.com/sampotts/plyr)) - [Remotion](https://www.remotion.dev/) - Create videos programmatically in React. ([Code](https://github.com/JonnyBurger/remotion)) - [Shrink my video](https://acailly.github.io/shrink-my-video/) - Upload your video then get a smaller one, easy. ([Code](https://github.com/acailly/shrink-my-video/)) - [Optimizing Video For Size And Quality (2021)](https://www.smashingmagazine.com/2021/02/optimizing-video-size-quality/) - [What Should I Teach in a Video Tutorial?](https://johnlindquist.com/what-should-i-teach-in-a-video-tutorial/) - [Milk Video](https://milk.video/) - Edit online event recordings quickly. - [NATS Streaming Server](https://github.com/nats-io/nats-streaming-server) - Extremely performant, lightweight reliable streaming platform built on NATS. - [Create animated GIF and WebP from videos using FFmpeg (2021)](https://mattj.io/posts/2021-02-27-create-animated-gif-and-webp-from-videos-using-ffmpeg/) - [PeerTube Index](https://github.com/silicium14/peertube_index) - Centralized search engine for PeerTube videos. ([Web](https://peertube-index.net/)) - [FFMPEG from Zero to Hero Book](https://ffmpegfromzerotohero.com/) ([HN](https://news.ycombinator.com/item?id=26370704)) - [Rally Studios](https://www.rally-studios.com/) - Full service creative studio. - [Video Literature](https://github.com/VideoForage/Video-Lit) - Systems and Networking related Video research published in major venues of Computer Science. - [Ask HN: What home security camera setup do you use? (2021)](https://news.ycombinator.com/item?id=26543233) - [Automatic Video Editing (2021)](https://tratt.net/laurie/blog/entries/automatic_video_editing.html) ([Lobsters](https://lobste.rs/s/amn5pk/automatic_video_editing)) - [Free Video Converter Online](https://vidds.co/free-video-converter/) - WebAssembly and ffmpeg = Quick clip, overlay, resize and GIF-ize videos. ([HN](https://news.ycombinator.com/item?id=26580333)) - [PyTube](https://github.com/pytube/pytube) - Lightweight, dependency-free Python library (and command-line utility) for downloading YouTube Videos. - [Easy video converting for the web (2021)](https://mefody.dev/chunks/ffmpeg-alias/) - [Tips for having video calls with strangers (2021)](https://twitter.com/chrishlad/status/1377724246793801730) - [Meet with Spot](https://www.meetwithspot.com/) - Step away from the screen and try a walking meeting with Spot. - [Jellyfin](https://jellyfin.org/) - Free Software Media System. ([Desktop Code](https://github.com/jellyfin/jellyfin-desktop)) ([GitHub](https://github.com/jellyfin)) ([HN](https://news.ycombinator.com/item?id=28664802)) ([Web Code](https://github.com/jellyfin/jellyfin-web)) ([iOS/tvOS Code](https://github.com/jellyfin/Swiftfin)) - [cam2ip](https://github.com/gen2brain/cam2ip) - Turn any webcam into an IP camera. - [FFmpeg 4.4](http://ffmpeg.org/index.html#pr4.4) ([HN](https://news.ycombinator.com/item?id=26746537)) - [goav](https://github.com/giorgisio/goav) - Go bindings for FFmpeg. - [RUHAcam](https://github.com/penk/ruha.camera) - 3D Printable Retro-style Raspberry Pi HQ Camera. ([Web](https://ruha.camera/)) ([HN](https://news.ycombinator.com/item?id=26859058)) - [FFmpeg cheat sheet](https://gist.github.com/steven2358/ba153c642fe2bb1e47485962df07c730) - [Video Call Checklist](https://checklist.video/) - Definitive Guide to Amazing Video Calls. ([HN](https://news.ycombinator.com/item?id=26944417)) - [FFmpegKit](https://github.com/tanersener/ffmpeg-kit) - FFmpeg Kit for applications. Supports Android, iOS, macOS and tvOS. - [Building video chat into my personal website using WebRTC, WebSockets, and Go (2021)](https://mattbutterfield.com/blog/2021-05-02-adding-video-chat) ([HN](https://news.ycombinator.com/item?id=27029502)) - [Videogrep](https://github.com/antiboredom/videogrep) - Command line tool that searches through dialog in video files. - [SVT Encore](https://github.com/svt/encore) - Scalable video transcoding tool, built on Open Source giants like FFmpeg and Redisson. - [CanCan](https://github.com/dfinity/cancan) - Scalable video-sharing service. - [SRS](https://github.com/ossrs/srs) - Simple, high efficiency and real time video server, supports RTMP/WebRTC/HLS/HTTP-FLV/SRT/GB28181. - [FFmpeg as a Library : libav tutorial](https://github.com/leandromoreira/ffmpeg-libav-tutorial) - [25 Edits That Define the Modern Internet Video (2021)](https://www.vulture.com/2021/05/best-online-videos-tiktok-youtube-vine.html) - [video-stream-merger](https://github.com/t-mullen/video-stream-merger) - Merge multiple video MediaStreams into one composite. - [JOY5](https://github.com/nareix/joy5) - AV Toolkit. - [Snickers](https://github.com/snickers/snickers) - Open source alternative to the video cloud encoding services. - [Video Transcoding API](https://github.com/video-dev/video-transcoding-api) - Agnostic API to transcode media assets across different cloud services. - [Recut](https://getrecut.com/) - Remove Silence From Your Videos Automatically. - [LightTwist](http://lighttwist.io/) - iOS app that turns your room into a customizable virtual video studio. - [OpenHD](https://github.com/OpenHD/Open.HD) - HD video, UAV telemetry, audio, and RC control. ([HN](https://news.ycombinator.com/item?id=27298422)) - [TubeNotes](https://tubenotes.xyz/) - Annotate and Loop Videos. - [Synthesia](https://www.synthesia.io/) - Create AI videos by simply typing in text. ([HN](https://news.ycombinator.com/item?id=27328205)) - [What’s the best YouTube video you’ve ever seen? (2021)](https://twitter.com/patrick_oshag/status/1399040672271941637) - [AVPress](https://avpress.zaps.dev/) - In-browser video compressor. - [How I Make Videos for Programmers (on Fireship.io) (2020)](https://www.youtube.com/watch?v=N6-Q2dgodLs) - [Loom SDK](https://www.loom.com/sdk-beta) - Integrate Loom screen and cam recording to your own products. ([Article](https://www.loom.com/blog/loomsdk-public-beta)) - [ffmpeg-concat](https://github.com/transitive-bullshit/ffmpeg-concat) - Concats a list of videos together using ffmpeg with sexy OpenGL transitions. - [An interactive look at how a video signal is made](https://blog.pizzabox.computer/random/videolines/) ([HN](https://news.ycombinator.com/item?id=27428380)) - [Nettu Meet](https://github.com/fmeringdal/nettu-meet) - Open source video conference web application designed for interactive online tutoring. ([HN](https://news.ycombinator.com/item?id=27434254)) - [Kapwing MP4 Editor](https://www.kapwing.com/tools/mp4-editor) - Edit MP4 Online. - [YT-DLP](https://github.com/yt-dlp/yt-dlp) - youtube-dl fork with additional features and fixes. ([HN](https://news.ycombinator.com/item?id=28319624)) - [Subtitle Horse](https://subtitle-horse.com/) - Browser-based captions editor for subtitling videos online. - [Horahora](https://github.com/horahoradev/horahora) - Microservice-based video hosting website and video archival manager for Bilibili, Niconico, and Youtube. - [tl;dv](https://tldv.io/) - Catch up on Google meetings in minutes. - [Rainway](https://rainway.com/) - Ultra-Low Latency Video Streaming. - [Learn How To Edit Stuff - YouTube](https://www.youtube.com/c/LearnHowToEditStuff/videos) - [Demystify video codecs by writing one in ~100 lines of Rust (2021)](https://blog.tempus-ex.com/hello-video-codec/) - [Piped](https://piped.kavin.rocks/) - Alternative privacy-friendly YouTube frontend which is efficient by design. ([Code](https://github.com/TeamPiped/Piped)) ([HN](https://news.ycombinator.com/item?id=27869188)) - [MoviePy](https://github.com/Zulko/moviepy) - Programmatic Video Editing with Python. ([HN](https://news.ycombinator.com/item?id=27902717)) - [Video Tools and Interfaces: Perspectives From Adobe Research (2021)](https://nickarner.com/notes/video-tools-and-interfaces-perspectives-from-a-webinar-with-adobes-mira-dontcheva-janurary-11-2021/) - [Realtime Video Capture with the Go Programming Language (2021)](https://medium.com/learning-the-go-programming-language/realtime-video-capture-with-go-65a8ac3a57da) - [Motionbox](https://motionbox.io/) - Collaborative video editing and motion graphics tool. - [Better web video with AV1 codec (2019)](https://dev.to/evilmartians/better-web-video-with-av1-codec-52kd) - [Confrere](https://confrere.com/) - Professional video calling, without the hassle. - [Sendspark](https://www.sendspark.com/video-platform/request-videos) - Request Videos from Customers, Colleagues or Friends. - [Supersearch](https://www.supersearch.ai/landingPage) - Copy code from inside any coding video and paste in your text editor and run it. - [Video Fingerprinting (2021)](https://emysound.com/blog/open-source/2021/08/01/video-fingerprinting.html) - When audio fingerprinting is not enough. - [Nebula](https://nebula.app/) - Smart, thoughtful videos from your favorite education-y creators. - [How We Shoot an MKBHD Intro (2021)](https://www.youtube.com/watch?v=pKfbSzTumXk) - [Robust High-Resolution Video Matting with Temporal Guidance](https://peterl1n.github.io/RobustVideoMatting/#/) ([Code](https://github.com/PeterL1n/RobustVideoMatting)) - [The Fatiguing Effects of Camera Use in Virtual Meetings (2021)](https://psycnet.apa.org/fulltext/2021-77825-003.pdf) ([HN](https://news.ycombinator.com/item?id=28351687)) - [yt-dlc](https://github.com/blackjack4494/yt-dlc) - Media downloader and library for various sites. - [Kino](https://kinoweb.dev/) - Sample Video on demand (VOD) app to demonstrate media functionality in the context of a Progressive Web App. ([Code](https://github.com/GoogleChrome/kino)) - [HLS Downloader](https://github.com/puemos/hls-downloader) - Capture and download HTTP Live streams (HLS) from your browser. - [Opal Camera](https://opalcamera.com/) - Professional web camera that helps you look better. ([HN](https://news.ycombinator.com/item?id=28463493)) - [How Bo Burnham made INSIDE (2021)](https://www.youtube.com/watch?v=eZiSApqoI2g) ([Reddit](https://www.reddit.com/r/television/comments/pn4rlk/bo_burnham_wins_his_first_emmy_for_outstanding/)) - [Open Video Downloader (youtube-dl-gui)](https://github.com/jely2002/youtube-dl-gui) - Cross-platform GUI for youtube-dl made in Electron and node.js. ([HN](https://news.ycombinator.com/item?id=28478603)) - [FFmpeg to WebRTC](https://github.com/ashellunts/ffmpeg-to-webrtc) - Stream video from FFmpeg to WebRTC. ([HN](https://news.ycombinator.com/item?id=28614454)) - [µStreamer](https://github.com/pikvm/ustreamer) - Lightweight and fast MJPG-HTTP streamer. - [8 tips to improve Zoom video calls (2021)](https://twitter.com/TrungTPhan/status/1448675891425337345) - [Video Download Tool](https://videodownloadtool.io/) - Download videos, but only the parts you want. ([HN](https://news.ycombinator.com/item?id=28854823)) - [Canva](https://www.canva.com/videos/) - Free and Easy Online Video Editor. - [Plopdown](https://plopdown.video/) - Video Annotating Web Extension. ([Code](https://github.com/spaceribs/plopdown)) - [ZipMessage](https://zipmessage.com/) - Asynchronous video messaging software for remote business. ([Twitter](https://twitter.com/ZipMessageApp)) - [Rustymedia](https://github.com/kevincox/rustymedia) - Media server. It mimics the DLNA protocol and should work with most DLNA clients. - [Tagger](https://github.com/dicej/tagger) - Simple photo and video organizer for the web. - [Viidoo Chat](https://viidoo.chat/) - Secure, Real time, Collaborative. ([GitHub](https://github.com/viidoo-it)) - [hls-video](https://github.com/muxinc/hls-video-element) - Custom element (web component) for playing HTTP Live Streaming (HLS) videos. - [Modfy](https://modfy.video/) - WASM Video Transcoder. ([Code](https://github.com/modfy/modfy.video)) - [Another Video Player](https://github.com/rust-av/avp) - Simple player based on rust-av and SDL2. - [Shotstack](https://shotstack.io/) - Cloud Video Editing API. - [Awesome Video](https://github.com/krzemienski/awesome-video) - Curated list of awesome streaming video tools, frameworks, libraries, and learning resources. - [Astrofox](https://astrofox.io/) - Turn audio into amazing videos. ([Code](https://github.com/astrofox-io/astrofox)) - [YouTube Trends](https://www.youtube.com/trends/) - [Top YouTube 2021 Videos/Creators](https://www.youtube.com/trends/2021/) - [FFrames](https://fframes.studio/) - Open source video creation framework. Make delightful videos with SVG and Rust. ([Twitter](https://twitter.com/fframes_rust)) - [Milk Video](https://app.milkvideo.com/focused-flow) - Turn webinars into shareable highlights. - [Tube Archivist](https://github.com/bbilly1/tubearchivist) - Your self hosted YouTube media server. - [Vidstack Elements](https://github.com/vidstack/elements) - Video player framework for the web. - [How to build large-scale end-to-end encrypted group video calls (2021)](https://signal.org/blog/how-to-build-encrypted-group-calls/) ([HN](https://news.ycombinator.com/item?id=29570938)) - [Camo](https://reincubate.com/camo/) - Use your phone as a pro webcam. - [Video Editing Automation](https://github.com/DevonCrawford/Video-Editing-Automation) - Toolkit of algorithms to automate the video editing process. - [ydls](https://github.com/wader/ydls) - youtube-dl HTTP download and transcode service. - [Netflix-4K-Script](https://github.com/widevinedump/Netflix-4K-Script) - Tool to download Netflix in 4k. - [Long educational videos on YouTube list](https://twitter.com/dan_abramov/status/1476755315492278280) - [Video Transcoding](https://github.com/donmelton/video_transcoding) - Tools to transcode, inspect and convert videos. - [prompeg decoder](https://github.com/kirintwn/prompeg-decoder) - Proxy to recover lost packets from FFmpeg Pro-MPEG video stream. - [xgplayer](https://github.com/bytedance/xgplayer) - HTML5 video player with a parser that saves traffic. - [YouTube playlist manager](https://github.com/glyn/youtube-playlist-manager) - YouTube playlist printing, sorting, etc.	120.098765	364	0.754163	yue_Hant	0.287108
b7eae98ec658d2d37907d1db4e34e4e5a5180650	447	md	Markdown	README.md	misterhay/VISCA-IP-Controller-GUI	e7dcde715f06e14a0e6dff7ab29783fb1663e582	[ "Unlicense" ]	1	2022-01-22T17:06:38.000Z	2022-01-22T17:06:38.000Z	README.md	misterhay/VISCA-IP-Controller-GUI	e7dcde715f06e14a0e6dff7ab29783fb1663e582	[ "Unlicense" ]	null	null	null	README.md	misterhay/VISCA-IP-Controller-GUI	e7dcde715f06e14a0e6dff7ab29783fb1663e582	[ "Unlicense" ]	1	2022-01-22T17:06:45.000Z	2022-01-22T17:06:45.000Z	# VISCA-IP-Controller-GUI A graphical program for controlling PTZ cameras using VISCA commands over a local network. This uses code from [VISCA-IP-Controller](https://github.com/misterhay/VISCA-IP-Controller). Ensure you have [Python](https://www.python.org/) installed, along with [Tkinter](https://www.tutorialspoint.com/how-to-install-tkinter-in-python), use a [binary release](https://github.com/misterhay/VISCA-IP-Controller-GUI/releases).	63.857143	234	0.782998	eng_Latn	0.503786
b7ebe0a386e9f8956a774681fae942124a81e4e9	7,595	md	Markdown	docs/ssms/object/custom-reports-in-management-studio.md	in4matica/sql-docs.de-de	b5a6c26b66f347686c4943dc8307b3b1deedbe7e	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/ssms/object/custom-reports-in-management-studio.md	in4matica/sql-docs.de-de	b5a6c26b66f347686c4943dc8307b3b1deedbe7e	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/ssms/object/custom-reports-in-management-studio.md	in4matica/sql-docs.de-de	b5a6c26b66f347686c4943dc8307b3b1deedbe7e	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- title: Benutzerdefinierte Berichte in Management Studio ms.custom: seo-lt-2019 ms.date: 01/19/2017 ms.prod: sql ms.prod_service: sql-tools ms.reviewer: '' ms.technology: ssms ms.topic: conceptual f1_keywords: - sql13.swb.summary.new.custom.report.f1 helpviewer_keywords: - SQL Server Management Studio [SQL Server], custom reports ms.assetid: 1ba3f758-f39b-4f5f-91ca-516cedc78979 author: markingmyname ms.author: maghan ms.openlocfilehash: 0e5dafb96c0bb94fcb2dd0134fefb3f96b7c5708 ms.sourcegitcommit: b78f7ab9281f570b87f96991ebd9a095812cc546 ms.translationtype: HT ms.contentlocale: de-DE ms.lasthandoff: 01/31/2020 ms.locfileid: "75257227" --- # <a name="custom-reports-in-management-studio"></a>Benutzerdefinierte Berichte in Management Studio [!INCLUDE[appliesto-ss-asdb-asdw-pdw-md](../../includes/appliesto-ss-asdb-asdw-pdw-md.md)] In [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)]wird von vielen Objekt-Explorer-Knoten ein Satz von Standardberichten angezeigt, die von [!INCLUDE[msCoName](../../includes/msconame_md.md)]erstellt werden. In diesen Berichten werden häufig angeforderte Serverinformationen zusammengefasst. Seit [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)] Service Pack 2 können in [!INCLUDE[ssBIDevStudioFull](../../includes/ssbidevstudiofull_md.md)] von [!INCLUDE[ssManStudio](../../includes/ssmanstudio-md.md)]erstellte benutzerdefinierte Berichte von Administratoren ausgeführt werden. ## <a name="implementation"></a>Implementierung Benutzerdefinierte Berichte werden als RDL-Dateien gespeichert und mithilfe der Berichtsdefinitionssprache (Report Definition Language, RDL) erstellt. In der Berichtsdefinitionssprache sind Informationen zum Datenabruf und Datenlayout für einen Bericht in einem XML-Format enthalten. Die Berichtsdefinitionssprache ist ein offenes Schema. Entwickler können die Berichtsdefinitionssprache mit zusätzlichen Attributen und Elementen erweitern. Jede gültige [!INCLUDE[tsql](../../includes/tsql-md.md)] -Anweisung in einem Bericht kann von Berichten ausgeführt wird. Wurde für den Objekt-Explorer eine Verbindung mit einem Server hergestellt, können benutzerdefinierte Berichte im Kontext der aktuellen Objekt-Explorer-Auswahl ausgeführt werden, wenn von den Berichten auf Berichtsparameter dieses Knotens verwiesen wird. Dadurch wird ermöglicht, dass im Bericht der aktuelle Kontext (beispielsweise die aktuelle Datenbank) oder ein konsistenter Kontext (beispielsweise die Angabe einer designierten Datenbank als Teil der im benutzerdefinierten Bericht enthaltenen [!INCLUDE[tsql](../../includes/tsql-md.md)] -Anweisung) verwendet wird. ## <a name="running-a-custom-report"></a>Ausführen eines benutzerdefinierten Berichts Es gibt folgenden Möglichkeiten zum Ausführen eines benutzerdefinierten Berichts in [!INCLUDE[ssManStudio](../../includes/ssmanstudio-md.md)] : - Klicken Sie im Objekt-Explorer mit der rechten Maustaste auf einen Knoten, zeigen Sie auf Berichte , und klicken Sie mit der linken Maustaste auf Benutzerdefinierte Berichte. Suchen Sie im Dialogfeld Datei öffnen einen Ordner mit RDL-Dateien, und öffnen Sie dann die entsprechende Berichtsdatei. - Klicken Sie im Objekt-Explorer mit der rechten Maustaste auf einen Knoten, zeigen Sie auf Berichte, zeigen Sie auf Benutzerdefinierte Berichte, und wählen Sie dann aus der Liste der zuletzt geöffneten Dateien einen benutzerdefinierten Bericht aus. ## <a name="limitations"></a>Einschränkungen Berücksichtigen Sie bei der Verwendung benutzerdefinierter Berichte die folgenden Einschränkungen: - Um die unbeabsichtigte Ausführung von bösartigem Code zu verhindern, kann [!INCLUDE[ssManStudio](../../includes/ssmanstudio-md.md)] auch dann nicht für das automatische Ausführen eines Berichts konfiguriert werden, wenn das Dateisystem so konfiguriert ist, dass RDL-Dateien [!INCLUDE[ssManStudio](../../includes/ssmanstudio-md.md)]zugeordnet werden. In [!INCLUDE[ssManStudio](../../includes/ssmanstudio-md.md)] können Berichte weder programmgesteuert noch an der Eingabeaufforderung über [!INCLUDE[ssManStudio](../../includes/ssmanstudio-md.md)]ausgeführt werden. - Benutzerdefinierte Berichte können in einem Kontext ausgeführt werden, in dem die erwarteten Werte nicht erstellt werden. Sie können beispielsweise einen Bericht über die Replikation im Kontext einer Datenbank ausführen, die nicht in der Replikation involviert ist, oder Sie können einen Bericht als ein Benutzer ausführen, der nicht über die Berechtigung für den Zugriff auf Informationen verfügt, die zum Generieren eines präzisen Berichts erforderlich sind. Der Ersteller des benutzerdefinierten Berichts ist für die Gültigkeit der Berichtsstruktur und seines Kontexts verantwortlich. - Sie können der Liste der Standardberichte keinen benutzerdefinierten Bericht hinzufügen. - Der vom Bericht verarbeitete Code kann möglicherweise Auswirkungen auf die Serverleistung haben. - Unterberichte werden von benutzerdefinierten Berichten nicht unterstützt. - Der Befehlstext für die einzelnen Abfragen im Bericht darf nicht über einen Ausdruck definiert sein. - Mit jedem in einem Befehl (Abfrage) verwendeten Abfrageparameter kann nur auf einen einzelnen Berichtsparameter verwiesen werden. Ausdrucksoperatoren können nicht verwendet werden. - Für Berichtsbefehle (Abfragen) werden nur Befehle vom Typ Text und gespeicherte Prozedur unterstützt. - Das Berichtsframework bietet keine Parameter zum Erstellen von Escapezeichen für die Abfragen. Abfrageautoren müssen sicherstellen, dass ihre Abfragen frei von SQL Injection-Angriffen sind. ## <a name="managing-custom-reports"></a>Verwalten von benutzerdefinierten Berichten Für Benutzer, die über eine Vielzahl benutzerdefinierter Berichte verfügen, empfiehlt es sich, diese mithilfe der Dateisystemordner zu organisieren, die über entsprechende NTFS-Dateisystemberechtigungen verfügen. ## <a name="permissions"></a>Berechtigungen Benutzerdefinierte Berichte werden mithilfe der Berechtigungen des aktuellen Benutzers ausgeführt. Berechtigungen für den Dateisystemordner mit den Berichtsdateien müssen so festgelegt werden, dass der Zugriff eingeschränkt wird, um das Ändern der vom Bericht ausgeführten Abfragen durch einen böswilligen Benutzer zu verhindern. Sowohl für den Benutzer als auch für das vom [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] -Dienst verwendete Konto ist Lesezugriff auf den Dateisystemordner mit den Berichtsdateien erforderlich. Jeder gültige [!INCLUDE[dnprdnshort](../../includes/dnprdnshort_md.md)] -Befehl kann in einen Bericht eingebettet werden, der Befehl wird jedoch nicht ausgeführt. > [!CAUTION] > Jede gültige [!INCLUDE[tsql](../../includes/tsql-md.md)] -Anweisung kann in einem Bericht eingebettet und von einem Bericht aus ausgeführt werden. Durch das Ausführen eines Berichts unter einem Benutzerkonto mit hohen Privilegien wird die problemlose Ausführung dieser eingebetteten Anweisungen ermöglicht. ## <a name="see-also"></a>Weitere Informationen [Hinzufügen eines benutzerdefinierten Berichts zu Management Studio](../../ssms/object/add-a-custom-report-to-management-studio.md) [Aufheben der Unterdrückung von Warnungen für das Ausführen von benutzerdefinierten Berichten](../../ssms/object/unsuppress-run-custom-report-warnings.md) [Verwenden benutzerdefinierter Berichte mit Eigenschaften von Objekt-Explorer-Knoten](../../ssms/object/use-custom-reports-with-object-explorer-node-properties.md)	93.765432	610	0.803292	deu_Latn	0.994171
b7ec2341022b3453fa196bc98ee20785e20b2078	8,580	md	Markdown	README.md	mre/quick-protobuf	8d67376c4de089fe7353a5970b519d55696ce754	[ "MIT" ]	null	null	null	README.md	mre/quick-protobuf	8d67376c4de089fe7353a5970b519d55696ce754	[ "MIT" ]	null	null	null	README.md	mre/quick-protobuf	8d67376c4de089fe7353a5970b519d55696ce754	[ "MIT" ]	1	2020-01-22T17:48:34.000Z	2020-01-22T17:48:34.000Z	# quick-protobuf A pure Rust library to serialize/deserialize [protobuf](https://developers.google.com/protocol-buffers) files. [Documentation](https://docs.rs/quick-protobuf) ## Description This library intends to provide a simple yet fast (minimal allocations) protobuf parser implementation. It provides both: - [pb-rs](pb-rs), a code generation tool: - each `.proto` file will generate a minimal rust module (one function to read, one to write, and one to compute the size of the messages) - each message will generate a rust struct where: \| Proto \| Rust \| \|------------------------------\|-------------------------\| \| bytes \| `Cow<'a, [u8]>` \| \| string \| `Cow<'a, str>` \| \| other scalars \| rust primitive \| \| repeated \| `Vec` \| \| repeated, packed, fixed size \| `Cow<'a, [M]>` \| \| optional \| `Option` \| \| message \| `struct` \| \| enum \| `enum` \| \| map \| `HashMap` \| \| oneof Name \| `OneOfName` enum \| \| nested `m1` \| `mod_m1` module \| \| package `a.b` \| `mod_a::mod_b` modules \| \| import file_a.proto \| `use super::file_a::` \| - no need to use google `protoc` tool to generate the modules - [quick-protobuf](quick-protobuf), a protobuf file parser: - this is the crate that you will typically refer to in your library. The generated modules will assume it has been imported. - it acts like an event parser, the logic to convert it into struct is handle by `pb-rs` ## Example: protobuf_example project - 1. Install pb-rs* binary to convert your proto file into a quick-protobuf compatible source code ```sh cargo install pb-rs pb-rs /path/to/your/protobuf/file.proto # will generate a # /path/to/your/protobuf/file.rs ``` - 2. Add a dependency to quick-protobuf ```toml # Cargo.toml [dependencies] quick-protobuf = "0.6.2" ``` - 3. Have fun ```rust extern crate quick_protobuf; mod foo_bar; // (see 1.) use quick_protobuf::Reader; // We will suppose here that Foo and Bar are two messages defined in the .proto file // and converted into rust structs // // FooBar is the root message defined like this: // message FooBar { // repeated Foo foos = 1; // repeated Bar bars = 2; // } // FooBar is a message generated from a proto file // in parcicular it contains a `from_reader` function use foo_bar::FooBar; use quick_protobuf::{MessageRead, BytesReader}; fn main() { // bytes is a buffer on the data we want to deserialize // typically bytes is read from a `Read`: // r.read_to_end(&mut bytes).expect("cannot read bytes"); let mut bytes: Vec<u8>; # bytes = vec![]; // we can build a bytes reader directly out of the bytes let mut reader = BytesReader::from_bytes(&bytes); // now using the generated module decoding is as easy as: let foobar = FooBar::from_reader(&mut reader, &bytes).expect("Cannot read FooBar"); // if instead the buffer contains a length delimited stream of message we could use: // while !r.is_eof() { // let foobar: FooBar = r.read_message(&bytes).expect(...); // ... // } println!("Found {} foos and {} bars", foobar.foos.len(), foobar.bars.len()); } ``` ## Examples directory You can find basic examples in the [examples](examples) directory. - [pb_rs_example](quick-protobuf/examples/pb_rs_example.rs): A basic write/read loop on all datatypes ## Message <-> struct The best way to check for all kind of generated code is to look for the codegen_example data: - definition: [data_types.proto](quick-protobuf/examples/pb_rs/data_types.proto) - generated code: [data_types.rs](quick-protobuf/examples/pb_rs/data_types.rs) #### Proto definition ``` enum FooEnum { FIRST_VALUE = 1; SECOND_VALUE = 2; } message BarMessage { required int32 b_required_int32 = 1; } message FooMessage { optional int32 f_int32 = 1; optional int64 f_int64 = 2; optional uint32 f_uint32 = 3; optional uint64 f_uint64 = 4; optional sint32 f_sint32 = 5; optional sint64 f_sint64 = 6; optional bool f_bool = 7; optional FooEnum f_FooEnum = 8; optional fixed64 f_fixed64 = 9; optional sfixed64 f_sfixed64 = 10; optional fixed32 f_fixed32 = 11; optional sfixed32 f_sfixed32 = 12; optional double f_double = 13; optional float f_float = 14; optional bytes f_bytes = 15; optional string f_string = 16; optional FooMessage f_self_message = 17; optional BarMessage f_bar_message = 18; repeated int32 f_repeated_int32 = 19; repeated int32 f_repeated_packed_int32 = 20 [ packed = true ]; } ``` #### Generated structs ```rust #[derive(Debug, PartialEq, Eq, Clone, Copy)] pub enum FooEnum { FIRST_VALUE = 1, SECOND_VALUE = 2, } #[derive(Debug, Default, PartialEq, Clone)] pub struct BarMessage { // all fields are owned: no lifetime parameter pub b_required_int32: i32, } #[derive(Debug, Default, PartialEq, Clone)] pub struct FooMessage<'a> { // has borrowed fields: lifetime parameter pub f_int32: Option<i32>, pub f_int64: Option<i64>, pub f_uint32: Option<u32>, pub f_uint64: Option<u64>, pub f_sint32: Option<i32>, pub f_sint64: Option<i64>, pub f_bool: Option<bool>, pub f_FooEnum: Option<FooEnum>, pub f_fixed64: Option<u64>, pub f_sfixed64: Option<i64>, pub f_fixed32: Option<u32>, pub f_sfixed32: Option<i32>, pub f_double: Option<f64>, pub f_float: Option<f32>, pub f_bytes: Option<Cow<'a, [u8]>>, // bytes -> Cow<[u8]> pub f_string: Option<Cow<'a, str>> // string -> Cow<str> pub f_self_message: Option<Box<FooMessage<'a>>>, // reference cycle -> Boxed message pub f_bar_message: Option<BarMessage>, pub f_repeated_int32: Vec<i32>, // repeated: Vec pub f_repeated_packed_int32: Vec<i32>, // repeated packed: Vec } ``` ### Leverage rust module system #### Nested Messages ``` message A { message B { // ... } } ``` As rust does not allow a struct and a module to share the same name, we use `mod_Name` for the nested messages. ```rust pub struct A { //... } pub mod mod_A { pub struct B { // ... } } ``` #### Package ``` package a.b; ``` Here we could have used the same name, but for consistency with nested messages, modules are prefixed with `mod_` as well. ```rust pub mod mod_a { pub mod mod_b { // ... } } ``` ## Why not rust-protobuf This library is an alternative to the widely used [rust-protobuf](https://github.com/stepancheg/rust-protobuf). #### Pros / Cons - Pros - [Much faster](quick-protobuf/benches/rust-protobuf), in particular when working with string, bytes and repeated packed fixed size fields (no extra allocation) - No need to install `protoc` on your machine - No trait objects: faster/simpler parser - Very simple generated modules (~10x smaller) so you can easily understand what is happening - Cons - Less popular - most rust-protobuf tests have been migrated here (see [v2](quick-protobuf/tests/rust_protobuf/v2/mod.rs) and [v3](quick-protobuf/tests/rust_protobuf/v3/mod.rs)) - quick-protobuf is being used by many people now and is very reliable - [some missing functionalities](https://github.com/tafia/quick-protobuf/issues/12) - Not a drop-in replacement of rust-protobuf - everything being explicit you have to handle more things yourself (e.g. `Option` unwrapping, `Cow` management) #### Codegen Have a look at the different generated modules for the same .proto file: - [rust-protobuf](https://github.com/tafia/quick-protobuf/blob/master/benches/rust-protobuf/perftest_data.rs): 2371 loc - [quick-protobuf](https://github.com/tafia/quick-protobuf/blob/master/benches/rust-protobuf/perftest_data_quick.rs): 302 loc #### Benchmarks See [perftest](perftest), an adaptation of rust protobuf's perftest. Depending on your scenario each crate has its merit. quick-protobuf is particularly good at reading large bytes. ## Contribution Any help is welcomed! (Pull requests of course, bug report, missing functionality etc...) ## Licence MIT	32.623574	166	0.64021	eng_Latn	0.915234
b7ec3b5c926ff2fd972568510c72b2b9e77bff36	2,803	md	Markdown	README.md	getnibble/nibble	4728fc842bebf233d258fc484cd25b9905e9d356	[ "MIT" ]	1	2019-01-27T13:02:40.000Z	2019-01-27T13:02:40.000Z	README.md	getnibble/nibble	4728fc842bebf233d258fc484cd25b9905e9d356	[ "MIT" ]	null	null	null	README.md	getnibble/nibble	4728fc842bebf233d258fc484cd25b9905e9d356	[ "MIT" ]	1	2019-01-27T13:02:41.000Z	2019-01-27T13:02:41.000Z	Nibble Specs: Ascending reward system to stave off insta-mining, pre-mining, unfair rewards for early adopters. Block 1 - 2016 @ 1 NBL Block 2017 - 4032 @ 2 NBL Block 4033 - 6047 @ 4 NBL Block 6048 - 8063 @ 8 NBL Block 8064 - 10079 @ 16 NBL Block 10080 - 12095 @ 32 NBL * Difficulty SHOULD reach 1+ at this point. Total NBL mined = 127,004 Block 12096 - 219555 @ 50 NBL Block 219556 - 639555 @ 25 NBL 21,000,004 total NBL (4 more than Bitcoin) 639,555 total blocks 2 1/2 minute blocks (4 times faster than Bitcoin) 2016 Block Difficulty Retarget Why is this system better? Litecoin's 1st 12,096 blocks produced 604,800 LTC - though GPU mining wasn't released to the general public (but that's not it wasn't used) Feathercoin's 1st 12,096 blocks produced 2,419,200 FTC Nibble's 1st 12,096 blocks will produce 127,054 NBL Ports: 8550 Connect 8551 JSON RPC Solo Mining: 1) Download the client or daemon for your OS 2) Launch the or daemon. 3) Create a nibble.conf file in the correct location for yoru OS: Windows: %appdata%\nibble\nibble.conf Linux: ~/.nibble/nibble.conf nibble.conf** rpcuser=[replace with username] rpcpassword=[replace with password] rpcport=[replace with any port you wish] rpcallowip=[* for all, or IP of a remote system] daemon=1 server=1 4) start your daemon or client with the -server option. For example: >nibble-qt.exe -server 5) Point your favorite miner to the IP of the machine running the server. Use the port and username/password as specified in the above nibble.conf file. Development process =================== Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready. The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if they don't match the project's coding conventions (see coding.txt) or are controversial. The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are regularly created to indicate new official, stable release versions of Litecoin. Feature branches are created when there are major new features being worked on by several people. From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure. The pull will be closed 15 days after the warning if action is not taken by the author. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'. Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled 'stale'. Check out http://getnibble.org for more info about the development.	32.976471	153	0.767749	eng_Latn	0.997752
b7ec9e28ac5833f9cb341736b656b631d685e08d	7,101	md	Markdown	microsoft-365/admin/email/about-shared-mailboxes.md	MicrosoftDocs/microsoft-365-docs-pr.sv-SE	67c51064aaff2914491449e43535fc7def5015de	[ "CC-BY-4.0", "MIT" ]	7	2020-05-18T20:11:59.000Z	2022-03-20T21:41:46.000Z	microsoft-365/admin/email/about-shared-mailboxes.md	MicrosoftDocs/microsoft-365-docs-pr.sv-SE	67c51064aaff2914491449e43535fc7def5015de	[ "CC-BY-4.0", "MIT" ]	null	null	null	microsoft-365/admin/email/about-shared-mailboxes.md	MicrosoftDocs/microsoft-365-docs-pr.sv-SE	67c51064aaff2914491449e43535fc7def5015de	[ "CC-BY-4.0", "MIT" ]	4	2020-12-20T22:21:14.000Z	2022-01-30T13:16:26.000Z	--- title: Om delade postlådor f1.keywords: - NOCSH ms.author: sharik author: SKjerland manager: scotv audience: Admin ms.topic: article ms.service: o365-administration ms.localizationpriority: medium ms.collection: - M365-subscription-management - Adm_O365 - Adm_TOC ms.custom: - MSStore_Link - AdminSurgePortfolio - okr_smb - AdminTemplateSet search.appverid: - BCS160 - MET150 - MOE150 description: Delade postlådor används när flera personer behöver åtkomst till samma postlåda. Lär dig vad du behöver veta innan du skapar en delad postlåda. ms.openlocfilehash: 11251ccc964e02a656a9978170443f6492ac1deb ms.sourcegitcommit: d4b867e37bf741528ded7fb289e4f6847228d2c5 ms.translationtype: MT ms.contentlocale: sv-SE ms.lasthandoff: 10/06/2021 ms.locfileid: "60165274" --- # <a name="about-shared-mailboxes"></a>Om delade postlådor Delade postlådor används när flera personer behöver åtkomst till samma postlåda, t. ex. företagsinformation eller supportens e-postadress, receptionen eller andra funktioner som kan delas av flera personer. Användare som har behörighet till gruppens postlåda kan skicka som eller skicka för postlådans e-postadress om administratören har gett dig behörighet att göra det. Det här är särskilt användbart för postlådor i hjälp och support eftersom användare kan skicka e-post från "contoso support" eller "Byggnad As reception". ## <a name="before-you-begin"></a>Innan du börjar Innan du [skapar en delad postlåda](create-a-shared-mailbox.md)finns det några saker du bör känna till: - Licenser: Den delade postlådan kan lagra upp till 50 GB data utan att du behöver tilldela en licens till den. Därefter måste du tilldela postlådan en licens för att kunna lagra mer data. Mer information om licensiering av delade postlådor finns i [Exchange Online Begränsningar.](/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#StorageLimits) När en delad postlåda når lagringsgränsen kommer du att kunna ta emot e-post ett tag till, men du kommer inte att kunna skicka ny e-post. Därefter slutar den att ta emot e-post. De som skickar e-post till postlådan får ett meddelande om utebliven leverans. - Användarbehörigheter: Du måste ge användare behörighet (medlemskap) att använda den delade postlådan. Det är bara personer i organisationen som kan använda en delad postlåda. - Externa användare: Du kan inte ge personer utanför företaget (t.ex. har ett Gmail-konto) åtkomst till den delade postlådan. Om du vill göra det kan du skapa en grupp för Outlook stället. Mer information finns i [Skapa en Microsoft 365 grupp i administrationscentret](../create-groups/create-groups.md). - Använd med Outlook: Förutom att använda Outlook på webben från webbläsaren för att komma åt delade postlådor kan du också använda appen Outlook för iOS eller Outlook för Android. Mer information finns i Lägga [till en delad postlåda i Outlook mobil](https://support.microsoft.com/office/f866242c-81b2-472e-8776-6c49c5473c9f). Ett annat alternativ är att skapa en grupp för den delade postlådan. Mer information finns i [Jämföra grupper.](../create-groups/compare-groups.md) - Kryptering: Du kan inte kryptera e-post som skickas från en delad postlåda. Det beror på att en delad postlåda inte har ett eget säkerhetssammanhang (användarnamn/lösenord) och kan därför inte tilldelas en nyckel. Om fler än en person är medlem och de skickar/tar emot e-postmeddelanden som de krypterat med sina egna nycklar kanske andra medlemmar kan läsa e-postmeddelandet och andra kanske inte, beroende på vilken offentlig nyckel e-postmeddelandet krypterades med. - Konvertering av postlåda: Du kan konvertera användarpostlådor till delade postlådor. Se [Konvertera en användarpostlåda till en delad postlåda](convert-user-mailbox-to-shared-mailbox.md). - Administratörsroller: Användare med globala administratörs- Exchange administratörsroller kan skapa delade postlådor. - Prenumerationskrav: Om du vill skapa en delad postlåda måste du prenumerera på ett Microsoft 365 för företag-abonnemang som innehåller e-Exchange Online posttjänsten. E Microsoft 365-applikationer för affärsverksamhet prenumerationen inkluderar inte e-post. Microsoft 365 Business Standard även e-post. - Logga in: En delad postlåda är inte avsedd för direkt inloggning via det associerade användarkontot. Du bör alltid blockera inloggning för det delade postlådekontot och behålla det blockerat. - För många användare: Om det finns för många användare som samtidigt ansluter till en delad postlåda (högst 25 rekommenderas) kan det hända att de inte kan ansluta till den här postlådan eller har inkonsekvenser som meddelanden som dupliceras i utkorgen. I det här fallet kan du minska antalet användare eller använda en annan arbetsbelastning, till exempel en Microsoft 365 grupp eller en offentlig mapp. - Meddelandeborttagning: Det går tyvärr inte att hindra andra från att ta bort meddelanden i en delad postlåda. Det enda sättet runt det här är att skapa Microsoft 365 grupp i stället för en delad postlåda. En grupp i Outlook är som en delad postlåda. En jämförelse mellan de två finns i [Jämföra grupper.](../create-groups/compare-groups.md) Mer information om grupper finns i [Läs mer om grupper.](https://support.microsoft.com/office/b565caa1-5c40-40ef-9915-60fdb2d97fa2) > [!NOTE] > För att komma åt en delad postlåda måste användaren Exchange Online en licens, men den delade postlådan kräver ingen separat licens. Alla delade postlådor har ett motsvarande användarkonto. Lade du märke till att du inte behövde ange något lösenord när du skapade den delade postlådan? Kontot har ett lösenord, men det genereras av systemet (okänt). Du bör inte använda kontot för att logga in på den delade postlådan. Utan licens är delade postlådor begränsade till 50 GB. För att öka storleksgränsen till 100 GB måste den delade postlådan tilldelas en licens Exchange Online abonnemang 2. Licensen Exchange Online abonnemang 1 med en Exchange Online - arkivering-tilläggslicens ökar bara storleken på arkivpostlådan. Det här gör det också möjligt att aktivera automatiskt expanderande arkivering för ytterligare lagringskapacitet. Om du vill skapa bevarande av juridiska skäl för en delad postlåda måste den delade postlådan ha en Exchange Online abonnemang 2-licens eller en Exchange Online abonnemang 1-licens med en Exchange Online - arkivering-tilläggslicens. Om du vill använda avancerade funktioner som Microsoft Defender för Office 365, Advanced eDiscovery eller automatiska bevarandeprinciper måste den delade postlådan vara licensierad för dessa funktioner. ## <a name="related-content"></a>Relaterat innehåll [Skapa en delad postlåda](create-a-shared-mailbox.md) (artikel)\ [Konfigurera en delad postlåda](configure-a-shared-mailbox.md) (artikel)\ [Konvertera en användarpostlåda till en delad postlåda](convert-user-mailbox-to-shared-mailbox.md) (artikel)\ [Ta bort en licens från en delad postlåda](remove-license-from-shared-mailbox.md) (artikel)\ [Lösa problem med delade postlådor](resolve-issues-with-shared-mailboxes.md) (artikel)	93.434211	1,270	0.809041	swe_Latn	0.999872
b7ecd24a619a31fcecc4ebb2e7d8964f76173bde	1,473	md	Markdown	_posts/2016-06-25-ALYCE-Paris-Alyce-Special-Occasion-Dress-Style-6453-2015.md	gownthlala/gownthlala.github.io	f86dbdf6fa0e98646ca4cb470fa2928a56e04eec	[ "MIT" ]	null	null	null	_posts/2016-06-25-ALYCE-Paris-Alyce-Special-Occasion-Dress-Style-6453-2015.md	gownthlala/gownthlala.github.io	f86dbdf6fa0e98646ca4cb470fa2928a56e04eec	[ "MIT" ]	null	null	null	_posts/2016-06-25-ALYCE-Paris-Alyce-Special-Occasion-Dress-Style-6453-2015.md	gownthlala/gownthlala.github.io	f86dbdf6fa0e98646ca4cb470fa2928a56e04eec	[ "MIT" ]	null	null	null	--- layout: post date: 2016-06-25 title: "ALYCE Paris Alyce Special Occasion Dress - Style 6453 2015" category: ALYCE Paris tags: [ALYCE Paris,2015] --- ### ALYCE Paris Alyce Special Occasion Dress - Style 6453 Just $469.99 ### 2015 <table><tr><td>BRANDS</td><td>ALYCE Paris</td></tr><tr><td>Years</td><td>2015</td></tr></table> <a href="https://www.readybrides.com/en/alyce-paris/56492-alyce-paris-alyce-special-occasion-dress-style-6453.html"><img src="//img.readybrides.com/133354/alyce-paris-alyce-special-occasion-dress-style-6453.jpg" alt="ALYCE Paris Alyce Special Occasion Dress - Style 6453" style="width:100%;" /></a> <!-- break --><a href="https://www.readybrides.com/en/alyce-paris/56492-alyce-paris-alyce-special-occasion-dress-style-6453.html"><img src="//img.readybrides.com/133355/alyce-paris-alyce-special-occasion-dress-style-6453.jpg" alt="ALYCE Paris Alyce Special Occasion Dress - Style 6453" style="width:100%;" /></a> <a href="https://www.readybrides.com/en/alyce-paris/56492-alyce-paris-alyce-special-occasion-dress-style-6453.html"><img src="//img.readybrides.com/133353/alyce-paris-alyce-special-occasion-dress-style-6453.jpg" alt="ALYCE Paris Alyce Special Occasion Dress - Style 6453" style="width:100%;" /></a> Buy it: [https://www.readybrides.com/en/alyce-paris/56492-alyce-paris-alyce-special-occasion-dress-style-6453.html](https://www.readybrides.com/en/alyce-paris/56492-alyce-paris-alyce-special-occasion-dress-style-6453.html)	86.647059	312	0.745418	yue_Hant	0.340736
b7edc7fa9205f4817f3c4e2c4f1100d38f48d798	35	md	Markdown	README.md	DeliciousFlask/DeliciousFlask-4.1	dfe9be563e31d7429a356340f5290a5ab4ee4b0b	[ "MIT" ]	null	null	null	README.md	DeliciousFlask/DeliciousFlask-4.1	dfe9be563e31d7429a356340f5290a5ab4ee4b0b	[ "MIT" ]	null	null	null	README.md	DeliciousFlask/DeliciousFlask-4.1	dfe9be563e31d7429a356340f5290a5ab4ee4b0b	[ "MIT" ]	null	null	null	# DeliciousFlask-4.1 App responses	11.666667	20	0.8	eng_Latn	0.286841
b7ee64b304fd6610f9c12b97f90b27e099787b9c	8,583	md	Markdown	articles/active-directory/managed-identities-azure-resources/how-to-assign-app-role-managed-identity-powershell.md	pmsousa/azure-docs.pt-pt	bc487beff48df00493484663c200e44d4b24cb18	[ "CC-BY-4.0", "MIT" ]	15	2017-08-28T07:46:17.000Z	2022-02-03T12:49:15.000Z	articles/active-directory/managed-identities-azure-resources/how-to-assign-app-role-managed-identity-powershell.md	pmsousa/azure-docs.pt-pt	bc487beff48df00493484663c200e44d4b24cb18	[ "CC-BY-4.0", "MIT" ]	407	2018-06-14T16:12:48.000Z	2021-06-02T16:08:13.000Z	articles/active-directory/managed-identities-azure-resources/how-to-assign-app-role-managed-identity-powershell.md	pmsousa/azure-docs.pt-pt	bc487beff48df00493484663c200e44d4b24cb18	[ "CC-BY-4.0", "MIT" ]	17	2017-10-04T22:53:31.000Z	2022-03-10T16:41:59.000Z	--- title: Atribua uma identidade gerida a uma função de aplicação utilizando PowerShell - Azure AD description: Instruções passo a passo para atribuir um acesso de identidade gerido ao papel de outra aplicação, utilizando o PowerShell. services: active-directory documentationcenter: '' author: johndowns manager: '' editor: '' ms.service: active-directory ms.subservice: msi ms.devlang: na ms.topic: how-to ms.tgt_pltfrm: na ms.workload: identity ms.date: 12/10/2020 ms.author: jodowns ms.collection: M365-identity-device-management ms.custom: devx-track-azurepowershell ms.openlocfilehash: 5150c26d67b77008c11764cc6e51ca7085ffcb31 ms.sourcegitcommit: 4b0e424f5aa8a11daf0eec32456854542a2f5df0 ms.translationtype: MT ms.contentlocale: pt-PT ms.lasthandoff: 04/20/2021 ms.locfileid: "107784916" --- # <a name="assign-a-managed-identity-access-to-an-application-role-using-powershell"></a>Atribuir um acesso de identidade gerido a uma função de aplicação utilizando o PowerShell Identidades geridas para recursos Azure fornecem aos serviços Azure uma identidade no Azure Ative Directory. Funcionam sem precisar de credenciais no seu código. Os serviços Azure utilizam esta identidade para autenticar serviços que suportem a autenticação AZURE AD. As funções de aplicação fornecem uma forma de controlo de acesso baseado em funções e permitem que um serviço implemente regras de autorização. Neste artigo, aprende-se a atribuir uma identidade gerida a uma função de aplicação exposta por outra aplicação utilizando o Azure AD PowerShell. [!INCLUDE [az-powershell-update](../../../includes/updated-for-az.md)] ## <a name="prerequisites"></a>Pré-requisitos - Se não está familiarizado com as identidades geridas para os recursos da Azure, consulte a [secção de visão geral.](overview.md) Certifique-se de rever a [diferença entre uma identidade gerida atribuída ao sistema e atribuída ao utilizador](overview.md#managed-identity-types). - Se ainda não tiver uma conta do Azure, [inscreva-se numa conta gratuita](https://azure.microsoft.com/free/) antes de continuar. - Para executar os scripts de exemplo, tem duas opções: - Utilize o [Azure Cloud Shell,](../../cloud-shell/overview.md)que pode abrir utilizando o botão Try It no canto superior direito dos blocos de código. - Executar scripts localmente instalando a versão mais recente do [Azure AD PowerShell](/powershell/azure/active-directory/install-adv2). ## <a name="assign-a-managed-identity-access-to-another-applications-app-role"></a>Atribuir um acesso de identidade gerido à função de app de outra aplicação 1. Ativar a identidade gerida num recurso Azure, [como um Azure VM](qs-configure-powershell-windows-vm.md). 1. Encontre a identificação do objeto do principal de serviço da identidade gerida. Para uma identidade gerida atribuída ao sistema, pode encontrar o ID do objeto no portal Azure na página identidade do recurso. Também pode utilizar o seguinte script PowerShell para encontrar o ID do objeto. Você precisará do ID de recursos do recurso que criou no passo 1, que está disponível no portal Azure na página propriedades do recurso. ```powershell $resourceIdWithManagedIdentity = '/subscriptions/{my subscription ID}/resourceGroups/{my resource group name}/providers/Microsoft.Compute/virtualMachines/{my virtual machine name}' (Get-AzResource -ResourceId $resourceIdWithManagedIdentity).Identity.PrincipalId ``` Para uma identidade gerida atribuída pelo utilizador, pode encontrar o ID do objeto de identidade gerida no portal Azure na página geral do recurso. Também pode utilizar o seguinte script PowerShell para encontrar o ID do objeto. Vai precisar da identificação de recursos da identidade gerida atribuída pelo utilizador. ```powershell $userManagedIdentityResourceId = '/subscriptions/{my subscription ID}/resourceGroups/{my resource group name}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{my managed identity name}' (Get-AzResource -ResourceId $userManagedIdentityResourceId).Properties.PrincipalId ``` 1. Crie um novo registo de inscrição para representar o serviço ao que a sua identidade gerida enviará um pedido. Se a API ou o serviço que expõe a subvenção de função da app à identidade gerida já tem um diretor de serviço no seu inquilino AZure AD, ignore este passo. Por exemplo, se pretender conceder o acesso de identidade gerido à API do Gráfico microsoft, pode saltar este passo. 1. Encontre a identificação do objeto do principal serviço da aplicação de serviço. Pode encontrar isto usando o portal Azure. Vá ao Azure Ative Directory e abra a página de aplicações da Enterprise, em seguida, encontre a aplicação e procure o ID do objeto. Também pode encontrar o ID do objeto do principal do serviço pelo seu nome de exibição utilizando o seguinte script PowerShell: ```powershell $serverServicePrincipalObjectId = (Get-AzureADServicePrincipal -Filter "DisplayName eq '$applicationName'").ObjectId ``` > [!NOTE] > Os nomes de exibição para aplicações não são únicos, pelo que deve verificar se obtém o principal de serviço da aplicação correta. 1. Adicione um [papel de aplicação](../develop/howto-add-app-roles-in-azure-ad-apps.md) à aplicação que criou no passo 3. Pode criar a função utilizando o portal Azure ou utilizando o Microsoft Graph. Por exemplo, pode adicionar um papel de aplicação como este: ```json { "allowedMemberTypes": [ "Application" ], "displayName": "Read data from MyApi", "id": "0566419e-bb95-4d9d-a4f8-ed9a0f147fa6", "isEnabled": true, "description": "Allow the application to read data as itself.", "value": "MyApi.Read.All" } ``` 1. Atribua o papel da aplicação à identidade gerida. Necessitará das seguintes informações para atribuir o papel da aplicação: * `managedIdentityObjectId`: o iD do objeto do principal de serviço da identidade gerida, que encontrou no passo 2. * `serverServicePrincipalObjectId`: o iD do objeto do principal de serviço da aplicação do servidor, que encontrou no passo 4. * `appRoleId`: o ID da função da aplicação exposta pela aplicação do servidor, que gerou no passo 5 - no exemplo, o ID da função da aplicação é `0566419e-bb95-4d9d-a4f8-ed9a0f147fa6` . Execute o seguinte script PowerShell para adicionar a atribuição de funções: ```powershell New-AzureADServiceAppRoleAssignment -ObjectId $managedIdentityObjectId -Id $appRoleId -PrincipalId $managedIdentityObjectId -ResourceId $serverServicePrincipalObjectId ``` ## <a name="complete-script"></a>Script completo Este script de exemplo mostra como atribuir a identidade gerida de uma aplicação web Azure a um papel de app. ```powershell # Install the module. (You need admin on the machine.) # Install-Module AzureAD # Your tenant ID (in the Azure portal, under Azure Active Directory > Overview). $tenantID = '<tenant-id>' # The name of your web app, which has a managed identity that should be assigned to the server app's app role. $webAppName = '<web-app-name>' $resourceGroupName = '<resource-group-name-containing-web-app>' # The name of the server app that exposes the app role. $serverApplicationName = '<server-application-name>' # For example, MyApi # The name of the app role that the managed identity should be assigned to. $appRoleName = '<app-role-name>' # For example, MyApi.Read.All # Look up the web app's managed identity's object ID. $managedIdentityObjectId = (Get-AzWebApp -ResourceGroupName $resourceGroupName -Name $webAppName).identity.principalid Connect-AzureAD -TenantId $tenantID # Look up the details about the server app's service principal and app role. $serverServicePrincipal = (Get-AzureADServicePrincipal -Filter "DisplayName eq '$serverApplicationName'") $serverServicePrincipalObjectId = $serverServicePrincipal.ObjectId $appRoleId = ($serverServicePrincipal.AppRoles \| Where-Object {$_.Value -eq $appRoleName }).Id # Assign the managed identity access to the app role. New-AzureADServiceAppRoleAssignment ` -ObjectId $managedIdentityObjectId ` -Id $appRoleId ` -PrincipalId $managedIdentityObjectId ` -ResourceId $serverServicePrincipalObjectId ``` ## <a name="next-steps"></a>Passos seguintes - [Identidade gerida para visão geral dos recursos da Azure](overview.md) - Para permitir a identidade gerida num Azure VM, consulte [identidades geridas configure para recursos Azure num VM Azure utilizando o PowerShell](qs-configure-powershell-windows-vm.md).	60.443662	411	0.774205	por_Latn	0.99171
b7eedfda2258c82562518a5f52e91e67ee27365b	40	md	Markdown	README.md	csuastt/liusm	818588f93bf4edeee2ec8eaee9579132943caf5a	[ "MIT" ]	1	2021-12-03T09:05:30.000Z	2021-12-03T09:05:30.000Z	README.md	csuastt/Stereo-Enhancement-of-Thermal-Imaging	818588f93bf4edeee2ec8eaee9579132943caf5a	[ "MIT" ]	null	null	null	README.md	csuastt/Stereo-Enhancement-of-Thermal-Imaging	818588f93bf4edeee2ec8eaee9579132943caf5a	[ "MIT" ]	null	null	null	# Stereo-Enhancement-of-Thermal-Imaging	20	39	0.825	deu_Latn	0.260931
b7efc5c1f59d762383b19ef78ecf292533534ca0	21,501	md	Markdown	docs/connect/ado-net/connection-strings-and-configuration-files.md	PowerBee-AK/sql-docs.de-de	f6f4854db855a89c4e49dc0557fa456da060b3c7	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/connect/ado-net/connection-strings-and-configuration-files.md	PowerBee-AK/sql-docs.de-de	f6f4854db855a89c4e49dc0557fa456da060b3c7	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/connect/ado-net/connection-strings-and-configuration-files.md	PowerBee-AK/sql-docs.de-de	f6f4854db855a89c4e49dc0557fa456da060b3c7	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- title: Verbindungszeichenfolgen und Konfigurationsdateien description: Erfahren Sie, wie Verbindungszeichenfolgen für ADO.NET-Anwendungen als bewährte Methode für Sicherheit und Wartung in einer Anwendungskonfigurationsdatei gespeichert werden können. ms.date: 11/13/2020 dev_langs: - csharp ms.assetid: 37df2641-661e-407a-a3fb-7bf9540f01e8 ms.prod: sql ms.prod_service: connectivity ms.technology: connectivity ms.topic: conceptual author: David-Engel ms.author: v-daenge ms.reviewer: v-chmalh ms.openlocfilehash: 8f1e0ac5fc52576f0e47ccb8be4b8e90899c6e68 ms.sourcegitcommit: c938c12cf157962a5541347fcfae57588b90d929 ms.translationtype: HT ms.contentlocale: de-DE ms.lasthandoff: 12/25/2020 ms.locfileid: "97771457" --- # <a name="connection-strings-and-configuration-files"></a>Verbindungszeichenfolgen und Konfigurationsdateien [!INCLUDE[appliesto-netfx-netcore-xxxx-md](../../includes/appliesto-netfx-netcore-xxxx-md.md)] [!INCLUDE[Driver_ADONET_Download](../../includes/driver_adonet_download.md)] Das Einbetten von Verbindungszeichenfolgen in den Code Ihrer Anwendung kann zu Sicherheitslücken und Wartungsproblemen führen. Unverschlüsselte Verbindungszeichenfolgen, die in den Quellcode einer Anwendung kompiliert wurden, können mit dem Tool [Ildasm.exe (IL Disassembler)](/dotnet/framework/tools/ildasm-exe-il-disassembler) angezeigt werden. Hinzu kommt, dass die Anwendung neu kompiliert werden muss, wenn sich die Verbindungszeichenfolge irgendwann einmal ändert. Aus diesen Gründen empfehlen wir, Verbindungszeichenfolgen in einer Anwendungskonfigurationsdatei zu speichern. ## <a name="work-with-application-configuration-files"></a>Arbeiten mit Anwendungskonfigurationsdateien Anwendungskonfigurationsdateien enthalten anwendungsspezifische Einstellungen. Eine ASP.NET-Anwendung kann beispielsweise mindestens eine web.config-Datei enthalten, und eine Windows-Anwendung kann eine optionale app.config-Datei enthalten. Konfigurationsdateien haben etliche Elemente gemein, auch wenn sich der Name und der Speicherort der Konfigurationsdateien abhängig vom jeweiligen Host der Anwendung ändert. ### <a name="the-connectionstrings-section"></a>connectionStrings-Abschnitt Verbindungszeichenfolgen können als Schlüssel/Wert-Paare im Abschnitt connectionStrings des configuration-Elements einer Anwendungskonfigurationsdatei gespeichert werden. Zu den untergeordneten Elementen gehören add, clear und remove. Das folgende Konfigurationsdateifragment zeigt das Schema und die Syntax für das Speichern einer Verbindungszeichenfolge. Das name-Attribut ist ein Name, den Sie zum eindeutigen Identifizieren einer Verbindungszeichenfolge angeben, damit diese zur Laufzeit abgerufen werden kann. providerName ist Microsoft.Data.SqlClient mit dem Microsoft SqlClient-Datenanbieter für SQL Server. ```xml <?xml version='1.0' encoding='utf-8'?> <configuration> <connectionStrings> <clear /> <add name="Name" providerName="Microsoft.Data.SqlClient" connectionString="Valid Connection String;" /> </connectionStrings> </configuration> ``` > [!NOTE] > Sie können einen Teil der Verbindungszeichenfolge in einer Konfigurationsdatei speichern und zur Vervollständigung zur Laufzeit die <xref:System.Data.Common.DbConnectionStringBuilder>-Klasse verwenden. Diese Vorgehensweise empfiehlt sich in Szenarien, in denen Ihnen die Elemente der Verbindungszeichenfolge vorab nicht bekannt sind oder wenn Sie sicherheitsrelevante Informationen nicht in einer Konfigurationsdatei speichern möchten. Weitere Informationen finden Sie in [Connection String Builders (Verbindungszeichenfolgengeneratoren)](connection-string-builders.md). ### <a name="use-external-configuration-files"></a>Verwenden externer Konfigurationsdateien Externe Konfigurationsdateien sind separate Dateien, die ein aus einem einzigen Abschnitt bestehendes Fragment einer Konfigurationsdatei enthalten. Auf die externe Konfigurationsdatei wird dann von der Hauptkonfigurationsdatei verwiesen. Das Speichern des Abschnitts connectionStrings in einer separaten Datei empfiehlt sich, wenn die Verbindungszeichenfolgen auch nach der Bereitstellung der Anwendung noch geändert werden können. ASP.NET verhält sich z. B. standardmäßig so, dass nach Änderungen an Konfigurationsdateien eine Anwendung neu gestartet wird, wodurch Statusinformationen verloren gehen. Änderungen an einer externen Konfigurationsdatei hingegen führen nicht zum Neustart der Anwendung. Externe Konfigurationsdateien sind nicht auf ASP.NET beschränkt und können auch von Windows-Anwendungen verwendet werden. Außerdem kann der Zugriff auf externe Konfigurationsdateien auch durch Dateizugriffssicherheit und Berechtigungen eingeschränkt werden. Der Einsatz externer Konfigurationsdateien zur Laufzeit ist transparent und erfordert keine besondere Codierung. Wenn Sie Verbindungszeichenfolgen in einer externen Konfigurationsdatei speichern möchten, erstellen Sie eine separate Datei, die ausschließlich den connectionStrings-Abschnitt enthält. Nehmen Sie in diese Datei keine zusätzlichen Elemente, Abschnitte oder Attribute auf. Das folgende Beispiel zeigt die Syntax für eine externe Konfigurationsdatei. ```xml <connectionStrings> <add name="Name" providerName="Microsoft.Data.SqlClient" connectionString="Valid Connection String;" /> </connectionStrings> ``` Verwenden Sie in der Hauptkonfigurationsdatei der Anwendung das configSource-Attribut, um den vollqualifizierten Namen und den Speicherort der externen Datei anzugeben. Das folgende Beispiel verweist auf eine Konfigurationsdatei mit dem Namen `connections.config`. ```xml <?xml version='1.0' encoding='utf-8'?> <configuration> <connectionStrings configSource="connections.config"/> </configuration> ``` ## <a name="retrieving-connection-strings-at-run-time"></a>Abrufen von Verbindungszeichenfolgen zur Laufzeit Mit .NET Framework 2.0 wurden neue Klassen im <xref:System.Configuration>-Namespace eingeführt, um das Abrufen von Verbindungszeichenfolgen aus Konfigurationsdateien zur Laufzeit zu vereinfachen. Sie können programmgesteuert eine Verbindungszeichenfolge nach Namen oder Anbieternamen abrufen. > [!NOTE] > Die Datei machine.config enthält auch einen connectionStrings-Abschnitt, der von Visual Studio verwendete Verbindungszeichenfolgen enthält. Beim Abrufen von Verbindungszeichenfolgen anhand des Anbieternamens aus der Datei app.config in einer Windows-Anwendung werden zuerst die in machine.config vorhandenen Verbindungszeichenfolgen und dann die in app.config vorhandenen Verbindungszeichenfolgen geladen. Wenn unmittelbar hinter dem connectionStrings-Element clear hinzugefügt wird, werden alle geerbten Verweise aus der Datenstruktur im Arbeitsspeicher entfernt, sodass nur die in der lokalen Datei app.config definierten Verbindungszeichenfolgen berücksichtigt werden. ### <a name="work-with-the-configuration-files"></a>Arbeiten mit den Konfigurationsdateien Ab .NET Framework 2.0 wird bei der Arbeit mit Konfigurationsdateien auf dem lokalen Computer der <xref:System.Configuration.ConfigurationManager> verwendet, der die <xref:System.Configuration.ConfigurationSettings> ersetzt. Für die Arbeit mit ASP.NET-Konfigurationsdateien kommt der <xref:System.Web.Configuration.WebConfigurationManager> zum Einsatz. Er wurde für die Verwendung mit den auf einem Webserver befindlichen Konfigurationsdateien entwickelt und erlaubt den programmgesteuerten Zugriff auf Konfigurationsdateiabschnitte, wie z.B. system.web. > [!NOTE] > Wenn ein Aufrufer zur Laufzeit auf Konfigurationsdateien zugreifen können soll, benötigt er Berechtigungen. Welche Berechtigungen notwendig sind, hängt von der Art der Anwendung, der Konfigurationsdatei und dem Speicherort ab. Weitere Informationen finden Sie unter [Verwenden der Konfigurationsklassen](/previous-versions/aspnet/ms228063(v=vs.100)) und <xref:System.Web.Configuration.WebConfigurationManager> (für ASP.NET-Anwendungen) und unter <xref:System.Configuration.ConfigurationManager> (für Windows-Anwendungen). Zum Abrufen von Verbindungszeichenfolgen aus Anwendungskonfigurationsdateien können Sie die <xref:System.Configuration.ConnectionStringSettingsCollection> verwenden. Sie enthält eine Auflistung von <xref:System.Configuration.ConnectionStringSettings>-Objekten, wobei jedes Objekt für einen einzelnen Eintrag im connectionStrings-Abschnitt steht. Ihre Eigenschaften werden entsprechenden Verbindungszeichenfolgenattributen zugeordnet, sodass es möglich ist, Verbindungszeichenfolgen nach dem Namen oder dem Anbieternamen abzurufen. \|Eigenschaft\|BESCHREIBUNG\| \|--------------\|-----------------\| \|<xref:System.Configuration.ConnectionStringSettings.Name%2A>\|Name der Verbindungszeichenfolge: Wird dem name-Attribut zugeordnet.\| \|<xref:System.Configuration.ConnectionStringSettings.ProviderName%2A>\|Vollqualifizierter Anbietername: Wird dem providerName-Attribut zugeordnet.\| \|<xref:System.Configuration.ConnectionStringSettings.ConnectionString%2A>\|Verbindungszeichenfolge. Wird dem connectionString-Attribut zugeordnet.\| ### <a name="example-listing-all-connection-strings"></a>Beispiel: Auflisten aller Verbindungszeichenfolgen Dieses Beispiel iteriert durch <xref:System.Configuration.ConnectionStringSettingsCollection> und zeigt die Eigenschaften <xref:System.Configuration.ConnectionStringSettings.Name%2A?displayProperty=nameWithType>, <xref:System.Configuration.ConnectionStringSettings.ProviderName%2A?displayProperty=nameWithType> und <xref:System.Configuration.ConnectionStringSettings.ConnectionString%2A?displayProperty=nameWithType> im Konsolenfenster an. > [!NOTE] > <legacyBold>System.Configuration.dll</legacyBold> ist nicht in allen Projekttypen enthalten, sodass Sie u. U. einen Verweis einfügen müssen, um die Konfigurationsklassen zu verwenden. Wie die jeweilige Anwendungskonfigurationsdatei heißt und wo sie gespeichert ist, hängt von der Art der Anwendung und dem Hostingprozess ab. [!code-csharp[DataWorks ConnectionStringSettings.RetrieveFromConfig#1](~/../SqlClient/doc/samples/ConnectionStringSettings_RetrieveFromConfig.cs#1)] ### <a name="example-retrieving-a-connection-string-by-name"></a>Beispiel: Abrufen einer Verbindungszeichenfolge über den Namen In diesem Beispiel wird gezeigt, wie eine Verbindungszeichenfolge aus einer Konfigurationsdatei durch Angabe ihres Namens abgerufen werden kann. Der Code erstellt ein <xref:System.Configuration.ConnectionStringSettings>-Objekt, das den bereitgestellten Eingabeparameter mit dem <xref:System.Configuration.ConfigurationManager.ConnectionStrings%2A>-Namen abgleicht. Wird kein übereinstimmender Name gefunden, gibt die Funktion `null` (`Nothing` in Visual Basic) zurück. [!code-csharp[DataWorks ConnectionStringSettings.RetrieveFromConfigByName#1](~/../SqlClient/doc/samples/ConnectionStringSettings_RetrieveFromConfigByName.cs#1)] ### <a name="example-retrieving-a-connection-string-by-provider-name"></a>Beispiel: Abrufen einer Verbindungszeichenfolge über den Anbieternamen In diesem Beispiel wird gezeigt, wie eine Verbindungszeichenfolge durch Angabe des Anbieternamens im Format Microsoft.Data.SqlClient abgerufen werden kann. Der Code durchläuft die <xref:System.Configuration.ConnectionStringSettingsCollection> und gibt die Verbindungszeichenfolge für den ersten gefundenen <xref:System.Configuration.ConnectionStringSettings.ProviderName%2A>-Eintrag zurück. Wird kein Anbietername gefunden, gibt die Funktion `null` (`Nothing` in Visual Basic) zurück. [!code-csharp[DataWorks ConnectionStringSettings.RetrieveFromConfigByProvider#1](~/../SqlClient/doc/samples/ConnectionStringSettings_RetrieveFromConfigByProvider.cs#1)] ## <a name="encrypt-configuration-file-sections-using-protected-configuration"></a>Verschlüsseln von Konfigurationsdateiabschnitten mithilfe der geschützten Konfiguration In ASP.NET 2.0 wurde mit der geschützten Konfiguration ein neues Feature eingeführt, mit dem Sie sicherheitsrelevante Informationen in einer Konfigurationsdatei verschlüsseln können. Die geschützte Konfiguration wurde zwar primär für ASP.NET entwickelt, sie kann aber auch zum Verschlüsseln von Konfigurationsdateiabschnitten in Windows-Anwendungen verwendet werden. Eine ausführliche Beschreibung der Funktionen der geschützten Konfiguration finden Sie unter [Verschlüsseln von Konfigurationsinformationen mithilfe der geschützten Konfiguration](/previous-versions/aspnet/53tyfkaw(v=vs.100)). Das folgende Konfigurationsdateifragment zeigt den connectionStrings-Abschnitt nach der Verschlüsselung. configProtectionProvider gibt den Anbieter für die geschützte Konfiguration an, der zum Verschlüsseln und Entschlüsseln der Verbindungszeichenfolgen verwendet wird. Der EncryptedData-Abschnitt enthält den Verschlüsselungstext. ```xml <connectionStrings configProtectionProvider="DataProtectionConfigurationProvider"> <EncryptedData> <CipherData> <CipherValue>AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAH2... </CipherValue> </CipherData> </EncryptedData> </connectionStrings> ``` Wenn die verschlüsselte Verbindungszeichenfolge zur Laufzeit abgerufen wird, verwendet .NET Framework den angegebenen Anbieter, um den CipherValue zu entschlüsseln und ihn für Ihre Anwendung zur Verfügung zu stellen. Sie müssen für die Verwaltung des Entschlüsselungsprozesses keinen zusätzlichen Code schreiben. ### <a name="protected-configuration-providers"></a>Anbieter geschützter Konfigurationen Die Anbieter für die geschützte Konfiguration werden im configProtectedData-Abschnitt der Datei machine.config auf dem lokalen Computer registriert, wie dies im folgenden Fragment dargestellt ist. Das Fragment enthält die beiden Anbieter für die geschützte Konfiguration in .NET Framework. Die hier gezeigten Werte wurden aus Gründen der besseren Lesbarkeit gekürzt. ```xml <configProtectedData defaultProvider="RsaProtectedConfigurationProvider"> <providers> <add name="RsaProtectedConfigurationProvider" type="System.Configuration.RsaProtectedConfigurationProvider" /> <add name="DataProtectionConfigurationProvider" type="System.Configuration.DpapiProtectedConfigurationProvider" /> </providers> </configProtectedData> ``` Sie können zusätzliche Anbieter für die geschützte Konfiguration konfigurieren, indem Sie sie der Datei machine.config hinzufügen. Sie können auch einen eigenen Anbieter für die geschützte Konfiguration erstellen, indem Sie von der abstrakten Basisklasse <xref:System.Configuration.ProtectedConfigurationProvider> erben. In der folgenden Tabelle werden die zwei in .NET Framework enthaltenen Anbieter für die geschützte Konfiguration beschrieben. \|Anbieter\|Beschreibung\| \|--------------\|-----------------\| \|<xref:System.Configuration.RsaProtectedConfigurationProvider>\|Verwendet zum Verschlüsseln und Entschlüsseln der Daten den RSA-Verschlüsselungsalgorithmus. Der RSA-Algorithmus kann sowohl für die Verschlüsselung mit öffentlichem Schlüssel als auch für digitale Signaturen verwendet werden. Er wird auch als "öffentlicher Schlüssel" oder asymmetrische Verschlüsselung bezeichnet, da bei dieser Art der Verschlüsselung zwei verschiedene Schlüssel eingesetzt werden. Mit dem [ASP.NET IIS-Registrierungstool (Aspnet_regiis.exe)](/previous-versions/dotnet/netframework-3.5/k6h9cz8h(v=vs.90)) können Sie die Abschnitte in einer Web.config-Datei verschlüsseln und die Verschlüsselungsschlüssel verwalten. ASP.NET entschlüsselt die Konfigurationsdatei, wenn die Datei verarbeitet wird. Die Identität der ASP.NET-Anwendung muss berechtigt sein, den Verschlüsselungsschlüssel zu lesen, mit dem die verschlüsselten Abschnitte verschlüsselt und entschlüsselt werden.\| \|<xref:System.Configuration.DpapiProtectedConfigurationProvider>\|Verwendet zum Verschlüsseln der Konfigurationsabschnitte die Windows-Datenschutz-API (DPAPI). Die DPAPI verwendet die in Windows integrierten Kryptografiedienste, und sie kann für den computerspezifischen oder den benutzerkontospezifischen Schutz konfiguriert werden. Der computerspezifische Schutz bietet sich an, wenn auf demselben Server mehrere Anwendungen vorhanden sind, die Informationen gemeinsam nutzen müssen. Die Verwendung des benutzerkontospezifischen Schutzes empfiehlt sich bei Diensten, die mit einer bestimmten Benutzeridentität, z. B. einer freigegebenen gehosteten Umgebung, ausgeführt werden. Jede Anwendung wird unter einer separaten Identität ausgeführt, die den Zugriff auf Ressourcen wie z. B. Dateien und Datenbanken einschränkt.\| Beide Anbieter bieten eine starke Verschlüsselung der Daten. Wenn Sie aber beabsichtigen, ein und dieselbe verschlüsselte Konfigurationsdatei auf mehreren Servern, z. B. in einer Webfarm, zu verwenden, müssen Sie den <xref:System.Configuration.RsaProtectedConfigurationProvider> verwenden, da nur er die Möglichkeit bietet, die zum Verschlüsseln der Daten verwendeten Verschlüsselungsschlüssel zu exportieren und sie auf einem anderen Server zu importieren. Weitere Informationen finden Sie unter [Importieren und Exportieren von RSA-Schlüsselcontainern mit geschützter Konfiguration](/previous-versions/aspnet/yxw286t2(v=vs.100)). ### <a name="use-the-configuration-classes"></a>Verwenden der Konfigurationsklassen Der <xref:System.Configuration>-Namespace stellt Klassen zum programmgesteuerten Arbeiten mit Konfigurationseinstellungen bereit. Die <xref:System.Configuration.ConfigurationManager>-Klasse ermöglicht den Zugriff auf Computer-, Anwendungs- und Benutzerkonfigurationsdateien. Beim Erstellen einer ASP.NET-Anwendung können Sie die <xref:System.Web.Configuration.WebConfigurationManager>-Klasse verwenden, die dieselbe Funktionalität bietet, Ihnen gleichzeitig aber auch Zugriff auf Einstellungen erlaubt, die es so nur in ASP.NET-Anwendungen gibt, beispielsweise die Einstellungen in \<system.web> . > [!NOTE] > Der <xref:System.Security.Cryptography>-Namespace enthält Klassen, die zusätzliche Optionen zum Verschlüsseln und Entschlüsseln von Daten bereitstellen. Verwenden Sie diese Klassen, wenn Sie Kryptografiedienste benötigen, die bei Verwendung der geschützten Konfiguration nicht verfügbar sind. Einige dieser Klassen sind Wrapper für die nicht verwaltete Microsoft CryptoAPI, während es sich bei anderen Klassen um verwaltete Implementierungen handelt. Weitere Informationen finden Sie unter [Kryptografiedienste](/previous-versions/visualstudio/visual-studio-2008/93bskf9z(v=vs.90)). ### <a name="appconfig-example"></a>Beispiel für app.config In diesem Beispiel wird gezeigt, wie Sie die Verschlüsselung des Abschnitts connectionStrings in der Datei app.config einer Windows-Anwendung aktivieren und deaktivieren können. In diesem Beispiel übernimmt die Prozedur den Namen der Anwendung, z. B. MyApplication.exe, als Argument. Die Datei app.config wird dann verschlüsselt und in den Ordner kopiert, der die ausführbare Datei mit dem Namen „MyApplication.exe.config“ enthält. > [!NOTE] > Die Verbindungszeichenfolge kann nur auf dem Computer entschlüsselt werden, auf dem sie verschlüsselt wurde. Der Code öffnet die Datei app.config mit der <xref:System.Configuration.ConfigurationManager.OpenExeConfiguration%2A>-Methode, um sie bearbeiten zu können, und die <xref:System.Configuration.ConfigurationManager.GetSection%2A>-Methode gibt den connectionStrings-Abschnitt zurück. Der Code überprüft nun die <xref:System.Configuration.SectionInformation.IsProtected%2A>-Eigenschaft, indem er die <xref:System.Configuration.SectionInformation.ProtectSection%2A>-Methode aufruft, um den Abschnitt zu verschlüsseln, sofern dieser nicht bereits verschlüsselt ist. Die <xref:System.Configuration.SectionInformation.UnprotectSection%2A>-Methode wird aufgerufen, um den Abschnitt zu entschlüsseln. Die <xref:System.Configuration.Configuration.Save%2A>-Methode schließt den Vorgang ab und speichert die Änderungen. > [!NOTE] > Sie müssen in Ihrem Projekt einen Verweis auf `System.Configuration.dll` angeben, damit der Code ausgeführt wird. [!code-csharp[DataWorks ConnectionStrings.Encrypt#1](~/../SqlClient/doc/samples/ConnectionStrings_Encrypt.cs#1)] ### <a name="webconfig-example"></a>Beispiel für web.config Das folgende Beispiel verwendet die <xref:System.Web.Configuration.WebConfigurationManager.OpenWebConfiguration%2A>-Methode `WebConfigurationManager`. Beachten Sie, dass Sie in diesem Fall den relativen Pfad zur Datei Web.config mit einer Tilde angeben können. Der Code benötigt einen Verweis auf die `System.Web.Configuration`-Klasse. [!code-csharp[DataWorks ConnectionStringsWeb.Encrypt#1](~/../SqlClient/doc/samples/ConnectionStringsWeb_Encrypt.cs#1)] Weitere Informationen zum Absichern von ASP.NET-Anwendungen finden Sie unter [Absichern von ASP.NET-Websites](/previous-versions/aspnet/91f66yxt(v=vs.100)). ## <a name="see-also"></a>Weitere Informationen - [Verbindungszeichenfolgen-Generatoren](connection-string-builders.md) - [Schützen von Verbindungsinformationen](protecting-connection-information.md) - [Verwenden der Konfigurationsklassen](/previous-versions/visualstudio/visual-studio-2008/ms228063(v=vs.90)) - [Konfigurieren von Apps](/dotnet/framework/configure-apps/index) - [ASP.NET-Websiteverwaltung](/previous-versions/aspnet/6hy1xzbw(v=vs.100)) - [Microsoft ADO.NET für SQL Server](microsoft-ado-net-sql-server.md)	107.505	1,075	0.824985	deu_Latn	0.990552
b7f040d6a37a439cb244cb2bc3b7381e22028792	7,132	md	Markdown	_i18n/es/_posts/2021-01-21-git_config.md	raquelfishes/raquelfishes.github.io	2beabf8bdea8b669bed878990428190acb80f8e3	[ "MIT" ]	null	null	null	_i18n/es/_posts/2021-01-21-git_config.md	raquelfishes/raquelfishes.github.io	2beabf8bdea8b669bed878990428190acb80f8e3	[ "MIT" ]	1	2020-06-04T18:47:08.000Z	2020-06-04T18:47:08.000Z	_i18n/es/_posts/2021-01-21-git_config.md	raquelfishes/raquelfishes.github.io	2beabf8bdea8b669bed878990428190acb80f8e3	[ "MIT" ]	2	2020-07-18T09:04:46.000Z	2020-07-18T09:10:47.000Z	--- layout: post title: "Todos los secretos para configurar Git" author: raquel date: '2021-01-21' category: - Git - Github image: assets/img/posts/git_config.jpg --- <blockquote> El ordenador (a lo que añadiría los repositorios) nacieron para resolver problemas que antes no existían. Bill Gates </blockquote> ¿Cuántas veces has subido algo a un repositorio con el usuario que no deberías? ¿Quieres cambiar tu configuración de Git? ¿No sabes dónde se guarda la configuración o cómo consultarla? Si es así este artículo es para tí, así podrás amplicar los conocimientos para trabajar con repositorios Git. Así que, ¡allá vamos! ## Configuración de git Son muchas las opciones que tenemos para configurar nuestra consola de Git desde el usuario hasta el editor que queremos usar por defecto, y eso mismo lo podemos configurar para un repositorio concreto o entorno local, y para configurarlo a nivel genérico o global. Toda nuestra configuración de Git se puede modificar y consultar a través de la herramienta `git config` y añadir los flags que queramos en concreto para obtener y establer las variables de configuración que controlan el aspecto y funcionamiento de Git. Toda la documentación oficial sobre la configuración de Git puedes encontrarla en su [página oficial](git_config_web) ## Dónde se guarda esa configuración y cómo la consulto Hay varios niveles de configuración en Git: sistema, global, local y worktree, los cuales se corresponden con cada uno de los entornos en los que podemos configurar nuestra relación con Git. Cada una de estas configuraciones se guarda en un fichero diferente y vamos "pisando" la configuración de los entornos más genéricos a los más específicos. La lista ordenada de la configuración más general a la más específica es la siguiente con el path correspondiente a su archivo de configuración y el comando de git para consultar la configuración de ese fichero: 1. System: \[directorio_instalacion_git\]/etc/gitconfig `$ git config --system --list` 2. Global: \[HOME\]/.gitconfig `$ git config --global --list` 3. Local: \[repositorio_git\]/.git/config `$ git config --local --list` 4. Worktree: \[repositorio_git\]/.git/config.worktree `$ git config --worktree --list` Donde normalmente los paths serán: * \[directorio_instalación_git\] * Windows: C:/Program Files/Git/ * Linux: ~etc/ * \[HOME\] * Windows: C:/Users/\[username\] * Linux: ~home/\[username\] o ~root/ No te preocupes si no encuentras alguno de los ficheros Git no los genera hasta que no son referenciados por primera vez Si quieres ver de qué fichero está cogiendo qué configuración en cada momento puedes usar el siguiente comando el cual muestra el fichero y qué configuración aplica con algunos ejemplos de lo que puede salir. Como puedes ver en el ejemplo el editor aprece en la configuracion del sistema y global, y el usuario en la global y local. ```console $ git config --list --show-origin file:C:/Program Files/Git/etc/gitconfig core.editor="C:\\Program Files\\Sublime Text 3\\sublime_text.exe" ... file:C:/Users/Fishes/.gitconfig user.name=Raquel file:C:/Users/Fishes/.gitconfig core.editor=vim ... file:.git/config user.name=Rachel ... ``` Y por último si quieres ver o modificar uno de esos ficheros directamente tienes el comando `edit`, para cada uno de los entornos. ```console $ git config --system --edit $ git config --global --edit $ git config --local --edit $ git config --worktree --edit ``` Recuerda, que las configuraciones más específicas van a sobreescribir las más genéricas. ## ¿Qué configuro primero? El usuario Si ves muchas cosas que no entiendes, y te lias con tanta configuración, no te preocupes. La mayoría lo usarás por defecto. Lo primero es lo primero, a configurar tu usuario, si no tienes usuario no vas a poder hacer ni un commit. Así que vamos a configurar el nombre de usuario y correo electrónico a nivel global y no te preocupes esta información no va a parar a ninguna lista de correo ni nada, se tratará como metadatos para identificar tus cambios en el repositorio Git. Puedes modificar la configuración tanto por ficheros o por consola de comandos, yo prefiero la segunda opción. ```console $ git config --global user.name raquel $ git config --global user.email [email protected] ``` Pero a mi también me resulta muy útil configurar el usuario a nivel local, por ejemplo para repositorios de trabajo en los que ya tengo una configuración diferente a nivel global y no quiero tocarla, sólo tendría que cambiar el flag de global a local. ```console $ git config --local user.name Raquel $ git config --local user.email [email protected] ``` Si tienes dudas, siempre puedes comprobar el valor de un clave específica de la configuración ejecutando `git config <clave>` ```console $ git config user.name Raquel $ git config user.email [email protected] ``` Y adiós a subir cambios con usuarios equivocados. ## ¿Qué más puedo configurar? El editor Ahora que ya tenemos configurada la identidad del usuario, también puedes elegir el editor de texto por defecto que se utilizará cuando Git necesite que introduzcas un mensaje. Ten en cuenta que si no indicas nada, Git usará el editor por defecto del sistema, que generalmente es Vim. Puedes seleccionar tanto los que vienen preinstalados en el sistema como el que tú suelas utilizar, por ejemplo Sublime o NotePad++, y al igual que antes puedes cambiarlo para los diferentes niveles, aunque yo recomiendo hacerlo a nivel global. Te dejo aquí los comandos correspondientes \| Atom \| `git config –global core.editor "atom wait"` \| \| emacs \| `git config –global core.editor "emacs"` \| \| Textmate \| `git config –global core.editor "mate –w"` \| \| Vim \| `git config –global core.editor "vim"` \| \| Sublime \| `git config –global core.editor "'C:\\Program Files\\Sublime Text 3\\sublime_text.exe' -w"` \| \| NotePad++ \| `git config –global core.editor "'C:/Program Files/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin"` \| ## Quiero eliminar mi configuración Para borrar una configuración de git, hay que usar el comando `unset`. ```console $ git config --global --unset core.editor ``` Es probable, que por error tengamos puesta una configuración dos veces y que el comando anterior de error. Para esos casos tenemos otro comando más potente `unset-all`, con él se eliminarán todas las líneas que coincidan con la clave indicada ```console $ git config --global --unset-all core.editor ``` ## ¿Y ahora qué? Aún hay muchos más comandos y trucos, por lo que intentaré compartir algunos de los comandos que más útiles me resultan a mi en mi día a día. Mientras espero que este artículo os haya resultado útil. Ahora, ¡a divertirse! ¡Gracias por leer! =) [git_config_web]: https://www.git-scm.com/book/es/v2/Personalizaci%C3%B3n-de-Git-Configuraci%C3%B3n-de-Git	48.189189	371	0.735698	spa_Latn	0.989725
b7f0895d97027a061c20c9af485d7de34431cb9e	1,584	md	Markdown	README.md	Jason-Cooke/dart-neats	48a1b947076ce1a4e81449464af4364a2ddb6bad	[ "Apache-2.0" ]	2	2019-08-08T15:31:08.000Z	2020-01-18T23:13:16.000Z	README.md	Jason-Cooke/dart-neats	48a1b947076ce1a4e81449464af4364a2ddb6bad	[ "Apache-2.0" ]	null	null	null	README.md	Jason-Cooke/dart-neats	48a1b947076ce1a4e81449464af4364a2ddb6bad	[ "Apache-2.0" ]	null	null	null	Dart Neats [![Build Status](https://travis-ci.org/google/dart-neats.svg?branch=master)](https://travis-ci.org/google/dart-neats) ========== _A collection of a small neat packages for dart._ Disclaimer: This is not an officially supported Google product. This repository is meant as a playground where small _neat_ packages are cultivated. If package grows too large and complex and needs a dedicated issue tracker it should be moved to a dedicated repository. Each folder in this repository contains a _neat_ `pub` package. This project aims to use a separate package whenever it makes sense to have an independent major verison. This often means splitting functionality into separate packages, which can be reused independently. ## Repository Management The root `pubspec.yaml` is only intended to lock the development dependencies for repository management. When adding new packages or changing `mono_repo.yaml` or `mono_pkg.yaml` in a package, make sure to run the following commands to update travis configuration. * `pub get` * `pub run mono_repo travis` ## Contributing We love patches and contributions, please refer to [CONTRIBUTING.md][1] for technicalities on [CLA][2] and community guidelines. As this project aims to build _neat_ packages using other _neat_ packages we might also accept proposals for new neat packages, though it's often easier to publish independently. ## License Unless stated otherwise contents in this repository is licensed under Apache License 2.0, see [LICENSE](LICENSE). [1]: CONTRIBUTING.md [2]: https://cla.developers.google.com/	42.810811	128	0.78851	eng_Latn	0.997201
b7f141d288d3f4fb14abc9c7d8de1780181a82ae	1,180	md	Markdown	docs/vs-2015/profiling/no-thread-activity-to-show-threads-view.md	mavasani/visualstudio-docs	4aa6fed75c395bb654dc884441ebb2d9b88bfd30	[ "CC-BY-4.0", "MIT" ]	2	2019-08-19T19:51:53.000Z	2021-03-17T18:30:52.000Z	docs/vs-2015/profiling/no-thread-activity-to-show-threads-view.md	mavasani/visualstudio-docs	4aa6fed75c395bb654dc884441ebb2d9b88bfd30	[ "CC-BY-4.0", "MIT" ]	1	2019-07-18T09:59:10.000Z	2019-07-18T09:59:10.000Z	docs/vs-2015/profiling/no-thread-activity-to-show-threads-view.md	mavasani/visualstudio-docs	4aa6fed75c395bb654dc884441ebb2d9b88bfd30	[ "CC-BY-4.0", "MIT" ]	1	2020-07-11T07:13:18.000Z	2020-07-11T07:13:18.000Z	--- title: "No Thread Activity to Show (Threads View) \| Microsoft Docs" ms.date: 11/15/2016 ms.prod: "visual-studio-dev14" ms.technology: "vs-ide-debug" ms.topic: conceptual f1_keywords: - "vs.cv.threads.nothreadreport" helpviewer_keywords: - "Concurrency Visualizer, No Thread Activity to Show (Threads View)" ms.assetid: aa5ae9d0-561d-4ef8-b36b-258ce553d50a caps.latest.revision: 13 author: MikeJo5000 ms.author: mikejo manager: jillfra --- # No Thread Activity to Show (Threads View) [!INCLUDE[vs2017banner](../includes/vs2017banner.md)] This area shows data about the unhidden threads in the currently visible time range. If no information is visible, check the following settings: - Is the zoom level high? Try zooming out or scrolling to bring more thread activity in range. - Are too many threads hidden? If so, try showing all threads - If Just My Code is selected, you can only view data about your code. Try clearing the setting to ascertain whether there is any system thread activity. - Make sure that Noise Reduction is set to a low threshold. ## See Also [Threads View](../profiling/threads-view-parallel-performance.md)	34.705882	159	0.747458	eng_Latn	0.973492
b7f1923875e6b19d02e8b139efc5d8be6f455552	569	md	Markdown	_feats/bullying-blow.md	tynansdtm/pathminder.github.io	9a0cb763af82c13804def4197e0535ee54453581	[ "OML", "RSA-MD" ]	8	2016-07-24T04:27:04.000Z	2019-10-03T21:31:23.000Z	_feats/bullying-blow.md	tynansdtm/pathminder.github.io	9a0cb763af82c13804def4197e0535ee54453581	[ "OML", "RSA-MD" ]	11	2016-07-11T11:41:13.000Z	2022-02-26T02:55:19.000Z	_feats/bullying-blow.md	tynansdtm/pathminder.github.io	9a0cb763af82c13804def4197e0535ee54453581	[ "OML", "RSA-MD" ]	8	2016-04-03T17:58:13.000Z	2020-08-01T03:01:11.000Z	--- title: Bullying Blow tags: - Combat sources: - Pathfinder Roleplaying Game Advanced Race Guide flavor_text: With a simple hit, you more easily intimidate an opponent. prerequisites: - "[Intimidate](/skills/intimidate/) 1 rank" - "[orc](/races/orcs/)" benefit: \| As a standard action, you may make a melee attack with a --2 penalty on the attack roll. If the attack damages your opponent, you may make an [Intimidate](/skills/intimidate/) check to demoralize that opponent as a free action. normal: \| Intimidating an opponent is a standard action. ---	33.470588	229	0.73638	eng_Latn	0.976325
b7f2e3d3fda979a24bea43586a0f9c384f883d6c	1,588	md	Markdown	changelog.md	igorrosenberg/grails-plugin-uml-class-diagram	b50e4e5a2766ead8b3cf8940c809525f6b19cd47	[ "Apache-2.0" ]	3	2016-06-08T14:30:08.000Z	2019-05-12T02:37:18.000Z	changelog.md	igorrosenberg/grails-plugin-uml-class-diagram	b50e4e5a2766ead8b3cf8940c809525f6b19cd47	[ "Apache-2.0" ]	19	2015-03-25T17:09:38.000Z	2017-03-08T13:45:45.000Z	changelog.md	igorrosenberg/grails-plugin-uml-class-diagram	b50e4e5a2766ead8b3cf8940c809525f6b19cd47	[ "Apache-2.0" ]	4	2017-08-14T14:30:52.000Z	2018-09-23T14:38:57.000Z	# grails-plugin-uml-class-diagram changelog ## Finished tasks * (v0.4.4) Documentation of the plugin - user guides, as exposed by "gh-pages" git branch * (v0.4.0) Refactored for common algorithm: "read model > uml script > image" * (v0.3.4) separate README.md (dev) from src/docs/guide (usage) * (v0.3.4) moved extra info from readme to user guide, see [github gh-pages](http://igorrosenberg.github.io/grails-plugin-uml-class-diagram/) * (v0.3.3) grails docs, see [github gh-pages](http://igorrosenberg.github.io/grails-plugin-uml-class-diagram/) * (v0.3.2) GSP View exposing the Config Command object * (v0.3.1) published as public grails plugin, see http://grails.org/plugin/uml-class-diagram * (v0.3.0) plantUml diagram spec to PNG file (script mode) * (v0.2.6) Config options (renderingEngine) * (v0.2.6) plantUml diagram spec to PNG byteStream, * (v0.2.5) Config options (showGrailsInternals) * (v0.2.4) grails introspect * controllers >> list dependencies * services >> list dependencies * (v0.2.3) Config options (fieldFilterRegexps classFilterRegexps showCanonicalJavaClassNames diagramType) * (v0.2.1) domain >> list dependencies (hasmany) * (v0.2.0) domain >> all fields not external (ie excluding hasmany) * (v0.2.0) domain introspection result to diagram spec * (v0.2.0) Refactor (pass1) script / controller / service (UmlController \| UmlService \| PlantUmlService \|YumlService) ## Future tasks (help needed!) See the ['enhancement' bug reports](https://github.com/igorrosenberg/grails-plugin-uml-class-diagram/issues?q=is%3Aopen+is%3Aissue+label%3Aenhancement)	51.225806	151	0.742443	eng_Latn	0.599372
b7f49f28cb81bffecc3b5c3e8fbc8a818c1e7864	4,663	md	Markdown	doc_source/list_machinelearning.md	cloudreach/iam-user-guide	70f06a830fef0da8eed219f1900b5df9601a7c36	[ "MIT-0" ]	2	2018-08-16T10:59:34.000Z	2018-10-16T10:01:00.000Z	doc_source/list_machinelearning.md	cloudreach/iam-user-guide	70f06a830fef0da8eed219f1900b5df9601a7c36	[ "MIT-0" ]	null	null	null	doc_source/list_machinelearning.md	cloudreach/iam-user-guide	70f06a830fef0da8eed219f1900b5df9601a7c36	[ "MIT-0" ]	1	2018-10-16T10:00:47.000Z	2018-10-16T10:00:47.000Z	# Actions and Condition Context Keys for Amazon Machine Learning<a name="list_machinelearning"></a> Amazon Machine Learning $service prefix: machinelearning$ provides the following service\-specific actions and condition context keys for use in IAM policies\. Actions for Amazon Machine Learning For information about using the following Amazon ML API actions in an IAM policy, see [Permission Model](http://docs.aws.amazon.com/machine-learning/latest/dg/reference.html#controlling-access-to-amazon-ml-resources-by-using-iam) in the Amazon Machine Learning Developer Guide\. + `[machinelearning:CreateMLModel](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_CreateMLModel.html)` + `[machinelearning:Predict](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_Predict.html)` + `[machinelearning:DeleteRealtimeEndpoint](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_DeleteRealtimeEndpoint.html)` + `[machinelearning:GetDataSource](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_GetDataSource.html)` + `[machinelearning:CreateEvaluation](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_CreateEvaluation.html)` + `[machinelearning:DeleteMLModel](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_DeleteMLModel.html)` + `[machinelearning:UpdateBatchPrediction](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_UpdateBatchPrediction.html)` + `[machinelearning:CreateBatchPrediction](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_CreateBatchPrediction.html)` + `[machinelearning:CreateDataSourceFromRedshift](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_CreateDataSourceFromRedshift.html)` + `[machinelearning:DescribeDataSources](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_DescribeDataSources.html)` + `[machinelearning:DeleteBatchPrediction](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_DeleteBatchPrediction.html)` + `[machinelearning:GetMLModel](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_GetMLModel.html)` + `[machinelearning:GetEvaluation](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_GetEvaluation.html)` + `[machinelearning:DescribeBatchPredictions](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_DescribeBatchPredictions.html)` + `[machinelearning:UpdateMLModel](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_UpdateMLModel.html)` + `[machinelearning:DescribeTags](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_DescribeTags.html)` + `[machinelearning:GetBatchPrediction](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_GetBatchPrediction.html)` + `[machinelearning:CreateDataSourceFromS3](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_CreateDataSourceFromS3.html)` + `[machinelearning:DeleteDataSource](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_DeleteDataSource.html)` + `[machinelearning:UpdateEvaluation](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_UpdateEvaluation.html)` + `[machinelearning:CreateRealtimeEndpoint](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_CreateRealtimeEndpoint.html)` + `[machinelearning:DeleteEvaluation](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_DeleteEvaluation.html)` + `[machinelearning:CreateDataSourceFromRDS](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_CreateDataSourceFromRDS.html)` + `[machinelearning:DescribeMLModels](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_DescribeMLModels.html)` + `[machinelearning:UpdateDataSource](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_UpdateDataSource.html)` + `[machinelearning:AddTags](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_AddTags.html)` + `[machinelearning:DeleteTags](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_DeleteTags.html)` + `[machinelearning:DescribeEvaluations](http://docs.aws.amazon.com/machine-learning/latest/APIReference/API_DescribeEvaluations.html)` Condition context keys for Amazon Machine Learning Amazon Machine Learning has no service\-specific context keys that can be used in an IAM policy\. For the list of the global condition context keys that are available to all services, see [Available Global Condition Keys](reference_policies_condition-keys.md#AvailableKeys) in the IAM Policy Elements Reference\.	69.597015	314	0.822217	yue_Hant	0.956485
b7f4d39237b37d9b245c1412296453f754b41a74	947	md	Markdown	README.md	mckadv/product-management	55b48f8e3284fdae30be79f775c0223593e48e2d	[ "MIT" ]	null	null	null	README.md	mckadv/product-management	55b48f8e3284fdae30be79f775c0223593e48e2d	[ "MIT" ]	null	null	null	README.md	mckadv/product-management	55b48f8e3284fdae30be79f775c0223593e48e2d	[ "MIT" ]	null	null	null	# product-management Este proyecto esta basado en framework CodeIgniter 3.1.11, Bootstrap 3.x, PHP y MySQL, permite la creación, edición y eliminación de productos así como listar todos los productos registrados en el sistema. ### Instalación Primero debe descargar e instalar el framework codeigniter 3.1.11 desde su página oficial. Luego desde su phpMyadmin cree una base de datos de nombre "CoffeShop" y siga las instrucciones en el archivo readme.txt ubicado en la carpeta SQL. Genere las estructura de su base de datos con el archivo anterior. Actualice su archivo "autoload.php" con el que le proporcionamos en application/config. Actualice "routes.php" con el que le proporcionamos en application/config. Suba los archivos ubicados en las carpetas application/controllers, application/models y application/views a sus respectivas ubicaciones en su instalación primaria de CodeIgniter. Eso es todo (Advertencia: Aún en fase de desarrollo).	86.090909	205	0.81415	spa_Latn	0.998219
b7f51aca7bec6ecac22bae80eecab39cff683d56	5,413	md	Markdown	aspnetcore/grpc/basics.md	alper-yoruk/AspNetCore.Docs.tr-tr	e137583f957428bf6fba0c285c0b231c14857a9f	[ "CC-BY-4.0", "MIT" ]	null	null	null	aspnetcore/grpc/basics.md	alper-yoruk/AspNetCore.Docs.tr-tr	e137583f957428bf6fba0c285c0b231c14857a9f	[ "CC-BY-4.0", "MIT" ]	null	null	null	aspnetcore/grpc/basics.md	alper-yoruk/AspNetCore.Docs.tr-tr	e137583f957428bf6fba0c285c0b231c14857a9f	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- title: C# içeren gRPC hizmetleri author: juntaoluo description: C# ile gRPC hizmetlerini yazarken temel kavramları öğrenin. monikerRange: '>= aspnetcore-3.0' ms.author: johluo ms.date: 07/09/2020 no-loc: - appsettings.json - ASP.NET Core Identity - cookie - Cookie - Blazor - Blazor Server - Blazor WebAssembly - Identity - Let's Encrypt - Razor - SignalR uid: grpc/basics ms.openlocfilehash: 4968ac889cd3b4e0780ce73dc729d0107a416932 ms.sourcegitcommit: 3593c4efa707edeaaceffbfa544f99f41fc62535 ms.translationtype: MT ms.contentlocale: tr-TR ms.lasthandoff: 01/04/2021 ms.locfileid: "93061021" --- # <a name="grpc-services-with-c"></a>C ile gRPC Hizmetleri\# Bu belgede, C# dilinde [GRPC](https://grpc.io/docs/guides/) uygulamaları yazmak için gereken kavramlar özetlenmektedir. Burada ele alınan konular hem [C Core](https://grpc.io/blog/grpc-stacks)tabanlı hem de ASP.NET Core tabanlı GRPC uygulamaları için geçerlidir. [!INCLUDE[](~/includes/gRPCazure.md)] ## <a name="proto-file"></a>Proto dosyası gRPC, API geliştirmesi için bir sözleşmenin ilk yaklaşımını kullanır. Protokol arabellekleri (protoarabellek) varsayılan olarak arabirim tanım dili (IDL) olarak kullanılır. \ . Proto* dosyası şunları içerir: * GRPC hizmetinin tanımı. * İstemciler ve sunucular arasında gönderilen iletiler. Prototipsiz dosyaların sözdizimi hakkında daha fazla bilgi için bkz <xref:grpc/protobuf> .. Örneğin, [gRPC hizmetini kullanmaya başlama](xref:tutorials/grpc/grpc-start)bölümünde kullanılan Greet. proto dosyasını düşünün: * Bir `Greeter` hizmeti tanımlar. * `Greeter`Hizmet bir çağrıyı tanımlar `SayHello` . * `SayHello` bir `HelloRequest` ileti gönderir ve bir `HelloReply` ileti alır: [!code-protobuf[](~/tutorials/grpc/grpc-start/sample/GrpcGreeter/Protos/greet.proto)] [!INCLUDE[about the series](~/includes/code-comments-loc.md)] ## <a name="add-a-proto-file-to-a-c-app"></a>C uygulamasına bir. proto dosyası ekleyin \# \ . Proto* dosyası bir projeye öğe grubuna eklenerek dahil edilir `<Protobuf>` : [!code-xml[](~/tutorials/grpc/grpc-start/sample/GrpcGreeter/GrpcGreeter.csproj?highlight=2&range=7-9)] Varsayılan olarak, `<Protobuf>` başvuru somut bir istemci ve hizmet temel sınıfı oluşturur. Başvuru öğesinin özniteliği, `GrpcServices` C# varlık oluşturmayı sınırlamak için kullanılabilir. Geçerli `GrpcServices` Seçenekler şunlardır: * `Both` (mevcut olmadığında varsayılan) * `Server` * `Client` * `None` ## <a name="c-tooling-support-for-proto-files"></a>. Proto dosyaları için C# araçları desteği Araçları Paketi [GRPC. Tools](https://www.nuget.org/packages/Grpc.Tools/) , \ . proto* dosyalarından C# varlıkları oluşturmak için gereklidir. Oluşturulan varlıklar (dosyalar): * , Projenin oluşturulduğu her seferinde gerekli olarak oluşturulur. * Projeye eklenmez veya kaynak denetimine iade edilmedi. * Obj dizininde bulunan bir yapı yapıtı. Bu paket hem sunucu hem de istemci projeleri için gereklidir. `Grpc.AspNetCore`Metapackage öğesine bir başvuru içerir `Grpc.Tools` . Sunucu projeleri `Grpc.AspNetCore` , Visual Studio 'Da Paket Yöneticisi 'ni kullanarak veya bir proje dosyasına bir ekleyerek ekleyebilir `<PackageReference>` : [!code-xml[](~/tutorials/grpc/grpc-start/sample/GrpcGreeter/GrpcGreeter.csproj?highlight=1&range=12)] İstemci projeleri `Grpc.Tools` , gRPC istemcisini kullanmak için gereken diğer paketlerle birlikte doğrudan başvurmalıdır. Çalışma zamanında araç paketi gerekli değildir, bu nedenle bağımlılık şu şekilde işaretlenir `PrivateAssets="All"` : [!code-xml[](~/tutorials/grpc/grpc-start/sample/GrpcGreeterClient/GrpcGreeterClient.csproj?highlight=3&range=9-11)] ## <a name="generated-c-assets"></a>Oluşturulan C# varlıkları Araç paketi, eklenen \ . proto* dosyalarında tanımlanan Iletileri temsil eden C# türlerini üretir. Sunucu tarafı varlıklar için, soyut bir hizmet temel türü oluşturulur. Temel tür, . proto dosyasında bulunan tüm GRPC çağrılarının tanımlarını içerir. Bu temel türden türetilen somut bir hizmet uygulamasını oluşturun ve gRPC çağrılarının mantığını uygular. `greet.proto`Daha önce açıklanan örnek için, `GreeterBase` sanal bir yöntemi içeren bir soyut tür `SayHello` oluşturulur. Somut bir uygulama `GreeterService` , yöntemini geçersiz kılar ve gRPC çağrısını işleme mantığını uygular. [!code-csharp[](~/tutorials/grpc/grpc-start/sample/GrpcGreeter/Services/GreeterService.cs?name=snippet)] İstemci tarafı varlıklar için somut bir istemci türü oluşturulur. . Proto dosyasındaki GRPC çağrıları, çağrılabilecek somut türdeki yöntemlere çevrilir. `greet.proto`Daha önce açıklanan örnek için somut bir `GreeterClient` tür oluşturulur. `GreeterClient.SayHelloAsync`Sunucuya bir gRPC çağrısı başlatmak için çağrısı yapın. [!code-csharp[](~/tutorials/grpc/grpc-start/sample/GrpcGreeterClient/Program.cs?name=snippet)] Varsayılan olarak, sunucu ve istemci varlıkları öğe grubuna dahil edilen her \ . proto* dosyası için oluşturulur `<Protobuf>` . Sunucu projesinde yalnızca sunucu varlıklarının oluşturulmasını sağlamak için `GrpcServices` özniteliği olarak ayarlanır `Server` . [!code-xml[](~/tutorials/grpc/grpc-start/sample/GrpcGreeter/GrpcGreeter.csproj?highlight=2&range=7-9)] Benzer şekilde, özniteliği `Client` istemci projelerinde olarak ayarlanır. ## <a name="additional-resources"></a>Ek kaynaklar * <xref:grpc/index> * <xref:tutorials/grpc/grpc-start> * <xref:grpc/aspnetcore> * <xref:grpc/client>	51.552381	487	0.785701	tur_Latn	0.999046
b7f5c1c7abcda6faf9c324d9f9622d2948f1e708	3,862	md	Markdown	_pages/faq.md	g205dns/sdg-indicators	4ca938e1b978ff48f76de10abd311f34adcaeb57	[ "MIT" ]	null	null	null	_pages/faq.md	g205dns/sdg-indicators	4ca938e1b978ff48f76de10abd311f34adcaeb57	[ "MIT" ]	null	null	null	_pages/faq.md	g205dns/sdg-indicators	4ca938e1b978ff48f76de10abd311f34adcaeb57	[ "MIT" ]	null	null	null	--- title: Frequently Asked Questions (FAQ) permalink: /faq/ layout: page --- ## How do I suggest new or different data sources? If you have feedback on the data sources we have used or have suggestions for new data sources then please email us at <a href="mailto:{{site.email_contacts.questions}}">{{site.email_contacts.questions}}</a>. ## What does the reporting status mean? We have used three different types of reporting status for an indicator, which are also colour coded: * Reported online (green) – as a minimum the headline national data for this indicator is available on this website but the data might not be fully disaggregated yet. We are continuing to source additional disaggregations. * Statistics in progress (amber) – we have found a suitable source of data for this indicator or relevant proxy at national level. We are currently quality assuring the data and preparing it for publication. * Exploring data sources (red) – we are still looking for a suitable data source for this indicator. Where there is additional information about the status of indicator data collection and reporting, this will be displayed at the top of the indicator page. ## How often will new data be added to this site? We will add data as soon as it has been sourced and checked. This includes new data as well as updates to data we have already published. We will continue to collect data from existing sources where possible, in cooperation with topic experts. ## What are you doing to fill data gaps? For some indicators, although we may have data at the national level, our existing data sources don’t always allow us to disaggregate by all main groups. This means we need to look for new data sources, link existing ones, or model data. We are working with colleagues across the Government Statistical Service to do this, including the Data Science Campus. We have recently published our response to the [consultation on measuring and reporting SDGs in the UK](https://consultations.ons.gov.uk/sustainable-development-goals/ons-approach-to-measuring-reporting-sdgs-in-the-uk/) where we asked for your ideas on prioritising data development. Your feedback will inform our data development plans, which will be published here in 2018. ## How accessible is this website? Our aim is to make this website as accessible and usable as possible for every user. We are working towards meeting AA level of the [Web Content Accessibility Guidelines (WCAG 2.0)](https://www.gov.uk/service-manual/helping-people-to-use-your-service/understanding-wcag-20). We have recently undertaken an accessibility audit by the [Digital Accessibility Centre](http://digitalaccessibilitycentre.org/) and are using the recommendations from this review to help us improve our website. ## What browsers can I use to view this website? We are developing and testing our site in line with the Government Digital Service (GDS) [guidance on designing for different browsers and devices](https://www.gov.uk/service-manual/technology/designing-for-different-browsers-and-devices). Our website works with most of the latest versions of the commonly used browsers listed in the ‘Browsers to test in’ section of the GDS guidance. There are some issues with using the site on older versions of browsers eg IE8 and we are working to fix these. ## Can other countries copy this website? Yes. We have deliberately developed an open source solution for reporting UK SDGs data so other countries can freely reuse our code. Technical guidance on copying our site is available in our [wiki](https://github.com/ONSdigital/sdg-indicators/wiki). Countries exploring how to report their own SDGs national data can also get support from the [Center for Open Data Enterprise (CODE)](http://www.opendataenterprise.org/) through their [SDG National Reporting Initiative](https://www.sdgreporting.org/).	104.378378	502	0.796479	eng_Latn	0.998519
b7f6b964a7f9cff3306817a159d0d5cad03257dd	81	md	Markdown	README.md	Dae12-Han/dae12-han.github.io	45850d2c84db8d90ad77726dbbe175e49b9a0664	[ "Apache-2.0", "BSD-3-Clause" ]	null	null	null	README.md	Dae12-Han/dae12-han.github.io	45850d2c84db8d90ad77726dbbe175e49b9a0664	[ "Apache-2.0", "BSD-3-Clause" ]	null	null	null	README.md	Dae12-Han/dae12-han.github.io	45850d2c84db8d90ad77726dbbe175e49b9a0664	[ "Apache-2.0", "BSD-3-Clause" ]	null	null	null	# Dae12-Han.github.io https://idratherbewriting.com/documentation-theme-jekyll/	20.25	57	0.802469	kor_Hang	0.268172
b7f6b967ddccb16ce490c28e0b2b3151d1f8e564	3,122	md	Markdown	docs/framework/winforms/controls/how-to-associate-a-contextmenustrip-with-a-control.md	Ming77/docs.zh-cn	dd4fb6e9f79320627d19c760922cb66f60162607	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/framework/winforms/controls/how-to-associate-a-contextmenustrip-with-a-control.md	Ming77/docs.zh-cn	dd4fb6e9f79320627d19c760922cb66f60162607	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/framework/winforms/controls/how-to-associate-a-contextmenustrip-with-a-control.md	Ming77/docs.zh-cn	dd4fb6e9f79320627d19c760922cb66f60162607	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- title: "如何：将 ContextMenuStrip 与控件关联" ms.custom: ms.date: 03/30/2017 ms.prod: .net-framework ms.reviewer: ms.suite: ms.technology: dotnet-winforms ms.tgt_pltfrm: ms.topic: article dev_langs: - csharp - vb helpviewer_keywords: - context menus [Windows Forms], relating - ContextMenuStrips [Windows Forms], associating with controls - context menus [Windows Forms], associating with controls - ContextMenuStrips [Windows Forms], relating ms.assetid: 6fc40a42-5d69-427f-aa30-0a146193226b caps.latest.revision: "11" author: dotnet-bot ms.author: dotnetcontent manager: wpickett ms.workload: dotnet ms.openlocfilehash: 7307af535dce39443b623e1fee4491dd48ffbd94 ms.sourcegitcommit: 16186c34a957fdd52e5db7294f291f7530ac9d24 ms.translationtype: MT ms.contentlocale: zh-CN ms.lasthandoff: 12/22/2017 --- # <a name="how-to-associate-a-contextmenustrip-with-a-control"></a>如何：将 ContextMenuStrip 与控件关联创建控件和快捷菜单后，使用以下过程在用户右键单击控件时显示给定的快捷菜单。这些过程将 <xref:System.Windows.Forms.ContextMenuStrip> 与 Windows 窗体和 <xref:System.Windows.Forms.ToolStrip> 控件相关联。 ### <a name="to-associate-a-contextmenustrip-with-a-windows-form"></a>将 ContextMenuStrip 与 Windows 窗体关联 1. 将 <xref:System.Windows.Forms.Control.ContextMenuStrip%2A> 属性设置为关联的 <xref:System.Windows.Forms.ContextMenuStrip> 的名称。 ### <a name="to-associate-a-contextmenustrip-with-a-toolstrip-control"></a>将 ContextMenuStrip 与 ToolStrip 控件关联 1. 将控件的 <xref:System.Windows.Forms.Control.ContextMenuStrip%2A> 属性设置为关联的 <xref:System.Windows.Forms.ContextMenuStrip> 的名称。 ## <a name="example"></a>示例下面的代码示例创建了 Windows 窗体和 <xref:System.Windows.Forms.ToolStrip>，并将不同的 <xref:System.Windows.Forms.ContextMenuStrip> 与其中每个控件关联。 [!code-csharp[System.Windows.Forms.ContextMenuStrip#1](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.ContextMenuStrip/CS/form1.cs#1)] [!code-vb[System.Windows.Forms.ContextMenuStrip#1](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/System.Windows.Forms.ContextMenuStrip/VB/form1.vb#1)] ## <a name="compiling-the-code"></a>编译代码此示例需要： - 对 System、System.Data、System.Drawing 和 System.Windows.Forms 程序集的引用。有关从 [!INCLUDE[vbprvb](../../../../includes/vbprvb-md.md)] 或 [!INCLUDE[csprcs](../../../../includes/csprcs-md.md)] 的命令行生成此示例的信息，请参阅[从命令行生成](~/docs/visual-basic/reference/command-line-compiler/building-from-the-command-line.md)或[在命令行上使用 csc.exe 生成](~/docs/csharp/language-reference/compiler-options/command-line-building-with-csc-exe.md)。还可以通过将代码粘贴到新项目，在 [!INCLUDE[vsprvs](../../../../includes/vsprvs-md.md)] 中生成此示例。另请参阅 [如何：使用 Visual Studio 编译和运行完整的 Windows 窗体代码示例](http://msdn.microsoft.com/library/Bb129228$v=vs.110$)。 ## <a name="see-also"></a>请参阅 <xref:System.Windows.Forms.ContextMenuStrip> <xref:System.Windows.Forms.Control.ContextMenuStrip%2A> <xref:System.Windows.Forms.ToolStrip> [如何：向 ContextMenuStrip 添加菜单项](../../../../docs/framework/winforms/controls/how-to-add-menu-items-to-a-contextmenustrip.md) [ContextMenuStrip 控件](../../../../docs/framework/winforms/controls/contextmenustrip-control.md)	51.180328	527	0.751441	yue_Hant	0.831903
b7f7357c65e47c231486c0b8a37f58281a095b2b	9,757	md	Markdown	_docs/research/larvabot-dev.md	jtebert/document-everything	b98a310264cc72c844832da7adcaeac134b1df2d	[ "MIT" ]	2	2020-02-02T14:59:19.000Z	2021-01-04T17:25:30.000Z	_docs/research/larvabot-dev.md	jtebert/document-everything	b98a310264cc72c844832da7adcaeac134b1df2d	[ "MIT" ]	8	2019-11-21T21:26:14.000Z	2021-09-14T22:22:18.000Z	_docs/research/larvabot-dev.md	jtebert/document-everything	b98a310264cc72c844832da7adcaeac134b1df2d	[ "MIT" ]	3	2021-06-13T12:51:37.000Z	2021-10-04T05:52:33.000Z	--- title: LARVAbot Development parent: Research last_modified_date: 2020-01-09 --- 1. TOC {:toc} --- ## Christmas Redesign This starts with development as of December 2019. The current version of the LARVAbot (PCB version 2.2, git commit [14f8468](https://github.com/jtebert/larvabot/commit/14f8468450e2ec294b87def1cffc1aaf779bde6e)) is based around a couple of main principles that I want to change/update: ### Change microcontroller from ATmega 328p to 32u4 There are many reasons for this. The thought of changing was first prompted by running out of interrupts when I put on the motor encoders. The quadrature encoders require 2 interrupt pins each, plus I need one for I2C communication. The 328p only has 2 interrupt pins. The 32u4 has 5 external interrupt pins (or 4, since 1 seems to be synchronous?). This microcontroller is also what's running the Arduino Micro (and Leonardo), so if I set it up right, I can use it "natively" with the Arduino IDE (no need to install something from someone's GitHub repo to use the microcontroller). The Micro can also provide me with a template of what parts and connections I need to configure my own PCB to work this way, since it's all open source. Because it has native USB, I can also ditch the external programmer without needing a lot of extra stuff on the board to make that work (the way the Arduino Uno works). As a bonus, this would also simplify serial debugging with Arduino (instead of my current hacky approach of having a pair of TX/RX pins for an FTDI cable, which doesn't interface with the Arduino IDE.) The limitation of this is that I would have to do a lot of redesign for this, both for the PCB and also the code. In addition, since the 32u4 has more pins than the 328p, even its large package looks way too small to solder by hand with a soldering iron. But Clark thinks that it's possible to do with reflow soldering on a hot plate or oven. And we have that in our lab! So it's a great excuse to learn to do that. ### Changing IR communication to digital Currently I'm using IR phototransistors to detect whether there's a robot above it. This just uses the analog intensity, which means it's heavily dependent on background IR, and difficult to communicate a digital message (as I discovered in HTMAA). But as I learned in Physics 223, there are [IR receivers](https://www.adafruit.com/product/157) that process high frequency IR signals (like are sent by remote controls) and output a digital signal. ([And there are some easy-to-follow tutorials for it in Arduino.](https://learn.sparkfun.com/tutorials/ir-communication/all)) ### Switching from 5 V to 3.3 V power Currently, everything is powered by a 2-cell LiPo battery (7.4 V), which is used directly for the motors, down-regulated to 5 V for most of the circuitry, and 3.3 V for the IMU. Using 5 V means I need this 2-cell battery or an up-regulating voltage regulator. But it turns out I can probably easily switch almost everything to 3.3 V, which would have a bunch of advantages. First, is it possible? All of the active components need to be able to function on 3.3 V, namely the motor driver, IR LIDAR, IMU, and [motor encoders](https://www.pololu.com/product/4761). According to their datasheets, we're in good shape! Switching to 3.3 V means I can use a single-cell 3.7 V LiPo battery, which makes charging significantly easier because there's no need to worry about load balancing. Which means I can pull off charging it through the same USB I use for programming the board. (Yay, standardization!) Also, (with the exception of the motors), that theoretically means a 1/3 reduction in power consumption. There are trade offs to this change, though. First is the motor power: 3.3 V is probably not enough to power the 6 V motors at the speed/torque that I want. But it's definitely possible to get a switching voltage regulator (probably on a breakout board) to power just that. Lowering the voltage also lowers the maximum possible clock speed. Instead of my current 20 MHz at 5V, I'd probably have to drop to 12 or 8 MHz. ### What now? So what are the steps to do this? I can go down another PCB redesign rabbit hole, but it's tricky without a post doc electrical engineer to consult on component choice. On the other hand, how much time does it make sense to spend on code when I'm about to change a bunch of things? (To be fair, a lot of the changes will probably just be pin numbers; the biggest change will be interrupts for the encoders yet, which I haven't done anything for yet, anyway.) Also, there are definitely things I haven't even tested on the current version of the board (like the motor drivers), so I should probably make sure that works before continuing on with my design... There are a couple of relevant parts I'll need to add/change: - Charging circuit: I can steal from this [SparkFun LiPo charger design](https://www.sparkfun.com/products/10217), which is dead simple for charging a single-cell LiPo. Since it's open source, they even provide the Eagle files for it, and all of the parts (like the [charging IC](https://www.digikey.com/product-detail/en/microchip-technology/MCP73831T-2ATI-OT/MCP73831T-2ATI-OTCT-ND/1979803)) are available on DigiKey. The circuit design looks very simple, at least. Plus, I can then ditch this other charging port and not have to open up the robot whenever I want to reprogram it. - Battery: Time to swtich to single-cell. No idea how much capacity I need. My current 1200 mAh battery is probably excessive, though. I could also take this opportunity to pick a battery with a connector that I won't accidentally plug in backwards. (Which means I also need to find board-mountable female connectors for them.) [These 800 mAh batteries on Amazon look not completely sketchy.](https://smile.amazon.com/dp/B01N74TTW6/). - Step-up voltage convertor: In the event that I need 5 V (which I'm realizing I might for the MCU if I want to be able to use it like an Arduino Micro), I will need a step-up convertor from 3.7 V to 5 V. Sparkfun [used to make one of these](https://www.sparkfun.com/products/retired/109680), but it's now retired because the 5V version of the part is not available anymore. Pololu makes a [different 5V convertor with a newer part](https://www.pololu.com/product/2564). It looks to be made of simple parts, but the chip it uses only comes in a [package no human can solder](https://www.digikey.com/products/en/integrated-circuits-ics/pmic-voltage-regulators-dc-dc-switching-regulators/739?k=TPS+6120&k=&pkeyword=TPS+6120&sv=0&sf=0&FV=-8%7C739%2C1779%7C249171&quantity=1&ColumnSort=0&page=1&pageSize=25). - 32u4 microcontroller: [It's on Digikey](https://www.digikey.com/product-detail/en/microchip-technology/ATMEGA32U4-AU/ATMEGA32U4-AU-ND/1914602). The 44-TQFP has pins sticking out, which means it's at least conceivable to solder it by hand. The other version of this (ATMEGA32U4RC-AU-ND) has an internal resistor/capacitor clock, which isn't super precise. The non-RC version means I need to add an external clock, but I'm already doing that, and I'll get a more precise clock. The Arduino website also has [all of the files for the Arduino Micro](https://www.arduino.cc/en/pmwiki.php?n=Main/arduinoBoardMicro) (all hail open source hardware), which means I can pick that apart to figure out what I need to make this thing function like an Arduino, and ditch the parts I don't need. (Again, it would be really nice to have an electrical engineer on hand to help with this.) Because I'm planning to power it 3.3 V with an 8MHz (or at least less than 16 MHz), I probably won't be able to directly use the Micro board within the Arduino IDE. But people have written [instructions on how to create your own custom board](https://www.hackster.io/wallarug/arduino-ide-creating-custom-boards-89f7a6). - Updated motor encoders: Pololu has come out with a new varient for their [motor encoders](https://www.pololu.com/product/4761), which now feature JST plugs for attachment. Does this mean I can avoid having to solder as many tiny ribbon cable wires?? I do still have to figure out how to get wires with the relevant male ends for this, but I'm optimistic about less tiny sad soldering. (It looks like [Pololu even sells some](https://www.pololu.com/product/4762).) - IR receiver: There are [through-hole ones on Sparkfun](https://www.sparkfun.com/products/10266), but I want to be able to stick these on top of the robots, so I'll probably go with surface mount if possible. The [TSOP6238TT](https://www.digikey.com/product-detail/en/vishay-semiconductor-opto-division/TSOP6238TT/TSOP6238TTCT-ND/3516290) on Digikey looks promising, with an excessive 45 m range and +/- 50 degree viewing angle. But I'm not certain whether the package it comes in is something I could solder. The [datasheet](http://www.vishay.com/docs/82463/tsop62.pdf) gives instructions for manual soldering, but I don't know if that's a standard thing, or perhaps just that it's technically possible to solder it by hand. ## 2020 January On my battery connector conundrum, SparkFun might simplify things again with its internal consistency. They have a [right angle JST connector](https://www.sparkfun.com/products/8612) (and [corresponding DigiKey part](https://www.digikey.com/product-detail/en/jst-sales-america-inc/S2B-PH-SM4-TB-LF-SN/455-1749-6-ND/1059119) for slightly cheaper), and it's compatible with all of their [LiPo batteries, like this 850 mAh one](https://www.sparkfun.com/products/13854). (And I'd also trust these batteries more than the similar ones on Amazon with few and poor reviews.) And while I'm at it, I could also get [ribbon cable that doesn't suck](https://www.sparkfun.com/products/10647).	171.175439	1,201	0.775751	eng_Latn	0.997468
b7f75c49316c16ff48ae8c26700659b828bd26c5	5,054	md	Markdown	content/ru/user-manual/assets/materials.md	zyfdoudou/developer.playcanvas.com	6c1cfd603f4b1b6fc720be6b841c02f22c635703	[ "MIT" ]	57	2015-02-25T18:13:18.000Z	2021-12-16T01:45:32.000Z	content/ru/user-manual/assets/materials.md	kinvix/developer.playcanvas.com	679ac644e63140cc6251695fa057d56f283cf4ba	[ "MIT" ]	185	2015-05-23T09:37:21.000Z	2022-03-29T23:08:42.000Z	content/ru/user-manual/assets/materials.md	kinvix/developer.playcanvas.com	679ac644e63140cc6251695fa057d56f283cf4ba	[ "MIT" ]	43	2015-03-17T08:44:27.000Z	2022-03-26T07:08:57.000Z	--- title: Materials template: usermanual-page.tmpl.html position: 6 --- Every surface on a 3D model is rendered using a material. The material defines the properties of that surface, such as its color, shininess, bumpiness. In PlayCanvas, a material is an Asset type which collects all these properties together. By default, it represents a Physical material. This exposes the fundamental properties that can be used to create many different types for visual effects, from smooth plastic, to rough wood, or scratched metal. We also support our old Phong Material type. ## Importing Materials Materials are imported automatically when you upload a 3D model (e.g. FBX or COLLADA) file into PlayCanvas. Materials will be generated with the same properties as they exist in your 3D modelling tool. If you upload using embedded media (FBX only) all the relevant texture maps will be automatically set up for you. ## Creating New Materials You can create new materials directly from the PlayCanvas Editor interface. <img src="/images/user-manual/create-asset-menu.jpg" style="width: 300px;" /> This creates a new material Asset and opens up the material inspector on the right-hand side of the screen. ## Selecting a Material <img src="/images/user-manual/model-inspector-simple.jpg" style="width: 300px; float:right; padding: 20px; padding-top: 0px;" /> In order to edit a material, first you must select it. This will bring up the material inspector. You can select a material in the asset panel. You can also select materials from the model inspector or from the model component. Generally, clicking on a material preview icon will take you to the material inspector. ## Assigning Materials <img src="/images/user-manual/material_overrides/model.png" style="width: 300px; float: right; padding: 20px; padding-top: 0px;" /> You can modify which materials are assigned to where on a model asset or you can customize the materials of a particular Entity that has a model component. When you select an Entity with a model component you will see two buttons - Asset Materials and Entity Materials. <br style="clear:both;" /> <img src="/images/user-manual/model-inspector-free-slot.jpg" style="width: 300px; float: right; padding: 20px; padding-top: 0px;" /> Clicking on Asset Materials will select the model asset. You can also select the model asset from the asset panel. The model inspector will show the meshes of model and which material is assigned to each. You can clear a material using the X button, and click the empty slot to assign a new material. You can also drag and drop material Assets from the asset panel onto the material slot. <br style="clear:both;" /> Clicking on Entity Materials will first ask you to select the mesh instance for which you want to customize the material: <img src="/images/user-manual/material_overrides/select.png" style="max-width: 100%" /> After selecting the mesh instance a new material picker will appear in the model component: <img src="/images/user-manual/material_overrides/selected.png" style="max-width: 100%" /> Then you can select a different material for this particular Entity: <img src="/images/user-manual/material_overrides/overriden.png" style="max-width: 100%" /> <br style="clear:both;" /> ## Editing a Material <img src="/images/user-manual/material-inspector.jpg" style="width: 300px; float: right; padding: 20px; padding-top: 0px;" /> Once you have a material selected you can edit its properties. The Editor supports to types of material 'Shading Model', this is defined in a drop-down at the top of the material inspector. ### Physical The physical shading model is our most advanced shading model. This is the model for PlayCanvas's Physically Based Renderer (PBR). [Physical Material Properties][1] ### Phong The phong shading model is our legacy shading model. Use this for compatibility reasons. [Phong Material Properties][2] ## Material Maps <img src="/images/user-manual/material-map-slot.jpg" style="width: 300px; float: right; padding: 20px; padding-top: 0px;" /> Much of editing a material involves creating and assigning textures maps to the various slots detailed on the pages above. There are a few options that are available on most texture map slots for a material. ### Texture Asset First is the texture asset, upload an image to PlayCanvas and we'll create a texture asset for you. you can assign this to a slot on a material. ### Color or Tint Color Some map slots can be a flat color instead of a texture map. Some slots also support a tint color if a texture is also assigned. If enabled the tint color is multiplied by the color in the texture map slot. ### Channel Some maps only require a single grayscale value e.g. 0.0 -> 1.0. In this case it is possible to select which channel of the texture to use. RGB means that all three channels are used. R, G or B means that only the red, green or blue channel will be used. [1]: /user-manual/assets/physical-material [2]: /user-manual/assets/phong-material	45.945455	315	0.767907	eng_Latn	0.997225
b7f7c4abbbf00fffde69093217f5a3e84ec837f5	4,684	md	Markdown	pages/1.8/usage/cli/index.md	rukletsov/dcos-docs-site	970515625fcd2fc71c370e19647acf5b61a84fae	[ "Apache-2.0" ]	1	2019-04-12T10:30:56.000Z	2019-04-12T10:30:56.000Z	pages/1.8/usage/cli/index.md	rukletsov/dcos-docs-site	970515625fcd2fc71c370e19647acf5b61a84fae	[ "Apache-2.0" ]	null	null	null	pages/1.8/usage/cli/index.md	rukletsov/dcos-docs-site	970515625fcd2fc71c370e19647acf5b61a84fae	[ "Apache-2.0" ]	null	null	null	--- layout: layout.pug navigationTitle: CLI title: CLI menuWeight: 10 excerpt: enterprise: false --- <!-- This source repo for this topic is https://github.com/dcos/dcos-docs --> You can use the DC/OS command-line interface (CLI) to manage your cluster nodes, install DC/OS packages, inspect the cluster state, and administer the DC/OS service subcommands. You can quickly [install](/1.8/usage/cli/install) the CLI from the DC/OS web interface. DC/OS 1.8 requires the DC/OS CLI 0.4.x. To list available commands, either run `dcos` with no parameters or run `dcos help`: ```bash Command line utility for the Mesosphere Datacenter Operating System (DC/OS). The Mesosphere DC/OS is a distributed operating system built around Apache Mesos. This utility provides tools for easy management of a DC/OS installation. Available DC/OS commands: auth Authenticate to DC/OS cluster config Manage the DC/OS configuration file experimental Experimental commands. These commands are under development and are subject to change help Display help information about DC/OS job Deploy and manage jobs in DC/OS marathon Deploy and manage applications to DC/OS node Administer and manage DC/OS cluster nodes package Install and manage DC/OS software packages service Manage DC/OS services task Manage DC/OS tasks Get detailed command description with 'dcos <command> --help'. ``` # Environment Variables These environment variables are supported by the DC/OS CLI and can be set dynamically. #### DCOS_CONFIG Specifies the path to the DC/OS configuration file. By default, this variable is set to `DCOS_CONFIG=/<home-directory>/.dcos/dcos.toml`. For example, if you moved your DC/OS configuration file to `/home/jdoe/config/` you can specify this command: ```bash export DCOS_CONFIG=/home/jdoe/config/dcos.toml ``` #### DCOS_SSL_VERIFY Indicates whether to verify SSL certificates or set the path to the SSL certificates. You must set this variable manually. Setting this environment variable is equivalent to setting the `dcos config set core.ssl_verify` option in the DC/OS configuration [file](#configuration-files). For example, to indicate that you want to set the path to SSL certificates: ```bash export DCOS_SSL_VERIFY=false ``` #### DCOS_LOG_LEVEL Prints log messages to stderr at or above the level indicated. This is equivalent to the `--log-level` command-line option. The severity levels are: * debug Prints all messages to stderr, including informational, warning, error, and critical. * info Prints informational, warning, error, and critical messages to stderr. * warning Prints warning, error, and critical messages to stderr. * error Prints error and critical messages to stderr. * critical Prints only critical messages to stderr. For example, to set the log level to warning: ```bash export DCOS_LOG_LEVEL=warning ``` #### DCOS_DEBUG Indicates whether to print additional debug messages to `stdout`. By default this is set to `false`. For example: ```bash export DCOS_DEBUG=true ``` # <a name="configuration-files"></a>Configuration Files By default, the DC/OS CLI stores its configuration files in a directory called `~/.dcos` within your HOME directory. However, you can specify a different location by using the `DCOS_CONFIG` environment variable. The configuration settings are stored in the `dcos.toml` file. You can modify these settings with the `dcos config` command. #### dcos_url The public master IP of your DC/OS installation. This is set by default during installation. For example: ```bash dcos config set core.dcos_url 52.36.102.191 ``` #### dcos_acs_token The token generated by authenticating to DC/OS with the Access Control Service (ACS). To set the ACS token, run: ```bash dcos config set core.dcos_acs_token <token> ``` #### mesos_master_url The Mesos master URL. This must be of the format: `http://<host>:<port>`. For example, to set your Mesos master URL: ```bash dcos config set core.mesos_master_url 52.34.160.132:5050 ``` #### pagination Indicates whether to paginate output. By default this is set to `True`. For example, to set to false: ```bash dcos config set core.pagination False ``` #### ssl_verify Indicates whether to verify SSL certs for HTTPS or path to certs. By default this is set to `True`. For example, to set to false: ```bash dcos config set core.ssl_verify False ``` #### timeout Request timeout in seconds, with a minimum value of 1 second. By default this is set to 5 seconds. For example, to set to 3 seconds: ```bash dcos config set core.timeout 3 ```	35.218045	359	0.743168	eng_Latn	0.983245
b7f81006a2cb990d87b81a0cdb943d77e8e28efb	363	md	Markdown	README.md	opticdev/optic-intellij-platform-plugin	e4c769bafe37083cd80027433c1b9f9f45fbbb06	[ "MIT" ]	1	2018-06-03T18:55:48.000Z	2018-06-03T18:55:48.000Z	README.md	opticdev/optic-intellij-platform-plugin	e4c769bafe37083cd80027433c1b9f9f45fbbb06	[ "MIT" ]	null	null	null	README.md	opticdev/optic-intellij-platform-plugin	e4c769bafe37083cd80027433c1b9f9f45fbbb06	[ "MIT" ]	null	null	null	# Optic JetBrains Plugin A lightweight plugin that allows you to use Optic with any JetBrains IDE. This plugin will forward the state of your IDE (current file, position and staged content) to Optic. The plugin itself has no GUI or configuration options to worry about. ## Install [From JetBrains Marketplace](https://plugins.jetbrains.com/plugin/10786-optic)	60.5	246	0.793388	eng_Latn	0.956382
b7f81f2ca576b51dd01d2ce91f3ee3f0502fe51f	249	md	Markdown	content/fr/blog/_index.md	rendiputra/website	4b93c0608828e685881be1662e766d696f0b097b	[ "CC-BY-4.0" ]	3,157	2017-10-18T13:28:53.000Z	2022-03-31T06:41:57.000Z	content/fr/blog/_index.md	rendiputra/website	4b93c0608828e685881be1662e766d696f0b097b	[ "CC-BY-4.0" ]	27,074	2017-10-18T09:53:11.000Z	2022-03-31T23:57:19.000Z	content/fr/blog/_index.md	rendiputra/website	4b93c0608828e685881be1662e766d696f0b097b	[ "CC-BY-4.0" ]	11,539	2017-10-18T15:54:11.000Z	2022-03-31T12:51:54.000Z	--- title: Blog de Kubernetes linkTitle: Blog menu: main: title: "Blog" weight: 40 post: > <p>Lisez les dernières nouvelles à propos de Kubernetes et des conteneurs en général. Obtenez les derniers tutoriels techniques.</p> ---	22.636364	139	0.686747	fra_Latn	0.745529
b7f820bcca7074759c5532896ba55375fdd2814c	646	md	Markdown	docs/add/metadata/DocumentFormat.OpenXml.Office2010.Excel/OlapSlicerCacheItemParent.meta.md	mairaw/open-xml-docs-ref-dotnet	078db78b64aaade35a15f31e279cc81294f0bae1	[ "CC-BY-4.0", "MIT" ]	3	2021-01-14T16:13:01.000Z	2021-08-30T21:20:02.000Z	docs/add/metadata/DocumentFormat.OpenXml.Office2010.Excel/OlapSlicerCacheItemParent.meta.md	mairaw/open-xml-docs-ref-dotnet	078db78b64aaade35a15f31e279cc81294f0bae1	[ "CC-BY-4.0", "MIT" ]	12	2018-08-02T20:11:26.000Z	2022-02-15T02:39:52.000Z	docs/add/metadata/DocumentFormat.OpenXml.Office2010.Excel/OlapSlicerCacheItemParent.meta.md	mairaw/open-xml-docs-ref-dotnet	078db78b64aaade35a15f31e279cc81294f0bae1	[ "CC-BY-4.0", "MIT" ]	7	2018-10-11T16:55:35.000Z	2021-05-05T15:13:48.000Z	--- uid: DocumentFormat.OpenXml.Office2010.Excel.OlapSlicerCacheItemParent ms.author: "soliver" manager: "soliver" --- --- uid: DocumentFormat.OpenXml.Office2010.Excel.OlapSlicerCacheItemParent.LocalName ms.author: "soliver" manager: "soliver" --- --- uid: DocumentFormat.OpenXml.Office2010.Excel.OlapSlicerCacheItemParent.Name ms.author: "soliver" manager: "soliver" --- --- uid: DocumentFormat.OpenXml.Office2010.Excel.OlapSlicerCacheItemParent.CloneNode(System.Boolean) ms.author: "soliver" manager: "soliver" --- --- uid: DocumentFormat.OpenXml.Office2010.Excel.OlapSlicerCacheItemParent.#ctor ms.author: "soliver" manager: "soliver" ---	21.533333	96	0.780186	yue_Hant	0.371219
b7f863703738a72283ad0ee306bc9237211624db	2,939	md	Markdown	README.md	Hekstra-Lab/nesm-python	5b13cebe0019a589ea234d1191148e120aa75114	[ "BSD-3-Clause" ]	1	2021-05-07T18:03:30.000Z	2021-05-07T18:03:30.000Z	README.md	Hekstra-Lab/nesm-python	5b13cebe0019a589ea234d1191148e120aa75114	[ "BSD-3-Clause" ]	1	2021-05-13T14:54:27.000Z	2021-05-13T14:54:27.000Z	README.md	Hekstra-Lab/nesm-python	5b13cebe0019a589ea234d1191148e120aa75114	[ "BSD-3-Clause" ]	null	null	null	# NESM Python Workshop Notebooks for the python workshop at the New England Society for Microscopy Spring 2021 Meeting Prepared and presented by John Russell ([email protected]) and Ian Hunt-Isaak ([email protected]) ## Where to start: If you are reading this independently we recommend you start in the `solutions` folder. ## Proposed Schedule See [`outline.md`](outline.md) for a more detailed outline. - Part 1 Python basics - Part 2 Hardware Control - Part 3 Image analysis and I/O - Part 4 Advanced topics ## Getting started ### Online Version To get a known working envinroment without setting up a local python environment go to this binder link: [![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/Hekstra-Lab/nesm-python/spring-2021?urlpath=lab) This binder can run all the code except for the end of `part3` where we use `Napari` as Napari cannot run in a browser window. ### Local Installation Please install `conda`, a package manager, with python 3.8 or 3.9. Follow one of the links below and then follow instructions for your operating system. There are two options 1. [Miniconda](https://docs.conda.io/en/latest/miniconda.html) - an absolutely minimal version - [miniforge](https://github.com/conda-forge/miniforge#miniforge) version maintained by open source community 2. [Conda](https://conda.io/projects/conda/en/latest/user-guide/install/index.html#regular-installation) - this version includes conda as well as many other common python packages. Actual installation steps 1. Open a terminal (mac or linux) or the Anaconda Prompt (windows) 1. Type the following and press enter: `conda create -n nesm python`. This uses `conda` to create a new environment with the name (`-n`) `nesm`. It will install the latest python version in that environment. Whenever you are starting a new project, it is best to create a new environement. 1. `conda info --envs` -- this will list all the environments on your computer. Note that `base` is the default. The `` next to an environement means that you are currently using that environment. 1. `conda activate nesm` -- Switch to using the newly created `nesm` environment. (If you run `conda info --envs` again you will see that the `` has moved.) 1. `conda install -c conda-forge numpy scipy matplotlib jupyterlab xarray scikit-image ipympl dask scikit-learn` -- This line uses `conda` to `install` several common python libraries. We will use all of them in this workshop (time permitting). We also specify to install these libraries from `conda-forge` which is the community maintatined repository for conda installable software. This is where the most up to date versions of software are. 1. `pip install mpl_interactions tifffile dask_labextension hyperspy 'napari[all]'` - This uses `pip` the default python package installer to install a few extra libraries that are not available through conda.	63.891304	445	0.769309	eng_Latn	0.995865
b7f8d1562a4ddd2f592ed643ce7c269f47bdfb9c	668	md	Markdown	docs/pages/versions/v30.0.0/react-native/settings.md	mwood23/expo	d686e66d19cf69a8c756d9d111ae9df08c9ebe39	[ "Apache-2.0", "MIT" ]	null	null	null	docs/pages/versions/v30.0.0/react-native/settings.md	mwood23/expo	d686e66d19cf69a8c756d9d111ae9df08c9ebe39	[ "Apache-2.0", "MIT" ]	1	2019-01-30T19:04:30.000Z	2019-01-30T19:04:30.000Z	docs/pages/versions/v30.0.0/react-native/settings.md	mwood23/expo	d686e66d19cf69a8c756d9d111ae9df08c9ebe39	[ "Apache-2.0", "MIT" ]	null	null	null	--- id: settings title: Settings --- import withDocumentationElements from '~/components/page-higher-order/withDocumentationElements'; export default withDocumentationElements(meta); ### Methods * [`get`](../settings/#get) * [`set`](../settings/#set) * [`watchKeys`](../settings/#watchkeys) * [`clearWatch`](../settings/#clearwatch) ### Properties --- # Reference ## Methods ### `get()` ```javascript static get(key) ``` --- ### `set()` ```javascript static set(settings) ``` --- ### `watchKeys()` ```javascript static watchKeys(keys, callback) ``` --- ### `clearWatch()` ```javascript static clearWatch(watchId) ``` ## Properties	9.150685	97	0.627246	eng_Latn	0.458492
b7f8efe4abb0952891f7a9fac1c8886a76ee48e6	1,944	md	Markdown	README.md	rugginoso/dread	a3c6267b0db1c229c89dd059d9c313f2c605feba	[ "BSD-3-Clause" ]	null	null	null	README.md	rugginoso/dread	a3c6267b0db1c229c89dd059d9c313f2c605feba	[ "BSD-3-Clause" ]	null	null	null	README.md	rugginoso/dread	a3c6267b0db1c229c89dd059d9c313f2c605feba	[ "BSD-3-Clause" ]	null	null	null	&&&&& & @ @ & 0 & \| & 0 & \_o===0 &\ _ /& & & & & DREAD - REST microframework Overview ======== The code is in an alpha stage DREAD is a web microframework based on [Werkzeug](https://github.com/mitsuhiko/werkzeug) explicitely wrote to implement REST services. It support high level resource action definition and nested resources. Installation ============ ``` $ pip install dread ``` Example ======= ```python from dread.base import BaseResource from dread.json import JSONDispatcher from werkzeug.exceptions import NotFound class User(BaseResource): def __init__(self): self.users = [] super(User, self).__init__(name="users", param_name="user_id") def on_list(self, params): return {'data': self.users} def on_detail(self, params): try: return self.users[params['user_id']] except IndexError: raise NotFound def on_create(self, params): new_user = params['data'] self.users.append(new_user) return {'data': new_user} def on_update(self, params): try: self.users[params['user_id']] = params['data'] return {'data': self.users[params['user_id']]} except IndexError: raise NotFound def on_delete(self, params): try: del self.users[params['user_id']] return {} except IndexError: raise NotFound class Item(BaseResource): def __init__(self): super(Item, self).__init__(name='items', param_name='item_id') def on_list(self, params): return {'owner': params['user_id']} def on_detail(self, params): return {'owner': params['user_id'], 'item': params['item_id']} app = JSONDispatcher() users_resource = User() app.add_resource(users_resource) app.add_resource(Item(), users_resource) if __name__ == '__main__': app.run() ```	23.142857	134	0.605967	eng_Latn	0.271818
b7f8f22497109b8b2daa81a8c0d00365b415f32c	33	md	Markdown	README.md	andre-xs/meu-repositorio	a15fbf4de5cbddc07eaa7478951f1be4dffb6e37	[ "MIT" ]	null	null	null	README.md	andre-xs/meu-repositorio	a15fbf4de5cbddc07eaa7478951f1be4dffb6e37	[ "MIT" ]	null	null	null	README.md	andre-xs/meu-repositorio	a15fbf4de5cbddc07eaa7478951f1be4dffb6e37	[ "MIT" ]	null	null	null	# Meu Repositório HTML5-CSS3-JS	11	17	0.757576	por_Latn	0.981395
b7f9b2eb08ed7a1df29be5137864e5ece3a60194	912	md	Markdown	AlchemyInsights/price-doesn-t-look-correct.md	isabella232/OfficeDocs-AlchemyInsights-pr.sr-Latn-RS	eb66d955dca362c1508b6ad53bf0974ef5a7a1a0	[ "CC-BY-4.0", "MIT" ]	1	2020-05-19T19:08:02.000Z	2020-05-19T19:08:02.000Z	AlchemyInsights/price-doesn-t-look-correct.md	MicrosoftDocs/OfficeDocs-AlchemyInsights-pr.sr-Latn-RS	ef115121eb0e71ad7eddda959b97441101a2b11a	[ "CC-BY-4.0", "MIT" ]	3	2020-06-02T23:14:22.000Z	2022-02-09T06:57:49.000Z	AlchemyInsights/price-doesn-t-look-correct.md	isabella232/OfficeDocs-AlchemyInsights-pr.sr-Latn-RS	eb66d955dca362c1508b6ad53bf0974ef5a7a1a0	[ "CC-BY-4.0", "MIT" ]	2	2019-10-09T20:34:14.000Z	2020-06-02T23:12:22.000Z	--- title: Cena ne izgleda ispravno? ms.author: cmcatee author: cmcatee-MSFT manager: scotv ms.reviewer: jkinma, jmueller ms.audience: Admin ms.topic: article ms.service: o365-administration ROBOTS: NOINDEX, NOFOLLOW localization_priority: Normal ms.collection: Adm_O365 ms.custom: - commerce_billing - "473" - "1500027" ms.date: 04/21/2020 ms.assetid: 9703c272-2836-4ca2-9d91-cf1e86120dea ms.openlocfilehash: 43d6e94e94f890feba4c472387dfdcdefefe811d ms.sourcegitcommit: e781da003fb7b878854846cbe12b13b9dca8df92 ms.translationtype: MT ms.contentlocale: sr-Latn-RS ms.lasthandoff: 08/31/2021 ms.locfileid: "58844220" --- # <a name="price-doesnt-look-correct"></a>Cena ne izgleda ispravno? Ako cena na fakturi ne izgleda ispravno, to može biti zbog promena cena pri obnovi. Ako ne smatrate da to objašnjava problem, koristite opciju "Dozvolite nam da vas pozovemo" da biste porazgovarali sa inženjerom za podršku.	32.571429	223	0.804825	hrv_Latn	0.427063
b7f9c59c06a3f31252cee0975f812cdc6348f3c9	254	md	Markdown	ci/README.md	mariojmdavid/sqa-baseline	d63edeeccd7eb73ba72e6a9231549e580da52f3d	[ "CC-BY-4.0", "CC0-1.0" ]	7	2019-02-07T15:34:32.000Z	2021-09-17T07:32:09.000Z	ci/README.md	mariojmdavid/sqa-baseline	d63edeeccd7eb73ba72e6a9231549e580da52f3d	[ "CC-BY-4.0", "CC0-1.0" ]	63	2019-02-07T15:24:40.000Z	2022-03-23T11:59:11.000Z	ci/README.md	mariojmdavid/sqa-baseline	d63edeeccd7eb73ba72e6a9231549e580da52f3d	[ "CC-BY-4.0", "CC0-1.0" ]	3	2019-04-01T19:07:35.000Z	2019-10-16T10:42:36.000Z	# Continuous integration tools [![Build Status](https://travis-ci.org/indigo-dc/sqa-baseline.svg?branch=master)](https://travis-ci.org/indigo-dc/sqa-baseline) For more information on the CI implementation, see the CI setup documentation in `SETUP.md`.	42.333333	127	0.771654	eng_Latn	0.365164
b7f9d3f70905f3bd02cd1b3093709b645f1f14fc	10,481	md	Markdown	git-commands.md	woai3c/Front-end-development-process	4074f49e2f56e8ffd65a900042cea2a3004306e3	[ "MIT" ]	1	2021-10-21T01:44:37.000Z	2021-10-21T01:44:37.000Z	git-commands.md	sarlemon/Front-end-articles	ed49838c8b9b72a46a8cf6b9b102ba59e8a5dffb	[ "MIT" ]	null	null	null	git-commands.md	sarlemon/Front-end-articles	ed49838c8b9b72a46a8cf6b9b102ba59e8a5dffb	[ "MIT" ]	null	null	null	# git 常用命令介绍 ## 基础命令 ### 1. `git add <file>` 将 `file.txt` 文件添加到暂存区。 ``` git add file.txt ``` 将当前所有有变动的文件添加到暂存区。 ``` git add . ``` ### 2. `git commit` 将暂存区的文件提交到当前分支。 ``` git commit -m '将刚才添加到暂存区的文件提交到当前分支，-m 代表要加注释' ``` 修改最近一次提交的消息： ``` git commit --amend ``` 修改最近一次提交的用户信息： ``` git commit --amend --author="xxx <[email protected]>" --no-edit ``` #### 全局修改邮箱地址另一个常见的情形是在你开始工作时忘记运行 git config 来设置你的名字与邮箱地址，或者你想要开源一个项目并且修改所有你的工作邮箱地址为你的个人邮箱地址。任何情形下，你也可以通过 filter-branch 来一次性修改多个提交中的邮箱地址。需要小心的是只修改你自己的邮箱地址，所以你使用 --commit-filter： ``` git filter-branch --commit-filter ' if [ "$GIT_AUTHOR_EMAIL" = "schacon@localhost" ]; then GIT_AUTHOR_NAME="Scott Chacon"; GIT_AUTHOR_EMAIL="[email protected]"; git commit-tree "$@"; else git commit-tree "$@"; fi' HEAD ``` 这会遍历并重写每一个提交来包含你的新邮箱地址。因为提交包含了它们父提交的 SHA-1 校验和，这个命令会修改你的历史中的每一个提交的 SHA-1 校验和，而不仅仅只是那些匹配邮箱地址的提交。 ### 3. `git push <远程主机名> <分支名>` 推送分支，就是把该分支上的所有本地提交推送到远程库。 ``` git push origin master ``` 上面命令表示，将本地的 master 分支推送到 origin 主机的 master 分支。如果 master 不存在，则会被新建。远程库的名字就是 origin，这是 Git 默认的叫法，也可以改成别的，但是 origin 这个名字一看就知道是远程库。推送到远程仓库 dev 分支。 ``` git push origin dev ``` 第一次使用时要带上 `-u` 参数 ``` git push -u origin master ``` 以后每次提交就可以直接使用 `git push` 了，不用每次都输上一串命令 ``` git push ``` 要同时为源和目的地指定 <分支名> 的话，只需要用冒号 : 将二者连起来就可以了： ``` git push origin <source>:<destination> ``` 例如 `git push origin a:b` 命令，它会把本地分支 a 推送到远程分支 b，如果分支 b 不存在，还会创建它。而且还能这样使用 `git push origin a^:b`，这样将把 a 分支的父提交推送到远程分支 b。注意，如果 source 为空，它将删除远程分支。`git push origin :foo` 这条命令将删除远程分支 foo。 ### 4. `git fetch <远程主机名> <分支名>` `git fetch origin foo`， Git 会到远程仓库的 foo 分支上，然后获取所有本地不存在的提交，放到本地的 origin/foo 上。`git fetch` 它不会更新你的本地的非远程分支, 只是下载提交记录。所以它把提交记录放在 origin/foo 上，而不是 foo 分支。如果一定要直接更新本地分支，可以使用 `git fetch origin <source>:<destination>`，其中 source 是指远程分支，destination 是本地分支，正好与 `git pull` 相反。例如 `git fetch origin foo~1:bar`，它把远程分支 foo 的上一个记录更新到本地分支 bar。如果 git fetch 没有参数，它会下载所有的提交记录到各个远程分支... 注意，如果 fetch 空到本地，它将创建一个分支。`git fetch origin :foo` 将在本地创建一个 foo 分支。 ### 5. `git pull` `git pull` 将远程仓库的更新拉取下来，再和本地分支进行合并。它相当于 `git fetch` `git merge` 这两个操作的结合。 `git pull origin foo` 相当于 `git fetch origin foo; git merge origin/foo`。 ![image](https://user-images.githubusercontent.com/22117876/134711798-6320f10f-81e0-4d9d-b8f1-d5144da94142.png) ### 6. `git branch` `git checkout`... * `git branch` 查看当前所有分支 * `git branch <name>` 创建分支 * `git checkout <name> [commitid--可选的 commitid]` 切换分支 * `git branch -d <branchName>` 删除本地分支 * `git push origin --delete <branchName>` 删除远程分支 * `git checkout <commitid>` 将 HEAD 切换到该记录创建分支 dev ``` git branch dev ``` 切换到分支 dev ``` git checkout dev ``` `git checkout` 命令加上 `-b` 参数表示创建并切换，`git checkout -b dev` 相当于以下两条命令: ``` git branch dev git checkout dev ``` 强制切换分支到指定的 commit ``` git branch -f <branchName> <commitID> ``` 将当前 HEAD 分支的记录树往后移动 2 个 commit ``` git checkout HEAD~2 ``` ### 7. `git log` `git log` 命令可以查看提交的历史记录。 ``` E:\res\platform>git log commit 783ec77f1447125971aa2651e4320a768938d453 (HEAD -> 3.0, origin/3.0) Author: woai3c <[email protected]> Date: Wed Apr 22 14:19:00 2020 +0800 chore: 只有打包时才应用忽略 console.log 语句 commit 514cf81798a14b3bf273019d02885f87bf8ad2ac Author: woai3c <[email protected]> Date: Wed Apr 22 13:40:11 2020 +0800 feat: 添加全局 log 函数 ``` 如果不想显示无用的信息，可以使用 `git log --pretty=oneline` ``` E:\res\platform>git log --pretty=oneline 783ec77f1447125971aa2651e4320a768938d453 (HEAD -> 3.0, origin/3.0) chore: 只有打包时才应用忽略 console.log 语句 514cf81798a14b3bf273019d02885f87bf8ad2ac feat: 添加全局 log 函数 2f0e28962d3f2d5e9c047387560986411d2a07d0 chore: 更新 eslint 规则 ``` ### 8. `git reset` 版本回退 `git reset` 命令用于版本回退。假如你正在开发一个项目，有一天产品提了个新功能，要求三天内完成，于是你快马加鞭、加班加点终于在三天内完成了。结果第四天产品告诉你新功能不要了。你想打死产品的心都有了，话虽如此，工作还是得继续，这时 `git reset` 就可以派上用场了。将版本回退到上一版本。 ``` git reset --hard HEAD~1 ``` 将版本回退到三个版本前。 ``` git reset --hard HEAD~3 ``` 也可以指定固定的版本进行回退，先使用 `git log --pretty=oneline` 命令查看历史记录，将想要回退版本的 commit id 复制一下，回退时使用这个 commit id 进行回退。 ``` git reset --hard 485776d96f57db88c6a6f31146532d21fc01b1ab ``` 接着使用 `git push -f` 将回退版本后的分支强制推送到远程仓库，这样本地分支和远程分支就同步了。 ``` git push -f ``` 用远程分支覆盖本地分支 ``` git fetch --all git reset --hard origin/master（这里的 master 为远程分支） ``` ### 9. `git revert` `git revert` 也可以撤销记录，只不过它撤销的记录不会消失，这一点和 `git reset` 不一样。`git reset` 撤销的记录就跟消失了一样。假设现在当前分支有 `a b c d` 记录，执行 `git reset b` 后，当前的分支记录会变成 `a b`。如果用 `git revert` 来撤销记录，即执行 `git revert b`，会在当前分支上再生成一个新的 commit 记录，变成 `a b c d b'`，这个 `b'` 的状态和记录 `b` 是一样的。如果你想让别人知道你撤销过记录，就使用 `git revert`，因为它会留下撤销的记录，否则用 `git reset`。 ### 10. `git rebase` 如果你想将多个 commit 合并成一个，可以使用 `git rebase`。假设你有三次提交，分别为 abc。并且需要合并 ab，则输入以下命令： ``` git rebase -i <c 的 commit id> ``` 下面是一个真实示例： ``` git rebase -i c486fa803767ff75780c8df7e18b560fdc332b1e ``` 执行命令后，会弹出一个框，上面会显示 a 和 b 的 commit 消息。类似于这样： ```vim pick 9fe8f12 chore: 全局命令 mvl -> mvc(mini-vue-cli) pick 645156a chore(create): 美化下载格式提示语 ``` 同时有一些命令需要了解一下： ``` p, pick = use commit r, reword = use commit, but edit the commit message e, edit = use commit, but stop for amending s, squash = use commit, but meld into previous commit f, fixup = like “squash”, but discard this commit’s log message x, exec = run command (the rest of the line) using shell d, drop = remove commit ``` 按照上述命令的解释，这时只要保证第一个 commit 不动，将第二个 commit 的 pick 改为 s 就可以了。由于这是 vi 编辑模式，所以你需要按一下 i 才可以开始编辑，编辑完成按一个 esc 然后输入 :wq 回车即可。这时还会弹出一个提示框，让你更改 commit message。按照刚才的操作修改完后保存即可。最后在命令行执行 `git push -f` 推送到远程仓库。 #### 合并分支 `git rebase <branchName>`，假设要将 test 分支合到 main 分支上，可以在 test 分支上执行 `git rebase main`。也可以用 `git rebase main test`，这时不管你在哪个分支上执行这条命令，都会把 test 分支 rebase 到 main 分支上。 ### 11. 解决冲突当执行 `git pull`，将远程分支和本地分支合并时，有可能会出现冲突的情况。例如有 A 和 B 两个人，对同一文件 `test.txt` 进行了修改。A 修改完后先提交到了远程分支，当 B 要提交时，执行 `git pull`，发现远程仓库的 `test.txt` 和自己本地的版本有冲突。 ``` ### 以太网的的信道利用率 ### 以太网的的信道利用率 <<<<<<< HEAD aaaaaa ======= bbb >>>>>>> 9ccc398514d6a80a6ea2e44ade8171660d15cacf ### 以太网的的信道利用率 ### 以太网的的信道利用率 ``` 从上面的代码可以看出，当前版本的文件内容 `aaaaaa` 和远程仓库文件的内容 `bbb` 产生了冲突。冲突用 `<<<` `====` `>>>>` 将产生冲突的内容分隔开，如果你觉得远程仓库的内容不对，要换成自己的，那可以这样改。 ``` ### 以太网的的信道利用率 ### 以太网的的信道利用率 aaaaaa ### 以太网的的信道利用率 ### 以太网的的信道利用率 ``` 把 `<<<` `===` `>>>` 删除掉，并替换成自己的内容，再执行 `git add` `git commit` 提交内容。这时，执行 `git pull`，你会发现没有更新，刚修改的内容也不会变，最后再执行 `git push` 将内容推送到远程仓库。 ### 12. `git merge` 将指定分支合并到当前分支。例如你想将 a 分支合并到 b 分支，则切换到 b 分支，并执行： ``` git merge a ``` git merge 合并分支后可能不是一条直线，所以可以使用 git rebase 来合并分支。这样合并后在历史记录上看起来就是一条直线了。 ``` git rebase a ``` ### 13. `git tag` 打标签 ``` git tag <tagName> ``` 如果忘记打标签了，可以指定以前的 commit 打标签 ``` git tag <tagName> <commitid> ``` 推送标签 ``` git push origin --tags ``` 删除标签 ``` git tag -d <tagName> ``` 删除远程标签 ``` git push origin --delete <tagname> ``` ### 14. `git cherry-pick` 如果你想将某个指定记录放到当前分支上，可以使用 `git cherry-pick <commitid1> <commitid2>...`。假设当前分支为 master，历史记录为 `x y`。现在 dev 分支上有 `a b c d` 四个记录，你想将其中的 b 记录合并到当前分支，可以执行 `git cherry-pick b`。执行后 master 分支变为 `x y b`。或者想批量提交 dev 分支中的 `b d` 两个记录，可以执行 `git cherry-pick b d`。这样 dev 分支的 `b d` 记录就合并到 master 分支了，变成 `x y b d`。另外批量连续合并还有省略语法 ``` git cherry-pick A..B ``` 这表示合并从 A 到 B 的所有记录。 ### 15. `git describe` `git describe` 的语法是： ``` git describe <ref> ``` <ref> 可以是任何能被 Git 识别成提交记录的引用，如果你没有指定的话，Git 会以你目前所检出的位置（HEAD）。它输出的结果是这样的： ``` <tag>_<numCommits>_g<hash> ``` tag 表示的是离 ref 最近的标签， numCommits 是表示这个 ref 与 tag 相差有多少个提交记录， hash 表示的是你所给定的 ref 所表示的提交记录哈希值的前几位。当 ref 提交记录上有某个标签时，则只输出标签名称。 ![image](https://user-images.githubusercontent.com/22117876/132954224-2a6a7cea-be85-4719-930e-fd614980eb45.png) ### 16. `^` 和 `~` 的区别操作符 `^` 与 `~` 符一样，后面也可以跟一个数字。但是 `^` 操作符后面的数字与 `~` 后面的不同，并不是用来指定向上返回几代，而是指定合并提交记录的第几个父记录。还记得前面提到过的一个合并提交有两个记录吧，所以遇到这样的节点时该选择哪条路径就不是很清晰了。 Git 默认选择合并提交的“第一个”父记录，在操作符 `^` 后跟一个数字可以改变这一默认行为。 ![image](https://user-images.githubusercontent.com/22117876/132990602-5038f4ec-4c57-48e5-aa35-dfe26f8076a1.png) ![image](https://user-images.githubusercontent.com/22117876/132990627-0fa9c6b2-78c7-4ce6-905d-a686ee798244.png) ![image](https://user-images.githubusercontent.com/22117876/132990636-d984e9c4-84f1-4efa-9a1d-a43988b3ecbe.png) ![image](https://user-images.githubusercontent.com/22117876/132990701-643719be-989e-4236-99d7-f938e0c8ba09.png) 从下面的示例也可以看出它们俩的区别： ``` G H I J \ / \ / D E F \ \| / \ \ \| / \| \\|/ \| B C \ / \ / A A = = A^0 B = A^ = A^1 = A~1 C = A^2 = A^2 D = A^^ = A^1^1 = A~2 E = B^2 = A^^2 F = B^3 = A^^3 G = A^^^ = A^1^1^1 = A~3 H = D^2 = B^^2 = A^^^2 = A~2^2 I = F^ = B^3^ = A^^3^ J = F^2 = B^3^2 = A^^3^2 ``` ### 17. 本地分支与远程分支大家都知道，本地分支 main 是和远程分支 origin/main 关联的。这种关联在以下两种情况下可以清楚地得到展示： * pull 操作时, 提交记录会被先下载到 origin/main 上，之后再合并到本地的 main 分支。隐含的合并目标由这个关联确定的。 * push 操作时, 我们把工作从 main 推到远程仓库中的 main 分支(同时会更新远程分支 origin/main) 。这个推送的目的地也是由这种关联确定的！ ![image](https://user-images.githubusercontent.com/22117876/134705044-f3194ef2-739e-4ee5-8fce-33e333f258bd.png) 改变本地分支与远程分支关联的方法： 1. `git checkout -b foo origin/main`，就可以创建一个名为 foo 的分支，它跟踪远程分支 origin/main。 2. `git branch -u origin/main foo`，这样也可以让 foo 跟踪 origin/main。 ## 高级技巧 ### 1. 修改历史 commit 的消息假设当前分支有 `a b c d` 四个 commit 记录: ``` a b c d ``` 如果你想对 `c` 记录的消息进行修改。可以使用 `git rebase` 将 `c` 记录换到最前面，然后使用 `git commit --amend` 对其消息进行修改。 #### 具体操作步骤执行以下命令对记录 `d` 前面的三个 commit 进行编辑： ``` git rebase -i d ``` 进行 vim 编辑界面后，移动光标到 c 记录上，按下 `dd` 剪切该记录，然后移动光标到第一行，按下 `p` 粘贴，再输入 `:wq` 保存。执行 `git commit --amend` 对切换顺序后的 `c` 记录进行修改。然后按照刚才的操作将 `c` 记录恢复到原来的位置。最后执行 `git push -f` 强推到远程仓库。 ![image](https://user-images.githubusercontent.com/22117876/132132078-4de2cf12-8529-4556-9b6b-77f048fa347d.png) 就和上图一样，这是当前分支修改后和远程分支上的对比，箭头指向的记录消息就是修改后的消息。 #### 第二种方式 1. 使用 `git checkout -b <branchName> c` 从指定记录切出一个分支 2. 在新分支使用 `git commit --amend` 修改提交消息 3. 使用 `git cherry-pick` 将 `b a` 记录，追加到新分支（注意，这里的 `b a` 提交记录是指原分支上的 commit，也就是选取原分支上的 `b a` 记录添加到新分支上，这样新分支上的记录就变成了 `a b c`，并且 c 记录的提交消息在第二步已经修改过） 4. 使用 `git checout 原分支名` 切换回原来的分支，再执行 `git rebase <branchName>` 合并新分支，最后强推到远程分支 ### 2. 合并分支前，先整理当前分支的记录假设你切了一个 bugFix 分支来修复线上 bug，经过一段时间的努力后终于将 bug 修复了。但是为了调试（加了很多 debug 代码）或其他原因，bugFix 上多了很多无用的记录消息。 ``` commit3: 修复登录 bug commit2: 添加 debug 语句 commit1: 添加 console 语句 ``` 例如上面的三个记录，前面的两个记录添加了很多调试代码，在最后一个记录终于修复了 bug，并且删除了调试代码。这时如果直接将 bugFix 分支合到 master 分支，就会把调试的记录也合并进来。这时可以使用 `git cherry-pick` 只将最后一个记录合并到 master 分支。或者使用 `git rebase` 将 bugFix 分支另外两个记录抛弃，然后再合并。 ## 参考资料 * [Git教程-廖雪峰](https://www.liaoxuefeng.com/wiki/896043488029600) * [learngitbranching](https://learngitbranching.js.org/?locale=zh_CN)	26.072139	167	0.704227	yue_Hant	0.781361
b7fc6aed0919d00d6a5778c85c8d34943ec8bcb5	15	md	Markdown	README.md	wawansukma/wa	d9434dbebff7490e88a6d14e3a188e659f6c28e6	[ "MIT" ]	null	null	null	README.md	wawansukma/wa	d9434dbebff7490e88a6d14e3a188e659f6c28e6	[ "MIT" ]	null	null	null	README.md	wawansukma/wa	d9434dbebff7490e88a6d14e3a188e659f6c28e6	[ "MIT" ]	null	null	null	# wa tombol wa	5	9	0.666667	swh_Latn	0.590059
b7fcd05a32cee916a97e823f40d64b19b3fcae84	4,307	md	Markdown	business-central/LocalFunctionality/Italy/how-to-set-up-automatic-payments-and-automatic-bills.md	momoto/dynamics365smb-docs	040514c47391773f6391f9a1e15a3af506fb2d79	[ "CC-BY-4.0", "MIT" ]	null	null	null	business-central/LocalFunctionality/Italy/how-to-set-up-automatic-payments-and-automatic-bills.md	momoto/dynamics365smb-docs	040514c47391773f6391f9a1e15a3af506fb2d79	[ "CC-BY-4.0", "MIT" ]	null	null	null	business-central/LocalFunctionality/Italy/how-to-set-up-automatic-payments-and-automatic-bills.md	momoto/dynamics365smb-docs	040514c47391773f6391f9a1e15a3af506fb2d79	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- title: How to Set Up Automatic Payments and Automatic Bills description: In Business Central, you can manage automatic payments and bills. author: SorenGP ms.service: dynamics365-business-central ms.topic: article ms.devlang: na ms.tgt_pltfrm: na ms.workload: na ms.search.keywords: ms.date: 10/01/2019 ms.author: sgroespe --- # Set Up Automatic Payments and Automatic Bills In [!INCLUDE[d365fin](../../includes/d365fin_md.md)], you can manage automatic payments and bills. To use automatic payments and automatic bills, you must set up the relevant information. ## To add bank information for your company 1. Choose the ![Search for Page or Report](../../media/ui-search/search_small.png "Search for Page or Report icon") icon, enter Company Information, and then choose the related link. 2. On the Payments FastTab, fill in the key fields as described in the following table. \|Field\|Description\| \|------------------------------------\|---------------------------------------\| \|Payment Method\|Select the payment method for the type of payments made to or from this bank account. For example, for the bank account that will be used for automatic payments made by customers, select a payment method for bank transfers.\| \|Bills For Collection Acc. No.\|Specify the general ledger account where bills for collection will be credited.\| \|Bills For Discount Acc. No.\|Specify the general ledger account where bill discounts will be debited.\| \|Bills Subj. to Coll. Acc. No.\|Specify the general ledger account where bills subject to collection will be credited.\| \|Expense Bill Account No.\|Specify the general ledger account where expenses for bank receipts will be posted.\| 5. Choose the OK button. > [!IMPORTANT] > Before you can export a vendor bill, you must select a payment format in the Payment Export Format field on the Bank Account Card page. > > Before you can export a customer bill, you must select a payment format in the SEPA Direct Debit Exp. Format field on the Bank Account Card page. The following procedure describes how to set up automatic bills for sales and receivables, but the same steps also apply to setting up purchases and payables for using automatic payments. ## To set up automatic bills for sales and receivables 1. Choose the ![Search for Page or Report](../../media/ui-search/search_small.png "Search for Page or Report icon") icon, enter Sales & Receivables Setup, and then choose the related link. 2. On the Bills FastTab, in the Temporary Bill List No. field, select the temporary bill list number. Fill in the fields as described in the following table. \|Field\|Description\| \|---------------------------------\|---------------------------------------\| \|Temporary Bill List No.\|Select the number series that will be used for temporary bill lists.\| \|Recall Bill Description\|Specify the descriptive text that will be used for recalled bills.\| \|Bank Receipts Risk Period\|Specify a date formula to calculate the risk period in days, such as 20D.<br /><br /> This will be a reference for bank receipt closing. Customer bills will be closed only at the end of the risk period that you specify here.\| 3. Choose the OK button. Next, you must specify bill codes for those payment methods that you use for automatic payments and automatic bills. ## To specify bill codes for a payment method 1. Choose the ![Search for Page or Report](../../media/ui-search/search_small.png "Search for Page or Report icon") icon, enter Payment Methods, and then choose the related link. 2. Select the payment method that you use for bank transfers to vendors, and then, in the Bill Code field, select a bill code. 1. To create a bill code, in the Bill Code field, choose the field, and then choose the New action. 2. On the Bill page, fill in the fields. Now, you can process customer bills and vendor bills so that they are handled automatically. ## See Also [Defining Payment Methods](../../finance-payment-methods.md) [Italy Local Functionality](italy-local-functionality.md)	59.819444	266	0.693987	eng_Latn	0.992318
b7fd5f0d960a1c0b82011d8694a717c0c9c6d348	161	markdown	Markdown	_posts/2016-07-25-powershellbrasil.markdown	ProgramacaoPratica/listatelegram.github.io	e24ab8db600b4210ce6a87ce89e9ef3d4b9ea1f9	[ "MIT" ]	150	2016-04-18T11:29:51.000Z	2021-11-25T20:10:20.000Z	_posts/2016-07-25-powershellbrasil.markdown	ProgramacaoPratica/listatelegram.github.io	e24ab8db600b4210ce6a87ce89e9ef3d4b9ea1f9	[ "MIT" ]	37	2016-05-17T17:55:30.000Z	2021-06-14T21:50:57.000Z	_posts/2016-07-25-powershellbrasil.markdown	ProgramacaoPratica/listatelegram.github.io	e24ab8db600b4210ce6a87ce89e9ef3d4b9ea1f9	[ "MIT" ]	231	2016-04-18T21:03:50.000Z	2021-08-05T21:02:03.000Z	--- layout: post title: "Powershell Brasil" categories: link-telegram: https://telegram.me/powershellbr --- Contribuição: Wanderlei Hüttel (@wanderleihuttel)	17.888889	49	0.757764	deu_Latn	0.112076
b7fe4aa1109178fa4deb7fd58f9202836aaba1bd	1,708	md	Markdown	packages/orbit-components/src/HorizontalScroll/README.md	mohofo7/orbit	ff63a3c38c39cdbcbf8aa06c8865f280141eb3ee	[ "MIT" ]	510	2020-09-05T03:33:17.000Z	2022-03-30T10:52:03.000Z	packages/orbit-components/src/HorizontalScroll/README.md	ninarazi/orbit	a8ef089ef53cb0c53f88a7b3e385249f8988903f	[ "MIT" ]	1,084	2020-08-25T22:14:54.000Z	2022-03-30T12:34:53.000Z	packages/orbit-components/src/HorizontalScroll/README.md	ninarazi/orbit	a8ef089ef53cb0c53f88a7b3e385249f8988903f	[ "MIT" ]	54	2020-09-06T12:40:38.000Z	2022-03-29T14:31:39.000Z	# HorizontalScroll To implement HorizontalScroll component into your project you'll need to add the import: ```jsx import HorizontalScroll from "@kiwicom/orbit-components/lib/HorizontalScroll"; ``` After adding import into your project you can use it simply like: ```jsx <HorizontalScroll> <FirstComponent /> <SecondComponent /> <ThirdComponent /> ...etc </HorizontalScroll> ``` ## Props \| Name \| Type \| Required \| Default \| Description \| \| ------------- \| --------------------------- \| ------------------ \| ------- \| ----------------------------------------- \| \| minHeight \| `number` \| \| \| set minimal height \| \| dataTest \| `string` \| \| \| prop for testing purposes \| \| spacing \| [`Spacing`](#Spacing) \| \| "small" \| the spacing between children elements \| \| children \| `React.ReactNode` \| :heavy_check_mark: \| \| content of HorizontalScroll \| \| scrollSnap \| [`ScrollSnap`](#ScrollSnap) \| \| "none" \| set value for `scroll-snap-type` property \| \| scrollPadding \| `number` \| \| \| set value for `scroll-padding` property \| # ScrollSnap \| ScrollSnap \| \| ------------- \| \| `"mandatory"` \| \| `"proximity"` \| \| `"inline"` \| \| `"none"` \| # Spacing \| Spacing \| \| ------------ \| \| `"none"` \| \| `"XXXSmall"` \| \| `"XXSmall"` \| \| `"XSmall"` \| \| `"small"` \| \| `"medium"` \| \| `"large"` \| \| `"XLarge"` \| \| `"XXLarge"` \|	32.226415	122	0.442623	eng_Latn	0.609954
b7fec8ee9291a44bab060d2c84fa7dcd027fb1f7	1,607	md	Markdown	_docs/debug.md	catataw/s2top	3364f3299d7808e63953a8e4c0d2e676ba2b2ad1	[ "MIT" ]	null	null	null	_docs/debug.md	catataw/s2top	3364f3299d7808e63953a8e4c0d2e676ba2b2ad1	[ "MIT" ]	null	null	null	_docs/debug.md	catataw/s2top	3364f3299d7808e63953a8e4c0d2e676ba2b2ad1	[ "MIT" ]	null	null	null	# Debug Mode `s2top` comes with a built-in logging facility and local socket server to simplify debugging at run time. ## Quick Start If running `s2top` via Docker, debug logging can be most easily enabled as below: ```bash docker run -ti --rm \ --name=s2top \ -e S2TOP_DEBUG=1 \ -e S2TOP_DEBUG_TCP=1 \ -p 9000:9000 \ -v /var/run/docker.sock:/var/run/docker.sock \ quay.io/vektorlab/s2top:latest ``` Log messages can be followed by connecting to the default listen address: ```bash curl -s localhost:9000 ``` example output: ``` 15:06:43.881 ▶ NOTI 002 logger initialized 15:06:43.881 ▶ INFO 003 loaded config param: "filterStr": "" 15:06:43.881 ▶ INFO 004 loaded config param: "sortField": "state" 15:06:43.881 ▶ INFO 005 loaded config switch: "sortReversed": false 15:06:43.881 ▶ INFO 006 loaded config switch: "allContainers": true 15:06:43.881 ▶ INFO 007 loaded config switch: "enableHeader": true 15:06:43.883 ▶ INFO 008 collector started for container: 7120f83ca... ... ``` ## Unix Socket Debug mode is enabled via the `S2TOP_DEBUG` environment variable: ```bash S2TOP_DEBUG=1 ./s2top ``` While `s2top` is running, you can connect to the logging socket via socat or similar tools: ```bash socat unix-connect:./s2top.sock stdio ``` ## TCP Logging Socket In lieu of using a local unix socket, TCP logging can be enabled via the `S2TOP_DEBUG_TCP` environment variable: ```bash S2TOP_DEBUG=1 S2TOP_DEBUG_TCP=1 ./s2top ``` A TCP listener for streaming log messages will be started on the default listen address(`0.0.0.0:9000`)	28.192982	112	0.703796	eng_Latn	0.878279
b7ff2604f9e4f7b9703d12462fae2cb5d0eb010b	5,863	md	Markdown	CloudFunctionsDemo/README.md	voidp34r/SEAL-Demo	eaf54def8ad8f1904f6d8f4aec288c0e59481a96	[ "MIT" ]	59	2019-05-07T12:56:02.000Z	2021-11-17T02:19:49.000Z	CloudFunctionsDemo/README.md	voidp34r/SEAL-Demo	eaf54def8ad8f1904f6d8f4aec288c0e59481a96	[ "MIT" ]	4	2020-03-06T10:18:54.000Z	2020-10-05T01:26:33.000Z	CloudFunctionsDemo/README.md	voidp34r/SEAL-Demo	eaf54def8ad8f1904f6d8f4aec288c0e59481a96	[ "MIT" ]	23	2019-06-23T15:59:08.000Z	2021-08-31T19:03:33.000Z	# Cloud Functions Demo This demo shows how to use Microsoft SEAL for .NET to perform homomorphic operations in Azure Functions. Azure Functions is a solution for easily running small pieces of code, or "functions", in the cloud. You can write just the code you need for the problem at hand, without worrying about a whole application or the infrastructure to run it. Functions can make development even more productive, and you can use your programming language of choice, such as C#, F#, Node.js, Java, or PHP. You pay only for the time your code runs and trust Azure to scale as needed. Azure Functions lets you develop serverless applications on Microsoft Azure. Learn more by [following this link](https://docs.microsoft.com/en-us/azure/azure-functions/functions-overview). The demonstration implements basic matrix operations: addition, subtraction, and multiplication. One of the projects (`CloudBasedFunctions/CloudBasedFunctions.sln`) implements these operations in Azure Functions, receiving as input a pair of ciphertexts. The other project (`ClientBasedFunctions/ClientBasedFunctions.sln`) provides a user interface that allows entering matrices, encrypting them, sending them to the cloud functions, receiving the result, decrypting the result, and finally showing it to the user. The user interface has an option to show the actual data that is being sent and received from the cloud functions. Matrix addition and subtraction is implemented by converting the matrices to vectors (using `BatchEncoder` class in Microsoft SEAL), and then performing element-wise operations in the resulting ciphertexts. Matrix multiplication is slightly more complicated and is explained in detail in [this file](ClientBasedFunctions/ClientBasedFunctions/MatrixProduct.md). ## Instructions for Cloud-Based Implementation ### Steps to configure project to run Azure Functions locally 1. [Download 64-bit Azure Functions Command Line Interface](https://github.com/Azure/azure-functions-core-tools/releases). 2. Install to known directory, for example: `D:\Progs\Azure.Functions.Cli.win-x64.2.3.199`. 3. Open CloudBasedFunctions solution. 4. Right click on CloudBasedFunctions project and select `Properties`. 5. Go to `Debug` tab in project properties. 6. In `Executable`, browse for `func.exe` on the 64-bit Azure Functions Command Line download, for example: `D:\Progs\Azure.Functions.Cli.win-x64.2.3.199\func.exe`. 7. In `Application arguments`, add: `host start`. 8. In `Working directory`, type `$(TargetDir)`. 9. Now you should be able to debug the CloudBasedFunctions project locally. ### Steps to configure project to run Azure Functions in Azure 1. Open CloudBasedFunctions solution. 2. Right click on CloudBasedFunctions project and select `Publish...`. 3. You will be asked to select a publish target, select Azure Function App. 4. After clicking `Publish` you might have to enter your Azure credentials. 5. Once the functions are published, go to the [Azure Portal](https://portal.azure.com). 6. Select `Function Apps`. 7. Select your newly published Function App. 8. Select `Platform features` tab. 9. Under `General Settings`, select `Application Settings`. 10. Change the `Platform` to 64 bit, save your changes. 11. After this change, Functions should be enabled and running. ## Instructions for Client-Based Implementation ### Steps to configure client project to connect to locally run Azure Functions 1. Open CloudBasedFunctions solution. 2. Start CloudBasedFnctions project, functions should run locally. A command window will appear and after some initialization the available Azure Functions will be printed, as well as the http address where they are available, for example: `http://localhost:7071/api/Addition`. 3. Open ClientBasedFunctions solution. 3. Start ClientBasedFunctions project. 4. The app window will appear. At the top there is a text box to specify the base address of the Azure Functions. To connect to the Azure Functions in step 2 above, for example, the textbox should contain: `http://localhost:7071`. ### Steps to configure client project to connect to Azure Functions in Azure 1. Please follow the instructions in the CloudBasedFunctions solution to deploy the functions to Azure.. 2. Go to [Azure Portal](https://portal.azure.com). 3. Select "Function Apps". 4. Select your Function App. 5. In the right part of the screen you will see the URL you need to use to access the Azure Functions, for example: `https://sealazurefuncdemoXXXX.azurewebsites.net`. 6. In the left part of the screen you will see a tree structure. The root node is your Function App, its first child node is `Functions`, and below this your will find the `Addition`, `Subtraction` and `Multiplication` functions. 7. For each function we need to obtain the function key needed to be able to call the API. When you select a function in the tree, the right part of the screen will show the contents of the `function.json` file that configures the function. At the top you will see a link called `</> Get function URL`. 8. Clicking `</> Get function URL` will show a dialog showing the complete URL needed to access the function. Make sure `default (Function key)` is selected in the combo box, and copy only the value of the function key. This is the text after `?code=`. 9. Open ClientBasedFunctions solution. 10. In the ClientBasedFunctions project, open the file `GlobalProperties.cs`. 11. Update the constants under `GlobalProperties.Codes` with the function keys from your Function App. 12. Run the ClientBasedFunctions project, and in the top textbox enter the URL from step 4, for example: `https://sealazurefuncdemoXXXX.azurewebsites.net`. 13. This will enable the client to connect to the Azure Functions running in Azure.	61.715789	165	0.775712	eng_Latn	0.991174
b7ffed448bb12addfd61d57ae78ce33847b5507a	2,836	md	Markdown	angular/components/readme.md	brandon93s/ui-framwork-comparison	cbac9888d28460373554f7e62a08242c0f89362c	[ "MIT" ]	null	null	null	angular/components/readme.md	brandon93s/ui-framwork-comparison	cbac9888d28460373554f7e62a08242c0f89362c	[ "MIT" ]	null	null	null	angular/components/readme.md	brandon93s/ui-framwork-comparison	cbac9888d28460373554f7e62a08242c0f89362c	[ "MIT" ]	null	null	null	# Full UI Frameworks ### Responsive Set of components + responsive layout system - [ng2-bootstrap](https://github.com/valor-software/ng2-bootstrap) - Native Angular directives for Bootstrap. - [@ng-bootstrap/ng-bootstrap](https://github.com/ng-bootstrap/ng-bootstrap) - Angular powered Bootstrap. - [ng-semantic](https://github.com/vladotesanovic/ngSemantic) - Angular 2 building blocks based on Semantic UI. - [angular2-materialize](https://github.com/InfomediaLtd/angular2-materialize) - Angular 2 support for Materialize CSS framework. - [ng2-semantic-ui](https://github.com/edcarroll/ng2-semantic-ui) - Semantic UI Angular 2 Integrations -- no JQuery required --. - [clarity-angular](https://github.com/vmware/clarity) - Clarity Design System: UX guidelines, HTML/CSS framework, and Angular 2 components working together to craft exceptional experiences. - [@covalent/core](https://github.com/teradata/covalent) - Teradata UI Platform built on Angular-Material 2.0. ### Component Collections Set of components without layout system - [@angular/material](https://github.com/angular/material2) - Official Material Design components for Angular. - [primeng](https://github.com/primefaces/primeng) - UI Components for Angular 2. - [ng-lightning](https://github.com/ng-lightning/ng-lightning) - Native Angular 2 components & directives for Lightning Design System. - [angular2-mdl](https://github.com/mseemann/angular2-mdl) - Angular 2 components, directives and styles based on material design lite. - [fuel-ui](https://github.com/FuelInteractive/fuel-ui) - UI Components for use with Angular2 and Bootstrap4. - [igniteui-angular2](https://github.com/IgniteUI/igniteui-angular2) - Ignite UI directives for Angular 2. - [md2](https://github.com/Promact/md2) - Angular2 based Material Design components, directives and services are Accordion, Autocomplete, Collapse, Colorpicker, Datepicker, Dialog(Modal), Menu, Multiselect, Select, Tabs, Tags(Chips), Toast and Tooltip. - [igniteui-js-blocks](https://github.com/IgniteUI/igniteui-js-blocks) - Mobile-first Angular native components. - [devextreme-angular](https://github.com/DevExpress/devextreme-angular) - Angular 2 UI and visualization components based on DevExtreme widgets. - [ng-zorro-antd](https://github.com/NG-ZORRO/ng-zorro-antd) - An enterprise-class UI components based on Ant Design and Angular. ### Mobile - [ionic2](https://github.com/driftyco/ionic) - Build amazing native and progressive web apps with Angular and open web technologies. One app running on everything. - [angular2-onsenui](https://github.com/onsenui/onsenui) - Mobile app development framework and SDK using HTML5 and JavaScript. Create beautiful and performant cross-platform mobile apps. Based on Web Components, and provides bindings for Angular 1, 2, React and Vue.js.	85.939394	271	0.771509	eng_Latn	0.557524
4d00208f11cb86b3f3761c0e518c413d02aace2c	7,667	md	Markdown	README.md	hayoung-kim/segmap	ceff035ba68df3afdd4faabeaf3febe1296a6eda	[ "BSD-3-Clause" ]	null	null	null	README.md	hayoung-kim/segmap	ceff035ba68df3afdd4faabeaf3febe1296a6eda	[ "BSD-3-Clause" ]	null	null	null	README.md	hayoung-kim/segmap	ceff035ba68df3afdd4faabeaf3febe1296a6eda	[ "BSD-3-Clause" ]	null	null	null	## SegMap SegMap is a map representation based on 3D segments allowing for robot localization, environment reconstruction, and semantics extraction. The SegMap code is open-source (BSD License) and has been tested under Ubuntu 14.04, 16.04 and ROS Indigo, Kinetic. Please remember that this is on-going research code which is subject to changes in the future. ### Related Publications R. Dubé, A. Cramariuc, D. Dugas, J. Nieto, R. Siegwart, and C. Cadena. "SegMap: 3D Segment Mapping using Data-Driven Descriptors." Robotics: Science and Systems (RSS), 2018. [pdf](http://www.roboticsproceedings.org/rss14/p03.pdf) - [video](https://youtu.be/CMk4w4eRobg) R. Dubé, MG. Gollub, H. Sommer, I. Gilitschenski, R. Siegwart, C. Cadena and , J. Nieto. "Incremental Segment-Based Localization in 3D Point Clouds." IEEE Robotics and Automation Letters, 2018. [pdf](http://n.ethz.ch/~cesarc/files/RAL2018_rdube.pdf) R. Dubé, D. Dugas, E. Stumm, J. Nieto, R. Siegwart, and C. Cadena. "SegMatch: Segment Based Place Recognition in 3D Point Clouds." IEEE International Conference on Robotics and Automation, 2017. [pdf](https://arxiv.org/pdf/1609.07720.pdf) - [video](https://youtu.be/iddCgYbgpjE) ## Features - 3D CNN encoder – decoder - ICP based LiDAR odometry - Dynamic voxel grid - Single and multi-robot SLAM back-end - Generic incremental region-growing segmentation - Incremental geometric verification ## Installation The SegMap repository contains the following modules: - segmap: The C++ library for 3D segment mapping. - segmap_ros: ROS interface for segmap. - segmapper: Example application using segmap and ros. - laser_slam: Backend for the example application, based on LiDAR sensor data. - segmappy: Python library for training and evaluating the neural network models. This section provides a step by step guide to installing the full flavor of SegMap. Advanced: it is also possible to use the SegMap C++ library standalone in a C++ project, or integrate the C++ library and ROS interface in a ROS project. ### Dependencies First install the required system packages: ``` $ sudo apt-get install python-wstool doxygen python3-pip python3-dev python-virtualenv dh-autoreconf ``` Set up the workspace configuration: ``` $ mkdir -p ~/segmap_ws/src $ cd ~/segmap_ws $ catkin init $ catkin config --merge-devel $ catkin config --cmake-args -DCMAKE_BUILD_TYPE=Release ``` Then use wstool for fetching catkin dependencies: ``` $ cd src $ git clone https://github.com/ethz-asl/segmap.git $ wstool init $ wstool merge segmap/dependencies.rosinstall $ wstool update ``` #### Tensorflow \| If you do not plan on using the deep learned descriptors in SegMap you should at least install the CPU version of Tensorflow to compile the whole package. Otherwise we recommend the GPU version. \| \| --- \| \| The precompiled version of Tensorflow can only be used with Ubuntu 14.04, for further explanations see [here](https://github.com/tradr-project/tensorflow_ros_cpp#c-abi-difference-problems) (requirements for the GPU version [here](https://www.tensorflow.org/install/install_sources#tested_source_configurations)). For Ubuntu 16.04 and 18.04 you must compile tensorflow from source. After compiling tensorflow, generate the pip package and continue with these instructions, installing the custom generated package instead of the precompiled one. \| \| --- \| SegMap relies on the package [tensorflow_ros_cpp](https://github.com/tradr-project/tensorflow_ros_cpp) for linking to the tensorflow C++ API. All our code has been tested with Tensorflow 1.8. ``` $ virtualenv ~/segmappyenv $ source ~/segmappyenv/bin/activate (segmappyenv)$ pip install --upgrade pip (segmappyenv)$ pip install catkin_pkg empy pyyaml (segmappyenv)$ pip install tensorflow-gpu==1.8.0 ``` ##### Build tensorflow_ros_cpp For more details on the optional compile flags or in case of issues compiling see the [FAQ](https://github.com/ethz-asl/segmap/wiki/FAQ#q-issues-compiling-tensorflow_ros_cpp). ``` $ cd ~/segmap_ws $ catkin build tensorflow_ros_cpp ``` ### Build SegMap Finally, build the segmapper package which will compile all dependencies and SegMap modules: ``` $ cd ~/segmap_ws $ catkin build segmapper ``` #### (Optional) Install SegmapPy python package Installing segmappy allows you to train data-driven models yourself to use with SegMap. ``` $ cd src/segmap/segmappy/ $ source ~/segmappyenv/bin/activate (segmappyenv)$ pip install . ``` ## Running segmapper Examples Make sure to source the SegMap workspace before running the segmapper demonstrations: ``` $ source ~/segmap_ws/devel/setup.bash ``` To train new models see intructions [here](https://github.com/ethz-asl/segmap/wiki/Training-new-models). #### Download demonstration files To download all necessary files, copy the content of the [segmap_data](http://robotics.ethz.ch/~asl-datasets/segmap/segmap_data/) into ```~/.segmap/```. If you installed the segmappy python package you can run the automated download script. Note: These models have been trained using Tensorflow 1.8 and are only guaranteed to work for that version. #### Run online SLAM example An online SLAM example can be run with ``` $ roslaunch segmapper kitti_loop_closure.launch ``` #### Run localization against known map example A localization example can be run with ``` $ roslaunch segmapper kitti_localization.launch ``` #### Run online SLAM with CNN example An online SLAM example with data-driven descriptor can be run with ``` $ roslaunch segmapper cnn_kitti_loop_closure.launch ``` You can now visualize the reconstructed target map in rviz by subscribing to `/segmatch/target_reconstruction`. More details on the demonstrations can be found [here](https://github.com/ethz-asl/segmap/blob/master/wiki/demonstrations.md). ## License SegMap is released under [BSD 3-Clause License](https://github.com/ethz-asl/segmap/blob/master/LICENSE) Thank you for citing the related publication if you use SegMap in academic work: ``` @inproceedings{segmap2018, title={{SegMap}: 3D Segment Mapping using Data-Driven Descriptors}, author={Dub{\'e}, Renaud and Cramariuc, Andrei and Dugas, Daniel and Nieto, Juan and Siegwart, Roland and Cadena, Cesar}, booktitle={Robotics: Science and Systems (RSS)}, year={2018} } ``` ``` @inproceedings{segmatch2017, title={SegMatch: Segment based place recognition in 3d point clouds}, author={Dub{\'e}, Renaud and Dugas, Daniel and Stumm, Elena and Nieto, Juan and Siegwart, Roland and Cadena, Cesar}, booktitle={IEEE International Conference on Robotics and Automation (ICRA)}, pages={5266--5272}, year={2017}, organization={IEEE} } ``` If you use the incremental version for the segmentation or geometric verification algorithms (used in the provided configuration files), please consider citing the describing paper: ``` @article{incremental2018, title={Incremental Segment-Based Localization in {3D} Point Clouds}, author={Dub{\'e}, Renaud and Gollub, Mattia G and Sommer, Hannes and Gilitschenski, Igor and Siegwart, Roland and Cadena, Cesar and Nieto, Juan}, journal={IEEE Robotics and Automation Letters}, volume={3}, number={3}, pages={1832--1839}, year={2018}, publisher={IEEE} } ``` ## Contributing to SegMap We would be very grateful if you would contribute to the code base by reporting bugs, leaving comments and proposing new features through issues and pull requests. Please see the dedicated [wiki page](https://github.com/ethz-asl/segmap/wiki/Contributing-to-SegMap) on this topic and feel free to get in touch at renaud.dube(at)sevensense(dot)ch, dugasd(at)ethz(dot)ch and crandrei(at)ethz(dot)ch. Thank you!	42.126374	547	0.761315	eng_Latn	0.913628
4d0048aaa737b4b6d903decda869e6e00ad8d7d5	193	md	Markdown	docs/clova-extension-core/com.linecorp.clova.extension.model.directive/-directive-name/-init-.md	uich/clova-cek-sdk-kotlin	59cef6d2f803a5ac410caae9682bafc987387aee	[ "Apache-2.0" ]	4	2018-07-27T05:38:22.000Z	2018-12-11T10:21:16.000Z	docs/clova-extension-core/com.linecorp.clova.extension.model.directive/-directive-name/-init-.md	uich/clova-cek-sdk-kotlin	59cef6d2f803a5ac410caae9682bafc987387aee	[ "Apache-2.0" ]	3	2018-07-27T07:57:35.000Z	2019-03-15T05:25:54.000Z	docs/clova-extension-core/com.linecorp.clova.extension.model.directive/-directive-name/-init-.md	uich/clova-cek-sdk-kotlin	59cef6d2f803a5ac410caae9682bafc987387aee	[ "Apache-2.0" ]	3	2018-08-29T05:14:19.000Z	2019-03-15T04:50:49.000Z	[clova-extension-core](../../index.md) / [com.linecorp.clova.extension.model.directive](../index.md) / [DirectiveName](index.md) / [<init>](./-init-.md) # <init> `DirectiveName()`	38.6	158	0.65285	yue_Hant	0.473931
4d005b0c72b4c81a1aee51e8702e2474a306114a	1,832	md	Markdown	articles/communication-services/quickstarts/meeting/samples-for-teams-embed.md	otrekw/azure-docs.de-de	60cf2ae78d532fc77e09432defdad8443a57019a	[ "CC-BY-4.0", "MIT" ]	null	null	null	articles/communication-services/quickstarts/meeting/samples-for-teams-embed.md	otrekw/azure-docs.de-de	60cf2ae78d532fc77e09432defdad8443a57019a	[ "CC-BY-4.0", "MIT" ]	null	null	null	articles/communication-services/quickstarts/meeting/samples-for-teams-embed.md	otrekw/azure-docs.de-de	60cf2ae78d532fc77e09432defdad8443a57019a	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- title: Verwenden der Azure Communication Services-Bibliothek zum Einbetten von Teams description: Hier erfahren Sie mehr über die Funktionen der Communication Services-Bibliothek zum Einbetten von Teams. author: palatter ms.author: palatter ms.date: 06/30/2021 ms.topic: conceptual ms.service: azure-communication-services zone_pivot_groups: acs-plat-ios-android ms.openlocfilehash: d5ddb8589343bca55554ad71327b6adfd0202976 ms.sourcegitcommit: 98308c4b775a049a4a035ccf60c8b163f86f04ca ms.translationtype: HT ms.contentlocale: de-DE ms.lasthandoff: 06/30/2021 ms.locfileid: "113215124" --- # <a name="use-the-communication-services-teams-embed-library"></a>Verwenden der Communication Services-Bibliothek zum Einbetten von Teams [!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)] Steigen Sie in Azure Communication Services ein, indem Sie mithilfe der Communication Services-Bibliothek zum Einbetten von Teams Ihrer App Teams-Besprechungen hinzufügen. ::: zone pivot="platform-android" [!INCLUDE [Meetings with Android](./includes/samples-android.md)] ::: zone-end ::: zone pivot="platform-ios" [!INCLUDE [Meetings with iOS](./includes/samples-ios.md)] ::: zone-end ## <a name="clean-up-resources"></a>Bereinigen von Ressourcen Wenn Sie ein Communication Services-Abonnement bereinigen und entfernen möchten, können Sie die Ressource oder die Ressourcengruppe löschen. Wenn Sie die Ressourcengruppe löschen, werden auch alle anderen Ressourcen gelöscht, die ihr zugeordnet sind. Weitere Informationen zum Bereinigen von Ressourcen finden Sie [hier](../create-communication-resource.md#clean-up-resources). ## <a name="next-steps"></a>Nächste Schritte Weitere Informationen finden Sie in den folgenden Artikeln: - [Erste Schritte zum Einbetten von Teams](./getting-started-with-teams-embed.md)	45.8	377	0.801856	deu_Latn	0.777586
4d00870bf3b3e672f937739f3c554c2cfdc2597a	5,316	md	Markdown	docs/analytics-platform-system/configure-an-external-smp-sql-server-to-receive-remote-table-copies.md	in4matica/sql-docs.de-de	b5a6c26b66f347686c4943dc8307b3b1deedbe7e	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/analytics-platform-system/configure-an-external-smp-sql-server-to-receive-remote-table-copies.md	in4matica/sql-docs.de-de	b5a6c26b66f347686c4943dc8307b3b1deedbe7e	[ "CC-BY-4.0", "MIT" ]	null	null	null	docs/analytics-platform-system/configure-an-external-smp-sql-server-to-receive-remote-table-copies.md	in4matica/sql-docs.de-de	b5a6c26b66f347686c4943dc8307b3b1deedbe7e	[ "CC-BY-4.0", "MIT" ]	null	null	null	--- title: Konfigurieren von SQL Server für den Empfang von Remote Tabellen Kopien description: Beschreibt, wie eine externe SMP-SQL Server-Instanz konfiguriert wird, um Remote Tabellen Kopien von parallelen Data Warehouse zu empfangen. author: mzaman1 ms.prod: sql ms.technology: data-warehouse ms.topic: conceptual ms.date: 04/17/2018 ms.author: murshedz ms.reviewer: martinle ms.custom: seo-dt-2019 ms.openlocfilehash: 3e5475e86582ede2e6fa7ca5a302bba7ee74faa3 ms.sourcegitcommit: b87d36c46b39af8b929ad94ec707dee8800950f5 ms.translationtype: MT ms.contentlocale: de-DE ms.lasthandoff: 02/08/2020 ms.locfileid: "74401326" --- # <a name="configure-an-external-smp-sql-server-to-receive-remote-table-copies---parallel-data-warehouse"></a>Konfigurieren eines externen SMP-SQL Server zum Empfangen von Remote Tabellen Kopien-parallel Data Warehouse Beschreibt, wie eine externe SQL Server Instanz so konfiguriert wird, dass Remote Tabellen Kopien von parallelen Data Warehouse empfangen werden. In diesem Thema wird einer der Konfigurationsschritte zum Konfigurieren der Remote Tabellen Kopie beschrieben. Eine Liste aller Konfigurationsschritte finden Sie unter Kopieren von [Remote Tabellen](remote-table-copy.md). ## <a name="before-you-begin"></a>Vorbereitungen Bevor Sie die externe SQL Server konfigurieren können, müssen Sie folgende Schritte ausführen: - Sie müssen über ein Windows-System mit SQL Server 2008 Enterprise Edition oder einer neueren Version verfügen, die installiert oder bereits installiert ist. Das Windows-System muss bereits gemäß den Anweisungen in [Konfigurieren eines externen Windows-Systems zum Empfangen von Remote Tabellen Kopien mithilfe von InfiniBand](configure-an-external-windows-system-to-receive-remote-table-copies-using-infiniband.md)konfiguriert werden. - Ein Windows-Administrator Konto mit der Möglichkeit, die SQL Server Instanz und das Windows-System zu konfigurieren. - Ein SQL Server-Anmelde Konto (wenn SQL Server bereits installiert ist) mit der Möglichkeit, Anmeldungen zu erstellen und Berechtigungen für die Zieldatenbank (en) zu erteilen. ## <a name="HowToSQLServer"></a>Konfigurieren eines externen SMP-SQL Server zum Empfangen von Remote Tabellen Kopien Das Feature "Remote Tabellen Kopie" kopiert Tabellen aus der SQL Server PDW Appliance in eine externe SMP-SQL Server Datenbank, die auf einem Windows-System ausgeführt wird. Nachdem Sie das externe Windows-System für das Empfangen von Remote Tabellen Kopien konfiguriert haben, besteht der nächste Schritt darin, SQL Server auf dem Windows-System zu installieren und zu konfigurieren. Führen Sie die folgenden Schritte aus, um SQL Server zu konfigurieren: 1. Installieren Sie SQL Server 2008 Enterprise Edition oder eine höhere Version auf dem Windows-System. Dies wird als SMP-SQL Server bezeichnet. 2. Konfigurieren Sie SQL Server, um TCP/IP-Verbindungen an einem TCP-Port zu akzeptieren. Diese Konfiguration ist standardmäßig deaktiviert und muss aktiviert werden, damit SQL Server PDW eine Verbindung mit der SMP-SQL Server herstellen kann. 3. Deaktivieren Sie die Windows-Firewall, oder konfigurieren Sie den SMP-SQL Server TCP-Port so, dass er mit aktivierter Windows-Firewall funktioniert. 4. Konfigurieren Sie SQL Server, um SQL Server Authentifizierungsmodus zuzulassen. Der parallele Datenexport verwendet immer SQL Server Konten für die Authentifizierung. 5. Bestimmen Sie ein SQL Server Konto auf dem SMP-SQL Server, das für die Authentifizierung verwendet wird. Erteilen Sie diesem Konto die Berechtigung zum Erstellen, löschen und Einfügen von Daten in Tabellen in der Zieldatenbank für den parallelen Datenexport Vorgang. ## <a name="BPSQLConfig"></a>Bewährte Methoden für die Konfiguration von SMP-SQL Server für die Remote Tabellen Kopie Verwenden Sie beim Konfigurieren der SMP-SQL Server für den Empfang von Remote Tabellen Kopien die folgenden bewährten Methoden, um die Leistung zu verbessern. 1. Befolgen Sie die bewährten Methoden, wie in SQL Server Produktdokumentation dokumentiert. Aktivieren Sie z. b. die Datenverschlüsselung. Weitere Informationen zum Sichern von SQL Server finden Sie unter [Sichern von SQL Server](../relational-databases/security/securing-sql-server.md) auf MSDN. 2. Verwenden Sie das Massen protokollierte oder einfache Wiederherstellungs Modell. Während der parallelen Datenexport Vorgänge werden Daten in die neu erstellte Ziel Tabelle Massen eingefügt. Legen Sie für die maximale Leistung während der Massen Einfügung fest, dass die Zieldatenbank das Massen protokollierte oder das einfache Wiederherstellungs Modell verwendet. 3. Verwenden Sie die Option batch_size, um Protokoll Speicher freizugeben. Obwohl bei den Massen protokollierten oder einfachen Wiederherstellungs Modellen die minimale Protokollierung für die Massen eingefügten Daten verwendet wird, erfolgt immer noch eine Protokollierung. Um zu verhindern, dass die Protokolldateien zu groß werden, verwenden Sie die Option SQL Server batch_size, um in regelmäßigen Abständen Protokoll Speicher freizugeben. <!-- MISSING LINKS ## See Also [Common Metadata Query Examples (SQL Server PDW)](../sqlpdw/common-metadata-query-examples-sql-server-pdw.md) -->	80.545455	440	0.80681	deu_Latn	0.994104
4d01282da70d52e4e9e4bf9e0d1d7b96334d7644	4,723	md	Markdown	README.md	nanostores/vue	356cec6fc195970e65d44ae364d7ea22ee6ea133	[ "MIT" ]	17	2021-10-14T17:06:16.000Z	2021-12-06T10:34:00.000Z	README.md	nanostores/vue	356cec6fc195970e65d44ae364d7ea22ee6ea133	[ "MIT" ]	4	2021-10-14T20:20:41.000Z	2021-12-07T11:55:16.000Z	README.md	nanostores/vue	356cec6fc195970e65d44ae364d7ea22ee6ea133	[ "MIT" ]	5	2021-11-25T01:40:39.000Z	2022-02-08T20:00:03.000Z	# Nano Stores Vue <img align="right" width="92" height="92" title="Nano Stores logo" src="https://nanostores.github.io/nanostores/logo.svg"> Vue integration for [Nano Stores], a tiny state manager with many atomic tree-shakable stores. * Small. Less than 1 KB with all helpers. Zero dependencies. * Fast. With small atomic and derived stores, you do not need to call the selector function for all components on every store change. * Tree Shakable. The chunk contains only stores used by components in the chunk. * Helpers. Designed to keep code clean and save a few keystrokes. * Devtools. Plugin with full support of [Vue Devtools]. * Was designed to move logic from components to stores. * It has good TypeScript support. ## Install ```sh npm install @nanostores/vue ``` ## Usage ### Store state Subscribe to store changes and use reactive store state. ```vue <template> <header>{{ post.title }} for {{ user.name }}</header> </template> <script> import { useStore } from '@nanostores/vue' import { profile } from '../stores/profile.js' import { Post } from '../stores/post.js' export default { setup (props) { const user = useStore(profile) const post = useStore(Post(props.postId)) return { user, post } } } </script> ``` ### Multiple store states Generate multiple store states and save a few keystrokes. ```vue <template> <header>{{ project.name }} / {{ user.name }}</header> </template> <script> import { mapStores } from '@nanostores/vue' import { project } from '../stores/project.js' import { user } from '../stores/user.js' export default { setup () { return { ...mapStores({ project, user }) } } } </script> ``` ### Form handling Since the store state is deep read-only, you cannot directly mutate it. But for `v-model` you can create model via `useVModel(store, keys, opts)`. It will explicitly mutate the store via `store.set()` / `store.setKey()`. ```vue <template> <input v-model="username"/> </template> <script> import { useVModel } from '@nanostores/vue' import { profile } from '../stores/profile.js' export default { setup () { const username = useVModel(profile, 'username') return { username } } } </script> ``` The `keys` argument can be an array of keys to create multiple models. Each model will be prefixed with `Model`. You can change it via `opts.prefix`. ```vue <template> <input v-model="firstNameModel"/> <input v-model="lastNameModel"/> </template> <script> import { useVModel } from '@nanostores/vue' import { profile } from '../stores/profile.js' export default { setup () { return { ...useVModel(profile, ['firstName', 'lastName']) } } } </script> ``` ## Devtools <p align="center"> <img src="img/screenshot.jpg" alt="Nanostores Vue Devtools screenshot" width="830"> </p> ### Install ```sh npm install --save-dev @vue/devtools-api ``` ### Usage #### Store detector Install [Vue Devtools] plugin as usual. It will detect nanostores in selected component and add their states to the component inspector. ```js import { createApp } from 'vue' import { devtools } from '@nanostores/vue/devtools' import { User } from '../stores/user.js' const app = createApp(…) app.use(devtools) ``` > Notice: if you are using SSR, there is no Vue Devtools on server. > Check it’s a browser environment: > ```js > if (window) app.use(devtools) > ``` Attach stores to add them to the nanostores inspector and see their builds, lifecycles and changes on the timeline. ```js import { createApp } from 'vue' import { devtools, attachStores } from '@nanostores/vue/devtools' import { User } from '../stores/user.js' const app = createApp(…) app.use(devtools) attachStores(app, { User }) ``` You can connect several stores in different places of your application and set custom names to simplify the work with devtools. ```js attachStores(app, { 'Current User': User, Post }) ``` For `MapTemplate` you can create a custom `nameGetter` to set suitable names for each store built from template. ```js attachStores(app, { User }, { nameGetter: (store, templateName) => { return `User:${store.get().id}` } }) ``` ### Settings The states of all detected stores in component inspector are updated in real time. You can disable this in the the plugin settings via the Real-time update detected property. By default, we removes unmounted stores from nanostores inspector to keep it clean. You can change this via the Keep unmounted property. [Nano Stores]: https://github.com/nanostores/nanostores/ [Vue Devtools]: https://devtools.vuejs.org	23.151961	85	0.676265	eng_Latn	0.914046
4d012efd67b3dc988e84090c8b087834e0580bc9	5,959	md	Markdown	tensorflow/lite/g3doc/guide/reduce_binary_size.md	EricLi404/tensorflow	23759800d89f7b5362c338d9a3fd72a6810c3e22	[ "Apache-2.0" ]	74	2020-07-06T17:11:39.000Z	2022-01-28T06:31:28.000Z	tensorflow/lite/g3doc/guide/reduce_binary_size.md	sseung0703/tensorflow	be084bd7a4dd241eb781fc704f57bcacc5c9b6dd	[ "Apache-2.0" ]	9	2020-10-13T23:25:29.000Z	2022-02-10T06:54:48.000Z	tensorflow/lite/g3doc/guide/reduce_binary_size.md	sseung0703/tensorflow	be084bd7a4dd241eb781fc704f57bcacc5c9b6dd	[ "Apache-2.0" ]	12	2020-07-08T07:27:17.000Z	2021-12-27T08:54:27.000Z	# Reduce TensorFlow Lite binary size ## Overview When deploying models for on-device machine learning (ODML) applications, it is important to be aware of the limited memory that is available on mobile devices. Model binary sizes are closely correlated to the number of ops used in the model. TensorFlow Lite enables you to reduce model binary sizes by using selective builds. Selective builds skip unused operations in your model set and produce a compact library with just the runtime and the op kernels required for the model to run on your mobile device. Selective build applies on the following three operations libraries. 1. [TensorFlow Lite built-in ops library](https://www.tensorflow.org/lite/guide/ops_compatibility) 1. [TensorFlow Lite custom ops](https://www.tensorflow.org/lite/guide/ops_custom) 1. [Select TensorFlow ops library](https://www.tensorflow.org/lite/guide/ops_select) The table below demonstrates the impact of selective builds for some common use cases: <table> <thead> <tr> <th>Model Name</th> <th>Domain</th> <th>Target architecture</th> <th>AAR file size(s)</th> </tr> </thead> <tr> <td rowspan = 2> <a href="https://storage.googleapis.com/download.tensorflow.org/models/mobilenet_v1_2018_08_02/mobilenet_v1_1.0_224.tgz">Mobilenet_1.0_224(float)</a> </td> <td rowspan = 2>Image classification</td> <td>armeabi-v7a</td> <td>tensorflow-lite.aar (296,635 bytes)</td> </tr> <tr> <td>arm64-v8a</td> <td>tensorflow-lite.aar (382,892 bytes)</td> </tr> <tr> <td rowspan = 2> <a href="https://tfhub.dev/google/lite-model/spice/">SPICE</a> </td> <td rowspan = 2>Sound pitch extraction</td> <td>armeabi-v7a</td> <td>tensorflow-lite.aar (375,813 bytes)<br />tensorflow-lite-select-tf-ops.aar (1,676,380 bytes)</td> </tr> <tr> <td>arm64-v8a</td> <td>tensorflow-lite.aar (421,826 bytes)<br />tensorflow-lite-select-tf-ops.aar (2,298,630 bytes)</td> </tr> <tr> <td rowspan = 2> <a href="https://tfhub.dev/deepmind/i3d-kinetics-400/1">i3d-kinetics-400</a> </td> <td rowspan = 2>Video classification</td> <td>armeabi-v7a</td> <td>tensorflow-lite.aar (240,085 bytes)<br />tensorflow-lite-select-tf-ops.aar (1,708,597 bytes)</td> </tr> <tr> <td>arm64-v8a</td> <td>tensorflow-lite.aar (273,713 bytes)<br />tensorflow-lite-select-tf-ops.aar (2,339,697 bytes)</td> </tr> </table> Note: This feature is currently experimental and available since version 2.4 and may change. ## Known issues/limitations 1. Selective Build for C API and iOS version is not supported currently. ## Selectively build TensorFlow Lite with Bazel This section assumes that you have downloaded TensorFlow source codes and [set up the local development environment](https://www.tensorflow.org/lite/guide/android#build_tensorflow_lite_locally) to Bazel. ### Build AAR files for Android project You can build the custom TensorFlow Lite AARs by providing your model file paths as follows. ```sh sh tensorflow/lite/tools/build_aar.sh \ --input_models=/a/b/model_one.tflite,/c/d/model_two.tflite \ --target_archs=x86,x86_64,arm64-v8a,armeabi-v7a ``` The above command will generate the AAR file `bazel-bin/tmp/tensorflow-lite.aar` for TensorFlow Lite built-in and custom ops; and optionally, generates the aar file `bazel-bin/tmp/tensorflow-lite-select-tf-ops.aar` if your models contain Select TensorFlow ops. Note that this builds a "fat" AAR with several different architectures; if you don't need all of them, use the subset appropriate for your deployment environment. ### Advanced Usage: Build with custom ops If you have developed Tensorflow Lite models with custom ops, you can build them by adding the following flags to the build command: ```sh sh tensorflow/lite/tools/build_aar.sh \ --input_models=/a/b/model_one.tflite,/c/d/model_two.tflite \ --target_archs=x86,x86_64,arm64-v8a,armeabi-v7a \ --tflite_custom_ops_srcs=/e/f/file1.cc,/g/h/file2.h \ --tflite_custom_ops_deps=dep1,dep2 ``` The `tflite_custom_ops_srcs` flag contains source files of your custom ops and the `tflite_custom_ops_deps` flag contains dependencies to build those source files. Note that these dependencies must exist in the TensorFlow repo. ## Selectively Build TensorFlow Lite with Docker This section assumes that you have installed [Docker](https://docs.docker.com/get-docker/) on your local machine and [built the TensorFlow Lite docker file](https://www.tensorflow.org/lite/guide/android#set_up_build_environment_using_docker). ### Build AAR files for Android project Download the script for building with Docker by running: ```sh curl -o build_aar_with_docker.sh \ https://raw.githubusercontent.com/tensorflow/tensorflow/master/tensorflow/lite/tools/build_aar_with_docker.sh && chmod +x build_aar_with_docker.sh ``` Then, you can build the custom TensorFlow Lite AAR by providing your model file paths as follows. ```sh sh build_aar_with_docker.sh \ --input_models=/a/b/model_one.tflite,/c/d/model_two.tflite \ --target_archs=x86,x86_64,arm64-v8a,armeabi-v7a \ --checkpoint=master ``` The `checkpoint` flag is a commit, a branch or a tag of the TensorFlow repo that you want to checkout before building the libraries. The above command will generate the AAR file `tensorflow-lite.aar` for TensorFlow Lite built-in and custom ops and optionally the AAR file `tensorflow-lite-select-tf-ops.aar` for Select TensorFlow ops in your current directory. ## Add AAR files to project Add AAR files by directly [importing the AAR into your project](https://www.tensorflow.org/lite/guide/android#add_aar_directly_to_project), or by [publishing the custom AAR to your local Maven repository](https://www.tensorflow.org/lite/guide/android#install_aar_to_local_maven_repository). Note that you have to add the AAR files for `tensorflow-lite-select-tf-ops.aar` as well if you generate it.	37.955414	155	0.747944	eng_Latn	0.888846
4d016d13c8a483eb62668eae7ee224f794a17c3d	1,289	md	Markdown	content/user-guide/rules/selector-no-vendor-prefix.md	cslint/stylelint.cn	8efd492958092b1b209ab96c5997940e13bca733	[ "MIT" ]	null	null	null	content/user-guide/rules/selector-no-vendor-prefix.md	cslint/stylelint.cn	8efd492958092b1b209ab96c5997940e13bca733	[ "MIT" ]	null	null	null	content/user-guide/rules/selector-no-vendor-prefix.md	cslint/stylelint.cn	8efd492958092b1b209ab96c5997940e13bca733	[ "MIT" ]	1	2021-09-27T07:25:46.000Z	2021-09-27T07:25:46.000Z	# selector-no-vendor-prefix Disallow vendor prefixes for selectors. 禁止使用浏览器引擎前缀。 ```css input::-moz-placeholder {} /** ↑ * These prefixes / ``` This rule does not blanketly condemn vendor prefixes. Instead, it uses [Autoprefixer's](https://github.com/postcss/autoprefixer) up-to-date data (from [caniuse.com](http://caniuse.com/)) to know whether a vendor prefix should cause a warning or not. If you've included a vendor prefixed selector that has a standard alternative, one that Autoprefixer could take care of for you, this rule will warn about it. If, however, you use a non-standard vendor-prefixed selector, one that Autoprefixer would ignore and could not provide, this rule will ignore it. 该规则并不全面否定浏览器引擎前缀。相反，它使用 [Autoprefixer's](https://github.com/postcss/autoprefixer) 更新最新数据(从 [caniuse.com](http://caniuse.com/))来查看一个浏览器引擎前缀是否会引起警告。如果你使用了一个标准的浏览器引擎前缀，Autoprefixer 将会为你处理，该规则将发出警告，然而，如果你使用了一个非标准的浏览器引擎前缀，Autoprefixer 会忽略它，无法提供处理 (比如 `-webkit-touch-callout`)，该规则将忽略这个属性。 ## Options ### `true` The following patterns are considered warnings: 以下模式被认为是个警告： ```css input::-moz-placeholder {} ``` ```css :-webkit-full-screen a {} ``` The following patterns are not* considered warnings: 以下模式正常： ```css input::placeholder {} ``` ```css :full-screen a {} ```	29.295455	556	0.747091	eng_Latn	0.901701

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.