Looking through the list of suspect
exit nodes, they fall into three
categories:
1) very low-bandwidth Window Vista
systems running 0.2.4.21
2) recently dead/offline
3) one massive Linux exit
The (1) exits might be hacked Windows
systems, perhaps part of a botnet
--no contact given. Seems a
Could someone comment on why 15 exit nodes
discovered to be sniffing and abusing login
credentials have not been marked with the
BAD EXIT flag?
The research appears to be legitimate, involved
a good deal of effort, and seems credible:
https://chloe.re/2015/06/20/a-month-with-badonions/
was blogg
Takes a full two weeks for the
new-relay cap to be aged-out.
Patience.
At 13:33 7/2/2015 +, Speak Freely wrote:
>
>I did as s7r suggested, updated to 0.2.7.1-alpha-dev,
>and changed fingerprints.
>
>And we're still crippled by CW of 20.
>(Yes, yes, I know. The relay has gone back
>to stage 1
I did as s7r suggested, updated to 0.2.7.1-alpha-dev, and changed
fingerprints.
And we're still crippled by CW of 20.
(Yes, yes, I know. The relay has gone back to stage 1/3 because the
fingerprints changed.)
Uptime: > 48 hours
Upload/download : 2.1GB, works out to a blazingly fast speed of 12.1
"So, it's as simple as changing type="text" to type="date"?
Turns out that Firefox (and hence Tor Browser) doesn't support this
yet, but it falls back to plain text nicely.
I just made that change in the mockup.
Thanks!"
Yes, it's as easy as that! The date selector also works natively on mobile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/07/15 11:45, Joshua Lee Tucker wrote:
> Hi Karsten,
>
> I've made a patch to the page to add the HTML5 date components - it
> should work nicely across the majority of browsers (maybe even all
> with a plaintext fallback).
>
> I wasn't sure exa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Karsten,
I've made a patch to the page to add the HTML5 date components - it should
work nicely across the majority of browsers (maybe even all with a
plaintext fallback).
I wasn't sure exactly in which format you wanted the patch, so I've
uploa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/07/15 11:15, Jens Kubieziel wrote:
> * Karsten Loesing schrieb am 2015-07-02 um 09:40 Uhr:
>> Please take a look at the design mockup, maybe compare it to the
>> existing ExoneraTor service, and let us know your thoughts.
>
> - I find the logo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/07/15 10:59, Joshua Lee Tucker wrote:
> Hi Karsten,
Hello Joshua,
> I much prefer the design of the first logo (over the existing ones)
> - I think it helps to retain ExoneraTor's affiliation with Tor, as
> I think the other logos make it too d
* Karsten Loesing schrieb am 2015-07-02 um 09:40 Uhr:
> Please take a look at the design mockup, maybe compare it to the
> existing ExoneraTor service, and let us know your thoughts.
- I find the logo 1 quite nice.
- When a user enters the date field, it might be helpful when some
calendar-like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Karsten,
I much prefer the design of the first logo (over the existing ones) - I
think it helps to retain ExoneraTor's affiliation with Tor, as I think the
other logos make it too difficult to recognise that Tor logo.
The designs look great!
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello relay operators,
Julius and I have been working on a design mockup for the ExoneraTor
service for the past few months and would want to hear what you think
about this:
https://people.torproject.org/~karsten/volatile/exonerator-mockup/
The main
12 matches
Mail list logo
