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
Add Executable Packing #2151
Add Executable Packing #2151
Conversation
Executable (PE, ELF, ...) packing, complementing *Malware Analysis*.
Added a description with the link.
Completed the link with the #readme anchor.
Made the description comply with the contributing guidelines.
unicorn |
Cfr guidelines.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No lo entiendo ?? Quiere que solo explicalo total y compresivamente
The description is meta. See:
Also, there's five different commits. You might want to combine them into one. |
Hi @catdevnull |
What I mean is that the guidelines suggest talking about the subject of the list instead of the list itself. |
Hi @catdevnull |
I agree, I don't think it's that critical. I just thought it wasn't quite aligned with what the guidelines said.
I can't really define executable packing in one sentence; maybe something along the lines of:
β¦ Executable packing is the art(?) of the different methods of compressing, obfuscating and packing files into an executable file.
|
c9f7039
to
4b3a8e2
Compare
The list description in the list readme needs to be improved. |
Many entries are missing a description. |
Descriptions should not be title-case. |
@sindresorhus Thank you for your remarks.
Edit: I improved it. @sindresorhus : Does it fit in the current state ?
This is still work in progress ; I generate the README from a Zotero knowledge base and I'm progressively filling in entries. Edit: All descriptions are filled in.
Edit: Fixed. |
@catdevnull : FYI ; I added a definition of packing. Thank you for the suggestion. |
@sindresorhus |
https://github.com/dhondta/awesome-executable-packing
This provides a full bibliography, links to packers, unpackers and other related tools for executable formats (PE, ELF, ...). This aims to complement the Malware Analysis list.
By submitting this pull request I confirm I've read and complied with the below requirements π
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting βlooks goodβ or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
Add Name of List
.Add Swift
Add Software Architecture
Update readme.md
Add Awesome Swift
Add swift
add Swift
Adding Swift
Added Swift
- [iOS](β¦) - Mobile operating system for Apple phones and tablets.
- [Framer](β¦) - Prototyping interactive UI designs.
- [iOS](β¦) - Resources and tools for iOS development.
- [Framer](β¦)
- [Framer](β¦) - prototyping interactive UI designs
#readme
.- [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.
Requirements for your Awesome list
That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
awesome-lint
on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.main
, notmaster
.Mobile operating system for Apple phones and tablets.
Prototyping interactive UI designs.
Resources and tools for iOS development.
Awesome Framer packages and tools.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
awesome-name-of-list
.awesome-swift
awesome-web-typography
awesome-Swift
AwesomeWebTypography
# Awesome Name of List
.# Awesome Swift
# Awesome Web Typography
# awesome-swift
# AwesomeSwift
awesome-list
&awesome
as GitHub topics. I encourage you to add more relevant topics.Contents
, notTable of Contents
.Contributing
orFootnotes
sections.https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0
(replace<user>
and<repo>
accordingly).license
orLICENSE
in the repo root with the license text.Licence
section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.unicorn
.contributing.md
. Casing is up to you.Contributing
, positioned at the top or bottom of the main content.Footnotes
section at the bottom of the readme. The section should not be present in the Table of Contents.Example:
- [AVA](β¦) - JavaScript test runner.
Node.js
, notNodeJS
ornode.js
.You can still use Travis for list linting, but the badge has no value in the readme.
Inspired by awesome-foo
orInspired by the Awesome project
kinda link at the top of the readme. The Awesome badge is enough.Go to the top and read it again.