Solved Chromium and Hotword

  • Thread starter Thread starter hukadan
  • Start date Start date
H

hukadan

Guest
I just came accross this bug report. It seems that once installed, chromium downloads a blob without asking permission.

This blob is apparently related to hotword. It seems according to this commit message that this option is enabled by default but can be disabled. I do not use chromium myself but a fresh install (using public repo) confirmed that this blob was installed (at least it is how I interpret the information provided by chrome://voicesearch/ and the following output)
Code: 
$ ls -l /home/hukadan/.config/chromium/Default/Extensions/lccekmodgklaepjeofjdjpbminllajkg/0.3.0.5_0/_platform_specific/x86-64_
total 4386
-rw-------  1 hukadan  hukadan  1181296 Jun  5 23:54 hotword-x86-64.nexe
-rw-------  1 hukadan  hukadan  896976 Jun  5 23:54 hotword.data

Could someone confirm this on his/her machine before bothering the freebsd-chromium mailing list ? Also, I am not a security expert so this blob could be of no concern but not knowing, I prefer to ask.

-- Edit --

Apparently the following line on the make.conf should solve the problem :
Code: 
.if ${.CURDIR:M*/www/chromium}
GYP_DEFINES+= enable_hotwording=0
.endif
I am trying now..
 
I looked at this when I first heard it and thought I read they were fixing it or it was fixed. Didn't read anything about "hotword", and that looks like a Windows thing, but I wasn't really paying attention.
 
It happens also on Debian and since it is a compilation option, I expect it to happen on any platform that supports www/chromium. I am waiting the end of the compilation to see if there is any difference. But again, I am not saying that it is a problem. I rather do not know.
 
Interesting:
Code: 
tingo@kg-core1$ ll .config/chromium/Default/Extensions/lccekmodgklaepjeofjdjpbminllajkg/*/_platform_specific/x86-64_/
total 2152
drwx------  2 tingo  wheel  -  512 May 27 00:03 ./
drwx------  3 tingo  wheel  -  512 May 27 00:03 ../
-rw-------  1 tingo  wheel  - 1181296 Mar 31 16:31 hotword-x86-64.nexe
-rw-------  1 tingo  wheel  -  896976 Mar 31 16:31 hotword.data
and
Code: 
tingo@kg-core1$ file .config/chromium/Default/Extensions/lccekmodgklaepjeofjdjpbminllajkg/*/_platform_specific/x86-64_/*
.config/chromium/Default/Extensions/lccekmodgklaepjeofjdjpbminllajkg/0.3.0.5_0/_platform_specific/x86-64_/hotword-x86-64.nexe: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=0x555dd22448ca6d88d6311092340a8b92309865f5, stripped
.config/chromium/Default/Extensions/lccekmodgklaepjeofjdjpbminllajkg/0.3.0.5_0/_platform_specific/x86-64_/hotword.data:  data
 
hukadan said:
I just came accross this bug report. It seems that once installed, chromium downloads a blob without asking permission.

This blob is apparently related to hotword. It seems according to this commit message that this option is enabled by default but can be disabled. I do not use chromium myself but a fresh install (using public repo) confirmed that this blob was installed (at least it is how I interpret the information provided by chrome://voicesearch/ and the following output)
Code: 
$ ls -l /home/hukadan/.config/chromium/Default/Extensions/lccekmodgklaepjeofjdjpbminllajkg/0.3.0.5_0/_platform_specific/x86-64_
total 4386
-rw-------  1 hukadan  hukadan  1181296 Jun  5 23:54 hotword-x86-64.nexe
-rw-------  1 hukadan  hukadan  896976 Jun  5 23:54 hotword.data

Could someone confirm this on his/her machine before bothering the freebsd-chromium mailing list ? Also, I am not a security expert so this blob could be of no concern but not knowing, I prefer to ask.

-- Edit --

Apparently the following line on the make.conf should solve the problem :
Code: 
.if ${.CURDIR:M*/www/chromium}
GYP_DEFINES+= enable_hotwording=0
.endif
I am trying now..
Click to expand...
I tried adding that to make.conf and recompiling www/chromium just out of curiosity. It doesn't seem to work. The files are still present after first startup.
 
protocelt said:
I tried adding that to make.conf and recompiling www/chromium just out of curiosity. It doesn't seem to work. The files are still present after first startup.
Click to expand...

Sorry, I should have come back here before. The www/chromium version of the ports does not make this flag avaible yet. I should have check that before trying to compile... I will fill a bug report today to see if they can make it avaible. Meanwhile, it seems that hotword needs the native client (NaCl) of chromium to work and this native client is disabled on the FreeBSD version. I will post the link of the bug here once done.


-- Edit --

Here is the bug report : PR 200965
 
You must log in or register to reply here.
Back
Top