GNOME/Wayland Test Day – 2014-08-28

Heya Friends, So here comes another opportunity to contribute in Fedora QA.
We have a test day coming up for GNOME / Wayland which is scheduled for 2014-08-28, that is, this Thursday.
You really don’t need to sweat blood to be part of this test day. It is really very simple.

gnome

We have each and every information included in our wiki page . Vladimír Beneš is big cheese for this test day, who is burning the candle at both ends trying to get everything done and in place for all of the contributors.
So you really don’t need to worry about almost anything. Just make your self available to execute test cases for GNOME/Wayland.

There are some very attractive features to test for example captive portal support in gnome-shell and better rdp support in vinagre. If you have problems with any of the tests, try and report a bug. Bugs clearly related to GNOME Shell and it’s browser integration as well as to extensions.gnome.org should be reported to GNOME Bugzilla. Bugs that are clearly issues in Fedora GNOME integration should be reported to Fedora Bugzilla. If you are unsure, please report into Fedora Bugzilla or ask on #fedora-test-day or #fedora-qa. You will need an account to report bugs, but creating one is easy, and we will help you do this if you ask in IRC.

If you are not sure of the appropriate component, please check in IRC before filing, there are many possibilities. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, don’t forget to add your results to the results table available on wiki.

I am trying to get updates on test day participation badge. So if we are lucky, we will be able to earn some badges for participation. So be ready to roll. Happy Testing :)

Synonym of Fedora QA – Adam Williamson

profile_square_1024

A very famous name in Fedora QA “Adam Williamson“, we all know him
more as “Community Monkey”.
I was already quite impressed the amount of work he has been putting in Fedora QA since quite a long time and I am sure it is not just me. I got a golden opportunity to meet him in person at flock and it was really nice to know about him more as a person.

My first meeting with him was a big surprise for me. I was about to start my talk on Fedora QA and with in five minutes after I started giving talk, just a another boy with shorts came running with a big smile on his face in to my talk room and I actually stopped my talk to mention that people are so happy to get registered in the flock. But,he was smiling all the time as I was giving my talk (may be because, there were lot many things I included in my slides created/managed/initiated by Adam). I was quite confused what making this guy so happy. At the end of my talk he was helping me out in giving answers quite confidently. I was wondering who is this guy, then I read his name on his flock badge – I was almost dead with shock because it was none other than “Adam Williamson”

There are lot many contributors in Fedora QA who definitely want to know more about him as a person, So I used this opportunity to interview him. I did not had a set of questions ready for him for this interview because I don’t want it to be boring one but more natural and interesting one. So I am going to put the conversation I had with him
during this interview.

Ami :: your geographical location?
Adam :: Vancouver, BC (Canada).

Ami :: What is the secret behind this name “community monkey”, any story?
Adam :: Nothing in particular – I just didn’t like the term ‘community manager’ as it seems to imply a particular relationship which I don’t think is quite right for a project like Fedora. I can’t recall quite where the monkey thing originated, it’s lost in the mists of time, but it was back when I was working at Mandriva. The cartoon monkey icon I use often was very kindly drawn for me by a Mandriva community member.

Ami :: What do you like and dislike most about yourself?
Adam :: I’m not the most introspective of people, but I guess I like being relaxed and positive and I dislike when I get angry and/or sarcastic, or let people down.

Ami :: I want to know about the kind of upbringing you had which made this “community monkey” so efficient. So, tell me something about your childhood?
Adam ::  I was a normal kid, who used to love playing video games on computer. But eventually I noticed that it is more cool to play games on open source operation systems. I used to read PCW magazine. I got a open source OS CD with this magazine and I felt it was better. It offers you lot more interesting things in games and I used to experiment with things to make them work my way.

Ami :: It sounds more like a super kid than a normal one you must have technical studies background?
Adam :: No, It is academic. But I was part of Linux group in my university. I used to write about Linux.

Ami :: With academic background, how you made it to open source, computing, testing so successfully.
Adam :: Well, it is more about interest. I found open source, testing much more interesting than doing PHD and being a teaching.

Ami :: What was your first job and when you started doing Fedora QA.
Adam :: I did a lot of different jobs here and there. I worked in supermarket then in UK government agency, also worked for Shaw Cable – a cable TV / internet company in Canada for some time. But nothing interesting / technical, just phone stuff and data entry. My technical carrier started with Mandriva initially but then eventually I moved out. Later, I used to help people via community forum, answering their technical issues. I actually had to make money by posting ads on my blog.
It was 5 years back, when I started with Fedora QA. James Laska was my first mentor and manager who was quite helpful.

Ami :: What kind of work did you start with for QA and what all things you do now.
Adam :: It started with managing fedora QA wiki pages with Roshi, which made me learn a lot many things in QA. I used to read every document on wiki to update them. It helped me a lot and I do it even now when I found something is not right.
Now, I do almost all kind of things in Fedora QA : Test days co-ordinator,Testing various releases on different archs, Bugs, meetings, play with different testing tools, helping people.. so all the interesting stuff in QA.

Ami:: What is your inspiration which keeps your zeal so high day and night?
Adam :: Having interesting and useful work to do is really all I need!

Ami :: How do you manage to be online up and running 24*7?
Adam:: Bots! Well, I’m kidding, but using an IRC proxy certainly contributes to the impression: I use Bip – https://bip.milkypond.org/ . Other than that, it’s mostly just that I check my email and IRC pings regularly when I’m awake, as I work from home (but try not to take too much time for work in the evenings).

Ami :: Most memorable or challenging and interesting issue/bug which you want to share with us?
Adam :: There have been a lot and I’m probably forgetting many, but I enjoy ones
I have to trace out a long way and learn new stuff from. One example is https://github.com/openid/php-openid/issues/108 , where I figured out why OpenID wasn’t working on my WordPress install any more; probably trivial for an experienced PHP developer, but I learned a lot in following the trail. Another example is a bug I found in OwnCloud 7.0 which prevented the types for contact information (“Home”, “Work” etc) being displayed correctly in the web UI, https://github.com/owncloud/contacts/issues/536 – it turned out to be as simple as a check being “is this thing false?” when it should have been “is this thing true?”, but the tricky part is working all the way through the code to find that point, when your starting knowledge is
simply what you see on the screen.

Ami :: what were the significant hurdles during these 5 years long journey as community monkey and how did you beat them?
Adam :: I guess I don’t see things in that context – the way I see things is just that there is always more work to do, always some way to make Fedora better, and every day I do as many of those as I can without becoming a shut-in or going insane! So I don’t really tend to see hurdles in the way of some finishing line I could reach, I just wake up every day and think about what I could do to make things a little better
than they were the day before.

Ami :: What is your favorite pass time or hobby,  Other than Fedora QA  ?
Adam :: I have quite a few – my regular routine involves swimming all year round, which I like for the exercise and the different way you think when you’re constantly moving in a very repetitive environment, playing tennis and golf in summer, and snowboarding in winter. I like to read, watch bad American and Japanese TV, and eat out at all kinds of different places.

Ami :: If you were not a QA, what do you think what you should be doing?
Adam :: Anything useful that someone would let me do! Ideally in F/OSS. But it’s
something I don’t spend a lot of time thinking about, I tend to take the world one day at a time.

Ami :: What are your future plans, some more interesting stuff in Fedora  QA or it will be some other area?
Adam:: Nothing specific – as long as my job is interesting I’m happy to keep doing it as long as anyone will let me do it.

Ami :: Would you like to mention any name behind your glorified journey as community monkey?
Adam :: Ha! The Mandriva community was always incredibly kind and generous to me, and so has the Fedora community been; I’d hate to mention individual names as I feel I’d always leave someone out unintentionally. But I have to give a special mention to James Laska, former Red Hat Fedora QA team manager, whose friendliness, consideration, technical capabilities and attention to detail I’ve always tried (very poorly) to imitate.

Ami :: Best thing about Fedora community? What makes it outstanding?
Adam :: I like most positive-minded, productive F/OSS communities. I think the
best quality of Fedora specifically is its commitment to long-term thinking, which is evident in various ways but mainly in its commitment to approaching development from the perspective of ‘how do we fix this forever, for everyone?’ – not just ‘how do we fix it right now, for us?’

Ami:: What do you suggest for a new contributor in QA, what should be the starting point?
Adam :: https://fedoraproject.org/wiki/QA/Join is meant to be the starting point for new contributors – it should walk you through getting involved with QA. You can always ask on the mailing list or IRC channel if you have questions about the steps on that page.

Ami :: Any message for other contributors, beginners ?
Adam :: Contributing to Fedora (or any F/OSS project) is fun, rewarding, and probably easier than you think. There’s always something you can do, and with most things, there’s no penalty for getting it wrong – and you’ll probably learn something when you do. So don’t be afraid, and give it a try.

Invitation for Saturday Party – FAD at RH, Pune

fad

This post is a call for action. It is to spread the word about fedora event FAD (one day) at Red Hat Pune . For those, who wants to know what FAD is, can read FAD wiki . This FAD is mostly dedicated to testing for Fedora 21 Alpha. We will test different components on Fedora 21 Alpha. If you want to be part of fun, you are most welcome. You can pick up your favorite among these components to test and you will get help if required.

You really don’t need to be an expert in testing or any of these components and we are not at all restricted to only the listed components. If you want to test some other components, feel free to add that in this list.

Many people has shown their interest in Fedora activities and expressed that they want to be active contributor but don’t know exactly from where to start. Specially, after my talk at flock 2014. So this is a very nice opportunity for all of you. You can still do it, just update list of Attendees with your name and come join Saturday party. :)

Thanks to all of you who have already done it.

We also have some swags for you, which are very limited and will be distributed on first come first serve basis, So if you want to get one, be sure to come on time. And yes, you’ll need to get in touch with Siddhesh in advance so that passes can be arranged for your entry into office.

Flock 2014

I visited Prague, the beautiful city of Czech Republic for Flock. This was my first conference ever and it was a life time experience. I will make sure that I can attend many more in coming years. I presented a talk on Fedora QA. My talk was first talk after the keynote. It went pretty well. Many in the audience asked questions and during the discussion we talked about reviving the bug triaging project. As there are many bugs in Fedora Bugzilla which are currently in zombie state and we really want to get rid of them. People agreed to the fact that Fedora QA team is doing hard work to test every bit of Fedora. But certainly we need more hands to contribute. if you want to be part of it, please join us here -> https://fedoraproject.org/wiki/QA/Join.

There were so many awesome people at Flock. I met Mathew Miller, who is the Fedora project leader currently. He is so down to earth person, it was pleasure to meet him. I talked about getting involved in fedora magazine. There is one more name to highlight for fedora magazine ie. Chris Roberts. He is again very nice, fun loving person, who is always happy to help.

Obviously, I wanted to meet fedora QA team and I met this fabulous person Adam Williamson. We talked about fedora QA in depth. We discussed about wiki test plans, tcms, bug triaging. He also showed me Mozilla tcms which he was trying to play with. So maybe Fedora test plans will be migrated to Mozilla tcms in future. It was nice meeting him. Later I met Tim Flink who is handling taskotorn. I got to know about the features and how he is planning to make it better than AutoQA. I got a chance to meet Ben Levenson too. It was a privilege to meet him.

I attended many talks during conference. Here are the videos of all the talks. I attended the keynote, Taskotron and Me, Life of a remotee, Predictive Input Methods, UX 101: Practical usability methods that everyone can use, Release Engineering and You, Fedora Badges & Badge Design, The Problem with Unit Testing, Systemd daemon integration, next step to world domination, Secure Programming Practices, Security Code Audit 101, You can write kernel tests too! during the conference.

It was awesome experience to get to know so many fantastic people and to learn about new things in Fedora. It was little hard to digest all the information though. But we have to make sure that we can utilize every single second while in the conference.

Apart from work, we had fun too. Boat party was nice. I loved to be there on boat. Prague looks more beautiful in evening. I could feel zephyr. River water was sparkling in lights. Thanks to Flock organizers for doing it. We have a badge too for attending this party :)

Abrt Mail Configuration on RHEL7

ABRT :: Automatic Bug Reporting tool, On RHEL7 we can configure the system to send mail on every crash along with other information.

1. Install all required rpms :: abrt-tui abrt-addon-ccpp libreport-plugin-mailx

2. Update file /etc/abrt/abrt-action-save-package-data.conf – It allows you to modify the behaviour of the abrt-action-save-package-data program. I have ::

OpenGPGCheck = no — if yes, crashes will be detected only in the applications whose packages are signed by the GPG keys. No means crashes will be reported in all programs even not signed by GPG.

ProcessUnpackaged = yes — yes means, process crashes in executables that do not belong to any package. The default setting is no.

3. Configure mailx plugin by modifying /etc/libreport/plugins/mailx.conf, define Subject, EmailFrom, EmailTo and SendBinaryData

4. Restart the services abrtd and abrt-ccpp.

5. Enable abrt-auto-reporting, sudo abrt-auto-reporting enabled.

6. /usr/bin/abrt-cli list shows crashes with the abrt crash directories created, go to the directory, and execute

            /usr/bin/abrt-action-install-debuginfo -v;
            /usr/bin/abrt-action-generate-backtrace -v;
            /usr/bin/reporter-mailx -v

 

 

 

Kerberos

Properties
=========
– Kerberos is a authentication protocol
– Credentials never flow through network in this case
– Kerberos uses symmetric keys.

How it works
===============
1. When you login early in the morning to your system first, you provide login user ID (User Name). So think your system as a client.

2. User name goes to KDC(key Distribution Center – which has AS(Authentication Server), DataBase(to store keys of services, users and servers) and TGS (Ticket granting Server).

3. Now KDC, checks its db if the user is present or not, and generates 2 things ::
3.1 A TGT(ticekt granting ticket-which has username+client IP+Kerberised name) for the user which in encypted by KDC’s private key.
3.2 A session key[KDC-Client session key]
both the things travels in a packet which is encrypted by the user’s private key(password)from KDC to client/user.[KDC-Client session key]

4. Now the packet gets decrypted at the client’s system using user’s private key. The session key isolated from the packet, but TGT is still in encrypted form, because it was encrypted with the KDC’s private key which is only with KDC in its db.

5. When client tries to access any service of application server(say ssh server), it has to prove its identity to Application server while client has already proved its identity to KDC and got the encrypted TGT.

6. Client will send request to KDC ::
1. A authenticater(User name,IP,time stamp) which is encrypted with the session key[KDC-Client session key] got from KDC AND
2. Already encrypted TGT
3. This whole packet (authenticater+TGT) encrypted by the session key[KDC-Client session key].

7. KDC will receive this packet request from client for SSH service, it decrypts the packet using session key[KDC-Client session key]
1. KDC will decrypt the TGT using its private key and matches it with the authenticator’s details.
2. If details matches, KDC will generate a Ticket for the client which will have username,client IP and service name. Which will be encrypted using the application server’s private key.
3. With Ticket, KDC will also send another session key which is client-application session key.
4. Now, this packet (Ticket for app server + Client-appServer’s session key) will be encrypted using session key[KDC-Client session key] and sent from KDC to client.

8. Now Client has received the packet encrypted with [KDC-Client session key], it decrypts it and got the Ticket for app server along with the session key of client and KDC server. But Ticket is still encrypted as it is encrypted using App Server’s private key.
1. Client send the Ticket+Authenticator to App server which is now encrypted using the session key of client and app server’s session key.
2. App server receives the packet request from the client, it has the session key to decrypt the packet and isolate the Ticket.
3. App server decryptes the Ticket using its own private key and check for the access and responds back.

VNC

On RHEL6

  1. yum install *vnc*
  • set vnc password by using #vncserver
  • do #service vncserver restart
  1. yum groupinstall “X Window System” AND yum groupinstall “Desktop”
  2. edit /etc/sysconfig/vncservers
  • uncomment line # 19 and 20
  • and replace myusername with the username you want vnc to run as -> maybe ‘root’
  • and remove the options “-localhost” and “-nolisten tcp”
  • then restart vncserver
  1. From your host go to Applications -> internet –> vncviewer and type ip:1