Author: psharples
Date: Wed Apr 25 19:08:52 2012
New Revision: 1330490
URL: http://svn.apache.org/viewvc?rev=1330490&view=rev
Log:
CMS commit to wookie by psharples
Modified:
incubator/wookie/site/trunk/content/wookie/docs/developer/release-configuration.mdtext
Modified:
incubator/wookie/site/trunk/content/wookie/docs/developer/release-configuration.mdtext
URL:
http://svn.apache.org/viewvc/incubator/wookie/site/trunk/content/wookie/docs/developer/release-configuration.mdtext?rev=1330490&r1=1330489&r2=1330490&view=diff
==============================================================================
---
incubator/wookie/site/trunk/content/wookie/docs/developer/release-configuration.mdtext
(original)
+++
incubator/wookie/site/trunk/content/wookie/docs/developer/release-configuration.mdtext
Wed Apr 25 19:08:52 2012
@@ -1,99 +1,101 @@
-Title: Release Configuration
-Notice: Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
- .
- http://www.apache.org/licenses/LICENSE-2.0
- .
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
-
-# Release configuration and setup
-
-These setup steps only need to be performed on a particular machine once.
-
-Developers using Linux workstations can skip over the references to Cygwin. If
using Windows, install cygwin, including Utils/gnupg and Net/openssh packages.
-
-##Create and install a SSH key
-
- Open a shell window. If using Windows, open a cygwin window.
- Use ssh-keygen to create an SSH key.
-
-Follow the latest steps and guides on the [ASF
website](http://www.apache.org/dev/openpgp.html#generate-key) as you should NOT
be using SHA1 and new keys MUST be at least 4096 bits.
-
- $ ssh-keygen -t rsa -b 4096
-
-Program defaults should be fine. No passphrase is required for the ssh key
generation. The keys will be saved in ~/.ssh/id_dsa (private) and
~/.ssh/id_dsa.pub (public).
-
-See [Authenticating By Public Key
(OpenSSH)](http://www.networknewz.com/networknewz-10-20030707AuthenticatingbyPublicKeyOpenSSH.html)
for a good description on why and how to perform this task.
-
- 1. SCP your SSH public key ~/.ssh/id_dsa.pub created in last step to
~/id_dsa.pub on people.apache.org.
-
- $ cd ~/.ssh
- $ scp id_dsa.pub @people.apache.org:id_dsa.pub
- $ You will be prompted for your password.
-
- 2. Use ssh to login to people.apache.org
-
- $ cd ~
- $ ssh @people.apache.org
-
-At this point, you will still be prompted for your password.
-
- 1. Create a ~/.ssh folder in your home directory on people.apache.org and
change its file mode to 700.
-
- $ mkdir ~/.ssh
- $ chmod 700 ~/.ssh
-
- 2. Move or append ~/id_dsa.pub to ~/.ssh/authorized_keys and change its file
mode to 600.
-
- $ mv ~/id_dsa.pub ~/.ssh/authorized_keys $ chmod 600 ~/.ssh/authorized_keys
- *Each public key in the authorized_keys spans only one line.
- For example: "ssh-dss AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA==
dsa-key-20071107"
- '#' in the first column is a comment line.*
-
- 3. Exit out of this ssh session.
-
- 4. Start a new ssh session. No login should be required this time due to the
private ssh key on your local box matching up with the public ssh key in your
home directory (~/.ssh).
-
- $ ssh @people.apache.org
-
- If you are still prompted for a password, then you have not set up the ssh
keys properly. Review the steps above and ensure that all of the steps were
followed properly. Or, maybe the instructions are still not quite right and
they still need some adjusting. In that case, please update the instructions
accordingly.
-
-You can alternatively use putty to create and install your ssh key. The
instructions [here](http://people.apache.org/~gmcdonald/ssh_putty.html) outline
the process.
-
-##Create a GPG key
-
-Apache recommend using GNU Privacy Guard to generate keys and sign artifacts.
-
- 1. Open a shell window. If using Windows, open a cygwin window.
-
- 2. Generate a key-pair with gpg, using default key kind ("RSA and RSA") and
keys size (4096).
-
- $ gpg --gen-key
-
- The program's default values should be fine. For the "Real Name" enter
your full name (ie. Stan Programmer). For the "e-mail address" enter your
apache address (ie. [email protected]). You will also be required to enter
a "passphrase" for the GPG key generation. Keep track of this as you will need
this for the Release processing.
-
- 3. The generated keys are stored in $HOME/.gnupg or %HOME%\Application
Data\gnupg subdirectory.
-
- 4. Save the content in this subdirectory to a safe media. This contains your
private key used to sign all the Wookie release materials.
-
- 5. Backup your home directory to another media ||
-
- 6. Add your public key to the [SVN
repository](https://svn.apache.org/repos/asf/incubator/wookie/KEYS). See the
commands describe at the beginning of this KEYS file to perform this task. The
gpg key-pair is used to sign the published artifacts for the Wookie releases.
-
- $ gpg --list-sigs && gpg --armor -- export
-
- The [KEYS](https://svn.apache.org/repos/asf/incubator/wookie/KEYS) file is
updated via normal svn commit procedures.
-
- 7. Submit your public key to a key server. E.g. [MIT](http://pgp.mit.edu/)
-
- 8. Following the instructions in http://people.apache.org/~henkp/trust/ and
ask multiple (at least 3) current Apache committers to sign your public key.
+Title: Release Configuration
+Notice: Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+ .
+ http://www.apache.org/licenses/LICENSE-2.0
+ .
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+
+# Release configuration and setup
+
+These setup steps only need to be performed on a particular machine once.
+
+Developers using Linux workstations can skip over the references to Cygwin. If
using Windows, install cygwin, including Utils/gnupg and Net/openssh packages.
+
+##Create and install a SSH key
+
+ Open a shell window. If using Windows, open a cygwin window.
+ Use ssh-keygen to create an SSH key.
+
+Follow the latest steps and guides on the [ASF
website](http://www.apache.org/dev/openpgp.html#generate-key) as you should NOT
be using SHA1 and new keys MUST be at least 4096 bits.
+
+ $ ssh-keygen -t rsa -b 4096
+
+Program defaults should be fine. No passphrase is required for the ssh key
generation. The keys will be saved in ~/.ssh/id_dsa (private) and
~/.ssh/id_dsa.pub (public).
+
+See [Authenticating By Public Key
(OpenSSH)](http://www.networknewz.com/networknewz-10-20030707AuthenticatingbyPublicKeyOpenSSH.html)
for a good description on why and how to perform this task.
+
+ 1. SCP your SSH public key ~/.ssh/id_dsa.pub created in last step to
~/id_dsa.pub on people.apache.org.
+
+ $ cd ~/.ssh
+ $ scp id_dsa.pub @people.apache.org:id_dsa.pub
+ $ You will be prompted for your password.
+
+ 2. Use ssh to login to people.apache.org
+
+ $ cd ~
+ $ ssh @people.apache.org
+
+At this point, you will still be prompted for your password.
+
+ 1. Create a ~/.ssh folder in your home directory on people.apache.org and
change its file mode to 700.
+
+ $ mkdir ~/.ssh
+ $ chmod 700 ~/.ssh
+
+ 2. Move or append ~/id_dsa.pub to ~/.ssh/authorized_keys and change its file
mode to 600.
+
+ $ mv ~/id_dsa.pub ~/.ssh/authorized_keys
+ $ chmod 600 ~/.ssh/authorized_keys
+
+ *Each public key in the authorized_keys spans only one line.
+ For example: "ssh-dss AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA==
dsa-key-20071107"
+ '#' in the first column is a comment line.*
+
+ 3. Exit out of this ssh session.
+
+ 4. Start a new ssh session. No login should be required this time due to the
private ssh key on your local box matching up with the public ssh key in your
home directory (~/.ssh).
+
+ $ ssh @people.apache.org
+
+ If you are still prompted for a password, then you have not set up the ssh
keys properly. Review the steps above and ensure that all of the steps were
followed properly. Or, maybe the instructions are still not quite right and
they still need some adjusting. In that case, please update the instructions
accordingly.
+
+You can alternatively use putty to create and install your ssh key. The
instructions [here](http://people.apache.org/~gmcdonald/ssh_putty.html) outline
the process.
+
+##Create a GPG key
+
+Apache recommend using GNU Privacy Guard to generate keys and sign artifacts.
+
+ 1. Open a shell window. If using Windows, open a cygwin window.
+
+ 2. Generate a key-pair with gpg, using default key kind ("RSA and RSA") and
keys size (4096).
+
+ $ gpg --gen-key
+
+ The program's default values should be fine. For the "Real Name" enter
your full name (ie. Stan Programmer). For the "e-mail address" enter your
apache address (ie. [email protected]). You will also be required to enter
a "passphrase" for the GPG key generation. Keep track of this as you will need
this for the Release processing.
+
+ 3. The generated keys are stored in $HOME/.gnupg or %HOME%\Application
Data\gnupg subdirectory.
+
+ 4. Save the content in this subdirectory to a safe media. This contains your
private key used to sign all the Wookie release materials.
+
+ 5. Backup your home directory to another media ||
+
+ 6. Add your public key to the [SVN
repository](https://svn.apache.org/repos/asf/incubator/wookie/KEYS). See the
commands describe at the beginning of this KEYS file to perform this task. The
gpg key-pair is used to sign the published artifacts for the Wookie releases.
+
+ $ gpg --list-sigs && gpg --armor -- export
+
+ The [KEYS](https://svn.apache.org/repos/asf/incubator/wookie/KEYS) file is
updated via normal svn commit procedures.
+
+ 7. Submit your public key to a key server. E.g. [MIT](http://pgp.mit.edu/)
+
+ 8. Following the instructions in http://people.apache.org/~henkp/trust/ and
ask multiple (at least 3) current Apache committers to sign your public key.
\ No newline at end of file
