HDTenEightyP/NetNews huggingface dataset:
From: harvard!scubed!riipsdev.waterloo.ncr.com!ajlill@EDDIE.MIT.EDU (Tony Lill)
Subject: Re: Porting problems in V5
Organization: Internet-USENET Gateway at Stanford University
Date: Mon, 4 Jan 1993 15:04:04 GMT

>> In article <9212082146.AA07100@riipsdev.waterloo.ncr.com> harvard!scubed!riipsdev.waterloo.ncr.com!ajlill@eddie.mit.edu writes:
>> >For those of you lucky enough not to have dealt extensively with DOS don't
>> >know, the DOS time() call returns the number of seconds since midnight, Dec
>> >31, 1899, rather than Jan 1, 1970.
>> 
>> That's strange.  Every DOS C compiler I've used returns seconds since
>> Jan. 1, 1970.  The only time I've seen something based on 1899/1900
>> was in code that queried a time server for the time.  time()'s very
>> definition depends on the Unix epoch of 1/1/70.

Surprise! In C 7.0, they changed the definition of time. 

>> No matter what, you have the right solution, I think.  A better solution,
>> if possible, would be to fix the offset used by your time() call.

Yes, after trying to make Kerberos work with this weird definition of
time, I've found that for the decrypt integrity checks (as written) to
work depends on both machines using the same epoch to encode time 0,
so I'll be changing krb5_timestamp to offset it. I've already provided
my own gmtime since the one in the Windows 3.1 SDK libraries is sooooo
broken, it's not funny (they don't even have a large model object in
the large model library!).

Windows/NT the death of UNIX? At least UNIX knows what time it is!

>> >Pepsy (from isode 8.0) turns that into an int when it creates it's
>> >tables.
>> 
>> That's a bug in Pepsy-on-DOS, or Pepsy-on-PDP-11 for that matter.  :-)
>> Someone did a port of ISODE to DOS a while back.  You might see if you
>> can find that port, since the Pepsy there probably has this bug fixed.

Actually, that problem turned out to be a bug in int2prim() or
something not getting what was expected in 0x1ff<<24. (Hint: this is 0
on a 16 bit machine).

- ---
Tony Lill,                                 Tony.Lill@Waterloo.NCR.COM
President, A. J. Lill Consultants                 (519) 650 0660
539 Grand Valley Dr., Cambridge, Ont.             (519) 653 9732
presently at E&M Waterloo, NCR Canada Ltd.        (519) 884 1710 x624
					     voice plus 643 1624

"Welcome to All Things UNIX, where if it's not UNIX, it's CRAP!"
From: paul@kuhub.cc.ukans.edu
Newsgroups: comp.protocols.kerberos
Subject: Kerberos capable PC/Mac telnet clients?
Date: 5 Jan 93 12:08:47 CST
Organization: University of Kansas Academic Computing Services

Anyone know of any Kerberos capable PC/Mac shareware Telnet clients?
We currently run Mac tcp, NCSA Telnet, CUTCP clients for our various
single user platforms. Thank you!
Newsgroups: comp.protocols.kerberos
From: jmcarli@srv.PacBell.COM (Jerry M. Carlin)
Subject: Re: Are there any MVS implementations?
Organization: Pacific * Bell
Date: Wed, 6 Jan 1993 16:37:14 GMT

In article <1429@blue.cis.pitt.edu> gaf+@pitt.edu (Jerry A Flotta) writes:
>  Is there a current implementation of Kerberos in any flavor, that will 
>support IBM's MVS operating system?  Further, does any Kerberos support
>or have "hooks" into any MVS security package like ACF2, RACF or TOPSECRET? 

IBM's TCP/IP on MVS includes Kerberos V4. IBM has announced that OSF DCE
will run on MVS.
-- 
Jerry M. Carlin	(510) 823-2441 jmcarli@srv.pacbell.com
Alchemical Engineer and Virtual Realist
Newsgroups: comp.protocols.kerberos
From: jk@teal.csn.org (John Kranz)
Subject: Kerberos Primer Needed
Organization: Colorado SuperNet, Inc.
Distribution: na
Date: Fri, 8 Jan 1993 17:40:53 GMT

