Chrome_ChildIOT detected without a path or anything else to identify it #850
-
|
Mint 21.1, OpenSnitch 1.6.0.rc3. I know the current version is rc4, but rc3 is in the repo and I don't see anything relevant in the changelog. The issue may be hard to reproduce so I'm looking mostly for general guidance here. The problem was not present back when I was using Chromium but appeared immediately after I switched to Edge. Chromium is still installed on my system, though. OpenSnitch reports an outbound attempt by Chrome_ChildIOT. No path shows regardless of what I click in the dialog. If left unattended, it creates a rule as expected. Screenshot attached. I'm mostly curious about why it has no path. For now I'm not even sure if it is a legitimate Chromium or Edge process at all.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
Hi @zerthsky , My recommendation would be to upgrade v1.6.0rc4, there're 3 important bugs that fix errors adding rules (Fixed adding interception rules on new and old kernels ( ced9a24 , d31c4e8, #781)) This scenario is likely caused because we failed getting the path of the process, and instead of dropping the package and let chrome retry the connection again, we used /proc/$pid/comm value to associate it the connection. There're several reasons that can cause this behaviour, do you usually suspend/hibernate your PC? On the other hand, set LogLevel to DEBUG under Preferences -> Nodes, and when you this problem again, copy right away /var/log/opensnitchd.log to /tmp (for example), and post the log. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much for your prompt response. I set the log level to debug. Will post when I get anything happening. Not using suspend or hibernate, by the way. It's a desktop and always plugged in, hence I see no point. Forgot to mention that my Edge is flatpak. However, Chromium is flatpak also and it never gives me this. |
Beta Was this translation helpful? Give feedback.
-
|
The issue has not happened once in the 3 weeks passed, so I guess it was related to a specific Edge version and no longer relevant. Thank you again for your help. I'm very happy with OpenSnitch as a whole. It's both educative and fun. |
Beta Was this translation helpful? Give feedback.
Hi @zerthsky ,
My recommendation would be to upgrade v1.6.0rc4, there're 3 important bugs that fix errors adding rules (Fixed adding interception rules on new and old kernels ( ced9a24 , d31c4e8, #781))
This scenario is likely caused because we failed getting the path of the process, and instead of dropping the package and let chrome retry the connection again, we used /proc/$pid/comm value to associate it the connection.
There're several reasons that can cause this behaviour, do you usually suspend/hibernate your PC?
On the other hand, set LogLevel to DEBUG under Preferences -> Nodes, and when you this problem again, copy right away /var/log/opensnitchd.log to /tmp (for example), and pos…