Re: adding new cipher support to kernel
Riaan: do you have a newer version of your patchset, or can I use the latest you sent to me ? Yvan: The last one I sent, I believe it was named aesgcm_cleaned.diff is the latest. If there is anything I can help with, just say. I know I am not Mr. Speedy, but I would like to help if I can :) Yvan Dylan: Strongswan does not support aes gcm for freebsd; it does not have the pfkey identifier in its kernel_pfkey plugin. All it needs is the identifier in its kernel_pfkey plugin. We have a simple strongswan patch for that. The identifier is defined in the freebsd aes gcm patches that Yvan is looking at. Riaan ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
AES-GCM in FreeBSD
We wish to implement AES-GCM in the FreeBSD OCF whith the main aim of using it in IPsec [a]. I have a number of questions: 1. What mailing list is the most appropriate for questions and comments related to this subject? 2. What is the best way to share any work done? (pacthes to mailing list?) 3. Is it best to work of HEAD when implementing the solution? 4. We aim to port the work done for openbsd [b][c]. Does anybody know of any specific pitfalls, gotchas etc. when using this approach? (E.g.I assume the FreeBSD OCF has diverged from OpenBSDs over the years) [a] - RFC4106: The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP), http://tools.ietf.org/html/rfc4106 [b] - AES-GCM Part 1: AES-GCM implementation, http://marc.info/?t=12823311051r=1w=2 [c] - AES-GCM Part 2: PFKEY/ESP, http://marc.info/?t=12825877369r=1w=2 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: kgdb error: Ignoring packet error, continuing....
On Thu, Jul 3, 2008 at 1:47 PM, karim sk [EMAIL PROTECTED] wrote: Hi, I am trying to setup kgdb on serial console in freebsd. I have done the following steps. 1. Compile the kernel with the following options options DDB options KDB makeoptions DEBUG-g 2.Installed the kernel on the target machine. 3. Transferred the kernel.debug to host machine. 4. Modified the file /boot/device.hints in the target machine to have sio flags as hint.sio.0.at=isa hint.sio.0.port=0X3F8 hint.sio.0.flags=0x80 hint.sio.0.irq=4 5. Reboot the target machine. At the loader prompt type the following set comconsole_speed=9600 boot -d Then the target machine stops at ddb prompt. 6.In the host machine type the following at kgdb prompt kgdb set remotebaud 9600 kgdb file kernel.debug kgdb target remote /dev/cuad0 This is not able to establish the connection. It is giving following errors. Ignoring packet error, continuing... Ignoring packet error, continuing... Couldn't establish connection to remote target. Malformed response to offset query, timeout. Can any body tell why packet error is coming when kgdb is trying to establish the connection. Thanks in advance. Karim I am not sure if it will help but according to on http://www.lemis.com/grog/Papers/Debug-tutorial/tutorial.pdf the target : You choose a serial port by setting bit 0x80 of the device flags in /boot/loader.conf : hint.sio.0.flags=0x90 In this example, bit 0x10 is also set to tell the kernel gdb stub to access remote debugging via this port. Hope it helps Riaan PS. Sorry previous reply was only to Karin and not to the list as well. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
