HDTenEightyP/NetNews huggingface dataset:
From: root@SNOWHITE.CIS.UOGUELPH.CA (gopher I)
Subject: Kerberized NFS in 4.4BSD
Organization: Internet-USENET Gateway at Stanford University
Date: Wed, 7 Oct 1992 15:59:48 GMT

There is an experimental Kerberized NFS over TCP transport in the 4.4BSD
distribution, that is unfortunately incompatible with all the others
(more on that later) and which functions roughly as follows:

- a cache of client uid --> server credentials is maintained on the server
  for each client mount TCP connection for a Kerberized mount point

- when a client RPC for a uid not in the cache is received (the cache is
  initially empty at mount time), an authentication failed is replied back
  to the client
  - the client then gets a Kerberos ticket for service rcmd for the user and
    sends that to the server along with the client uid in a retry of the RPC
  - the server verifies the ticket and if ok does a getpwnam() etc. to
    build a set of server credentials for that client uid and caches them

- the cache is thrown away whenever the TCP connection is lost

- the basic assumption is that a TCP connection is a "good enough"
  mechanism to subvert replay attempts

To do something similar over UDP, (which my hunch is is what Sun does, I haven't
seen any spec)
a mechanism such as an encrypted timestamp on every RPC request would be required
to subvert replay attempts along with a relatively short expiry timeout on
the server cache entries, so that they wouldn't get too stale.

The choice of this incompatible design was necessitated mostly by politics
beyond my control:

- Due to the export restrictions, CSRG did not want any DES encryption routines
  or even calls to them in the kernel. (for the above, the tickets are
  acquired and verified by calls to the standard Kerberos IV library routines
  by the mount_nfs and nfsd processes which temporarily exit the kernel to
  make the library calls.) This seemed to make any mechanism for UDP impractical.

- Sun has not published the spec. for its variant, although I suspect that
  it would require DES in the kernel anyhow.

- The specification of the MIT mechanism is not public either. My
  understanding is that MIT logs all requests for the info. for Sun and that
  this suggests that Sun considers some of the provided code/info proprietary.
  (I developed my NFS implementation "clean", without having ever seen any
   Sun sources and it was felt that getting the info. from MIT might actually
   "soil" me and therefore not worth the risk.) It might also be observed
  that the MIT mechanism is not ideal, but simply the best they could do
  without making NFS protocol modifications.

I hope this is of some interest, rick
ps: In case you wondered, Canada has a general exemption of the requirement
    for an export permit for DES encryption and as such it is perfectly legal
    for me to have full Kerberos sources. (see: Title #22, Code of Federal
    Regulations "International Traffic in Arms Regulations", Section 126.5)
Newsgroups: comp.protocols.kerberos
From: husemann@camelot.informatik.uni-erlangen.de (Dirk Husemann)
Subject: Why call DES routines directly? (was Re: Kerberos DES <> MD5)
Organization: CSD., University of Erlangen
Date: Thu, 8 Oct 1992 20:57:22 GMT

kaufman@kibitz.enet.dec.com (Charlie Kaufman) writes:

>>I believe that MD5 is patented by RSADSI in the US of A.  It may be used
>>only under license from RSADSI in this country.

>MD5 may or may not be patented, but in any case RSADSI has made it
>freely useable without payment of royalties (unlike the RSA algorithm
>itself).  The notice in the model code in RFC 1321 includes the following text:
...

>Encryption used for data integrity protection (either via DES or MD5)
>is easier to license for export than encryption used for data privacy. 
>But if you use MD5 for data privacy (which is possible but
>cryptographically unproven), you're in the same soup.

>It is possible to remove encryption for privacy from Kerberos and get a
>fairly general export license.  Digital has done so with Kerberos V4. 
>Unfortunately, that is not the same as freely distributable and - at
>least in our case - part of the price was not distributing source code.
> It did not require removal of DES.

Why do we need to make calls to DES directly? Why not call a routine hurzit() or
dehurzit() that is defined in a header file 

	(a)	US: calling des_encode() (or something like it) or des_decode
	(b)	Non-US: just calling a routine that does nothing

