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

Support for patches that add or remove files #28

Open
GoogleCodeExporter opened this issue Apr 18, 2015 · 4 comments
Open

Support for patches that add or remove files #28

GoogleCodeExporter opened this issue Apr 18, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

I noticed that patch.py does not support patches that add or remove files.
Following patch against v245 adds support for this.

Original issue reported on code.google.com by [email protected] on 12 Dec 2014 at 4:25

Attachments:

@techtonik techtonik added this to the 2.16 milestone Feb 13, 2016
joshbeal added a commit to RevealHQ/python-patch that referenced this issue Mar 10, 2016
joshbeal added a commit to RevealHQ/python-patch that referenced this issue Mar 10, 2016
@ghost
Copy link

ghost commented Mar 24, 2016

Hello. I was wondering if there was any timescale for applying and making a release with the create/remove functionality. I'd love to use patch.py (just testing it out for the first time today), and this is a blocker. Is there anything missing in the last patch attached here which is lacking/missing which you need a hand with?

Kind regards,
Roger

@techtonik
Copy link
Owner

@rleigh-dundee hi, glad you find it useful. The last patch lacks a proper security research:

  1. that created files do not fall outside of scope of patch local directory
  2. that API still allows to use patches with absolute paths if people really need them

Patching existing files is already a danger, but creating them opens several new attack vectors. I am not getting time for it, because I am actively looking for a solution to refill my living cost funds, and so far no proposal included the work on patch.py

Actionable items include:

  1. review that filename normalization function is secure
  2. write missing tests for it
  3. run it against existing test suites for filename sanitization (and find those suites)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants