Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Processus index must be 4 bytes #4455

Merged
merged 1 commit into from
Jul 12, 2024
Merged

Processus index must be 4 bytes #4455

merged 1 commit into from
Jul 12, 2024

Conversation

guedou
Copy link
Member

@guedou guedou commented Jul 9, 2024

Here is a fix for OSS-fuzz finding #70115.

Copy link

codecov bot commented Jul 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.35%. Comparing base (a1afb9a) to head (fcf2a9b).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4455      +/-   ##
==========================================
- Coverage   81.46%   81.35%   -0.12%     
==========================================
  Files         353      353              
  Lines       84477    84652     +175     
==========================================
+ Hits        68822    68868      +46     
- Misses      15655    15784     +129     
Files Coverage Δ
scapy/utils.py 73.24% <100.00%> (+0.10%) ⬆️

... and 8 files with indirect coverage changes

@guedou guedou force-pushed the guedou/20240708/epb-crash branch from 966eaa3 to b884671 Compare July 9, 2024 08:45
@guedou guedou force-pushed the guedou/20240708/epb-crash branch from c40adc4 to fcf2a9b Compare July 11, 2024 08:18
@guedou guedou added this to the 2.6.0 milestone Jul 11, 2024
@p-l- p-l- merged commit 836e4d5 into master Jul 12, 2024
25 checks passed
@p-l- p-l- deleted the guedou/20240708/epb-crash branch July 12, 2024 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants