From owner-ietf-radius@livingston.com Thu Sep 3 15:08:29 1998 Received: from bast (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA10188 for ; Thu, 3 Sep 1998 15:08:28 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast (8.8.5/8.6.9) with ESMTP id LAA09576; Thu, 3 Sep 1998 11:52:34 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id LAA15440 for ietf-radius-outgoing; Thu, 3 Sep 1998 11:59:46 -0700 (PDT) Message-ID: <001601bdd76c$c2325440$c889e9cc@titanium.techapp.com> From: "Russell J. LeBar" To: "RADIUS" Subject: (radius) Input and Output Octets Date: Thu, 3 Sep 1998 13:57:54 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0013_01BDD742.D9130E40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Russell J. LeBar" This is a multi-part message in MIME format. ------=_NextPart_000_0013_01BDD742.D9130E40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit This may seem like a really dumb question, but what's an Octet (as in Input and Output Octets)? Is it 256 bytes? About how big is a packet usually? Thanks! -- Russell J. LeBar ------=_NextPart_000_0013_01BDD742.D9130E40 Content-Type: text/x-vcard; name="Russell J. LeBar.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Russell J. LeBar.vcf" BEGIN:VCARD VERSION:2.1 N:LeBar;Russell;J.; FN:Russell J. LeBar ORG:Technology Applications, Inc.;Windows System Administration; RADIUS = Engineer TITLE:Software Engineer TEL;WORK;VOICE:(314) 733-5234 ; 1-800-854-9005; 1-800-854-9006 TEL;WORK;FAX:(314) 733-5252 ADR;WORK;ENCODING=3DQUOTED-PRINTABLE:;;900 Roosevelt = Pkwy.=3D0D=3D0ASuite 350;Chesterfield;MO;63017;USA LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:900 Roosevelt = Pkwy.=3D0D=3D0ASuite 350=3D0D=3D0AChesterfield, MO 63017=3D0D=3D0AUSA URL:http://www.techapp.com URL:http://www.techapp.com EMAIL;PREF;INTERNET:rjl@techapp.com REV:19980903T185738Z END:VCARD ------=_NextPart_000_0013_01BDD742.D9130E40-- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Thu Sep 3 15:32:08 1998 Received: from bast (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA10576 for ; Thu, 3 Sep 1998 15:32:08 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast (8.8.5/8.6.9) with ESMTP id MAA10493; Thu, 3 Sep 1998 12:16:18 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id MAA17739 for ietf-radius-outgoing; Thu, 3 Sep 1998 12:25:20 -0700 (PDT) Message-Id: <3.0.5.32.19980903152827.00cb7100@fred.xylogics.com> X-Sender: mitton@fred.xylogics.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 03 Sep 1998 15:28:27 -0400 To: "Russell J. LeBar" , "RADIUS" From: Dave Mitton Subject: Re: (radius) Input and Output Octets In-Reply-To: <001601bdd76c$c2325440$c889e9cc@titanium.techapp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Dave Mitton An octet is 8 bits. (oct = 8) In some architectures, in an earlier world, a byte was not necessarily 8 bits. Nor are "words" fixed at a standard size either. Dave. At 01:57 PM 9/3/98 -0500, Russell J. LeBar wrote: >This may seem like a really dumb question, but what's an Octet (as in Input >and Output Octets)? Is it 256 bytes? > >About how big is a packet usually? > >Thanks! > > >-- Russell J. LeBar > >Attachment Converted: "L:\Eudora\attachments\Russell J. LeBar41.vcf" > --------------------------------------------------------------- David Mitton 978-670-8888 Main Consulting Engineer, Nortel 978-916-4570 Direct Carrier Packet Networks, I&SP Group 978-916-4789 FAX Billerica, MA 01821 dmitton@baynetworks.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Thu Sep 3 16:34:59 1998 Received: from bast (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA11679 for ; Thu, 3 Sep 1998 16:34:59 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast (8.8.5/8.6.9) with ESMTP id NAA13783; Thu, 3 Sep 1998 13:19:23 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id NAA24753 for ietf-radius-outgoing; Thu, 3 Sep 1998 13:25:32 -0700 (PDT) Message-Id: <3.0.5.32.19980903132537.007f6100@bichon.cisco.com> X-Sender: gclark@bichon.cisco.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 03 Sep 1998 13:25:37 -0700 To: "Russell J. LeBar" , "RADIUS" From: Glen Clark Subject: Re: (radius) Input and Output Octets In-Reply-To: <001601bdd76c$c2325440$c889e9cc@titanium.techapp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Glen Clark Octet - From the Latin 'Oct' meaning 8. Octet is 8 bits, in the common venacular, 1 byte. Cheers .... Glenc At 01:57 PM 9/3/98 -0500, Russell J. LeBar wrote: >This may seem like a really dumb question, but what's an Octet (as in Input >and Output Octets)? Is it 256 bytes? > >About how big is a packet usually? > >Thanks! > > >-- Russell J. LeBar > >Attachment Converted: "C:\Data\Email\Attach\Russell J. LeBar.vcf" > - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed Sep 9 11:02:23 1998 Received: from bast (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA02607 for ; Wed, 9 Sep 1998 11:00:20 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast (8.8.5/8.6.9) with ESMTP id HAA04056; Wed, 9 Sep 1998 07:42:20 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id HAA03001 for ietf-radius-outgoing; Wed, 9 Sep 1998 07:48:04 -0700 (PDT) Message-Id: <199809091446.KAA02320@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce:; Cc: ietf-radius@livingston.com From: Internet-Drafts@ietf.org Subject: (radius) I-D ACTION:draft-ietf-radius-tunnel-acct-02.txt Date: Wed, 09 Sep 1998 10:46:08 -0400 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Internet-Drafts@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Remote Authentication Dial-In User Service Working Group of the IETF. Title : RADIUS Accounting Modifications for Tunnel Protocol Support Author(s) : G. Zorn, D. Mitton Filename : draft-ietf-radius-tunnel-acct-02.txt Pages : 9 Date : 08-Sep-98 This document defines new RADIUS accounting Attributes and new values for the existing Acct-Status-Type Attribute [1] designed to support the provision of compulsory tunneling in dial-up networks. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-radius-tunnel-acct-02.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-radius-tunnel-acct-02.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-radius-tunnel-acct-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980908160852.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-radius-tunnel-acct-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-radius-tunnel-acct-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980908160852.I-D@ietf.org> --OtherAccess-- --NextPart-- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Sep 15 13:44:52 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA00439 for ; Tue, 15 Sep 1998 13:39:11 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id KAA25673; Tue, 15 Sep 1998 10:19:27 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id KAA24242 for ietf-radius-outgoing; Tue, 15 Sep 1998 10:25:13 -0700 (PDT) From: 12886144@18131.com Date: Tue, 17 Jun 97 23:53:05 EST To: sender422@mail.whynot.net Subject: (radius) Re: subject Message-ID: <93904039291232@hsd_hypothesis.com> X-PMFLAGS: 10322341.10 X-UIDL: 10293287_192832.222 Comments: Authenticated sender is Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: 12886144@18131.com GET IT OUT THERE! WHERE PEOPLE CAN SEE IT!! Tired of endlessly posting your ad to ONLINE CLASSIFIED SITES that don't get the results you need? The fact is there are over 7000 such sites scattered about the web and frankly none of them generate enough traffic to be worth your while. The greatest way of marketing this century is undoubtedly direct e-mail. The ability to promote your product, service, website or MLM/Network Marketing opportunity to millions instantly is what advertisers have been dreaming of for over 100 years. And the greatest part, it's completely affordable. We will e-mail your one page promotion to a list of our general and/or targeted list. Call 1-972-227-7286 to get current prices. If you respond by 26th of September, receive a special discount. NOTICE: No pornogaphy, chain letters, get quick rich scheme, or any threating or questionable materials. Don't even Ask!! * * * SPECIAL OF THE DAY: 20 Million addresses on a CD-ROM, General and targeted. This CD consists 16 of the biggest companies. Also receive targeted lists of Bizmlm, Bizopp, Consumer, food, health, investing and etc. Other services charge upward of 5 cents per address for this type of targeted list. (appx. 1.6 million) This CD has over 20 million addresses, these are less than 30 days old. This CD was sorted/deduped, and randomized in each domain. These were run against the global remove list, and through our 140 mb (almost 7million) remove\flamer list. The EDU, ORG, Gov, Mil, and US was removed with some domains that ask not receive e-mail. Then CD was run against our custom filter with 492 keywords to remove more. Also we have 61mbs of undeliverables, just to make sure our list are clean as possible. Regular price is $299, but If its purchased before 9-26-98 Only $199 and PRIORITY shipping is included. Call 1-972-227-7286 for complete details. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed Sep 16 08:02:56 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id IAA18580 for ; Wed, 16 Sep 1998 08:02:31 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id EAA00353; Wed, 16 Sep 1998 04:45:22 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id EAA29649 for ietf-radius-outgoing; Wed, 16 Sep 1998 04:53:45 -0700 (PDT) Date: Wed, 16 Sep 1998 12:48:00 +0100 To: rituke30@edunet.dk From: rituke30@edunet.dk (reisian) Comments: Authenticated sender is Subject: (radius) Great Deals on AirFares--2nd Half 1998 Fare Outlook Message-Id: <199809162221RAA7400@sertyui.ist.utl.pt> Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: rituke30@edunet.dk (reisian) TravelNews keeps on-line travellers updated on Fare Wars, cruise and vacation specials, and other travel-related news. To enroll in this FREE Email service, please see end of message. Dear Client, Special Preferred AirFares now available by phone.....Airfare outlook for the rest of 1998..... Our Preferred Fares are now available by phone. These special AirFares are lower than the Airlines themselves and lower than travel agencies. We currently offer Preferred Fares with Delta, Northwest, Continental, United, and American (Caribbean only). Call us for the best rates for travel in the US, Canada, the Caribbean, Europe, Central and South America, and more !! 800-672-1672 (9am-6pm EST) ** Fully Bonded Airline Ticket supplier, serving clients worldwide since 1991. ** (rates are discounts off lowest published fare by above carriers, must be purchased at least 7 days in advance and include a Saturday night stay, subject to availability) You'll never pay regular rates again!! 800-672-1672 (9am-6pm EST) Airfare Outlook for 1998......Most airlines continue to report record booking levels which will continue the trend of higher fares that we predicted at the beginning of this year. Even though many carriers did offer sporadic "sales fares", the discounts were generally smaller and the "fare wars" fewer. It is even more important to monitor fares closely during the 2nd half of 1998 and especially important to BUY EARLY !! Remember that low fares for Holiday travel (Labor Day, Thanksgiving, Christmas) are currently available but will no doubt be selling out much sooner this year because demand will be higher. If you wait too long to buy tickets, you could pay up to 50% more. ** Did you know that we have lower fares than on-line booking !! ** ** Most transactions on-line take up to 40 minutes, ours take only 5-10 minutes!! ** 800-672-1672 (9am-6pm EST) TravelNews keeps on-line consumers updated on AirFares, Fare Wars, travel bargains, and other travel-related news. If you would like a subscription to this FREE news service, Call 919-383-0388 ext 11 (2-3 brief messages per month, no cost, addresses kept confidential, can cancel anytime.) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This was filtered against the Global Remove Database. To be added to the Global Remove Database, go to http:// 142.176.13.105 *** *** *** dk - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Sun Sep 20 00:05:01 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id AAA02498 for ; Sun, 20 Sep 1998 00:01:45 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id UAA24339; Sat, 19 Sep 1998 20:44:02 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id UAA26109 for ietf-radius-outgoing; Sat, 19 Sep 1998 20:49:57 -0700 (PDT) Date: Sun, 20 Sep 1998 05:50:10 +0200 (MET DST) To: dibemoi99@paradise.kaist.ac.kr From: dibemoi99@paradise.kaist.ac.kr ( Kraftworks) Comments: Authenticated sender is Subject: (radius) Re: PREMIUM TV.........No Monthly Bills! Message-Id: <199809193291CAA40189@coolidea.okwf.fuw.edu.pl> Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: dibemoi99@paradise.kaist.ac.kr ( Kraftworks) This is really cool! PREMIUM CHANNELS........Descrambled! EASY to assemble plans for only $6.00 ! YOU WILL BE WATCHING all your FAVORITE PAY STATIONS featuring MOVIES, SPORTS. Adult entertainment, and any other scrambled signal NEXT WEEK! You can EASILY assemble a cable descrambler in less than 30 minutes! You have probably seen many advertisments for similar plans......... BUT OURS are BETTER! We have compared it to all the others and have actually IMPROVED the quality and SIMPLIFIED the design !!! ** We even include PHOTOS! ** OUR PLANS ARE BETTER! We have NEW, EASY TO READ,EASY to assemble plans for only $6.00! We have seen them advertised for as much as $29.00 and you have to wait weeks to receive them! WHAT THE OTHERS SAY IS TRUE! Parts are available at "The TV HUT" or any electronics store. Trademark rights do not allow us to use a national electronics retail chains' name but there is one in your town! Call and ask them BEFORE you order! They are very familiar with these plans! You will need these easy to obtain parts : 270-235 mini box 271-1325 2.2k ohm resistor 278-212 chasis connectors RG59 coaxial cable #12 copper wire Variable capacitor They may have to special order the variable capacitor, But WHY WAIT for a special order? WE have them! All you need now is the EASY TO ASSEMBLE plans to show you how this educational device in 30 MINUTES! WE have secured a supply of the capacitors directly from the manufacturer and We WILL include one with your plans for an ADDITIONAL $10.00 only! It is LEGAL, providing of course you use these plans for EDUCATIONAL PURPOSES only. See first hand and LEARN how this SIMPLE circuitry works! If you intend to use these plans for any other purpose DO NOT ORDER them. IT'S FUN TO BUILD! We're sure you'll enjoy this project! This is a unique opportunity for hobbiest of ANY skill level to learn simple circuitry! Learn how easy descrambling is! $ 6.00 for plans only $10.00 for variable capacitor only $16.00 for The easy to assemble plans and one variable capacitor! Pay by check or money order payable to: Kraftworks P.O. Box 11752 San Rafael, Ca. 94912 WE pay postage and handling! Please allow 10 days for delivery. The Mailing List that you are being mailed from was filtered against the Global Remove List. If you wish to be included in this REMOVE LIST please go to: http://remove-list.com It is a widely used list honored by all responsible emailers. Once on this list you will see a great reduction in advertisements. Thank You - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Thu Sep 24 04:38:55 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id EAA28504 for ; Thu, 24 Sep 1998 04:38:54 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id BAA08662; Thu, 24 Sep 1998 01:16:09 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id BAA19290 for ietf-radius-outgoing; Thu, 24 Sep 1998 01:22:05 -0700 (PDT) Message-ID: <005601bde793$ae399520$0103a8c0@ds9> From: "Darran Potter" To: Subject: (radius) max radius password Date: Thu, 24 Sep 1998 09:16:49 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0051_01BDE79C.0F717490" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Darran Potter" This is a multi-part message in MIME format. ------=_NextPart_000_0051_01BDE79C.0F717490 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I was trying to work out the max possible password length supported by radius and I think its 240 characters. I based this on the method by which >16 char passwords are encrypted in 16char chunks with the final chunk being padded out to 16 chars. Hence to be less than the max string allowed of 253 you can only have 15 chunks =3D 240 chars. Does this look OK? If it does, do vendors ensure they truncate passwords before encryption to an aaa server? I dont think anyone would ever enter a long password (unless they were trying to break the NAS/aaa server software). However I've seen noise (or PPP stuff) somehow get into a password - with various vendors. = Luckily its never been long enough to cause the attribute length to wrap. Darran ------=_NextPart_000_0051_01BDE79C.0F717490 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I was trying to work out the max possible = password=20 length supported
by radius and I think its 240 characters. I = based this=20 on the method
by which >16 char passwords are encrypted = in 16char=20 chunks with the
final chunk being padded out to 16 = chars.
 
Hence to be less than the max string allowed = of 253 you=20 can only have
15 chunks =3D 240 chars.
 
Does this look OK? If it does, do vendors ensure they truncate=20 passwords
before encryption to an aaa server?
 
I dont think anyone would ever enter a long password (unless they=20 were
trying to break the NAS/aaa server software). However I've seen = noise
(or PPP stuff) somehow get into a password - with various vendors.=20 Luckily
its never been long enough to cause the attribute length to = wrap.
 
Darran
------=_NextPart_000_0051_01BDE79C.0F717490-- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Thu Sep 24 09:45:48 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id JAA01230 for ; Thu, 24 Sep 1998 09:45:48 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id GAA12092; Thu, 24 Sep 1998 06:28:04 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id GAA27769 for ietf-radius-outgoing; Thu, 24 Sep 1998 06:36:55 -0700 (PDT) Message-Id: <3.0.5.32.19980924093933.02f15230@fred.xylogics.com> X-Sender: mitton@fred.xylogics.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 24 Sep 1998 09:39:33 -0400 To: "Darran Potter" , From: Dave Mitton Subject: Re: (radius) max radius password In-Reply-To: <005601bde793$ae399520$0103a8c0@ds9> Mime-Version: 1.0 Content-Type: text/enriched; charset="us-ascii" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Dave Mitton Well, maybe in theory, except that Section 5.2 User-Password, page 22 of the RFC says that the password algorithm is repeated "to no more than 128 characters". And the next page says: Length: At least 18 and no larger than 130. Dave. At 09:16 AM 9/24/98 +0100, Darran Potter wrote: >>>> I was trying to work out the max possible password length supported by radius and I think its 240 characters. I based this on the method by which >16 char passwords are encrypted in 16char chunks with the final chunk being padded out to 16 chars. Hence to be less than the max string allowed of 253 you can only have 15 chunks = 240 chars. Does this look OK? If it does, do vendors ensure they truncate passwords before encryption to an aaa server? I dont think anyone would ever enter a long password (unless they were trying to break the NAS/aaa server software). However I've seen noise (or PPP stuff) somehow get into a password - with various vendors. Luckily its never been long enough to cause the attribute length to wrap. Darran <<<<<<<< --------------------------------------------------------------- David Mitton 978-670-8888 Main Consulting Engineer, Nortel 978-916-4570 Direct Carrier Packet Networks, I&SP Group 978-916-4789 FAX Billerica, MA 01821 dmitton@baynetworks.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Thu Sep 24 11:06:29 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA03228 for ; Thu, 24 Sep 1998 11:06:29 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id HAA13959; Thu, 24 Sep 1998 07:46:50 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id HAA02784 for ietf-radius-outgoing; Thu, 24 Sep 1998 07:57:32 -0700 (PDT) Message-Id: <3.0.5.32.19980924110008.00abb300@fred.xylogics.com> X-Sender: mitton@fred.xylogics.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 24 Sep 1998 11:00:08 -0400 To: "Darran Potter" , From: Dave Mitton Subject: Re: (radius) max radius password In-Reply-To: <001601bde7c9$0787e070$0103a8c0@ds9> Mime-Version: 1.0 Content-Type: text/enriched; charset="us-ascii" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Dave Mitton And to your second point... been there, fixed that. Yes, we've seen PPP messages somehow get in CLI username/password prompts. And we had to fix the code to length check the input before proceeding. Depending on the implementation situation, you may also want to check for printable characters. (Since only real users should be coming through that interface. Save binary capabilities for the programatic interfaces) In the best case, the server may just reject the session because the garbage doesn't match any username. But even truncated, a server is hopefully not adversely sensitive to random binary strings in the username. Dave. At 03:38 PM 9/24/98 +0100, Darran Potter wrote: >>>> Good point. Arial-----Original Message----- From: ArialDave Mitton <<<dmitton@baynetworks.com> To: Darran Potter <<<darran@warp9.co.uk>; <ietf-radius@livingston.com <<<ietf-radius@livingston.com> Date: 24 September 1998 14:40 Subject: Re: (radius) max radius password Well, maybe in theory, except that Section 5.2 User-Password, page 22 of the RFC says that the password algorithm is repeated "to no more than 128 characters". And the next page says: Length: At least 18 and no larger than 130. Dave. At 09:16 AM 9/24/98 +0100, Darran Potter wrote: >>>> I was trying to work out the max possible password length supported by radius and I think its 240 characters. I based this on the method by which >16 char passwords are encrypted in 16char chunks with the final chunk being padded out to 16 chars. Hence to be less than the max string allowed of 253 you can only have 15 chunks = 240 chars. Does this look OK? If it does, do vendors ensure they truncate passwords before encryption to an aaa server? I dont think anyone would ever enter a long password (unless they were trying to break the NAS/aaa server software). However I've seen noise (or PPP stuff) somehow get into a password - with various vendors. Luckily its never been long enough to cause the attribute length to wrap. Darran <<<<<<<< --------------------------------------------------------------- David Mitton 978-670-8888 Main Consulting Engineer, Nortel 978-916-4570 Direct Carrier Packet Networks, I&SP Group 978-916-4789 FAX Billerica, MA 01821 dmitton@baynetworks.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. <<<<<<<< --------------------------------------------------------------- David Mitton 978-670-8888 Main Consulting Engineer, Nortel 978-916-4570 Direct Carrier Packet Networks, I&SP Group 978-916-4789 FAX Billerica, MA 01821 dmitton@baynetworks.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Thu Sep 24 11:06:35 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA03239 for ; Thu, 24 Sep 1998 11:06:31 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id HAA13954; Thu, 24 Sep 1998 07:46:47 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id HAA02702 for ietf-radius-outgoing; Thu, 24 Sep 1998 07:56:24 -0700 (PDT) Message-ID: <001601bde7c9$0787e070$0103a8c0@ds9> From: "Darran Potter" To: "Dave Mitton" , Subject: Re: (radius) max radius password Date: Thu, 24 Sep 1998 15:38:42 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0013_01BDE7D1.68BD27D0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Darran Potter" This is a multi-part message in MIME format. ------=_NextPart_000_0013_01BDE7D1.68BD27D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Good point. -----Original Message----- From: Dave Mitton To: Darran Potter ; ietf-radius@livingston.com = Date: 24 September 1998 14:40 Subject: Re: (radius) max radius password =20 =20 Well, maybe in theory, except that Section 5.2 User-Password, page = 22 of the RFC says that the password algorithm is repeated "to no more = than 128 characters". =20 And the next page says: Length: At least 18 and no larger than 130. =20 Dave. =20 At 09:16 AM 9/24/98 +0100, Darran Potter wrote:=20 >>>> =20 I was trying to work out the max possible password length = supported by radius and I think its 240 characters. I based this on the = method by which >16 char passwords are encrypted in 16char chunks with = the final chunk being padded out to 16 chars. =20 Hence to be less than the max string allowed of 253 you can only = have 15 chunks =3D 240 chars. =20 Does this look OK? If it does, do vendors ensure they truncate = passwords before encryption to an aaa server? =20 I dont think anyone would ever enter a long password (unless = they were trying to break the NAS/aaa server software). However I've seen = noise (or PPP stuff) somehow get into a password - with various = vendors. Luckily its never been long enough to cause the attribute length to = wrap. =20 Darran =20 =20 <<<< =20 =20 =20 --------------------------------------------------------------- David Mitton 978-670-8888 Main Consulting Engineer, Nortel 978-916-4570 Direct Carrier Packet Networks, I&SP Group 978-916-4789 FAX Billerica, MA 01821 dmitton@baynetworks.com - To unsubscribe, email = 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of = the message. ------=_NextPart_000_0013_01BDE7D1.68BD27D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Good point.
-----Original = Message-----
From:=20 Dave Mitton <dmitton@baynetworks.com>To:=20 Darran Potter <darran@warp9.co.uk>; ietf-radius@livingston.com= =20 <ietf-radius@livingston.com= >
Date:=20 24 September 1998 14:40
Subject: Re: (radius) max = radius=20 password

Well, maybe in theory, except that = Section 5.2=20 User-Password, page 22 of the RFC says that the password algorithm = is=20 repeated "to no more than 128 characters".

And the = next=20 page says: Length: At least 18 and no larger than=20 130.

Dave.

At 09:16 AM 9/24/98 +0100, Darran Potter = wrote:=20
>>>>
I was trying to work out the max possible password = length=20 supported
by radius and I think its 240 characters. I based = this on=20 the method
by which >16 char passwords are encrypted in = 16char=20 chunks with the
final chunk being padded out to 16=20 chars.

Hence to be less than the max string allowed of = 253 you=20 can only have
15 chunks =3D 240 chars.

Does this look = OK? If it=20 does, do vendors ensure they truncate passwords
before = encryption to=20 an aaa server?

I dont think anyone would ever enter a = long=20 password (unless they were
trying to break the NAS/aaa server = software). However I've seen noise
(or PPP stuff) somehow get = into a=20 password - with various vendors. Luckily
its never been long = enough=20 to cause the attribute length to=20 = wrap.

Darran

<<<<



-= --------------------------------------------------------------
David=20 Mitton 978-670-8888 Main
Consulting Engineer, Nortel 978-916-4570 = Direct
Carrier Packet Networks, I&SP Group 978-916-4789=20 FAX
Billerica, MA 01821 dmitton@baynetworks.com - To unsubscribe, = email=20 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the = body of the=20 message. ------=_NextPart_000_0013_01BDE7D1.68BD27D0-- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Thu Sep 24 11:49:19 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA04833 for ; Thu, 24 Sep 1998 11:49:18 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id IAA15464; Thu, 24 Sep 1998 08:33:12 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id IAA07323 for ietf-radius-outgoing; Thu, 24 Sep 1998 08:43:55 -0700 (PDT) From: Ralf Schandl To: Subject: Re: (radius) max radius password Message-ID: <5120010016589016000002L162*@MHS> Date: Thu, 24 Sep 1998 15:36:15 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Ralf Schandl Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA04833 > And the next page says: Length: At least 18 and no larger than 130 From owner-ietf-radius@livingston.com Fri Sep 25 02:57:52 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id CAA00246 for ; Fri, 25 Sep 1998 02:57:51 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id XAA18991; Thu, 24 Sep 1998 23:41:16 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id XAA20453 for ietf-radius-outgoing; Thu, 24 Sep 1998 23:51:39 -0700 (PDT) Message-ID: <360B3EEE.6C628F7F@iea-software.com> Date: Thu, 24 Sep 1998 23:57:50 -0700 From: "Dale E. Reed Jr." Organization: IEA Software, Inc. X-Mailer: Mozilla 4.06 [en] (WinNT; I) MIME-Version: 1.0 To: Darran Potter CC: ietf-radius@livingston.com Subject: Re: (radius) max radius password References: <005601bde793$ae399520$0103a8c0@ds9> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Script: \\FilterScript.mml X-DomainScript: warp9.co.uk\\script.mml X-UserScript: livingston.com\ietf-radius\script.mml Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Dale E. Reed Jr." > Darran Potter wrote: > > I was trying to work out the max possible password length supported > by radius and I think its 240 characters. I based this on the method > by which >16 char passwords are encrypted in 16char chunks with the > final chunk being padded out to 16 chars. > > Hence to be less than the max string allowed of 253 you can only have > 15 chunks = 240 chars. > > Does this look OK? If it does, do vendors ensure they truncate > passwords before encryption to an aaa server? This *IS* specified in the RFC in section 5.2: ---------------------------- Type 2 for User-Password. Length At least 18 and no larger than 130. String The String field is between 16 and 128 octets long, inclusive. ---------------------------- So 128 would be the definitive answer. -- Dale E. Reed Jr. (daler@iea-software.com) _________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Fri Sep 25 10:52:08 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA06789 for ; Fri, 25 Sep 1998 10:52:07 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id HAA25764; Fri, 25 Sep 1998 07:34:58 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id HAA07301 for ietf-radius-outgoing; Fri, 25 Sep 1998 07:41:09 -0700 (PDT) Message-ID: <00d401bde892$202c10f0$c889e9cc@titanium.techapp.com> From: "Russell J. LeBar" To: "RADIUS" Subject: Re: (radius) max radius password Date: Fri, 25 Sep 1998 09:38:05 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Russell J. LeBar" I would not expect a NAS to send a null terminator (which still leaves one octet free) nor would I expect a LF and/or CR. So what is up with the extra two octets? -----Original Message----- From: Dale E. Reed Jr. > Length > > At least 18 and no larger than 130. > > String > > The String field is between 16 and 128 octets long, inclusive. -- Russell J. LeBar - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Fri Sep 25 11:26:05 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA07923 for ; Fri, 25 Sep 1998 11:26:05 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id IAA27587; Fri, 25 Sep 1998 08:09:43 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id IAA10729 for ietf-radius-outgoing; Fri, 25 Sep 1998 08:18:35 -0700 (PDT) Message-Id: <3.0.5.32.19980925112106.02fa9b60@fred.xylogics.com> X-Sender: mitton@fred.xylogics.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 25 Sep 1998 11:21:06 -0400 To: "Russell J. LeBar" , "RADIUS" From: Dave Mitton Subject: Re: (radius) max radius password In-Reply-To: <00d401bde892$202c10f0$c889e9cc@titanium.techapp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Dave Mitton All RADIUS attribute length values include their type and length fields. (not sure why, "but just like the bees in your head, there they are!") Dave. Quotation: Firesign Theater, "I Think We're all Bozo's on this Bus" At 09:38 AM 9/25/98 -0500, Russell J. LeBar wrote: >I would not expect a NAS to send a null terminator (which still leaves one >octet free) nor would I expect a LF and/or CR. So what is up with the extra >two octets? > >-----Original Message----- >From: Dale E. Reed Jr. > >> Length >> >> At least 18 and no larger than 130. >> >> String >> >> The String field is between 16 and 128 octets long, inclusive. > > >-- Russell J. LeBar > >- >To unsubscribe, email 'majordomo@livingston.com' with >'unsubscribe ietf-radius' in the body of the message. > > --------------------------------------------------------------- David Mitton 978-670-8888 Main Consulting Engineer, Nortel 978-916-4570 Direct Carrier Packet Networks, I&SP Group 978-916-4789 FAX Billerica, MA 01821 dmitton@baynetworks.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Fri Sep 25 19:04:04 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id TAA17796 for ; Fri, 25 Sep 1998 19:04:03 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id PAA14780; Fri, 25 Sep 1998 15:47:14 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id PAA27354 for ietf-radius-outgoing; Fri, 25 Sep 1998 15:56:08 -0700 (PDT) Message-ID: <016801bde8d7$468a66d0$c889e9cc@titanium.techapp.com> From: "Russell J. LeBar" To: "RADIUS" Subject: Re: (radius) max radius password Date: Fri, 25 Sep 1998 17:53:13 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0165_01BDE8AD.5D9739E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Russell J. LeBar" This is a multi-part message in MIME format. ------=_NextPart_000_0165_01BDE8AD.5D9739E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Duh! I was thinking of the string length, not the length of the AVP. -----Original Message----- From: Dave Mitton > > All RADIUS attribute length values include their type and length fields. >(not sure why, "but just like the bees in your head, there they are!") ------=_NextPart_000_0165_01BDE8AD.5D9739E0 Content-Type: text/x-vcard; name="Russell J. LeBar.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Russell J. LeBar.vcf" BEGIN:VCARD VERSION:2.1 N:LeBar;Russell;J.; FN:Russell J. LeBar ORG:Technology Applications, Inc.;Windows System Administration; RADIUS = Engineer TITLE:Software Engineer TEL;WORK;VOICE:(314) 733-5234 ; 1-800-854-9005; 1-800-854-9006 TEL;WORK;FAX:(314) 733-5252 ADR;WORK;ENCODING=3DQUOTED-PRINTABLE:;;900 Roosevelt = Pkwy.=3D0D=3D0ASuite 350;Chesterfield;MO;63017;USA LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:900 Roosevelt = Pkwy.=3D0D=3D0ASuite 350=3D0D=3D0AChesterfield, MO 63017=3D0D=3D0AUSA URL:http://www.techapp.com URL:http://www.techapp.com EMAIL;PREF;INTERNET:rjl@techapp.com REV:19980925T225313Z END:VCARD ------=_NextPart_000_0165_01BDE8AD.5D9739E0-- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Sun Sep 27 04:50:04 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id EAA01242 for ; Sun, 27 Sep 1998 04:49:53 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id BAA16165; Sun, 27 Sep 1998 01:33:19 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id BAA01686 for ietf-radius-outgoing; Sun, 27 Sep 1998 01:41:36 -0700 (PDT) Message-ID: <49732B786CD4D111A04500A0C9AF50189CF591@nds-il-ex2.ilndc.com> From: "Maarek, llan" To: "'radius'" Subject: (radius) radius frame on sniffer Date: Sun, 27 Sep 1998 10:37:57 +0200 X-MS-TNEF-Correlator: <49732B786CD4D111A04500A0C9AF50189CF591@nds-il-ex2.ilndc.com> MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01BDE9F2.247D22A0" Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Maarek, llan" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01BDE9F2.247D22A0 Content-Type: text/plain hi , Somebody know if exist a RADIUS protocol package on sniffer to read & understand the radius frames on the network. Thanks Ilan Maarek I & T Group Network System Engineer NDS technologies ltd. Tel: 02-5894772 E-mail : imaarek@ndsisrael.com ------_=_NextPart_000_01BDE9F2.247D22A0 Content-Type: application/ms-tnef Content-Transfer-Encoding: base64 eJ8+IgUIAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQWAAwAOAAAAzgcJABsACgAlADkAAABhAQEggAMADgAAAM4HCQAb AAoAJgADAAAALAEBCYABACEAAAA4MjVDMzE5M0RGNTVEMjExQTA3RDAwQTAyNEIyRkY3MQAJBwEE gAEAGAAAAHJhZGl1cyBmcmFtZSBvbiBzbmlmZmVyAL0IAQ2ABAACAAAAAgACAAEDkAYAxAcAAC4A AAADAACACCAGAAAAAADAAAAAAAAARgAAAABShQAAFRIAAB4AAYAIIAYAAAAAAMAAAAAAAABGAAAA AFSFAAABAAAABQAAADguMDMAAAAAAwACgAggBgAAAAAAwAAAAAAAAEYAAAAAAYUAAAAAAAALAAOA CCAGAAAAAADAAAAAAAAARgAAAAADhQAAAAAAAAsABIAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAA AAAAAwAFgAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAADAAaACCAGAAAAAADAAAAAAAAARgAA AAARhQAAAAAAAAMAB4AIIAYAAAAAAMAAAAAAAABGAAAAABiFAAAAAAAAHgAIgAggBgAAAAAAwAAA AAAAAEYAAAAANoUAAAEAAAABAAAAAAAAAB4ACYAIIAYAAAAAAMAAAAAAAABGAAAAADeFAAABAAAA AQAAAAAAAAAeAAqACCAGAAAAAADAAAAAAAAARgAAAAA4hQAAAQAAAAEAAAAAAAAAAgEJEAEAAAB+ AQAAegEAAPMBAABMWkZ1Lm+KyAMACgByY3BnMTI10jIA+zM2AeggAqQD4wkCAGNoCsBzZXQwPiAH EwKDAFAC8hC5VGGWaANxAoB9CoF1YwBQiwsDC2BuDhAwMzMMYBRsbgIgZQumIGhpXCAsCqIKhAqA UwNwZeEG4GR5IGsVEAfgBpBYIGV4BAAFQGEH8EEoRElVBfBwA2B0bwcI4RjQANBrYWdlILkCICBz AwABIASQIBkQAiAJcGFkICYgdZ5uBIEYIABwGwB0aBnQsnIa8Gl1BCADUGEHgicZ8RvyFTB0dwWw ay7PFioK8xMAEOBuaxCgFjmWSRRhBdBhCsBlax/lkRsRVCBHA2B1cBYkFwfAHaMGAHkYIGVtIK5F FIALgAngciIFRAXwPyMQENAVEAkAI3AHkWx0AmQd9VRlbDogMIAyLTU4OTQ3AcDvHmkMwQHBI0At AMADESYQ2wdwIKNAG1AAkHMcMCXwii4FoG0R43MxNybaFwu2FjMTkQAsIAAAAwAmAAAAAAADADYA AAAAAAsAAgABAAAAAgExAAEAAAAbAQAAUENERkVCMDkAAQACAHIAAAAAAAAAOKG7EAXlEBqhuwgA KypWwgAARU1TTURCLkRMTAAAAAAAAAAAG1X6IKpmEc2byACqAC/EWgwAAABORFMtSUwtRVgyAC9v PU5EUy9vdT1ORFMtSkVSL2NuPVJlY2lwaWVudHMvY249SW1hYXJlawAuAAAAAAAAAFABcUN0StIR oH0AoCSy/3EBAElzK3hs1NERoEUAoMmvUBgAAACbgrAAAAAAAAAuAAAAAAAAAFABcUN0StIRoH0A oCSy/3EBAElzK3hs1NERoEUAoMmvUBgAAACbgrEAABAAAACCXDGT31XSEaB9AKAksv9xGAAAAHJh ZGl1cyBmcmFtZSBvbiBzbmlmZmVyAAAeAHAAAQAAABgAAAByYWRpdXMgZnJhbWUgb24gc25pZmZl cgACAXEAAQAAABYAAAABvenyJVqG0LpYVeoR0qHfAGAIYFC+AABAADkAAAXBIPLpvQEDAPE/CQQA AB4AMUABAAAACAAAAElNQUFSRUsAAwAaQAAAAAAeADBAAQAAAAgAAABJTUFBUkVLAAMAGUAAAAAA AwD9P+QEAAADAIAQ/////wIBRwABAAAAMAAAAGM9VVM7YT0gO3A9TkRTO2w9TkRTLUlMLUVYMi05 ODA5MjcwODM3NTdaLTE4Mjk1AAIB+T8BAAAARwAAAAAAAADcp0DIwEIQGrS5CAArL+GCAQAAAAAA AAAvTz1ORFMvT1U9TkRTLUpFUi9DTj1SRUNJUElFTlRTL0NOPUlNQUFSRUsAAB4A+D8BAAAADQAA AE1hYXJlaywgbGxhbgAAAAAeADhAAQAAAAgAAABJTUFBUkVLAAIB+z8BAAAARwAAAAAAAADcp0DI wEIQGrS5CAArL+GCAQAAAAAAAAAvTz1ORFMvT1U9TkRTLUpFUi9DTj1SRUNJUElFTlRTL0NOPUlN QUFSRUsAAB4A+j8BAAAADQAAAE1hYXJlaywgbGxhbgAAAAAeADlAAQAAAAgAAABJTUFBUkVLAEAA BzBIpqTl8em9AUAACDCgIn0k8um9AR4APQABAAAAAQAAAAAAAAAeAB0OAQAAABgAAAByYWRpdXMg ZnJhbWUgb24gc25pZmZlcgAeADUQAQAAAD4AAAA8NDk3MzJCNzg2Q0Q0RDExMUEwNDUwMEEwQzlB RjUwMTg5Q0Y1OTFAbmRzLWlsLWV4Mi5pbG5kYy5jb20+AAAACwApAAEAAAALACMAAQAAAAMABhAA y6RnAwAHEMkAAAADABAQAAAAAAMAERAAAAAAHgAIEAEAAABlAAAASEksU09NRUJPRFlLTk9XSUZF WElTVEFSQURJVVNQUk9UT0NPTFBBQ0tBR0VPTlNOSUZGRVJUT1JFQUQmVU5ERVJTVEFORFRIRVJB RElVU0ZSQU1FU09OVEhFTkVUV09SS1RIQQAAAAACAX8AAQAAAD4AAAA8NDk3MzJCNzg2Q0Q0RDEx MUEwNDUwMEEwQzlBRjUwMTg5Q0Y1OTFAbmRzLWlsLWV4Mi5pbG5kYy5jb20+AAAAOaM= ------_=_NextPart_000_01BDE9F2.247D22A0-- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Sun Sep 27 12:07:14 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id MAA03999 for ; Sun, 27 Sep 1998 12:07:14 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id IAA18765; Sun, 27 Sep 1998 08:51:07 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id JAA08320 for ietf-radius-outgoing; Sun, 27 Sep 1998 09:01:16 -0700 (PDT) From: "Bernard Aboba" To: "Maarek, llan" , "'radius'" Subject: Re: (radius) radius frame on sniffer Date: Sun, 27 Sep 1998 08:39:37 -0700 Message-Id: <01bdea2d$08b94770$0f8939cc@e1kj2.internaut.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-Mimeole: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Bernard Aboba" For what it's worth, NT 5 Beta 2 has a RADIUS-capable sniffer (NetMon). -----Original Message----- From: Maarek, llan To: 'radius' Date: Sunday, September 27, 1998 4:04 AM Subject: (radius) radius frame on sniffer >hi , > >Somebody know if exist a RADIUS protocol package on sniffer to read & >understand the radius frames on the network. > >Thanks > >Ilan Maarek >I & T Group >Network System Engineer >NDS technologies ltd. >Tel: 02-5894772 >E-mail : imaarek@ndsisrael.com > > - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Sun Sep 27 12:28:30 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id MAA04229 for ; Sun, 27 Sep 1998 12:28:29 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id JAA19207; Sun, 27 Sep 1998 09:12:29 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id JAA08887 for ietf-radius-outgoing; Sun, 27 Sep 1998 09:23:30 -0700 (PDT) Date: Sun, 27 Sep 1998 11:22:18 -0500 (CDT) From: John Arden Subject: Re: (radius) radius frame on sniffer To: ietf-radius@livingston.com In-Reply-To: "Your message with ID" <01bdea2d$08b94770$0f8939cc@e1kj2.internaut.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: John Arden use snoop on your solaris box. >hi , > >Somebody know if exist a RADIUS protocol package on sniffer to read & >understand the radius frames on the network. > >Thanks > >Ilan Maarek >I & T Group >Network System Engineer >NDS technologies ltd. >Tel: 02-5894772 >E-mail : imaarek@ndsisrael.com > > - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Mon Sep 28 11:58:48 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA02129 for ; Mon, 28 Sep 1998 11:58:48 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id IAA10069; Mon, 28 Sep 1998 08:42:22 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id IAA24135 for ietf-radius-outgoing; Mon, 28 Sep 1998 08:51:15 -0700 (PDT) Message-Id: <199809281547.KAA02572@madhatter.surfhappy.net> From: "ITRANS Support" Organization: Internet Transaction Services, Inc. To: ietf-radius@livingston.com Date: Mon, 28 Sep 1998 10:46:50 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: (radius) max radius password Priority: normal In-reply-to: <005601bde793$ae399520$0103a8c0@ds9> Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "ITRANS Support" On 24 Sep 98 at 9:16, Darran Potter wrote: > I was trying to work out the max possible password length supported > by radius and I think its 240 characters. I based this on the method > by which >16 char passwords are encrypted in 16char chunks with the > final chunk being padded out to 16 chars. > I haven't checked it lately, but about 2 years ago we did some tests with Ascend and they did NOT recalculate the MD5 hash after every 16 octets, rather the original hash was used for the entire password. As I recall at least one other vendor we tested with did the same thing, but I can't say for sure. Anybody checked this out lately??? Martin ------------------------------------------------------------------------- Internet Transaction Services, Inc. http://www.itrans.com mailto:support@itrans.com mailto:sales@itrans.com ------------------------------------------------------------------------- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Sep 29 13:31:20 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA16966 for ; Tue, 29 Sep 1998 13:31:19 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id KAA03721; Tue, 29 Sep 1998 10:10:08 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id KAA15706 for ietf-radius-outgoing; Tue, 29 Sep 1998 10:13:44 -0700 (PDT) From: info@cyber-host.net Message-Id: <199809292058.QAA01807@mars.your-mail.com> To: user@the.internet Date: Tue, 29 Sep 98 05:39:03 EST Subject: (radius) AD: Your Computer Makes Money While You Sleep Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: info@cyber-host.net This message is sent in compliance with the new e-mail bill: SECTION 301, Paragraph (a)(2)(C) of s. 1618 Sender : Quantum Tech, INC., 694 Rocky Woods Cove, Cordova, TN 38018 Phone : 1-901-737-8667 E-mail : info@cyber-host.net To be removed from our mailing list, simply reply with "REMOVE" in the subject. Could you use another income, but don't want to leave your day job? Here is the Answer. A Leader in the Computer Industry has developed an automated system that allows your computer to go to work and earn major income. You provide business services to professionals and companies through your computer and modem....and it works while you sleep! You get everything you need.... 1. Software and programming developed by the Industry's Leader. 2. Your own technical support and customer service staff to get you started and keep you up and running. Let us fill in all the details, NOW! Please visit our website at http://www.cyber-host.net/opportunity for full details! Or CALL NOW: 1-901-737-8667 (This is not a 900 number, it's our area code! If you would like us to call you, include your phone number in your e-mail) Quantum Tech, INC. 694 Rocky Woods Cove Cordova, TN 38018 *************************************************** - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Sep 29 18:13:17 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id SAA21867 for ; Tue, 29 Sep 1998 18:13:16 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id NAA13435; Tue, 29 Sep 1998 13:19:36 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id NAA08600 for ietf-radius-outgoing; Tue, 29 Sep 1998 13:28:59 -0700 (PDT) Message-ID: <009c01bdebe7$23d9f020$0137a8c0@glennz-2.dns.microsoft.com> From: "Glen Zorn" To: "Harald Tveit Alvestrand" , "Bert Wijnen" Cc: "RADIUS" , "Beadles, Mark A." , "pcalhoun@eng.sun.com" , "Glen Zorn" Subject: (radius) Re: draft-ietf-radius-acct-interim-01.txt has expired! Date: Tue, 29 Sep 1998 13:22:12 -0700 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_008F_01BDEBAC.2B1A7B60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2120.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: "Glen Zorn" This is a multi-part message in MIME format. ------=_NextPart_000_008F_01BDEBAC.2B1A7B60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit And have just resubmitted the draft on tunnel authentication attributes; for the second time in a row, without substantive change. I have asked the WG Chair to make WG Last Call on my draft _twice_ and nothing has happenened. I don't like to complain (too much ;-), but the ridiculousness of this situation is verging on the sublime. I think that it is well past time for the ADs to take action: if the RADIUS WG is dead, fine, but let's att least give it a decent burial. I propose that Carl Rigney be replaced as both WG Chair and editor of the RADIUS Extensions draft. I'm sure he won't mind (since he seems to have lost all interest) and if the new chair is at least breathing, perhaps we can truly finish the work on which we have spent so much time and energy. -----Original Message----- From: Beadles, Mark A. To: 'Glen Zorn' ; pcalhoun@eng.sun.com ; Beadles, Mark A. ; alexr@uu.net Date: Tuesday, September 29, 1998 12:51 PM Subject: RE: draft-ietf-radius-acct-interim-01.txt has expired! >Yes, and draft-ietf-radius-ext-02, which is supposed to be where the >information was going, has not yet appeared! > >+ Mark Anthony Beadles + WorldCom Advanced Networks + >+ mbeadles@wcom.net + http://www.wcom.net + >+ Voice 614.723.1941 + Fax 614.723.8407 + > > >-----Original Message----- >From: Glen Zorn [mailto:gwz@pinky.microsoft.com] >Sent: Tuesday, 29 September 1998 15:54 >To: pcalhoun@eng.sun.com; Mark Beadles; alexr@uu.net >Subject: draft-ietf-radius-acct-interim-01.txt has expired! > > > > ------=_NextPart_000_008F_01BDEBAC.2B1A7B60 Content-Type: text/x-vcard; name="Glen Zorn.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Glen Zorn.vcf" BEGIN:VCARD VERSION:2.1 N:Zorn;Glen FN:Glen Zorn EMAIL;PREF;INTERNET:glennz@microsoft.com REV:19980929T202212Z END:VCARD ------=_NextPart_000_008F_01BDEBAC.2B1A7B60-- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Tue Sep 29 21:19:36 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id VAA23787 for ; Tue, 29 Sep 1998 21:19:36 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id SAA24062; Tue, 29 Sep 1998 18:14:40 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id SAA04099 for ietf-radius-outgoing; Tue, 29 Sep 1998 18:11:46 -0700 (PDT) Date: Tue, 29 Sep 1998 18:11:45 -0700 (PDT) From: Carl Rigney Message-Id: <199809300111.SAA04091@server.livingston.com> To: ietf-radius@livingston.com Subject: (radius) Busy, not bored Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Carl Rigney No, I haven't lost interest in RADIUS, I've just been extra-busy. I'm now back and wading through my backlog on the mailing list, and will then kick out a flurry of updated drafts. -- Carl Rigney cdr@livingston.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message. From owner-ietf-radius@livingston.com Wed Sep 30 10:14:30 1998 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA09219 for ; Wed, 30 Sep 1998 10:14:29 -0400 (EDT) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.8.5/8.6.9) with ESMTP id HAA10591; Wed, 30 Sep 1998 07:09:21 -0700 (PDT) Received: (from majordom@localhost) by server.livingston.com (8.8.5/8.6.9) id HAA04031 for ietf-radius-outgoing; Wed, 30 Sep 1998 07:07:37 -0700 (PDT) Message-Id: <199809301405.KAA09096@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce:; Cc: ietf-radius@livingston.com From: Internet-Drafts@ietf.org Subject: (radius) I-D ACTION:draft-ietf-radius-tunnel-auth-06.txt Date: Wed, 30 Sep 1998 10:05:33 -0400 Sender: owner-ietf-radius@livingston.com Precedence: bulk Reply-To: Internet-Drafts@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Remote Authentication Dial-In User Service Working Group of the IETF. Title : RADIUS Attributes for Tunnel Protocol Support Author(s) : G. Zorn, D. Leifer, A. Rubens, J. Shriver Filename : draft-ietf-radius-tunnel-auth-06.txt Pages : 16 Date : 29-Sep-98 This document defines a set of RADIUS attributes designed to support the provision of compulsory tunneling in dial-up networks. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-radius-tunnel-auth-06.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-radius-tunnel-auth-06.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-radius-tunnel-auth-06.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980929171137.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-radius-tunnel-auth-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-radius-tunnel-auth-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980929171137.I-D@ietf.org> --OtherAccess-- --NextPart-- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe ietf-radius' in the body of the message.