Google Chrome may (or may not) be more secure than other browsers in the long run. There's a lot of promise in its multiprocessor model, for instance. On the other hand, it's so new and untested that it just shouldn't be trusted as much as you may trust many other browsers yet.
Come to think of it, you probably shouldn't trust your other browsers as much asyou do, either.
Discussion on:
View:
Show:
"Come to think of it, you probably shouldn't
trust your other browsers as much asyou do,
either."
It pays to always be on your toes. But
thanks for the heads up on a couple of issues
I hadn't known about.
trust your other browsers as much asyou do,
either."
It pays to always be on your toes. But
thanks for the heads up on a couple of issues
I hadn't known about.
and secure your connection and what your
browser / system can be exposed to (by proxy
and filter) and just a 'little less' about
the browser security, no?
browser / system can be exposed to (by proxy
and filter) and just a 'little less' about
the browser security, no?
a fork of KHTML according to webkit.org.
the KDE project is pretty good about security issues, in that they do work on keeping them to a minimum, so webkit started out with a solid base.
the KDE project is pretty good about security issues, in that they do work on keeping them to a minimum, so webkit started out with a solid base.
Yes, WebKit forked from KHTML. In my (limited) experience, with KHTML, WebKit is better -- at least in terms of rendering capabilities.
have a webkit browser to test it, webkit doesn't build on linux.
[ really silly of them ]
I know that KHTML works, though I've frequently seen browser issues with konq not knowing how to handle a file type when a link is clicked.. yet 2 seconds later it will load the html page just fine.
khtml doesn't always render css right, which is a sticky point for all browsers.
[ really silly of them ]
I know that KHTML works, though I've frequently seen browser issues with konq not knowing how to handle a file type when a link is clicked.. yet 2 seconds later it will load the html page just fine.
khtml doesn't always render css right, which is a sticky point for all browsers.
I was humming and ahing about trying it, you've convinced me, I'll let the less and more aware be guinea pigs for now. 
Check out how many instances of chrome.exe are running on your machine. When
you first open Chrome you have at least 2. Then open another tab and you'll have
at least one more. Open enough tabs or new windows and you'll run low on
resources. There is also a list of commands floating out there on the net that you
can append to chrome.exe to do things such as turning off the sandbox, adding
even more chrome.exe processes or one called -remote-shell-port. Sounds like
and exploit waiting to happen to me.
you first open Chrome you have at least 2. Then open another tab and you'll have
at least one more. Open enough tabs or new windows and you'll run low on
resources. There is also a list of commands floating out there on the net that you
can append to chrome.exe to do things such as turning off the sandbox, adding
even more chrome.exe processes or one called -remote-shell-port. Sounds like
and exploit waiting to happen to me.
Every tabbed browser consumes more resources when more tabs are opened.
Every browser has execution options that change the way it behaves.
This is not some kind of unique set of conditions that add up to a unique exploit or failure.
Every browser has execution options that change the way it behaves.
This is not some kind of unique set of conditions that add up to a unique exploit or failure.
Great post Chad,
I know that Google has changed the EULA, eliminating the verbiage about copyright conflicts. I was curious if you had a serious look at the EULA and found any other issues?
I know that Google has changed the EULA, eliminating the verbiage about copyright conflicts. I was curious if you had a serious look at the EULA and found any other issues?
The original article has been edited to reflect new information about how Google Chrome manages saved passwords.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