I wondered if someone could recommend a good ground level
introduction to Kerberos for someone who has been asked to
"look into it." 

Any help would be greatly appreciated. (Is there an FAQ for 
this group?)

e-mail to: jk@spectra.wali.com
I'd be happy to summarize.

Newsgroups: comp.protocols.kerberos
From: rubin@EECS.UMICH.EDU (Aviel Rubin)
Subject: Slave servers in Kerberos
Organization: Internet-USENET Gateway at Stanford University
Date: Mon, 11 Jan 1993 20:52:46 GMT

In the operations manual, the section 4. Setting up
and testing slave server(s) says,
"Unfortunately, this chapter is not yet read. SOrry.

Has anyone written this chapter yet, or have the information?
Newsgroups: comp.protocols.kerberos
From: vvawh@convx1.lerc.nasa.gov (Tony Hackenberg)
Subject: List of platforms kerberos successfully ported to? FAQ
Followup-To: vvawh@convx1.lerc.nasa.gov
Keywords: kerberos ports listing
Organization: NASA Lewis Research Center
Distribution: usa
Date: Mon, 11 Jan 1993 23:33:25 GMT


Does anybody have a list of platforms (machines and operating system levels)
that kerberos has been successfully ported to (and ideally the source of 
those ports)?

Maybe there is a FAQ for this group with this info in it? 

I'm particularly interested in the kerberos status on the following
platforms:

	CRAY XMP (UNICOS operating system level 6.1);  
	CRAY YMP (UNICOS operating system level 6.1);
	Convex C220 (Convex operating system level 10.x);


Thanks,
Tony
-- 
Tony Hackenberg
NASA/Lewis Research Center M.S.142-2, 21000 Brookpark Rd., Cleveland, OH 44135
Internet: vvawh@convx1.lerc.nasa.gov  Phone: (216) 433-5201 (work)
Opinions are mine & do NOT represent any official position by my employer.
From: jik@athena.mit.edu (Jonathan I. Kamens)
Newsgroups: comp.protocols.kerberos
Subject: V5 kinit patch: signal error if extra arguments
Date: 6 Jan 1993 20:58:39 GMT
Organization: Massachusetts Institute of Technology
Distribution: world
NNTP-Posting-Host: pit-manager.mit.edu

V5 kinit ignores any arguments after the principal.  It should report an error.
(because they're probably there because the person running the program put the
arguments in the wrong order and needs to know about it).

This patch won't apply if you haven't applied Barry Jaspan's patch to add
ksrvtgt functionality to kinit, but you can apply it by hand because it's
obvious.


*** 5.24        1992/12/24 21:32:16
--- kinit.c     1993/01/06 20:54:16
***************
*** 155,160 ****
--- 155,166 ----
        }
      }
  
+     if (argc - optind > 1) {  /* extra arguments */
+        fprintf(stderr, "Extra arguments (starting with \"%s\").\n",
+                argv[optind+1]);
+        errflg++;
+     }
+        
      if (errflg) {
        fprintf(stderr, "Usage: %s [-r time] [-puf] [-l lifetime] [-c cachename] [-k] [-t keytab] [principal]\n", argv[0]);
        exit(2);

-- 
Jonathan Kamens                                         jik@MIT.Edu
Aktis, Inc.                                 Moderator, news.answers
Newsgroups: comp.protocols.kerberos
From: fielding@theory.TC.Cornell.EDU (David L. Fielding)
Subject: Installing version 4 on SunOS 4.1.2
Organization: Cornell Theory Center
Date: Fri, 8 Jan 1993 19:47:58 GMT

Hello,

	I have ftp'd the kerberos version 4 software and am trying to make it on a Sun Sparc 2 running 4.1.2, with little luck. I followed
the installation notes dating from 1989, but these don't seem to work
in my case. If someone knows about installing kerberos on SunOS 4.1.2
I would greatly appreciate communicating withhearing from you. If there 
are notes somewhere describing details for SunOS installation let me
know.
THANKS
-- 
David L. Fielding			fielding@theory.tc.cornell.edu
Cornell Information Technologies
502 Olin Library		     Phone:(607)273-8664 or
Cornell University, Ithaca, NY 14853 Phone:(607)255-9098 Fax:(607)255-9346
From: ljd2@roger.gte.com (Leonard D'Alotto)
Newsgroups: comp.protocols.iso.x400
Subject: MIME
Summary: Help finding information
Date: 6 Jan 93 21:46:32 GMT
Organization: GTE Laboratories

I have been asked to learn about, and become conversant about, something
called MIME(?).  I haven't a clue as to what it is, but it is supposedly
some type of multimedia messaging standard, system, ow whatever.  It
fell on me as I happen to know a little about X.400.  If anyone can
point me in the right direction for gaining knowledge on this subject,
it would be appreciated.

Len D'Alotto
GTE Laboratories
Waltham, MA  USA
ljd2@gte.com
From: /PN=Thomas.K.Hinders/OU=CCMAIL/O=CHAN.IS/PRMD=MMC/ADMD=TELEMAIL/C=US/@sprint.com
Subject: Thanks and the "I" field
Newsgroups: comp.protocols.iso.x400
X-Message-Id: <"520907070193"*/PN=Thomas.K.Hinders/OU=CCMAIL/O=CHAN.IS/PRMD=MMC/ADMD=TELEMAIL/C=US/@sprint.com>
Date: 7 Jan 93 21:57:31 GMT

    Can I get a "vote" on what info is supposed to be in the "I" field, for
    both 1984 and 1988.

    I believe that the 1988 standard requires that the "I" field contain
    the first letter of all PN fields except the S.

    Therefore, with my PN being Thomas K Hinders, the G, S, and I fields
    would be:

    1984-
    G=Thomas S=Hinders I=K

    1988-
    G=Thomas S=Hinders I=TK

    Am I right on this?

    Also, many thanks to those who responded to my request for help
    concerning employment opportunities.  If you did not receive a reply
    from me, please re-post.

                                Thomas K Hinders
                       Martin Marietta Computing Standards
                             4795 Meadow Wood Lane
                               Chantilly, VA 22021
                        703.802.5593 (v) 703.802.5218 (f)

Newsgroups: comp.protocols.iso.x400
From: whyman@mwassocs.demon.co.uk (Tony Whyman)
Subject: Re: The "I" field 
Distribution: world
Organization: McCallum Whyman Associates Ltd
Reply-To: whyman@mwassocs.demon.co.uk
X-Mailer: Simple NEWS 1.90 (ka9q DIS 1.19)
Date: Mon, 11 Jan 1993 15:08:11 +0000

In article <1993Jan10.120626.11429W@lumina.edb.tih.no> ketil@edb.tih.no writes:

>I didn't take time to read the entire X.400, so I may have overlooked
>something. X.402, 18.3.12 c) identifies "the initials of all his names
>but his surname" as an optional piece of information out of the four 
>that makes up a personal-name. So it looks as if - in principle - the
>initial of the Givenname should be included. 
>
The clause is not as precisely written as it could be. The text reads:

"The value of a personal-name comprises the following four pieces of
information, the first mandatory, the others optional:

a) The person's surname

b) The person's given name

c) The initials of all his names, but his surname.

d) His generation (e.g. "Jr")."

As it stands, it an undeniably sexist and WASP view of the world, and probably
ought to be challenged. However, the statement is clear as it stands. It is 
the INITIALS parameter that is optional, but if present, the requirement is
clear - all the initials except the last.

This is not a trivial discussion. Implementors should validate O/R Addresses
for correctness. It is a good way of checking for errors and avoiding
mis-delivery. I would expect many implementations (including MTAs) to check
the above, and to invalidate O/R Addresses that include both a Given Name 
and Initials, and to non-deliver when the first letter of the initials is
not the same as the first letter of the given name.


-- 
Tony Whyman             McCallum Whyman Associates      Tel +44 962 735580
                                                        FAX +44 962 735581
                        Internet: whyman@mwassocs.demon.co.uk
                        Compuserve: 100041,315
From: pcl@pegasus.att.com ("Paul C. Lustgarten")
Subject: Re: Asynchronous Protocol Specification Aliance - any one heard of it?
Content-Length: 644
Content-Type: text
Newsgroups: comp.protocols.iso.x400
Date: 4 Jan 93 07:50:28 GMT

Andrew,

A short blurb on p. 2 of the 26 October issue of "Network World"
gives a (U.S.) contact number for the Asynchronous Protocol
Specification Alliance of 310 472 1055.  The article says little more
than to basically repeat the description you gave, that it's a forum
for "developing a standard means for X.400 communications over dial-up
lines".

Although we (AT&T EasyLink Services) are also a member of the Alliance,
I personally am not closely enough involved to try to represent their
objectives or current status.  Maybe one of those involved in convening
the Alliance could say more . . .

	Paul Lustgarten
	AT&T EasyLink Services
From: chun@cote.etri.re.kr (Woojik Chun)
Subject: Looking for Estelle Specification of MHS '84/`88
Newsgroups: comp.protocols.iso.x400
Date: 9 Jan 93 01:18:49 GMT


I am a researcher working for ETRI, Korea.
I am going to implement MHS '88.

Is there Estelle specification of MHS '88 or '84?
If you have information about this, please let me know.

My E-mail address is :
	chun@cote.etri.re.kr

Thanks in advance.
Newsgroups: comp.protocols.iso.x400
From: ketil@edb.tih.no (Ketil Albertsen,TIH)
Subject: Re: The "I" field 
Organization: T I H / T I S I P 
Posting-Front-End: Winix Conference v 92.05.15  1.20 (running under MS-Windows)
Date: Tue, 12 Jan 1993 07:41:27 GMT

In article <726764891snz@mwassocs.demon.co.uk>, whyman@mwassocs.demon.co.uk 
(Tony Whyman) writes:

[...]
>The clause is not as precisely written as it could be. The text reads:
>
>"The value of a personal-name comprises the following four pieces of
>information, the first mandatory, the others optional:
>
>a) The person's surname
>
>b) The person's given name
>
>c) The initials of all his names, but his surname.
>
>d) His generation (e.g. "Jr")."
>
>As it stands, it an undeniably sexist and WASP view of the world, and probably
>ought to be challenged. However, the statement is clear as it stands. It is 
>the INITIALS parameter that is optional, but if present, the requirement is
>clear - all the initials except the last.

Sorry, you lost me. How can the statement "the first [piece] mandatory,
the others optional" justify the conclusion "It is the INITIALS parameter
that is optional" ? (That is, with emphasis on "initials")

Are you saying that "The person's given name" and "His generation 
(e.g. "Jr")" is any less optional than the initials information?

To me it is 100% clear that the surname is mandatory, the given name
optional, the initials optional, the generation optional. Am I wrong?

K.Albertsen
Newsgroups: comp.protocols.iso.x400
From: whyman@mwassocs.demon.co.uk (Tony Whyman)
Subject: Re: Thanks and the "I" field 
Distribution: world
Organization: McCallum Whyman Associates Ltd
Reply-To: whyman@mwassocs.demon.co.uk
X-Mailer: Simple NEWS 1.90 (ka9q DIS 1.19)
Date: Fri, 8 Jan 1993 14:46:06 +0000

In article <1993Jan8.111416.24490@ugle.unit.no> harald.alvestrand@delab.sintef.no writes:

>The recommendation to include the first letter of the G when the G is used
>is silly. Ignore it.
>-- 
>                   Harald Tveit Alvestrand
>Harald.Alvestrand@delab.sintef.no
>C=no;PRMD=uninett;O=sintef;OU=delab;S=alvestrand;G=harald
>+47 7 59 70 94

Yes, it is silly, but if you implement the standard ignoring it then a 
conformance tester may label your implementation as non-comformant. If
you really think it should be ignored then please send a defect report to 
the CCITT.

-- 
Tony Whyman             McCallum Whyman Associates      Tel +44 962 735580
                                                        FAX +44 962 735581
                        Internet: whyman@mwassocs.demon.co.uk
                        Compuserve: 100041,315
From: Stef@nma.com (Einar Stefferud)
Subject: Re: MIME
In-reply-to: Your message of 06 Jan 1993 21:46:32 +0000.
 <5227@ceylon.gte.com>
Newsgroups: comp.protocols.iso.x400
Reply-To: Stef@nma.com
Date: 7 Jan 93 02:47:04 GMT

Here is Another source of the information that you seek about MIME.

        author  =       Marshall T. Rose,
        title   =       "{The Internet Message:
                          Closing the Book with Electronic Mail}",
        publisher=      {Prentice-Hall},
        address =       {Englewood Cliffs, New Jersey},
        series  =       {Prentice Hall Series in Innovative Computing},
        year    =       1992,
        note    =       {ISBN 0--13--092941--7}

Enjoy...\Stef
From: /PN=Thomas.K.Hinders/OU=CCMAIL/O=CHAN.IS/PRMD=MMC/ADMD=TELEMAIL/C=US/@sprint.com
Subject: Seasons Greetings....and help!
Newsgroups: comp.protocols.iso.x400
X-Message-Id: <"104513241292"*/PN=Thomas.K.Hinders/OU=CCMAIL/O=CHAN.IS/PRMD=MMC/ADMD=TELEMAIL/C=US/@sprint.com>
Date: 4 Jan 93 16:28:21 GMT

    First, to all those on the 'net...I wish happy holidays and a
    prosperous new year.

    This mailing list has been the source of many answers to questions that
    I have posed, and very little "flaming".

    Now for my latest request......

    I have just been informed that our group (Computing Standards) is being
    disbanded, and that we will receive layoff notices the first part of
    Jan.

    I am seeking opportunities in the E-mail environment.  I have a strong
    background in LAN based E-Mail (Novell and overseeing a 6000+ cc:Mail
    installation) and X400 (operating a Retix X400 MTA).

    I manage the Computing Standards Lab for Martin Marietta, where we
    perform evaluations, testing and benchmarking of standard products used
    by Martin Marietta.  For a flavor of Computing Standards, check out the
    premier issue of Corp. Computing or Dec's issue of NetWork Computing.
    The lab is featured in both.

    My first choice would be in sales or sales support for an E-Mail vendor
    (I am pursuing opportunities with Lotus/cc:Mail), or operating a large
    multi-mail installation.

    I would be willing to relocate in the US or oversees.

    Of course I have more info in my resume, if anyone has any
    suggestions/leads, please reply to me via E-mail or at:

                                Thomas K Hinders
                       Martin Marietta Computing Standards
                             4795 Meadow Wood Lane
                               Chantilly, VA 22021
                        703.802.5593 (v) 703.802.5027 (f)
                                 301.681.7152 (h)

    Thanks...in advance

Newsgroups: comp.protocols.iso.x400
From: traceyw@microsoft.com (Tracey Waszkiewicz)
Subject: ject: Request for mailing address
Date: 11 Jan 93 18:50:07 GMT
Organization: Microsoft Corp.
Keywords: x.400

A friend of mine lacking net access would like to know if there is a mailing
address for this group.  I do not read this group regularly, so I would
appreciate a response via e-mail.  Thanks in advance!

Tracey Waszkiewicz
traceyw@microsoft.comp
From: dougv@vnet.ibm.com (Doug Valkenaar)
Date: Thu, 7 Jan 93 13:48:31 PST
Newsgroups: comp.protocols.iso.x400
Subject: Wanted: x.400 protocol exchange analyzer
Reply-To: dougv@vnet.ibm.com
Organization: ROLM
Disclaimer: This posting represents the poster's views, not those of IBM
News-Software: UReply 3.0

I am looking for an analyzer to monitor x.400 protocol exchange.  I
would appreciate any references anyone could provide.  Also, if anyone
has had experience with such an analyzer, good or bad, I would
appreciate your comments.

Thanks,
Jeanne Ichnowski
ROLM Systems
4900 Old Ironsides Drive,  MS 1206
Santa Clara, CA 95052
Newsgroups: comp.protocols.iso.x400
From: ajw@squid.mel.dit.CSIRO.AU (Andrew Waugh)
Subject: Re: The "I" field
Organization: CSIRO, Division of Information Technology, Melbourne
Date: Mon, 11 Jan 93 23:12:20 GMT

In article <9301111916.AA18613@gateway.mitre.org> epg@gateway.mitre.org ("Ella P. Gardner") writes:
>The 1992 edition of the Directory standard has an initials attribute type.
>The editor's draft of part 6 from the October 1991 Orlando meeting says:
>
>The Initials attribute type contains the initials of some or all of an
>individual's names, but not the surname(s),
>An attribute value for Initials is a string, e.g. "D" or "D." or "J.P."

Damn. And I thought X.500 had avoided all the nonsense that plague
X.400 O/R addresses.

I'd be interested in arguments _for_ the provision of an 'initial'
attribute and the benefits the provision of this attribute is expected
to provide.

The basic argument _against_ is that the structure of human names
varies so much from society to society that attempting to split the
name into components is a pointless exercise. Even the provision of
'surname' is not necessarily useful in all cultures. In Indonesia,
for example, it is apparently common to have only one name, and not
to have a surname (or equivalent). (Source: 'Naming Systems of Ethnic
Groups', Dept. of Social Security, Australia).

By providing attributes to store naming components, two things occur.

First, databases are designed assuming that such fields always occur.
The same DSS book, for example, suggests that when an Indonesian name
without a surname is entered into their computer system, the name
should be entered into the family name field and a title (e.g. 'Mr')
should be entered into the given name field and the title field should
be blank.

Second, software will be written that assumes that naming components
have certain relationships. An example: that the surname always
occurs last (a quick search of the DSS book shows just how frequently
this assumption -- common in Anglo-Saxon communities -- is wrong).

Finally, if we are going to have an attribute to store one type of
name component, why not other types? The sex indicator in Vietnamese
names or the generational name in Chinese names, for example.

Name components just open up a whole can of worms for little or no
benefit as far as I can see.

Andrew Waugh
From: jpalme@dsv.su.se (Jacob Palme DSV)
Subject: MATCHES FOR EQUALITY on OR-names
Newsgroups: comp.protocols.iso.x400
X400-Received: by /PRMD=SUNET/ADMD=_/C=SE/;
	Relayed; 04 Jan 93 12:31:04+0100
Date: 4 Jan 93 11:41:11 GMT

The Message Store standard (X.413) has a search command which uses
filters in the same format as in X.500.

I am wondering how "MATCHES FOR EQUALITY" is interpreted in such
filters for OR-names?

A minimum might be to accept those differences which are equivalent
according to X.402 clause 18.4, which specifies that attributes
of OR-addresses can be equivalent even if one of them is in
"Printable string" and the other in "Teletex String". Also, upper
and lower cases match, and the same country is equivalent if
it is given in the alphabetical or numerical form, and leading
and trailing spaces are insignifant.

In addition to this, an OR-name might contain only a directory
name, or only an OR-address, or both, and will still refer to
the same UA. Should such OR-names be considered equivalent in
Message Store searches?

Finally, some functional standards specify that you should be able
to omit some elements of OR-addresses, for example OU-s which
are not necessary to uniquely identifiy one UA. Should a filter
search in the Message Store then also regard two OR-names
are equivalent even if some superfluous OU-s are omitted
from one of them?

Xref: sparky comp.protocols.iso.x400:757 comp.mail.mime:90
From: 9999sc01@uhdvx3.dt.uh.edu (Alexandre Khalil)
Newsgroups: comp.protocols.iso.x400,comp.mail.mime
Subject: Re: MIME
Date: 10 Jan 1993 01:02 CST
Organization: University of Houston-Downtown
Distribution: world
NNTP-Posting-Host: uhdvx3.dt.uh.edu
Summary: Help finding information
News-Software: VAX/VMS VNEWS 1.41A   

In article <5227@ceylon.gte.com>, ljd2@roger.gte.com (Leonard D'Alotto) writes...
>I have been asked to learn about, and become conversant about, something
>called MIME(?).  I haven't a clue as to what it is, but it is supposedly
>some type of multimedia messaging standard, system, ow whatever.  It
>fell on me as I happen to know a little about X.400.  If anyone can
>point me in the right direction for gaining knowledge on this subject,
>it would be appreciated.

There is a newsgroup called comp.mail.mime : it is a little more than a 
month old, with a FAQ in the make.

>Len D'Alotto
>GTE Laboratories
>Waltham, MA  USA
>ljd2@gte.com

  Happy hacking

alex khalil
U. of Houston-Downtown
alex@dt.uh.edu