I got onto my first mini rosetta 1.24 work unit today and it has started to try and access the internet which got caught by the firewalls.

All communication has till this point been handled by boinc so I don't know why it suddenly wants branch out on it's own.

I really don't want to go adding more exceptions to the firewalls as if nothing else it's a right pain in the arse.

---

You are correct, all normal network activity is handled via BOINC. What's evidentally happend is that an error was trapped, and it was trying to report in with the symbol tables. This has to occur within the application. Since that was blocked, once you clear any error prompt from the firewall, the task will report through with the rest of the details it has.

So, this was not a change in Rosetta. And you don't need to change your firewall if you do not wish to, it probably has to be changed every time the application version changes. It was just attempting to report additional useful information about the error that occured.

---

Rosetta Moderator: Mod.Sense

So it may prompt for aditional access in the future but only in the case of errors not as a standard course of practice?

---

exactly. It may, due to errors, and if you wanted to enable the Rosetta executable to access the internet that would allow it to report the debug information, but if you chose not to that is fine too. But on some systems, the prompt will cause your execution to stop until the message is responded to. That would probably be true with access was permitted or not. So, still, doesn't really make a difference. Use the firewall options you prefer.

---

Rosetta Moderator: Mod.Sense