Crypto help. Looking for AES/CFB8 on standard library.

[Carlos Cobo]

Hi there gophers,

I'm implementing a server in Go that requires AES/CFB8, client uses it.

I tried with using crypto/cipher's NewCFBEncrypter and NewCFBDecrypter but I get weird errors from the client.

I found a helpful guy on IRC that pointed me to a CFB8 implementation made by some other guy in haXe. That one works nicely.

I'm a crypto newbie so I just want some help figuring out why the std version doesn't work or why does it produce different crypto output.

I Google'd a bit but almost everything mentions just CFB not CFB8. Is it the same?

http://play.golang.org/p/LTbId4b6M2

Thanks in advance,

Carlos

[Péter Szilágyi]

Hi,

  Looking at the haXe code you linked in, the first obvious difference that occurred to me is that this CFB8 has a block size of 8 bits, whilst the generic CFB uses the block size of AES (namely 128 bits). This is pretty much a deal breaker (i.e. the Go standard lib does not support 8bit CFB, and to tell the truth, I very much doubt it will).

  Any reason why you want an 8bit CFB instead of the 128bit one, beside the already existing code base?

Cheers,

  Peter

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Carlos Cobo]

So that's it.. Can't use Go's std to deal with this.

Most of the time I find what I want on Go's std, that's why I asked.

It's not a requirement for me, just for this server I'm coding.