-
```
Looking at the current source, there's a slight issue in RC4's code. In the
next() method:
...
t = S[i];
S[i] = S[j];
S[j] = t;
return S[(t+S[i])&255];
Since t is still S[i]…
-
```
Looking at the current source, there's a slight issue in RC4's code. In the
next() method:
...
t = S[i];
S[i] = S[j];
S[j] = t;
return S[(t+S[i])&255];
Since t is still S[i]…
-
```
Looking at the current source, there's a slight issue in RC4's code. In the
next() method:
...
t = S[i];
S[i] = S[j];
S[j] = t;
return S[(t+S[i])&255];
Since t is still S[i]…
-
```
Looking at the current source, there's a slight issue in RC4's code. In the
next() method:
...
t = S[i];
S[i] = S[j];
S[j] = t;
return S[(t+S[i])&255];
Since t is still S[i]…
-
## Environment data
`dotnet --info` output:
```
.NET Command Line Tools (1.0.0-rc4-004706)
Product Information:
Version: 1.0.0-rc4-004706
Commit SHA-1 hash: e38bc4950c
Runtime…
-
```
Looking at the current source, there's a slight issue in RC4's code. In the
next() method:
...
t = S[i];
S[i] = S[j];
S[j] = t;
return S[(t+S[i])&255];
Since t is still S[i]…
-
```
Looking at the current source, there's a slight issue in RC4's code. In the
next() method:
...
t = S[i];
S[i] = S[j];
S[j] = t;
return S[(t+S[i])&255];
Since t is still S[i]…
-
```
Looking at the current source, there's a slight issue in RC4's code. In the
next() method:
...
t = S[i];
S[i] = S[j];
S[j] = t;
return S[(t+S[i])&255];
Since t is still S[i]…
-
```
Looking at the current source, there's a slight issue in RC4's code. In the
next() method:
...
t = S[i];
S[i] = S[j];
S[j] = t;
return S[(t+S[i])&255];
Since t is still S[i]…
-
Maybe it's me (I don't understand).
I used the program to obfuscate a javascript file, but the strings are all visible in the code.
I used this command line:
```
javascript-obfuscator in.js …