<?xml version="1.0"?>
<!-- name="generator" content="blosxom/2.0" -->
<!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN" "http://my.netscape.com/publish/formats/rss-0.91.dtd">

<rss version="0.91">
  <channel>
    <title>people.samba.org/people/   </title>
    <link>http://people.samba.org/people</link>
    <description>Yet another Blosxom weblog.</description>
    <language>en</language>

  <item>
    <title>SambaXP 2007</title>
    <link>http://people.samba.org/people/2007/05/04#sambaxp07-1</link>
    <description>
&lt;p&gt;
It's been a year since I last visited Europe, and spoke at the annual&lt;br&gt;
SambaXP event, so again I'm tracking across the globe, laptop in hand&lt;br&gt;
to our annual geek-out, hosted by SerNet in Goettingen, Germany.
&lt;/p&gt;

&lt;p&gt;
This time it's a little harder - I'm now a married man, and time away&lt;br&gt;
is hard on both of us - but I'm still very much enjoying the trip, and&lt;br&gt;
the chance to catch up with friends, old and new.
&lt;/p&gt;

&lt;p&gt;
This year I'm presenting on a similar topic to last year - Directory&lt;br&gt;
Services - but I hope to bring more than vaporware to the party.  It&lt;br&gt;
has been a long year of work to get an LDAP backend to Samba4, and I&lt;br&gt;
hope I give suitable enough credit to everybody else who worked on the&lt;br&gt;
features that I so critically depend on.
&lt;/p&gt;

&lt;p&gt;
I'm hoping to make a little bit of a splash, and I've planned a live&lt;br&gt;
demo - a risky, but usually entertaining option for a talk.  I'm&lt;br&gt;
hoping to show off what is special about Fedora DS (particularly as&lt;br&gt;
Howard Chu of OpenLDAP is giving a keynote), in the spirit of friendly&lt;br&gt;
rivalry: I'll show Samba4 in front of 2 replicating Fedora DS&lt;br&gt;
servers, in a multi-master replication agreement.
&lt;/p&gt;

&lt;p&gt;
One of the great advantages of Fedora DS is that it's the only Free&lt;br&gt;
Software LDAP server that I know of with full multi-master replication&lt;br&gt;
(including all the fiddly bits of per-attribute conflict resolution).
&lt;/p&gt;

&lt;p&gt;
This should show that, even if we don't have full DRSUAPI (Native AD&lt;br&gt;
replication), that we can have more than a single AD master - nobody&lt;br&gt;
would want Samba4's features in a site with just a single DC.  By&lt;br&gt;
making replication 'somebody else's problem', we leave that to the&lt;br&gt;
experts (replicated LDAP implementations).
&lt;/p&gt;

&lt;p&gt;
It is taking some time to get this demo ready, mostly because I'm&lt;br&gt;
still fairly green at Fedora DS, and to make the demo 'real', I'm&lt;br&gt;
adding in the CN=Configuration partition to the LDAP backend.  This&lt;br&gt;
has required some work on Samba4, and it's configuration of the LDAP&lt;br&gt;
backends, particularly as we have very specific subtree search&lt;br&gt;
behaviours we are looking for.
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2007-04-23
&lt;/p&gt;
</description>
  </item>
  <item>
    <title>From one end of Germany to the other...</title>
    <link>http://people.samba.org/people/2007/05/04#sambaxp07-3</link>
    <description>
&lt;p&gt;
After SambaXP, I decided to experience the full glory of German&lt;br&gt;
trains.  Well, that wasn't the prime motivation, but by train is how&lt;br&gt;
you get around in Germany, and I first travelled north to Bremen.
&lt;/p&gt;

&lt;p&gt;
I stayed as a guest of Univention, a small German IT firm, which has a&lt;br&gt;
product based around Samba 3.0.  As with many companies looking&lt;br&gt;
forward, they are intersted in how Samba4 could fit into their&lt;br&gt;
product, and it was their interest that got ldb_map going again, as&lt;br&gt;
they proposed one of their interns (Martin Keuhl) for a Google Summer&lt;br&gt;
of Code project to fix it up last year.
&lt;/p&gt;

&lt;p&gt;
Then I took a long trip south, and stayed with Kai Blin, in Teubligen,&lt;br&gt;
near Stuttgart.  Kai has been a Google SoC student for Wine the past&lt;br&gt;
two years, and this year has been accepted to work on Samba4's&lt;br&gt;
winbind.  I wanted to get to know him better, and to help him get&lt;br&gt;
started with his work.
&lt;/p&gt;

&lt;p&gt;
I had a wonderful time, and very much enjoyed Kai and Regi's&lt;br&gt;
hospitailiy.  Importantly, we also worked on winbind bugs, isolating a&lt;br&gt;
pidl issue that metze eventually fixed, to get NTLM pass-though&lt;br&gt;
authentication working on our member server.  I hope this gives Kai an&lt;br&gt;
easier start, when he begins his coding, but the real benfit was&lt;br&gt;
getting to know him - understanding people in the flesh makes IRC and&lt;br&gt;
e-mail interactions so much easier...
&lt;/p&gt;

&lt;p&gt;
Now I'm on my long trip home, with the jetlag and my wife's arms to&lt;br&gt;
look forward to.
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2007-05-01
&lt;/p&gt;</description>
  </item>
  <item>
    <title>What a day of talks!</title>
    <link>http://people.samba.org/people/2007/05/04#sambaxp07-2</link>
    <description>
&lt;p&gt;
Yesterday Howard Chu paraded his latest benchmarks on OpenLDAP and&lt;br&gt;
other directory servers, and generally poked fun at the competition,&lt;br&gt;
but today was all about Samba.  We started the day hearing about&lt;br&gt;
Volker talk about how he had been cleaning up Samba3's 'room', taking&lt;br&gt;
the drastic action that has been long-overdue to some of that&lt;br&gt;
codebase.  However, the really impressive talks were later in the day:
&lt;/p&gt;

&lt;p&gt;
Julian presented OpenChange, the exchange connector built on Samba4's&lt;br&gt;
DCE/RPC infrastructure.  Sending and receiving mails may seem like a&lt;br&gt;
simple task, but when you need to use Microsoft's proprietary&lt;br&gt;
protocols to do it, this was a massive challenge that nobody has&lt;br&gt;
succeeded at in the past.  The existing 'WebDAV' connector is a kludge&lt;br&gt;
at best, compared with this 'native protocols' implementation.
&lt;/p&gt;

&lt;p&gt;
The other impressive talk was that of Metze.  Working long and hard on&lt;br&gt;
his research thesis for his university studies, Metze has implemented&lt;br&gt;
pull and push replication with Windows over DRSUAPI.  Similarly, this&lt;br&gt;
is a massive break-though in the use of native protocols, and means&lt;br&gt;
that we know the internal database format used by windows.  This will&lt;br&gt;
allow products like Fedora DS's AD Sync to be improved, to use native&lt;br&gt;
protocols, and I talked to Howard about doing the same for OpenLDAP.&lt;br&gt;
I hope we can see this as a useful tool component, for other projects&lt;br&gt;
to pick Samba4 up for.
&lt;/p&gt;

&lt;p&gt;
Jelmer and I then took the stage to discuss the progress of Samba4.&lt;br&gt;
It has been a long year, but we have made a great deal of progress,&lt;br&gt;
and similarly Jelmer made a much better presentation (with better&lt;br&gt;
planning and practice).  We still did this together, as we have&lt;br&gt;
effectively become co-release managers, but Jelmer did most of the&lt;br&gt;
speaking this time.
&lt;/p&gt;

&lt;p&gt;
We are hoping to move to an Alpha release of Samba4 in the next few&lt;br&gt;
months (next stop is one more 'TP', hopefully in the next week or&lt;br&gt;
two).  Given the list we promised last year, we just don't have that&lt;br&gt;
many blockers any more: In particular, we know the database format, so&lt;br&gt;
we won't loose/require conversion of user's passwords.
&lt;/p&gt;

&lt;p&gt;
My talk on Fedora DS didn't go as well - between the two presentations,&lt;br&gt;
my screen locked, but gnome-screensaver didn't display a password&lt;br&gt;
dialog (just a black screen).  I restarted X, and then lost it's link&lt;br&gt;
to the external display (as I found out only when I got up front).&lt;br&gt;
Tridge came to the rescue, restarting the computer for me, while I&lt;br&gt;
started my talk, but it left me a little flustered.  I never got to&lt;br&gt;
the demo I worked so hard to create, but hope to at least get&lt;br&gt;
reproducible instructions out of it.  I did demo the smart-card&lt;br&gt;
insertion technology (Love had commented that loading smart-cards was&lt;br&gt;
too hard), and at least that worked.
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2007-04-25
&lt;/p&gt;
</description>
  </item>
  <item>
    <title>SambaXP for another year.</title>
    <link>http://people.samba.org/people/2006/04/28#sambaxp06</link>
    <description>
&lt;p&gt;
And again, I find myself on a train, as SambaXP ends for another year.  
&lt;/p&gt;

&lt;p&gt;
SambaXP is 'the' Samba conference, and provides a great opportunity&lt;br&gt;
for us to meet up, particularly for our developers in Europe.  Even&lt;br&gt;
with the horror 23 or so hours flying from Australia, I haven't missed&lt;br&gt;
a conference yet.
&lt;/p&gt;

&lt;p&gt;
Particularly in recent years, SambaXP has given us an opportunity to&lt;br&gt;
hear from our users, as they present on their deployments and&lt;br&gt;
experiences.  This is something that we just can't get at the other&lt;br&gt;
annual conference (the CIFS conference) that many Samba team members&lt;br&gt;
attend.
&lt;/p&gt;

&lt;p&gt;
Likewise we get to talk about technical details of Samba's internals,&lt;br&gt;
without fear that we are exceeding our mandate, or dominating the&lt;br&gt;
schedule.  With Tridge away on EU duty, it was left to Jelmer and I to&lt;br&gt;
deliver the Samba4 Status report.  (Including the compulsory live&lt;br&gt;
demo).  I also had an opportunity to discuss ideas about how we might&lt;br&gt;
integrate Samba4 with existing directory servers.
&lt;/p&gt;

&lt;p&gt;
While presentations are importantly, equally so is the ability to&lt;br&gt;
spend time with my fellow developers.  In particular, it was a great&lt;br&gt;
opportunity to meet with Kai Blin, a Wine developer experimenting with&lt;br&gt;
making Wine use Samba4's GENSEC.  While we were making very good&lt;br&gt;
progress on e-mail and IRC, there is nothing quite like working&lt;br&gt;
problems out in person.
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2006-04-27
&lt;/p&gt;</description>
  </item>
  <item>
    <title>My Grandmother misses me</title>
    <link>http://people.samba.org/people/2006/04/28#taking-time-away</link>
    <description>
&lt;p&gt;
I have this arrangement: Every Saturday, when I'm town, I spend part&lt;br&gt;
or all of the afternoon doing something with my Grandmother.  It is a&lt;br&gt;
special time for both of us, and something we both look forward to.&lt;br&gt;
But there is a catch to this regular routine 'when I'm in town'.  I&lt;br&gt;
won't be home again for a bit, and it will have been 6 weeks by the&lt;br&gt;
time I return.
&lt;/p&gt;

&lt;p&gt;
I've had a ball.  I returned to Tasmania for the first time since I&lt;br&gt;
was 12, and we spend 3 weeks hiking and camping around the apple isle.&lt;br&gt;
And now I'm on a train as I travel though rural Germany.  I'll also be&lt;br&gt;
at LinuxTag before this trip is over.
&lt;/p&gt;

&lt;p&gt;
Meanwhile, back at Hawker (where my Linux network remains, for an&lt;br&gt;
unknown length of time), it seems my computers miss me too.  As we&lt;br&gt;
descended from our camp at Cradle Valley, a message appeared on the&lt;br&gt;
mobile: 'Ring Ben'.  Ben is one of the year 12 students at Hawker, and&lt;br&gt;
in year 11 he was taken on as a 'School-based New Apprentice'.  As the&lt;br&gt;
Network admin, I tried to train him and James in the mysterious arts&lt;br&gt;
of systems and network administration.  In any case, as I left, I&lt;br&gt;
handed him the keys, and a phone number in case it all went to mush.
&lt;/p&gt;

&lt;p&gt;
It went to mush: Somehow they knew, and a server locked up, was&lt;br&gt;
rebooted, and never returned.
&lt;/p&gt;

&lt;p&gt;
It's not the first time this has happened.  Just before I left for the&lt;br&gt;
CIFS conference in 2004, a server decided to spit disks out of it's&lt;br&gt;
RAID array.  I got the critical files onto an alternate server, while&lt;br&gt;
my father waited in the carpark, waiting to rush me to the airport.&lt;br&gt;
Or when my mobile rings, and I'm half-way down the Hume highway to&lt;br&gt;
Melbourne, or attending a family funeral...
&lt;/p&gt;

&lt;p&gt;
How do they know?!?  
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2006-04-27
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Without a computer in sight</title>
    <link>http://people.samba.org/people/2006/03/08#on-the-bike</link>
    <description>
&lt;p&gt;
I recently found some time to get away from the computer, and spent it&lt;br&gt;
on the &lt;a href=&quot;http://www.bigride.com.au/&quot;&gt;NSW Big Bike Ride&lt;/a&gt;.  I, and 700 others, rode our bicycles from&lt;br&gt;
Holbrook to Binalong, over a distance of around 550KM, taking 9 days.
&lt;/p&gt;

&lt;p&gt;
This was an event like no other that I had ever been a part of, and I&lt;br&gt;
most certainly enjoyed it.  But what I enjoyed most was the time spent&lt;br&gt;
with friends, old and new, doing something we all loved.
&lt;/p&gt;

&lt;p&gt;
I'll remember the days, both easy and very, very hard.  I'll remember&lt;br&gt;
the 6AM wakeup calls, from a big bloke named 'Debbie' (a one-off joke&lt;br&gt;
that stuck).  I'll remember packing up a tent in 15mins, still wet&lt;br&gt;
from the morning dew.  I'll remember riding in the crisp morning air,&lt;br&gt;
before the sun and the wind.  I'll remember the sunscreen (applied&lt;br&gt;
like paint, yet still feeling like it will still all sweat off).  I'll&lt;br&gt;
remember the long, long day: 98KM of up and down hills (how could I&lt;br&gt;
ever forget).
&lt;/p&gt;

&lt;p&gt;
But most of all I will remember spending time with people I grew to&lt;br&gt;
know well, and who's company I treasured.  
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2006-03-07
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Scripting Hawker</title>
    <link>http://people.samba.org/people/2006/01/23#hawker-scripts</link>
    <description>
&lt;p&gt;
I recently gave a presentation at the Linux in Education mini-conference, &lt;br&gt;
and was again bugged for my collection of scripts that I use at 
&lt;a href=&quot;http://hawkerc.net&quot;&gt;Hawker College&lt;/a&gt; &lt;br&gt;
(a year 11/12 High School in the ACT).  As the network at Hawker &lt;br&gt;
is 'upgraded' to Win2003, I hope that some last part of what we have&lt;br&gt;
learnt at Hawker is useful to a wider world.
&lt;/p&gt;

&lt;p&gt;
Hawker's network is a collection of Linux servers, all tied togeather &lt;br&gt;
by a bunch of perl scripts.  I've uploaded these to &lt;a href=&quot;http://samba.org/~abartlet/scripts&quot;&gt;my scripts directory&lt;/a&gt;
on my homepage.  
&lt;/p&gt;

&lt;p&gt;
These scripts, and a pile of 'junk code' snippites continually modifed&lt;br&gt;
for various tasks, are what runs my entire network.  There is no&lt;br&gt;
documentation, just the source.
&lt;/p&gt;

&lt;p&gt;
I originaly gave this presentation at the Association of Independent&lt;br&gt;
Schools IT managers conference (when I worked for Novell), but 
&lt;a href=&quot;http://samba.org/~abartlet/lca_edlinux_abartlet_hawker_plain.sxi&quot;&gt;I gave it again&lt;/a&gt; at LCA.
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2006-01-23
&lt;/p&gt;</description>
  </item>
  <item>
    <title>On the path to a Samba4 technology preview</title>
    <link>http://people.samba.org/people/2006/01/13#samba4-tech-preview</link>
    <description>
&lt;p&gt;
It is 3 months since Tridge posted his proposal for a Samba4&lt;br&gt;
technology preview, and almost a month since I started a real push on&lt;br&gt;
the topic.  It has been a wild ride, with hundreds of commits, strong&lt;br&gt;
mailing list discussion and real progress on packaging and external&lt;br&gt;
testing.
&lt;/p&gt;

&lt;p&gt;
For me, the race for a technology preview started while I was spending&lt;br&gt;
time in the US, talking with companies about Samba4.  I was hoping to&lt;br&gt;
drum up the kind of interest that would put a corporate backing behind&lt;br&gt;
the Samba4 DC (and potentially find me some work back home in the&lt;br&gt;
process).  But time after time, I found myself having to sell our&lt;br&gt;
progress so far, against a backdrop without a prospect of a release.
&lt;/p&gt;

&lt;p&gt;
We have made great progress on Samba4, and we achieved a AD domain join&lt;br&gt;
and login with Kerberos and the infamous PAC months ago.  But as Roger&lt;br&gt;
Binns (of BitPIM fame) so eloquently put it: 'If you never release,&lt;br&gt;
you never release'.  Each manager and engineer I talked with didn't&lt;br&gt;
know of our progress so far, and was pleasantly surprised.  But&lt;br&gt;
pleasant surprises doesn't sell us into upper management, doesn't get&lt;br&gt;
us users and doesn't attract us developers.
&lt;/p&gt;

&lt;p&gt;
I came back from the US energised and with a single goal in mind: To&lt;br&gt;
produce a technology preview by the time Tridge gave his 'Samba4&lt;br&gt;
status update' talk at Linux.conf.au in Dunedin NZ.
&lt;/p&gt;

&lt;p&gt;
And that has been my battle ever since.  Joined in my cause have been&lt;br&gt;
my fellow developers, both on the Samba Team and further afield.  In&lt;br&gt;
particular Jelmer, Metze and Simo found time in their Christmas holidays to&lt;br&gt;
keep the tree ticking over, and Steinar H. Gunderson pushed the Debian&lt;br&gt;
packaging from an in-tree idea into a reality in Debian's experimental&lt;br&gt;
distribution.
&lt;/p&gt;

&lt;p&gt;
Samba4 is rapidly growing up, and I've been able to put some polish on&lt;br&gt;
the raw technologies.  For example, we now support 'vampire'&lt;br&gt;
operations from the SWAT GUI, doing the domain join and vampire in the&lt;br&gt;
one action.  This extracts the full user database from windows and&lt;br&gt;
replicates it, including passwords and Kerberos attributes, into&lt;br&gt;
Samba4's LDB database.  
&lt;/p&gt;

&lt;p&gt;
Likewise, we have closed off some of the silly things that were&lt;br&gt;
blocking the release, like bugs in SWAT and lack of any access control&lt;br&gt;
on LDB.  While the solutions may not be final, we can at least make&lt;br&gt;
the technology preview release with a straight face.
&lt;/p&gt;

&lt;p&gt;
To everybody who has helped us get this far, Congratulations!
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2006-01-14
&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Different ways to spend Christmas day</title>
    <link>http://people.samba.org/people/2005/12/30#christmas-2005</link>
    <description>
&lt;p&gt;
As the Christmas week rolls by, it seems right to ponder the different&lt;br&gt;
and very enjoyable ways I have spent this time over the past years.
&lt;/p&gt;

&lt;p&gt;
In the past few years I have enjoyed to spend some of the time before&lt;br&gt;
Christmas camping, particularly at Tidal River, Wilsons Promontory.  A&lt;br&gt;
few years back we were fortunate enough to spend Christmas day there.
&lt;/p&gt;

&lt;p&gt;
This year Christmas was postponed by a few hours (into the early&lt;br&gt;
evening), and Dad and I used the opportunity to go for a bike ride.&lt;br&gt;
The weather was great, not to hot, and we circled Lake Burley Griffin.&lt;br&gt;
That the roads were dead quiet was no surprise, but what I was quite&lt;br&gt;
pleasantly surprised by was how many families had chosen the lake&lt;br&gt;
foreshore for the Christmas lunch.  All around the lake, families were&lt;br&gt;
enjoying each other and this magnificent centrepiece to our capital.
&lt;/p&gt;

&lt;p&gt;
As we completed our ride, most had packed up, and we got home for our&lt;br&gt;
own Christmas dinner, the quiet ride such a counterpoint to the hassle&lt;br&gt;
and bustle so often associated with this season of Peace and Goodwill.
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2005-12-31
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Heimdal Progress</title>
    <link>http://people.samba.org/people/2005/12/18#heimdal-progress</link>
    <description>
&lt;p&gt;
Over the past few weeks and months, some great progress has been made&lt;br&gt;
in the area of the Samba4 KDC and Kerberos library.  This is in no&lt;br&gt;
small part been due to the cooperation of the Heimdal Kerberos team,&lt;br&gt;
in the form of Love H&amp;ouml;rnquist &amp;Aring;strand.  
&lt;/p&gt;

&lt;p&gt;
I have been working to make Samba4's hooks into Heimdal more&lt;br&gt;
reasonable, and as I have done so Love has merged many of them into the&lt;br&gt;
upstream code.  As an example of this, we recently changed the HDB&lt;br&gt;
interface, so that it would return pointers to allow additional&lt;br&gt;
manipulation (such as give me a PAC for this user).  These are&lt;br&gt;
critical hooks for Samba4, but are also unique to our requirements.
&lt;/p&gt;

&lt;p&gt;
Love has met me half way, not introducing all the hooks into Heidmal,&lt;br&gt;
but making my patch adding them smaller.  This makes it easier for me&lt;br&gt;
to merge new upstream code, and ensures more of the code-paths in&lt;br&gt;
Samba4 is tested by other Heimdal users.
&lt;/p&gt;

&lt;p&gt;
At the functional level, we now have the same level of account&lt;br&gt;
management checking in Heimdal as the NTLM authentication code, and we&lt;br&gt;
correctly issue the PAC into the TGT.  Behind the hdb interface, we&lt;br&gt;
are now able to call into common libraries for name translation and&lt;br&gt;
authorisation, including hacks such as the 'netbios name as&lt;br&gt;
workstation'.
&lt;/p&gt;

&lt;p&gt;
On the much more mundane level, I have had a number of other issues in&lt;br&gt;
Heimdal and Samba4 resolved with ease:  My changes for GSSAPI&lt;br&gt;
credentials were not accepted, instead Love coded a better API.&lt;br&gt;
Similarly, MEMORY: keytabs have been improved due to Samba's&lt;br&gt;
requirements.  
&lt;/p&gt;

&lt;p&gt;
This day to day co-operation has made my life much easier, as I&lt;br&gt;
navigate the maze that is Kerberos.
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2005-12-17
&lt;/p&gt;</description>
  </item>
  <item>
    <title>The peace of God</title>
    <link>http://people.samba.org/people/2005/11/12#peace-of-god</link>
    <description>
&lt;i&gt;And the peace of God, which transcends all understanding, will guard&lt;br&gt;
your hearts and your minds in Christ Jesus. &lt;/i&gt; Philippians 4:7 (NIV)
&lt;/p&gt;

&lt;p&gt;
In the Anglican tradition, this forms part of the final blessing in&lt;br&gt;
the service.  Like much of the liturgy it is said so often, but it&lt;br&gt;
really seemed to mean something in the past week:
&lt;/p&gt;

&lt;p&gt;
It has been a rough week, and in many ways I feel like a punching bag,&lt;br&gt;
taking a hit, and recoiling for more.  So many things are changing,&lt;br&gt;
yet each day I stand up, even more ready for what the world may&lt;br&gt;
bring.  
&lt;/p&gt;

&lt;p&gt;
I should have every right to feel angry: Life was already changing,&lt;br&gt;
but in the course of a week, I lost both a contract position with SuSE&lt;br&gt;
and learned that the Linux/Samba/LDAP network I built at Hawker&lt;br&gt;
College would be dismantled, to be replaced with Windows 2003.
&lt;/p&gt;

&lt;p&gt;
But angry is not how I feel.  Disappointed certainly.  Frustrated, but&lt;br&gt;
more than ever in such difficult circumstances I felt peace.  I cannot&lt;br&gt;
explain it any way but in faith, and in the sound knowledge that no&lt;br&gt;
matter the frustrations of this world, that there are much bigger&lt;br&gt;
plans for my life.
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2005-11-13
&lt;/p&gt;</description>
  </item>
  <item>
    <title>SamSync, the unlikely hero</title>
    <link>http://people.samba.org/people/2005/09/03#samba4-samsync</link>
    <description>
&lt;p&gt;
Over the weeks before the CIFS conference, both metze and I spent time&lt;br&gt;
trying to track down remaining problems with the PAC.  We got to the&lt;br&gt;
stage of being able to verify the signature, and later to&lt;br&gt;
reconstructing an identical PAC, through a full parse and resign&lt;br&gt;
process.
&lt;/p&gt;

&lt;p&gt;
So, why did I venture off into the world of SamSync?  SamSync is the&lt;br&gt;
windows NT4 SAM (users, groups and passwords) replication protocol.&lt;br&gt;
It features in the 'net rpc samsync' command in Samba 3.0, and is a&lt;br&gt;
key feature there.  I had spent some time on the protocol in late&lt;br&gt;
2004, but why finish off that work now?  It certainly sparked comment&lt;br&gt;
from Tridge, along the lines of 'samsync is important, but it's not&lt;br&gt;
exactly key for a release.  How about domain member support?'.
&lt;/p&gt;

&lt;p&gt;
This is why I call it the unlikely hero, because it seemed just a&lt;br&gt;
diversion.  What I knew, (but Tridge didn't yet know), was how I was&lt;br&gt;
trying to prove our internal routines:
&lt;/p&gt;

&lt;p&gt;
What we were not confident of was the data inside the PAC: could the&lt;br&gt;
data, rather than the format, be causing the client rejection?
&lt;/p&gt;

&lt;p&gt;
To answer that, we needed to be able to match the windows data, to&lt;br&gt;
operate in a mode where we would issue exactly the same data as we&lt;br&gt;
would see from a windows system, to show that it matched.  From there&lt;br&gt;
we should be able to do a byte-for-byte comparison, and prove we had&lt;br&gt;
things correct.
&lt;/p&gt;

&lt;p&gt;
I saw there being two ways to get data identical to windows: One is&lt;br&gt;
to ad-hock, hard code the correct data into various points in the&lt;br&gt;
code, while the other would be to 'correctly' generate that data from&lt;br&gt;
the database.  I chose to pursue the generation option, because we&lt;br&gt;
would need to have a correct mapping from ldb to the PAC structures&lt;br&gt;
anyway.  (We could also validate with LDAP the correctness of the&lt;br&gt;
SamSync, and therefore validate the entire area pretty well).
&lt;/p&gt;

&lt;p&gt;
The SamSync turned out to be even more useful than that, and when&lt;br&gt;
Tridge and I were playing the proxy attacks between the windows client&lt;br&gt;
and AD DC, we could do so knowing we had at all times the full and&lt;br&gt;
current set of (preferred) arcfour-hmac-md5 keys.  This allowed us to&lt;br&gt;
swap Samba4 and AD for each other without changing the client at all,&lt;br&gt;
as well as giving us the key material for 'resigning' the PAC (when&lt;br&gt;
the TGT was generated by AD, but we issued the service ticket).
&lt;/p&gt;

&lt;p&gt;
Like all things, the SamSync code could be improved, and the main pain&lt;br&gt;
we felt when using it was the lack of msDS-keyVersionNumber&lt;br&gt;
replication (as this is not an NT4 concept).  In production, we may&lt;br&gt;
have a combination process using both LDAP and SamSync, or move to the&lt;br&gt;
newly decoded DSSsync code (the AD way of doing things).
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2005-09-04
&lt;/p&gt;</description>
  </item>
  <item>
    <title>What an anticlimax!</title>
    <link>http://people.samba.org/people/2005/09/03#pac-finally</link>
    <description>
&lt;p&gt;
Just a week ago, we finally figured out the last of the problems with&lt;br&gt;
the PAC.  Nothing complex really, just one time field that must match&lt;br&gt;
another.
&lt;/p&gt;

&lt;p&gt;
It makes it seem so simple really: What was not simple were the&lt;br&gt;
efforts we needed to put in, to get this far.
&lt;/p&gt;

&lt;p&gt;
Between the two of us, we spent Thursday and Friday of last week on&lt;br&gt;
the problem, working though the status so far, and devising solutions.&lt;br&gt;
Thursday was a day of frustration: Particularly with an odd bug in&lt;br&gt;
ethereal, which prevented us seeing or copying the decrypted data,&lt;br&gt;
despite it being displayed in the protocol tree.
&lt;/p&gt;

&lt;p&gt;
We reproduced the problem, analysed traces, compared tickets, and&lt;br&gt;
everything seemed to be in order.  There were a few flags different,&lt;br&gt;
but nothing that stood out.
&lt;/p&gt;

&lt;p&gt;
The evening rolled around, and we both headed out for a night of geeky&lt;br&gt;
talks and pizza at CLUG.  Tridge continued to work that evening, and I&lt;br&gt;
got some well-needed sleep.
&lt;/p&gt;

&lt;p&gt;
Clearly this wasn't a problem that Tridge was going to let die,&lt;br&gt;
because the next morning (Friday) I heard news that Tridge had made&lt;br&gt;
the it work, if we didn't use our KDC (but used Microsoft's instead).&lt;br&gt;
This started the process to chase things down, and after spending the&lt;br&gt;
day on other tasks I returned to work on the puzzle.
&lt;/p&gt;

&lt;p&gt;
Finally, it simplified the problem down, and we could smell a possible&lt;br&gt;
victory.  By later that evening we had cracked it.
&lt;/p&gt;

&lt;p&gt;
Tridge made an interesting post detailing some of the final steps we used, which is well-worth repeating here:
&lt;/p&gt;

&lt;pre&gt;

I thought it might be useful to describe the specifics of this
technique, as others working on similar problems may find it useful.

Andrew and I setup a vmware network like this:

      ------- w2k3 PDC
      |
 Samba4
      |
      ------- w2k3 member server

the linux box had 2 virtual network interfaces, on 192.168.114.1 and
192.168.115.1. 

We first joined the w2k3 member server to the w2k3 PDCs domain. Then
we used the samsync code to replicate the account information from
that PDC onto the Samba box, so the Samba4 box was using exactly the
same keys and account information as the w2k3 box for the same domain
name.

Then we used a combination of 'sockspy' and 'udpproxy' which are two
little hackish C progs from junkcode (junkcode.samba.org) to proxy
different combinations of the various protcols, alternately allowing
the Samba4 box to serve the protocols or the w2k3 PDC to serve them to
the w2k3 member server. The various protocols we needed are:

 - udp 88  - kerberos
 - udp 53  - dns
 - udp 389 - cldap
 - tcp 135 - rpc portmapper
 - tcp 139 - SMB/CIFS
 - tcp 389 - ldap
 - tcp 445 - SMB/CIFS
 - tcp 1024, 1025, 1026 - RPC 

So we did things like this:

  UDP=&quot;88 389&quot;
  for p in $UDP; do
    ./udpproxy $p 192.168.114.5 $p &amp;
  done

  TCP=&quot;135 139 389 445 1024 1025 1026&quot;
  for p in $TCP; do
    while ./sockspy $p 192.168.114.5 $p; do date; done &amp;
  done

and in that way we proxied whatever selection of protocols we wanted
to.

The first test was to proxy all protocols, except for DNS which we
setup on the Linux box to always point all the PDC names at the Linux
box IP. This was the 'null' test, and showed that logins work via the
proxies.

Next, we proxied all protocols except kerberos, and setup smbd to only
server kerberos. This showed the &quot;PAC bug&quot;, as expected. That proved
that the bug is definately kerberos related, and not an artifact of
some RPC or LDAP problem.

Next, we proxied all only kerberos, serving everying else from
smbd. In this case the login worked, again showing the bug is kerberos
related.

Finally, we hacked udpproxy.c to only proxy packets smaller than 400
bytes. This was a really nasty hack, but had the effect of only
proxying the AS-REQ packet, and not the TS-REQ. This meant the client
gave us back the PAC from the AS-REP from the real PDC in the TS-REQ,
which meant that the Samba4 kdc received the real PAC from the w2k3
box. We could then re-sign this PAC using the clients keys and send it
out in the TS-REP from smbd. This worked, giving us a successful
login.

That last test proved the problem lay in the PAC itself, and not in
any other part of the krb5 packets. From there we did a byte by byte
comparison of our generated PAC to the one that w2k3 gave, and tested
'fixing' each field by replacing it with the field from the w2k3
PAC. The field that turned out to be critcal was
LOGON_NAME-&gt;logon_time, which must exactly equal the time from the
AS-REP authtime field.  That solved the puzzle.

Cheers, Tridge

&lt;/pre&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2005-09-04
&lt;/p&gt;</description>
  </item>
  <item>
    <title>The slog end of testing - Binary searching</title>
    <link>http://people.samba.org/people/2005/08/19#binary-search</link>
    <description>
&lt;p&gt;
I always 'knew' what testing involved, and have been happy to run&lt;br&gt;
'make test', to give myself some confidence that a change was good, or&lt;br&gt;
even to work on the automated testing system that is the samba build&lt;br&gt;
farm.  What I've never done before is a real-life binary search over&lt;br&gt;
months of Samba changes, in the hunt for a real regression.
&lt;/p&gt;

&lt;p&gt;
That is how I've spent the past couple of days, working on my test-net&lt;br&gt;
at Hawker College, trying to pin down why Samba 3.0.13 worked, but&lt;br&gt;
Samba 3.0.20rc2 didn't.
&lt;/p&gt;

&lt;p&gt;
In many ways, the procedure is simple:  &lt;br&gt;
 &lt;ol&gt;
 &lt;li&gt;Download Samba&lt;/li&gt;
 &lt;li&gt;Install Samba&lt;/li&gt;
 &lt;li&gt;Attempt domain logon from windows client&lt;/li&gt;
 &lt;li&gt;Record result&lt;/li&gt;
 &lt;li&gt;Save network trace&lt;/li&gt;
 &lt;li&gt;Reset client&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;
This is done in a bisection, as we try to half the distance to the bug&lt;br&gt;
each time.
&lt;/p&gt;

&lt;p&gt;
What is not simple is the waiting, particularly as my poor, slow test&lt;br&gt;
server (a PIII 700Mhz) compiles up yet another Samba revision.
&lt;/p&gt;

&lt;p&gt;
But with few other clues: the network trace suggests a particular&lt;br&gt;
packet may be upsetting the client, but I'm not sure why or how, I'm&lt;br&gt;
left to try and find the change-set that broke it.
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2005-08-19
&lt;/p&gt;</description>
  </item>
  <item>
    <title>And it's all over, for another year</title>
    <link>http://people.samba.org/people/2005/08/09#cifs2005</link>
    <description>
&lt;p&gt;
As a slowly recover from jet-lag, I realise that it is all over again.&lt;br&gt;
Again I'm at home, trying to migrate back into a normal sleep pattern,&lt;br&gt;
and again I'm trying to do all the things I got so rev'ed up about at&lt;br&gt;
the conference.
&lt;/p&gt;

&lt;p&gt;
From trying to convince Windows to accept our PAC, to sucessfully&lt;br&gt;
fixing Samba to accept logins from Windows Vista clients, it has been&lt;br&gt;
an eventful week.  Best of all was the chance to talk tech-to-tech&lt;br&gt;
with the other CIFS vendors, and the long hours in the lab: able to&lt;br&gt;
work face-to-face with the others on the team.
&lt;/p&gt;

&lt;p&gt;
I hope we continue to get the opportunity to have such an event, be it&lt;br&gt;
at the 'CIFS Conference' or something less formal.  Now if only I can&lt;br&gt;
stay in one spot long enough to implement all these things...
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2005-08-09
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Images of God</title>
    <link>http://people.samba.org/people/2005/08/09#images_of_god</link>
    <description>
&lt;p&gt;
Recently, I attended Convo C3, a 'youth' camp run by the local&lt;br&gt;
Anglican Church.  It was a great experience, mostly because of the&lt;br&gt;
people I met.
&lt;/p&gt;

&lt;p&gt;
One of the many questions posed at the camp was 'what is your image of&lt;br&gt;
God, and how has it changed?'.  And since then, I've been thinking&lt;br&gt;
about this point: There are of course many images, but the one that&lt;br&gt;
sprang to mind was that of a soft breeze over the water.  Sitting in&lt;br&gt;
the water, you can go about life pretending it's not there, but reach&lt;br&gt;
out with faith, put up the windsurfer and God races you across the&lt;br&gt;
surface, on an amazing journey with him.
&lt;/p&gt;

&lt;p&gt;
The other image of God I have is very simple:  It is people, and the&lt;br&gt;
human condition.  We are made in God's image, and much as we stray far&lt;br&gt;
from that at times, the Church is about community, about people and&lt;br&gt;
about relationships with one another.  
&lt;/p&gt;

&lt;p&gt;
As a certified geek (and currently working from home), I certainly am&lt;br&gt;
feeling the last part: I gained so much from simply spending time with&lt;br&gt;
the other campers at C3, hearing their story, telling mine, without&lt;br&gt;
strings or overtones attached.  It is sad: we so easily loose our&lt;br&gt;
relationships with one another, yet these are the very things God gave&lt;br&gt;
us to make us strong.
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2005-07-05
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Milestones and Graduation</title>
    <link>http://people.samba.org/people/2005/08/09#graduation</link>
    <description>
&lt;p&gt;
Well, I finally did it:  I graduated from the Australian National&lt;br&gt;
University as a Bachelor of Software Engineering.  I say finally,&lt;br&gt;
because I decided to put it off for 6 months, to take a pre-Christmas&lt;br&gt;
holiday instead. 
&lt;/p&gt;

&lt;p&gt;
I enjoyed the big day, wore my silly dress, silly hat and specially&lt;br&gt;
coloured silly hood, walked across the stage and shook the hand of&lt;br&gt;
Chancellor.  Actually, it all looked very nice.
&lt;/p&gt;

&lt;p&gt;
But perhaps more noted in that big day were the comments made from the&lt;br&gt;
podium:  &lt;i&gt;&quot;and there will be some children with us on this special day&lt;br&gt;
today, who we hope will some day walk proudly across a stage similar&lt;br&gt;
to this one.  And so, if they act as children, we won't let that&lt;br&gt;
bother us one little bit. &quot;&lt;/i&gt;.  It brought such a beautiful humanity&lt;br&gt;
to what was also a formal and joyful occasion. 
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2005-07-14
&lt;/p&gt;</description>
  </item>
  <item>
    <title>The great game of PAC-a-mole</title>
    <link>http://people.samba.org/people/2005/08/09#pac-a-mole</link>
    <description>
&lt;p&gt;
Perhaps the single biggest challenge in Samba4's implementation of the&lt;br&gt;
windows logon protocols is that of the PAC.  Micrsoft's proprietry&lt;br&gt;
extension to Kerberos, the PAC is a signed and validated data&lt;br&gt;
structure that includes information on the user and their group&lt;br&gt;
membership.
&lt;/p&gt;

&lt;p&gt;
For the last 12 months, I have been working on and off, along with&lt;br&gt;
others on the Samba and Heimdal teams, to built a KDC that a Windows&lt;br&gt;
client will respect as one of it's own.  Slowly, we have built&lt;br&gt;
backends, hacks, and patches for the KDC we derived from the Heimdal&lt;br&gt;
Kerberos.
&lt;/p&gt;

&lt;p&gt;
As the months have gone by, we have got closer and closer: We now&lt;br&gt;
accept the PAC when generated by windows, and have written tests (with&lt;br&gt;
static data) that ensure we continue to.  We accept the PAC we&lt;br&gt;
generate, and can produce a PAC that matches the windows format&lt;br&gt;
exactly.  But still, we don't have it quite right: we still don't&lt;br&gt;
have something right.
&lt;/p&gt;

&lt;p&gt;
It is a game I have come to know as whack a mole: Always one more&lt;br&gt;
thing, one more problem to be solved, and no particular clue how to&lt;br&gt;
solve it.  The hunt is again on, and the exact byte-for-byte&lt;br&gt;
differences need to be tracked down, one by one.
&lt;/p&gt;

&lt;p&gt;
For the moment, I've decided to leave the PAC, and I'll concentrate on&lt;br&gt;
other areas in Kerberos (such as improving the structure of the link&lt;br&gt;
between Heimdal and Samba4), as well as a kpasswd implementation.  I&lt;br&gt;
figure that even if I can't get windows to accept what I'm producing,&lt;br&gt;
I may as well try to get Apple, NetApp and Samba3 clients to play&lt;br&gt;
ball.
&lt;/p&gt;

&lt;p&gt;
In going so far, I do have to thank 
&lt;a href=&quot;mailto:metze@samba.org&quot;&gt;Stefan Metzmacher&lt;/a&gt; and 
&lt;a href=&quot;http://people.su.se/~lha/&quot;&gt;Love H&amp;ouml;rnquist &amp;Aring;strand&lt;/a&gt;, &lt;br&gt;
because without their efforts, going even this far would not be possible.
&lt;/p&gt;

&lt;p&gt;
Andrew Bartlett&lt;br&gt;
2005-08-09
&lt;/p&gt;</description>
  </item>
  <item>
    <title>San Francisco Chronicle Marathon</title>
    <link>http://people.samba.org/people/2005/08/02#2005-08-01</link>
    <description>
&lt;p&gt;
Well yesterday was the day.  Mileage from last week ended up being:
&lt;/p&gt;

&lt;p&gt;
Date: Jul 24 - 30, 2005&lt;br&gt;
Weekly Mileage: 16&lt;br&gt;
Total Number of runs: 4&lt;br&gt;
Longest Run: 7.2 (1:00:00)
&lt;/p&gt;

&lt;p&gt;
The race started at 5:20am and had somewhere around 15,000 registered runners (for all events) according to the newspaper.   The temperature was in the upper 50's and foggy.  Given the early start time, the first half hour or so would be in the dark.  
&lt;/p&gt;

&lt;p&gt;
Dad ran the 1st half and I ran the full.  There's something about this run that is really attractive to me.  The fog was still heavy over the bridge and you could see the towers rising up.  Inspiring enough to take you mind off as I reached the first hour mark.
&lt;/p&gt;

&lt;p&gt;
One the way back across the bridge I was scanning the people in the opposite direction trying to spot Dad in the crowd.  I didn't see him soon enough but at 1:07:41 I heard him run by as he carried on a conversation with a couple of other runners.  I knew his pace was pretty close to the 2 hour mark he was shooting for.  
&lt;/p&gt;

&lt;p&gt;
After the bridge came Golden Gate park.  I hit the first half at 1:47:40.  I made some time up coming through the park and hit the 20.2 time split at 2:48:23.  The highlight though was to hit 22 at 2:58:00.  
&lt;/p&gt;

&lt;p&gt;
At 23 I started to hit my threshold and honestly just got tired of running.  But unlike the Philadelphia marathon, I knew I would finish.  So I hit 30 second walks with 1/4 to 1/2 runs.  I still had enough for a spring the last 385 yards to finish up 3:35:06.  That was good enough to rank 439 out of 3123 for the men's group and 502 out of 4869 overall.
&lt;/p&gt;

&lt;p&gt;
Dad finished up extremely close to his goal at 2:00:56.  
&lt;/p&gt;

&lt;p&gt;
We are both hooked on this run now.  It could become an annual event.  
&lt;/p&gt;

&lt;p&gt;
`whoami`$ jerry
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Racing Times over the past year</title>
    <link>http://people.samba.org/people/2005/08/02#2005-07-27</link>
    <description>
&lt;p&gt;
Waiting on a race drives me crazy.  So far things have gone as expected this week.  A couple of 30 minute runs the past few days.  I'm looking for an hour today (7 - 7.5 miles).   
&lt;/p&gt;

&lt;p&gt;
In the meantime, I figured this would be a good time to transfer my race times over the past year from paper.
&lt;/p&gt;

&lt;p&gt;
Date: May 29, 2004&lt;br&gt;
Race: Jubilee Run (Mont, AL)&lt;br&gt;
Distance: 8K&lt;br&gt;
Time: 42:21
&lt;/p&gt;

&lt;p&gt;
Date: Aug 1, 2004&lt;br&gt;
Race: San Francisco 1/2 Marathon&lt;br&gt;
Distance: 13.1 miles&lt;br&gt;
Time: 1:52:33
&lt;/p&gt;

&lt;p&gt;
Date: Aug 21, 2004&lt;br&gt;
Race: Pike Road (AL)&lt;br&gt;
Distance: 10K&lt;br&gt;
Time: 48:04
&lt;/p&gt;

&lt;p&gt;
Date: Nov 11, 2004&lt;br&gt;
Race: Chewacla Start Park (AL)&lt;br&gt;
Distance: 10k&lt;br&gt;
Time: 46:55
&lt;/p&gt;

&lt;p&gt;
Date: Nov 21, 2004&lt;br&gt;
Race: Philadelphia Marathon&lt;br&gt;
Distance: 26.2 miles&lt;br&gt;
Time: 3:41:38 (chip time)
&lt;/p&gt;

&lt;p&gt;
Date: Mar 5, 2005&lt;br&gt;
Race: Auburn Classic Half Marathon&lt;br&gt;
Distance: 13.1 miles&lt;br&gt;
Time: 1:41:30
&lt;/p&gt;

&lt;p&gt;
Date: Apr 2, 2005&lt;br&gt;
Race: Marine Corp 1/2 Marathon (Albany, GA)&lt;br&gt;
Distance: 13.1 miles&lt;br&gt;
Time: 1:42:40
&lt;/p&gt;

&lt;p&gt;
Date: May 22, 2005&lt;br&gt;
Race: Jubilee Run (Mont, AL)&lt;br&gt;
Distance: 8K&lt;br&gt;
Time: 36:01
&lt;/p&gt;

&lt;p&gt;
&lt;br&gt;
`whoami`$ jerry
&lt;/p&gt;</description>
  </item>
  <item>
    <title>Training Log for week ending Jul 23</title>
    <link>http://people.samba.org/people/2005/08/02#2005-07-25</link>
    <description>
&lt;p&gt;
I stopped keeping a training log after my last marathon (Philadelphia, last November).  Just ended up being a hassle.  I thought maybe I would have better luck if I tracked my weekly mileage instead of daily totals.  And since I spend &lt;b&gt;so&lt;/b&gt; much time in front of a computer, a blog was pretty obvious.  
&lt;/p&gt;

&lt;p&gt;
Date: Jul 17 - 23, 2005&lt;br&gt;
Weekly Mileage: 30&lt;br&gt;
Total Number of runs: 5&lt;br&gt;
Longest Run: 10 (1:25:00)
&lt;/p&gt;

&lt;p&gt;
Two weeks out from the &lt;a href=&quot;http://www.runsfm.com/index2.htm&quot;&gt;San Francisco Marathon&lt;/a&gt; and I'm trying to recuperate from the final 20 miler.  Five days a week is still the normal but the mileage drop will help me recover some.  I'm about sick of training at this stage.  The final week is always a little nerve racking because I feel like I should be pushing towards the last minute.   Of course, that's self-defeating.  So instead I'll plan about 3 x 3 mile runs and one 5 miler to finish up before the flight to SF.  
&lt;/p&gt;

&lt;p&gt;
`whoami`$ jerry
&lt;/p&gt;</description>
  </item>
  </channel>
</rss>