- ソース を表示
- sl_cache (E)/Security へ行く。
現: 2008-12-21 (日) 03:29:18 gambled  |
|||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ** sl_cache [#l20d170b] | ||
| + | -Access to [[sl_relay>sl_relay (E)]] can be done on a per machine basis through an access list. | ||
| + | ** Control Process (Cache GET Process)[#c29fd19d] | ||
| + | -The communication port for [[sl_relay>sl_relay (E)]] is selected at random by negotiation. | ||
| + | -When the same host doesn't have both [[sl_relay>sl_relay (E)]] and [[sl_cache>sl_cache (E)]], the negotiation and subsequent data communication might be tapped. | ||
| + | -If the negotiation or subsequent data communication is tapped, there is a possibility for the terminate command to be sent forcing a shutdown. | ||
| + | |||
| + | ** Cache PUT Server [#j422416a] | ||
| + | - The Cache PUT Server disregards packets not coming from localhost. | ||
| + | |||
| + | ** Relay Process to Cache PUT Server [#e8b44bb1] | ||
| + | -The port and the connection password are decided by negotiation with [[sl_relay>sl_relay (E)]]. | ||
| + | -The connection password is not used too strictly (it is possible to tap it). This is an advanced trial of a feature for a future version. | ||
| + | -Only data from the IP address and port number determined during negotiation is relayed to the Cache PUT Server. | ||
| + | -If the negotiation or subsequent data communication is tapped it is possible that false texture data might be transmitted by the Relay Process. | ||
- sl_cache (E)/Security のバックアップ差分(No. All)
- 現: 2008-12-21 (日) 03:29:18 gambled
