Discuss

discuss@lists.centos.org

34753 discussions

Start a nNew thread

CentOS-announce Digest, Vol 107, Issue 6
by centos-announce-request＠centos.org 10 Jan '14

10 Jan '14

1 0

CentOS-announce Digest, Vol 107, Issue 5
by centos-announce-request＠centos.org 09 Jan '14

09 Jan '14

1 0

Hash rounds in /etc/libuser.conf won't work
by george.shaffer＠comcast.net 09 Jan '14

09 Jan '14

Two weeks ago I reported a problem I was having in the CentOS 5 Security Support forum. I could not get hash rounds, configured in /etc/libuser.conf, to work on CentOS release 5.10 (Final), 2.6.18-371.3.1.el5 x86_64. The details are here: https://www.centos.org/forums/viewtopic.php?f=24&t=44245&sid=975951a5a0eb26… I read all the documentation and looked for more off the CentOS site. I searched the entire CentOS site for hash_rounds_min and hash_rounds_max, the parameters changed in libuser.conf to configure the desired changes, without a single hit in any area on either. Over 800 people have seen my post and not a single reply; not unusual in that forum for what may be an infrequent situation. I'm guessing very few people have tried these options. At the same time I changed the hashing algorithm. Hash rounds only works with sha256 or sha512. The algorithm change worked the first time. The concept of configurable hash rounds is that the administrator can adapt the the hashing process to the specific hardware on which this is being configured and on faster hardware when a system is installed late in a OSs life cycle, up the rounds to make cracking harder. If an admin is willing to make users wait 2 seconds on every login and su, then a cracker on similar hardware could only get 0.5 cracks per second. This would make even 3 character passwords that did not fall to dictionary attacks tedious, and "good" 6 character passwords would be uncrackable. Even with a fast cracking network, with multiple GPGPU enabled PCs and a mixture of compromised systems working 10,000 times faster than a single PC, good 6 character passwords would be a serious obstacle and 8 uncrackable. I need this for a paper I'm writing which maintains "After 20 Years, Windows Passwords Still Broken". I want to compare Windows' poor MD4 with no salts (this is about NT hashes, not the notoriously broken LM hashes), to Unix like with salts, choice of algorithms, and hashing cycle control. The comparison is much weaker if I have no working example for one of the 3 key pieces on the Unix side. If anyone has successfully used hash rounds controls, I'd very much like to know what you did that I missed in my detailed forum report. It's possible there is no bug. I'm basing this on the belief that 900 million to 1 billion hashing rounds with SHA512 should produce a substantial delay and not complete in a small fraction of a second. Either my knowledge is way of or my PC MUCH faster than I thought it was, or there is a bug, if I've done everything correctly according to the documentation. I looked up how to report a bug and this said to submit the report to the CentOS-qa mailing list but I cannot find such a list. Is there such a list or any bug reporting procedure? If this is a duplicate post I apologize. I sent one yesterday and never got it and it's not in the archives when messages sent latter are.

1 0

Forward http traffic
by Nikolaos Milas 09 Jan '14

09 Jan '14

Hello, On CentOS 6.5 x86_64 I have (/etc/sysconfig/iptables): *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A FORWARD -j RH-Firewall-1-INPUT -A RH-Firewall-1-INPUT -i lo -j ACCEPT -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -s 10.10.10.0/24 -m tcp -p tcp --dport 22 -j ACCEPT -A RH-Firewall-1-INPUT -s 10.10.10.0/24 -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited COMMIT Now, I want to forward all http traffic coming in from 10.250.250.0/24, at local port 8080, to 2 particular IP Addresses (port 80). Is it enough to prepend (to the above) the following: *nat :PREROUTING ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A PREROUTING -s 10.250.250.0/24 -p tcp --dport 8080 -j DNAT --to-destination xxx.xxx.xxx.xxx:80 -A PREROUTING -s 10.250.250.0/24 -p tcp --dport 8080 -j DNAT --to-destination yyy.yyy.yyy.yyy:80 COMMIT ...? Please advise! Thanks in advance, Nick

11 16

Re: [CentOS] [CentOS-announce] CentOS Project joins forces with Red Hat
by Michael Weiner 08 Jan '14

08 Jan '14

This is great news!! Congrats and thanks to everyone that has put in all the hard work to make this a great environment. Michael Weiner On Tue, Jan 7, 2014 at 4:09 PM, Karanbir Singh <kbsingh(a)centos.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > With great excitement I'd like to announce that we are joining the Red > Hat family. The CentOS Project ( http://www.centos.org ) is joining > forces with Red Hat. Working as part of the Open Source and Standards > team ( http://community.redhat.com/ ) to foster rapid innovation > beyond the platform into the next generation of emerging technologies. > Working alongside the Fedora and RHEL ecosystems, we hope to further > expand on the community offerings by providing a platform that is > easily consumed, by other projects to promote their code while we > maintain the established base. > > We are also launching the new CentOS.org website ( > http://www.centos.org ). > > - ------------- > The new initiative is going to be overseen by the new CentOS Governing > Board. The initial Board comprises of the existing CentOS Core team > members : > > - - Ralph Angenent > - - Tru Hyunh > - - Johnny Hughes JR > - - Jim Perrin > - - Karanbir Singh > > and also sees new members: > - - Fabian Arrotin, who comes to the board nominated from the community > - - Carl Trieloff, Karsten Wade, and Mike McLean join us, nominated by > Red Hat. > > Please join me in welcoming the new members to the Board. > > The key operating points of the Board are going to be: Public, Open, > and Inclusive. You can find more information about the governance > model, the board, and the operating policies we are proposing at > http://www.centos.org/about/governance/ > > Furthermore, some of the existing CentOS Core members are moving to > take up roles at Red Hat, as a part of their sponsorship of the CentOS > Project, allowing these people to work on the Project as their primary > job function. This includes Johnny Hughes Jr, Jim Perrin, Fabian > Arrotin, and myself. We will be working with and operating out of the > Red Hat Open Source and Standards team in the CTO's Office. > > - ------------- > Some of the things that are not changing: > - - The CentOS Linux platform isn't changing. The process and methods > built up around the platform however are going to become more open, > more inclusive and transparent. > - - The sponsor driven content network that has been central to the > success of the CentOS efforts over the years stays intact. > - - The bugs, issues, and incident handling process stays as it has been > with more opportunities for community members to get involved at > various stages of the process. > - - The Red Hat Enterprise Linux to CentOS firewall will also remain. > Members and contributors to the CentOS efforts are still isolated from > the RHEL Groups inside Red Hat, with the only interface being srpm / > source path tracking, no sooner than is considered released. In > summary: we retain an upstream. > > Feel free to reach out if you have specific concerns about how this > change impacts your CentOS story. URLs mentioned at the bottom of this > email should be a good starting point. > > - ------------- > Some of the key things that are changing: > - - Some of us now work for Red Hat, but not RHEL. This should not have > any impact to our ability to do what we have done in the past, it > should facilitate a more rapid pace of development and evolution for > our work on the community platform. > > - - Red Hat is offering to sponsor some of the buildsystem and initial > content delivery resources - how we are able to consume these and when > we are able to make use of this is to be decided. > > - - Sources that we consume, in the platform, in the addons, or the > parallel stacks such as Xen4CentOS will become easier to consume with > a git.centos.org being setup, with the scripts and rpm metadata needed > to create binaries being published there. The Board also aims to put > together a plan to allow groups to come together within the CentOS > ecosystem as a Special Interest Group (SIG) and build CentOS Variants > on our resources, as officially endorsed. You can read about the > proposal at http://www.centos.org/variants/ > > - - Because we are now able to work with the Red Hat legal teams, some > of the contraints that resulted in efforts like CentOS-QA being behind > closed doors, now go away and we hope to have the entire build, test, > and delivery chain open to anyone who wishes to come and join the effort. > > The changes we make are going to be community inclusive, and promoted, > proposed, formalised, and actioned in an open community centric manner > on the centos-devel mailing list. And I highly encourage everyone to > come along and participate. > > - ------------- > Contacting us works best via the established community mechanisms. > - - Real time chats via IRC ( http://wiki.centos.org/irc ) ; To keep > conversation sanity intact, I recommend using the #centos-devel > channel to discuss project related activity while #centos is best used > for end user conversations. > > - - The Mailing lists are a great way to interface with the developers, > contributors and the community at large ( http://lists.centos.org ). > As with IRC, we recommend using the centos-devel list to talk about > project related issues while the general centos list is best used for > end user conversations. > > - - The CentOS Forums are another great way to engage in conversation > with other users ( http://www.centos.org/forums ), if you prefer that > mechanism. > > All the above mentioned venues are public and open to the community, > should you wish to discuss something privately, you can email us at > centosdev(a)centos.org. Press requests should be sent to > press(a)centos.org. Please note that it will take us much longer to > reply to private requests as compared to content on the public venues. > > - ------------- > In the coming days we are going to create opportunities for people to > come and get involved in more face to face interactions. Starting with > a regular scheduled office-hours format hangouts ( > http://wiki.centos.org/OfficeHours ) that start early next week. We > are trying to split the sessions into two different timezones so as to > maximise the number of people who are able to join. The sessions will > run live, with #centos-devel on irc.freenode.net being used for > conversations alongside. > > We are also running a CentOS Dojo on the 31st Jan 2014 at Belgium ( > http://wiki.centos.org/Events/Dojo/Brussels2014 ); The event will run > two tracks, with lots of opportunities for social interaction between > the talks; followed by CentOS in the Clouds Hack sessions. We are > limited in the number of people we can accomodate, so I encourage > everyone to register early. > > - ------------- > I want to take this opportunity to thank all the sponsors, the > contributors and the CentOS team members for all their help over the > years, the project is built completely upon those contributions - and > I look forward to seeing even more involvement from everyone as we > move forward. > > - ------------- > A Request: > > We are still sorting out content in various places and it might take a > day or two to get everything in place. In the mean time if you find > something stale and perhaps misleading in the new context ( or the old > one! ) please drop in on #centos-devel at irc.centos.org and let us know. > > - ------------- > Some URLS: > - - http://www.centos.org/ The CentOS Project > - - http://wiki.centos.org/ CentOS Community wiki > - - http://community.redhat.com/ RedHat OSAS > - - > > http://www.redhat.com/about/news/press-archive/2014/1/red-hat-and-centos-jo… > - - Red Hat Press Release > - - http://community.redhat.com/centos-faq - Red Hat FAQ's about the > initiative > - - http://wiki.centos.org/FAQ - CentOS FAQ's about the initiative > > > Enjoy! and regards, > > Karanbir Singh and everyone from the CentOS team, > > > - -- > Karanbir Singh, Project Chair, The CentOS Project > +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS > GnuPG Key : http://www.karan.org/publickey.asc > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.14 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iEYEARECAAYFAlLMbQcACgkQMA29nj4Tz1sTnQCgj2fYxYpTjA0KwH7TpCWjE4gg > w2cAniQWb/nh6Zn/8daSQ3EAfLIzGNKg > =KJOk > -----END PGP SIGNATURE----- > _______________________________________________ > CentOS-announce mailing list > CentOS-announce(a)centos.org > http://lists.centos.org/mailman/listinfo/centos-announce > -- "A patriot must always be ready to defend his country against his government." E. Abbey

