I assume it's pretty much as (in)secure as any other QtWebKit-based browser.
Quote from: Frenzie on 2014-08-07, 11:58:09I assume it's pretty much as (in)secure as any other QtWebKit-based browser.Cookie settings, referrer settings, and proxy settings can make quite a difference.
Quote from: ersi on 2014-08-07, 12:25:53Quote from: Frenzie on 2014-08-07, 11:58:09I assume it's pretty much as (in)secure as any other QtWebKit-based browser.Cookie settings, referrer settings, and proxy settings can make quite a difference.The above settings are privacy and not security related.
What is the difference between privacy and security then? SSL? HTTPS?
What is the difference between privacy and security then?
I guess you are saying that when the engine is chosen, then everything security-related is settled and cannot be improved. Only privacy things can, right?
Quote from: ersi on 2014-08-07, 18:41:47What is the difference between privacy and security then? That's something you could find out by yourself In the meanwhile you could also ask yourself why to use different notions if they are the same thing.
Quote from: ersi on 2014-08-07, 18:41:47SSL? HTTPS? Encryption (SSL) is security related while HTTPS is the name of the protocol.
What I'm trying to say is that developing and maintaining a browser is costly and needs qualified manpower. Enthusiasm alone doesn't suffice. That's why we are left with only very few browsers and dozens of their deviants inheriting their shortcomings and security holes.
I know what they are (a little). The question is which one is security, which one is privacy, and why.
If your bank PIN and PW would be transmitted in plain text and the traffic sniffed then you could encounter some problems.
Encryption of emails or any other data on your HD is also security related.
Google (and other search engines) are advertising a secure connection for protecting your privacy - your searches are private, nobody knows what you are searching for
Is it the browser that determines if plain text is transmitted or is it the bank website's job to have control over what's being typed in there?
This is what I mean. "Security" and "privacy" are used so often together that it's certain that even experts don't keep them apart very well. "Security and privacy" sound to me like "terms and conditions" (which ones are the terms and which ones are the conditions?) or "preferences, options, and configuration".
The sender (me) encrypts the message, sends the encrypted message, and the receiver decrypts it. Who encrypts at what stage in browsers?
What I have heard about browsers is things like leaking history and leaking address bar. These sound like things that a browser developer could manage, regardless of browser engine.
Page created in 0.063 seconds with 39 queries.