USB digital camera erroneously says "no medium found"
Hello I have Nikon Coolpix 2000 digital camera which was working well on my old Linux 2.6.? machine. After moving to a different one while the old one is not accessible, where the new one has Linux version 2.6.13, I found it doesn't work anymore. When compact flash is inside the camera, camera turned on and connected, cat /dev/sda says no media found. cat /dev/sdb, /dev/sdc, /dev/sdd say no such file or directory. If I take the compact flash card out and stick it into "roline 8in1 card reader", it works perfectly. This reader puts the cards also as SCSI disks on /dev/sda.../dev/sdd. Attaching the camera with CF inside to Windows 2000 machine also works perfectly. dmesg: usb-storage: waiting for device to settle before scanning Vendor: NIKON Model: DSC E2000 Rev: 1.00 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 507905 512-byte hdwr sectors (260 MB) sda: Write Protect is off sda: Mode Sense: 04 00 00 00 sda: assuming drive cache: write through SCSI device sda: 507905 512-byte hdwr sectors (260 MB) sda: Write Protect is off sda: Mode Sense: 04 00 00 00 sda: assuming drive cache: write through sda: sda1 Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0 Attached scsi generic sg0 at scsi4, channel 0, id 0, lun 0, type 0 usb-storage: device scan complete [EMAIL PROTECTED]:~$ /sbin/lspci | grep USB :00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01) :00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01) :00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01) :00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01) What should I investigate and send to diagnose the problem? CL< - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
USB digital camera erroneously says no medium found
Hello I have Nikon Coolpix 2000 digital camera which was working well on my old Linux 2.6.? machine. After moving to a different one while the old one is not accessible, where the new one has Linux version 2.6.13, I found it doesn't work anymore. When compact flash is inside the camera, camera turned on and connected, cat /dev/sda says no media found. cat /dev/sdb, /dev/sdc, /dev/sdd say no such file or directory. If I take the compact flash card out and stick it into roline 8in1 card reader, it works perfectly. This reader puts the cards also as SCSI disks on /dev/sda.../dev/sdd. Attaching the camera with CF inside to Windows 2000 machine also works perfectly. dmesg: usb-storage: waiting for device to settle before scanning Vendor: NIKON Model: DSC E2000 Rev: 1.00 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 507905 512-byte hdwr sectors (260 MB) sda: Write Protect is off sda: Mode Sense: 04 00 00 00 sda: assuming drive cache: write through SCSI device sda: 507905 512-byte hdwr sectors (260 MB) sda: Write Protect is off sda: Mode Sense: 04 00 00 00 sda: assuming drive cache: write through sda: sda1 Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0 Attached scsi generic sg0 at scsi4, channel 0, id 0, lun 0, type 0 usb-storage: device scan complete [EMAIL PROTECTED]:~$ /sbin/lspci | grep USB :00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01) :00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01) :00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01) :00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01) What should I investigate and send to diagnose the problem? CL - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
man sendto ENOBUFS desc. wrong
man send(2): " ENOBUFS The output queue for a network interface was full. This gener- ally indicates that the interface has stopped sending, but may be caused by transient congestion. (Normally, this does not occur ^^^ in Linux. Packets are just silently dropped when a device queue ^^^ overflows.)" ^^ Which is not true, because just happened to me with kernel Linux version 2.6.11-gentoo-r9. Where should I report? CL< - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
man sendto ENOBUFS desc. wrong
man send(2): ENOBUFS The output queue for a network interface was full. This gener- ally indicates that the interface has stopped sending, but may be caused by transient congestion. (Normally, this does not occur ^^^ in Linux. Packets are just silently dropped when a device queue ^^^ overflows.) ^^ Which is not true, because just happened to me with kernel Linux version 2.6.11-gentoo-r9. Where should I report? CL - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
docbook stylesheets complaints when they are installed
kestrel linux-2.6.11.7 # make htmldocs *** You need to install DocBook stylesheets *** * app-text/docbook-dsssl-stylesheets Latest version available: 1.77-r2 Latest version installed: 1.77-r2 ^^^ Size of downloaded files: 385 kB Homepage:http://docbook.sourceforge.net Description: DSSSL Stylesheets for DocBook. License: as-is * app-text/docbook-xsl-stylesheets Latest version available: 1.66.1 Latest version installed: 1.66.1 ^^ Size of downloaded files: 1,514 kB Homepage:http://docbook.sourceforge.net/ Description: XSL Stylesheets for Docbook License: || ( as-is BSD ) Is this a symptom of linux kernel mis-detecting the docbook stylesheets? CL< - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Which Docbook stylesheets?
kestrel linux-2.6.11.7 # make htmldocs *** You need to install DocBook stylesheets *** * app-text/docbook-dsssl-stylesheets Latest version available: 1.77-r2 Latest version installed: 1.77-r2 Size of downloaded files: 385 kB Homepage:http://docbook.sourceforge.net Description: DSSSL Stylesheets for DocBook. License: as-is * app-text/docbook-xsl-stylesheets Latest version available: 1.66.1 Latest version installed: 1.66.1 Size of downloaded files: 1,514 kB Homepage:http://docbook.sourceforge.net/ Description: XSL Stylesheets for Docbook License: || ( as-is BSD ) Which stylesheets? CL< - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Which Docbook stylesheets?
kestrel linux-2.6.11.7 # make htmldocs *** You need to install DocBook stylesheets *** * app-text/docbook-dsssl-stylesheets Latest version available: 1.77-r2 Latest version installed: 1.77-r2 Size of downloaded files: 385 kB Homepage:http://docbook.sourceforge.net Description: DSSSL Stylesheets for DocBook. License: as-is * app-text/docbook-xsl-stylesheets Latest version available: 1.66.1 Latest version installed: 1.66.1 Size of downloaded files: 1,514 kB Homepage:http://docbook.sourceforge.net/ Description: XSL Stylesheets for Docbook License: || ( as-is BSD ) Which stylesheets? CL - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
docbook stylesheets complaints when they are installed
kestrel linux-2.6.11.7 # make htmldocs *** You need to install DocBook stylesheets *** * app-text/docbook-dsssl-stylesheets Latest version available: 1.77-r2 Latest version installed: 1.77-r2 ^^^ Size of downloaded files: 385 kB Homepage:http://docbook.sourceforge.net Description: DSSSL Stylesheets for DocBook. License: as-is * app-text/docbook-xsl-stylesheets Latest version available: 1.66.1 Latest version installed: 1.66.1 ^^ Size of downloaded files: 1,514 kB Homepage:http://docbook.sourceforge.net/ Description: XSL Stylesheets for Docbook License: || ( as-is BSD ) Is this a symptom of linux kernel mis-detecting the docbook stylesheets? CL - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Open hardware wireless cards
On Wed, Jan 05, 2005 at 03:05:26PM -0500, Luis R. Rodriguez wrote: > On Wed, Jan 05, 2005 at 02:24:47PM -0500, Luis R. Rodriguez wrote: > <-- snip --> > > > As far as support for the new chipsets goes -- sorry -- we won't be able > > to support it as I don't think even Conexant has a final well tested > > linux source base ready for 2.6. And even if we are given a source base > > there is nothing we can do to get around the need for the closed-source > > softmac libs that it relies on. As much as I'd like to support it, I > > don't want to get a headache to support something I cannot modify so I > > won't be willing to support a half-opened driver as the atheros driver. > > I'd also like to add... > > For those of you frustrated about our current wireless driver situation > in open platforms -- > > I think we probably will have this trouble with most modern hardware for a > while > (graphics cards, wireless driver, etc). A lot of has to do with patent > infringement issues, "intellectual property" protection, and other > business-oriented excuses. > > What I think we probably will have to do is just work torwards seeing if > we can come up with our own open wireless hardware. I know there was > a recent thread on lkml about an open video card -- anyone know where > that ended up? I got open hardware optical wireless, though it's not a card, just add-on to existing Ethernet: http://ronja.twibright.com Nevertheless it show how to use the free-software toolchain. Also see GNU Radio. http://www.gnu.org/software/gnuradio/doc/exploring-gnuradio.html CL< - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
GPL violation by CorAccess?
Hello I have seen a device by CorAccess which apparently uses Linux and didn't find anything that would suggest it complies to GPL, though I had access to the complete shipping package. Does anyone know about known cause of violation by this company or should I investigate further? CL< - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
GPL violation by CorAccess?
Hello I have seen a device by CorAccess which apparently uses Linux and didn't find anything that would suggest it complies to GPL, though I had access to the complete shipping package. Does anyone know about known cause of violation by this company or should I investigate further? CL - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Open hardware wireless cards
On Wed, Jan 05, 2005 at 03:05:26PM -0500, Luis R. Rodriguez wrote: On Wed, Jan 05, 2005 at 02:24:47PM -0500, Luis R. Rodriguez wrote: -- snip -- As far as support for the new chipsets goes -- sorry -- we won't be able to support it as I don't think even Conexant has a final well tested linux source base ready for 2.6. And even if we are given a source base there is nothing we can do to get around the need for the closed-source softmac libs that it relies on. As much as I'd like to support it, I don't want to get a headache to support something I cannot modify so I won't be willing to support a half-opened driver as the atheros driver. I'd also like to add... For those of you frustrated about our current wireless driver situation in open platforms -- I think we probably will have this trouble with most modern hardware for a while (graphics cards, wireless driver, etc). A lot of has to do with patent infringement issues, intellectual property protection, and other business-oriented excuses. What I think we probably will have to do is just work torwards seeing if we can come up with our own open wireless hardware. I know there was a recent thread on lkml about an open video card -- anyone know where that ended up? I got open hardware optical wireless, though it's not a card, just add-on to existing Ethernet: http://ronja.twibright.com Nevertheless it show how to use the free-software toolchain. Also see GNU Radio. http://www.gnu.org/software/gnuradio/doc/exploring-gnuradio.html CL - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Ethernet driver tweak for error correction codes
Is it possible to use up the src, dest MAC addresses (12B) and the CRC field (4B?) on a point-to-point full duplex Ethernet link for my own data? I would like to implement an error correction on this, because I'm gonna build a freespace laser link which would run just this way. And i want to use it on foggy days too when there will be a lot of bits fallen out. Is it possible to do it in the kernel somehow cleanly? How should I try to do it? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
53c400a status
I got a HP Scanjet 3p with a SCSI card that got a 53c400a SCSI interface chip with only one jumper without a label. The card was shipped with the scanner. I tried to insert the module and it does the same that was written in this archive earlier: complaint about business of the bus and then the machine stopped. Is there any chance this is solved in the more up-to-date kernels from my 2.2.18? Clock - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
53c400a status
I got a HP Scanjet 3p with a SCSI card that got a 53c400a SCSI interface chip with only one jumper without a label. The card was shipped with the scanner. I tried to insert the module and it does the same that was written in this archive earlier: complaint about business of the bus and then the machine stopped. Is there any chance this is solved in the more up-to-date kernels from my 2.2.18? Clock - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Ethernet driver tweak for error correction codes
Is it possible to use up the src, dest MAC addresses (12B) and the CRC field (4B?) on a point-to-point full duplex Ethernet link for my own data? I would like to implement an error correction on this, because I'm gonna build a freespace laser link which would run just this way. And i want to use it on foggy days too when there will be a lot of bits fallen out. Is it possible to do it in the kernel somehow cleanly? How should I try to do it? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Can't compile 2.2.18
clock@ghost:~$ gcc --version 2.95.2.1 libc5 make -C arch/i386/kernel make[1]: Entering directory `/usr/src/linux-2.2.18/arch/i386/kernel' cc -D__KERNEL__ -I/usr/src/linux-2.2.18/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -DEXPORT_SYMTAB -c i386_ksyms.c i386_ksyms.c:37: `__ioremap' undeclared here (not in a function) i386_ksyms.c:37: initializer element is not constant i386_ksyms.c:37: (near initialization for `__ksymtab___ioremap.value') i386_ksyms.c:38: `iounmap' undeclared here (not in a function) i386_ksyms.c:38: initializer element is not constant i386_ksyms.c:38: (near initialization for `__ksymtab_iounmap.value') make[1]: *** [i386_ksyms.o] Error 1 make[1]: Leaving directory `/usr/src/linux-2.2.18/arch/i386/kernel' make: *** [_dir_arch/i386/kernel] Error 2 Clock - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Can't compile 2.2.18
clock@ghost:~$ gcc --version 2.95.2.1 libc5 make -C arch/i386/kernel make[1]: Entering directory `/usr/src/linux-2.2.18/arch/i386/kernel' cc -D__KERNEL__ -I/usr/src/linux-2.2.18/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -DEXPORT_SYMTAB -c i386_ksyms.c i386_ksyms.c:37: `__ioremap' undeclared here (not in a function) i386_ksyms.c:37: initializer element is not constant i386_ksyms.c:37: (near initialization for `__ksymtab___ioremap.value') i386_ksyms.c:38: `iounmap' undeclared here (not in a function) i386_ksyms.c:38: initializer element is not constant i386_ksyms.c:38: (near initialization for `__ksymtab_iounmap.value') make[1]: *** [i386_ksyms.o] Error 1 make[1]: Leaving directory `/usr/src/linux-2.2.18/arch/i386/kernel' make: *** [_dir_arch/i386/kernel] Error 2 Clock - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: /dev/random: really secure?
> There are hidden sources of entropy. One is clock skew between the keyboard > processor's clock, the keyboard controller's clock, and the CPU clock > generator's PLL. Another is data motion between the CPU cache and main In the RFC 1750, they write it is not recommended to rely on computer clocks to generate random. Isn't it this case? > > depends solely on the network packets. These can be manipulated and their > > leading edge precisely sniffed. I think here exists a severe risk of > > compromise. Am I right? > > Nope. There is no way to sniff their leading edge accurate to a billionth > of a second. If you have a 1Ghz Pentium 3, that's the accuracy you'd need. But it reduces the entropy. When I have a 486/66 and sniff packets accurately to 3MHz, only 4 bits remain. These bits need not to show a uniform distribution so it could be even easier to guess them. Clock - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
/dev/random: really secure?
I noticed peculiarities in the behaviour of the delta-delta-3 system for entropy estimation in the random.c code./ When I hold right alt or control, I get about 8 bits of entropy per repeat fro the /dev/random which is overestimated. I think the real entropy is 0 bits because it is absolutely deterministic when the interrupt comes. Am I right or is there any hidden magic source of entropy in this case? Right shift, left alt, ctrl and shift make 4 bits per repeat. Is greater randomness being expected from the keys that return 8 bits? When I have a server where n blobk read, keyboard and mouse events occur (everything is cached within huge amount of semiconductor RAM), the /dev/random depends solely on the network packets. These can be manipulated and their leading edge precisely sniffed. I think here exists a severe risk of compromise. Am I right? Clock - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
random.c patch
There are several places where the rotation yields garbage according to ANSI
C definition when called with 0 bit position argument.
diff -Pur linux_reference/drivers/char/random.c linux/drivers/char/random.c
--- linux_reference/drivers/char/random.c Wed Jul 19 00:58:13 2000
+++ linux/drivers/char/random.c Sun Dec 17 22:42:59 2000
@@ -411,7 +411,7 @@
#if (!defined (__i386__))
extern inline __u32 rotate_left(int i, __u32 word)
{
- return (word << i) | (word >> (32 - i));
+ return (word << i) | (word >> ((-i)&31));
}
#else
@@ -857,7 +857,7 @@
#define K3 0x8F1BBCDCL/* Rounds 40-59: sqrt(5) * 2^30 */
#define K4 0xCA62C1D6L/* Rounds 60-79: sqrt(10) * 2^30 */
-#define ROTL(n,X) ( ( ( X ) << n ) | ( ( X ) >> ( 32 - n ) ) )
+#define ROTL(n,X) ( ( ( X ) << n ) | ( ( X ) >> ( (- n)&31 ) ) )
#define subRound(a, b, c, d, e, f, k, data) \
( e += ROTL( 5, a ) + f( b, c, d ) + k + data, b = ROTL( 30, b ) )
@@ -1087,7 +1087,7 @@
/* This is the central step in the MD5 algorithm. */
#define MD5STEP(f, w, x, y, z, data, s) \
- ( w += f(x, y, z) + data, w = w<>(32-s), w += x )
+ ( w += f(x, y, z) + data, w = w<>((-s)&31), w += x )
/*
* The core of the MD5 algorithm, this alters an existing MD5 hash to
@@ -1883,7 +1883,7 @@
* Rotation is separate from addition to prevent recomputation
*/
#define ROUND(f, a, b, c, d, x, s) \
- (a += f(b, c, d) + x, a = (a << s) | (a >> (32-s)))
+ (a += f(b, c, d) + x, a = (a << s) | (a >> ((-s)&31)))
#define K1 0
#define K2 013240474631UL
#define K3 015666365641UL
Clock
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
random.c patch
There are several places where the rotation yields garbage according to ANSI
C definition when called with 0 bit position argument.
diff -Pur linux_reference/drivers/char/random.c linux/drivers/char/random.c
--- linux_reference/drivers/char/random.c Wed Jul 19 00:58:13 2000
+++ linux/drivers/char/random.c Sun Dec 17 22:42:59 2000
@@ -411,7 +411,7 @@
#if (!defined (__i386__))
extern inline __u32 rotate_left(int i, __u32 word)
{
- return (word i) | (word (32 - i));
+ return (word i) | (word ((-i)31));
}
#else
@@ -857,7 +857,7 @@
#define K3 0x8F1BBCDCL/* Rounds 40-59: sqrt(5) * 2^30 */
#define K4 0xCA62C1D6L/* Rounds 60-79: sqrt(10) * 2^30 */
-#define ROTL(n,X) ( ( ( X ) n ) | ( ( X ) ( 32 - n ) ) )
+#define ROTL(n,X) ( ( ( X ) n ) | ( ( X ) ( (- n)31 ) ) )
#define subRound(a, b, c, d, e, f, k, data) \
( e += ROTL( 5, a ) + f( b, c, d ) + k + data, b = ROTL( 30, b ) )
@@ -1087,7 +1087,7 @@
/* This is the central step in the MD5 algorithm. */
#define MD5STEP(f, w, x, y, z, data, s) \
- ( w += f(x, y, z) + data, w = ws | w(32-s), w += x )
+ ( w += f(x, y, z) + data, w = ws | w((-s)31), w += x )
/*
* The core of the MD5 algorithm, this alters an existing MD5 hash to
@@ -1883,7 +1883,7 @@
* Rotation is separate from addition to prevent recomputation
*/
#define ROUND(f, a, b, c, d, x, s) \
- (a += f(b, c, d) + x, a = (a s) | (a (32-s)))
+ (a += f(b, c, d) + x, a = (a s) | (a ((-s)31)))
#define K1 0
#define K2 013240474631UL
#define K3 015666365641UL
Clock
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
/dev/random: really secure?
I noticed peculiarities in the behaviour of the delta-delta-3 system for entropy estimation in the random.c code./ When I hold right alt or control, I get about 8 bits of entropy per repeat fro the /dev/random which is overestimated. I think the real entropy is 0 bits because it is absolutely deterministic when the interrupt comes. Am I right or is there any hidden magic source of entropy in this case? Right shift, left alt, ctrl and shift make 4 bits per repeat. Is greater randomness being expected from the keys that return 8 bits? When I have a server where n blobk read, keyboard and mouse events occur (everything is cached within huge amount of semiconductor RAM), the /dev/random depends solely on the network packets. These can be manipulated and their leading edge precisely sniffed. I think here exists a severe risk of compromise. Am I right? Clock - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
