1 |
i take that back, ss is a scanner |
2 |
|
3 |
usage: %s <port> [-a <a class> | -b <b class>] [-i <interface] [-s <speed>] |
4 |
speed 10 -> as fast as possible, 1 -> it will take bloody ages (about 50 |
5 |
syns/s) |
6 |
-s requires an argument |
7 |
-i requires an argument |
8 |
A must be between 1 and 254 |
9 |
scanning network %d.*.*.* |
10 |
-a requires an A network as argument |
11 |
scanning network %d.%d.*.* |
12 |
-b requires an B network as argument(e.g. 192.168) |
13 |
usec: %ld, burst packets %d |
14 |
damn dude, port numbers are in 1 .. 65535 |
15 |
using inteface %s |
16 |
ERROR: %s |
17 |
(tcp[tcpflags]=0x12) and (src port %d) and (dst port %d) |
18 |
using "%s" as pcap filter |
19 |
my detected ip on %s is %s |
20 |
|
21 |
Alex Schultz wrote: |
22 |
|
23 |
> I'm not 100% sure, but after a quick look it appears that sshf opens |
24 |
> up the uniq.txt and then procedes to connect to every ip using |
25 |
> test:test or guest:guest. It then dumps out which of those |
26 |
> accounts:ip worked to vuln.txt. Then a person can just go through the |
27 |
> vuln.txt and ssh and perform whatever rooting they so choose. |
28 |
> |
29 |
> I wonder what the "ss" program does. It's got libpcap compiled into |
30 |
> it so maybe it's some sort of sniffer and/or ip generator (creates |
31 |
> bios.txt?). |
32 |
> |
33 |
> Br0mGreV wrote: |
34 |
> |
35 |
>> Hi, |
36 |
>> |
37 |
>> Does anyone started to reverse-ingineer that damn soft 'sshf'? I'm |
38 |
>> sure we can learn some information about the exploit, if we |
39 |
>> look at this file. |
40 |
>> I'll start that tommorow. Hope to give you some informations from |
41 |
>> that soon. |
42 |
>> |
43 |
>> GD |
44 |
>> |
45 |
>> -- |
46 |
>> gentoo-security@g.o mailing list |
47 |
>> |
48 |
>> |
49 |
> |
50 |
> |
51 |
> -- |
52 |
> gentoo-security@g.o mailing list |
53 |
> |
54 |
> |
55 |
|
56 |
|
57 |
-- |
58 |
gentoo-security@g.o mailing list |