Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Karlnet\]\s+SEC\s+Gold\s+client\s+\+\s+Encryption\s+\+\s+Cisco\s+350BR\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Karlnet\]\s+SEC\s+Gold\s+client\s+\+\s+Encryption\s+\+\s+Cisco\s+350BR\s*$/: 3 ]

Total 3 documents matching your query.

1. [Karlnet] SEC Gold client + Encryption + Cisco 350BR (score: 1): Author: "Bob Hrbek" <bhrbek@jagwireless.com>; Date: Sat, 19 Jul 2003 07:31:54 -0500; Anybody have encryption between a SEC Client and a Cisco 350 Bridge? I find it completely stupid that you cannot specify anything but "alphanumeric" encryption on the SEC and nothing but "HEX" encryp; /archives//html/Karlnet/2003-07/msg00168.html (8,411 bytes)
2. Re: [Karlnet] SEC Gold client + Encryption + Cisco 350BR (score: 1): Author: "Brendan O'Bra" <brendan@pvbb.net>; Date: Sat, 19 Jul 2003 07:47:15 -0700; Why not just translate the alphanumeric that's on the SEC into hex? That's what we do dor stuff that doesn't play nice. Use: http://www.asciitable.com/ Bob Hrbek wrote: Anybody have encryption betwee; /archives//html/Karlnet/2003-07/msg00169.html (9,251 bytes)
3. Re: [Karlnet] SEC Gold client + Encryption + Cisco 350BR (score: 1): Author: "Bob Hrbek" <bhrbek@jagwireless.com>; Date: Sat, 19 Jul 2003 10:18:13 -0500; THANK YOU SO MUCH!!!! I can't believe I never made the relationship. DUH!! That's the Anybody; /archives//html/Karlnet/2003-07/msg00170.html (10,055 bytes)

Current List: 1 - 3
Page: [1]