1 0

freenx vs KVM Virtual Machine Manager - mouse poiner
by Les Mikesell 08 Jan '14

08 Jan '14

When I run the GUI Virtual Machine Manager in an NX/freenx session and open a console to a windows guest VM (haven't tried Linux w/X as a guest yet), the mouse point location does not track correctly. Is there some setting to improve this? X2go seems better in this respect but I'm not sure I want to switch yet. Normally I'd use vnc or remote-desktop connections directly to the guest anyway, but there are times you need to use the virtual consoles. -- Les Mikesell lesmikesell(a)gmail.com

1 0

Hash rounds in /etc/libuser.conf won't work - how to report a bug
by george.shaffer＠comcast.net 08 Jan '14

08 Jan '14

Two weeks ago I reported a problem I was having in the CentOS 5 Security Support forum. I could not get hash rounds, configured in /etc/libuser.conf, to work on CentOS release 5.10 (Final), 2.6.18-371.3.1.el5 x86_64. The details are here: https:// www.centos.org/forums/viewforum.php?f=24&sid=44859638070165ed5d8d9c35cdbe03… I read all the documentation and looked for more off the CentOS site. I searched the entire CentOS site for hash_rounds_min and hash_rounds_max, the parameters changed in libuser.conf to configure the desired changes, without a single hit in any area on either. Nearly 800 people have seen my post and not a single reply; not unusual in that forum for what may be an infrequent situation. I'm guessing very few people have tried these options. At the same time I changed the hashing algorithm. Hash rounds only works with sha256 or sha512. This worked the first time. The concept of configurable hash rounds is the administrator can adapt the the hashing process to the specific hardware on which this is being configured and on faster hardware when a system is installed late in a OSs life cycle, up the rounds to make cracking harder. If an admin is willing to make users wait 2 seconds on every login and su, then a cracker on similar hardware could only get 0.5 cracks per second. This would make even 3 character passwords that did not fall to dictionary attacks tedious, and "good" 6 character passwords would be uncrackable. Even with a fast cracking network, with multiple GPGPU enabled PCs and a mixture of compromised systems working 10,000 times faster than the single PC, good 6 character passwords would be a serious obstacle and 8 quite uncrackable. I need this for a paper I'm writing which maintains "After 20 Years, Windows Passwords Still Broken". I want to compare Windows' poor MD4 with no salts (this is about NT hashes, not the notoriously broken LM hashes), to Unix like with salts, choice of algorithms, and hashing cycle control. The comparison is much weaker if I have no working example for one of the 3 key pieces on the Unix side. If anyone has successfully used hash rounds controls, I'd very much like to know what you did that I missed in my detailed forum report. It's possible there is no bug. I'm basing this on the belief that 900 million to 1 billion hashing rounds should produce a substantial delay and not complete in a small fraction of a second. Either my knowledge is way of or my PC MUCH faster than I thought it was, or there is a bug, if I've done everything correctly according to the documentation. I looked up how to report a bug and this said to submit the report to the CentOS-qa mailing list but I cannot find such a list.

1 0

FF 24 is borked: One must have tabs, like it or not!
by Robert Heller 08 Jan '14

08 Jan '14

I just did a yum update on my CentOS 5.10 desktop machine and it installed FF 24. And tabs have appeared and cannot be [really] removed! Arg!!! *I HATE TABS!* (Yes I did installed the "hide tabs when there is only one tab" plugin, but that is not really a complete solution.) In the Mozilla support forum thread relating to this (https://support.mozilla.org/en-US/questions/968331) there is mention of SeaMonkey which has better control of tabs and I was wondering: is there a supported version of SeaMonkey that will install under RHEL5 / CentOS5? Specificly, I am looking for RPMs for SeaMonkey, rather than the tarball install. -- Robert Heller -- 978-544-6933 / heller(a)deepsoft.com Deepwoods Software -- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments

4 3

Re: [CentOS] [CentOS-announce] CentOS Project joins forces with Red Hat
by Alain Péan 08 Jan '14

08 Jan '14

Le 08/01/2014 14:54, Reindl Harald a écrit : > *which independence*?????? > > CentOS is a*bug for bug* indentical rebuild of RHEL > you will never face*any* change or bugfix in CentOS > which is not done in the same RHEL package > > so about*what* independance are you talking about? For example to build a 100% bug for bug release of RHEL, and not : "better able to serve the needs of open source community members who require different or faster-moving components" From : http://community.redhat.com/centos-faq/ This is a kind of Fedora ? Will it supported 10 years, by recompiling the RHEL source updates too ? Alain -- Administrateur Système/Réseau Laboratoire de Photonique et Nanostructures (LPN/CNRS - UPR20) Centre de Recherche Alcatel Data IV - Marcoussis route de Nozay - 91460 Marcoussis Tel : 01-69-63-61-34

5 6

CentOS-announce Digest, Vol 107, Issue 4
by centos-announce-request＠centos.org 08 Jan '14

08 Jan '14

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CentOS Project joins forces with Red Hat (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Tue, 07 Jan 2014 21:09:27 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CentOS Project joins forces with Red Hat To: CentOS Announcements List <centos-announce(a)centos.org> Message-ID: <52CC6D07.5050909(a)centos.org> Content-Type: text/plain; charset=ISO-8859-1 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 With great excitement I'd like to announce that we are joining the Red Hat family. The CentOS Project ( http://www.centos.org ) is joining forces with Red Hat. Working as part of the Open Source and Standards team ( http://community.redhat.com/ ) to foster rapid innovation beyond the platform into the next generation of emerging technologies. Working alongside the Fedora and RHEL ecosystems, we hope to further expand on the community offerings by providing a platform that is easily consumed, by other projects to promote their code while we maintain the established base. We are also launching the new CentOS.org website ( http://www.centos.org ). - ------------- The new initiative is going to be overseen by the new CentOS Governing Board. The initial Board comprises of the existing CentOS Core team members : - - Ralph Angenent - - Tru Hyunh - - Johnny Hughes JR - - Jim Perrin - - Karanbir Singh and also sees new members: - - Fabian Arrotin, who comes to the board nominated from the community - - Carl Trieloff, Karsten Wade, and Mike McLean join us, nominated by Red Hat. Please join me in welcoming the new members to the Board. The key operating points of the Board are going to be: Public, Open, and Inclusive. You can find more information about the governance model, the board, and the operating policies we are proposing at http://www.centos.org/about/governance/ Furthermore, some of the existing CentOS Core members are moving to take up roles at Red Hat, as a part of their sponsorship of the CentOS Project, allowing these people to work on the Project as their primary job function. This includes Johnny Hughes Jr, Jim Perrin, Fabian Arrotin, and myself. We will be working with and operating out of the Red Hat Open Source and Standards team in the CTO's Office. - ------------- Some of the things that are not changing: - - The CentOS Linux platform isn't changing. The process and methods built up around the platform however are going to become more open, more inclusive and transparent. - - The sponsor driven content network that has been central to the success of the CentOS efforts over the years stays intact. - - The bugs, issues, and incident handling process stays as it has been with more opportunities for community members to get involved at various stages of the process. - - The Red Hat Enterprise Linux to CentOS firewall will also remain. Members and contributors to the CentOS efforts are still isolated from the RHEL Groups inside Red Hat, with the only interface being srpm / source path tracking, no sooner than is considered released. In summary: we retain an upstream. Feel free to reach out if you have specific concerns about how this change impacts your CentOS story. URLs mentioned at the bottom of this email should be a good starting point. - ------------- Some of the key things that are changing: - - Some of us now work for Red Hat, but not RHEL. This should not have any impact to our ability to do what we have done in the past, it should facilitate a more rapid pace of development and evolution for our work on the community platform. - - Red Hat is offering to sponsor some of the buildsystem and initial content delivery resources - how we are able to consume these and when we are able to make use of this is to be decided. - - Sources that we consume, in the platform, in the addons, or the parallel stacks such as Xen4CentOS will become easier to consume with a git.centos.org being setup, with the scripts and rpm metadata needed to create binaries being published there. The Board also aims to put together a plan to allow groups to come together within the CentOS ecosystem as a Special Interest Group (SIG) and build CentOS Variants on our resources, as officially endorsed. You can read about the proposal at http://www.centos.org/variants/ - - Because we are now able to work with the Red Hat legal teams, some of the contraints that resulted in efforts like CentOS-QA being behind closed doors, now go away and we hope to have the entire build, test, and delivery chain open to anyone who wishes to come and join the effort. The changes we make are going to be community inclusive, and promoted, proposed, formalised, and actioned in an open community centric manner on the centos-devel mailing list. And I highly encourage everyone to come along and participate. - ------------- Contacting us works best via the established community mechanisms. - - Real time chats via IRC ( http://wiki.centos.org/irc ) ; To keep conversation sanity intact, I recommend using the #centos-devel channel to discuss project related activity while #centos is best used for end user conversations. - - The Mailing lists are a great way to interface with the developers, contributors and the community at large ( http://lists.centos.org ). As with IRC, we recommend using the centos-devel list to talk about project related issues while the general centos list is best used for end user conversations. - - The CentOS Forums are another great way to engage in conversation with other users ( http://www.centos.org/forums ), if you prefer that mechanism. All the above mentioned venues are public and open to the community, should you wish to discuss something privately, you can email us at centosdev(a)centos.org. Press requests should be sent to press(a)centos.org. Please note that it will take us much longer to reply to private requests as compared to content on the public venues. - ------------- In the coming days we are going to create opportunities for people to come and get involved in more face to face interactions. Starting with a regular scheduled office-hours format hangouts ( http://wiki.centos.org/OfficeHours ) that start early next week. We are trying to split the sessions into two different timezones so as to maximise the number of people who are able to join. The sessions will run live, with #centos-devel on irc.freenode.net being used for conversations alongside. We are also running a CentOS Dojo on the 31st Jan 2014 at Belgium ( http://wiki.centos.org/Events/Dojo/Brussels2014 ); The event will run two tracks, with lots of opportunities for social interaction between the talks; followed by CentOS in the Clouds Hack sessions. We are limited in the number of people we can accomodate, so I encourage everyone to register early. - ------------- I want to take this opportunity to thank all the sponsors, the contributors and the CentOS team members for all their help over the years, the project is built completely upon those contributions - and I look forward to seeing even more involvement from everyone as we move forward. - ------------- A Request: We are still sorting out content in various places and it might take a day or two to get everything in place. In the mean time if you find something stale and perhaps misleading in the new context ( or the old one! ) please drop in on #centos-devel at irc.centos.org and let us know. - ------------- Some URLS: - - http://www.centos.org/ The CentOS Project - - http://wiki.centos.org/ CentOS Community wiki - - http://community.redhat.com/ RedHat OSAS - - http://www.redhat.com/about/news/press-archive/2014/1/red-hat-and-centos-jo… - - Red Hat Press Release - - http://community.redhat.com/centos-faq - Red Hat FAQ's about the initiative - - http://wiki.centos.org/FAQ - CentOS FAQ's about the initiative Enjoy! and regards, Karanbir Singh and everyone from the CentOS team, - -- Karanbir Singh, Project Chair, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLMbQcACgkQMA29nj4Tz1sTnQCgj2fYxYpTjA0KwH7TpCWjE4gg w2cAniQWb/nh6Zn/8daSQ3EAfLIzGNKg =KJOk -----END PGP SIGNATURE----- ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 107, Issue 4 ***********************************************

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss