GreyNOC Browser Beta Testing Release

GreyNOC Browser is now entering beta testing.

This release is intended for evaluation and testing, not general use. The goal is to validate core security behavior and identify gaps under real-world conditions.

Scope of This Release

The current build focuses on core browser security architecture:

• Session isolation between targets
• Explicit TLS trust handling
• Revocation-aware behavior
• Fail-closed enforcement in critical paths
• Runtime validation and reporting

These systems are implemented and ready for testing.

Known Limitations

• Media playback is limited due to missing codec support in the current Qt WebEngine runtime
• Trust enforcement is strongest on Windows environments
• Update and release pipeline is implemented but not fully production-grade
• Cross-platform behavior is not fully validated

This is expected for the current phase.

Purpose of Beta

This phase is intended to:

• Validate security behavior under real usage
• Identify edge cases and failure conditions
• Confirm isolation and trust enforcement work as expected
• Expose gaps that are not visible in controlled testing

Testing Focus

Testers should focus on:

• TLS handling and certificate behavior
• Revocation enforcement and failure cases
• Session isolation between different targets
• Any unexpected state leakage or inconsistent behavior
• Situations where the browser allows or blocks incorrectly

Reporting

Report the following:

• Steps to reproduce
• Expected behavior vs actual behavior
• Environment details
• Any logs or diagnostics available

Current Status

• Core architecture: implemented
• Security model: active and enforced
• Runtime codec support: not enabled
• Release pipeline: partially complete

Next Steps

• Improve trust validation depth
• Complete update and release pipeline
• Expand diagnostics and control features
• Validate behavior across environments

This release is for testing the foundation.