HDTenEightyP/NetNews huggingface dataset:
From: rcb@ncsu.edu (Randy Buckland)
Subject: Getting new principal key
Organization: North Carolina State University
Date: Thu, 19 Nov 1992 19:35:03 GMT

For various reasons, I need to perform the following sequence of operations:

1. Run kinit (or equivalent) on machine A
2. Run telnet/rlogin/rsh like utility on machine A
	2a. utility contacts machine B
	2b. server on machine B authenticates user from A
	2c. server on machine B creates new ticket file for user on B
	2d. server on machine B runs desired command under user's environment.
3. server on machine B removes tickets and cleans up in general after
   command has completed

The problem I have is that I can't figure out how to do step 2c. 
For example, if the command passed to B is "klist", it should list just the
krbtgt ticket for that user. The V4 rsh/etc. tools will not do step 2c


The reason I want to do this is to allow the command run on machine B to 
run as the user and get tickets of it's own for other operations. I just
need some way to propigate the krbtgt ticket.
--
Randy Buckland                               "It's hard to work
North Carolina State University               in a group when you're
randy_buckland@ncsu.edu (919) 515-5491        omnipotent"       -- Q
Newsgroups: comp.protocols.kerberos
From: sdawson@ENGIN.UMICH.EDU (Scott Dawson)
Subject: Kerberos on multi-homed hosts.
Organization: Internet-USENET Gateway at Stanford University
Date: Mon, 23 Nov 1992 17:57:58 GMT


I am having problems with kerberos client stuff on multi-homed hosts.

Here's my situation.  I have kerberos running on several machines 
which have ethernet and FDDI interfaces, and have the problem that 
I acquire my tickets through the FDDI interface but when I present 
them I sometimes do so through my ethernet interface.  The server 
which I present the ticket to then thinks that it is bogus because 
the address I am coming from doesn't match the address in the ticket.

I need a way for the server to recognize that the address in the ticket 
and the address of the interface that I am coming from are associated with
the same host.  The only ways that I can think of to do this are:

    1.  Use nameservice.  This is insecure because you may not
        necessarily trust the nameserver.
    2.  Have an equivalency list on the local host.  This doesn't scale
        well, nor can you know about all machines which might try to
        connect to your service.

Is there a kerberized nameserver or a better method that someone is
using right now?  Even examples of the above would be appreciated.


Thanks in advance,
-Scott Dawson
Newsgroups: comp.protocols.kerberos
From: prasad@ISI.EDU (Prasad Upasani)
Subject: Re: admin_acl_file
Reply-To: prasad@ISI.EDU
Organization: USC Information Sciences Institute.
Date: Tue, 24 Nov 1992 01:28:55 GMT

> 
> Is format of the admin_acl_file documented any where?  The man pages
> for kadmin, kadmind and kpasswd all seem to be null.  Are there
> any version 5 beta #2 man pages for these yet?
> 

There is a sample admin_acl_file that comes with the v5 beta release.
It is in kadmin/server.

The format is:
#       Administrator Access Control List
#       Format:
#       Name    Privileges      Comments
#       Where Privileges is a string containing one or more of
#               "a"             Add New Principals
#               "c"             Change Passwords
#               "d"             Delete Current Principals
#               "i"             Inquire About Existing Principals
#               "m"             Modify Existing Principals
#               "*"             All Privileges
#jqsample/admin@realm   *
#tomjones/admin@realm   acim    # Note - May Not Delete

Note that this file should be put in /krb5 along with the KDC
database.

-Prasad
Newsgroups: comp.protocols.kerberos
Subject: Kerberos 5 compile ?
From: mohan@lilac.cse.utoledo.edu (Mohan Pakkurti)
Date: 18 Nov 92 17:33:07 EST

Please reply by e-mail to mohan@jupiter.cse.utoledo.edu
-------------------------------------------------------
Hi,
I am trying to compile kerberos 5 on a Sun SparcStation 2 running 4.1.2.
my root source directory is /usr/lilac/athena/krb5/src.
I made changes to the site.def file to reflect the location of header files
for ss and com_err. and have isode-8.0.

When i give "make world" i get the following error and compilation stops.
--------------------
making all in lib/des...
rm -f cksum.o
cc -pipe -c -O  -I. -I/usr/lilac/athena/krb5/src/include -I../../include -I/usr/lilac/athena/krb5/src/include     -DBIG -DMUSTALIGN -DMSBFIRST  /usr/lilac/athena/krb5/src/lib/des/cksum.c
rm -f des.o
cc -pipe -c -O  -I. -I/usr/lilac/athena/krb5/src/include -I../../include -I/usr/lilac/athena/krb5/src/include     -DBIG -DMUSTALIGN -DMSBFIRST  /usr/lilac/athena/krb5/src/lib/des/des.c
/usr/lilac/athena/krb5/src/lib/des/des.c: 62: Can't find include file s_table.h
/usr/lilac/athena/krb5/src/lib/des/des.c: 63: Can't find include file p_table.h
/usr/lilac/athena/krb5/src/lib/des/des.c: 163: Can't find include file ip.c
"/usr/lilac/athena/krb5/src/lib/des/des.c", line 309: S_adj undefined
/usr/lilac/athena/krb5/src/lib/des/des.c: 390: Can't find include file p.c
/usr/lilac/athena/krb5/src/lib/des/des.c: 434: Can't find include file fp.c
*** Error code 3
make: Fatal error: Command failed for target `des.o'
Current working directory /usr/lilac/athena/krb5/src/lib/des
*** Error code 1
make: Fatal error: Command failed for target `all'
Current working directory /usr/lilac/athena/krb5/src/lib
*** Error code 1
make: Fatal error: Command failed for target `all'

---------------------
I found that the header files are in the same directory as des.c , also i cannotfind the files ip.c and fp.c in the distribution.

Have i messed up something, can someone please tell me how i can get this
to work.

Thanks a lot for your help, and hope to hear from someone soon.
:)
--mohan


-- 
===============================================================================
+ Mohanakrishna Pakkurti            + mohan@jupiter.cse.utoledo.edu           +
+ HOME: 2239 University Hills Blvd #204, Toledo OH 43606. Phone:(419)536-9073 +
===============================================================================
Newsgroups: comp.protocols.kerberos
From: efroyman@lynx.dac.northeastern.edu (Ella Froyman)
Subject: Kerberos Implementation on Dec 50000
Keywords: Kerberos
Organization: Northeastern University
Date: Tue, 24 Nov 1992 01:25:46 GMT


Hi Netters;
  
I have been asked to implement Kerberos Version 4 with an exisiting
application which is a motif-based application. It uses Yellow pages
, DNS and other thing like telnet,ftp,mail,etc....

My questions are:

(1) Whats a good and simple defintion of kerberos?
(2) How do I implement kerberos version with my application?
(3) Where do I get detailed documentation on kerberos version 4?
(4) What are the benefits of kerberos and disadvantages?
(5) Why should someone use kerberos

I would really appreciate input from you people

Ella

Newsgroups: comp.protocols.kerberos
From: warlord@MIT.EDU (Derek Atkins)
Subject: Re: Getting new principal key
Organization: Internet-USENET Gateway at Stanford University
Date: Fri, 20 Nov 1992 04:46:41 GMT

> The reason I want to do this is to allow the command run on machine B to 
> run as the user and get tickets of it's own for other operations. I just
> need some way to propigate the krbtgt ticket.

There is no way to do this under KRB V4.  You could run rkinit to get
remote tickets, but the user still has to type their password to do
that (which you really dont want to have to do).

V5 does this:  You can propagate a TGT in V5.  I suggest trying that.

Hope this helps.

-derek

         Derek Atkins -- MIT '93 -- Electrical Engineering
--warlord@MIT.EDU | ..!mit-eddie!mit-athena!warlord | s20069@mitvma.bitnet
      Chairman, MIT Student Information Processing Board (SIPB)
           MIT Media Laboratory, Speech Research Group
From: /PN=Thomas.K.Hinders/OU=CCMAIL/O=CHAN.IS/PRMD=MMC/ADMD=TELEMAIL/C=US/@sprint.com
Subject: TAB character conversion
Newsgroups: comp.protocols.iso.x400
X-Message-Id: <"110908231192"*/PN=Thomas.K.Hinders/OU=CCMAIL/O=CHAN.IS/PRMD=MMC/ADMD=TELEMAIL/C=US/@sprint.com>
Date: 23 Nov 92 16:39:49 GMT

    I receive messages in which the TAB character is translated to a
    non-ascii character.

    This seems to occur when the message orginates from the Internet, and
    passes through the Telemail X.400 <==> Internet gw (sprint.com)

    When I send messages to myself or through other X.400 connections,
    everything is OK.

    Has anyone else experienced the same problem?

    Thanks................

                                Thomas K Hinders
                       Martin Marietta Computing Standards
                             4795 Meadow Wood Lane
                               Chantilly, VA 22021
                        703.802.5593 (v) 703.802.5027 (f)
From: scase@email.sp.paramax.com (Steve Case)
Newsgroups: comp.protocols.iso.dev-environ
Subject: Question on ASN.1 Encodings
Date: 11 Nov 92 17:13:57 GMT
Organization: Paramax -  Eagan, MN
NNTP-Posting-Host: svcase.sp.paramax.com

I am trying to understand the various ASN.1 encoding and I cannot seem
to understand how the indefinite form for the length octets can possibly
work!  To make things simple, let me give you a specific example and
hopefully someone can clarify the situation for me.

Let's assume we are encoding a bitstring value.  The particular bitstring
to be encoded is '0900000009'H.  If I use the indefinite length format, 
wouldn't this be encoded as follows:

   BitString Length Contents
   23        80     000900000009

   EOC       Length
   00        00


My question, then, is when decoding this octet stream, how do you know
that the bitstring is '0900000009'H and not '09'H or '090'H or '0900'H
or '09000'H?  All three of these seem to be possible decodings?

Thank you for any assistance you might be able to give me.

Regards,
Steve Case
scase@planet8.sp.paramax.com
Newsgroups: comp.protocols.iso.dev-environ
From: euaeni@eua.ericsson.se (Erik Nissen)
Subject: Compilers for managed object specifications
Reply-To: euaeni@eua.ericsson.se
Organization: Ellemtel Telecom Systems Labs, Stockholm, Sweden
Date: Fri, 20 Nov 1992 15:32:10 GMT

Hi there
I'm looking for latest news on compilers of managed object specification,
confirming to CCITT X.722 (GDMO) templates.

All hints are welcome!

Please answer by e-mail to: euaeni@eua.ericsson.se
Thanks for any help.
Erik Nissen
From: pietro@nova.bellcore.com (Pietro Manzoni)
Newsgroups: comp.protocols.iso.dev-environ
Subject: Isode ftp site
Date: 23 Nov 92 18:43:28 GMT
Reply-To: pietro@nova.bellcore.com
Organization: Network Technology Research Lab, Bellcore

In article <HUGUES.92Nov21213001@gamay.afp.com>, hugues@afp.com (Hugues Lafarge) writes:
|> Sorry to ask such a trivial question, but a friend asked me what
|> was the ISODE last release number was and where he could get it
|> 
|> Please reply via e-mail, as i doubt there is any general interest
|> in such an already know question.
|> 
|> Thanks in advance.
I'm interested in those information, too.

Thanks

Pietro
Newsgroups: comp.protocols.iso.dev-environ
From: hender@sun429.nas.nasa.gov (Robert L. Henderson)
Subject: Pepsy bug with REAL
Keywords: ISODE
Organization: CSC at NASA Ames Research Center, NAS Ssytems Division
Date: Mon, 23 Nov 92 21:48:36 GMT
Reply-To: hender@nas.nasa.gov

I have installed ISODE 8.0 on a Sun sparc running SunOS 4.1.

I can generate a program with posy/pepy which allows me to encode/decode REALs.
However, attempting the same feat with pepsy results always results in a
return of NULLPE from any encode_ function which must encode a real.

Has anyone else noted this, even better has any a solution?

-- 
Bob Henderson				hender@nas.nasa.gov
NASA Ames Research Center

"My goal in life?  To find the winning lotto ticket on the sidewalk!"
From: baos@caip.rutgers.edu (Bancroft Scott)
Newsgroups: comp.protocols.iso.dev-environ
Subject: Re: Question on ASN.1 Encodings
Date: 20 Nov 92 18:00:58 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

scase@email.sp.paramax.com (Steve Case) writes:

>Let's assume we are encoding a bitstring value.  The particular bitstring
>to be encoded is '0900000009'H.  If I use the indefinite length format, 
>wouldn't this be encoded as follows:

>   BitString Length Contents
>   03        80     000900000009
>   EOC       Length
>   00        00

>My question, then, is when decoding this octet stream, how do you know
>that the bitstring is '0900000009'H and not '09'H or '090'H or '0900'H
>or '09000'H?  All three of these seem to be possible decodings?

In the above I changed your original identifier octet from '23' to '03' as
you requested in your followup mail.

Clause 6.3.2.c of ISO 8825 states "use the indefinite form if the
encoding is constructed".  Since the above encoding has the
primitive/constructed bit set to 0, indicating that the encoding is
primitive, the indefinite form cannot be used in encoding the bit
string, hence the encoding should be:

   BitString Length Contents
   03        06     000900000009


However, if we consider the example in your original message:

>   BitString Length Contents
>   23        80     000900000009
>   EOC       Length
>   00        00

we see that since in this case the encoding has the
primitive/constructed bit set to 1, indicating that the encoding is
constructed, the indefinite length form can be used.  However, the
Contents must eventually be a primitive encoding of the actual bit
string value, or of several bit string values that together form the
original value.  A proper encoding for the above is:

   BitString Length Contents
   23        80
		    BitString Length Contents
		    03        06     000900000009
   EOC       Length
   00        00

So why bother using indefinite length form?  So that you can start
the encoding process without knowing ahead of time the total length
of the value.  For example:

   BitString Length Contents
   23        80
		    BitString Length Contents
		    03        04     00090000
		    03	      03     000009
   EOC       Length
   00        00

See ISO 8825 clause 11.3 for details.

=====================================|========================================
Bancroft Scott			     |		Open Systems Solutions, Inc.
609-987-9073			     |		Princeton, N.J.
=====================================|========================================
Newsgroups: comp.protocols.iso.dev-environ
From: pwang@opencon.com (Patrick Wang)
Subject: any ftp site which has the CCITT Draft Recommendations
Organization: OpenCon Systems, Inc.
Date: Wed, 18 Nov 1992 15:08:39 GMT

Dear netter:


Is there anyone can kindly tell me any ftp site which has the CCITT
Draft Recommendations?

Thank you for what you will do for me.


My e-mail address is :  pwang@opencon.com


Patrick.
Organization: Middle East Technical University - Computer Center
Date: Friday, 20 Nov 1992 16:19:06 TUR
From: <C88196@TRMETU.BITNET>
Newsgroups: comp.protocols.iso.dev-environ
Subject:    ISODE

I am attending to a gradute course which is distributed computing
systems. I am making a research about ISODE . So, I need some
documents.

If you send related documents to my E-MAIL address I will be glad.

Thanks..


C88196@TRMETU.BITNET
From: hugues@afp.com (Hugues Lafarge)
Newsgroups: comp.protocols.iso.dev-environ
Subject: isode last release number & ftp site
Date: 22 Nov 92 01:30:45 GMT
Organization: Axis Design 119 rue de Flandre, 75019 Paris, France

Sorry to ask such a trivial question, but a friend asked me what
was the ISODE last release number was and where he could get it

Please reply via e-mail, as i doubt there is any general interest
in such an already know question.

Thanks in advance.
From: scase@email.sp.paramax.com (Steve Case)
Newsgroups: comp.protocols.iso.dev-environ
Subject: Re: Question on ASN.1 Encodings
Date: 11 Nov 92 17:39:04 GMT
Organization: Paramax -  Eagan, MN
NNTP-Posting-Host: svcase.sp.paramax.com

Sorry, but I made a mistake in my encoding.  The identifier octet should
have been '03'H and not '23'H.  Other than that, the question should be
ok.

Regards,
Steve Case
scase@planet8.sp.unisys.com
Newsgroups: comp.protocols.iso
From: Erik Naggum <enag@ifi.uio.no>
Date: 20 Nov 1992 18:35:04 +0100
Subject: Re: Question on ASN.1 Encodings

Steve,

The variable length encoding of the basic encoding rules can only be
used for constructed types.  X.209(88) (== ISO 8825:1987) 6.3.2 reads:

    A sender shall

    a)  use the definite form if the encoding is primitive;

    b)  use either the definite form or the indefinite form, a sender's
        option, if the encoding is constructed and all immediately
        available;

    c)  use the indefinite form if the encoding is contructed and is not
        all immediately available.

Since the constructed encodings ultimately have objectes with primitive
encoding as their constituents, your problem never arises.

In your particular case, you can choose the primitive encoding:

        03 06 00 09 00 00 00 09
        -- -- -- --------------
         |  |  |              |
         |  |  |              +-- contents
         |  |  +----------------- number of residual bits in last octet
         |  +-------------------- definite form, length of content
         +----------------------- universal, primitive, bit string

or constructed:

        23 80 03 06 00 09 00 00 00 09 00 00
        -- -- ----------------------- -----
         |  |                       |     |
         |  |                       |     +-- end of contents marker
         |  |                       +-------- contents of constructed
         |  |                                 encoding (see above!)
         |  +-------------------------------- indefinite form
         +----------------------------------- universal, constructed,
                                              bit string

Hope this helps.

</Erik>
--
Erik Naggum             :  ISO  8879 SGML     :      +47 295 0313
                        :  ISO 10744 HyTime   :
<erik@naggum.no>        :  ISO 10646 UCS      :      Memento, terrigena.
<enag@ifi.uio.no>       :  ISO  9899 C        :      Memento, vita brevis.
From: mpeters@pax.eunet.ch (MBX Michael Peters)
Newsgroups: comp.protocols.iso
Subject: E1 vs. T1 Signalling
Date: 16 Nov 92 22:10:43 GMT
Organization: EUnet Login/Mailbox Service
X-Newsreader: Tin 1.1 PL3


Hello,

I'm looking for E1 signalling specifications, and, if possible how they
differ from and relate to T1. Any reference to an FTP site would be
welcomed.

Mike.
____________________   .    .   __         . Michael Peters - FRANKLIN DATACOM
\______NCC_1701_____|) .____.--"--"---._____       mpeters@pax.eunet.ch
            ||      /-----._________.----/   Voice(in CH): 41 52 213 9347
     /=======||====/___/       "--"          FDI HQ: V: 1 805 373 8688
   . \==\____________|(-                .          Fax: 1 805 373 7373
Newsgroups: comp.protocols.iso
From: rkc@maestro.bellcore.com (Ramakrishna Chamarthy)
Subject: Re: Question on ASN.1 Encodings
Organization: Bellcore (Red Bank, NJ)
Date: Fri, 20 Nov 92 16:24:35 GMT

In article <1drej9INN8t8@svcase.sp.paramax.com> scase@email.sp.paramax.com (Steve Case) writes:
>I am trying to understand the various ASN.1 encoding and I cannot seem
>to understand how the indefinite form for the length octets can possibly
>work!  To make things simple, let me give you a specific example and
>hopefully someone can clarify the situation for me.
>
>Let's assume we are encoding a bitstring value.  The particular bitstring
>to be encoded is '0900000009'H.  If I use the indefinite length format, 
>wouldn't this be encoded as follows:
>
>   BitString Length Contents
>   23        80     000900000009
>
>   EOC       Length
>   00        00
>
>
>My question, then, is when decoding this octet stream, how do you know
>that the bitstring is '0900000009'H and not '09'H or '090'H or '0900'H
>or '09000'H?  All three of these seem to be possible decodings?
>
 
First of all a correction to your 'correction posting' (second posting that
I did not include) -

No, The Bit String Identifier should be '23' (instead of '03') as mentioned in 
your posting (the first reaction is the correct reaction) :-), as opposed to 
the correction ('03') mentioned in your second posting. 

The reason is, although, 
a Bit string can be encoded in Primitive Form (identifier '03') OR 
Constructor Form (identifier '23'),
you can encode only in Constructor Form using EOC. 

If it is Primitive Form, it will be encoded as

Bit String	Length	Contents
03		06	000900000009

If it is Constructor Form, you can encode it in many ways
Two of the ways are - 

Bit String	Length 	Contents
23  		80	
			Bit String	Length	Contents
			03		06	000900000009
			EOC		Length
			00		00
OR

Bit String	Length 	Contents
23  		80	
			Bit String	Length	Contents
			03		04	00090000
			Bit String	Length	Contents
			03		03	000009
			EOC		Length
			00 		00

I think, you mixed up the encodings of the Primitive Form and Constructor
Form for the Bit String in your example - and hence the confusion.

Hope this helps.

- Ramakrishna			E-mail: rkc@maestro.bellcore.com
From: steve@terminus.ericsson.se (Steve Reynolds)
Newsgroups: comp.protocols.iso
Subject: 4335 in normal response mode?
Date: 19 Nov 92 09:41:36 GMT
Reply-To: steve@terminus.ericsson.se
Distribution: world
Organization: Camtec Electronics (Ericsson), Leicester, England


Does any one know the relationship between X.25 (8208) and 4335 when used in 
Normal response mode?

How is addressing performed?
What is the relationship in terms of call to secondary mapping?

Am I missing a vital spec that I dont know about?



I understand that NRM is similar to SDLC. Is there an equivalent protocol to QLLC here
for encapsulation over X.25?


I realise this may sound like two problems, but what I actually want to do is the equivalent of carrying SDLC traffic over X.25 using QLLC.

thanks in advance 

Steve Reynolds
Newsgroups: comp.protocols.iso
From: pietro@nova.bellcore.com (Pietro Manzoni)
Subject: ESTELLE compiler
Keywords: estelle, fdt
Reply-To: ghosal@nyquist.bellcore.com
Organization: Network Technology Research Lab, Bellcore
Date: Tue, 17 Nov 92 16:24:10 GMT

Hello everybody,

I'm looking for an ESTELLE compiler to be used
on UNIX machine (sparc).
Any reference to an FTP site would be
welcomed.


Pietro
From: carlos@pico.qpsx.oz.au (Carlos Tomaz)
Newsgroups: comp.protocols.iso
Subject: Re: Information on X-tel
Date: 20 Nov 92 01:46:09 GMT
Organization: QPSX Communications LTD, Perth, Western Australia.
X-Newsreader: Tin 1.1 PL4

john@citr.uq.oz.au (John Gottschalk) writes:
: 
: Hello all,
: 
: Can anybody sent me information on a company called "X-tel". I think that
: they come from a University in the UK (University of Notingham perhaps?).
: I have heard that they have some relationship with the ISODE software,
: but I may be wrong.
: 
: 			-- regards, John Gottschalk
: 
: ===================================================================== 
:      John Gottschalk (john@citr.uq.oz.au) 
:      Centre for Information Technology Research,
:      The University of Queensland, 4072, 
:      Brisbane, Queensland, Australia,
:      +61 7 365 4321 (phone), +61 7 365 4399 (fax)
: ===================================================================== 

John,
The information you want:
	X-Tel Services Ltd.
	University Park,
	Nottingham, NG7 2RD
	UK
	Phone : +44 602 412648
	FAX :   +44 602 790278
        Email : support@xtel.co.uk
X-Tel is a founding member of the ISODE consortium, and provides support
for ISODE and associated packages on an international basis,

Cheers,

Carlos Tomaz
QPSX Communications, Ltd
33 Richardson St, West Perth
ctomaz@pico.qpsx.oz.au
carlos@atri.curtin.edu.au