When using hsubs in a.a.m is it secure against rainbow attacks?
Are hsubs, esubs in a.a.m secure against replay attacks?
Would you call it nowadays anonymous remailing, when the
remailer IP addresses are publicity known to third parties,
compared to tor hidden services mailer infrastructures,
where mailing is truly anonymous and without knowing the
sender/receiver addresses, thanks to ORBs?
When using hsubs in a.a.m is it secure against rainbow attacks?
Are hsubs, esubs in a.a.m secure against replay attacks?
Would you call it nowadays anonymous remailing, when the
remailer IP addresses are publicity known to third parties,
compared to tor hidden services mailer infrastructures,
where mailing is truly anonymous and without knowing the
sender/receiver addresses, thanks to ORBs?
Claas once again spams disinformation:
When using hsubs in a.a.m is it secure against rainbow attacks?
Yes, it's secure, as they aren't vulnerable to such attacks.
Are hsubs, esubs in a.a.m secure against replay attacks?
Yes, they are perfectly secure when you download the complete feed and
then process your messages locally.
Less secure would be adding dummy downloads combined with a distributed message retrieval from multiple servers through Tor, a strategy relevant
with low-bandwidth connections.
Anonymous still defending (as usual) old tech, wrote:
Claas once again spams disinformation:
When using hsubs in a.a.m is it secure against rainbow attacks?
Yes, it's secure, as they aren't vulnerable to such attacks.
https://rittervg.com/p/AAM-defcon13.pdf
So, Ritter's GPU cracker, for hsub, did not used then rainbow tables?
Are hsubs, esubs in a.a.m secure against replay attacks?
Yes, they are perfectly secure when you download the complete feed and
then process your messages locally.
Less secure would be adding dummy downloads combined with a distributed message retrieval from multiple servers through Tor, a strategy relevant with low-bandwidth connections.
You are telling us, that a.a.m software has something like a replay cache,
to filter many hsubs/esubs, injected with the same collected hex strings?
Never heard of ORBs.
So shove your BS up your a?? before you FOAD!
Anonymous still defending (as usual) old tech, wrote:
Claas once again spams disinformation:
When using hsubs in a.a.m is it secure against rainbow attacks?
Yes, it's secure, as they aren't vulnerable to such attacks.
https://rittervg.com/p/AAM-defcon13.pdf
So, Ritter's GPU cracker, for hsub, did not used then rainbow tables?
Are hsubs, esubs in a.a.m secure against replay attacks?
Yes, they are perfectly secure when you download the complete feed and
then process your messages locally.
Less secure would be adding dummy downloads combined with a distributed
message retrieval from multiple servers through Tor, a strategy relevant
with low-bandwidth connections.
You are telling us, that a.a.m software has something like a replay cache,
to filter many hsubs/esubs, injected with the same collected hex strings?
You are telling us, that a.a.m software has something like a replay cache, to filter many hsubs/esubs, injected with the same collected hex strings?
No, I'm not. And there's no reason to implement such a cache, as the user has to know that he's under attack. Furthermore, as all messages are processed locally, an attacker will never know about the extensive processing.
Mini Mailer wrote:
Anonymous still defending (as usual) old tech, wrote:
Claas once again spams disinformation:
When using hsubs in a.a.m is it secure against rainbow attacks?
Yes, it's secure, as they aren't vulnerable to such attacks.
https://rittervg.com/p/AAM-defcon13.pdf
So, Ritter's GPU cracker, for hsub, did not used then rainbow tables?
Are hsubs, esubs in a.a.m secure against replay attacks?
Yes, they are perfectly secure when you download the complete feed and
then process your messages locally.
Less secure would be adding dummy downloads combined with a distributed
message retrieval from multiple servers through Tor, a strategy relevant >>> with low-bandwidth connections.
You are telling us, that a.a.m software has something like a replay cache, >> to filter many hsubs/esubs, injected with the same collected hex strings?
Optional replay cache with database support added. :-)
https://github.com/Ch1ffr3punk/f-esub
In article <10366o4$1bvtl$2@news.tcpreset.net> Stefan Claas announced:
Optional replay cache with database support added. :-)
https://github.com/Ch1ffr3punk/f-esub
Stefan, that truly is an important measure to avoid the effort of
decoding other's a.a.m replies twice. You're absolutely on the
right track to something really great! Keep it up! We're with you.
Anonymous wrote:
You are telling us, that a.a.m software has something like a replay cache, >> > to filter many hsubs/esubs, injected with the same collected hex strings? >>No, I'm not. And there's no reason to implement such a cache, as the user >> has to know that he's under attack. Furthermore, as all messages are
processed locally, an attacker will never know about the extensive
processing.
What does the user gain from it when he knows that he is under an attack?
And what can he do to not get such unwanted messages to process?
Claas wrote:
Anonymous wrote:
You are telling us, that a.a.m software has something like a replay cache,
to filter many hsubs/esubs, injected with the same collected hex strings?
No, I'm not. And there's no reason to implement such a cache, as the user
has to know that he's under attack. Furthermore, as all messages are processed locally, an attacker will never know about the extensive processing.
What does the user gain from it when he knows that he is under an attack?
You're joking, aren't you?
Anonymous wrote:
So shove your BS up your a?? before you FOAD!
You and your LEA supporting team are only pissed,
because you can't control nor monitor Mini Mailer,
smtpdump and pluto, global and decentralized Tor
Hidden Services networks, like you can do with
outdated public store and forwarding mini remailer
networks. :-D
Stefan Claas dreams:
Anonymous wrote:
Claas wrote:
Anonymous wrote:You're joking, aren't you?
You are telling us, that a.a.m software has something like a replay cache,
to filter many hsubs/esubs, injected with the same collected hex strings?
No, I'm not. And there's no reason to implement such a cache, as the user
has to know that he's under attack. Furthermore, as all messages are
processed locally, an attacker will never know about the extensive
processing.
What does the user gain from it when he knows that he is under an attack? >>
In regards to a.a.m. no, I am not joking.
But... he does not know, when under
a Pegasus/FinSpy attack, if using online tools like Omnimix. So better one >prepares his stuff offline and then inject it later online for a.a.m. usage.
Same goes for fetching from a.a.m.
Claas wrote:
Anonymous wrote:
Claas wrote:
Anonymous wrote:
You are telling us, that a.a.m software has something like a replay cache,
to filter many hsubs/esubs, injected with the same collected hex strings?
No, I'm not. And there's no reason to implement such a cache, as the user
has to know that he's under attack. Furthermore, as all messages are processed locally, an attacker will never know about the extensive processing.
What does the user gain from it when he knows that he is under an attack?
You're joking, aren't you?
In regards to a.a.m. no, I am not joking.
So you're not interested in knowing whether you're under attack? That's stupid.
But... he does not know, when under
a Pegasus/FinSpy attack, if using online tools like Omnimix. So better one prepares his stuff offline and then inject it later online for a.a.m. usage.
For a.a.m usage? What's that?
BTW, simply set Display -> Shorten Msg to 0 on your offline OM and copy
the MM/YAMN output from Rem Data into files. But don't forget to update
your offline OM's statistics files every now and then to get reliable
chains.
Same goes for fetching from a.a.m.
I'm sure there'll also be ways to get an offline database of the a.a.m
group.
| Sysop: | Gate Keeper |
|---|---|
| Location: | Shelby, NC |
| Users: | 940 |
| Nodes: | 20 (0 / 20) |
| Uptime: | 497130:59:58 |
| Calls: | 15,888 |
| Calls today: | 13 |
| Files: | 5,345 |
| D/L today: |
4 files (8,192P bytes) |
| Messages: | 680,399 |