George Pop

Create a set of keys and sign an RPM package with your own private key.

2009-04-07T07:25:00.000-07:00

ToDo:
1. Create an RPM package that will install your repository configuration file and the key.
2. Test it.
3. Blog about this lab, and include a link to your repository RPM package.

First I create my set of keys by running gpg --gen-key. After I created the set of public and private keys, I start modifying the ~.rpmmacros file and make it look like this:

%_topdir %(echo $HOME)/rpmbuild
%_smp_mflags -j30
%__arch_install_post /usr/lib/rpm/check-rpaths /usr/lib/rpm/check-buildroot
%_gpg_name "nasugeorge@yahoo.com"

Then I take the spec file of filezilla-3.1.5.1-5.fc10.src.rpm and modify the version to 5 and rebuild the package. Then I sign all the filezilla packages with my private key rpm –addsign filezilla-3.1.5.1-5.fc10.src.rpm. Then I copy all the packages under my /var/www/html/george-sbr600 folder and then run createrepo /george-sbr600

Next step I create a my own repo file in the /etc/yum.repos.d/ george.repo
[georgep@australia yum.repos.d]$ cat george.repo
[george]
name=george $releasever - $basearch
failovermethod=priority
baseurl=http://australia.proximity.on.ca/george-sbr600/
#mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-george

Now I installed my new rpm package, filezilla release 5  signed with my own private key.

Differences in time between rpmbuild and distcc

2009-03-19T05:54:00.000-07:00

Things to do:

1.

Describe the differences in time between building crystalspace-1.2.1-1.fc10.src.rpm with rpmbuild and distcc on Australia.

So I make sure all the build requirements are installed and run time run rpmbuild -ba crystalspace.spec

and get this time and erros.

rm -f cscursor.csplugin

cp plugins/video/cursor/cscursor.csplugin cscursor.csplugin

make: *** [all] Error 1

error: Bad exit status from /var/tmp/rpm-tmp.ptb7jj (%build)

RPM build errors:

Bad exit status from /var/tmp/rpm-tmp.ptb7jj (%build)

real 5m29.565s

user 4m10.397s

sys 0m44.563s

[georgep@australia SPECS]$

Now I run distcc in order to see the time differences in my package

rm -f cscursor.csplugin

cp plugins/video/cursor/cscursor.csplugin cscursor.csplugin

make: *** [all] Error 1

error: Bad exit status from /var/tmp/rpm-tmp.XS12lV (%build)

RPM build errors:

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

user mockbuild does not exist - using root

group mockbuild does not exist - using root

Bad exit status from /var/tmp/rpm-tmp.XS12lV (%build)

real 5m12.124s

user 4m25.188s

sys 0m45.087s .

845 root 15 -5 0 0 0 S 0.3 0.0 0:00.88 md2_raid5

5470 nobody 25 5 21476 684 364 S 0.3 0.0 0:00.32 distccd

5471 nobody 25 5 21476 716 364 S 0.3 0.0 0:00.32 distccd

5473 nobody 25 5 21476 676 364 S 0.3 0.0 0:00.32 distccd

5474 nobody 25 5 21476 788 364 S 0.3 0.0 0:00.30 distccd

5476 nobody 25 5 21476 680 364 S 0.3 0.0 0:00.30 distccd

The results onn Scotland...

Lab 2 SBR600 : Build your first RPM package

2009-02-07T17:52:00.000-08:00

My first RPM: ophcrack-3.1.0
1.I downloaded the source code from: http://voxel.dl.sourceforge.net/sourceforge/ophcrack/ophcrack-3.1.0.tar.bz2.
2.Next copy to tar ball to the ~/rpmbuild/SOURCES.
3.Go into the ~/rpmbuild/SPECS and create a new spec file for the rpm by running: rpmdev-newspec ophcrack
4.Edit that file and first problem I run into was the Source0 line: You need to make sure in the Url there is the name of the tar ball otherwise the rpm builder won't know what is the tar ball name in the rpmbuild SOURCES folder.
5.Second problem was that I was missing to comment out the BuildRequires: line and Requires: line.
6.By running rpmbuild -ba ophcrack into the ~/rpmbuild/SPEC folder I run into another problem which had to do with the %files
that was missing this file: /usr/bin/ophcrack
.
7.So run again the build command and now it build everything but it has an error with regards to the qt-devel missing. So I installed that package with yum install qt-devel.
8.Run again the rpmbuild and it worked. When I run rpmlint ophcrack-3.1.0-1.fc10.i386.rpm in the /RPMS folder I get this:

ophcrack.i386: W: no-documentation

ophcrack.i386: E: description-line-too-long Ophcrack is a Windows password cracker based on a time-memory trade-off using rainbow tables. This is a new variant of Hellman's original trade-off, with better performance. It recovers 99.9% of alphanumeric passwords in seconds.

ophcrack.i386: W: non-standard-group Applications/System Tools

ophcrack.i386: W: incoherent-version-in-changelog 3.1-0.fc10 ['3.1.0-1.fc10', '3.1.0-1']

1 packages and 0 specfiles checked; 1 errors, 3 warnings.

9.So I had to fix those error fairly easy and then I loged as root and install my rpm from the /RPMS folder and go to the /usr/bin and run ./ophcrack and it works.
10.Also did an rpmlint ophcrack.spec
and it was free of erros.
11.Also did an rpmlint ophcrack-3.1.0-1.fc10.src.rpm
and it was free of erros.
12.So now you can enjoy the RPM and see the spec file, the only problem is that the icon under the Applications/System is not there I will look more into making the .desktop file for it and put it under /usr/share/applications .

Thanks to: John64, ctyler on the #seneca channel on irc.freenode.net.

Links:
a) ophcrack-3.1.0-1.fc10.i386.rpm
b)ophcrack-3.1.0-1.fc10.src.rpm
c)ophcrack-debuginfo-3.1.0-1.fc10.i386.rpm
d) ophcrack.spec

Lab 1 SBR600 Class CTY Program

2009-01-26T13:29:00.000-08:00

Hi Eveyone. This is my ToDo list for Lab1 in SBR600 class:

Lab 1: By Wednesday, January 21:

Build 2 packages from Source

The NLED editor from http://cdot.senecac.on.ca

Any package that uses autoconf -- SourceForge might be a good place to look for such packages.

Blog about the experience.

1. How to compile Nled editor in a standard Fedora 10 DVD Installtion.

First thing in order to build this 2 packages I installed from the DVD Fedora 10 on my Toshiba laptop with the standard packages. Then I went to http://cdot.senecac.on.ca and downloaded the tar ball source package of NLED called nled_2_52_src.tgz. After that I extracted the files by running the following command in the shell: tar -xzf nled_2_52_src.tgz. Now I was trying to run make from inside the nled-2.52 directory and first of all I needed gcc compiler installed on my standard Fedora 10. To intall gcc compiler just purely run yum install gcc and it will install it for you from the Fedora servers.

Now once again I tried to run make and I got some errors with regards the ncurses packages. I had to run yum list “ncuses*” in order to see which ncurses packages I had installed already and those one that were available to install. I was missing 3 ncurses packages ncurses-devel.i386, ncurses-static.i386, ncurses-term.i386 . I tried to install directly the ncurses-devel pack by running yum install ncurses-devel which did nothing. Then by running yum install ncurses-static devel and static packs got intalled.

Now I run again make and it compiled successfully the Nled editor.

Built a package that uses autoconf FileZilla Client on Fedora 10.

First thing you download the source code from http://filezilla-project.org/download.php?type=client and then you extract the files which will become filezilla-3.2.0. When I tried to run ./configure script that uses autoconf in a “Stock” Fedora 10 distro you run into problems with not having the C++ compiler. So Chris told me the solution :

“ctyler> yum groupinstall "Development Tools" "Development Libraries" # will probably do the trick”

So I installed the Development Tools but now I still need to get wxWidgets installed, so I run yum install wxGTK-devel and now another problem with gnutls library. So you have to install it by using: yum install gnutls-devel .

Now finally when I run ./configure it gives me no error and it creates the Makefile. So next I run make waited about 5 minutes on my laptop and then make install that was fast. Now under my Application, Internet I have the FileZilla Client Shortcut and run it and it WORKS :)

So that's all for the Lab1 and I would like to thanks Chris and everyone else from the #seneca IRC channel on irc.freenode.org for their help.

First Week of SBR600A

2009-01-14T17:21:00.001-08:00

Hi Everyone,
My name is George, and I am a Seneca CTY student in the 6th semester enjoying networking and security. This is my first time playing with blogs, wiki and planet so please excuse any First time mistakes.

First week of SBR600:
ToDo: Communication Lab: By Thursday, January 15, Set up your accounts (wiki, IRC, FAS2).

Create a blog post which will appear on the OpenSource@Seneca Planet, containing:
- A portion of an IRC conversation you've had with someone on a Fedora or Seneca IRC channel.
Hi Chris
Hi GeorgeP !
I have created some account and the blog but I get confused with the planet thing...
GeorgeP: what's your blog URL?
take your RSS URL (not the main URL) and add it to http://zenit.senecac.on.ca/wiki/index.php/Open_Source@Seneca_Planet_List
http://nashutzu.blogspot.com/
are you tagging your posts separately for the planet, or should all of your posts go onto the planet?
I should take them manualy
if you want to send all posts, the RSS URL is: http://nashutzu.blogspot.com/feeds/posts/default
anyways, see that page for examples of other URLs that are for specific tags
how do u find out the link for each post ? u just click on the post and u copy the whole big link ?
to select specific posts, use the tagging capability of blogspot ... for example, you can set it up so that all posts marked "seneca" go to the planet
oh that`s even better thanks i'll look more into it
if your tag is "seneca", your RSS feed will be http://nashutzu.blogspot.com/feeds/posts/default/-/seneca
A link to your User page on the Seneca wiki
http://zenit.senecac.on.ca/wiki/index.php/User:George_P
A link to your User page on the Fedora wiki
https://fedoraproject.org/wiki/User:Georgep

Add an entry to the Winter 2009 SBR600 Participants page
Done.