Jorge Castro: Unity Bitesize Bug Status for 19 January

Tags

security

Special Forums Cybersecurity Security Advisories (RSS) Jorge Castro: Unity Bitesize Bug Status for 19 January

01-20-2011

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

Jorge Castro: Unity Bitesize Bug Status for 19 January

I'm a day late due to being sick yesterday, now things are back on track.*

The team is now back from Dallas, Texas, and as OMG!Ubuntu! points out, much has landed after the sprint, a culmination of a week's work of hacking. Neil talks about Unity in this interview. Nice work Joey and Benjamin for covering Unity updates whilst the team flew back home.*

read more

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

removing application from the unity menu

Hello I have removed wine but the symbols of it application were in the unity menu (though nothing happened when I clicked on them). How can I remove symbols from the unity menu?

2. UNIX for Advanced & Expert Users

To run the script only if the date is not between 5 th and 10th of january ?

Hi I am new to unix. I have to set up a cron for the program , which should run every Monday at 3 a.m, however , if the date is between the 5 th and the 15th of January,APril or December, the program should not run I know i cant do this in cron , Help with writing the if contion is...

LEARN ABOUT DEBIAN

fwohci

FWOHCI(4)						   BSD Kernel Interfaces Manual 						 FWOHCI(4)

NAME

     fwohci -- OHCI FireWire chipset device driver

SYNOPSIS

     To compile this driver into the kernel, place the following line in your kernel configuration file:

	   device firewire

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

	   firewire_load="YES"

     To disable physical access (see BUGS section for detail), put the following line in loader.conf(5):

	   hw.firewire.phydma_enable=0

HARDWARE

     The fwohci driver provides support for PCI/CardBus FireWire interface cards.  The driver supports the following IEEE 1394 OHCI chipsets:

     o	 Adaptec AHA-894x/AIC-5800
     o	 Apple Pangea
     o	 Apple UniNorth
     o	 Intel 82372FB
     o	 IOGEAR GUF320
     o	 Lucent / Agere FW322/323
     o	 NEC uPD72861
     o	 NEC uPD72870
     o	 NEC uPD72871/2
     o	 NEC uPD72873
     o	 NEC uPD72874
     o	 National Semiconductor CS4210
     o	 Ricoh R5C551
     o	 Ricoh R5C552
     o	 Sony CX3022
     o	 Sony i.LINK (CXD3222)
     o	 Sun PCIO-2 (RIO 1394)
     o	 Texas Instruments PCI4410A
     o	 Texas Instruments PCI4450
     o	 Texas Instruments PCI4451
     o	 Texas Instruments TSB12LV22
     o	 Texas Instruments TSB12LV23
     o	 Texas Instruments TSB12LV26
     o	 Texas Instruments TSB43AA22
     o	 Texas Instruments TSB43AB21/A/AI/A-EP
     o	 Texas Instruments TSB43AB22/A
     o	 Texas Instruments TSB43AB23
     o	 Texas Instruments TSB82AA2
     o	 VIA Fire II (VT6306)

SEE ALSO

     firewire(4), fwe(4), fwip(4), sbp(4), fwcontrol(8), kldload(8)

HISTORY

     The fwohci device driver first appeared in FreeBSD 5.0.

AUTHORS

     The fwohci device driver was written by Katsushi Kobayashi and Hidetoshi Shimokawa.

BUGS

     The driver allows physical access from any nodes on the bus by default.  This means that any devices on the bus can read and modify any mem-
     ory space which can be accessed by an IEEE 1394 OHCI chip.  It is allowed mostly for sbp(4) devices.  This should be changed to allow it only
     for specific devices.  Anyway, FireWire is a bus and not expected to be connected with un-trustable devices because a node can monitor all
     the traffic.

BSD
								   March 3, 2008							       BSD

Security Advisories (RSS)