November 2011 - openSUSE Web - openSUSE Mailing Lists

[opensuse-web] New page SDB:Native_IPv6
by Freek de Kruijf 11 Dec '11

11 Dec '11

A page on practical issues with Native IPv6 is almost finished. Please find it here: http://en.opensuse.org/SDB:Native_IPv6 It is in the wiki, so you are invited to add to it. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

2 1

Re: [opensuse-web] Wiki Upgrade Report
by LisufasGnome3 01 Dec '11

01 Dec '11

Hey, Login (de) Wiki: with Opera (11.52) does not. Aborts with an error when forwarding to "https://novell ..." off! with Epiphany does not. Aborts with Error! with Chromium works. Cache and cookies of the browser (Opera) have been cleared! The Wiki Page-Editor (Timestamp, Headline, etc) is completely missing! -- Grüße aus' m Schwabenland ↓ → Lisufa, der Linuxsusefan ↓ ################################## ********************************** ....::: openSUSE Member :::..... ************************************************************* Die 'SuS(i)E' sei mit euch, wo immer ihr auch seid .... *************************************************************

7 16

[opensuse-web] Candidates for being es.o.o wiki admins
by Javier Llorente 30 Nov '11

30 Nov '11

Hello, I know two good candidates for being es.o.o wiki admins; karlggest, who is already involved with es.o.o wiki matters (organisation, translation,etc) and moderator at forosuse.org as well. davmont, a long time translator of the distribution and moderator at forosuse.org too. Please make them admins at es.o.o. I'm already an admin there but not a bureaucrat, that's why I'm asking :-) Thanks! Greetings, Javier

2 1

[opensuse-web] Wiki Upgrade Report
by Matthew Ehle 30 Nov '11

30 Nov '11

Hello, Scott and I have finished upgrading the openSUSE wikis to the latest version of MediaWiki. I have also moved the wikis and the blogs from iChain to Novell Access Manager. The forums will be moved tomorrow. As some of you may have noticed, it was not the smoothest upgrade that we have ever done. It was one of those times where every possible problem decided to happen. However, everything should be working now. I am aware of one minor issue where it may appear that you are logged in after logging out. This is a caching issue, and if you refresh the page, you should be able to see that you are actually logged out of the wiki. Aside from the above issue, please let me know if you find any other problems with the new MW software or with the new SSO solution. -Matt

4 9

[opensuse-web] openSUSE SSO Background
by Matthew Ehle 29 Nov '11

29 Nov '11

Hello All, As we work through some of the growing pains of moving openSUSE.org onto a new SSO (single sign-on) system, I feel it would be a good idea to give some background and technical information as to why we are doing this and what the community should expect. Until yesterday, the openSUSE landing page, blogs, and wikis were running on a product called iChain. iChain is an appliance that acts as an accelerating (caching) proxy that can perform SSO, authorization, and identity injection for applications. While iChain does its job very well, it was discontinued a number of years ago, and we are running into a number of problems with trying to keep it in service. One is that it will not run on any new hardware, and the hardware that it is running on is very old. Another is that it will not work with newer certificates and browsers running newer versions of TLS. Those of you who have tried to log visit openSUSE sites with iOS 5 have probably noticed this already. Because of these issues, we are working on a project to move all iChain sites to Novell Access Manager. Novell Access Manager is the successor to iChain. While it is slightly more buggy than iChain, it has a lot of additional features, and is an actively developed and supported product. Recent builds have also been much more stable and issue-free. It works on a different principle than iChain in that it is based on a federation model. This makes SSO across domains and organizations much easier. For example, openSUSE.org is now single sign-on with novell.com and suse.com. We can also do SAML 2 federation with other sites, if that ever becomes necessary. While we are working on moving the rest of the Novell related sites to Access Manager, we are running in what we call "migration mode". In this setup, iChain continues to handle the authentication for itself and Novell Access Manager. This allows us to retain single sign-on between the two systems as we migrate. As some of you have noticed, a side effect of this is that the openSUSE sites now log in via a Novell-branded login page. When the rest of the sites have been moved off of iChain, we will be able to change back to an openSUSE branded login. This will probably take some time, but we will get there. Since the openSUSE blogs, wikis, and forums were running on a single iChain server that is out of warranty and irreplaceable, they were among the first sites to be moved to Access Manager. While this provides some benefits, it may also provide some headaches as we identify and resolve issues. Thanks for your patience as we continue to work through these problems. -Matt

1 0

[opensuse-web] wiki search index broken ?
by Adrian Schröter 29 Nov '11

29 Nov '11

Hi, I noticed that I am not able to find the factory arm pages. Neither with "factory arm" or just "arm" on http://en.opensuse.org. There is at least Portal:ARM and Portal is enabled by default. could you have a look ? thanks adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-web+owner(a)opensuse.org

2 2

[opensuse-web] openSUSE Web Updates
by Matthew Ehle 22 Nov '11

22 Nov '11

