openSUSE Wiki November 2011

wiki@lists.opensuse.org

12 participants
7 discussions

by Matthew Ehle

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

10 years, 5 months

[opensuse-wiki] openSUSE SSO Background

by Matthew Ehle

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

10 years, 5 months

[opensuse-wiki] Fwd: openSUSE Wiki translation

by Jan Papež (mailing lists)

Hi, I'd like to know, what's the best way to translate openSUSE Wiki? For example, I'm going to translate to Czech: http://en.opensuse.org/Portal:12.1 Is there some SVN/GIT repository (with .po/.pot files), or should I to write directly into Wiki? Thanks. Jan > ---------- Přeposlaná zpráva ---------- > > Předmět: Re: [opensuse-translation] openSUSE Wiki translation > Datum: Čt 17. listopadu 2011, 17:05:15 > Od: Andreas Jaeger <aj(a)suse.com> > Do: opensuse-translation(a)opensuse.org > > On Thursday, November 17, 2011 16:45:19 Jan Papež wrote: > > Hi, > > > > based on > > > > > Dne Čt 17. listopadu 2011 15:36:59, Andreas Jaeger napsal(a): > > > we've put the landing page (www.opensuse.org) now on github.com > > > and if you like to translate it there are two options: > > > * Translation via github tools (my preferred way) > > > > I must to ask: > > > > What way is the best for openSUSE Wiki translation? Is there some > > recommended to-do? > > > > For example, I'm going to translate: > > http://en.opensuse.org/Portal:12.1 to Czech. > > > > How to do it? Is there some SVN/GIT repository (with .po/.pot files), > > or should I to write directly into Wiki? > > Please ask on the opensuse-wiki mailing list, > > Andreas > -- > Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi > SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany > GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > > -- -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-wiki+owner(a)opensuse.org

10 years, 5 months

[opensuse-wiki] openSUSE Web Updates

by Matthew Ehle

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

10 years, 6 months

[opensuse-wiki] wiki formatting problem

by Dave Howorth

Every opensuse wiki page is disfigured by the presence of status information about the page's accuracy, depth and readability overlaid over the page itself. In some cases, it makes important information on the page unreadable, as in the following example: http://en.opensuse.org/Lifetime An image of what I see is pasted at http://imagepaste.nullnetwork.net/viewimage.php?id=2762 I believe the issue is that instead of using CSS to display this information, javascript has been used. You can reproduce the issue by disabling javascript. Javascript should not be used where CSS is suitable. -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-wiki+owner(a)opensuse.org

10 years, 6 months

Re: [opensuse-web] Re: [opensuse-wiki] openSUSE.org Security Alert

by Christian Boltz

Hello, Am Montag, 7. November 2011 schrieb Thomas Schmidt: > On 07.11.2011 16:18, Matthew Ehle wrote: > > I know you have suggested this before. In all honesty, it doesn't > > really matter whether I use subversion or not, especially with > > the way that we have to upgrade these wikis. Getting the MW core > > code is the easy part. I just download, extract, and move a > > couple of files over. That's still more work when compared to "svn up". And even more work if you have to modify one of the mediawiki files - you have to (remember to) patch it again at every update. (I'm quite sure index.php is modified for iChain, and MultiBoilerplate contains a patch from me to support different templates per namespace) I know that using svn doesn't change much on _this_ update - but it will save you time on the _next_ updates. Counter-question: what's the advantage of using the tarball? ;-) > > The vast majority of the time is spent in > > downloading and installing the extensions. I use subversion for > > as many of them as I can, but that is suitable for maybe half of > > the extensions that we use. Yes, I know there are several extensions that consist of only a single file (which is not available via SVN). OTOH, for example MultiBoilerplate is available via SVN, and we are using a modified version (with a patch from me). Just updating it with "svn up" or "svn switch" would save you lots of time here. > > What would be most helpful is to re-evaluate the extensions that > > we are running and see if we can get rid of a couple. That would > > go a long way for making the upgrades easier. As you have seen in the second half of my mail, I'm even requesting a new extension (ReplaceText) to make maintenance tasks like the CSS cleanup easier. Also the WikiEditor would be a nice feature ;-) (and will be shipped with 1.18, if I got the beta release notes right). Removing extensions is a very hard task - I had a quick look on them and think all of them still make sense. In other words: nothing to remove. The only exceptions might be SelectCategory and MultiUpload because they are already disabled ;-) > the problem we face with hosting the wiki code in git is, that our > production system doesn't have git installed (only svn) and it would > be quite complicated to do so because of datacenter policies etc... I > think a possible solution could be githubs subversion client > support[1]. I already pushed our current code state there[2], so we > can evaluate if this is an option for our deployments. If Matthew > confirms that this works, we can go ahead and set up the repo at > https://github.com/openSUSE/wiki . That sounds like a good idea - and brings up an interesting question: If we push SVN checkouts to git, they will include .svn directories. What will happen if you check them out using svn? ;-) (Please test this and tell me the result.) > @Christian: Could you help us doing your requested changes in the > github repo once it's at its final place? You are probably the one of > us with the most knowledge and experience in mediawiki, Thanks for the flowers ;-) I should add that the wiki I'm maintaining is quite small when compared to the openSUSE wiki: only one language, less visitors (54000 total views for main page - en.opensuse.org mainpage has 1.6 million views), less than 90 registered users etc. For example, I never had to think about memcached. Oh, and I even have some more extensions [1] installed ;-) > so it would be nice if you could help us :-) I have the "usual" problem - days with only 24 hours ;-) I'll help whenever possible, but it really depends on what other things I have on my schedule. BTW: skins/bento/css_local/style.css seems to contain a bug ;-) Line 471 is thumb tright { I'd guess there are some dots missing (".thumb .tright"), but that's only a wild guess because I don't know where this style should be used. : Regards, Christian Boltz [1] see http://hortipendium.de/Spezial:Version Just in case I shocked you: most of the additional extensions don't make sense for the openSUSE wiki for various reasons ;-) -- Wenn ich eine SuSE-CD an ein Schwein binde und dieses trete, laufen KDE & Co. auch ohne RAM recht schnell. [Robin S. Socha in de.comp.os.unix.linux.newusers] -- To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-wiki+owner(a)opensuse.org

10 years, 6 months

[opensuse-wiki] openSUSE.org Security Alert

by Matthew Ehle

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

10 years, 6 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Wiki November 2011