enbility / ship-go / 16100038350

95%

Build Type

push

github

Committed by DerAndereAndi

Commit Message

refactor: improve WebSocket message size limits and reorganize documentation

- Fix misleading MaxMessageSize constant (was used as buffer size, not message limit)
- Change MaxMessageSize from buffer size (1024) to actual message limit (100KB)
- Remove explicit buffer size configuration (use gorilla/websocket defaults)
- Add SetReadLimit() calls to enforce message size limits for DoS protection
- Add tests for message size validation

Documentation updates:
- Move SHIP analyses from specific-issues/ to detailed-analysis/
- Create comprehensive TLS fragment analysis documentation:
  - TLS_FRAGMENT_ANALYSIS.md: Core analysis with regulatory implications
  - TLS_1024_IMPLEMENTATION_EFFORT.md: Implementation options and effort
  - OpenSSL_Integration_Analysis.md: Feasibility of OpenSSL approach
- Update SPEC_DEVIATIONS.md with refined compliance assessment
- Rename SHIP_Requirements_Analysis.md to SHIP_Installation_Requirements_Analysis.md
- Update all documents to follow new documentation standards
- Add Document Purpose Guide to README_START_HERE.md
- Migrate content from ANALYSIS_HISTORY.md to appropriate documents

Key findings:
- TLS 1024-byte fragment requirement not supported by Go's crypto/tls
- Requirement designed for 2015-2016 era devices with <512KB RAM
- EU CRA and BSI TR-03109 compliance implications documented
- Implementation possible via proxy/sidecar (1-2 weeks) or OpenSSL (3-4 months)

Run Details

3 of 5 new or added lines in 1 file covered. (60.0%)

2 existing lines in 1 file now uncovered.

2583 of 2792 relevant lines covered (92.51%)

88.59 hits per line