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.

Sign up for GitHub

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

Jump to bottom

Update chapter14.txt #220

Closed
wants to merge 1 commit into from
Closed

Update chapter14.txt #220

wants to merge 1 commit into from

Conversation

theAtropos4n6
Copy link
Collaborator

No description provided.

@github-actions GitHub Actions
Copy link

@check-spelling-bot Report

🔴 Please review

See the 📂 files view, the 📜action log, or 📝 job summary for details.

Unrecognized words (138) 
Adroid
Akkaya
Alabdulsalam
Alassafi
Alenezi
Almolhis
Alsagri
analisys
appications
athoritative
Atlam
Baggili
Baig
Berla
botnet
Bouchaud
Breitinger
BSides
budle
CFCE
chapterj
Chattopadhyay
Chehab
Chernyshev
collaboratecom
commmands
comnet
COMST
Contiki
CSCI
cyberattack
Dehghantanha
DHFS
diin
direcotries
doi
Dragonas
elcomsoft
encompasing
Epifani
Epiphaniou
Evangelos
FAIo
followingt
forenisc
fsidi
garadi
Gmdsoft
Grupposo
Guizani
Habtamu
Hadi
hal
Hannay
Hashem
Hemdan
Heraklion
Hexordia
HIKVISION
Hyunji
IACIS
ICGS
icst
IJDCF
Imran
infotainment
Ioa
Jazani
Kangyoun
Karabiyik
Katrin
Kazmi
Kechadi
Kerai
Khac
LEAHY
Ledit
Lutta
Markakis
Mattia
MCCE
Mccormack
MCME
Mirai
MNT
MOBI
Montasari
Multijurisdictional
Nikoloudakis
Noura
NTMS
Oriwoh
Pallis
Panagiotakis
Paraben
Phill
proactively
Rabadia
Rehman
rnes
Sandvik
Sangjin
Sansurooah
Sedky
Seo
Servida
Shenoi
Sikos
Skynet
smartphones
smartwatch
Snapchat
spredsheets
Spyder
stakeholders
Stoyanova
subnetting
subsituted
Sustainability
Szewczyk
Tik
tprimary
traige
uninstalls
Vantroys
wal
webinar
Worksharing
WSNs
Xiaomi
Yaacoub
Yaqoob
Yirang
Youn
Zawoad
zena
zhiliaoapp
Zulkipli
To accept these unrecognized words as correct, you could run the following commands

... in a clone of the git@github.com:Digital-Forensics-Discord-Server/TheHitchhikersGuidetoDFIRExperiencesFromBeginnersandExperts.git repository
on the theAtropos4n6-patch-5 branch (ℹ️ how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/prerelease/apply.pl' |
perl - 'https://github.com/Digital-Forensics-Discord-Server/TheHitchhikersGuidetoDFIRExperiencesFromBeginnersandExperts/actions/runs/8791061200/attempts/1'

OR

To have the bot accept them for you, comment in the PR quoting the following line:
@check-spelling-bot apply updates.

Forbidden patterns 🙅 (1)

In order to address this, you could change the content to not match the forbidden patterns (comments before forbidden patterns may help explain why they're forbidden), add patterns for acceptable instances, or adjust the forbidden patterns themselves.

These forbidden patterns matched content:

s.b. GitHub

(?<![&*.]|// |type )\bGithub\b(?![{)])
Pattern suggestions ✂️ (1)

You could add these patterns to .github/actions/spelling/patterns.txt:

# Automatically suggested patterns
# hit-count: 1 file-count: 1
# Non-English
[a-zA-Z]*[ÀÁÂÃÄÅÆČÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝßàáâãäåæčçèéêëìíîïðñòóôõöøùúûüýÿĀāŁłŃńŅņŒœŚśŠšŜŝŸŽžź][a-zA-Z]{3}[a-zA-ZÀÁÂÃÄÅÆČÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝßàáâãäåæčçèéêëìíîïðñòóôõöøùúûüýÿĀāŁłŃńŅņŒœŚśŠšŜŝŸŽžź]*|[a-zA-Z]{3,}[ÀÁÂÃÄÅÆČÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝßàáâãäåæčçèéêëìíîïðñòóôõöøùúûüýÿĀāŁłŃńŅņŒœŚśŠšŜŝŸŽžź]|[ÀÁÂÃÄÅÆČÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝßàáâãäåæčçèéêëìíîïðñòóôõöøùúûüýÿĀāŁłŃńŅņŒœŚśŠšŜŝŸŽžź][a-zA-Z]{3,}
Errors (4)

See the 📂 files view, the 📜action log, or 📝 job summary for details.

❌ Errors Count
ℹ️ candidate-pattern 1
❌ check-file-path 1
❌ forbidden-pattern 1
⚠️ non-alpha-in-dictionary 4

See ❌ Event descriptions for more information.

If the flagged items are 🤯 false positives

If items relate to a ...

  • binary file (or some other file you wouldn't want to check at all).

    Please add a file path to the excludes.txt file matching the containing file.

    File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

    ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

  • well-formed pattern.

    If you can write a pattern that would match it,
    try adding it to the patterns.txt file.

    Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

    Note that patterns can't match multiline strings.

🚂 If you're seeing this message and your PR is from a branch that doesn't have check-spelling,
please merge to your PR's base branch to get the version configured for your repository.

github-advanced-security[bot]
github-advanced-security bot found potential problems Apr 22, 2024
View reviewed changes
manuscript/chapter14.txt
@@ -58,7 +59,7 @@
Now that the reader has an understanding of the challenges associated with IoT Forensics, it is time to explore some of the skills required for conducting digital investigations of IoT products. As identified by Stoyanova et al., (2020) (See Fig. 1), IoT Forensics is divided into IoT device-level forensics, network forensics, and cloud forensics. One can be really proficient in one of these three disciplines and lack expertise in the other two, or any other possible combination may apply. A metaphor for an investigator in IoT forensics might be a [UFC](https://www.ufc.com/) fighter. Of course, this doesn't mean one should punch sensors and devices out of the way, nor grapple with the refrigerator. However, it implies that one needs develop and combine cross-disciplined investigative competencies to succeed in this field of digital forensics, similar to how a UFC fighter practices different fighting disciplines to enhance competitiveness. Each of the three categories, along with some of the skills that a practitioner needs to develop while diving into this field, are presented below:

{width: 50%}
![Components of the IoT Forensics - Stoyanova et al., 2020](resources/Ch14/Stoyanova.PNG)
![Components of the IoT Forensics - Stoyanova et al., 2020](resources/Ch14/Stoyanova.png)

Check failure

Code scanning / check-spelling

Unrecognized Spelling Error

Stoyanova is not a recognized word. (unrecognized-spelling)
manuscript/chapter14.txt
@@ -58,7 +59,7 @@
Now that the reader has an understanding of the challenges associated with IoT Forensics, it is time to explore some of the skills required for conducting digital investigations of IoT products. As identified by Stoyanova et al., (2020) (See Fig. 1), IoT Forensics is divided into IoT device-level forensics, network forensics, and cloud forensics. One can be really proficient in one of these three disciplines and lack expertise in the other two, or any other possible combination may apply. A metaphor for an investigator in IoT forensics might be a [UFC](https://www.ufc.com/) fighter. Of course, this doesn't mean one should punch sensors and devices out of the way, nor grapple with the refrigerator. However, it implies that one needs develop and combine cross-disciplined investigative competencies to succeed in this field of digital forensics, similar to how a UFC fighter practices different fighting disciplines to enhance competitiveness. Each of the three categories, along with some of the skills that a practitioner needs to develop while diving into this field, are presented below:

{width: 50%}
![Components of the IoT Forensics - Stoyanova et al., 2020](resources/Ch14/Stoyanova.PNG)
![Components of the IoT Forensics - Stoyanova et al., 2020](resources/Ch14/Stoyanova.png)

Check failure

Code scanning / check-spelling

Unrecognized Spelling Error

Stoyanova is not a recognized word. (unrecognized-spelling)
@AndrewRathbun
Copy link
Member

@theAtropos4n6 is this a stale PR now? Should we just close this?

@theAtropos4n6
Copy link
Collaborator Author

Yeap, please do not approve this commit. I replaced the file completely

@AndrewRathbun AndrewRathbun self-assigned this Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@AndrewRathbun AndrewRathbun

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@theAtropos4n6 @AndrewRathbun