Can you say “crib sent in the clear” children ? Good, I knew you could..

Why they all decide they need to invent their own configuration/build system is beyond me, especially when autotools work (well, much better than what they invent anyway)..

Grr… :-)

Cheers. I’d not heard of tcptrack before - it’s a cool utility and I’ll add it to my toolbox.

I assume that you visited the user in question with a LART in hand.

Mick

I’ve also used tcptrack on our NFS server to work out which nodes on which cluster are hammering it when we see high load averages and try and track back to users. Was very handy when someone changed a configuration parameter in their WRF weather model which caused every process in a 32 CPU job busy loop on an error message.. They managed to sustain 800Mb/s writes!

One day we’ll be saying “and we used to make do with just 8GB of RAM, but you tell that to the youth of today and they won’t believe you…”.

I was unable to get an adequate result from the vendor and the receptionist did not forward the calls after the first few. A direct call to the sales channel resulted in the comment, “who the hell would want to monitor a toothbrush”.

I agree that Ben may have been indulging in a bit of post facto “face saving” as you say. But he has the decency to mention the openssl-dev list posting - embarrassing as that may be. But that still doesn’t change my view that the upstream package maintainer is best placed to fix flaws.

Both sides of the argument look bad here. The openssl team for not providing sufficient support to a query about the code (and for not commenting the code sufficiently well to allow the researcher to understand the impact of commenting out the “offending” lines); and the Debian team for making and then maintaining a fork of the openssl code for two years without getting it back into the upstream.

Mick

Whilst I am not happy with what happened here in Debian the patch in question was actually discussed on the openssl-dev list *before* being applied. Ben now tries to claim that the openssl-dev list isn’t for openssl development, but as this LWN article points out the list was described on their site as:

Discussions on development of the OpenSSL library. Not for application development questions!

The list he suggested to be used was not mentioned on their website. So I suspect there’s a bit of face saving going on here on their part too.. :-)

Also don’t forget that if you’ve used a compromised client with a good DSA key then you should consider that DSA key compromised as well. :-(

No - I had no problem with k9copy and without more detail about your failure I can’t really diagnose the problem. I assume that you have added codec options for psp and psp audio as I suggested in my post. If you are having trouble with using those specific options, then I suggest that you first try ripping with one of the standard pre-set options such as MS-MPEG4 with mp3 or aac audio. If that works (and it should so long as you have the appropriate codecs installed) then there may be a problem with the entries you made for the psp.

Let me know how you get on.