Carbon For Mac Os X


Stops advanced threats and zero-day attacks; closes major enterprise security hole of Macs with limited or outdated protection

  1. Carbon Black Macos
  2. Carbon Framework Mac Os X
  3. Carbon Copy Cloner For Mac Os X
  4. Carbon Copy Cloner For Mac Os X 10.7.5

I’d like to take this opportunity to say I’ve been extremely happy with Carbon Copy Cloner and Bombich Software over the four years I’ve been a customer. CCC is a truly outstanding piece of crafted software with top-notch support (I love the integrated help and support features) offered by a reliable and professionally-run company. Time Machine is backup software that Apple includes with Mac desktop computers and MacBook laptops running OS X. It creates copies of documents and stores them on an external hard drive that you purchase, such as an Apple Time Capsule.

WALTHAM, Mass.—July 23, 2013—Bit9, the leader in a new generation of endpoint and server security based on real-time visibility and protection, today announced the introduction of the Bit9 Security Platform for Mac OS X. Built from the ground up for seamless integration with Mac desktops, laptops and servers, Bit9 for Mac offers the same industry-leading security innovations of the Bit9 Platform for Windows and delivers three industry firsts:

  • It is the FIRST enterprise security solution that continuously monitors and records all activity on Mac desktops, laptops and servers.
  • It is the FIRST enterprise security solution for Macs that detects and stops Mac-targeted advanced threats and zero-day attacks without using signatures.
  • It is the FIRST security solution for Macs that integrates with network security devices such as FireEye and Palo Alto Networks to accelerate incident response and ensure all files arriving on endpoints and servers are safe.

Click to Tweet:@Bit9 debuts 1st enterprise security product that continuously monitors & records all activity on Macs #Bit9forMac

Carbon For Mac Os X

Business users are driving demand for Macs across the enterprise. Until now, the few enterprise security products available for the Mac were dependent on malware signatures and behavioral patterns, which makes them ineffective against today’s advanced threats and targeted attacks. Organizations and analysts are concerned that Macs now represent a growing vulnerability in the enterprise. With Bit9 for Mac, IT and security teams can support their employees’ desire to use Macs while ensuring the highest level of security against today’s threat landscape. And enterprises that deploy Bit9 for Windows and Bit9 for Mac are able to manage all of their endpoints and servers from a single console.

Bit9 for Mac defends enterprises against advanced threats and delivers key benefits for advanced threat protection and compliance purposes, including:

  • Visibility: Know what’s running on every Mac OS X endpoint and server—right now
  • Detection: Real-time, signature-less detection of advanced threats and zero-day attacks
  • Protection: Stop all untrusted software from executing on any Mac.
  • Forensics: A complete recorded history and full audit trail of all threat-related activity on every Mac for immediate incident analysis and response
  • Network security integration: A first-of-its-kind integration with next-generation network security solutions from industry leaders such as FireEye and Palo Alto Networks for accelerated incident response and remediation

The Bit9 Security Platform for Mac is available worldwide immediately.

Bit9 Executive Quote:Brian Hazzard, vice president of product management
“The proliferation of Macs in the enterprise has exposed organizations to a fast-growing security challenge. For the past 20 years, Windows endpoints and servers have been the target of most malware. Now, with Macs being deployed in record numbers, enterprises urgently need new solutions to stop threats targeted specifically at Macs. We built Bit9 for Mac from the ground up to provide the same unmatched security for Macs in the enterprise that we do for Windows endpoints and servers. There’s no other Mac security solution on the market that delivers continuous monitoring and recording and stops advanced attacks without relying on signatures. Now, enterprises can manage Mac and Windows security from a single Bit9 console. The bar for Mac security has been raised sky high.”

Industry Analyst Quote:Fran Howarth, security practice leader, Bloor Research
“Macs are a reality in the enterprise IT ecosystem, and as they proliferate, they are increasingly vulnerable to advanced threats and targeted attacks. It’s a big mistake for enterprise security teams to underestimate the potential risks their Mac deployments represent. Bit9 has delivered a version of its platform for Mac that addresses this growing problem with a true enterprise-class security solution that offers real-time monitoring and recording and the same level of protection against untrusted software it offers for Windows.”

