Re: USB Keyboards during install
On 12/4/06, Matthew P Szudzik [EMAIL PROTECTED] wrote: There used to be problems using USB keyboards during the OpenBSD install on i386, and workarounds were discussed in section I've done a few 4.0 installs with usb keyboards on different i386 machines, haven't had to perform any workarounds. Not sure if that's representative of all cases but I thought I'd mention it. Mike
Re: console font size
On Wed, Jan 25, 2006 at 05:45:52PM -0600, Igor Vilensky wrote: How does one control appearance of console/fonts on the screen? On one laptop, letters are quite large and console fills entire screen, on another, letters are tiny and the console fills a fraction of the screen. Check out the man pages for: wsconscfg, wsconsctl, wsfontload Mike
Re: A Little Tip for OpenBSD Users of KDE
On 12/26/05, Dave Feustel [EMAIL PROTECTED] wrote: Don't use sudo in any konsole session. That's odd. Why shouldn't you use sudo? Mike
Re: Why Perl (a request to the developer sof the Ports-System)
On Fri, Dec 02, 2005 at 11:27:34AM -0600, L. V. Lammert wrote: Perl has been around 'forever', .. is very useful for a ton of sysadmin applications (a good reason for it to be in base), .. has a lot of good support (a la class libraries interfaces), .. but it's NOT true OO (which has it's plusses minuses). Python is an OO language that is much less widely supported, but it has a good start in the web community. It's just now starting to proliferate for other applications. If Web is your forte, however, you might want to consider Ruby. I'd definitely suggest a look at ruby. It's gotten publicity lately for web stuff due to rails but is also very useful for other applications including sysadmin-stuff, gui apps, etc. The FreeBSD ports system uses ruby as well. Mike
Re: su on 3.8 soekris
Someone (you perhaps?) just recently said: Additionally, try to su and sudo to another account - create one, if necessary. Report back on your findings. I missed the beginning of this thread (fingers get happy on the d key some mornings;)) but you may want to add a new user in the staff login class and the wheel group and try to su with that account? Mike H
Re: OpenBSD hack for the ipod
On 10/20/05, Ed Wandasiewicz [EMAIL PROTECTED] wrote: 3.8-current now provides scsi access for all ipods, including the nano. If apple only knew that I was waiting for this so that I could plug an ipod into my zaurus. What a great advertising campaign that would be... Mike
Re: OpenBSD's 10th birthday -- how about a present?
On 10/21/05, Ramiro Aceves [EMAIL PROTECTED] wrote: Hi OpenBSD fans! My 3.8 CD preorder is sent also! I am waiting nervous for the 3.8 release! Nervous? You must mean anxious :) One of the main reasons I love OpenBSD is because there is so much less to be nervous about! Mike
Re: getting usb networking up on the Zaurus
On 10/4/05, Chuck Robey [EMAIL PROTECTED] wrote: I guess I don't immediately see why you say that those would be better choices than the usb solution. I'm guessing that if you don't have the usb host cable then it's the better choice. Buying one piece (i.e. a cf network card) is easier than buying a host cable, and a usb ethernet card (espcially since you can't usually just walk into your local shop and get the host cable, usually requires some shipping). FWIW I'm using a linksys usb200M and it works great. Mike
Re: OpenBSD on Nokia IP3300?
On 10/4/05, Alexandre [EMAIL PROTECTED] wrote: If they did it with Linux, it can be done with OpenBSD. unless it uses some proprietary drivers ;) (like my nvidia card...doh!) Mike
Re: PF story, happy ending.
On 10/1/05, Diana Eichert [EMAIL PROTECTED] wrote: I helped a friend setup a firewall environment years ago in front of his web business, first it was on IPF(back when OpenBSD shipped w/IPF), then PF. Amazingly he's managed to keep his business up, running and growing through the dot-bomb period, but I digress. Great story ;) I'm just wondering what version the firewall is running, and if it's an old version, have you considered upgrading? Would there be any benefit to upgrading? (I suppose that last question is what I'm really wondering about) Mike
Re: is there a way to block sshd trolling?
IIRC there are scripts what will automatically add lines to your hosts.deny file. Sorry, but I can't remember the names. I suggest you also create some keys for yourself to use and disable password authentication. With password auth disabled the attacks won't go be more than an annoyance for the most part. If you google you'll find it's a very common problem, I'm sure you'll also find the scripts I mentioned above. If I can find them I'll post links. Good luck! Mike
Re: Text Editor
You might try gvim, or xemacs, or bluefish? Mike
Re: scp Remote - Remote fails
On 9/8/05, Roy Morris [EMAIL PROTECTED] wrote: I know this is not 'exactly' openbsd directly related but I'll give it a go anyway. I am trying to copy remote 2 remote, basically to change the name of a file. If you are working with remote files only, and you know they exist, why not just use something like: ssh hostname command to run cp? Just a thought... Mike
Re: [OT] Question about vpn and athorization between OpenBSD and Windows clients
I use openvpn, it uses PKI so only hosts with keys that you've signed will be able to access your vpn. I found an article (http://blog.innerewut.de/articles/2005/07/04/openvpn-2-0-on-openbsd) that helped me get it set up. openvpn also has client + server versions for windows, so it might be useful to you. Mike
Re: Shell account cgi script
On 9/7/05, Will H. Backman [EMAIL PROTECTED] wrote: Perhaps the OpenBSD community can at least come up with some general hints for people who wish to use OpenBSD for hosting shell accounts. IMHO a good method of this is by setting up a chroot for user shells, whereby a user can log in and at worst will only have access to other user's files, not the system's core files (assuming of course it's impossible for them to su to root and exit the chroot). There is documentation available for setting up such accounts, though maybe not openbsd specific, I'm sure the main principles apply? Mike
Re: Shell account cgi script
On 9/7/05, Adam [EMAIL PROTECTED] wrote: On Wed, 7 Sep 2005 13:37:45 -0400 Mike Hernandez [EMAIL PROTECTED] wrote: If someone is wanting to give people shell accounts, then they generally want people to be able to access more than just the shell itself. The whole point is to let them use the system, if you chroot them then they can't do anything. On the contrary, they can do anything that the administrator makes it possible for them to do. Many of the web hosting accounts I've signed up for came with a jailed shell that I could use to work with the files on the server but nothing more. Mike
Re: Shell account cgi script
On 9/7/05, Adam [EMAIL PROTECTED] wrote: And web hosting is not shell hosting is it? What does work with mean anyways? You need all the binaries to work with, and they need all their libs to function. Sure, you could copy all the binaries and libraries of the entire OS into the chroot, but then what is the point of chrooting them at all? What do you think this will protect you from? Work with means using various programs like vim or emacs or sed, etc to manipulate the files. And yes you need the binaries and their associated libraries for each program you want a jailed user to be able to run. You don't need an entire OS made available to you in order to have some sort of useful experience with a shell account. For many people a shell account is just that... access to bash, or zsh, etc. and basic system utils. Maybe lynx... maybe mutt. What it does is allow you to give users access to a shell where they can experiment with their own files but not the files of the machine running the shells. This is the point of chrooting any running program. In the case of a shell it's just the shell binary running in the chroot as opposed to httpd or mysqld, etc. It's a useful idea in some scenarios, in others it's not. Mike
Re: Shell account cgi script
On 9/7/05, Adam [EMAIL PROTECTED] wrote: It's a useful idea in some scenarios, in others it's not. Right, and providing shell accounts is in the not category. Adam OK I have to concede here. I didn't realize how powerful user classes were. After doing some research I see that all of the docs I've read about chrooted shells contain info that really only applies to Linux (e.g. http://www.linuxexposed.com/Articles/General/Using-Chroot.html). I'm still new to bsd, so this was an eye opener. It would have been more fun learning this if the person on the other end of the argument wasn't [EMAIL PROTECTED] though. A lesson learned is a lesson learned nonetheless I suppose Mike
Re: Text editor
On 8/6/05, J.C. Roberts [EMAIL PROTECTED] wrote: 5.) pico is a very simple editor that is friendly to new people who have only worked with modeless editors like MS notepad. If you just want to edit the damn file without destroying it or giving up in frustration, pico is a good answer that works in a familiar way. pico is part of the pine email client available in the OpenBSD ports/packages collection. Great summary of text editors, imho. Just want to mention that if you don't want to install pine just to use pico, you can try nano, which is basically pico. The name is another of the countless silly jokes I guess... :) Mike
