Can't access to people with SSH (was: [NOTICE] Windows build machine setted up)
you wrote you had uploaded the SSH keys to id.apache.org, that is a good first step.Next a couple of questions: - which terminal program do you use ? I use putty, and had to generate the keys with puttygen, you also have to remember to configure the terminal program to use SSH (not telnet) and give a path to your part of the key. - What exactly happens ? is your key rejected or do you get some kind of key error ? hrin I am using graphical terminal emulator xfce-terminal, bash and openssh 6.9p1 ... so I need to generate keys : ssh-keygen -t rsa Done. Now I need to start agent and give to it keys: ssh-agent ssh-add I can check if the agent has keys with: ssh-add -L ssh-add -l Now I am going to id webadmin and copy paste here public ssh-key. I am awiting that I can connect: ssh myid@people... or ssh -2 myid@people... to force v2 protocol. The output is: -- Note: logging in to this server with a password has been disabled. Please see : https://blogs.apache.org/infra/entry/committer_shell_access_to_people Remember to load your ssh key:- See: http://linux.die.net/man/1/ssh-add ; See: http://linux.die.net/man/1/ssh-agent Permission denied (publickey). -- I remembered that, I had setted up keys connection some years ago, nowadays I do not have old keys. In that time I had to copy my public key, to .ssh/authorized_keys file on people machine. Now I am not able to do this. Maybe this is the problem. Regards, Michal Hriň /hrin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Can't access to people with SSH (was: [NOTICE] Windows build machine setted up)
On Sunday, August 9, 2015, Michal Hriň h...@apache.org wrote: you wrote you had uploaded the SSH keys to id.apache.org, that is a good first step.Next a couple of questions: - which terminal program do you use ? I use putty, and had to generate the keys with puttygen, you also have to remember to configure the terminal program to use SSH (not telnet) and give a path to your part of the key. - What exactly happens ? is your key rejected or do you get some kind of key error ? hrin I am using graphical terminal emulator xfce-terminal, bash and openssh 6.9p1 ... so I need to generate keys : ssh-keygen -t rsa Done. Now I need to start agent and give to it keys: ssh-agent ssh-add I can check if the agent has keys with: ssh-add -L ssh-add -l Now I am going to id webadmin and copy paste here public ssh-key. I am awiting that I can connect: ssh myid@people... or ssh -2 myid@people... to force v2 protocol. The output is: -- Note: logging in to this server with a password has been disabled. Please see : https://blogs.apache.org/infra/entry/committer_shell_access_to_people Remember to load your ssh key:- See: http://linux.die.net/man/1/ssh-add ; See: http://linux.die.net/man/1/ssh-agent Permission denied (publickey). -- I remembered that, I had setted up keys connection some years ago, nowadays I do not have old keys. In that time I had to copy my public key, to .ssh/authorized_keys file on people machine. Now I am not able to do this. Maybe this is the problem. no now ldap is used (id.apache.org), but I wonder if the problem could be that you have old keys on people. This would normally give you a key invalid error. Since you get the note it seems key is rejected and it therefore falls back to the password, which is blocked. Fastest solution for you is to jump on hip chat with infra, they have the karma to e.g. remove your old keys. rgds jan i Regards, Michal Hriň /hrin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org javascript:; For additional commands, e-mail: dev-h...@openoffice.apache.org javascript:; -- Sent from My iPad, sorry for any misspellings.
Re: [NOTICE] Windows build machine setted up
BTW: Do you still have the access problem with your people@a.o account? If so, we (maybe together with Infra) should solve this. Then you can save the binaries there to indicate that the work comes from an AOO committer and not from somewhere else. hrin Yes, I have still this problems. Solving this will be great. Thanks ! /hrin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [NOTICE] Windows build machine setted up
On 8 August 2015 at 20:21, Michal Hriň h...@apache.org wrote: BTW: Do you still have the access problem with your people@a.o account? If so, we (maybe together with Infra) should solve this. Then you can save the binaries there to indicate that the work comes from an AOO committer and not from somewhere else. hrin Yes, I have still this problems. Solving this will be great. Thanks ! you wrote you had uploaded the SSH keys to id.apache.org, that is a good first step. Next a couple of questions: - which terminal program do you use ? I use putty, and had to generate the keys with puttygen, you also have to remember to configure the terminal program to use SSH (not telnet) and give a path to your part of the key. - What exactly happens ? is your key rejected or do you get some kind of key error ? rgds jan i. /hrin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [NOTICE] Windows build machine setted up
On 07/08/15 09:50, Michal Hriň wrote: Thanks for providing a binary, but I am a bit concerned that a version is made public, before the PMC have even spoken about being ready to make a release candidate or started voting on a release candidate. Is this coordinated with the release manager for 4.1.2 ? Please do not misunderstand me, I think it is great that work is being done, I am just surprised we are ready to go public with 4.1.2 even as a pre-view. hrin OK. Binary is deleted. This was not coordinated, that was only snapshot .. not release candidate. All in all Linux 32bit builds from AOO410 branch are on buildbots, so everybody can downlaod it, this is not secret. Sorry, that I was excited and want to show it publically. no problem you did a good job and I don't see any problem, you did not publish anything official and just provided a new fresh binary for preview and testing if your build env is working as expected and can be used for a Windows release build. Please continue your tests and keep us informed. I'm would be happy if I don't have to prepare windows builds. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [NOTICE] Windows build machine setted up
jan i wrote: Is this coordinated with the release manager for 4.1.2 ? No. It doesn't need to be. Maybe some confusion arose because Michal wrote 4.1.2 Early Preview here and somebody may find the name confusing, but this is clearly Michal's build of the current state of 4.1.2 and it is OK (and actually great, Michal!) to have it. It is like the buildbots output (or anything on people.apache.org): a public, totally unofficial, development version. I didn't download it. I'm collecting information for answering the important part of this discussion (digital signing and access to the system), but this requires digging into the archives more than I had anticipated so it will take a while. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[NOTICE] Windows build machine setted up
Thanks for providing a binary, but I am a bit concerned that a version is made public, before the PMC have even spoken about being ready to make a release candidate or started voting on a release candidate. Is this coordinated with the release manager for 4.1.2 ? Please do not misunderstand me, I think it is great that work is being done, I am just surprised we are ready to go public with 4.1.2 even as a pre-view. hrin OK. Binary is deleted. This was not coordinated, that was only snapshot .. not release candidate. All in all Linux 32bit builds from AOO410 branch are on buildbots, so everybody can downlaod it, this is not secret. Sorry, that I was excited and want to show it publically. /hrin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [NOTICE] Windows build machine setted up
Am 08/07/2015 10:20 AM, schrieb Andrea Pescetti: jan i wrote: Is this coordinated with the release manager for 4.1.2 ? No. It doesn't need to be. Maybe some confusion arose because Michal wrote 4.1.2 Early Preview here and somebody may find the name confusing, but this is clearly Michal's build of the current state of 4.1.2 and it is OK (and actually great, Michal!) to have it. +1 @Michael: When you make sure that the file name like now always contain Early Preview or Early Access or anything far away from a Beta or Release version, then it cannot be mixed-up. So, keep up the good work. :-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[NOTICE] Windows build machine setted up
On Friday, August 7, 2015, Rich Bowen rbo...@rcbowen.com javascript:_e(%7B%7D,'cvml','rbo...@rcbowen.com'); wrote: On 08/07/2015 04:00 AM, Jürgen Schmidt wrote: On 07/08/15 09:50, Michal Hriň wrote: Thanks for providing a binary, but I am a bit concerned that a version is made public, before the PMC have even spoken about being ready to make a release candidate or started voting on a release candidate. Is this coordinated with the release manager for 4.1.2 ? Please do not misunderstand me, I think it is great that work is being done, I am just surprised we are ready to go public with 4.1.2 even as a pre-view. hrin OK. Binary is deleted. This was not coordinated, that was only snapshot .. not release candidate. All in all Linux 32bit builds from AOO410 branch are on buildbots, so everybody can downlaod it, this is not secret. Sorry, that I was excited and want to show it publically. no problem you did a good job and I don't see any problem, you did not publish anything official and just provided a new fresh binary for preview and testing if your build env is working as expected and can be used for a Windows release build. Please continue your tests and keep us informed. I'm would be happy if I don't have to prepare windows builds. I'm finding this conversation perplexing, and, no doubt, I lack some back-story. Surely it's wonderful that someone is producing binaries for folks to try out, right? Why would we want them to be deleted, and not publicized? Binaries are not (as has been discussed DOZENS of times) official releases. And anyone is free to take our code and push out binaries. Can someone explain to me what the problem is here? We should be encouraging the work that Michal is doing, celebrating it, tweeting it, and encouraging everyone and their grandmothers to try out this new build. What am I missing? Since I was the cause, let me explain what I tried to write, I think the work done is very good, and wrote so, and I do not think anybody asked for it to be deleted. My concern was the naming 4.1.2 early preview. Thats sounds official (not as an apache release, but you know that for AOO the binary is downloaded factors more than the release source tar ball) and I do not want a confusion to arise between what the release manager does and what individual committers does. I think Michael is doing a very important job with preparing builds for the upcomming release, his work is known here, so much more reason to be carefull when naming intermidiate builds. Andrea wrote it more direct, this is a michael build based on the 4.1.0 branch, this is totally correct and something a lot of people should test. So I do not think you missed a lot, but as always it is real difficult to write something without getting misinterpreted or misunderstood. rgds jan i. -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Sent from My iPad, sorry for any misspellings.
Re: [NOTICE] Windows build machine setted up
Am 08/07/2015 09:50 AM, schrieb Michal Hriň: Thanks for providing a binary, but I am a bit concerned that a version is made public, before the PMC have even spoken about being ready to make a release candidate or started voting on a release candidate. Is this coordinated with the release manager for 4.1.2 ? Please do not misunderstand me, I think it is great that work is being done, I am just surprised we are ready to go public with 4.1.2 even as a pre-view. hrin OK. Binary is deleted. This was not coordinated, that was only snapshot .. not release candidate. All in all Linux 32bit builds from AOO410 branch are on buildbots, so everybody can downlaod it, this is not secret. Sorry, that I was excited and want to show it publically. /hrin please don't put too much negative interpretion into some answers. Of course, it's great that you create builds from the new branch. It's also OK to publish this as download offer. Unfortunately, I haven't seen the file name structure you have used. But please make sure that you always add a term like Early Preview, Early Access, Dev-Snapshot or something else that cannot be mixed-up with a Beta or Release version. BTW: Do you still have the access problem with your people@a.o account? If so, we (maybe together with Infra) should solve this. Then you can save the binaries there to indicate that the work comes from an AOO committer and not from somewhere else. As said before, please keep up the good work. :-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [NOTICE] Windows build machine setted up
On 08/07/2015 04:00 AM, Jürgen Schmidt wrote: On 07/08/15 09:50, Michal Hriň wrote: Thanks for providing a binary, but I am a bit concerned that a version is made public, before the PMC have even spoken about being ready to make a release candidate or started voting on a release candidate. Is this coordinated with the release manager for 4.1.2 ? Please do not misunderstand me, I think it is great that work is being done, I am just surprised we are ready to go public with 4.1.2 even as a pre-view. hrin OK. Binary is deleted. This was not coordinated, that was only snapshot .. not release candidate. All in all Linux 32bit builds from AOO410 branch are on buildbots, so everybody can downlaod it, this is not secret. Sorry, that I was excited and want to show it publically. no problem you did a good job and I don't see any problem, you did not publish anything official and just provided a new fresh binary for preview and testing if your build env is working as expected and can be used for a Windows release build. Please continue your tests and keep us informed. I'm would be happy if I don't have to prepare windows builds. I'm finding this conversation perplexing, and, no doubt, I lack some back-story. Surely it's wonderful that someone is producing binaries for folks to try out, right? Why would we want them to be deleted, and not publicized? Binaries are not (as has been discussed DOZENS of times) official releases. And anyone is free to take our code and push out binaries. Can someone explain to me what the problem is here? We should be encouraging the work that Michal is doing, celebrating it, tweeting it, and encouraging everyone and their grandmothers to try out this new build. What am I missing? -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [NOTICE] Windows build machine setted up
On Aug 7, 2015 12:04 PM, Marcus marcus.m...@wtnet.de wrote: Maybe Jan was afraid that a new version could come into the public too early, others can see it as new release - and then the problem is just starting: we have to deny this, discussions here and there, and nobody wants to have this mess. I would think we would welcome the publicity. However, all the problems can be easily solved with coordination and communication (e.g., offering binaries only from Apache infra systems like people@a.o, agreeing on file nameing to differentiate clearly from release builds, etc.). Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [NOTICE] Windows build machine setted up
Am 08/07/2015 05:22 PM, schrieb Rich Bowen: On 08/07/2015 04:00 AM, Jürgen Schmidt wrote: On 07/08/15 09:50, Michal Hriň wrote: Thanks for providing a binary, but I am a bit concerned that a version is made public, before the PMC have even spoken about being ready to make a release candidate or started voting on a release candidate. Is this coordinated with the release manager for 4.1.2 ? Please do not misunderstand me, I think it is great that work is being done, I am just surprised we are ready to go public with 4.1.2 even as a pre-view. hrin OK. Binary is deleted. This was not coordinated, that was only snapshot .. not release candidate. All in all Linux 32bit builds from AOO410 branch are on buildbots, so everybody can downlaod it, this is not secret. Sorry, that I was excited and want to show it publically. no problem you did a good job and I don't see any problem, you did not publish anything official and just provided a new fresh binary for preview and testing if your build env is working as expected and can be used for a Windows release build. Please continue your tests and keep us informed. I'm would be happy if I don't have to prepare windows builds. I'm finding this conversation perplexing, and, no doubt, I lack some back-story. Surely it's wonderful that someone is producing binaries for folks to try out, right? Why would we want them to be deleted, and not publicized? absolutely Binaries are not (as has been discussed DOZENS of times) official releases. And anyone is free to take our code and push out binaries. Of course, the official truth is in the source code - this applies also for AOO. But please try to imagine that the AOO users think different. Just a few percent are interested in the source code. But the very most trust in the binaries as nearly no end-user is building from the source code Can someone explain to me what the problem is here? We should be encouraging the work that Michal is doing, celebrating it, tweeting it, and encouraging everyone and their grandmothers to try out this new build. What am I missing? Maybe Jan was afraid that a new version could come into the public too early, others can see it as new release - and then the problem is just starting: we have to deny this, discussions here and there, and nobody wants to have this mess. However, all the problems can be easily solved with coordination and communication (e.g., offering binaries only from Apache infra systems like people@a.o, agreeing on file nameing to differentiate clearly from release builds, etc.). Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[NOTICE] Windows build machine setted up
Hi all, finally I setted up Windows machine for dev builds. I have compiled build from AOO410 branch, for this time only in US and sk language. If nobody have better solution, I can prepare test builds. The only problem is that I cannot access people.a.o machine, I have generated ssh keys and uploaded public key to my id, but connection is still refused. I can upload builds to OneDrive or to our own server, but it has limitted bandwith so somebody need to copy it, to Apache machines (it can't be used for massive downloading). Jan - could you sent to me in private step-by-step guide for dummy about digital signing ? I can play a little with it. (for example with self generated certificate) Thanks everybody! Regards wih wishing good day, Michal Hriň - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[NOTICE] Windows build machine setted up
On Thursday, August 6, 2015, Michal Hriň h...@apache.org javascript:_e(%7B%7D,'cvml','h...@apache.org'); wrote: V Štvrtok, 6. august 2015 o 10:22 +0200, Michal Hriň napísal(a): Hi all, finally I setted up Windows machine for dev builds. I have compiled build from AOO410 branch, for this time only in US and sk language. If nobody have better solution, I can prepare test builds. The only problem is that I cannot access people.a.o machine, I have generated ssh keys and uploaded public key to my id, but connection is still refused. I can upload builds to OneDrive or to our own server, but it has limitted bandwith so somebody need to copy it, to Apache machines (it can't be used for massive downloading). If somebody would like to try en-US 4.1.2 Early Preview https://onedrive.live.com/redir?resid=9CF40FA60FBDCD!293authkey=!AP86Q 1h_P__6LjIithint=file%2cexe https://onedrive.live.com/redir?resid=9CF40FA60FBDCD!293authkey=!AP86Q1h_P__6LjIithint=file%2cexe Thanks for providing a binary, but I am a bit concerned that a version is made public, before the PMC have even spoken about being ready to make a release candidate or started voting on a release candidate. Is this coordinated with the release manager for 4.1.2 ? Please do not misunderstand me, I think it is great that work is being done, I am just surprised we are ready to go public with 4.1.2 even as a pre-view. rgds jan i Jan - could you sent to me in private step-by-step guide for dummy about digital signing ? I can play a little with it. (for example with self generated certificate) Thanks everybody! Regards wih wishing good day, Michal Hriň - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Sent from My iPad, sorry for any misspellings.
Re: [NOTICE] Windows build machine setted up
On Thursday, August 6, 2015, Michal Hriň h...@apache.org wrote: Hi all, finally I setted up Windows machine for dev builds. I have compiled build from AOO410 branch, for this time only in US and sk language. If nobody have better solution, I can prepare test builds. The only problem is that I cannot access people.a.o machine, I have generated ssh keys and uploaded public key to my id, but connection is still refused. I can upload builds to OneDrive or to our own server, but it has limitted bandwith so somebody need to copy it, to Apache machines (it can't be used for massive downloading). Jan - could you sent to me in private step-by-step guide for dummy about digital signing ? I can play a little with it. (for example with self generated certificate) I wrote it in an earlier email, search for digital signing. You need a verisign account and only andrea has a AOO account and you need a simple modification of the build procedure. Andrea wanted to add me earlier but due to I believe some complications it never happened. Anyhow the way I suggested digital signing, was an idea which I tested, but others might have different ideas about how to do it. First step would be to agree on what should be signed (only the setup exe, the runtime exe, the runtime dll and jars). A good digital signing (like my proposal) contain it all. rgds jan i Thanks everybody! Regards wih wishing good day, Michal Hriň - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org javascript:; For additional commands, e-mail: dev-h...@openoffice.apache.org javascript:; -- Sent from My iPad, sorry for any misspellings.
Re: [NOTICE] Windows build machine setted up
V Štvrtok, 6. august 2015 o 10:22 +0200, Michal Hriň napísal(a): Hi all, finally I setted up Windows machine for dev builds. I have compiled build from AOO410 branch, for this time only in US and sk language. If nobody have better solution, I can prepare test builds. The only problem is that I cannot access people.a.o machine, I have generated ssh keys and uploaded public key to my id, but connection is still refused. I can upload builds to OneDrive or to our own server, but it has limitted bandwith so somebody need to copy it, to Apache machines (it can't be used for massive downloading). If somebody would like to try en-US 4.1.2 Early Preview https://onedrive.live.com/redir?resid=9CF40FA60FBDCD!293authkey=!AP86Q 1h_P__6LjIithint=file%2cexe Jan - could you sent to me in private step-by-step guide for dummy about digital signing ? I can play a little with it. (for example with self generated certificate) Thanks everybody! Regards wih wishing good day, Michal Hriň - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
