sci.crypt
  Home FAQ Contact Sign in
sci.crypt only
 
Advanced search
July 2008
motuwethfrsasuw
 123456 27
78910111213 28
14151617181920 29
21222324252627 30
28293031    31
2008
 Jan   Feb   Mar   Apr 
 May   Jun   Jul   Aug 
 Sep   Oct   Nov   Dec 
2008 2007 2006  
total
sci.crypt Profile…
RELATED GROUPS

POPULAR GROUPS

 Up
  M$ encrypted file system.. what a load of crap!!!         


Author: robdevloper
Date: Jul 30, 2008 14:59

I hate M$ for screwing me up..their Encrypted file system is a load of
cr@p.
Ok before ranting more, here's my problem:

In my scenario, there are three WinXP computers: A (desktop), B
(laptop) and C (laptop), all with NTFS
and two external hard drives, EXT1 and EXT2 both with NTFS.
Here's what happened:

1) A had some file F encrypted under NTFS, which I moved to EXT1.
Now I could read F on EXT1 without any problems when accessing it from
A

However, when I tried reading F on EXT1 when accessing from B, I got
the usual error.
So I copied the private key files to EXT1 (as described in M$ site for
recovery agent), imported the private key (PA) of A to B and then
tried reading F on EXT1 via B. It all worked fine.
So far so good.

2) Now somehow my computer A got damaged/lost. Luckily I had backed up
the private key PA to EXT1.
I could now read F via B (as I had already imported PA to B).
Show full article (2.13Kb)
5 Comments
  A Bit-Stream Parity Attack         


Author: Douglas Eagleson
Date: Jul 30, 2008 09:37

Here is a parity shuffle and it takes the initial state and causes all
binary.

The (2) in the code is resolvable in runtime as a parity. Just
ignaore or remove the unused variables.

I just might crack bit-stream type of data sets.

#include

main(){

unsigned int in;
unsigned int out;
unsigned int y;
unsigned int x;
unsigned int end;

in=0x0001;
y=2;
end=0;

while(end<65535){

in=in*(2)*65535; //the (2) is critical to the function.

in = in^end;

printf("out=0x%%04x\n",in);
Show full article (0.58Kb)
2 Comments
  Kaspersky & friends should be locked up.         


Author: Jan Panteltje
Date: Jul 30, 2008 07:37

This is an 'opinion' post.
It is my view, that those who make public vulnerabilities in
wide spread internet software should be locked up.
And it is my opinion, with all respect for life, that those
NUT CASES who use that knowledge and tools to start attacks on websites
BE EXECUTED.

The internet used to be OK, it used to be OK to run your own server.
Now not a day goes by without some kids using toolkits and info obtained
from EGO TRIPPERS like Karspersky (or however you spell the name of that moron)
to try DNS attacks, and other attacks, with the potential to bring down the whole
internet.

Karpersky are you doing it for you own glory? Think about what happens if only
1 in a million internet users 'have a go'.
Idiot!
Show full article (1.20Kb)
20 Comments