0 Members and 1 Guest are viewing this topic.
One morning I was called to the emergency room by the head ER nurse. She directed me to a patient who had refused to describe his problem other than to say "he needed a doctor who took care of men's troubles" ... the patient permitted me to remove his trousers, shorts, and two or three yards of foul-smelling stained gauze wrapped about his scrotum, which was swollen to twice the size of a grapefruit and extremely tender.... amid the matted hair, edematous skin, and various exudates, I saw some half-buried dark linear objects and asked the patient what they were. Several days earlier, he replied, he had injured himself in the machine shop where he worked, and had closed the laceration himself with a heavy-duty stapling gun ... eight rusty staples were retrieved.
RD - what's the difference between the https secure wikipedia and the normal one? Would it be advisable to use the secure one in day to day usage?
Strictly speaking, HTTPS is not a separate protocol, but refers to use of ordinary HTTP over an encrypted Secure Sockets Layer (SSL) or Transport Layer Security (TLS) connection.Everything in the HTTP message is encrypted, including the headers, and the request/response load.
Q. When does HTTPS Everywhere protect me? When does it not protect me? A. HTTPS Everywhere protects you only when you are using encrypted portions of supported web sites. On a supported site, it will automatically activate HTTPS encryption for all known supported parts of the site (for some sites, this might be only a portion of the entire site). For example, if your web mail provider does not support HTTPS at all, HTTPS Everywhere can't make your access to your web mail secure. Similarly, if a site (like Wikipedia) allows HTTPS for text but not images, someone might be able to see which images your browser loads and guess what you're accessing
thanks - my chrome installations are crashing regularly at present so it might be time to go back to firefox.
... might try to be more secure as well!
Communicating via HTTP is like sending a postcard written in pencil: anyone can read or modify the text.