From owner-freebsd-current@freebsd.org Sat May 14 12:49:48 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CED0FB3949C for ; Sat, 14 May 2016 12:49:48 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 957DD1F5B for ; Sat, 14 May 2016 12:49:48 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-oi0-x22a.google.com with SMTP id v145so208819257oie.0 for ; Sat, 14 May 2016 05:49:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Il2b9ZcoHVS8N7wOJJiQFZfSEKHWoR8ZSc45aYZxrX8=; b=yNuMq2yosHq3HtzTBw31k1Y0LAmQJ3WGG47FhIm1MFwVM4VBNJCEMqlWo5NZS0oNgN 8xEuALV5pwgZ5A2LsiU8HAC8kyorpPBZar1LZ5CBvPUMeqzak1BuRgQ/0oNYgEquoqD1 IMKLV/jOcv8izGRqBlBLtnMevEiR/iMFni9jXJg1z6zqHhJCh+4Rp/G2Zlh/5Isav84a AYpUuwx4GS738e48Mk68NQ3fxUenwoUjttVGQKP7Iae3bzEVEALmeog0EKX8bCwY1eQ7 hHOEZ4x39xGBbxaF4t9jl0UNH99DItoKON+8UORLTUm1suSxwO6AdB7W29hHUSryc+S+ aYcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Il2b9ZcoHVS8N7wOJJiQFZfSEKHWoR8ZSc45aYZxrX8=; b=Qx/IZ34X6LCIaUIIGkYlzOtaOOlq6QuJED6C6SGtc408fUNiepFQo+Cj+Jd+bY+sdP AhSIBhAqOfDNc/wgWW5CrcQ/fh3sOLm6vAyBiaEAWrtT3amyD8pY/GeOpEv7mpFrcbYI ALtftoOLLYdk4XaoyWWOy8YHKdZEm3g8rJ2cROQxjYgtbo9fGy9xBB44DdVeZtFf8nV1 K+n3/S9q5s3VwCiQoE8+laP1exJU8MqvKLKUcnqCtPodM/wePPpjQccEKRCWZrhvgUgM K8mQVL8U6mxEzzHE9VOvvqQs5s8fUIWfaxBwhQwl5FJUcZWEARknzcJQk5b1Y5LgExLn BnPg== X-Gm-Message-State: AOPr4FXu248Fi5VNfzQT7qF7y5YJA+9g6CiiPXZpnAIQKhCO0eiNPBmmyO/v+Mg1Oh0PhcaQfk2FwRFGm26Jow== MIME-Version: 1.0 X-Received: by 10.202.75.78 with SMTP id y75mr11935801oia.70.1463230188016; Sat, 14 May 2016 05:49:48 -0700 (PDT) Received: by 10.157.45.131 with HTTP; Sat, 14 May 2016 05:49:47 -0700 (PDT) In-Reply-To: <5736AE91.7030108@ShaneWare.Biz> References: <5736A988.5020603@ShaneWare.Biz> <5736AE91.7030108@ShaneWare.Biz> Date: Sat, 14 May 2016 05:49:47 -0700 Message-ID: Subject: Re: Issue mentioned on questions list From: Mehmet Erol Sanliturk To: Shane Ambler Cc: FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 May 2016 12:49:48 -0000 On Fri, May 13, 2016 at 9:50 PM, Shane Ambler wrote: > I'm not expecting a reply to this, it was something that come up > discussing building custom kernels. > > Just wondering if someone may be interested in looking at the > possibility of changing username length to a sysctl. > > As the number of people using computers is increasing, it is now > common for web sites/mail servers to use your full email as your > username, keeping that consistent through all username usage doesn't > seem like an unreasonable request. I would expect a username length > sysctl value would only be allowed to be set in the loader.conf at boot > time, similar to zfs.arc_max > > > Over time , I want to generate a FreeBSD live CD/DVD with root/user password entered on boot ( i.e. , no prerecorded passwords ) from a 2D bar code or from a USB stick or from an SD card with sufficiently long length defined in the kernel routines . This feature also may be used for remote logins . Such a long password generated by a program by random character selection from a character alphabet is impossible to estimate . This "password name length" feature may also be considered along side with "user name length" . Mehmet Erol Sanliturk > -------- Forwarded Message -------- > Subject: Re: Custom kernel for NAT and PF ? > Date: Sat, 14 May 2016 13:58:56 +0930 > From: Shane Ambler > To: Doug McIntyre , FreeBSD Questions < > freebsd-questions@freebsd.org> > > On 14/05/2016 04:40, Doug McIntyre wrote: > >> On Fri, May 13, 2016 at 02:04:55PM +0930, Shane Ambler wrote: >> >>> Now you only need to compile a custom kernel if you want to use newer >>>> >>> features. >>> >> ... >> >> Unfortunately, I have two situations where that isn't true. >> >> For the first, I wish that just loading the PPS drivers enabled the >> PPS_SYNC option in the kernel, but it doesn't seem to. (if there is >> a way to enable 'option PPS_SYNC' with a generic kernel I'd like to know, >> but my experients didn't lead me that working. I still have to compile >> the kernel for my GPS connected NTP servers. Which makes me wonder why >> the PPS drivers are a kernel loadable object. >> > > I would report that as a bug and see if it can be improved. > > The second is that the username handling is still limited to 32-bytes, >> which really cramps my logins for ' >> billyjoebobuser@somesillydomainname.com' >> so I have to build a custom kernel with longer usernames patched for >> the systems that need to deal with system logins like that. >> > > While I don't have that issue, it does sound like an old time > limitation that should be considered for rework. Maybe it could be > made into an adjustable sysctl. > > -- > FreeBSD - the place to B...Software Developing > > Shane Ambler > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >