Softpedia >Mac >Security >TCPBlock >  Changelog

TCPBlock Changelog

What's new in TCPBlock 4.2

Apr 28, 2014
  • Solved an error related to connecting apps display.

New in TCPBlock 4.0 (Apr 14, 2014)

  • Cryptographical hash filtering.
  • Optionally block incoming connections too.
  • Support for Mac OS 10.5 removed.

New in TCPBlock 4.0 Beta 1 (Mar 24, 2014)

  • Cryptographical hash filtering.
  • Support for Mac OS 10.5 removed.

New in TCPBlock 3.0 (Jan 16, 2014)

  • Support for Notification Center added.
  • Notifier resolves hostnames.
  • Added ignore list to notifier.
  • Preference Pane authorization timeout removed.
  • Block incoming connections too.
  • Improved filtering of UDP connections.
  • Filtering of specific addresses for each app.
  • Filtering of specific ports for each app.
  • Filtering for an IP address range or a port range.
  • Global rules.
  • Support for PowerPC removed.

New in TCPBlock 3.0 Beta 7 (Jan 9, 2014)

  • Filtering of specific ports for each app.
  • Filtering for an IP address range or a port range.
  • Global rules.

New in TCPBlock 3.0 Beta 6 (Dec 30, 2013)

  • Added ignore list to notifier.

New in TCPBlock 3.0 Beta 5 (Dec 16, 2013)

  • Filtering of specific addresses for each app.
  • Limit of 300 Application List items removed.

New in TCPBlock 3.0 Beta 4 (Dec 5, 2013)

  • Improved filtering of UDP connections.
  • Notifier resolves hostnames.

New in TCPBlock 3.0 Beta 1 (Nov 18, 2013)

  • Support for Notification Center added.
  • Preference Pane authorization timeout removed.
  • Application List can contain up to 300 apps to block.
  • Block incoming connections too.
  • Support for PowerPC removed.

New in TCPBlock 2.10 (Oct 20, 2011)

  • Filter UDP Protocol:
  • Additionally to the TCP protocol TCPBlock filters and blocks the UDP protocol. UDP provides a minimal, unreliable, best-effort, message-passing transport to applications and upper-layer protocols. As we know from the Windows world many trojans are using UDP to communicate. With TCPBlock you can filter the two most widely used internet communication protocols.
  • For blacklist users no configuration changes are required. If you are using a TCPBlock whitelist then you may wish to include in the list some basic system services like NTP or DNS, which are using UDP.
  • Report if apps are connecting over TCP or UDP:
  • In the Connecting Apps tab and in the TCPBlock Network Monitor you can see which communication protocol is used.
  • Improved logging:
  • You can set the TCPBlock log level with a slider in the preference pane. Your options are: No logging at all, log only the blocked connections and log all connections. The last option logs both blocked and allowed connections. All the log information is written to the file /var/log/system.log in Leopard and /var/log/kernel.log in Snow Leopard.
  • Incompatibility with nginx resolved:
  • An incompatibility which causes your Mac to crash if the nginx web server is used together with TCPBlock is resolved.

New in TCPBlock 2.9 (Sep 26, 2011)

  • Support for Growl notifications:
  • Install Growl on your computer if you not already have it. TCPBlock will not install Growl for you.
  • In the TCPBlock Preference Pane enable the sending of Growl notifications. This will register three types of notifications with Growl: “Block outcon”, “Allow outcon” and “Allow incon”. As default only the “Block outcon” notification is displayed. If you want to see the other types of notifications you have to open the Growl Preference Pane and configure there the notification display options for the TCPBlock application.
  • If more than one notification of the same type is sent at the same time they are coalesced into a single notification to avoid flooding your display with too many messages. Note that not all Growl display plugins support coalescing.
  • The notifications will give you a quick overview of the current network activity of your Mac.
  • Option tcpblock -mt displays a timestamp when network activity occurs:
  • You can let the command line network monitor work unattendedly overnight, and write all network activity into a log file. With the timestamp you can see when the connection happens.
  • Improved detection of the process name an incoming connection connects to:
  • TCPBlock now maintains a list of all programs on your Mac as soon as they are listening for incoming connections. If an incoming connection is made then TCPBlock looks in its list for the program which is serving the new connection and display its name. You can configure TCPBlock to notify you about incoming connections.
  • TCPBlock Kernel Module stability improvements:
  • Kernel programming is an immense responsibility. You must be exceptionally careful to ensure that your code does not cause the system to crash, does not provide any unauthorized user access to someone else’s files or memory, does not introduce remote or local root exploits, and does not cause inadvertent data loss or corruption. The TCPBlock kernel code has been carefully reviewed and improved.

New in TCPBlock 2.8 (Dec 9, 2010)

  • Network Monitor shows incoming connections too.
  • Connecting Apps tab shows incoming network connections in light gray
  • and apps already included the Application List in dark gray.
  • Connecting Apps table automatically scrolls to the end of the list.
  • The configuration of the previous version is reused.
  • Minor GUI changes.

New in TCPBlock 2.7 (Dec 2, 2010)

  • Support for 64bit kernels added.

New in TCPBlock 2.6 (Nov 27, 2010)

  • Initial setup simplified.
  • Set application to be blocked within few mouse clicks.
  • Connecting Apps tab shows live network activity.