Re: Using ISO8859 and perl
Guy Coleman wrote: > I'm also seeing this with both en_GB.ISO8859-15 and en_GB.ISO_8859-15 > whenever I run perl. I'd missed out a colon in login.conf. Solved! -Guy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.5-RC1: Why sshd require opie for SSH version 2?
I send this message to [EMAIL PROTECTED], because Brian committed
skeychallenge() -> opiechallenge() staff...
Brian, could you check this?
I change crypto/openssh/auth-chall.c as follows, and test it.
--- auth-chall.c.dist Thu Sep 27 18:33:33 2001
+++ auth-chall.cThu Jan 17 13:28:07 2002
@@ -77,7 +77,7 @@
{
static char challenge[1024];
struct opie opie;
- if (opiechallenge(&opie, authctxt->user, challenge) == -1)
+ if (opiechallenge(&opie, authctxt->user, challenge))
return NULL;
strlcat(challenge, "\nS/Key Password: ", sizeof challenge);
return challenge;
It works as expected, ie:
* FreeBSD 4.5-RC1 box is in default config.
* Client is OpenSSH_3.0.1p1, in default config.
(1) If /etc/opiekeys @ FreeBSD box is size=0, opiechallenge return 1,
and sshd fall back to plain password. OK.
(2) If /etc/opiekeys @ FreeBSD box lists no requested user, same as
(1). OK.
(3) If there are no /etc/opiekeys @ FreeBSD box, /etc/opiekeys is
created automatically, and behave as (1). OK.
(4) If requested user is listed on /etc/opiekeys @ FreeBSD box, sshd
requests opie password, and happy with correct pass phrase. OK.
Koji
From: Koji Hino <[EMAIL PROTECTED]>
Subject: Re: 4.5-RC1: Why sshd require opie for SSH version 2?
Date: Wed, 16 Jan 2002 17:35:25 -0800 (PST)
ID: <[EMAIL PROTECTED]>
:> Thanks to everyone who answered to my question.
:>
:> OK, there are some workaround to overcome this problem. Then, how
:> 4.5-R should be? Disable opie as default sshd configuration?
:>
:> Or
:>
:> I looked into source (not deeply), and found:
:> * opiechallenge() [/usr/src/contrib/opie/libopie/challenge.c] returns
:> value: 0, -1, 1. If there are no related user, it seems (I'm not
:> checked by debugger. only my understanding..) to return 1.
:> * old version, skeychallenge(), only return 0 (OK), or -1 (BAD).
:> * get_challenge() [/usr/src/crypto/openssh/auth-chall.c] only check
:> return value of opiechallenge() if it is -1.
:>
:> So, I think get_challenge() should handle '1' case.
:>
:> Best regards,
:>
:>
:> Koji HINO(HINO is my family name)
:> C&C Research Laboratories, NEC USA, Inc.
:> E-mail: [EMAIL PROTECTED]
:> --
:> DISCLAIMER: this message is the author's personal opinion and does not
:> constitute the support, opinion, or policy of NEC USA, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: random crashes on 4.4-S - ASUS CUSL2-M mobo
On Thu, Jan 17, 2002 at 03:52:24PM -0500, Eric L. Howard wrote: > I'm experiencing totally random crashes on a rackmount box. It's a PIII 750 > on an ASUS CUSL2-M - onboard 3c920. > > The crashes are complete random and usually follow processes that die w/ > SIGSEGV (a couple of SIGABRT thrown in for good measure have been found > also). > > Syslog gives me info such as... (lines are wrapped) > > Jan 16 01:03:28 www /kernel: pid 692 (httpd), uid 65534: exited on signal 11 > Jan 17 15:09:35 www /kernel: pid 290 (cpp0), uid 0: exited on signal 11 (core dumped) > Jan 17 15:36:53 www /kernel: pid 310 (grep), uid 0: exited on signal 11 (core dumped) > Jan 17 15:36:57 www /kernel: pid 252 (bash), uid 0: exited on signal 11 (core dumped) > Jan 17 15:37:03 www /kernel: pid 313 (grep), uid 0: exited on signal 11 (core dumped) > Dec 29 13:43:54 www /kernel: pid 1703 (cvsup), uid 0: exited on signal 6 (core >dumped) > > I've swapped memory at least twice - each time yielding no success. Not > sure about how to get anywhere debugging core files - pointers appreciated. > > Any and all ideas will be appreciated and checked. Thanx. > > 4.4-STABLE FreeBSD 4.4-STABLE #0: Fri Nov 23 23:41:12 EST 2001 Temperature? Can you run a temperature/fan-rpm/whatnot monitor, such as healthd? Totally random w.r.t. system load, or just totally random w.r.t. clock time? Or something else? -- Mike Andrews [EMAIL PROTECTED] Tired old sysadmin since 1964 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
random crashes on 4.4-S - ASUS CUSL2-M mobo
I'm experiencing totally random crashes on a rackmount box. It's a PIII 750 on an ASUS CUSL2-M - onboard 3c920. The crashes are complete random and usually follow processes that die w/ SIGSEGV (a couple of SIGABRT thrown in for good measure have been found also). Syslog gives me info such as... (lines are wrapped) Jan 16 01:03:28 www /kernel: pid 692 (httpd), uid 65534: exited on signal 11 Jan 17 15:09:35 www /kernel: pid 290 (cpp0), uid 0: exited on signal 11 (core dumped) Jan 17 15:36:53 www /kernel: pid 310 (grep), uid 0: exited on signal 11 (core dumped) Jan 17 15:36:57 www /kernel: pid 252 (bash), uid 0: exited on signal 11 (core dumped) Jan 17 15:37:03 www /kernel: pid 313 (grep), uid 0: exited on signal 11 (core dumped) Dec 29 13:43:54 www /kernel: pid 1703 (cvsup), uid 0: exited on signal 6 (core dumped) I've swapped memory at least twice - each time yielding no success. Not sure about how to get anywhere debugging core files - pointers appreciated. Any and all ideas will be appreciated and checked. Thanx. 4.4-STABLE FreeBSD 4.4-STABLE #0: Fri Nov 23 23:41:12 EST 2001 ~elh -- Eric L. Howard e l h @ o u t r e a c h n e t w o r k s . c o m www.OutreachNetworks.com313.297.9900 Advocate of the Theocratic Rule To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Using ISO8859 and perl
Hi,
Gunnar Flygt wrote:
> When I start pkg_version I get the following startinfo:
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LC_ALL = (unset),
> LC_CTYPE = "sv_SE.ISO8859-1",
> LANG = "sv_SE.ISO8859-1"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
>
I'm also seeing this with both en_GB.ISO8859-15 and en_GB.ISO_8859-15
whenever I run perl.
/usr/share/locale/en_GB.ISO8859-15 does exist, and I re-built my
world/kernel today.
Have I missed something?
-Guy.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: NTP packet routing problem
On 2002-Jan-17 01:06:57 -0500, Harlan Stenn <[EMAIL PROTECTED]> wrote: >It might also be the NTP associations - ntpd makes it associations based on >the IP of the local machine, and if your PPP link goes down/up and you get a >new IP then ntpd will continue to attempt to communicate using its old >IP address (association). I'm using static IP addresses so that's not it. >OBTW, if you are using PPP connections for NTP it's probably a good idea to >use both the "burst" and "tinker huffpuff 7200" (more or less) things in >your ntp.conf file. Thanks for that. I've enabled "burst", but I missed the "huffpuff". Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Using ISO8859 and perl
hi,
On Thu, Jan 17, 2002 at 03:32:19PM +0100, Gunnar Flygt wrote:
> When I start pkg_version I get the following startinfo:
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LC_ALL = (unset),
> LC_CTYPE = "sv_SE.ISO8859-1",
> LANG = "sv_SE.ISO8859-1"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
>
> How can I make perl aware of local language settings. Maybe not a
> "stable" question, but since it's the only list I'm connected to :)
Please check existence of directory:
/usr/share/locale/sv_SE.ISO8859-1
If this directory is missing then just upgrade to -STABLE (support for
ISO8859-1 names was commited week ago)
Or just switch your environment to use sv_SE.ISO_8859-1.
> But of course the system is -STABLE
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Questions about upcoming FreeBSD 4.5...
* I am not subscribed to this list, please cc: me in any replies * I have a few questions about FreeBSD, I have been using Linux and Unix now for quite some time but am considering switching my home system to FreeBSD. One question I have is this, in linux even though there is a text console by default (using vga) you can use a frame buffer console for just about any video card out right now so that I am able to use my brand new ATI Radeon 7500 to have a console which is at 1280x1024 at 8bit depth with a refresh of 85 Hz, is this possible in FreeBSD or are only certain cards able to be used in frame buffer mode for virtual consoles? Also I only have a USB keyboard currently and when I boot up from FreeBSD 4.2 or 4.3 bootable CDs they do not detect my keyboard once the kernel has booted and I can not navigate the install menu at all, FreeBSD 4.4 seems to not boot at all on my system because it always hangs at the "detecting hardware" message, then today I downloaded the FreeBSD 4.5-RC1-cdboot iso and it at least booted again, and booted quite speadily using the new cdboot process but then once I am to the menu to begin installing it still will not work with my USB keyboard. Will there ever be support for USB keyboards during the installation process? If there will not be and I can borrow a PS2 keyboard for a while is there at least support for USB keyboards on virtual consoles and X Windows? Thank you for any information. Jordan Breeding To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Using ISO8859 and perl
On Jan 17, 2002, 15:32 (+0100) Gunnar Flygt <[EMAIL PROTECTED]> wrote:
> When I start pkg_version I get the following startinfo:
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LC_ALL = (unset),
> LC_CTYPE = "sv_SE.ISO8859-1",
> LANG = "sv_SE.ISO8859-1"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
I think you have misspelled the data. I have
LANG=sv_SE.ISO_8859-1
Mats
--
Mats Dufberg <[EMAIL PROTECTED]>
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Force keyboard detection flag?
Have you never compiled your own kernel? Here's a paste from LINT: # `flags' for atkbd: # 0x01Force detection of keyboard, else we always assume a keyboard # 0x02Don't reset keyboard, useful for some newer ThinkPads # 0x04Old-style (XT) keyboard support, useful for older ThinkPads And GENERIC has: device atkbd0 at atkbdc? irq 1 flags 0x1 Remove the 0x1 flag and recompile, also a look at the boot(8) manpage: -Pprobe the keyboard. If no keyboard is found, the -D and -h options are automatically set. Remove the -P from /boot.config Baldur On Thursday 17 January 2002 17:05, you wrote: > I started to look through the kernel code for keyboard detection > with plans toward having a sysctl that forces the keyboard at run > time, rather than kernel compile. But I got sidetracked. > > Related problems come up so often that I am convinced that such a > fix is required. Me finding time to implement is a problem. > > /\/\ \/\/ > > On Tue, Jan 15, 2002 at 06:21:30PM +1030, Daniel O'Connor wrote: > > I was wondering if there is a flag to force the kernel to detect a PS/2 > > keyboard even if it doesn't detect one. > > > > The usual answer is 'set atkbdc flags to 0x0' but you can't do that if > > you are installing for the first time - when you boot -c the config > > prompt is printed in an infinite loop :( > > > > The newer keyboards I have (Mitsubishi Diamond Touch) do not get detected > > by FreeBSD so every time I need to install from a base CD I have to dig > > up my detectable keyboard and hot swap it after the detection phase. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Force keyboard detection flag?
I started to look through the kernel code for keyboard detection with plans toward having a sysctl that forces the keyboard at run time, rather than kernel compile. But I got sidetracked. Related problems come up so often that I am convinced that such a fix is required. Me finding time to implement is a problem. /\/\ \/\/ On Tue, Jan 15, 2002 at 06:21:30PM +1030, Daniel O'Connor wrote: > I was wondering if there is a flag to force the kernel to detect a PS/2 > keyboard even if it doesn't detect one. > > The usual answer is 'set atkbdc flags to 0x0' but you can't do that if you are > installing for the first time - when you boot -c the config prompt is printed > in an infinite loop :( > > The newer keyboards I have (Mitsubishi Diamond Touch) do not get detected by > FreeBSD so every time I need to install from a base CD I have to dig up my > detectable keyboard and hot swap it after the detection phase. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Using ISO8859 and perl
On Thu, Jan 17, 2002 at 03:32:19PM +0100, Gunnar Flygt wrote:
> When I start pkg_version I get the following startinfo:
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LC_ALL = (unset),
> LC_CTYPE = "sv_SE.ISO8859-1",
> LANG = "sv_SE.ISO8859-1"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
>
> How can I make perl aware of local language settings. Maybe not a
> "stable" question, but since it's the only list I'm connected to :)
>
> But of course the system is -STABLE
Assuming you have recent enough system (so that the sv_SE.ISO8859-1
locale actually exists) you shouldn't have to do anything.
I just tried running pkg_version with LC_ALL, LC_CTYPE and LANG set as
above and I didn't get any warnings at all.
I am running 4.5-RC from Jan 10.
Since that locale name was added fairly recently I suggest to update
your system to the latest -STABLE if you haven't already done so within
the last week or so.
(In case your system doesn't have that locale installed.)
--
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: 4.5-RC1: Why sshd require opie for SSH version 2?
If memory serves me right, Josh Tiefenbach wrote: > > After doing some tests, I found that connecting to this 4.5-RC1 box > > from other machine by OpenSSH (without RSA/DSA key, nor rhost*auth, > > assuming to use plain password to login), requires opie to login, > > though /etc/opiekeys, and /etc/skeykeys are both size 0. If I start > > openssh with flag '-1', which means to use OpenSSH version 1 protocol, > > it works fine: require plain password. I checked 4.4-RELEASE machine, > > and found that it works fine without '-1' flag, and even with '-2', it > > works. [snip] > Perhaps its an OpenSSH v3 thing? If I have some time tonite, I'll go compile > up v3 someplace and check it out. Did you get a chance to do this? I'm unable to reproduce this problem between two RELENG_4 machines running the base system OpenSSH (both machines built within the last three days). Usually I use a DSA keypair to authenticate, but I temporarily blew away ~/.ssh/authorized_keys2 on the server side and ~/ .ssh/id_dsa on the client side. Bruce. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Using ISO8859 and perl
When I start pkg_version I get the following startinfo:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LC_ALL = (unset),
LC_CTYPE = "sv_SE.ISO8859-1",
LANG = "sv_SE.ISO8859-1"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
How can I make perl aware of local language settings. Maybe not a
"stable" question, but since it's the only list I'm connected to :)
But of course the system is -STABLE
--
__o
regards, Gunnar ---_ \<,_
email: [EMAIL PROTECTED] (_)/ (_)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
