On 10/02/16 17:31, Carsten Haitzler wrote: > On Wed, 10 Feb 2016 09:31:26 +0000 Tom Hacohen <t...@osg.samsung.com> said: > >> Hey, >> >> I reverted this patch. This patch is absolutely wrong, this is not the >> right place for it. Furthermore, for whatever reason, this patch broke >> key sync, so not only that it's wrong, but it didn't fix anything. >> >> I currently have two keys for apache, neither of them is this one. >> Please just make sure you know what the right key is, and that beber >> agrees (because you guys keep on messing up the keys, he's removing >> keys, you are adding them in the wrong place). >> >> Once you are in agreement, send me or him the key, and we'll update it >> accordingly. >> >> Again, this commit DID NOT fix anything, because it was never applied. >> So if everything works, it's because of what I did a while back, if it >> doesn't, let me know and we can fix it. Just please stop employing this >> hack. > > what did you do to make key sync STOP working with an apache user? it worked > when i originally set up dokuwiki. you must have done something to make it > explicitly not work. i kept asking you how to update the dev keys and you > didnt > know how. now you say you did something? what? where?
Huh? when did I ever say I didn't know how. Of course I know how to update the keys, I deal with gitolite all the time. I have no idea what you did to break it. Maybe it was the fact that a user called apache already exists outside of the user system, the same way I guess creating a new dev account for "root" would fail. Not entirely sure though. > > the dokuwiki commit-back keeps breaking and losing its ssh keys. go back to > the > old fashioned way of having a key in apache's ~/.ssh and be done with it. it > works and is what everyone knows. i have no idea how it's meant to work > otherwise > > just make the danged wiki work and keep working without it falling over then > no > one having any idea how to fix it. We elected Beber as our sysadmin. He's been doing a good job. Things fail sometimes, and we can talk to him to fix them. I have no idea about the setup, he does. All I know (hence my comment) is that you and him keep on reverting and mangling each other's work without talking to each other. > > if a setup is so complex no one can figure it out - it's broken. if it breaks > then who cares about security when the system is essentially non-functioning. > great - it's secure by it never actually working. that's useless. > Again, I'm not in charge of the system, I don't know the setup in its entire, but I do know what you did was wrong for our setup, and unnecessary. Contacting me would have solved it immediately (which as shown, when I saw your hack, I migrated it to the right place and that made dokuwiki work again). Anyhow, beber says he fixed the issue, let's see. -- Tom. >> On 05/02/16 07:52, Carsten Haitzler (Rasterman) wrote: >>> raster pushed a commit to branch master. >>> >>> http://git.enlightenment.org/admin/devs.git/commit/?id=a4ff9b51b3e7ca783c578cced5f3ebecd14c58ee >>> >>> commit a4ff9b51b3e7ca783c578cced5f3ebecd14c58ee >>> Author: Carsten Haitzler (Rasterman) <ras...@rasterman.com> >>> Date: Fri Feb 5 16:50:50 2016 +0900 >>> >>> Apache user is back - whatever keeps happing on www.e.org to stop the >>> wiki from being able to commit and losing its ssh creds is now just >>> too painful. do it the good olde way that everyone can deal with - ssh >>> pub keys for apache user. >>> --- >>> developers/apache/id_rsa.pub | 1 + >>> developers/apache/info.txt | 7 +++++++ >>> 2 files changed, 8 insertions(+) >>> >>> diff --git a/developers/apache/id_rsa.pub b/developers/apache/id_rsa.pub >>> new file mode 100644 >>> index 0000000..adaf73c >>> --- /dev/null >>> +++ b/developers/apache/id_rsa.pub >>> @@ -0,0 +1 @@ >>> +ssh-rsa >>> AAAAB3NzaC1yc2EAAAADAQABAAACAQC5RDOkanPfecjzSiUQI1EdD/n958r/15Ag3f00u8bhdw1PozipuJwgJEQ >>> +tDpD2l9q0IqbBzgcDv0Ct1bBQclFH28piwLsPkMhz7plsaM2O1xTKi3rmfQg5EMkCxJV8raGs6zHj4F/ov7N1Qn8EmLy2Nl8Ipg9k63PZNm3tKH >>> +rSWgmFKwuZPEOWYa1cQQ6h5boVvvdsniB8OAWM19tCBuvuJjgmz8kEGpdd2Z1C01NWInKC4ic6nu7ZFqHHGc4aEmxjYe7sIo48aIreWk2Y6a1x4 >>> +RYv4oEQTZeYUYnTCtZF9SEh9ix4GFsJsKtkk0iRN81Fa >>> +zDrsYWyvSwMskHm2hiiDd9n4P1K5c5PUZKjOn0 >>> +Ihb4nocepm9zIIZkH79LNlKF/DArMIIBnOYRhVBuiTAqi26WDh+9 >>> +iXuCrXxxGcJdsQ7NkXeNwh2VZgUqejlYaD2 [...] diff --git >>> a/developers/apache/info.txt b/developers/apache/info.txt new file mode >>> 100644 index 0000000..c5a5e3b >>> --- /dev/null >>> +++ b/developers/apache/info.txt >>> @@ -0,0 +1,7 @@ >>> +Login: apache >>> +IRC Nick: N/A >>> +Cloak: N/A >>> +Name: Wiki Web Bot >>> +WWW: http://www.enlightenment.org >>> +E-Mail: n...@anlightenment.org >>> +Managing: www-content >>> >> >> >> ------------------------------------------------------------------------------ >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >> _______________________________________________ >> enlightenment-devel mailing list >> enlightenment-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> > > ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
