I found a series of posts/bug reports about random DNS requests made by Chrome. The conclusion is that random DNS requests are neither generated by malware nor by plugins or add-ons.
The requests are done by Chrome to learn if it can handle searches made from its address bar.
The best explanation I have found is quoted below from this link.
If you ...
Chrome and Chromium dropped support for the NPAPI plugins (Netscape Plugin Application Programming Interface) in favor of PPAPI (Pepper Plugin Application Programming Interface) so all plugins that use NPAPI (like GNOME Extension plugin) are just not supported.
The only alternative is using another browser that allows them (like Firefox) or asking the ...
Chromium/Chrome does not cache DNS requests more than a minute indeed.
Interestingly enough, from bugs-chromium - Issue 164026 - DNS TTL not honored from Apr 21 2011
The only DNS cache in the system is in chrome and it does not honor
TTL. We need to either fix chrome and/or add an intermediate cache
that does handle TTL correctly.
Answer in the ...
Given that google killed chrome://memory in March 2016, I am now using smem:
# detailed output, in kB apparently
smem -t -P chrom
# just the total PSS, with automatic unit:
smem -t -k -c pss -P chrom | tail -n 1
to be more accurate replace chrom by full path e.g. /opt/google/chrome or /usr/lib64/chromium-browser
this works the same for multiprocess firefox ...
This command exits the chrome process tree gracefully, in all window managers:
pkill --oldest chrome
or if you prefer:
/usr/bin/pkill --oldest --signal TERM -f chrome
gracefully means: avoid seeing “Google Chrome didn't shut down correctly. To repoen ...” next time chrome starts
chrome browser (e.g. version 39.0.2171.95) traps and ...
Press Shift+Esc to bring up Chrome's task manager. Locate the line corresponding to the PID you want (click on the “Process ID” column header to sort by PID). Double-click the line to bring the tab to the foreground.
It is because chrome packages the...
Widevine Content Decryption Module - Version: 22.214.171.1247
Enables Widevine licenses for playback of HTML audio/video content. (version: 126.96.36.1997)
...whereas chromium does not and in August 2014 Netflix switched to allowing HTML5 content by default. Visit:
...to see a list.
You will need that ...
I was not sure I could post it as an answer as I did not specifically address "where vulnerability comes from" - and mere refs then own words. But anyhow –
Hopefully this shed some light on the topic of sandbox:
Quick introduction to Chrome's sandbox.
More in depth design document. With internal links to FAQ, etc.
And as stated, Google themselves ...
I noticed this issue when I check for local listening ports with ss -utln before Google brought me here.
My first thought of disabling this is to take a look at chrome://flags. And I found this: chrome://flags/#device-discovery-notifications
Disabling this so-called "device discovery" feature turns off listening of mDNS port 5353/tcp. You need to relaunch ...
Your node wants to start Chrome (or any browser) and use environment variables to set it out. Just export the variable along with the path pointing to the binary and it should work:
Now, actually it should just call sensible-browser instead of forcing you to do this.
Something to play with
It uses xdotool, which lets you script windows/desktop actions. If you supply the name of the browser as an argument, it'll find and reload the current page. You can set a default browser, so you don't need to supply one each time, and you can change whether you send a CTRL-R to reload, or SHIFT-CTRL-R to reload without cache.
Those are NSS built-in certificates. They are provided through a shared library: /usr/lib/libnssckbi.so (path may be different on your system). That's where Chrome gets them from.
You could list them with certutil like this:
Make a link to the library in ~/.pki/nssdb:
ln -s /usr/lib/libnssckbi.so ~/.pki/nssdb
certutil -L -d sql:$HOME/.pki/nssdb/...
Now that I'm at work, I'll write up a step by step answer. First off you seem to be doing the steps in the wrong order. As such, I'll number these steps in the order they should be executed.
mkdir -pv ~/chromium
git config --global user.name “Joel Maranhao”
git config --global user.email “firstname.lastname@example.org”
git config --global core....
Perhaps wmctrl could be of some assistance. You could use the -c option that closes a window gracefully:
wmctrl -c chrome
The string chrome is matched against the window titles. Note that the window might not close if some message pops-up (e.g. when you have multiple tabs open).
Chromium obeys the system-wide xdg settings. To configure opening magnet links with a custom application use the following command
xdg-mime default transmission-gtk.desktop x-scheme-handler/magnet
You can also do this manually: Open the file ~/.local/share/applications/mimeapps.list and add the following entry in the section [Default Applications]:
When you close a GNOME Terminal window, a SIGHUP is sent to the shell that it was running. The shell will typically send a SIGHUP to every process group that it knows it created - even ones started with nohup - and then exit. If the shell is bash, it will skip sending a SIGHUP to any process group that the user marked with disown.
Running a command with ...
The Pentadactyl and Vimperator addons for Firefox allow vim-like editing in text areas by pressing ctrl+t; I think there is also an option to turn it on permanenly. There is also It's All Text! that will actually launch an editor for you.
As far as Chrome goes, it's not as easy, as the API is quite limited. They require you to run a server on your system. ...
I have found the solution to both problems!
To not append a space, use the nospace option. This can be done in two ways:
Pass it to the complete:
complete -o nospace -F _chromium chromium
Use the compopt built-in:
compopt -o nospace (to enable the option)
compopt +o nospace (to disable the option)
I found it in the Bash documentation at gnu.org, 8.7 ...
Generally, a keyring is a secure password store, that is encrypted with a master password.
Once you input the master password, the keyring gets decrypted and all the passwords inside it are available to the application accessing the keyring.
On Gnome/Ubuntu the seahorse application can be used to look at the keyring and the master password is the same with ...
You want to install the "chrome-gnome-shell" (and probably also the "GNOME Shell Integration" Chrome Extension)
You can find instructions to install chrome-gnome-shell for your distro here on the GNOME wiki.
Essentially, install for your distro:
Ubuntu - available from ppa:ne0sight/chrome-gnome-shell.
Fedora - available from region51/chrome-gnome-shell ...
By default, yum will resolve both IPv4 & IPv6 addresses of host/domain name, see the wireshark screenshot below (I don't know python program, so network traffic capture is the only way to find out how yum resolve host name).
To resolve IPv4 address only, just add ip_resolve=4 or ip_resolve=ipv4 config to yum.conf (see man yum.conf for more help). For ...
To find version go to chrome://chrome in Google-Chrome, or say:
$ google-chrome --version
Version < 43 ]
At least for now, go to:
Select Disabled and restart browser.
Version [ 44, 46.0.2490.??]
As for version 44 to 46.0.?* the above tweak does not work. But add --disable-new-avatar-menu to startup:
Clarification : This .exe file you downloaded is an installation file for Windows operating systems. You can install Google Chrome in Ubuntu this way, open a terminal and execute these commands:
echo "deb http://dl.google.com/linux/chrome/deb/ stable main" | sudo tee /etc/apt/sources.list.d/google-chrome.list
wget -q -O - https://dl.google.com/linux/...
wasavi provides a vim interface for text boxes in multiple web browsers (Chrom(ium), Firefox/Iceweasel & Opera) and I can confirm that it works on Chromium on Linux (Debian 7 w/ Gnome3). Start it with <Ctrl><Enter>, lots more info on the home page below:
wasavi home page
Links for installing to Opera and Firefox/...
It get's them from the underlying operating system. You can read about it here:
Root Certificate Policy
excerpt from above link
Google Chrome attempts to use the root certificate store of the
underlying operating system to determine whether an SSL certificate
presented by a site is indeed trustworthy, with a few exceptions.
That page goes on to ...