[mostly OT] why is a netgear wgu624 router so much slower than a soekris net4801
hi, I have a quick question, maybe I just haven't thought this all the way through and the answer is obvious... well, the subject line doesn't give justice to my full question, here is the scenario. When I've plugged in an openbsd machine (by wire) to the netgear wgu624 router connected to my cable modem, and do a cvs checkout with my closest mirror (running over ssh), I get very very dismal results. The files come in dog slow, only like a couple files per minute. So slow, that I get reset by peer after a few hours. Meanwhile, all other http downloading etc., works super fast. When I've plugged in the same openbsd machine (by wire) to the soekris net4801 (obviously running openbsd) connect to the same cable modem (ie, swap out the netgear), and do a cvs checkout to the same mirror (running over ssh, everything completely the same), I can download the whole source tree in a couple of minutes, so fast I can't read the filenames. Of course I'm always going to use the soekris, but for a short time I was required to remove my soekris and put the netgear there temporarily. These performance results confused me. Maybe I need to post more information (and let me know if I do). I'm confused. If the NAT was really that much slower on the netgear, I'd see it with the http traffic too, right? This is really only noticeable with ssh traffic. sorry if this is a stupid question thanks b Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
Re: problems using usb keyboard on sunblade 100
Glad that somebody else broached this topic, I was about to ask the same question. I can't get ANY USB keyboard to work with OpenBSD on my desktop computer (a very standard Athlon 32). When I say it "doesn't work", I mean it's completely dead, as if the keyboard wasn't even attached to the machine. That's true if I boot directly from the OpenBSD CD, or boot from the hard drive. Although the OS cannot see a USB keyboard, I tested it with a (borrowed) PS/2 keyboard and there's no problem there. Before someone says "well just buy a PS/2 keyboard" - OK, I can do that, but I've got some concern that further down the road I may have a machine with lacks a PS/2 connector, since USB-only is becoming common (especially on laptops). Interestingly, it's not just OpenBSD that has this issue - USB the keyboard suffers total non-response with FreeBSD and NetBSD too. But the same keyboard works fine with Linux on the same machine. I did quite a bit of Googling for answers and found numerous suggestions (mostly for FreeBSD) all of which I tried, but none worked. best regards, Robert On Saturday 27 August 2005 09:02 pm, you wrote: > Hi, > > I want to use a sunblade 100 with openbsd as my primary desktop. > Unfortunately I'm not able to get the keyboard to work (sun usb type 6 > swedish layout). > After installing the miniroot.fs to the harddisk and resetting the > machine it > booted to the prompt where one can choose between shell, upgrade and > install. > I wasn't able to type anything here. I then installed over a serial line > and it worked fine. > After rebooting with the keyboard attached it booted to the login prompt > but still > I was not able to type anyhting here. Login over the network just works > fine. > I also can find the keyboard within the dmesg output. The eeprom command > shows keyboard > as input-device. The same behaviour can be seen with the 3.7 release and > the latest snapshot. > My OpenBoot version is 4.17.1. I'm new to openbsd maybe I'm missing > something obvious here. > > Thanks in advance, > > mark
Re: raid kernel
> Just curious, what does the dev team think about Vinum? I want a raid model that acts as if it is a regular scsi drive, ie. sdN. Like our hardware raid controllers work. Right now what we have in the tree is poo, and vinum is just as much poo too. I do not envision enabling this stuff in RAMDISKs anytime soon, so please stop asking.
Re: raid kernel
* Nick Holland <[EMAIL PROTECTED]> [050825 07:22]: > Edd Barrett wrote: > >> rather then trying more stupid band-aids and wuergarounds it would be > >> fantastic if someone could sit down and get us a software raid > >> implementation that doesn't suck and thus can be included in the regular > >> kernels. > > > > I havent noticed anything terribly wrong with raidframe. Why do you > > think it sucks? > > > > The only drawback with raidframe i see is that mirrors can only be 2 disks. > > * huge > * complex > * you can't add mirroring after initial install if you weren't planning > for it at the beginning. > * its recovery from "events" is not graceful (i.e., long boot times). > > That's just a starter... > > (can't believe I forgot the bsd.mp case...) > > Nick. > Just curious, what does the dev team think about Vinum? Jim
Re: Disable/Passprotect single user mode
I have always been under the assumption to lock up a critical piece of hardware where no one can get to it accept the person with the key or possbily a crowbar. rogern John 3:16 From: Christian Jones <[EMAIL PROTECTED]> To: black reaper <[EMAIL PROTECTED]> CC: misc@openbsd.org Subject: Re: Disable/Passprotect single user mode Date: Sat, 27 Aug 2005 15:50:52 -0700 On 8/27/05, black reaper <[EMAIL PROTECTED]> wrote: > Also, a BIOS password can be easily removed if one has physical access to > the box. The small CMOS battery can be popped out, and put back in (on the > motherboard), erasing your password. > Not always, actually. I have a Dell laptop that's rumored to store the password in some kind of ROM. Whatever the technical aspects, removing the battery (actually, cutting the leads to it) didn't remove the password. Note that I'm not actually suggesting this as an effective security mechanism, since most of these laptops also have a "Master" password, but this one didn't---or at least none of the ones I tried with the help of a Dell support person worked. Still, just important to realize that it may or may not be as easy as popping a battery out and in. -- Christian Jones [EMAIL PROTECTED] http://www.aleph0.com/~chjones http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Re: Netgear WG511T on CURRENT: Supported or not?
Hello Christian, I have successfully used the Compaq WL110 card on Panasonic Toughbooks, CF-25 and CF-71. OpenBSD 3.7 & 3.8-beta detected it correctly during boot process, setup as hostname.if with dhcp and nwkey Compaq WL410 wireless AP with WEP and Netgear not able to setup WEP. I just got two more WL110's from Ebay for $20.00 and $36.00. Online resellers around $83.00. These are 802.11b. Hope this helps you, rogern John 3:16 From: Christian Jones <[EMAIL PROTECTED]> To: misc@openbsd.org Subject: Netgear WG511T on CURRENT: Supported or not? Date: Sat, 27 Aug 2005 15:43:44 -0700 snip< PS---I'd also love any suggestions for supported PCMCIA/Cardbus or PCI 802.11b or g cards "officially" supported and known to work, as well as still available new in stores in the US. Feel free to use private mail for this---no need to clutter the list. snip< http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Re: Disable/Passprotect single user mode
Christian Jones wrote: On 8/27/05, black reaper <[EMAIL PROTECTED]> wrote: Also, a BIOS password can be easily removed if one has physical access to the box. The small CMOS battery can be popped out, and put back in (on the motherboard), erasing your password. Not always, actually. I have a Dell laptop that's rumored to store the password in some kind of ROM. Whatever the technical aspects, removing the battery (actually, cutting the leads to it) didn't remove the password. Note that I'm not actually suggesting this as an effective security mechanism, since most of these laptops also have a "Master" password, but this one didn't---or at least none of the ones I tried with the help of a Dell support person worked. Still,. just important to realize that it may or may not be as easy as popping a battery out and in. Its hard to be a "hard target" With Windoze on this HP zd8000 monster, I have no less than 3 passwords that I have to give before I can do anything. Then all of my essays on me, life, family (disfunctionsl) are all encrypted. I wrote Linus (who works about 3 miles from where I live) and told him to tell Gates to fix the miserable XP-Pro encyption. I made the mistake of encrypting my entire "My Documents" folder. That cpu now is OpenBSD only, haha. When I did the encryption it brought the laptop to a standstill. On the same subject, does anyone really know what XP-encryption actually means? My god, I would pick Blowfish if I had a choice. Rob.
Re: SETTLED - Re: proper way to format/use floppies (i386)
Hello, I haven't had any problems with fdformat and easy to use. Best regards, rogern John 3:16 From: Michael Adam <[EMAIL PROTECTED]> To: misc@openbsd.org Subject: Re: SETTLED - Re: proper way to format/use floppies (i386) Date: Sun, 28 Aug 2005 01:57:58 +0200 Hi Richard, Richard P. Koett <[EMAIL PROTECTED]> wrote: > > I'm coming in rather late on this discussion - just curious about the > formatting step? Presumably you would do something like: > > $ fdformat fd0 Yes exactly, but the low level formatting was not the question. But thanks for answering anyway! > I've had so many f*cking problems with floppy disks over the years I > wouldn't trust using one without a successful format first. Well, I can sing you a song of broken filesystems on floppies, too. Perhaps I should also make it a habit to always fdformat first... Cheers, Michael http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Re: SETTLED - Re: proper way to format/use floppies (i386)
Hi Richard, Richard P. Koett <[EMAIL PROTECTED]> wrote: > > I'm coming in rather late on this discussion - just curious about the > formatting step? Presumably you would do something like: > > $ fdformat fd0 Yes exactly, but the low level formatting was not the question. But thanks for answering anyway! > I've had so many f*cking problems with floppy disks over the years I > wouldn't trust using one without a successful format first. Well, I can sing you a song of broken filesystems on floppies, too. Perhaps I should also make it a habit to always fdformat first... Cheers, Michael
Re: Disable/Passprotect single user mode
On Saturday 27 August 2005 17:50, Christian Jones wrote: > On 8/27/05, black reaper <[EMAIL PROTECTED]> wrote: > > Also, a BIOS password can be easily removed if one has physical access to > > the box. The small CMOS battery can be popped out, and put back in (on the > > motherboard), erasing your password. > > > Not always, actually. I have a Dell laptop that's rumored to store > the password in some kind of ROM. Whatever the technical aspects, > removing the battery (actually, cutting the leads to it) didn't remove > the password. The password you were unable to remove may well be a disk-drive password. I have an 8-year-old Dell laptop which provides in the bios the capability of setting a disk-drive password in addition to 2 bios passwords(boot and master). The question is 'WHICH disk password was set?' If it was the master disk password, you aren't going to get your data back - period. If it was the user disk password, you may be able to clear it via the master disk password. Good Luck! > Note that I'm not actually suggesting this as an effective security > mechanism, since most of these laptops also have a "Master" password, > but this one didn't---or at least none of the ones I tried with the > help of a Dell support person worked. Still, just important to > realize that it may or may not be as easy as popping a battery out and > in. > > -- > Christian Jones > [EMAIL PROTECTED] > http://www.aleph0.com/~chjones > > -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
Re: Netgear WG511T on CURRENT: Supported or not?
On 8/27/05, Theo de Raadt <[EMAIL PROTECTED]> wrote: > The problem you are really having is a financial one. Someone has > your money, and has given you a device that has a new chip in it. > Return it. This problem has nothing to do with the limited abilities > that OpenBSD has to track vendors who change their chips revisions > whenever they feel like it. In fact, sometimes I wonder why we have > an Atheros driver at all, considering that Atheros has not gotten any > less evil. Still no docs. And still that push for binary drivers. > Understood. Thanks, Theo, and thanks (as always) for the wonderful work! CDJ -- Christian Jones [EMAIL PROTECTED] http://www.aleph0.com/~chjones
Re: Netgear WG511T on CURRENT: Supported or not?
> I can return the card easily enough, but there has been some > discussion previously of removing non-working cards from the ath(4) > man page. Has anyone gotten this card to work properly? Should it > also be removed from http://www.openbsd.org/i386.html ? No, no, no. Newer versions of chipsets come out. Vendors use the chipsets without changing the product name. We can do nothing about this. In the end, with the direction you are going, our manual pages would say: Some devices work with this driver. Right now the situation is more correct. The problem you are really having is a financial one. Someone has your money, and has given you a device that has a new chip in it. Return it. This problem has nothing to do with the limited abilities that OpenBSD has to track vendors who change their chips revisions whenever they feel like it. In fact, sometimes I wonder why we have an Atheros driver at all, considering that Atheros has not gotten any less evil. Still no docs. And still that push for binary drivers.
Netgear WG511T on CURRENT: Supported or not?
Hi, again, all. I've just picked up a Netgear WG511T, which is
detected by OpenBSD (I believe correctly) as a Atheros AR5212 Cardbus
card. There have been several discussions mentioning this and other
Atheros cards on this list in the last few months, but none seem to
come to any resolution. Somewhat unsurprisingly (if you're still
reading), I haven't gotten this to work, either, on a laptop that at
least at first glance has proper cardbus support. With the 24 August
snapshot, the card's apparently detected, lights blink, but I get the
dreaded "status: no network", and am unable to advance from there.
(See below for full dmesg, hostname.ath0, and output or lack thereof.)
I can return the card easily enough, but there has been some
discussion previously of removing non-working cards from the ath(4)
man page. Has anyone gotten this card to work properly? Should it
also be removed from http://www.openbsd.org/i386.html ?
I welcome any requests for more information or suggestions for better
troubleshooting. Thanks, as always!
CDJ
PS---I'd also love any suggestions for supported PCMCIA/Cardbus or PCI
802.11b or g cards "officially" supported and known to work, as well
as still available new in stores in the US. Feel free to use private
mail for this---no need to clutter the list.
Script started on Sat Aug 27 15:17:23 2005
# dmesg
OpenBSD 3.8-beta (GENERIC) #119: Wed Aug 24 01:47:37 MDT 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Mobile Intel(R) Celeron(R) CPU 2.20GHz ("GenuineIntel" 686-class) 2.20 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID
real mem = 232300544 (226856K)
avail mem = 205090816 (200284K)
using 2861 buffers containing 11718656 bytes (11444K) of memory
User Kernel Config
UKC> disable apm0
265 apm0 disabled
UKC> quit
Continuing...
mainbus0 (root)
bios0 at mainbus0: AT/286+(e5) BIOS, date 03/04/05, BIOS32 rev. 0 @ 0xfd830
apm at bios0 function 0x15 not configured
pcibios0 at bios0: rev 2.1 @ 0xfd830/0x7d0
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf40/160 (8 entries)
pcibios0: PCI Interrupt Router at 000:02:0 ("SIS 85C503 System" rev 0x00)
pcibios0: PCI bus #2 is the last bus
bios0: ROM list: 0xc/0xc000 0xcc000/0xa000 0xd6000/0x800!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "SIS 650 PCI" rev 0x80
ppb0 at pci0 dev 1 function 0 "SIS 86C201 AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "SIS 650 VGA" rev 0x00: aperture at
0xe800, size 0x40
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 2 function 0 "SIS 85C503 System" rev 0x25
pciide0 at pci0 dev 2 function 5 "SIS 5513 EIDE" rev 0x00: 650: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA48, 28615MB, 58605120 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: SCSI0
5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
"SIS 7013 Modem" rev 0xa0 at pci0 dev 2 function 6 not configured
auich0 at pci0 dev 2 function 7 "SIS 7012 AC97" rev 0xa0: irq 5, SiS7012 AC97
ac97: codec id 0x41445374 (Analog Devices AD1981B)
ac97: codec features headphone, 20 bit DAC, No 3D Stereo
audio0 at auich0
ohci0 at pci0 dev 3 function 0 "SIS 5597/5598 USB" rev 0x0f: irq 9,
version 1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: SIS OHCI root hub, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1 at pci0 dev 3 function 1 "SIS 5597/5598 USB" rev 0x0f: irq 10,
version 1.0, legacy support
usb1 at ohci1: USB revision 1.0
uhub1 at usb1
uhub1: SIS OHCI root hub, rev 1.00/1.00, addr 1
uhub1: 3 ports with 3 removable, self powered
ehci0 at pci0 dev 3 function 2 "SIS 7002 USB" rev 0x00: irq 3
usb2 at ehci0: USB revision 2.0
uhub2 at usb2
uhub2: SIS EHCI root hub, rev 2.00/1.00, addr 1
uhub2: 6 ports with 6 removable, self powered
sis0 at pci0 dev 4 function 0 "SIS 900 10/100BaseTX" rev 0x91: irq 4,
address 00:11:43:44:86:42
rlphy0 at sis0 phy 1: RTL8201L 10/100 PHY, rev. 1
cbb0 at pci0 dev 10 function 0 "Texas Instruments PCI1510 CardBus" rev
0x00: irq 9
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pckbcintr: no dev for slot 1
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
spkr0 at pcppi0
sysbeep0 at pcppi0
npx0 at isa0 port 0xf0/16: using exception 16
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 2 device 0 cacheline 0x8, lattimer 0x20
pcmcia0 at cardslot0
biomask efcd netmask efdd ttymask ffdf
pctr:
Re: Disable/Passprotect single user mode
On 8/27/05, black reaper <[EMAIL PROTECTED]> wrote: > Also, a BIOS password can be easily removed if one has physical access to > the box. The small CMOS battery can be popped out, and put back in (on the > motherboard), erasing your password. > Not always, actually. I have a Dell laptop that's rumored to store the password in some kind of ROM. Whatever the technical aspects, removing the battery (actually, cutting the leads to it) didn't remove the password. Note that I'm not actually suggesting this as an effective security mechanism, since most of these laptops also have a "Master" password, but this one didn't---or at least none of the ones I tried with the help of a Dell support person worked. Still, just important to realize that it may or may not be as easy as popping a battery out and in. -- Christian Jones [EMAIL PROTECTED] http://www.aleph0.com/~chjones
Re: Disable/Passprotect single user mode
On 8/27/05, Todd C. Miller <[EMAIL PROTECTED]> wrote: > > In message <[EMAIL PROTECTED]> > so spake JSD (sri): > > > I have a big root access problem. If someone has physical > > access to my OpenBSD box, than he/she can swith into single > > user mode (-s) and can change the password of root. It is a > > big problem for me and I would like to password protect this > > single user mode or to totally disable this function but I > > don't know how. > > Is anyone here who solved this problem? Please help, thanks! > > Just remove the "secure" qualifier from the console line in > /etc/ttys. E.g. > > Instead of: > console "/usr/libexec/getty Pc" vt220 off secure > > Use: > console "/usr/libexec/getty Pc" vt220 off > > - todd > > Also, a BIOS password can be easily removed if one has physical access to the box. The small CMOS battery can be popped out, and put back in (on the motherboard), erasing your password. -b14ck
Re: Disable/Passprotect single user mode
In message <[EMAIL PROTECTED]> so spake JSD (sri): > I have a big root access problem. If someone has physical > access to my OpenBSD box, than he/she can swith into single > user mode (-s) and can change the password of root. It is a > big problem for me and I would like to password protect this > single user mode or to totally disable this function but I > don't know how. > Is anyone here who solved this problem? Please help, thanks! Just remove the "secure" qualifier from the console line in /etc/ttys. E.g. Instead of: console "/usr/libexec/getty Pc" vt220 off secure Use: console "/usr/libexec/getty Pc" vt220 off - todd
Re: ThinkPad testers required
I have a thinkpad x22.. not sure if I can help, but if i can slap a snapshot on the lappy, would it be of any help? On 8/27/05, Jonathan Gray <[EMAIL PROTECTED]> wrote: > Can people with the following laptops: > > - ThinkPad R50, R50p, R51, R52 > - ThinkPad T41, T41p, T42, T42p, T43, T43p > - ThinkPad X40 > - ThinkPad X41, X41 Tablet > > Try running the latest snapshot (08/27/05 06:49:00) > > Check they have working aps via > sysctl hw.sensors > Numbers should change when tilting the laptop. > > Suspend the system ie > zzz > > Resume and check they still have normal looking > numbers when running the same sysctl command again? > > We need this to be tested on as wide a range > of models as possible ASAP. > > Send all reports positive and negative alike > to djm@ and me.
Re: Welcome to our Newsletter
On Fri, 26 Aug 2005 08:53:19 -0500 (CDT), "L. V. Lammert" <[EMAIL PROTECTED]> wrote: >> What is this? >> >> Is someone trying to spam the list? >> >Probably, .. looks like somebody else has already unsubscribed. > > Lee Actually, it could also be a trolling attack called "cross linking" where the goal is to fill one list/group with erroneous posts from someplace else. Though this case uses other email lists to accomplish the same goals, it's still similar to posting a big flaming troll to one group (like posting recipes to alt.rec.cats) while setting the "follow-up" header to someplace else, so all replies pollute another group. All the idiots that reply, flood the second group. JCR
ALi M5451 recognized but doesn't play sounds
I'm using OpenBSD 3.7 on a Compaq Presario 900 laptop and the sound device
(ALi M5451) is recognized and configured using the autri(4) driver, but I
don't get any output from the speakers when I do something like:
$ cat /bsd > /dev/audio
or when I try to play an audio CD.
I checked all of the mixerctl settings and played with various combinations,
none of which worked. Here is the output of mixerctl -a:
$ mixerctl -a
outputs.master=255,255
outputs.master.mute=off
outputs.mono=255
outputs.mono.mute=off
outputs.mono.source=mixerout
outputs.headphones=255,255
outputs.headphones.mute=off
outputs.bass=15
outputs.treble=15
inputs.speaker=255
inputs.speaker.mute=off
inputs.phone=191
inputs.phone.mute=on
inputs.mic=191
inputs.mic.mute=on
inputs.mic.preamp=off
inputs.mic.source=mic0
inputs.line=191,191
inputs.line.mute=on
inputs.cd=191,191
inputs.cd.mute=off
inputs.video=191,191
inputs.video.mute=on
inputs.aux=191,191
inputs.aux.mute=on
inputs.dac=191,191
inputs.dac.mute=off
record.source=mic
record.volume=255,255
record.volume.mute=off
record.mic=0
record.mic.mute=on
outputs.loudness=on
outputs.spatial=off
outputs.spatial.center=0
outputs.spatial.depth=0
outputs.surround=255,255
outputs.surround.mute=off
outputs.center=255
outputs.center.mute=off
outputs.lfe=255
outputs.lfe.mute=off
I pressed the "increase volume" button on the laptop but I still could not
hear anything.
I know that the sound device is not defective because it works on GNU/Linux.
And there seem to be no irq conflicts with the device either. Here is the
full dmesg:
$ /sbin/dmesg
OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Mobile AMD Athlon(tm) XP 1500+ ("AuthenticAMD" 686-class) 1.33 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,S
SE
real mem = 368611328 (359972K)
avail mem = 329007104 (321296K)
using 4278 buffers containing 18534400 bytes (18100K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(7c) BIOS, date 07/21/03, BIOS32 rev. 0 @ 0xfd760
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev 2.1 @ 0xfd760/0x8a0
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf10/208 (11 entries)
pcibios0: PCI Interrupt Router at 000:07:0 ("Acer Labs M1533 ISA" rev 0x00)
pcibios0: PCI bus #2 is the last bus
bios0: ROM list: 0xc/0xf000 0xdf000/0x1000! 0xe/0x4000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "ATI RS100 AGP" rev 0x13
ppb0 at pci0 dev 1 function 0 "ATI RS100 PCI" rev 0x01
pci1 at ppb0 bus 1
vga1 at pci1 dev 5 function 0 "ATI Radeon IGP 320M" rev 0x00
wsdisplay0 at vga1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
ohci0 at pci0 dev 2 function 0 "Acer Labs M5237 USB" rev 0x03: irq 11,
version 1.0, legacy support
ohci0: SMM does not respond, resetting
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: Acer Labs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
pcib0 at pci0 dev 7 function 0 "Acer Labs M1533 ISA" rev 0x00
autri0 at pci0 dev 8 function 0 "Acer Labs M5451 Audio" rev 0x02: irq 5
ac97: codec id 0x41445363 (Analog Devices AD1886A)
ac97: codec features headphone, Analog Devices Phat Stereo
audio0 at autri0
midi0 at autri0: <4DWAVE MIDI UART>
cbb0 at pci0 dev 10 function 0 "Texas Instruments PCI1410 CardBus" rev
0x02pci_intr_map: no mapping for pin A
: couldn't map interrupt
rl0 at pci0 dev 11 function 0 "Realtek 8139" rev 0x20: irq 11 address
00:08:02:f3:b9:33
rlphy0 at rl0 phy 0: RTL internal phy
"Conexant HSF 56k HSFi" rev 0x01 at pci0 dev 12 function 0 not configured
ohci1 at pci0 dev 15 function 0 "Acer Labs M5237 USB" rev 0x03: irq 11,
version 1.0, legacy support
usb1 at ohci1: USB revision 1.0
uhub1 at usb1
uhub1: Acer Labs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 4 ports with 4 removable, self powered
pciide0 at pci0 dev 16 function 0 "Acer Labs M5229 UDMA IDE" rev 0xc4: DMA,
channel 0 configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 19077MB, 39070080 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: SCSI0 5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
"Acer Labs M7101 Power Mgmt" rev 0x00 at pci0 dev 17 function 0 not
configured
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0 (mux 1 ignored for console): console keyboard, using
wsdisplay0
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pmsi0 mux 0
pcppi0 at isa0 port 0x61
midi1 at pcppi0:
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
ahc_isa_idstring: BIOS biffed it at 0x9c00
biom
frequency of ports-security mailing list updates?
I've been subscribed to the ports-security mailing lists since mid June 2005. Today I received a notice for a security update for pcre-4.5p0. Out of habit I double checked against the 3.7 packages errata page and noticed that there were a number of other updates applicable to my system(tiff-3.6.1p6, netpbm-9.24p2) that I had not received a notice for via ports-security. It looks like these updates were uploaded to ftp.openbsd.org on 8/19 so it seems I should have received a mail alert by now if in fact one was issued and barring any delivery problems to my mailbox. As a matter of clarification, will an email alert be sent via the ports-security mailing lists for all package errata? If not, what is the recommended method being alerted to relevant changes? Do I need to subscribe to ports-changes?
Re: Disable/Passprotect single user mode
On Saturday 27 August 2005 12:28, Tobias Weingartner wrote: > You BIOS password would prevent the machine from booting > automatically after power outtage for example... What! You're not running with backup power??? :-) -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
Re: Disable/Passprotect single user mode
On Saturday, August 27, Dave Feustel wrote: > On Saturday 27 August 2005 06:07, JSD wrote: > > > > I have a big root access problem. If someone has physical > > access to my OpenBSD box, than he/she can swith into single > > user mode (-s) and can change the password of root. It is a > > big problem for me and I would like to password protect this > > single user mode or to totally disable this function but I > > don't know how. > > In your bios, you should be able to set a boot password which will prevent > booting until the password is given. Oh god, please just read the ttys(5) manual, and mark the console as not being secure. PC's in general are shitty pieces of hardware that are easy to circumvent. You BIOS password would prevent the machine from booting automatically after power outtage for example... --Toby.
Re: Disable/Passprotect single user mode
On Saturday 27 August 2005 11:14, kami petersen wrote: > dave, what are you smoking? please carefully note how i edited out > _your_ text so as to indicate _who_ i was addressing and whom i > additionally consider being a smartass. let me rephrase: > > dear frank. > > your response is unneccesary and non constructive. provided that the box > in question cannot be physically secured there is little you can > practically do other than applying the above methods put forward by dave > and matt in order to prevent single user root access. > > /kami Sorry. I'll try to be more careful. Dave -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
The Festival Rag v03.01
The Festival Rag v03.01 08.2005 View online : http://www.kemek.com/indie-film/the-festival-rag/08-2005.htm Faithful Rag Readers, All apologies, for our amazing truancy of the last several months. All our fault. If you'll only read on, I promise to make a boring excuse short or, at the very least, mildly entertaining. As many of you know, several months back the Rag's Editor-in Chief, Mr. Gil S. Ripley, and yours truly began scribing something a little beyond our previous experience: Reality Shows. Okay, stop laughing. On second thought, go ahead and laugh because now it's funny. Back at the beginning, when we were so desperate for money that we began pitching reality shows, it really wasn't so funny. We invented many show ideas brilliant and inane, most of which were pitched and summarily rejected, until miraculously - here's where it gets funny - one was deemed worthy of making. It has been a long, very strange process, but I will cut to the chase and tell you it's a wild contest show and we are finally scheduled to start shooting it at the end of August. By this time I know you're hooked but I am bound by confidentiality and can only gloss over the show's concept for you. The gloss is really just two parts hot air, three parts smoke and a pinch of manure. (In other words, Hollywood phraseology.) So, here goes: it's Survivor meets Fear Factor by way of The Eco-Challenge. Keeping to the industry standard, the show is shrouded in secrecy to deflect possible copycat shows, but I can say that we are shooting on an island in the Caribbean. The production team is trying to make the aforementioned reality contests appear tame by comparison, and Gil came up with the pseudo-title The Ultimate, Ultimate Challenge which surely covers all bases. But enough about us. On with the Rag, and the world of indie film! Oh, wait! Independent film, that reminds me... Coming to a film festival near you, Mr. Ripley and I will soon be featured in a documentary about television shows and the writing that creates them. A small crew from Acme Pictures here in New York has been following the whole process: how we pitch, how we work (or in Gil's case, being late for work), and what goes into the very best TV shows. On behalf of the entire Rag team, I want to say we missed you all terribly while we were away. And judging by the copious email jamming our inboxes, I can see you missed us, too. Very sweet of you. The majority of the emails say that we can increase our ejaculation by 581%, just by taking two pills daily. Again, very sweet of you. It's great to be back. Dave Roberts, Managing Editor For two weekends each October, the stunningly colorful Berkshire Mountains of western Massachusetts play backdrop to the Williamstown Film Festival. Run by writer and showbiz buff extraordinaire Steve Lawson, who began the festival in 1999, the event provides huge support for indie film from a community long known for its devotion to the arts. Not long ago, the Festival Rag found Steve at home mixing his trademark Grey Goose martinis, and pried loose some of the secrets behind running one of the best-curated film events in the country. --- Festival Rag: How many submissions do you expect to receive for the festival this year? And how is it possible to screen them all, let alone pick the ones that will actually win a berth on the schedule? Steve Lawson: Last year we got 360. Willing members of the Board pre-screen and evaluate general submissions, but in the end I see at least part of every film that comes in. FR: How often do you accept a film unseen, for whatever reason, like for instance, it screened well at another festival you admire? SL: Of 135 films at WFF in six years, I've booked just one title without seeing it first. That was Roger Dodger, because Campbell Scott is a friend and I felt implicitly that the film would be worth including. And it was. FR: Filmmakers will often pursue big names on small movies - even at the expense of telling a good story well. This often succeeds in getting them into festivals, and it certainly helps drive ticket sales. But is it a good idea? SL: Dylan Kidd's last film p.s. had an all-star cast (Laura Linney, Topher Grace, Gabriel Byrne, et al). Clearly they all wanted to work with him after Roger Dodger put him on the map. I think it's as fallible to slam an indie just because it has "names" as it is to tout an indie because it was made with unknowns on a shoestring. It all comes down to quality, which knows no hard and fast rules. FR: Most filmmakers would attend most festivals their films are shown at. Does their attendance help the festivals in return? SL: Audiences love to hear the back story, the war stories - how much did it cost? How long was the shoot? What would you do differently next time? On the rare occasion when things screw up and we don't have at
Re: Disable/Passprotect single user mode
That's right. The complete story is that I would like to protect it from my nasty family. :) They should know the BIOS password to restart my machine when I am away from home but I wouldn't like them to reach single user mode. Thanks for your advice, I think the best way is to edit /etc/ttys and set a BIOS user password for them. Jaya Sri John Kintaro Tate <[EMAIL PROTECTED]> mrta: > Edit /etc/ttys and remove the secure option and disable booting from > CD/Floppy and set a BIOS password so to change the BIOS you need > authentication. Boot authentication is another option however it > becomes a pain in the arse when you are away from home and the power > goes out, hence your server gets knocked offline until someone enters > a password. > > Simple enough, > John. > > On 8/27/05, JSD <[EMAIL PROTECTED]> wrote: > > Hi folks, > > > > I have a big root access problem. If someone has physical > > access to my OpenBSD box, than he/she can swith into single > > user mode (-s) and can change the password of root. It is a > > big problem for me and I would like to password protect this > > single user mode or to totally disable this function but I > > don't know how. > > Is anyone here who solved this problem? Please help, thanks! > > > > Jaya Sri > > > > > > ___ > > [freemail] extra 1GB-os postafiskkal, Vnnek mar van? http://freemail.hu > > > > > > > -- > John Kintaro Tate > Mobile: 0413 348 815 (Yep, old number, but I have a new phone) > > Attention all Internet users, is life getting you down? Are you so > happy you could chainsaw an innocent bystander and LAUGH? Do you > believe in God? Do you not believe in God? Have you found yourself > stranded on prehistoric Earth for 5 years? If so, if you do anything > at all there are people who care at the Kintaro Labs Forum, join now > and after you reach 50 posts you get a free OpenBSD shell account! > http://labs.kintaro.noobify.com > > Personal Website: http://kintaro.noobify.com > ___ [freemail] extra 1GB-os postafiskkal, Vnnek mar van? http://freemail.hu
Re: BSD PPPoA Hardware
Simon Morgan wrote: On 8/15/05, Simon Morgan <[EMAIL PROTECTED]> wrote: Does anyone have any suggestions? Any advice is welcome. To anyone who might be reading this in the future (Hi! Do you have robots and flying cars yet?), I've given up looking for a native solution. The state of ADSL hardware support under BSD as well as Linux is shockingly bad and simply isn't worth bothering with. The Sangoma S518 looked pretty promising but last I checked there still weren't any available to purchase in the UK and the shipment from their manufacturer keeps on getting delayed. I can only hope their engineers are more competent. I bought a Sagem [EMAIL PROTECTED] 800 to use with the ueagle driver and have had nothing but trouble with it in the 4 days I've been using it. It seems to work fine under Windows so I can only assume the driver is to blame. So that leaves cheap and nasty combination modem and routers or Cisco hardware. I've ordered a Cisco SOHO 97. i've been using an Alcatel Speedtouch usb modem with openbsd 3.7 with no problems. take a look...http://www.speedtouchdsl.com/prod330.htm i have a few documents which explains how to get it working, if you want them mail me. poncenby
Re: sensorsd and mail alert
Antoine Jacoutot skrev: How can I make sensorsd or syslog to mail me this, without running a parser every minute on /var/log/messages which looks overkill. man 5 sensorsd.conf /kami
Re: Disable/Passprotect single user mode
Dave Feustel skrev: On Saturday 27 August 2005 09:08, kami petersen wrote: Did you miss the line "If someone has physical access to my OpenBSD box"? With physical access, all of your suggestions are easily bypassed with a bios reset. as you are sure you know, that, along with matt's tip, is about as reasonable advice you can get if you can't physically secure your box, and that's why you can't come up with anything better, smart ass. /kami Also, Kami is unfamiliar with the details of the disk password. man atactl /secsetpass Dave Feustel dave, what are you smoking? please carefully note how i edited out _your_ text so as to indicate _who_ i was addressing and whom i additionally consider being a smartass. let me rephrase: dear frank. your response is unneccesary and non constructive. provided that the box in question cannot be physically secured there is little you can practically do other than applying the above methods put forward by dave and matt in order to prevent single user root access. /kami ps. except tying your german shepherd to it...
Re: sensorsd and mail alert
Antoine Jacoutot wrote: How can I make sensorsd or syslog to mail me this, without running a parser every minute on /var/log/messages which looks overkill. Answering to myself... Allright, I had a check on sensorsd under current and it looks like in 3.8 I will be able to give a command to execute when the sensor is too high. Great, I just have to wait for 3.8... Sorry for the noise, in the meanwhile, I'll use syslogc. Regards, Antoine
Re: BSD PPPoA Hardware
On 8/27/05, poncenby <[EMAIL PROTECTED]> wrote: > i've been using an Alcatel Speedtouch usb modem with openbsd 3.7 with no > problems. take a look...http://www.speedtouchdsl.com/prod330.htm How stable has it been? > i have a few documents which explains how to get it working, if you want > them mail me. I'd appreciate that, thanks.
Re: BSD PPPoA Hardware
On 8/27/05, Simon Morgan <[EMAIL PROTECTED]> wrote: > On 8/15/05, Simon Morgan <[EMAIL PROTECTED]> wrote: > > > Does anyone have any suggestions? Any advice is welcome. > > To anyone who might be reading this in the future (Hi! Do you have robots > and flying cars yet?), I've given up looking for a native solution. The > state of ADSL hardware support under BSD as well as Linux is shockingly > bad and simply isn't worth bothering with. Hi Simon and others: I am using an Actiontec model GT701R DSL modem for PPPoA here on OpenBSD 3.6. It was easy to configure. The Modem itself has the address of 192.168.0.1 and does the Network Address Translation. First, I did: /usr/bin/sudo ifconfig bge0 inet 192.168.0.5 netmask 255.255.255.0 then /usr/bin/sudo route add default 192.168.0.1 Afterwards, I configured it with Firefox. Lynx or Links would not work. The DSL modem and PPPoA works like a charm. -- Kind regards, Jonathan
Re: Disable/Passprotect single user mode
On 8/27/05, JSD <[EMAIL PROTECTED]> wrote: > I have a big root access problem. If someone has physical > access to my OpenBSD box, than he/she can swith into single > user mode (-s) and can change the password of root. This is hardly unique to OpenBSD. How about placing your devices in a securely locked place where you can adequately determine who gets access? Once people have physical access to your devices, a password to enter single user mode will not do you much good. Unless you bolt down the machine and its access panels, an attacker will just plug the hard drive into a system under his control. > [...] I would like to password protect this single user mode or to totally > disable this function You might even argue that placing a password such as you suggest slows you down when trying to get repairs done. You wouldn't be the first to lose such a password. That said, disabling single user mode seems rather nasty: you'd lose one of the best places to work on a troublesome system. Keep your maintenance access panels accessible. It's what they're there for. Cheers, Rogier -- If you don't know where you're going, any road will get you there.
Re: Disable/Passprotect single user mode
On Saturday 27 August 2005 09:08, kami petersen wrote: > > Did you miss the line "If someone has physical access to my OpenBSD > > box"? With physical access, all of your suggestions are easily bypassed > > with a bios reset. > > > > as you are sure you know, that, along with matt's tip, is about as > reasonable advice you can get if you can't physically secure your box, > and that's why you can't come up with anything better, smart ass. > > /kami > Also, Kami is unfamiliar with the details of the disk password. man atactl /secsetpass Dave Feustel -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
ThinkPad testers required
Can people with the following laptops: - ThinkPad R50, R50p, R51, R52 - ThinkPad T41, T41p, T42, T42p, T43, T43p - ThinkPad X40 - ThinkPad X41, X41 Tablet Try running the latest snapshot (08/27/05 06:49:00) Check they have working aps via sysctl hw.sensors Numbers should change when tilting the laptop. Suspend the system ie zzz Resume and check they still have normal looking numbers when running the same sysctl command again? We need this to be tested on as wide a range of models as possible ASAP. Send all reports positive and negative alike to djm@ and me.
Re: BSD PPPoA Hardware
On 8/15/05, Simon Morgan <[EMAIL PROTECTED]> wrote: > Does anyone have any suggestions? Any advice is welcome. To anyone who might be reading this in the future (Hi! Do you have robots and flying cars yet?), I've given up looking for a native solution. The state of ADSL hardware support under BSD as well as Linux is shockingly bad and simply isn't worth bothering with. The Sangoma S518 looked pretty promising but last I checked there still weren't any available to purchase in the UK and the shipment from their manufacturer keeps on getting delayed. I can only hope their engineers are more competent. I bought a Sagem [EMAIL PROTECTED] 800 to use with the ueagle driver and have had nothing but trouble with it in the 4 days I've been using it. It seems to work fine under Windows so I can only assume the driver is to blame. So that leaves cheap and nasty combination modem and routers or Cisco hardware. I've ordered a Cisco SOHO 97. Thanks to everyone who replied.
Re: SMS (mobile phone) authentication
On Sat, Aug 27, 2005 at 03:44:14PM +0200, Rickard Dahlstrand wrote: > Right now the last line just logs the key to syslog instead of sending > it to a phone. Also not that the otp-key password is hardcoded in the > script. Not really a good idea, but I have no choice. (The file is not > world readable) > > Yes, I know this is a hack and that I should probably find something > better to do instead of wasting your time with my crappy code. BUT this > exist, and even thought you don't see the use for it, can you please > just give me a hand in pointing out if this most obvious security concerns. Since SMS is, I'm pretty sure plaintext, it has all the downsides of sending any password in the clear. > > Thanks, Rickard. > -- BOFH excuse #306: CPU-angle has to be adjusted because of vibrations coming from the nearby road
Re: Disable/Passprotect single user mode
Did you miss the line "If someone has physical access to my OpenBSD box"? With physical access, all of your suggestions are easily bypassed with a bios reset. as you are sure you know, that, along with matt's tip, is about as reasonable advice you can get if you can't physically secure your box, and that's why you can't come up with anything better, smart ass. /kami
sensorsd and mail alert
Hi... One quick stupid question. I'm looking for a way to get a mail when sensorsd logs something to syslog. Is there an easy way to do this ? For instance, today sensorsd reported the following : Aug 27 15:27:21 mcp sensorsd[6314]: failure for hw.sensors.0: 46.40C/115.52F not within limits How can I make sensorsd or syslog to mail me this, without running a parser every minute on /var/log/messages which looks overkill. Thanks in advance. Regards, Antoine
SMS (mobile phone) authentication
Hi,
I have a customer that has asked me to build a SMS-authentication
solution for OpenBSD. The idea being (not saying this is a good idea,
but anyway) that when the user connects using ssh, he will get a
sms-message to his phone with a one-time passkey.
I have made it easy for myself and modified the existing login_skey. I
created a new one called login_sms and added the following three lines
to the "case MODE_CHALLENGE"-section:
-SNIPP--
case MODE_CHALLENGE:
haskey = (skeychallenge2(fd, &skey, user, challenge) == 0);
>char cmd[200];
>sprintf(cmd, "/bin/sh /etc/smsscript.sh \"%s\" \"%s\"",
auth_mkvalue(challenge), user);
>system(cmd);
strlcat(challenge, "\nS/Key Password: ", sizeof(challenge));
-SNIPP--
This means that before sending the challenge to the user the system
executes a script with the challenge and the user name as parameters.
The script looks like this:
#!/bin/sh
declare -a pno
# Declare username/phonenumber-combinations here
pno[rd]="46712344554"
pno[skeytest]="46756223452"
# Get passkey
parm1=`/bin/echo "$1" | /usr/bin/cut -f 1 -d " "`
parm2=`/bin/echo "$1" | /usr/bin/cut -f 2,3 -d " "`
key=`/usr/bin/${parm1} -p 1234567890 ${parm2}`
# Send passkey to user
/usr/bin/logger -p "auth.info" "Sending key ${key} for challenge
${parm2} to ${pno[$2]}"
Right now the last line just logs the key to syslog instead of sending
it to a phone. Also not that the otp-key password is hardcoded in the
script. Not really a good idea, but I have no choice. (The file is not
world readable)
Yes, I know this is a hack and that I should probably find something
better to do instead of wasting your time with my crappy code. BUT this
exist, and even thought you don't see the use for it, can you please
just give me a hand in pointing out if this most obvious security concerns.
Thanks, Rickard.
Re: Disable/Passprotect single user mode
Edit /etc/ttys and remove the secure option and disable booting from CD/Floppy and set a BIOS password so to change the BIOS you need authentication. Boot authentication is another option however it becomes a pain in the arse when you are away from home and the power goes out, hence your server gets knocked offline until someone enters a password. Simple enough, John. On 8/27/05, JSD <[EMAIL PROTECTED]> wrote: > Hi folks, > > I have a big root access problem. If someone has physical > access to my OpenBSD box, than he/she can swith into single > user mode (-s) and can change the password of root. It is a > big problem for me and I would like to password protect this > single user mode or to totally disable this function but I > don't know how. > Is anyone here who solved this problem? Please help, thanks! > > Jaya Sri > > > ___ > [freemail] extra 1GB-os postafiskkal, Vnnek mar van? http://freemail.hu > > -- John Kintaro Tate Mobile: 0413 348 815 (Yep, old number, but I have a new phone) Attention all Internet users, is life getting you down? Are you so happy you could chainsaw an innocent bystander and LAUGH? Do you believe in God? Do you not believe in God? Have you found yourself stranded on prehistoric Earth for 5 years? If so, if you do anything at all there are people who care at the Kintaro Labs Forum, join now and after you reach 50 posts you get a free OpenBSD shell account! http://labs.kintaro.noobify.com Personal Website: http://kintaro.noobify.com
Re: uh oh promise card problems
What would be the best way to use OpenBSD on these systems? obviously you need to get other controllers (http://openbsd.org/i386.html). then offer to donate the surplus cards to the developers, and maybe someone will do some work on it, i.e. porting it from freebsd. /kami
problems using usb keyboard on sunblade 100
Hi, I want to use a sunblade 100 with openbsd as my primary desktop. Unfortunately I'm not able to get the keyboard to work (sun usb type 6 swedish layout). After installing the miniroot.fs to the harddisk and resetting the machine it booted to the prompt where one can choose between shell, upgrade and install. I wasn't able to type anything here. I then installed over a serial line and it worked fine. After rebooting with the keyboard attached it booted to the login prompt but still I was not able to type anyhting here. Login over the network just works fine. I also can find the keyboard within the dmesg output. The eeprom command shows keyboard as input-device. The same behaviour can be seen with the 3.7 release and the latest snapshot. My OpenBoot version is 4.17.1. I'm new to openbsd maybe I'm missing something obvious here. Thanks in advance, mark dmesg: OpenBSD 3.8-beta (GENERIC) #596: Wed Aug 24 07:36:33 MDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/sparc64/compile/GENERIC total memory = 1073741824 avail memory = 968990720 using 6553 buffers containing 53682176 bytes of memory bootpath: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 mainbus0 (root): Sun Blade 100 (UltraSPARC-IIe) cpu0 at mainbus0: SUNW,UltraSPARC-IIe @ 502 MHz, version 0 FPU cpu0: physical 32K instruction (32 b/l), 16K data (32 b/l), 1024K external (64 b/l) psycho0 at mainbus0 pci108e,a001: impl 0, version 0: ign 7c0 bus range 0 to 1; PCI bus 0 DVMA map: c000 to e000 IOTDB: 4d0a000 to 4d8a000 pci0 at psycho0 ebus0 at pci0 dev 12 function 0 "Sun PCIO Ebus2 (US III)" rev 0x01 flashprom at ebus0 addr 0-f not configured clock1 at ebus0 addr 0-1fff: mk48t59: hostid 83087c13 ebus_attach: idprom: incomplete gem0 at pci0 dev 12 function 1 "Sun ERI Ether" rev 0x01: ivec 3006, address 00:0 3:ba:08:7c:13 ukphy0 at gem0 phy 1: Generic IEEE 802.3u media interface ukphy0: OUI 0x0010dd, model 0x0002, rev. 1 "Sun FireWire" rev 0x01 at pci0 dev 12 function 2 not configured ohci0 at pci0 dev 12 function 3 "Sun USB" rev 0x01: ivec 24, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: Sun OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ebus1 at pci0 dev 7 function 0 "Acer Labs M1533 ISA" rev 0x00 dma at ebus1 addr 0- ipl 42 not configured power at ebus1 addr 800-82f ipl 32 not configured com0 at ebus1 addr 3f8-3ff ipl 43: ns16550a, 16 byte fifo com1 at ebus1 addr 2e8-2ef ipl 43: ns16550a, 16 byte fifo "Acer Labs M7101 Power" rev 0x00 at pci0 dev 3 function 0 not configured autri0 at pci0 dev 8 function 0 "Acer Labs M5451 Audio" rev 0x01: ivec 23 ac97: codec id 0x41445348 (Analog Devices AD1881A) ac97: codec features headphone, Analog Devices Phat Stereo audio0 at autri0 midi0 at autri0: <4DWAVE MIDI UART> pciide0 at pci0 dev 13 function 0 "Acer Labs M5229 UDMA IDE" rev 0xc3: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using ivec 180c for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: wd0: 16-sector PIO, LBA, 21557MB, 44150400 sectors atapiscsi0 at pciide0 channel 0 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SCSI0 5/cdrom removable wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 cd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 disabled (no drives) ppb0 at pci0 dev 5 function 0 "DEC 21152 PCI-PCI" rev 0x03 pci1 at ppb0 bus 1 vgafb0 at pci1 dev 1 function 0 "Intergraph Expert3D" rev 0x00 vgafb0: failed to find all ports vgafb1 at pci0 dev 19 function 0 "ATI Rage XL" rev 0x27 wsdisplay0 at vgafb1 wsdisplay0: screen 0 added (std, sun emulation) pcons0 at mainbus0 No counter-timer -- using %tick at 502MHz as system clock. uhidev0 at uhub0 port 1 configuration 1 interface 0 uhidev0: Sun Microsystems Type 6 Keyboard, rev 1.00/1.02, addr 2, iclass 3/1 ukbd0 at uhidev0: 8 modifier keys, 6 key codes wskbd0 at ukbd0: console keyboard uhidev1 at uhub0 port 2 configuration 1 interface 0 uhidev1: Sun Microsystems Type 6 Mouse, rev 1.00/1.02, addr 3, iclass 3/1 ums0 at uhidev1: 3 buttons wsmouse0 at ums0 root on wd0a rootdev=0xc00 rrootdev=0x1a00 rawdev=0x1a02
Re: Disable/Passprotect single user mode
On Saturday 27 August 2005 07:27, Dave Feustel wrote: > On Saturday 27 August 2005 06:07, JSD wrote: > > Hi folks, > > > > I have a big root access problem. If someone has physical > > access to my OpenBSD box, than he/she can swith into single > > user mode (-s) and can change the password of root. It is a > > big problem for me and I would like to password protect this > > single user mode or to totally disable this function but I > > don't know how. > > Is anyone here who solved this problem? Please help, thanks! > > > > Jaya Sri > > > > > > ___ > > [freemail] extra 1GB-os postafiskkal, Vnnek mar van? http://freemail.hu > > In your bios, you should be able to set a boot password which will prevent > booting until the password is given. > > In addition, if you have a laptop, youshould be able to also set a disk > password > which will also prevent booting until it is given. > > Finally, you should be able in the bios to disable booting > from any device but the hard disk containing the operating system. I forgot to mention that there is also a master bios password that, when set. will permit the system to boot after the boot password is given, but will disable making any changes to the bios without first entering the master password. > Dave Feustel > -- > Tired of having to defend against Malware? > (You know: trojans, viruses, SPYWARE, ADWARE, > KEYLOGGERS, rootkits, worms and popups) > Then Switch to OpenBSD with a KDE desktop!!! > > -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
Re: Disable/Passprotect single user mode
At 08:27 AM 8/27/05, Dave Feustel wrote: On Saturday 27 August 2005 06:07, JSD wrote: > Hi folks, > > I have a big root access problem. If someone has physical > access to my OpenBSD box, than he/she can swith into single > user mode (-s) and can change the password of root. It is a > big problem for me and I would like to password protect this > single user mode or to totally disable this function but I > don't know how. > Is anyone here who solved this problem? Please help, thanks! > > Jaya Sri In your bios, you should be able to set a boot password which will prevent booting until the password is given. In addition, if you have a laptop, you should be able to also set a disk password which will also prevent booting until it is given. Finally, you should be able in the bios to disable booting from any device but the hard disk containing the operating system. Dave Feustel Did you miss the line "If someone has physical access to my OpenBSD box"? With physical access, all of your suggestions are easily bypassed with a bios reset.
Re: Disable/Passprotect single user mode
On Aug 27 01:07 PM, JSD wrote: > Hi folks, > > I have a big root access problem. If someone has physical > access to my OpenBSD box, than he/she can swith into single > user mode (-s) and can change the password of root. It is a > big problem for me and I would like to password protect this > single user mode or to totally disable this function but I > don't know how. > Is anyone here who solved this problem? Please help, thanks! > If you remove the 'secure' option for the console from /etc/ttys it will ask for a password in single user mode. But that won't stop someone from booting via floppy/cd/net if they have physical access to the device. Matt
Re: Disable/Passprotect single user mode
On Saturday 27 August 2005 06:07, JSD wrote: > Hi folks, > > I have a big root access problem. If someone has physical > access to my OpenBSD box, than he/she can swith into single > user mode (-s) and can change the password of root. It is a > big problem for me and I would like to password protect this > single user mode or to totally disable this function but I > don't know how. > Is anyone here who solved this problem? Please help, thanks! > > Jaya Sri > > > ___ > [freemail] extra 1GB-os postafiskkal, Vnnek mar van? http://freemail.hu In your bios, you should be able to set a boot password which will prevent booting until the password is given. In addition, if you have a laptop, youshould be able to also set a disk password which will also prevent booting until it is given. Finally, you should be able in the bios to disable booting from any device but the hard disk containing the operating system. Dave Feustel -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
Re: argus calloc failure on 3.7
On 8/27/05, Russell Fulton <[EMAIL PROTECTED]> wrote: > I am having problems running argus on 3.7. The server runs > for a variable amount of time (ususlly 1 - 2 hours) and then dies when a > calloc for > 128 bytes fails. We are fairly sure that this is not because of real memory > exhustion > (watching with top does not show any obvious leakying behaviour) so that > points to > possible bad frees or some other issue. Argus runs happily on other BSDs > (and other > flavous of UNIX/Linux) and people have used it on older OBSD versions. What user is argus running as? Have you hit a ulimit? -- ach
Disable/Passprotect single user mode
Hi folks, I have a big root access problem. If someone has physical access to my OpenBSD box, than he/she can swith into single user mode (-s) and can change the password of root. It is a big problem for me and I would like to password protect this single user mode or to totally disable this function but I don't know how. Is anyone here who solved this problem? Please help, thanks! Jaya Sri ___ [freemail] extra 1GB-os postafiskkal, Vnnek mar van? http://freemail.hu
HPN-SSH
Hi. I know, it doesnt concern to openbsd directly, but... Do You now what is this - http://www.psc.edu/networking/projects/hpn-ssh/ ? Your thoughts about it? Is this reasonably to use? wbr. Thanks.
Re: How scared should I be of "atactl: ATA command timed out"
On Fri, Aug 26, 2005 at 11:04:03AM -0600, Josh Tolley wrote: > One of my cronjobs, as suggested in the atactl manpage, is the > following, designed to email me if my soekris gets disk errors (it's a > disk-based install, not a flash-based one). > > atactl: ATA command timed out > > How worried should I be about this? I've run the same command again > today, without it reporting any errors, and this is the first error of > this kind I've seen. Google and archives didn't help much, and I'm not > a disk guru. Thanks in advance. > > -Josh is your disk in standby mode? the 'smartstatus' command seems to time-out if the disk is in standby mode. -- Alexandre
uh oh promise card problems
I just got 3 systems delivered today that have SATA drives connected to a Promise tx220 (pdc20571) card. Of course it turns out these are incompatible with OpenBSD. It looks like maybe these work with FreeBSD as this url seems to suggest: http://cvsup.de.openbsd.org/mirrors/ftp.freebsd.org/mail-archive/archive/cvs-all Naturally I'd prefer OpenBSD. I did try an install, with 3.7 -release and the latest 3.8-beta snapshot (no drives found). What would be the best way to use OpenBSD on these systems?
[SOLVED] problem with postgresql on sparc64 (lack of working socket?)
On Sat, Jul 02, 2005 at 03:12:52PM +0200, Simon Dassow wrote: > i've set up postgresql as usual and wanted to connect... but: > $ psql > psql: could not send startup packet: Broken pipe [snip] > LOG: could not connect socket for statistics collector: Invalid > argument > LOG: disabling statistics collector for lack of working socket [snip] > LOG: setsockopt(TCP_NODELAY) failed: Protocol not available [snip] > It's NOT dependent on the tcp listening socket as the same thing > happens without enabling tcp. > > I also added the login class as stated in the install script... so i > don't think there's anything i've forgotten. The only thing i missed is -current ;-) Now it's working like a charm without any issues. Regards, Simon
Re: Kernel having problems to read disklabel
I tried to install a Debian on the disk where OpenBSD had problems to
read the disklabel.
I managed to install it correctly BUT... at boot it hangs for about
1minutes, trying to access I don't know what on the disk. But it seems
to not affect the Debian.
And today, I tried to install OpenBSD disklabels on another disk (IBM
Travelstar 30gb, more recent), which model is quite similar to the one
causing problems.
No problems with that disk, which mean that there is no doubt
possible... the problem is coming from the disk.
But it remain strange that, even if I did not manage to install openbsd
on it, I managed to install Debian.
The disk seems to have a problem, but I can still use it.
Have a good day !
Marc
dooble M a icrit :
Hi everybody
Firstly, thanks to all people contributing to the OpenBSD project.
Thanks also to people who try to help others on that list.
I'm fairly new to OpenBSD.
I installed the 3.7 release some days ago on an old laptop, which
is a Dell Latitude Xpi p133st.
Hard disk: IBM OEM model DMCA-21440size: 1440MB
This was my first installation of OpenBSD, I read the FAQ carefully
and managed to install it from floppy (floppyC37.fs for laptops),
downloading the tgzs from FTP.
As it was just a test install, I put OpenBSD in only 500MB.
A few days after, as the system was running ok, I got a new hard disk
and tried to install OpenBSD 3.7 on the new disk.
New hard disk: IBM Travelstar mode DBCA-206480size: 6.49GB
I did the same as the first install, and all the installation procedure
goes ok... (partitionning, download and extaction of tgzs).
At the first boot, while the kernel was loading, it does a kernel panic
: the kernel was not able to reach '/' on wd0a.
Here was my problem in a nutshell. I will know give you more
information.
First openbsd install on the 1440MB drive (ok) :
I installed openbsd in a 500mb partition, at the begining of the disk.
-
Result of 'fdisk wd0':
Disk: wd0geometry: 699/64/63 [2818368 Sectors]
Offset: 0Signature: 0xAA55
Starting Ending LBA Info:
#: idC H S -C H S [ start: size ]
*0: A60 1 1 - 253 63 63 [ 63: 1024065 ] OpenBSD
1: 05 254 0 1 - 277 63 63 [ 1024128: 96768 ] Extended
DOS
2: 83 278 0 1 - 698 63 63 [ 1120896: 1697472 ] Linux
files*
3: 000 0 0 -0 0 0 [ 0: 0 ] unused
Offset: 1024128Signature: 0xAA55
Starting Ending LBA Info:
#: idC H S -C H S [ start: size ]
0: 82 254 1 1 - 277 63 63 [ 1024191: 96705 ] Linux swap
1: 000 0 0 -0 0 0 [ 0: 0 ] unused
2: 000 0 0 -0 0 0 [ 0: 0 ] unused
3: 000 0 0 -0 0 0 [ 0: 0 ] unused
-
Result of 'disklabel wd0':
# /dev/rwd0c:
type: ESDI
disk: ESDI/IDE disk
label: IBM-DMCA-21440
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 2796
total bytes: 1376.2M
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0# microseconds
track-to-track seek: 0# microseconds
drivedata: 0
16 partitions:
# sizeoffset fstype [fsize bsize cpg]
a: 99.9M 0.0M 4.2BSD 2048 16384 202 # Cyl
0*- 202
b: 32.0M 99.9Mswap # Cyl 203
- 267
c: 1376.2M 0.0M unused 0 0 # Cyl 0
- 2795
d: 50.2M131.9M 4.2BSD 2048 16384 102 # Cyl 268
- 369
e: 50.2M182.1M 4.2BSD 2048 16384 102 # Cyl 370
- 471
f:267.8M232.3M 4.2BSD 2048 16384 328 # Cyl 472
- 1015
i:828.8M547.3M ext2fs # Cyl 1112
- 2795
j: 47.2M500.1M unknown # Cyl
1016*-
--
(mount points :)
a: /
b: swap
d: /tmp
e: /var
f: /usr
-
Result of 'dmesg':
OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium (P54C) ("GenuineIntel" 586-class) 134 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8
cpu0: F00F bug workaround installed
real mem = 24752128 (24172K)
avail mem = 14585856 (14244K)
using 327 buffers containing 1339392 bytes (1308K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 07/22/97, BIOS32 rev. 0 @
0xffe90
apm0 at bios0: Power Management spec V1.1
apm0: battery life expectancy 88%
apm0: AC on, battery charge high, charging, estimated 3:45 hours
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI BIOS has 0 Interrupt Routing table entries
pcibios0: no compatible PCI IC
Writing errataXX.html easier and providing a kind of RSS feed of vulnerabilities at the same time
What if we had something like this: More stringent checking should be done in the http://www.openbsd.org/cgi-bin/man.cgi?query=copy&sektion=9";>copy(9) functions to prevent their misuse. We would be able to build the respective errataXX.html from it, separating format from content, and providing at the same time a kind of RSS feed for those who want it (like me). The benefits would be many: For developers maintaining errataXX.html: - One single place for changing the format of _all_ the errataXX.html pages (layout, links to new releases, colors, ...) - No need to mess with HTML when adding a new patch, except for writing the patch description. - No more errors because of copying an old errataXX.html as a base for writing the new errata.html We could even use it for sending a mail automatically to security-announce@ For translators: - Focus on translating the text only - No need to track changes in the format of the pages any more :) For users: - A simple, easy to parse file for getting errata up to date - Eases the writing of scripts for automating patching XSL would do the magic here. It would be as easy as: $ xsltproc errata.xsl errata-37.xml > errata37.html We only have to edit errata.xsl to change the layout/format for all the errataXX.html files. We could even write a Makefile for that. errataXX.html would be not the only pages generated from a script (groups.html is already generated from one). If any developer/translator/user is still reading this and thinks it would be good idea ... you can find two samples and the XSL script in the URL provided below. It's a working _prototype_ that I could developer further if it is of any interest. It may lack of many things yet (update date & time comes to mind). http://www.openbsd.org.mx/santana/errata/ -- Gerardo Santana
Re: wireless bridge with soekris 4801 and seano 2511mp+
I ought to kick myself! I've been through that page so many times, but never saw that. Thanks a lot! Regards, Anwar. ___ Sent with SnapperMail www.snappermail.com .. Original Message ... On Sat, 27 Aug 2005 01:23:51 +0100 "pedro la peu" <[EMAIL PROTECTED]> wrote: >> It would be useful if this little gotcha could be added to the man page > >man 4 wi >/EXAMPLES
Re: boot> set tty com0; switching to serial console com0; blinking cursor
Hello List, While waiting for a make build to finish... I thought of just letting OpenBSD boot to login and use the other terminals to login to the serial consoles. Works like a charm! Now learn to build an Alpha bastion server, Sparc64 dhcp, DNS server, i386 mail server... getting off of M$ Windows eventually. Have a good weekend, rogern From: "Roger Neth Jr" <[EMAIL PROTECTED]> To: misc@openbsd.org Subject: boot> set tty com0; switching to serial console com0; blinking cursor Date: Fri, 26 Aug 2005 17:33:08 -0700 Hello List, I have been successfully communicating to an Alpha and Sparc64 via serial tty00 and tty01 in fvwm term as root # cu -l tty00 When I try to set this at boot there is a blinking cursor boot> set tty com0 switching to serial console com0 _ I have tried editing /etc/ttys tty00 "/usr/libexec/getty std.9600" vt220 on secure This is on 3.8-beta i386 I don't know if I understand that a host i386 is unable to do this at boot time. This is on an IBM x220 Any assitance on this is appreciated. Here is my ttys file, let me know if any other info. is required. Thank you, rogern # $OpenBSD: ttys,v 1.17 2002/06/09 06:15:14 todd Exp $ # # name getty typestatus comments # console "/usr/libexec/getty Pc" vt220 off secure ttyC0 "/usr/libexec/getty Pc" vt220 on secure ttyC1 "/usr/libexec/getty Pc" vt220 on secure ttyC2 "/usr/libexec/getty Pc" vt220 on secure ttyC3 "/usr/libexec/getty Pc" vt220 on secure ttyC4 "/usr/libexec/getty Pc" vt220 off secure ttyC5 "/usr/libexec/getty Pc" vt220 on secure ttyC6 "/usr/libexec/getty Pc" vt220 off secure ttyC7 "/usr/libexec/getty Pc" vt220 off secure ttyC8 "/usr/libexec/getty Pc" vt220 off secure ttyC9 "/usr/libexec/getty Pc" vt220 off secure ttyCa "/usr/libexec/getty Pc" vt220 off secure ttyCb "/usr/libexec/getty Pc" vt220 off secure tty00 "/usr/libexec/getty std.9600" unknown off tty01 "/usr/libexec/getty std.9600" unknown off tty02 "/usr/libexec/getty std.9600" unknown off tty03 "/usr/libexec/getty std.9600" unknown off tty04 "/usr/libexec/getty std.9600" unknown off tty05 "/usr/libexec/getty std.9600" unknown off tty06 "/usr/libexec/getty std.9600" unknown off tty07 "/usr/libexec/getty std.9600" unknown off _ On the road to retirement? Check out MSN Life Events for advice on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement _ On the road to retirement? Check out MSN Life Events for advice on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement
