[Home] [By Thread] [By Date] [Recent Entries]
On 15/01/07, Tei <oscar.vives@g...> wrote: > safe: > - protected from nake eye inspection of actual data HTTP move > - validate server identity, that can serve to avoid phising or DNS spoofing. > - protected content from malware javascript/html inyection > - validate client identity? (not idea about this, but I think is posible) > - cypher is strong against brute force > - cypher strong against password distribution problem (PKI dont need > that ...much) > > Other than that. Again. Maybe was not soo a good idea, cause people > want fast porn. Not safe or private porn. Wait... bad analogy. You hit one problem -- HTTPS significantly increases the server load (by several times). The other, more serious problem is that HTTPS makes web resources uncacheable. All the best, David
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |

Cart