Hello Everyone, I thought you would be interested to hear about what is coming down the pipeline for the openSUSE forums, wikis, and blogs. Here it goes: 1) We are working on getting the wikis and blogs up to the latest versions. Aside from what appears to be some minor cosmetic issues on the wikis, these upgrades have been successful on stage. We are also working on getting the systems themselves patched to the latest versions of Apache and PHP. The blogs will be updated tomorrow on production, and the wikis will be updated on the 28th. 2) We are moving the blogs, wikis, and forum from iChain to Access Manager as part of the project to decommission iChain. The major advantage, other than being on a supported SSO system, is that these sites will now be single sign-on with all of the novell.com sites. We plan on coordinating this move with the wiki upgrade on the 28th, as we had to make a few updates to our extensions and theme to work with Access Manager. 3) As part of this transition, we were able to make the staging sites available to the public! We have been asked about this for years, and switching SSO systems was the perfect opportunity to do it. You may access any of the blogs or wikis by adding "stage" onto the first part of the domain name (enstage.o.o, wwwstage.o.o, lizardsstage.o.o, etc.). I would like to encourage the community to go and test the new wiki software and the integration with Novell Access Manager. -Matt

4 4

Re: [opensuse-web] Re: [opensuse-wiki] openSUSE.org Security Alert
by Matthew Ehle 19 Nov '11

19 Nov '11

>> On 11.11.2011 01:00, Christian Boltz wrote: [using a SVN checkout of MediaWiki and the extensions] >> > At least not without a workaround ;-) >> > >> > What about this: rename the .svn directories to .upstreamsvn and >> > add .svn -> .upstreamsvn symlinks, but do not add the .svn >> > symlinks to git (can git automatically ignore the symlinks named >> > .svn in all subdirectories?) >> > >> > Those symlinks would be easy to create with a script (run it on >> > your git checkout), and are not needed on the webserver. Also >> > renaming the .svn directories to .upstreamsvn on a fresh checkout >> > would be easy with a script. >> > >> > I just tested this - it looks like svn happily accepts the symlink >> > and continues to work. >> > >> > What do you think about this idea? >> >> I think it sounds complicated, > >Yes, but the complicated part would be done by a script (which I'll >happily contribute, I expect <20 lines) + adding ".svn" to gitignore. > >You/Matthew would need to run this script on the "development" machine: >- after git clone to "enable" the .svn directories >- same after git pull, if new directories were added by someone else >- after running svn co / svn up / svn switch (if new directories were >added) Fortunately, this is not needed anymore. After Thomas explained to me how easy it was to drop the .git directory into a new installation and commit those changes, we have decided to simply use git on the openSUSE servers. I will be updating the wiki on stage using my normal workflow, but I will be pushing the new wiki core into github when I finish building it. This will let you guys modify the themes and/or extensions to work with the new MW version, and then it will let me easily move those updates to production when we feel it is fully baked. It also lets us continue with the ability to quickly checkout theme updates between releases. >> but in the end who does the mediawiki updates decides what is the best >> workflow to do it. At the moment this is Matthew ;-) > >I know, and I'm not too keen to take over his job ;-) >(It might also be somehow problematic - even with public read access to >the staging servers (thanks!) getting write/shell access for non-SUSE >people might be harder.) That is true, due to system access policies. That's the tradeoff for hosting it in the data center :) >> For me it's important that it's documented how we >> do it, so that not only one person is able to do it. > >Full ACK. I'll publish a new workflow, including how it will work with git.

2 1

Re: [opensuse-web] openSUSE Web Updates
by Matthew Ehle 19 Nov '11

19 Nov '11

>Am Samstag, 19. November 2011 schrieb Christian Boltz: >> Am Donnerstag, 17. November 2011 schrieb Matthew Ehle: >> > 1) We are working on getting the wikis and blogs up to the latest >> > versions. Aside from what appears to be some minor cosmetic >> > issues >> > on the wikis, these upgrades have been successful on stage. >> >> Just a quick note about the wiki: MultiBoilerplate doesn't contain my >> "boilerplate per namespace" patch. Please re-apply it. > >Another quick note: firebug shows me several 404 errors for /load.php >(and the server needs 10 seconds to serve the 404, see below). > >AFAIK load.php is used to merge and compress CSS and JS into one file. >This could give us a noticable performance improvement compared to >loading $lots_of CSS and JS files. > >At the moment the CSS and JS files are still loaded in the "traditional" >way (not too surprising - there are some and tags in >the bento template). In other words: We need to do some changes in the >Bento template to use the ResourceLoader. See >http://www.mediawiki.org/wiki/ResourceLoader - and note that it's also a >new topic for me ;-) I've actually been thinking about this as well. Most of the content is served from static.o.o, and it is actually one of the longest things to wait on with the production servers. Minimizing that would have a huge impact. The theme is in github now, so you guys should be able to work on it now, like when it was in berlios. >> > 3) As part of this transition, we were able to make the staging >> > sites available to the public! > >Is it normal/expected that GET Main_Page on enstage.o.o takes nearly 11 >seconds to load? (measured with firebug) > >The same happens for other pages, including 404 errors like the page for >load.php (which is handled as non-existing wiki page). Unfortunately, yes. The problem is the staging database (notice how much more quickly wwwstage.opensuse.org loads), and I have been meaning to talk to the DBAs about it. -Matt

1 0

[opensuse-web] openSUSE.org Security Alert
by Matthew Ehle 19 Nov '11

19 Nov '11

Hi Everyone, Last night, we received an alert of a possible XSS or iFrame injection issue somewhere on www.opensuse.org or one of the wikis. We temporarily redirected the site and wikis to a maintenance page for about an hour while we assessed the risk and impact of the alert. After learning a little more, we felt that it was not a legitimate alert, and we brought the site back up. I am still waiting on a full report, so that we can figure out what to do for a long term solution. As a precaution, I am working on an immediate upgrade path to the latest version of Mediawiki and its plugins. I will also be working on upgrading Apache to 2.2.21 on the www and wiki servers. -Matt

5 10