Re: Booting OpenBSD on a HP Compaq Desktop

2018-02-26 Thread Israel Brewster 
On Feb 26, 2018, at 8:10 AM, Stuart Henderson <s...@spacehopper.org> wrote:
> 
> On 2018/02/26 07:50, Israel Brewster wrote:
>>On Feb 24, 2018, at 3:06 AM, Stuart Henderson <s...@spacehopper.org> 
>> wrote:
>> 
>>On 2018-02-24, Israel Brewster <isr...@ravnalaska.net> wrote:
>> 
>>I have an HP Compaq Pro 6300 machine on which I am trying to run
>>OpenBSD. The installer boots and runs fine, but after rebooting into 
>> the
>>newly installed OS, I start getting the boot sequence (the white text 
>> on
>>blue background stuff - don't know what that is officially called), 
>> but
>>after a second or so the screen goes blank and that's all she wrote.
>> 
>>My first thought was that it was just a display issue, and that I
>>should be able to ssh in and tweak stuff, but as it turns out, the
>>machine never shows up on the network, either, so apparently it never
>>gets far enough in the boot process to enable the network (networking
>>*does* work while I am running through the installer, so I don't think
>>it's just a missing network driver there).
>> 
>> 
>>It sounds like it's crashing after the video mode is changed. The
>>machine probably has inteldrm so at the boot loader prompt, try
>>"boot -c", then at UKC "disable inteldrm" and "quit".
>> 
>> 
>> Bingo! that did the trick - got a good clean boot after running that 
>> command. The only issue
>> appears to be that I'm going to have to do that every time I boot. Given 
>> that, how do I make it
>> stick? Or, now that we know that is the issue, is there some other, more 
>> permanent "fix" I can
>> try? Do I need that inteldrm for any reason?
> 
> You'll want it if the machine will be running X.

It won't be. It's role in life is to be a FTP/SFTP server, so no need for X.

> 
> It's possible to modify an on-disk kernel with config(8)'s -e flag, but
> that has other problems (not least, syspatch won't be able to update the
> kernel).

Gotcha. It did work to allow ongoing booting, but I'll keep trying other 
solutions.

> 
>>That may let it boot, if not then you're at least more likely to see
>>a hidden error message of some sort.
>> 
>>If this is 6.2, try -current instead. If it's OpenBSD/i386, try amd64
>>instead.
>> 
>> 
>> Since disabling inteldrm seemed to bypass the issue, if only temporarily, 
>> would these still be
>> worth trying, or were they just additional suggestions if the inteldrm thing 
>> didn't work?
> 
> Definitely worth trying, it would be better to have a fix than a workaround,
> and without trying -current you won't know if it's already been fixed. With
> the information you've given so far we have very little idea about what you're
> running or what hardware.

My apologies, I mean't to mention that, but it slipped my mind (kind of like 
remembering to remove the stupid image signature my boss insists upon). This is 
a brand-new install of OpenBSD 6.2, running on a HP Compaq Pro 6300, stock 
hardware (no add-in cards or the like). 

> 
> Please send a bug report with the files generated from sendbug (run as root).
> It's often easiest to do "sendbug -P > /tmp/template.txt" then copy that to
> another machine, edit to add a description etc, and send the whole thing
> to b...@openbsd.org <mailto:b...@openbsd.org>.

Will do. Thanks!

---
Israel Brewster
Systems Analyst II
Ravn Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7293
---

Re: Booting OpenBSD on a HP Compaq Desktop

2018-02-26 Thread Israel Brewster 
> On Feb 24, 2018, at 3:06 AM, Stuart Henderson <s...@spacehopper.org> wrote:
> 
> On 2018-02-24, Israel Brewster <isr...@ravnalaska.net> wrote:
>> I have an HP Compaq Pro 6300 machine on which I am trying to run
>> OpenBSD. The installer boots and runs fine, but after rebooting into the
>> newly installed OS, I start getting the boot sequence (the white text on
>> blue background stuff - don't know what that is officially called), but
>> after a second or so the screen goes blank and that's all she wrote.
>> 
>> My first thought was that it was just a display issue, and that I
>> should be able to ssh in and tweak stuff, but as it turns out, the
>> machine never shows up on the network, either, so apparently it never
>> gets far enough in the boot process to enable the network (networking
>> *does* work while I am running through the installer, so I don't think
>> it's just a missing network driver there).
> 
> It sounds like it's crashing after the video mode is changed. The
> machine probably has inteldrm so at the boot loader prompt, try
> "boot -c", then at UKC "disable inteldrm" and "quit".

Bingo! that did the trick - got a good clean boot after running that command. 
The only issue appears to be that I'm going to have to do that every time I 
boot. Given that, how do I make it stick? Or, now that we know that is the 
issue, is there some other, more permanent "fix" I can try? Do I need that 
inteldrm for any reason?

> 
> That may let it boot, if not then you're at least more likely to see
> a hidden error message of some sort.
> 
> If this is 6.2, try -current instead. If it's OpenBSD/i386, try amd64
> instead.

Since disabling inteldrm seemed to bypass the issue, if only temporarily, would 
these still be worth trying, or were they just additional suggestions if the 
inteldrm thing didn't work?

---
Israel Brewster
Systems Analyst II
Ravn Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7293
---
> 
>

Booting OpenBSD on a HP Compaq Desktop

2018-02-23 Thread Israel Brewster 
I have an HP Compaq Pro 6300 machine on which I am trying to run OpenBSD. The 
installer boots and runs fine, but after rebooting into the newly installed OS, 
I start getting the boot sequence (the white text on blue background stuff - 
don't know what that is officially called), but after a second or so the screen 
goes blank and that's all she wrote.

My first thought was that it was just a display issue, and that I should be 
able to ssh in and tweak stuff, but as it turns out, the machine never shows up 
on the network, either, so apparently it never gets far enough in the boot 
process to enable the network (networking *does* work while I am running 
through the installer, so I don't think it's just a missing network driver 
there).

What can I do to fix this?

Re: 4G modems for OpenBSD?

2018-01-15 Thread Israel Brewster 


> On Jan 9, 2018, at 11:06 PM, Daniel Gracia <palad...@gmail.com> wrote:
> 
> This scenario is trivial, as far as the Sierra Wireless Airlink supports UDP 
> client/server links. I.e., a properly configurated gateway (easily done 
> through their web interface) should be able to accept UDP packets on any 
> defined port and accept messages in the form 
> '<<<phonenumber,format,length,message>>>', so just using netcat to send the 
> line
> 
> <<<16046556677,ASCII,14,5448495320495320412054455354>>>
> 
> (being the message formatted in hex ASCII, in this case 'THIS IS A TEST') 
> will do the trick. You should receive another UDP packet to a port of your 
> choice ACKing the message. And that's all.
> 
> Regards!
> 
> 

Thanks. Yeah, I saw that in the documentation, and after discussing with my 
coworkers we're thinking this is the way to go. Perhaps a bit pricier than 
other options, but it looks like it could be more useful. The main thing will 
be to work out the code that receives the response such that I can receive both 
ACKs as well as incoming messages (if we decide to do so), but that's what 
makes it fun!

> 
> 2018-01-09 18:03 GMT+01:00 Israel Brewster <isr...@ravnalaska.net 
> <mailto:isr...@ravnalaska.net>>:
> On Jan 9, 2018, at 12:07 AM, Daniel Gracia <palad...@gmail.com 
> <mailto:palad...@gmail.com>> wrote:
>> 
>> Maybe this is not exactly the solution you're looking for, but have you
>> considered using a 4G gateway? In the past I've had great success with
>> Sierra Wireles AirLink family. It's pretty easy to send SMS commands
>> through IP with them, so a local Ethernet connection to the gateway should
>> do the trick. Neat devices!
> 
> Sounds worth checking out. I can always connect it directly via a second 
> ethernet port or the like, so being IP should be fine.
> 
> The main concern is that the machine in question be able to get a message 
> out, even if the switch it is connected to dies. So a little creative 
> networking, and a solution like this should be fine, as long as the SMS 
> commands can be sent from the command line. 
> 
> Thanks!
> 
> ---
> Israel Brewster
> Systems Analyst II
> Ravn Alaska
> 5245 Airport Industrial Rd 
> <https://maps.google.com/?q=5245+Airport+Industrial+RdFairbanks,+AK+99709+(907=gmail=g>
> Fairbanks, AK 99709 
> <https://maps.google.com/?q=5245+Airport+Industrial+RdFairbanks,+AK+99709+(907=gmail=g>
> (907 
> <https://maps.google.com/?q=5245+Airport+Industrial+RdFairbanks,+AK+99709+(907=gmail=g>)
>  450-7293
> ---
>> 
>> Regards,
>> 
>> 
>> 2018-01-09 1:35 GMT+01:00 Israel Brewster <isr...@ravnalaska.net 
>> <mailto:isr...@ravnalaska.net>>:
>> 
>>> Could anyone suggest a USB 4G cell modem model that will work well with
>>> OpenBSD, specifically SMSTools? I've looked over most of the list in "man
>>> umsm", but those all appear to be 3G. That said, I haven't checked every
>>> model on the list, so there could be one or more 4G models that I missed.
>>> I've also seen this thread: http://openbsd-archive.7691 
>>> <http://openbsd-archive.7691/>.
>>> n7.nabble.com/4g-LTE-modem-td106310.html 
>>> <http://n7.nabble.com/4g-LTE-modem-td106310.html> 
>>> <http://openbsd-archive.7691 <http://openbsd-archive.7691/>.
>>> n7.nabble.com/4g-LTE-modem-td106310.html 
>>> <http://n7.nabble.com/4g-LTE-modem-td106310.html>>, but that is over 5 
>>> years old.
>>> There is also this thread: http://openbsd-archive.7691 
>>> <http://openbsd-archive.7691/>.
>>> n7.nabble.com/Anyone-experienced-with-4G-LTE-modems-td281872.html 
>>> <http://n7.nabble.com/Anyone-experienced-with-4G-LTE-modems-td281872.html> <
>>> http://openbsd-archive.7691.n7.nabble.com/Anyone-experienced-with-4G-LTE- 
>>> <http://openbsd-archive.7691.n7.nabble.com/Anyone-experienced-with-4G-LTE->
>>> modems-td281872.html>, but that doesn't appear to offer any suggestions
>>> of USB cell modems - just suggestions of using external cellular routers.
>>> 
>>> I do need a direct USB connection for the purposes of sending SMS messages
>>> directly from the system, i.e. I need to be able to send a SMS even if the
>>> internet is down, so online cloud services or the like that can convert
>>> e-mail to SMS aren't an option. Thanks.
>>> 
>>> ---
>>> Israel Brewster
>>> Systems Analyst II
>>> Ravn Alaska
>>> 5245 Airport Industrial Rd 
>>> <https://maps.google.com/?q=5245+Airport+Industrial+Rd+Fairbanks,+AK+99709+(907=gmail=g>
>>> Fairbanks, AK 99709 
>>> <https://maps.google.com/?q=5245+Airport+Industrial+Rd+Fairbanks,+AK+99709+(907=gmail=g>
>>> (907 
>>> <https://maps.google.com/?q=5245+Airport+Industrial+Rd+Fairbanks,+AK+99709+(907=gmail=g>)
>>>  450-7293
>>> ---
>>> 
>>> 
>>> 
>>> 
>>> 
> 
>

Re: 4G modems for OpenBSD?

2018-01-09 Thread Israel Brewster 
On Jan 9, 2018, at 9:47 AM, Roderick <hru...@gmail.com> wrote:
> 
> 
> 
> On Tue, 9 Jan 2018, Israel Brewster wrote:
> 
>> Well, as I said I'm using SMSTools - it's in ports - comms/smstools. 
>> No special program or extended AT commands, at least not on my end. 
>> I just call the command line "sendsms" that smstools provides. 
>> Easy peasy. I haven't looked at the source to see what it does under 
>> the hood.
> 
> You mean this:
> 
> http://smstools3.kekekasvi.com/
> 
> There you read:
> 
> "This software needs a GSM modem (or mobile phone) with SMS command set 
> according to the european specifications GSM 07.05 (=ETSI TS 300 585) and 
> GSM 03.38 (=ETSI TS 100 900). AT command set is supported."
> 
> And the links I gave you name some commands for sending and receiving
> SMS. And if you want to write a script to talk with the modem, then expect
> is the tool. Do you need concurrency? Many people on a network sending
> SMS through the same modem?

Yep, that's the page. Not sure why I would want to write a script using expect 
to talk to the modem directly though, unless smstools doesn't work for some 
reason. Using smstools, all you have to do is call the command-line "sendsms" 
with the number and the message. Or even just by creating a text file in the 
spool directory. No need for expect or any fancy scripting.

That said, all the references on that page refer to a GSM modem, not a LTE 
modem. My knowledge of cellular protocols is quite limited, but if that's an 
issue, then maybe I would need to use expect or the like to talk to the modem 
directly.

No, I don't need concurrency. Primarily this would just be a backup 
communications channel for our network monitor should it be unable to reach the 
mailserver for any reason. For example, should the switch the network monitor 
box is connected to die, it should still be able to send a SMS notifying of the 
failure. Also, I find that for the more important notifications, SMS gets 
noticed more easily than e-mail. While we may use it occasionally for other 
purposes as well, the total usage will still be quite light, so no need to get 
overly fancy.

---
Israel Brewster
Systems Analyst II
Ravn Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7293
---

> 
> Rodrigo.
>

Re: 4G modems for OpenBSD?

2018-01-09 Thread Israel Brewster 
On Jan 9, 2018, at 12:07 AM, Daniel Gracia <palad...@gmail.com> wrote:
> 
> Maybe this is not exactly the solution you're looking for, but have you
> considered using a 4G gateway? In the past I've had great success with
> Sierra Wireles AirLink family. It's pretty easy to send SMS commands
> through IP with them, so a local Ethernet connection to the gateway should
> do the trick. Neat devices!

Sounds worth checking out. I can always connect it directly via a second 
ethernet port or the like, so being IP should be fine.

The main concern is that the machine in question be able to get a message out, 
even if the switch it is connected to dies. So a little creative networking, 
and a solution like this should be fine, as long as the SMS commands can be 
sent from the command line. 

Thanks!

---
Israel Brewster
Systems Analyst II
Ravn Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7293
---
> 
> Regards,
> 
> 
> 2018-01-09 1:35 GMT+01:00 Israel Brewster <isr...@ravnalaska.net>:
> 
>> Could anyone suggest a USB 4G cell modem model that will work well with
>> OpenBSD, specifically SMSTools? I've looked over most of the list in "man
>> umsm", but those all appear to be 3G. That said, I haven't checked every
>> model on the list, so there could be one or more 4G models that I missed.
>> I've also seen this thread: http://openbsd-archive.7691.
>> n7.nabble.com/4g-LTE-modem-td106310.html <http://openbsd-archive.7691.
>> n7.nabble.com/4g-LTE-modem-td106310.html>, but that is over 5 years old.
>> There is also this thread: http://openbsd-archive.7691.
>> n7.nabble.com/Anyone-experienced-with-4G-LTE-modems-td281872.html <
>> http://openbsd-archive.7691.n7.nabble.com/Anyone-experienced-with-4G-LTE-
>> modems-td281872.html>, but that doesn't appear to offer any suggestions
>> of USB cell modems - just suggestions of using external cellular routers.
>> 
>> I do need a direct USB connection for the purposes of sending SMS messages
>> directly from the system, i.e. I need to be able to send a SMS even if the
>> internet is down, so online cloud services or the like that can convert
>> e-mail to SMS aren't an option. Thanks.
>> 
>> ---
>> Israel Brewster
>> Systems Analyst II
>> Ravn Alaska
>> 5245 Airport Industrial Rd
>> Fairbanks, AK 99709
>> (907) 450-7293
>> ---
>> 
>> 
>> 
>> 
>>

Re: 4G modems for OpenBSD?

2018-01-09 Thread Israel Brewster 


> On Jan 8, 2018, at 10:58 PM, Kirill <nightl...@nightbbs.ru> wrote:
> 
> Try huawei e3276 with patch.
> (http://openbsd-archive.7691.n7.nabble.com/Trouble-with-Huawei-e3276-td241825.html)
> Works for me, but I dont use smstools, just ppp.

As long as it shows up as a comm/serial port, it should work. I'll check it 
out. Thanks.

> 
> On 01/09/18 03:35, Israel Brewster wrote:
>> Could anyone suggest a USB 4G cell modem model that will work well with 
>> OpenBSD, specifically SMSTools? I've looked over most of the list in "man 
>> umsm", but those all appear to be 3G. That said, I haven't checked every 
>> model on the list, so there could be one or more 4G models that I missed. 
>> I've also seen this thread: 
>> http://openbsd-archive.7691.n7.nabble.com/4g-LTE-modem-td106310.html 
>> <http://openbsd-archive.7691.n7.nabble.com/4g-LTE-modem-td106310.html>, but 
>> that is over 5 years old. There is also this thread: 
>> http://openbsd-archive.7691.n7.nabble.com/Anyone-experienced-with-4G-LTE-modems-td281872.html
>>  
>> <http://openbsd-archive.7691.n7.nabble.com/Anyone-experienced-with-4G-LTE-modems-td281872.html>,
>>  but that doesn't appear to offer any suggestions of USB cell modems - just 
>> suggestions of using external cellular routers. 
>> 
>> I do need a direct USB connection for the purposes of sending SMS messages 
>> directly from the system, i.e. I need to be able to send a SMS even if the 
>> internet is down, so online cloud services or the like that can convert 
>> e-mail to SMS aren't an option. Thanks.
>> 
>> ---
>> Israel Brewster
>> Systems Analyst II
>> Ravn Alaska
>> 5245 Airport Industrial Rd
>> Fairbanks, AK 99709
>> (907) 450-7293
>> ---
>> 
>> 
>> 
>> 
>> 
>

Re: 4G modems for OpenBSD?

2018-01-09 Thread Israel Brewster 
On Jan 9, 2018, at 3:16 AM, Christoph R. Murauer  wrote:
> 
> Hello !
> 
>> Could anyone suggest a USB 4G cell modem ...
>> I do need a direct USB connection for the purposes of sending SMS
>> messages directly from the system, ...
> 
> I don't know, if it is what you are looking for but have a look at man
> 4 cdce. I use the listet ZTE MF831.
> 
> Yes, it is connected using USB and it supports 4G / LTE (I have the
> European version) - even it is listed as Ethernet device.
> 
>> i.e. I need to be able to send a SMS even if the internet is down, ...
> 
> The default (you can do that also manually over the web interface)
> setting is, that the device connects automatically to the network of
> the SIM (you don't need a internet connection to send SMS but to your
> phone provider as for all devices to send SMS).
> 
> I also don't know, how you define SMSTools. You can open a web
> browser, connect to the stick using the gateway IP and send and
> recieve SMS (you can also manage kontakts on the SIM).

SMSTools - as in, the program smstools, available in ports/comm/smstools. It 
provides a command line tool called sendsms (as well as other tools) that I can 
call with a phone number and a message to send a SMS. If your suggested 
solution requires a web page for interaction, then as I mention in another 
response it's probably not going to work - I need to be able to script it on 
the command line. Thanks though!

> 
> 
> Regards,
> 
> Christoph
> 
>

Re: 4G modems for OpenBSD?

2018-01-09 Thread Israel Brewster 
On Jan 9, 2018, at 3:20 AM, Roderick <hru...@gmail.com> wrote:
> 
> 
> On Mon, 8 Jan 2018, Israel Brewster wrote:
> 
>> Could anyone suggest a USB 4G cell modem model that will work well with 
>> OpenBSD, specifically SMSTools? I've looked over most of the list in "man 
>> umsm", but those all appear to be 3G. That said, I haven't checked every 
>> model on the list, so there could be one or more 4G models that I missed. 
>> I've also seen this thread: 
>> http://openbsd-archive.7691.n7.nabble.com/4g-LTE-modem-td106310.html 
>> <http://openbsd-archive.7691.n7.nabble.com/4g-LTE-modem-td106310.html>, but 
>> that is over 5 years old. There is also this thread: 
>> http://openbsd-archive.7691.n7.nabble.com/Anyone-experienced-with-4G-LTE-modems-td281872.html
>>  
>> <http://openbsd-archive.7691.n7.nabble.com/Anyone-experienced-with-4G-LTE-modems-td281872.html>,
>>  but that doesn't appear to offer any suggestions of USB cell modems - just 
>> suggestions of using external cellular routers. 
>> 
>> I do need a direct USB connection for the purposes of sending SMS messages 
>> directly from the system, i.e. I need to be able to send a SMS even if the 
>> internet is down, so online cloud services or the like that can convert 
>> e-mail to SMS aren't an option. Thanks.
> 
> External Router: "Globsurfer III" you can send SMS from its cofiguration
> page.

Does that mean web interface? if so, that won't work - I need a scriptable 
command line option. I'll look into it though. Thanks!

> 
> With a modem, you can ask someone here having a 4G modem if it has the
> extended AT commands that your program need.
> But what are these commands?
> I do not know if they are standard. See for example here:

Well, as I said I'm using SMSTools - it's in ports - comms/smstools. No special 
program or extended AT commands, at least not on my end. I just call the 
command line "sendsms" that smstools provides. Easy peasy. I haven't looked at 
the source to see what it does under the hood.

> 
> http://www.smssolutions.net/tutorials/gsm/receivesmsat/
> 
> http://www.smssolutions.net/tutorials/gsm/sendsmsat/
> 
> Perhaps you can write your own script with expect: 
> 
> https://www.tcl.tk/man/expect5.31/expect.1.html
> 
> Rodrigo.
>

4G modems for OpenBSD?

2018-01-08 Thread Israel Brewster 
BEGIN:VCARD
VERSION:3.0
N:Brewster;Israel;;;
FN:Israel Brewster
ORG:Frontier Flying Service;MIS
TITLE:PC Support Tech II
EMAIL;type=INTERNET;type=WORK;type=pref:isr...@frontierflying.com
TEL;type=WORK;type=pref:907-450-7293
item1.ADR;type=WORK;type=pref:;;5245 Airport Industrial Wy;Fairbanks;AK;99701;
item1.X-ABADR:us
CATEGORIES:General
X-ABUID:36305438-95EA-4410-91AB-45D16CABCDDC\:ABPerson
END:VCARD

Re: ypldap 1024 character limit on groups?

2014-03-11 Thread Israel Brewster 
Thanks. I'll see if I can find the time to fix this. It could be a fun project
:-) In the meantime, however, I have determined that CentOS works properly in
this regard, so sadly I'll have to switch, at least for now :-( Thanks for the
feedback, and information as to exactly where the problem lies so I know where
to start looking!

---
Israel Brewster
Computer Support Technician II
Era Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x7293
---

[demime 1.01d removed an attachment of type text/directory which had a name of 
Israel Brewster.vcf]
On Mar 7, 2014, at 8:02 AM, Theo de Raadt dera...@cvs.openbsd.org wrote:

 I see. Wow, that is a HUGE bug.
 
 Such maximum line lengths have been commonplace in Unix forever.  This
 is not an OpenBSD-introduced problem; it is just something that has
 not yet been improved.
 
 Improvements come when people try to push forward along the curve.
 People like you...

Re: ypldap 1024 character limit on groups?

2014-03-07 Thread Israel Brewster 
On Mar 6, 2014, at 3:24 PM, Philip Guenther guent...@gmail.com wrote:

 On Mon, Mar 3, 2014 at 4:14 PM, Israel Brewster isr...@eraalaska.net
wrote:
 I am working on setting up my OpenBSD 5.2 box to connect to my company
LDAP
 server (Mac OS X 10.8.5 OpenDirectory). I have successfully installed
 login_ldap from ports and configured ypldap and the login.conf file such
that
 I can now authenticate as any of my ldap users. However, when ypldap pulls
in
 the group membership information from my LDAP server, it appears to be
cutting
 off the group membership listing at 1024 characters. The end result is
that
 only about half of my users are actually showing up as members of the
 appropriate group(s). I have confirmed this not only by behavior (sftp is
not
 chrooted for some users even though I have the proper entries to match the
 group in sshd_conf), but also by using the userinfo command: userinfo for
a
 user that shows up in the first 1024 characters of the group membership
 listing properly shows the user as a member of the group. userinfo for a
user
 that does not show up in the first 1024 characters show the user as only
being
 part of the default group (staff in this case). How can I get ypldap to
show
 the full member listing?

 The 1024 byte limit is hardcoded in libc's getgr* routines.

 /usr/src/lib/libc/gen/getgrent.c:#defineMAXLINELENGTH   1024
 /usr/src/lib/libc/gen/getgrouplist.c:#define MAXLINELENGTH  1024

 Increasing those would also require an increase to grp.h's _GR_BUF_LEN
 and possibly other places in the tree.  Not tested: good luck!


 Philip Guenther

I see. Wow, that is a HUGE bug. Unless there is some workaround, that
essentially means OpenBSD is not suitable for use in any sort of directory
environment, unless it is very small. I mean, I only have about 300 users in
my directory (about 1/3 of the total company), split between two groups, and
ypldap only shows about 2/3 of each group, or about 100 people. You could
MAYBE manage 200 if you used shorter usernames. But maybe we're just weird,
and no normal company puts more than 100 people in a group :-)

In any case, thanks for the information. I guess I'll start looking at other
OS options. That stinks - I like OpenBSD.
---
Israel Brewster
Computer Support Technician II
Era Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x7293
---

[demime 1.01d removed an attachment of type text/directory which had a name of 
Israel Brewster.vcf]

Re: ypldap 1024 character limit on groups?

2014-03-06 Thread Israel Brewster 
On Mar 3, 2014, at 3:14 PM, Israel Brewster isr...@eraalaska.net wrote:

 I am working on setting up my OpenBSD 5.2 box to connect to my company LDAP
 server (Mac OS X 10.8.5 OpenDirectory). I have successfully installed
 login_ldap from ports and configured ypldap and the login.conf file such
that
 I can now authenticate as any of my ldap users. However, when ypldap pulls
in
 the group membership information from my LDAP server, it appears to be
cutting
 off the group membership listing at 1024 characters. The end result is that
 only about half of my users are actually showing up as members of the
 appropriate group(s). I have confirmed this not only by behavior (sftp is
not
 chrooted for some users even though I have the proper entries to match the
 group in sshd_conf), but also by using the userinfo command: userinfo for a
 user that shows up in the first 1024 characters of the group membership
 listing properly shows the user as a member of the group. userinfo for a
user
 that does not show up in the first 1024 characters show the user as only
being
 part of the default group (staff in this case). How can I get ypldap to
show
 the full member listing?
 ---
 Israel Brewster
 Computer Support Technician II
 Era Alaska
 5245 Airport Industrial Rd
 Fairbanks, AK 99709
 (907) 450-7250 x7293
 ---


I was thinking: is there any chance this is due to a problem with the Apple
OpenDirectory LDAP, and not with ypldap? When I use a LDAB browser such as
explorer, it shows all the groups, but perhaps it works differently. Any
suggestions would be appreciated, as right now the LDAP binding is useless,
and if I can't get this working I'll have to start over on a different OS
where I can make this work - which will not be fun :-(. Thanks.

---
Israel Brewster
Computer Support Technician II
Era Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x7293
---

[demime 1.01d removed an attachment of type text/directory which had a name of 
Israel Brewster.vcf]

ypldap 1024 character limit on groups?

2014-03-03 Thread Israel Brewster 
I am working on setting up my OpenBSD 5.2 box to connect to my company LDAP
server (Mac OS X 10.8.5 OpenDirectory). I have successfully installed
login_ldap from ports and configured ypldap and the login.conf file such that
I can now authenticate as any of my ldap users. However, when ypldap pulls in
the group membership information from my LDAP server, it appears to be cutting
off the group membership listing at 1024 characters. The end result is that
only about half of my users are actually showing up as members of the
appropriate group(s). I have confirmed this not only by behavior (sftp is not
chrooted for some users even though I have the proper entries to match the
group in sshd_conf), but also by using the userinfo command: userinfo for a
user that shows up in the first 1024 characters of the group membership
listing properly shows the user as a member of the group. userinfo for a user
that does not show up in the first 1024 characters show the user as only being
part of the default group (staff in this case). How can I get ypldap to show
the full member listing?
---
Israel Brewster
Computer Support Technician II
Era Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7250 x7293
---