J. Mark Bull

41 papers A 3B 1C 1Journal 16Unranked 20
YearRankTypeTitle / Venue / Authors
2024 conf
CUG
J. Mark Bull, Andrew Coughtrie, Deva Deeptimahanti, Mark Hedley, Caoimhín Laoide-Kemp, Christopher M. Maynard, Harry Shepherd, Sebastiaan van de Bund, Michèle Weiland, Benjamin Went
2024 J jnl
CoRR
J. Mark Bull, Andrew Coughtrie, Deva Deeptimahanti, Mark Hedley, Caoimhín Laoide-Kemp, Christopher M. Maynard, Harry Shepherd, Sebastiaan van de Bund, Michèle Weiland, Benjamin Went
2020 J jnl
CoRR
Nick Brown, Oliver Thomson Brown, J. Mark Bull
2020 C conf
CLUSTER
Marcos Maroñas, Xavier Teruel, J. Mark Bull, Eduard Ayguadé, Vicenç Beltran
2020 J jnl
CoRR
Nick Brown, Ludovic Anthony Richard Capelli, J. Mark Bull
2020 J jnl
CoRR
Ludovic Anthony Richard Capelli, Zhenjiang Hu, Timothy A. K. Zakian, Nick Brown, J. Mark Bull
2015 conf
WHPCF@SC
Mark Tucker, J. Mark Bull
2014 J jnl
CoRR
Mark Tucker, J. Mark Bull
2014 J jnl
Algorithmic Finance
Mark Tucker, J. Mark Bull
2014 J jnl
Int. J. High Perform. Comput. Appl.
Iain Bethune, J. Mark Bull, Nicholas J. Dingle, Nicholas J. Higham
2012 conf
IWOMP
J. Mark Bull, Fiona Reid, Nicola McDonnell
2012 conf
SC Companion
Mark Tucker, J. Mark Bull
2010 J jnl
Int. J. Parallel Program.
J. Mark Bull, James P. Enright, Xu Guo, Chris M. Maynard, Fiona Reid
2009 conf
IWOMP
J. Mark Bull, James P. Enright, Nadia Ameer
2003 J jnl
Concurr. Comput. Pract. Exp.
J. Mark Bull, Lorna A. Smith, Carwyn Ball, Linday Pottage, Robin Freeman
2001 J jnl
SIGARCH Comput. Archit. News
J. Mark Bull, Darragh O'Neill
2001 A conf
SC
L. A. Smith, J. Mark Bull, Jan Obdrzálek
2001 J jnl
Concurr. Comput. Pract. Exp.
Mark E. Kambites, Jan Obdrzálek, J. Mark Bull
2001 conf
Java Grande
J. Mark Bull, Lorna A. Smith, Linday Pottage, Robin Freeman
2001 B conf
ICPP
Jordi Guitart, Jordi Torres, Eduard Ayguadé, J. Mark Bull
2001 conf
Euro-Par
Allen D. Malony, Graham D. Riley, Bernd Mohr, J. Mark Bull, Tomàs Margalef
2000 J jnl
Concurr. Pract. Exp.
J. Mark Bull, L. A. Smith, Martin D. Westhead, D. S. Henty, R. A. Davey
2000 conf
ICPP Workshops
David J. Hancock, J. Mark Bull, Rupert W. Ford, T. L. Freeman
2000 conf
PARA
T. L. Freeman, David J. Hancock, J. Mark Bull, Rupert W. Ford
2000 conf
Java Grande
J. Mark Bull, Mark E. Kambites
1999 conf
Java Grande
J. Mark Bull, L. A. Smith, Martin D. Westhead, D. S. Henty, R. A. Davey
1999 conf
PP
J. Mark Bull, Rupert W. Ford, Len Freeman, David J. Hancock
1998 conf
Euro-Par
J. Mark Bull
1998 conf
HPCN Europe
J. M. MacLaren, J. Mark Bull
1998 J jnl
Parallel Distributed Comput. Pract.
J. Mark Bull, T. L. Freeman
1997 conf
PP
J. Mark Bull, T. L. Freeman
1997 A conf
International Conference on Supercomputing
Graham D. Riley, J. Mark Bull, John R. Gurd
1996 conf
Software Engineering for Parallel and Distributed Systems
J. Mark Bull
1996 J jnl
Sci. Program.
Michael F. P. O'Boyle, J. Mark Bull
1995 J jnl
Sci. Program.
C. Falcó Korn, J. Mark Bull, Graham D. Riley, P. K. Stansby
1995 conf
PARA
Rupert W. Ford, Andy Nisbet, J. Mark Bull
1994 conf
PARLE
J. Mark Bull, T. L. Freeman
1994 J jnl
Adv. Comput. Math.
J. Mark Bull, T. L. Freeman
1994 A conf
International Conference on Supercomputing
Gregory K. Egan, Graham D. Riley, J. Mark Bull
1994 conf
PARA
T. L. Freeman, J. Mark Bull
1992 conf
CONPAR
J. Mark Bull, T. L. Freeman
docs/macho_extractors_README.md
← Index docs/macho_extractors_README.md markdown
# MachO Extractors for RedB

This document describes the MachO extractors implementation for the RedB binary analysis framework.

## Overview

The MachO extractors provide comprehensive analysis capabilities for Mach-O binaries (macOS, iOS, watchOS, tvOS executables) following the same pattern as the existing PE extractors. The implementation uses the `machofile` library located in the `docs/` folder.

## Architecture

### Main Components

1. **MachOExtractor** (`redb/extractors/macho_extractor.py`)
   - Abstract base class for all MachO extractors
   - Handles MachO file parsing and common functionality
   - Supports both single-architecture and Universal/FAT binaries

2. **Individual Extractors** (`redb/extractors/macho_extractors/`)
   - `macho_features.py` - Basic MachO header and metadata
   - `macho_segments.py` - Segment information and analysis
   - `macho_imports.py` - Imported functions and libraries
   - `macho_exports.py` - Exported symbols
   - `macho_dylibs.py` - Dynamic library dependencies
   - `macho_signature.py` - Code signing information

3. **Data Models** (`redb/models/dataclasses.py`)
   - MachO-specific dataclasses for structured data storage
   - Compatible with Elasticsearch and ClickHouse exporters

## Features

### Supported Binary Types
- Single-architecture Mach-O binaries (32-bit and 64-bit)
- Universal/FAT binaries with multiple architectures
- All major CPU architectures (x86, x86_64, ARM, ARM64)

### Extracted Information

#### MachO Features
- Header information (magic, CPU type, file type, flags)
- Architecture detection
- Entry point information
- UUID
- Version information
- Signing status
- Encryption status
- Counts (segments, dylibs, imports, exports)

#### Segments
- Segment names and properties
- Virtual addresses and sizes
- File offsets and sizes
- Protection flags
- Entropy calculation
- Segment hashes (MD5, SHA256)

#### Imports
- Imported function names
- Library dependencies
- Import counts and statistics

#### Exports
- Exported symbol names
- Export counts and statistics

#### Dynamic Libraries
- Dylib names and paths
- Version information
- Timestamps
- Load command types

#### Code Signing
- Signing status
- Certificate information
- Entitlements
- Code directory details

## Usage

### Basic Usage

```python
from redb.extractors.macho_extractors import MachOFeaturesExtractor

# Create extractor
extractor = MachOFeaturesExtractor(
    filepath="/path/to/macho/binary",
    log=logger
)

# Extract data
features = extractor.extract()

# Export to databases
extractor.export_data()
```

### Testing

Use the provided test script to verify functionality:

```bash
python test_macho_extractors.py /path/to/macho/binary
```

## Implementation Details

### Universal Binary Support

The extractors handle Universal/FAT binaries by:
1. Detecting FAT binary format
2. Extracting individual architectures
3. Providing unified interface for both single and multi-arch binaries
4. Supporting architecture-specific extraction

### Error Handling

- Graceful handling of malformed binaries
- Comprehensive logging for debugging
- Fallback mechanisms for missing data
- Exception handling for corrupted files

### Performance Considerations

- Lazy parsing of MachO structures
- Efficient memory usage for large binaries
- Cached property access for repeated queries
- Optimized data extraction patterns

## Integration

### Database Exporters

The extractors support both Elasticsearch and ClickHouse exporters:

- **Elasticsearch**: JSON document storage with full-text search
- **ClickHouse**: Columnar storage for analytical queries

### Schema Compatibility

All extractors follow the established schema patterns:
- Consistent field naming
- Proper data types
- Timestamp handling
- Hash field inclusion

## Future Enhancements

Potential areas for improvement:

1. **Additional Extractors**
   - MachO resources extraction
   - Symbol table analysis
   - Relocation information
   - Thread state analysis

2. **Enhanced Analysis**
   - Malware detection patterns
   - Behavioral analysis
   - Similarity hashing
   - YARA rule integration

3. **Performance Optimizations**
   - Parallel processing for multi-arch binaries
   - Streaming data processing
   - Memory-mapped file access

## Dependencies

- `machofile` library (included in `docs/`)
- Standard Python libraries (hashlib, datetime, etc.)
- RedB framework components

## Contributing

When adding new MachO extractors:

1. Follow the established pattern in existing extractors
2. Add appropriate dataclasses to `dataclasses.py`
3. Update the enum tags in `enum.py`
4. Include comprehensive error handling
5. Add tests for new functionality
6. Update this documentation

## Troubleshooting

### Common Issues

1. **Import Errors**: Ensure `machofile` library is accessible
2. **Memory Issues**: Large Universal binaries may require significant memory
3. **Corrupted Files**: Malformed MachO files may cause parsing errors
4. **Architecture Mismatch**: Some features may not be available for all architectures

### Debugging

Enable debug logging to see detailed extraction process:

```python
import logging
logging.basicConfig(level=logging.DEBUG)
```

## License

This implementation follows the same license as the main RedB project.