Industry Analyst Quote: Jane Wright, Senior Research Analyst, Enterprise Strategy Group, Inc.
“According to ESG’s research, 59% of enterprise organizations surveyed know or believe that they have been targeted by an advanced persistent threat. As more enterprises deploy Macs to meet employees’ needs, those Macs represent an increasingly desirable target for cyber attackers who want to steal intellectual property, financial records, and other valuable data. Antivirus and intrusion protection systems are a first step in keeping most Macs safe, but advanced threats against Macs require more robust security. Solutions designed to detect and prevent cyber threats in real time, such as Bit9 for Mac, can help to fill the security gap arising from the use of Macs in the enterprise.”

Bit9 Security Platform for Mac

About Bit9
Bit9 is the leader in advanced threat protection for endpoints and servers based on real-time visibility and prevention. Bit9 is the only solution that continuously monitors and records all activity on endpoints and servers and stops cyber threats that evade traditional security defenses. Bit9’s real-time sensor and recorder, cloud-based services, and real-time enforcement engine give organizations immediate visibility into everything running on their endpoints and servers; real-time signature-less detection of and protection against advanced threats; a recorded history of all endpoint and server activity to rapidly respond to alerts and incidents; and real-time integration with network security devices such as FireEye and Palo Alto Networks. 1,000 organizations worldwide—from 25 Fortune 100 companies to small businesses—use Bit9 to increase security, reduce operational costs and improve compliance.

Media Contacts:

Carbon Black Macos

Kevin Flanagan
[email protected]

Danielle Ostrovsky
Hi-Touch PR
[email protected]


Mac::Carbon - Access to Mac OS Carbon API

This module provides documentation of the Mac::Carbon modules, and acts as a frontend to them.

Mac::Carbon is a collection of perl modules for accessing the Carbon API under Mac OS X. It is a port of the Toolbox modules written by Matthias Neeracher for MacPerl.

This module will load in all the Carbon modules, and export all of the functions, constants, and other variables. An export tag is set up for each module, so they may be selected individually.

This module exists primarily because in Mac OS X, all the Carbon functions are imported into a C program with a single header, Carbon.h, so Mac OS X users may prefer to load in the entire Carbon API with a single module.

For detailed information on the Carbon API (highly recommended, as a familiarity with Carbon is assumed in the POD), see

The documentation is also located on your system, if you have the Developer Tools installed, at /Developer/Documentation/Carbon/.

Also of significant use are the related header files on your system. Use the `locate` command to find them. They contain current documentation and notes for the API.

The modules were written for Mac OS originally, and are in part being ported to Carbon. You may also be interested in the original documentation.

Swiped from Mac/Toolbox.pod in the MacPerl distribution.

Carbon Framework Mac Os X

The Macintosh Operating System provides a rich API with thousands of toolbox calls. The MacPerl toolbox modules aim to make as much as possible of this functionality available to MacPerl programmers. The mapping of the toolbox interfaces into MacPerl is intended to be

  1. Convenient to use for Perl programmers.

  2. As close as possible to the C interfaces.

This translates into a mapping strategy which is discussed in the following sections.

Function mappings

MacPerl toolbox calls take their input arguments in the same order as the corresponding toolbox functions. Output arguments are never passed by reference, but returned from the calls. If there are several output arguments, a list is returned. If an error occurs, the function returns undef or () and the error code is available in the $^E variable.

Carbon Copy Cloner For Mac Os X

Data structure mappings

Complex data structures are mapped into blessed references. Data fields are available through member functions which return the value of a field if called without an argument and change the value if called with an argument.

Carbon For Mac Os X

The modules follow the same API under Mac OS X as Mac OS, except that the non-Carbon API is not supported (for example, NewHandle is supported, but NewHandleSys is not). Calling a function not supported by Carbon will generate an exception.

Carbon Copy Cloner For Mac Os X 10.7.5

In each module's documentation, functions that work only under Mac OS (non-Carbon) are marked with Mac OS only. Those that work only under Mac OS X (Carbon) are marked with Mac OS X only. A complete list is at the end of this document.

The MacPerl package is automatically bootstrapped in MacPerl; it is included here, though the app-specific functions (Reply, Quit) are not supported, and the MacPerl package must be loaded explicitly (e.g., use MacPerl;). Also, Ask/Answer/Pick are provided via AppleScript, talking to the SystemUIServer process.

The Mac-specific error codes are put in $^E as in MacPerl, but $^E does not automatically convert the numeric error into a string in string context. See brian d foy's Mac::Errors module on the CPAN for this:

