Thanks, Dan. I'll test this on OpenSolaris and if the same issue occurs I'll post the output here. The key itself is a test key that I use elsewhere with no problems; in particular with a device that supports *only* 256 bit keys. If it's broken, my tests have a lot of 'splainin to do. :)
On Tue, Sep 16, 2008 at 5:18 PM, Dan McDonald <[EMAIL PROTECTED]> wrote: > On Tue, Sep 16, 2008 at 04:46:49PM -0700, Fred Medlin wrote: > > Can anyone point me to docs or src to help me understand why I can load > 192 > > bit aes-cbc keys, but not 256 bit?The error claims it is an unsupported > > keysize. I'm running solaris 10/4 on an ultra 45. > > First off, technically, this isn't an S10 mailing list. You pay for S10 > support. > > OTOH, that's very odd behavior. Usually it's either just-128-bit or > all-sizes. > > Can you try putting "/256" at the end of your 256-bit key? That eliminates > errors from too-many digits, and gets ipseckey to barf if it's too-few. > > Can you show us: > > 1.) Your ipseckey(1M) input file? > > 2.) The results of: > > ipseckey -npv -f <your-file> > > I suspect you're entering a != 256-bit key. > > Dan >
_______________________________________________ networking-discuss mailing list [email protected]
