openssh-2.9p2, short hostnames

[Nicolas Williams]

On Tue, Oct 02, 2001 at 06:16:07PM +0200, Hans Werner Strube wrote:
> > > While the length of a key's value is 1024 bytes, you can break the
> > > value so it references other *keys* and therefore work around this
> > > limitation. If you generate the NDBM maps directly from text files
> > > though, your kinda screwed unless you somehow automate this process.
> 
> I have already applied this technique before (even for too many short
> host names) but would like to avoid it if possible.

Automate this. It's not hard. Remember, split the netgroups into a
shallow tree of netgroups, not a deep list. Some broken innetgr()
implementations do a depth-first traversal with a depth-limit as an
anti-looping heuristic.

> > The reverse maps are the ones used by innetgr() on Solaris. The reverse
> > maps' keys are named after users and hosts, and the values are
> > comma-separated lists of netgroups the users/hosts belong to.
> > 
> > There's no way to break those up.
> 
> But there is no need to break those up, since those records are quite short.

The hostname being long does not much affect the reverse map entries.
That is true.

But I have certainly seen very, very long reverse map entries.

Nico
--
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.