pear:rfc:pear_package_release_protocol
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| pear:rfc:pear_package_release_protocol [2011/04/06 10:59] – external edit 127.0.0.1 | pear:rfc:pear_package_release_protocol [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| I'd like a new protocol added to the channels that would indicate if a channel supported remotely pushing releases. This would be in the channel.xml file and would be indicated by something like | I'd like a new protocol added to the channels that would indicate if a channel supported remotely pushing releases. This would be in the channel.xml file and would be indicated by something like | ||
| - | < | + | |
| - | <baseurl type=" | + | |
| - | </ | + | <baseurl type=" |
| + | </ | ||
| Protocol overview: | Protocol overview: | ||
| - | 1. The client sends a pre-flight request, containing the releasing maintainer' | + | |
| - | 2. The channel issues a one-time ticket for the release. | + | - The client sends a pre-flight request, containing the releasing maintainer' |
| - | 3. The client then sends the release, ssh encrypted to the server, along with the ticket they were issued. | + | |
| - | 4. The server receives the release and checks the ticket, decrypts with the user's public key, and then runs a simplechannelserver release command. | + | |
| + | | ||
| Finer points, | Finer points, | ||
pear/rfc/pear_package_release_protocol.1302087566.txt.gz · Last modified: 2017/09/22 13:28 (external edit)