Page 1 of 1
Neue Iron-Version: 43.0.2300.0 Stable für MacOS
Posted: Tue Sep 22, 2015 6:11 pm
by SRWare
Ab sofort kann auch Iron für MacOS X mit Versionsnummer 43 heruntergeladen werden. Version 43.0.2300.0 führt alle Veränderungen und neuen Features ein, die auch von Chromium 43 bekannt sind.
Verbesserungen:
- verbesserte Extension-APIs
- allgemeine Bug-/Securityfixes
Bitte Gatekeeper vor der Installation und bis nach dem ersten Start abschalten:
http://its.uiowa.edu/support/article/4038
Um Sync zu aktivieren, Iron EINMAL mit folgenden Parametern von der Konsole starten und die Synchronisation dann aktivieren:
Chromium.app/Contents/MacOS/Chromium --user-agent="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.76 Safari/537.36"
Downloads (ab OS X 10.7 / Intel):
http://www.srware.net/downloads/iron-mac.zip (32-Bit) [Anmerkung: nicht mehr unterstützt, Download führt zu Version 37]
http://www.srware.net/downloads/iron-mac64.zip (64-Bit)
Re: Neue Iron-Version: 43.0.2300.0 Stable für MacOS
Posted: Sat Dec 05, 2015 3:37 pm
by ironic
I tried SRWare Iron 43.0.2300.0 (64-bit) in OS X 10.8.5 in a VM and promptly caught the following outgoing connections on first launch
Code: Select all
action: deny
direction: outgoing
process: /Applications/VMware Fusion.app/Contents/Library/vmnet-natd
owner: system
destination: alt1-safebrowsing.google.com
port: 443
protocol: 6
help: On Dec 4, 2015, vmnet-natd tried to establish a connection to alt1-safebrowsing.google.com on TCP port 443 (https). The request was denied via connection alert.
action: deny
direction: outgoing
process: /Applications/VMware Fusion.app/Contents/Library/vmnet-natd
owner: system
destination: http://www.google.com
port: 80
protocol: 6
help: On Dec 4, 2015, vmnet-natd tried to establish a connection to http://www.google.com on TCP port 80 (http). The request was denied via connection alert.
action: deny
direction: outgoing
process: /Applications/VMware Fusion.app/Contents/Library/vmnet-natd
owner: system
destination: http://www.google.de
port: 443
protocol: 6
help: On Dec 4, 2015, vmnet-natd tried to establish a connection to http://www.google.de on TCP port 443 (https). The request was denied via connection alert.
action: deny
direction: outgoing
process: /Applications/VMware Fusion.app/Contents/Library/vmnet-natd
owner: system
destination: http://www.google.com
port: 443
protocol: 6
help: On Dec 4, 2015, vmnet-natd tried to establish a connection to http://www.google.com on TCP port 443 (https). The request was denied via connection alert.
action: deny
direction: outgoing
process: /Applications/VMware Fusion.app/Contents/Library/vmnet-natd
owner: system
destination: maps.google.de
port: 443
protocol: 6
help: On Dec 4, 2015, vmnet-natd tried to establish a connection to maps.google.de on TCP port 443 (https). The request was denied via connection alert.
action: deny
direction: outgoing
process: /Applications/VMware Fusion.app/Contents/Library/vmnet-natd
owner: system
destination: plus.googleapis.com
port: 443
protocol: 6
help: On Dec 4, 2015, vmnet-natd tried to establish a connection to plus.googleapis.com on TCP port 443 (https). The request was denied via connection alert.
Then after changing default search engine to bing and disabling translation, it logged
action: deny
direction: outgoing
process: /Applications/VMware Fusion.app/Contents/Library/vmnet-natd
owner: system
destination: maps.google.de
port: 80
protocol: 6
help: On Dec 4, 2015, vmnet-natd tried to establish a connection to maps.google.de on TCP port 80 (http). The request was denied via connection alert.
action: deny
direction: outgoing
process: /Applications/VMware Fusion.app/Contents/Library/vmnet-natd
owner: system
destination: alt1-safebrowsing.google.com
port: 443
protocol: 6
help: On Dec 4, 2015, vmnet-natd tried to establish a connection to alt1-safebrowsing.google.com on TCP port 443 (https). The request was denied via connection alert.
action: deny
direction: outgoing
process: /Applications/VMware Fusion.app/Contents/Library/vmnet-natd
owner: system
destination: plus.googleapis.com
port: 443
protocol: 6
help: On Dec 4, 2015, vmnet-natd tried to establish a connection to plus.googleapis.com on TCP port 443 (https). The request was denied via connection alert.
action: deny
direction: outgoing
process: /Applications/VMware Fusion.app/Contents/Library/vmnet-natd
owner: system
destination: http://www.google.de
port: 443
protocol: 6
help: On Dec 4, 2015, vmnet-natd tried to establish a connection to http://www.google.de on TCP port 443 (https). The request was denied via connection alert.
action: deny
direction: outgoing
process: /Applications/VMware Fusion.app/Contents/Library/vmnet-natd
owner: system
destination: maps.google.de
port: 443
protocol: 6
help: On Dec 4, 2015, vmnet-natd tried to establish a connection to maps.google.de on TCP port 443 (https). The request was denied via connection alert.
I thought Iron didn't let outgoing connections to google not strictly related to the search engine.