Issue 3526 - ssh key
Summary: ssh key
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Website general issues (show other issues)
Version: current
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: issues@www
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-17 12:26 UTC by Unknown
Modified: 2004-03-22 16:09 UTC (History)
2 users (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
ssh public key (329 bytes, text/plain)
2002-03-17 14:04 UTC, Unknown 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-03-17 12:26:41 UTC 
all modules
Comment 1 Unknown 2002-03-17 14:04:58 UTC 
Created attachment 1224 [details]
ssh public key
Comment 2 lsuarezpotts 2002-03-18 00:08:27 UTC 
Karl,
First, before we can even consider accepting your key, we need:
1. Your project lead to let us know to accept your key. No key is 
accepted without the project leads prior authorization.
2. After that, you need to submit a copyright form to Sun. 
3. You then need to submit the key as you have done.
Please complete steps 1&2 above before submitting a key.
Thanks
Louis Suarez-Potts
Community Manager
Comment 3 stx123 2002-03-22 21:14:10 UTC 
Michael, another doc writer?
Comment 4 ooo 2002-03-25 11:34:36 UTC 
Karl, please state for which project you have commit rights. I don't
know about you and cannot backup your request, but at least one
project lead has to backup your request.
Comment 5 stx123 2002-03-26 21:55:44 UTC 
Karl stated in an email:
Hello,
I had missunderstood a howto. I only wanted to update my 641c sources for 
testing, but anoncvs did not work. so i tried to get the code by ssh. 
Please delete my request.
Thanks.
Yours Karl
Comment 6 michael.bemmer 2003-03-12 14:21:07 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 7 michael.bemmer 2003-03-12 14:21:33 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 8 michael.bemmer 2003-03-12 14:21:39 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 9 michael.bemmer 2003-03-12 14:39:13 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.
Comment 10 michael.bemmer 2003-03-12 14:39:35 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.
Comment 11 stx123 2004-03-22 16:09:58 UTC 
For technical reasons we have to move the issue to another subcomponent tan 'www'.
Sorry for bothering you with this generated notification message. There is no
need for any action from yor side.
Thanks for your understanding, Stefan