Suggestion: reduce network chatter for easier configuration of firewalls

Joshua Ellis

My Mac is setup to request authorization for unrecognized outbound network requests. The following is the list of requests made for Verbum to launch. This is *really* chatty for application startup. 

destination: academic.logos.com / port: 443<br />destination: academic.logos.com / port: 80<br />destination: api.faithlife.com / port: 443<br />destination: atlasapi.logos.com / port: 443<br />destination: auth.logos.com / port: 443<br />destination: bibliographyapi.logos.com / port: 443<br />destination: cbvstylesapi.logos.com / port: 443<br />destination: clientfeedback.logos.com / port: 443<br />destination: clientfeedback.logos.com / port: 80<br />destination: clientservices.logos.com / port: 443<br />destination: clippingsapi.logos.com / port: 443<br />destination: covers.assets.logos.com / port: 80<br />destination: customdictionariesapi.logos.com / port: 443<br />destination: customlibrarycatalogapi.logos.com / port: 443<br />destination: downloads.logoscdn.com / port: 80<br />destination: embed.faithlife.com / port: 443<br />destination: faithlife.com / port: 443<br />destination: favoritesapi.logos.com / port: 443<br />destination: guidesapi.logos.com / port: 443<br />destination: handoutsapi.logos.com / port: 443<br />destination: highlightingapi.logos.com / port: 443<br />destination: historyapi.logos.com / port: 443<br />destination: layoutsapi.logos.com / port: 443<br />destination: libapi.logos.com / port: 443<br />destination: librarycatalogapi.logos.com / port: 443<br />destination: logos.com / port: 443<br />destination: logos.com / port: 80<br />destination: mediaapi.logos.com / port: 443<br />destination: notesapi.logos.com / port: 443<br />destination: passagelistsapi.logos.com / port: 443<br />destination: pbbapi.logos.com / port: 443<br />destination: prayerlistsapi.logos.com / port: 443<br />destination: prefsapi.logos.com / port: 443<br />destination: productsapi.logos.com / port: 443<br />destination: readinglistsapi.logos.com / port: 443<br />destination: readingplansapi.logos.com / port: 443<br />destination: readingprogressapi.logos.com / port: 443<br />destination: resources.logoscdn.com / port: 80<br />destination: selftestsapi.logos.com / port: 443<br />destination: sendtokindleapi.logos.com / port: 443<br />destination: sentencediagramsapi.logos.com / port: 443<br />destination: serve.faithlifeads.com / port: 443<br />destination: services.logos.com / port: 443<br />destination: shortcutsapi.logos.com / port: 443<br />destination: syntaxsearchapi.logos.com / port: 443<br />destination: topics.logos.com / port: 443<br />destination: touchpointslog.logos.com / port: 443<br />destination: touchpointslog.logos.com / port: 80<br />destination: usereventsapi.logos.com / port: 443<br />destination: userinputsapi.logos.com / port: 443<br />destination: usertaggingapi.logos.com / port: 443<br />destination: visualfiltersapi.logos.com / port: 443<br />destination: votdapi.logos.com / port: 443<br />destination: wiki.logos.com / port: 443<br />destination: wordfindsapi.logos.com / port: 443<br />destination: wordlistsapi.logos.com / port: 443

Donnie Hale

I really appreciate you posting this. That list really is over the top. Every entry in that list with a port of 443 means that, in addition to needing a tcp connection, an SSL (TLS) session must be established. Yikes!

-Donnie