Fedora workshop, GEC, Barton Hill, Thiruvananthapuram, Kerala, India
by susmit shannigrahi
---------- Forwarded message ----------
From: Shakthi Kannan <shakthimaan(a)gmail.com>
Date: Tue, Mar 31, 2009 at 9:16 AM
Subject: Fedora workshop, GEC, Barton Hill, Thiruvananthapuram, Kerala, India
To: fedora-marketing-list(a)redhat.com
Hi,
I would like to thank Prof. Ranjith Kumar, Department of Mechanical
Engineering, Government Engineering College (GEC), Barton Hill,
Thiruvananthapuram, Kerala, India for coordinating with me for the
past one month for the National Seminar event on Embedded Design with
GNU/Linux that was held on Saturday, March 21, 2009:
http://fsc.gecbh.ac.in/
I would also like to thank the Directorate of Technical Education, and
Kerala State Council for Science, Technology, and Environment for
organizing the event.
I discussed basic concepts of embedded systems, and gave a demo of
gEDA tools suite (gschem, pcb, qucs, iverilog, gtkwave) on Fedora 10.
Some photos taken during the visit are available at:
http://www.shakthimaan.com/Mambo/gallery/album54
Regards,
SK
--
Shakthi Kannan
http://www.shakthimaan.com
--
Fedora-marketing-list mailing list
Fedora-marketing-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-marketing-list
--
Regards,
Susmit.
=============================================
ssh
0x86DD170A
http://www.fedoraproject.org/wiki/user:susmit
=============================================
15 years
Fwd: Update and Report on Fedora August 2008 Intrusion
by susmit shannigrahi
---------- Forwarded message ----------
From: Paul W. Frields <stickster(a)gmail.com>
Date: Mon, Mar 30, 2009 at 7:30 PM
Subject: Update and Report on Fedora August 2008 Intrusion
To: fedora-announce-list <fedora-announce-list(a)redhat.com>
This communication provides additional information on the Fedora
infrastructure intrusion first reported on August 14, 2008. In part
this communication reiterates information provided in previous
announcements.
On August 12, 2008, a failed cron job on a Fedora host reported an
error to the Fedora system administrators. While investigating the
source of this error, the sysadmins reviewed the recent logs and
discovered that the package complement on the host had changed.
Further investigation showed that changes were the result of tampering
by an intruder. Once the extent of the problem was discovered, we
notified the community:
https://www.redhat.com/archives/fedora-announce-list/2008-August/msg00008...
The compromise was not the result of a software vulnerability, and as
we have previously stated, our investigation has revealed no such
vulnerabilities. Instead, the intruder took a copy of a SSH private
key which was not secured with a passphrase from a system outside the
Fedora infrastructure. The intruder then used that key, which
belonged to a Fedora administrator, to access Fedora systems. In
addition, based on system log sudo entries, we believe the intruder
also compromised that user's password. New security policies for
Fedora administrators directly address the further safeguarding of
keys, as noted below.
The Fedora package signing key was present on a system to which the
intruder had access during the time of the event, but the results of
our investigation did not lead us to believe the intruder accessed the
key.
The intruder used the account's privileges to build modified versions
of openssh and rpm. These packages would have allowed the intruder to
capture the passphrases of unwitting users on our build system, or the
passphrase used to secure the package signing key. With the signing
key's passphrase and access to that key, the intruder would have been
able to fraudulently sign packages.
The intruder did deploy the modified packages, and the modified SSH
package may have captured passphrases for a short time. However, the
investigation supports the conclusion that the modified packages were
discovered before anyone accessed the system to sign any packages
using the modified RPM package. Therefore, we do not believe the
intruder ever had access to the passphrase to the signing key.
Nevertheless, previous announcements have explained clearly the
precautionary reasons for our earlier decision to deploy a new package
signing key. Details on the process and progress of the signing key
changes can be found here:
https://fedoraproject.org/wiki/New_signing_key
The modified packages were only installed on a small number of Fedora
infrastructure systems, and therefore we do not believe Fedora account
holders were at significant risk during the time the intruder had
these packages in place. We also required passphrase and SSH key
changes from Fedora users, to increase our confidence going forward.
To reiterate, our analysis supports our initial findings that the
Fedora Project infrastructure delivered no software compromised by the
intruder to any of its mirrors, or the master repository from which
they synchronize content. Our investigation also shows that the
intrusion affected only a few internal Fedora infrastructure servers.
Most of the mitigation work done by the Fedora Infrastructure team was
precautionary, and allows us to have higher confidence in our present
and future work.
The Fedora Infrastructure team quickly responded to the threat,
isolated the systems in question from the network, made snapshots of
affected hosts, assessed the damage, and proceeded to rebuild Fedora's
entire infrastructure essentially from scratch. By the end of the
first week after the event, most essential systems were functioning
nominally again. The remainder of the work took close to three weeks
to complete fully, and return all systems to normal status.
To increase our security posture, the Fedora Infrastructure team now
requires all members of the Fedora system administrator groups to use
passphrases on their private keys. That policy is found, along with
other policies of the Infrastructure team, here:
http://infrastructure.fedoraproject.org/csi/security-policy/
The Infrastructure team is also actively developing a Community
Services Infrastructure project (http://fedorahosted.org/csi) and
supporting documentation to include these lessons in their guidance.
Team members have also worked on deploying SELinux throughout our
infrastructure as well as an audit and prelude intrusion detection
system for added good measure. Furthermore, the Fedora release
engineering team is also leading efforts on further improvements and
refinements to Fedora's package signing system and procedures.
Community members are invited to contact the appropriate Fedora team
if they wish to get involved in any of these processes.
The specific facts that emerged during the investigation, which was
international in nature, made it necessary to restrict information
flowing to the public, to avoid damaging the effectiveness of the
investigation. That restriction has been unfortunate, and is not in
the ordinary spirit of openness and transparency with which we strive
to define the Fedora Project.
We appreciate the patience and support the Fedora community has given
us over the past several months. We also wish to express our thanks
for the technical assistance of the security response team at Red Hat.
This report concludes the matter from the Fedora Project's
perspective, and provides a final accounting of the intrusion event
and response by the Fedora infrastructure and management teams.
Following is a detailed time line, in UTC, of activities by Fedora
contributors.
= = = = =
2008-08-12 01:00:00 - Last packaging signing process from a Fedora
admin. Key would have been on host temporarily up until this time.
2008-08-12 07:49:05 - Standard Fedora 'pkgconfig' package installed by
the intruder. This package is required to build an 'openssh' package.
Intruder proceeds to build a modified 'openssh' package.
2008-08-12 08:10:46 - modified 'openssh' package installed by intruder.
2008-08-12 17:46:50 - Standard Fedora 'gettext' package installed by
intruder. This package is required to build an 'rpm' package.
2008-08-12 20:18:36 - Standard Fedora 'mc' package installed by
intruder, possibly for convenience of stealth.
2008-08-12 21:33:59 - Bacula backup started (scheduled job)
2008-08-12 22:01:54 - Bacula backup Ended
2008-08-12 22:31:51 - modified 'rpm' package installed (along with
standard Fedora package dependencies for 'rpm').
2008-08-12 22:51:00 - Cron job failed, notified admins.
2008-08-12 22:53:00 - Fedora Infrastructure admins first noticed and
started poking around at why RPM had changed.
2008-08-12 23:11:00 - Infrastructure team lead is notified and more
prodding begins.
2008-08-12 23:38:00 - Infrastructure team members gather for
discussions on dedicated, private IRC channel and conference call.
2008-08-13 01:50:00 - It becomes more clear that a script is not at
fault. LVM snapshot taken.
2008-08-13 04:00:14 - Bacula backup (during the intrusion) restored to
secure location
2008-08-13 04:04:14 - Discovery of an RPM in /root/.ssh/ provides
proof of malicious intent.
2008-08-13 04:05:00 - Red Hat security team notified.
2008-08-13 04:46:00 - Compromised host prohibited from routing out or
in. All machines on its network are preventing access from it.
Outbound connections logged.
2008-08-13 05:16:00 - Fedora Project Leader notified.
2008-08-13 06:13:00 - Host state saved (Xen guest). We have a running
copy of the host as it was without a reboot.
2008-08-13 06:14:00 - Users who have accessed the machine during the
intrusion advised to change their passwords and SSH keys.
2008-08-13 10:13:00 - Work continues in concert with Red Hat security
team members. Preliminary announcement prepared
2008-08-14 17:36:00 - All passwords and SSH keys disabled.
2008-08-14 23:15:13 - Preliminary announcement to
fedora-announce-list, 1+19:11 after initial determination of malicious
event.
2008-08-15 02:47:00 - All administrator access forced to shell access
only for partial re-enabling of account system.
2008-08-15 12:00:00 - (approximate) Fedora's package build system,
koji, patched to revoke all access.
2008-08-15 13:11:00 - Last package build routine allowed to complete
before shutdown. Comprehensive verification of the build system
database contents begins, comparing against known source for malicious
content.
2008-08-16 15:30:03 - Update announcement to fedora-announce-list,
3+11:26 after initial determination of malicious event.
2008-08-17 22:34:00 - Members of sysadmin-web group allowed back on app servers.
2008-08-18 04:06:31 - Primary content verification of build system and
CVS completed.
2008-08-18 18:06:00 - CVS admins allowed back on servers, and handle
additional verification for hosted projects.
2008-08-19 02:07:45 - Update announcement to fedora-announce-list,
5+22:03 after initial determination of malicious event.
2008-08-19 02:37:00 - Hosted project verification completed, and
Fedora Hosted back online.
2008-08-19 20:19:00 - Anonymous access via cvspserver allowed.
2008-08-20 02:53:00 - Writable access to cvs1 reactivated.
2008-08-20 18:35:00 - Koji build system officially open and building again.
2008-08-22 12:00:02 - Update announcement to fedora-announce-list,
9+07:56 after initial determination of malicious event.
2008-09-19 02:41:29 - Update announcement to fedora-announce-list,
37+22:37 after initial determination of malicious event.
Investigation and issue resolution continues.
2009-03-30 14:00:00 - Final report to fedora-announce-list, 229+9:56
after initial determination of malicious event.
= = = = =
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
--
fedora-announce-list mailing list
fedora-announce-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-announce-list
--
Regards,
Susmit.
=============================================
ssh
0x86DD170A
http://www.fedoraproject.org/wiki/user:susmit
=============================================
15 years
Fwd: fedora-i18n bug day 2 April
by sankarshan
---------- Forwarded message ----------
From: Jens Petersen <petersen(a)redhat.com>
Date: Mon, Mar 30, 2009 at 7:02 PM
Subject: fedora-i18n bug day 2 April
To: fedora-i18n-list(a)redhat.com
Cc: fedora-devel-list <fedora-devel-list(a)redhat.com>, fedora-test-list
<fedora-test-list(a)redhat.com>
The Fedora I18n Project is planning a bug day this Thursday (2nd April).
http://fedoraproject.org/wiki/I18N/Bugs has links to various lists of
i18n related bugs.
The main focus will be triaging rawhide bugs related to i18n but also
checking on older i18n bugs to see if they are still present in F10
and/or F11 Beta.
Join us on #fedora-i18n during the day to help out, ask questions, and
for discussion i18n issues.
Fedora I18n Team
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
--
http://www.gutenberg.net - Fine literature digitally re-published
http://www.plos.org - Public Library of Science
http://www.creativecommons.org - Flexible copyright for creative work
Sent from: Calcutta WB India.
15 years
How to install ".img" file without web access whilte installing a laserjet printer in Fedora 9
by saikat saha
Dear Concern,
This is saikat from R.P Infosystems Pvt.Ltd (Chirag, kolkata). We have a
problem regarding printer installation on Fedora 10 OS & 9 as well.
The model of the printer is *HP Laserjet P1007.*
We have solved the probelm using the 3rd party driver.There are a
command *"./getweb
P1007"* in the installation process. it requires the internet connection to
get the *".img"* file from the web.
But we need to install the ".img" file without web access. Please tell me
the command for the manual installation of the *".img"* file.
Please find the screen-shot attachment to understand the problem better.
Waiting for your early reply.
Thanks & Regards
Saikat Saha
Mobile-9836728444
15 years
F10 DVDs/Stickers
by Pradeepto Bhattacharya
Hi,
Recently, I got a nice spindle of F10 DVDs and some stickers from a
nice gentleman in Pune ;) . At that point I was very hopeful of going
to a nice foss meet in Panipat, that unfortunately never happened. So
now I have all this stuff and I would love to give them away before
they are too old.
Now, is it ok if I announce it on my local lug ( lug-bom ) about the
stuff that I have and that people can take it from me if they are
willing to come to my place or I go to BOM for some random reason and
thusly pass it on to them. ( Personally, I won't be able to afford the
courier costs ). Or do I wait for an event? Thank you for listening.
Cheers!
Pradeepto
--
The KDE Project : http://www.kde.org
KDE India : http://www.kde.in
Mailing List : http://mail.kde.org/mailman/listinfo/kde-india
15 years, 1 month
about fedora installation dvd
by Amirtham purendra raman bala
Hi friendsi amhappy to say that i am getting more than 10 request for the F10 installation DVD per month in tamilnadu, Dear fedoraindia ! Get Yourself a cool, short @in.com Email ID now!
15 years, 1 month
FAmSCo regional meetings one for each zone.
by susmit shannigrahi
Hi,
During FAmSCo meeting [1] we planned a series of FAmSCo
regional meetings to have in-depth discussion with the most active
ambassadors in each region.
Basically, we plan to concentrate on one region one day and discuss
things with mentors and active contributors.
This will give you and us the possibility to understand what it could
be done to improve ambassadors experience.
This is the proposed schedule for such meetings (dd/MM/yy):
02/04/2009 - NA
16/04/2009 - EMEA
30/04/2009 - India/APJ
07/05/2009 - LATAM
Please add the topics you want to discuss (about your region) directly
to this thread.
Thanks.
--
Regards,
Susmit.
=============================================
ssh
0x86DD170A
http://www.fedoraproject.org/wiki/user:susmit
=============================================
Sent from: Calcutta WB India.
15 years, 1 month
Re: Printer installation problem in fedora 10 & 9
by susmit shannigrahi
On Fri, Mar 27, 2009 at 7:15 PM, Saikat Saha <saikats(a)rpchirag.com> wrote:
> Dear Mr. Susmit,
>
> Thanks for your support!
Welcome...
> The Printer is working well in Fedora 9 & Fedora 10.
That's a good news.
> But there is a problem
> regarding the internet connection. There are no internet connections in the
> place where our system will be installed. So we have downloaded the ".img"
> file.
> Please tell me the command for the installation of the file. Please find the
> screenshot attachment for your reference.
For further questions please subscribe to fedora-india [1] mailing
list and ask your questions there. Thus many people from the community
will be able to help you and you won't be dependent on solely on me
for further problems.
Thanks.
[1] https://www.redhat.com/mailman/listinfo/fedora-india
--
Regards,
Susmit.
=============================================
ssh
0x86DD170A
http://www.fedoraproject.org/wiki/user:susmit
=============================================
Sent from: Calcutta WB India.
15 years, 1 month