Apache OpenOffice (AOO) Bugzilla – Issue 3863
submission of SSH certificate
Last modified: 2004-03-22 16:08:39 UTC
Hi Louis, please assign access rights appropriate for maintaining the lang/nl project. Best regards, Simon.
Created attachment 1322 [details] SSH certificate
Hi Louis, please ignore the above certificate, the following one is the correct one
Created attachment 1401 [details] SSH key
taska, please send on the second key to ops for uploading. thanks louis
I've submitted this to the operations group (PCN9253). Please, in the future, when you attach keys, make sure they are text/plain; otherwise the server sets a binary mime type and I have to save the key on my local machine just to look at it. Thanks.
Oh, and one more thing- this is not a defect; it's a task. Thanks.
Hi, SSH not working yet, possibly something wrong with the key. Therefore, I am submitting a new one.
Created attachment 1407 [details] yet another SSH key
Simon, I've submitted the old key to ops, but they haven't replied yet. It shouldn't be working yet. I'll let you know when they upload it.
Hi Louis, Hi Taska, OK, now I'm beginning to understand... I inferred Taska mistakenly thought that I had resubmitted the first, 'old' key. So, none of the keys have actually been activated. Taska, can you get the *third* key that I submitted to issue 3863 to ops instead? When generating the keys, I have overwritten the previously existing files. So I will only be able to use the third key. Sorry for the confusion... Best regards, Simon.
No, Simon. I didn't think you submitted the old key. I never submitted the 4/4 key to the operations group. When you submitted the key on 4/17, I submitted that to the operations group, but they have not uploaded it yet. So, it doesn't work yet. On 4/18, you assumed that the 4/17 key had already been uploaded, but that it didn't work, and deleted it. There was nothing wrong with the 4/17 key, but I can replace the request with the 4/18 key instead, since the operations group hasn't uploaded *any* keys yet.
Thanks for your emails Simon- the best way to contact me, in general, is via the issue (especially because it might not always be me- we have several support engineers here). I have indeed updated the internal ops request with the new key.
<copy of what I just wrote in email> Hi, Simon, Apologies. I do not know what is going on. We don't have shell access--that was taken from us--so we have to go through our ops dept., and they don't always move so quickly, esp. if they are dealing with important other issues. The issue has been assigned to the ops person dealing with day-to-day issues, like running the show; he may not be able to handle it until later on this week. I asked for an update. In the meanwhile, just continue to IZ me attachments and we can go on with the site; or, if you prefer, email me to louis@collab.net, and I can handle them that way. Again, sorry for the delay. -louis
This is Complete. Simon, please verify that you can log in! Thanks.
OK, I can login now! Thanks!
As agreed by Louis I will close these resolved fixed support-owned issues now. If you have trouble with that, please re-open the issue.
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