As there is a crypt.c (DES) implementation available with the GNU libc which 
has been done outside the US (in Denmark if I'm not mistaken) we (i.e. those
of us outside the US) could then easily substitute the appropriate routines
and make the SW available again (which of course could be imported to the US
--- but not exported again ... You may stop weeping now)


	Dirk Husemann
---

Newsgroups: comp.protocols.kerberos
From: ddavis@WORLD.STD.COM (Don T Davis)
Subject: Re: Kerberized NFS
Organization: Internet-USENET Gateway at Stanford University
Date: Thu, 8 Oct 1992 22:14:41 GMT

Sun sales told me in september that solaris 2.0 will support krb as an alternative
to secure rpc, but krb itself will not be included in the release. you have to
slap the krb code in yourself, after you've gotten it elsewhere.
						-don davis
						 geer zolot associates
						 200 portland st. boston 02114
Newsgroups: comp.protocols.kerberos
From: hendrick@neptune.ctron.com (Jim Hendrick)
Subject: Possible problem with rsh
Organization: Internet-USENET Gateway at Stanford University
Date: Wed, 7 Oct 1992 13:23:06 GMT

Hi,
	I have encountered a possible problem with the kerberized version
of rsh (latest sources as of a week ago) compiled on a SPARC IPX running
SunOS4.1.2 It seems that the parameters may not be being properly passed through
to the /usr/ucb/rsh.ucb. A simple test case illustrates:

#!/bin/ksh

host=altair

rsh -n $host "\cd /user/altair1;df"

It fails with the error:

hendrick@truck:/user/neptune/hendrick
6>>./test
-n: unknown host
rsh: Kerberos rcmd failed: rcmd protocol failure.
trying normal rsh (/usr/ucb/rsh.ucb)
-n: unknown host
hendrick@truck:/user/neptune/hendrick
7>>


yet when I either: remove the -n option or replace the kerberized version
with the original, it works fine. Is this a known problem? Is there a fix for
it? The kerberos man page for rsh says it supports this ( -n ) option.

Thanks for any help.

Jim
From: mamros@athena.lkg.dec.com (Shawn Mamros)
Newsgroups: comp.protocols.kerberos
Subject: Re: Possible problem with rsh
Date: 7 Oct 92 19:15:04 GMT
Reply-To: mamros@athena.lkg.dec.com (Shawn Mamros)
Organization: Digital Equipment Corporation


The -n flag for rsh has to come AFTER the host argument.
Matter of fact, the arguments must be placed in the exact same order as
what the man page lists - the argument parsing is fairly crude...

-Shawn Mamros
E-mail to: mamros@athena.lkg.dec.com
From: ysjae@korea.hp.com (Young Shin JAE)
Subject: Add my name to mailing list
Newsgroups: comp.protocols.iso.x400
Date: 15 Oct 92 05:51:34 GMT

Hello, I'm Young Shin JAE work at Samsung Hewlett-Packards in KOREA.
Would you Please add my mail address in your mailing list ?
My mail address is ysjae@korea.hp.com
From: S.Kille@isode.com (Steve Hardcastle-Kille)
Subject: Re: A very nasty typo
In-reply-to: Your message of Tue, 06 Oct 92 21:43:12 -0700. <7929.718432992@nma.com>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Newsgroups: comp.protocols.iso.x400.gateway
Date: 7 Oct 92 10:23:43 GMT
Phone: +44-71-223-4062

The ISODE Consortium has an OID in the BSI managed number space
as as an IANA enterprise.   I am using these as seems
approrpriate (I've only used hte IANA one to date, as I received
that first).

Steve
From: Stef@nma.com (Einar Stefferud)
Subject: Re: A very nasty typo
In-reply-to: Your message of Tue, 06 Oct 1992 23:17:58 +0100.
             <6310.718409878@isode.com>
Newsgroups: comp.protocols.iso.x400.gateway
Reply-To: Stef@nma.com
Date: 7 Oct 92 09:14:35 GMT

I seriously believe that the ISOC or the IAB should apply for and
obtain an ICD OID assignment from BSI under { 1 3 } for The Internet
(IETF).  Either the ISOC or the IAB are clearly an International
Organization, and that is what that registry is for.

This would help politically by removing the appearance of US DoD
dominance and control, and provide a nice short OID for the IANA.

I beleive that BSI would not even blink at the request, and would
promptly assign the next open ICD OID in their register.

Since you are only a short phone call away, how about you giving them
a call?  I expect that the ISODE Consortium should also be thinking of
getting one for itself anyway;-).

Cheers...\Stef
From: stari@romeppc.VNET.IBM.COM (Mauro Starinieri)
Date: Wed, 14 Oct 92 15:05:57 CET
Newsgroups: comp.protocols.iso.x400
Subject: X.400 Gateway
Organization: IBM Semea - RNSL
Disclaimer: This posting represents the poster's views, not those of IBM
News-Software: Usenet 3.0

 I'm a new user of Internet network. I heard the possibility to use
 a gateway in order to send email from the Internet to X.400.
 Can anyone help me?


   Mauro Starinieri
   Rome Networking Systems Laboratory
   via Paolo di Dono, 44 - 00143 Rome (Italy)
   Tel: +39-6-5187.2331
   FAX: +39-6-5187.2596
   E-MAIL: IBMMAIL(ITIBMP4L)
   X.400: c=IT/a=IBMX400/p=IBMMAIL/s=Starinieri/g=Mauro
From: eskovgaa@cue.bc.ca (Erik Skovgaard)
Newsgroups: comp.protocols.iso.x400
Subject: What is X.440 dealing with ?
Date: 8 Oct 92 03:48:35 GMT

X.440 is the new standard for Voice Messaging.  VM is a new Content Type.

Format is similar to P2 (actually to P22), but relates more to the
specific application.  For instance, the Subject is encoded in voice.
The chosen encoding for for voice data is 32K ADPCM as per some CCITT
standard (ask analog people - I've never read it).

Cheers,                             ....Erik.
Newsgroups: comp.protocols.iso.dev-environ
From: mbmg@mbunix.mitre.org (Michnikov)
Subject: PEPY question
Organization: The MITRE Corp., Bedford, Ma.
Date: Fri, 9 Oct 1992 12:57:44 GMT

For a very simple syntax (definition of Scope in CMIP):

Scope ::= CHOICE {
        INTEGER {
                base (0),
                first (1),
                depth (2)
        },
        oneLevel [1] IMPLICIT INTEGER,
        manyLevels [2] IMPLICIT INTEGER
}

pepy -A generates build routine with is essentially a no operation.

Addition of

PREFIXES encode decode print
and
ENCODER encode / DECODER decode directives produces encode and decode routines,
but encode is a noop again, and decode just checks correctness of asn.1, but
produces no actual data structures.

How do I get meaningful encode/decode routines?

On a related note, were can I get more info on pepy extensions (I know,
there is some in the ISODE manual; I would like more).

I use ISODE 7.0.
 Mike.
From: gram@aim1.aztec.co.za (Graham Wheeler)
Newsgroups: comp.protocols.iso.dev-environ
Subject: Estelle tools
Date: 7 Oct 92 15:26:34 GMT
Article-I.D.: aim1.gram.718471594
Organization: Aztec Information Management

Hi all

Some time back I posted an article on the Estelle tools that I had developed,
and received a very favourable response. I got everything packaged and
uploaded it to the comp.binaries.ibm.pc moderators several weeks ago. As
yet, there has been no response from the moderators, and the package has not
been posted. As I can only assume that the c.b.i.p. moderators are either
too busy, or rejected the package (in which case they could at least have
had the courtesy of informing me as to why they did this), I will upload the
code to Simtel as soon as I get a chance, and inform the group accordingly.

Sorry about the long wait
Regards
Graham

-- 
Graham Wheeler                     | "That which is weak conquers the strong,
Network Systems Programmer         | that which is soft conquers the hard."
Aztec Information Management       | 		Lao Tzu - Tao Te Ching Ch. 78
gram@aim1.aztec.co.za              | There's no justice, there's just us
Newsgroups: comp.protocols.iso.dev-environ
From: mbmg@heckle.mitre.org (Michael B. Michnikov)
Subject: PEPY question
Organization: The MITRE Corporation, Bedford, MA
Date: Thu, 8 Oct 1992 15:29:54 GMT

For a very simple syntax (definition of Scope in CMIP):

Scope ::= CHOICE {
        INTEGER {
                base (0),
                first (1),
                depth (2)
        },
        oneLevel [1] IMPLICIT INTEGER,
        manyLevels [2] IMPLICIT INTEGER
}

pepy -A generates build routine with is essentially a no operation.

Addition of

PREFIXES encode decode print
and
ENCODER encode / DECODER decode directives produces encode and decode routines,
but encode is a noop again, and decode just checks correctness of asn.1, but
produces no actual data structures.

How do I get meaningful encode/decode routines?

On a related note, were can I get more info on pepy extensions (I know,
there is some in the ISODE manual; I would like more).

I use ISODE 7.0.
 Mike.
From: tebbutt@rhino.ncsl.nist.gov (John Tebbutt)
Newsgroups: comp.protocols.iso.dev-environ
Subject: "Lightweight" DUAs
Date: 9 Oct 92 15:29:02 GMT
Organization: N.I.S.T.

Alright, alright, so I didn't sit up and listen when I should've!	;^)
And now I'm regretting it. I'm looking for lightweight DUA packages - DUAs
for use on Mac, PC, etc. Are there archives on this subject? Any pointers
much appreciated. Please mail me directly: tebbutt@rhino.ncsl.nist.gov.

Thanks!

JT
Newsgroups: comp.protocols.iso.dev-environ
From: mbmg@mbunix.mitre.org (Michnikov)
Subject: PEPY question
Organization: The MITRE Corp., Bedford, Ma.
Date: Thu, 8 Oct 1992 15:11:07 GMT

For a very simple syntax (definition of Scope in CMIP):

Scope ::= CHOICE {
        INTEGER {
                base (0),
                first (1),
                depth (2)
        },
        oneLevel [1] IMPLICIT INTEGER,
        manyLevels [2] IMPLICIT INTEGER
}

pepy -A generates build routine with is essentially a no operation.

Addition of 

PREFIXES encode decode print
and 
ENCODER encode / DECODER decode directives produces encode and decode routines,
but encode is a noop again, and decode just checks correctness of asn.1, but 
produces no actual data structures.

How do I get meaningful encode/decode routines?

On a related note, were can I get more info on pepy extensions (I know,
there is some in the ISODE manual; I would like more).

I use ISODE 7.0.
 Mike.
Newsgroups: comp.protocols.iso.dev-environ
From: mbmg@mbunix.mitre.org (Michnikov)
Subject: PEPY question
Organization: The MITRE Corp., Bedford, Ma.
Date: Thu, 8 Oct 1992 15:25:41 GMT

For a very simple syntax (definition of Scope in CMIP):

Scope ::= CHOICE {
        INTEGER {
                base (0),
                first (1),
                depth (2)
        },
        oneLevel [1] IMPLICIT INTEGER,
        manyLevels [2] IMPLICIT INTEGER
}

pepy -A generates build routine with is essentially a no operation.

Addition of

PREFIXES encode decode print
and
ENCODER encode / DECODER decode directives produces encode and decode routines,
but encode is a noop again, and decode just checks correctness of asn.1, but
produces no actual data structures.

How do I get meaningful encode/decode routines?

On a related note, were can I get more info on pepy extensions (I know,
there is some in the ISODE manual; I would like more).

I use ISODE 7.0.
 Mike.
From: jira@latcs1.lat.oz.au (Ajin Jirachiefpattana)
Newsgroups: comp.protocols.iso
Subject: Help for Stochastic Activity Networks.
Date: 16 Oct 92 12:51:58 GMT
Organization: Comp Sci, La Trobe Uni, Australia


Hi everybody,

This may not be the appropriate news group (if not, can someone point me
in the right direction?) but ..

Does anyone out there know of Stochastic Activity Networks (SAN),
general comments on a comparison of Stochastic Activity Networks to
Stochastic Petri Nets (SPN)? Why is it not widely used like Stochastic 
Petri Nets (this is my opinion that may be not correct)? Is there any 
software tool for analysis, simulation and evaluation the Stochastic 
Activity Networks available in the public domain? 

Any help is greatly appreciated.

Ajin Jirachiefpattana,
jira@latcs1.lat.oz.au

Department of Computer Science & Computer Engineering,
La Trobe University,
Bundoora, Vic., 3083.
Australia.
From: ctw@aero.org (Charles Wolverton)
Newsgroups: comp.protocols.iso
Subject: X.500 DUA API
Followup-To: comp.protocols.iso
Date: 7 Oct 1992 22:19:12 GMT
Organization: The Aerospace Corp.
Distribution: world
NNTP-Posting-Host: bacchus.aero.org

Other than the OSF's XDS, does anyone know of emerging "standard" APIs for
X.500 DUAs?? (cf. MAPI, VIM, XAPIA for X.400.)

-chas

Charles T. Wolverton                  The Aerospace Corporation
Computer Networking Department        P.O. Box 92957 MS M1-023
Ph. 310.336.0354                      Los Angeles, CA 90009
FAX 310.336.7505                      ctw@aero.org
From: kbs@ccr-p6.ccr.jussieu.fr (An OCR-IP fan)
Newsgroups: comp.protocols.iso
Subject: X200?
Date: 9 Oct 92 23:40:14 GMT
Organization: Universites P. & M. Curie / D. Diderot

Hi world,

Apart from asking you what is X200 8)
I'd like to know where I can get info on 
ISO stacks and protocols.

Also is there a FAQ...

Thanx,

-- 
=============================================================================
Laboratoire d'Electrochimie - Universite Paris 7  |Khac Binh Su
4, place Jussieu, Tour 44/45, 75005 PARIS. FRANCE |e-mail: kbs@ccr.jussieu.fr
=============================================================================
From: mskuhn@cip.informatik.uni-erlangen.de (Markus Kuhn)
Newsgroups: comp.protocols.iso
Subject: OSI Information Retrieval Protocol
Date: 7 Oct 92 15:48:52 GMT
Reply-To: mskuhn@immd4.informatik.uni-erlangen.de
Organization: CSD., University of Erlangen

Does anyone know the current status of

  ISO 10162     Bibliographic Search, Retrieval and Update Service
  ISO 10163     Bibliographic Search, Retrieval and Update Protocol

and the technical contents of these standards? Is this the new version of the
WAIS protocol (Z??.?? Sorry, I forgot the numbers)?

I want to include a short description of every layer 7 protocol in the FAQ
and I don't know anything about this standard. Is ISO SR the common
abbreviation for it?

And what do you know about ISO 10160/10161, the 'Interlibrary Loan
Service Definition/Protocol Specification'? Status?

Markus

---
Markus Kuhn, Computer Science student -=-=- University of Erlangen, Germany
Internet: mskuhn@immd4.informatik.uni-erlangen.de  |  X.500 entry available
-A distributed system is one in which the failure of a computer you didn't-
-even know existed can render your own computer unusable. (Leslie Lamport)-
Newsgroups: comp.protocols.iso
From: mskuhn@immd4.informatik.uni-erlangen.de (Markus Kuhn)
Subject: Re: X200?
Reply-To: mskuhn@immd4.informatik.uni-erlangen.de
Organization: CSD., University of Erlangen, Germany
Distribution: world 
Date: Wed, 14 Oct 1992 11:06:30 GMT

bob1@cos.com (Bob Blackshaw) writes:

>As a matter of fact, except for the CCITT boilerplate, X.200 is
>identical with IS 7498, at least it was in 1984 when I was the
>editor of X.200.

I'm just curious: As the editor of the OSI Reference Model standard, you
could perhaps tell us a little bit about the early history of OSI.

Who invented the 7 layer model? 
When did work on OSI start?
Who had the idea of OSI? 
Is it true that the people involved in early OSI design came mostly
from the telephone industry and not from computer science?
What alternative proposals have there been to the 7 layer model?

Looking forward to a few insider stories ...

Markus

-- 
Markus Kuhn, Computer Science student -=-=- University of Erlangen, Germany
Internet: mskuhn@immd4.informatik.uni-erlangen.de  |  X.500 entry available
--- Wer, wie, was? Wieso, weshalb, warum? Wer nichts fragt bleibt dumm. ---
From: xavier@srt-poste.fr (Xavier Saliou)
Newsgroups: comp.protocols.iso
Subject: RE : SNMP for OSI
Date: 8 Oct 92 14:30:01 GMT
Reply-To: xavier@srt-poste.fr
Organization: Service de Recherche Technique de la Poste

You will find what youn want in the RFC 1161
Newsgroups: comp.protocols.iso
From: brian@mel.dit.csiro.au (Brian May)
Subject: Re: XOM and XDS - more info
Organization: CSIRO DIT (Melb.)
Date: Thu, 15 Oct 92 22:56:57 GMT


In article <1992Oct14.195612.9110@walter.bellcore.com>, tain@wrench.bae.bellcore.com (Tai Nguyen) writes:
|> In article <1992Oct13.020901.3410@mel.dit.csiro.au>, brian@mel.dit.csiro.au (Brian May) writes:
|> 
|>   ... Stuff deleted 
|> 
|> |> 
|> |> OIDs and Class Tables
|> |> ---------------------
|> |> 
|> |> XOM holds a _static_ class table containing all the OIDs it knows about.
|> |> If you want to dynamically use/create a new object, it'll have to be 
|> |> re-compiled into XOM's class tables.
|> |> 
|> |> Class table structure is left up to the implementor.
|> |> 
|> |> Encode/Decode
|> |> -------------
|> |> 
|> |> These merely create the relevant structures for sending/receiving ASN.1
|> |> data relevant to the protocol stack in use.  (We use PEPSY for ISODE)
|> |> 

clarification:

These merely create the relevant structures, encoders and decoders
for sending/receiving ASN.1 data relevant to the protocol stack in use.
(We use PEPSY for ISODE)


|> it and its peer can use different stack. Thus, the encoding must be based on
|> ASN.1 syntax understood by both sides.

It is.

regards,

brian
--
| Brian.May@mel.dit.csiro.au |           Open Systems Program           |
| CSIRO/DIT, 723 Swanston st | TEL +61 3 282 2613 -- FAX +61 3 282 2600 |
|Carlton, VIC 3053, Australia|          Experimental Scientist          |
From: nyhuis@ictser.UUCP (Ruud Nyhuis)
Newsgroups: comp.protocols.iso
Subject: TLI on SunOS
Summary: Request for tli experience on SUN
Keywords: tli, connection-based, SUN, SunOS 4.1.1
Date: 8 Oct 92 11:06:09 GMT

Hello,

Currently, I am trying set up tli communication between two processes (client and server) on a Sun Workstation (SunOS 4.1.1). The manuals give an example.
However, they do not explain which stream device should be selected, or how
to set up a stream device. They only 'talk' about '/dev/tivc' which is fake, 
and a reference is given to a certain clone device. Does anybody have experience
with this, please let me know.

I don't know whether this is the right newsgroup, although, it is named 
protocols.iso, so it is at least very close.

Thanks

e-mail: nyhuis@ict.nl

Ruud Nijhuis
ICT Automatisering Deventer BV
P.O. Box 701
7400 AS  Deventer
The Netherlands

Newsgroups: comp.protocols.iso
From: brian@mel.dit.csiro.au (Brian May)
Subject: Re: X.500 DUA API
Organization: CSIRO DIT (Melb.)
Date: Fri, 9 Oct 92 04:31:36 GMT


In article <ctw-071092151351@bacchus.aero.org>, you write:
|> Other than the OSF's XDS, does anyone know of emerging "standard" APIs for
|> X.500 DUAs?? (cf. MAPI, VIM, XAPIA for X.400.)


I have the dubious good fortune to be implementing X/Open's XOM/XDS APIs at the
moment.  As far as 'standard' APIs go, basically you've got 2 flavours of
the APIs I just mentioned.

From X/Open:

XOM	-	Generic OSI data management API
XDS	-	X.500 API (which needs XOM)

The definitions are, as far as I can tell 'stable' - meaning they are not
likely to change.

From IEEE/POSIX

P1224		Generic OSI data management API
P1003.17	X.500 API (which needs P1224)

The POSIX APIs are based upon XOM & XDS and are still under development.

That's what I know of re: availability.  If you want any technical comments 
on the X/Open APIs, feel free to ask - there's plenty to talk about.

brian
--
| Brian.May@mel.dit.csiro.au |           Open Systems Program           |
| CSIRO/DIT, 723 Swanston st | TEL +61 3 282 2613 -- FAX +61 3 282 2600 |
|Carlton, VIC 3053, Australia|          Experimental Scientist          |