# Planning to eliminate the signature file
**URL:** https://drone.discourse.group/t/planning-to-eliminate-the-signature-file/6023
**Category:** Drone Support
**Created:** [March 19, 2017, 9:23am UTC](https://drone.discourse.group/t/planning-to-eliminate-the-signature-file/6023 "2017-03-19T09:23:30Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)
#### Post date: [March 19, 2017, 9:23am UTC](https://drone.discourse.group/t/planning-to-eliminate-the-signature-file/6023/1 "2017-03-19T09:23:30Z")
We are actively trying to eliminate the requirement for signing the yaml file. See [https://github.com/drone/drone/issues/1935](https://github.com/drone/drone/issues/1935)
The initial implementation implements a simple approval system that blocks a build if the pull request attempts to alter the yaml and the following conditions are met:
1. hook is a pull request
2. pull request author is not a project member (rw access)
3. pull request yaml does not match target branch
4. secrets exists, with verification required
This prevents the attack vector where a bad actor submits a pull request that attempts to expose secrets, while removing the need to sign the yaml file.
With the basic implementation in place, we are now discussing more robust workflows for blocking builds and how drone should behave by deafult. I would love community feedback and ideas, but would ask that everyone read the following issues carefully prior to giving feedback, so that we don’t end up having to repeat myself 🙂
- [https://github.com/drone/drone/issues/1935#issuecomment-287590061](https://github.com/drone/drone/issues/1935#issuecomment-287590061)
- [https://github.com/drone/drone/issues/1971](https://github.com/drone/drone/issues/1971)
---
### Author:  [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)
#### Post date: [March 19, 2017, 9:23am UTC](https://drone.discourse.group/t/planning-to-eliminate-the-signature-file/6023/2 "2017-03-19T09:23:34Z")