Using uploader (kup) uploader (kup) is a Perl program that was written for the sole purpose of making sure that any software uploaded to is cryptographically verified against a list of pre-approved maintainers. If you are a kernel developer and you’d like to be able to upload tarballs, patches or any other data to, this document is for you.

Before you begin


Do not upload non-Open Source software without special prior permission. This includes binaries of software intended to be Open Source for which source code isn’t actually available yet. IN PARTICULAR, do not upload non-Open Source cryptographic software, or cryptographic binaries from source not available on the Internet, under any circumstances. This is absolutely essential.

If you have not yet set up your ssh access, first see How to set up your ssh access.

Obtaining kup

Kup is packaged for most distributions and is probably installable using your distribution’s package management tools. For example, on Fedora it is installable using:

yum install kup


Make sure the version of kup is at least 0.3.6, as earlier versions will NOT work.

You can also check out the git tree to obtain the latest version of kup:

git clone git://

Configuring kup

Set your $HOME/.kuprc as follows (requires kup >= 0.3.6):

host =
subcmd = kup-server

That should be all you need to do. You may test things by running:

kup info

You should see the following or similar output:

kup-server 0.3.6 (gitolite integrated)

ls                       /*
put/rm/mv/mkdir          /testing/*
put/rm/mv/mkdir          /pub/linux/kernel/people/yourname/*

If you get an error in return, check to make sure you have correctly set up your ssh access (see How to set up your ssh access). Additionally, if you see a long list of gitolite repositories instead, make sure your version of kup is 0.3.6 or above, and that you have correctly set up your ~/.kuprc to specify subcmd=kup-server.

If it is still not working for you, please email for further assistance.

Uploading with kup

Please carefully read the manpages provided by kup to familiarize yourself with the procedure:

man kup

You can test kup by uploading into the special /testing directory:

kup put foo.tar foo.tar.asc /testing/foo.tar.gz

If you get “invalid signature”, the most likely cause is that your signature is against the compressed version of the archive. KUP expects the signature to be against .tar, not .tar.?z. It uncompresses the file, then runs the verification check, then recompresses in multiple formats.

Please remove anything you put there after you are done:

kup rm /testing/foo.tar.gz

Anything uploaded to ‘’/pub’’ will be rsynced to frontends and will be available on after a few minutes.


If you find that some directories do not have the correct permissions, or if you need to set up groups in order to allow multiple developers write access, please send a request to

Auto-publishing with git-archive-signer

In addition to direct kup usage, we also provide an automated mechanism to publish archives from repository tags. The process uses kup behind the scenes, but allows skipping most of the above steps once it is properly set up.

To start using this method:

  1. Download the git-archive-signer script from the helpers tree. You should not need to edit that file for it to work in most situations.
  2. Sign the tag (or tags) that you would like published.
  3. Send a request to asking to enable auto-publishing automation. Include the following details:
    • the git tree on to use as origin
    • the username of each person who will be publishing the releases
    • the location on where the results should be published.
  4. The backend job runs every 5 minutes and you will get a notification by email if your job has succeeded or failed.