Mac::Errors is not included with or required by Mac::Carbon, but it is highly recommended.

$! is set at the same time $^E is set. This is different behavior from MacPerl, but similar to other platforms. On MacPerl, $^E is signed, and on Unix it is unsigned, so to get the numeric value from $^E, just add 0, as above. Could be worse.

Carbon copy cloner for mac os x 10.6.8

Files are passed back and forth using Unix/POSIX filespecs (if you care about the gory details, a portion of the GUSI API has been reimplemented here, and it handles the conversions). Similarly, times are converted back and forth from the Mac OS epoch to the Unix epoch.

The support functions are in Carbon.h. See that file for descriptions of the issues, including bugs and possibilities for bugs, involved.

Significant portions of the Carbon API are unavailable to 64-bit programs on Mac OS X. Perhaps a subset of the API could be made available to a 64-bit perl (for more information see Apple's '64-Bit Guide for Carbon Developers'), and might in the future, but it's simpler at this point to just run perl in 32-bit mode.

There's a few ways to do this. Most obviously, you could simply build a 32-bit perl. I always build my own perl, and I just compile it for 32 bits.

There's also two methods mentioned in 'man perl' under Mac OS X 10.6: you can set an environment variable, or set a system preference. For the environment use:

And for the system preference, execute this line in your terminal:

There are very few issues on Intel. They mostly center around the fact that a Mac four-char-code is often treated as a string in Perl-space, but in C-space is an integer. The conversion process results in various errors.

Four-char-code types include typeType, typeEnumerated, typeProperty, typeKeyword, and typeApplSignature.

There are a few Don't Do Thats to keep in mind.

  • Don't change the type of an existing AEDesc; coerce it to a new desc instead, with AECoerceDesc(). This is generally good advice anyway.

  • Don't pass four-char-codes as arguments to AEBuild*; there's no easy way for the called function to know what type the argument is going to be passed as, and to fix the data before it is passed. Four-char-codes can be literals in AEBuild formats; this is a better method to use, when possible. For example:

  • Similarly, when using AEStream, don't pass a four-char-code to WriteData(), if you can avoid it. Use one of the methods that allow type specification (such as WriteDesc and WriteKeyDesc).

  • Don't try to parse binary data when you don't have to; use the API. For example, one of the example files for Mac::Speech parsed the creator ID out of the binary data structure instead of calling the API, and got the string reversed.

See each individual module for more information on use. See README for more information about modules not included here.

Functions supported only in Mac OS

The functions below are supported only in Mac OS, and not in Mac OS X, either because they are not supported by Carbon, or make no sense on Mac OS X.


Functions supported only in Mac OS X

The functions below are supported only in Mac OS X, and not in Mac OS, either because they are newer APIs, or make no sense on Mac OS.


See for more information.

  • Need more tests for:


    Should be more comprehensive for very little-used functions; main functionality is tested OK.




    Tested really only in other test suites, like Mac::Sound. Should be more comprehensive.




    Very good, but could do more exhausative FindFolder() tests.


    Tests not very good, but tested pretty extensively by Mac::Glue and friends.






    No real testing done.

  • In a few places, we need to know a text encoding, and assume it (such as in LSFindApplicationForInfo(), where Latin-1 is assumed). This is likely incorrect.

  • FSSpecs are limited to 31 characters. Ugh. Provide access to newer FSRef-based APIs.

  • Not specific to the Carbon versions: the Mac:: modules define classes such as Handle which probably should be something else, like Mac::Handle or Mac::Carbon::Handle or Mac::Memory::Handle (other examples include AEDesc, Point, Rect). No one has really complained before except on principle, but still ...

  • Can we support XCMDs etc. via XL? Do we want to?

The Mac Toolbox modules were written by Matthias Neeracher <[email protected]>. They were ported to Mac OS X and are currently maintained by Chris Nandor <[email protected]>.

Michael Blakeley, Emmanuel. M. Decarie, Matthew Drayton, brian d foy, David Hand, Gero Herrmann, Peter N Lewis, Paul McCann, Sherm Pendley, Randal Schwartz, Michael Schwern, John Siracusa, Dan Sugalksi, Ken Williams, Steve Zellers.



To install Mac::Carbon, copy and paste the appropriate command in to your terminal.

For more information on module installation, please visit the detailed CPAN module installation guide.