Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
2ton_jeff
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
2ton_jeff
11y ago
Mosh has this fully sorted too IMO: https://mosh.mit.edu
32.
▲
Diffie-Hellman 1024 bits difficulty compared to Bitcoins
(blog.erratasec.com)
7 points
by
2ton_jeff
11y ago
|
0 comments
33.
▲
by
2ton_jeff
11y ago
Only fixed wireless where I am on the Sunshine Coast, QLD .. and unfortunately my building is not line of sight to the tower, so I don't have any options whatsoever. ~2mbps/200kbps on a good day, otherwise the backhaul is so satur
34.
▲
by
2ton_jeff
11y ago
Bit late to the party here, but this is why I wrote https://2ton.com.au/dhtool/ ... I have 48 CPU cores still dedicated to constantly generating safe primes and generators (have amassed a huge number of 2k, 3k, 4k and
35.
▲
by
2ton_jeff
11y ago
Impressive amount of effort here. How is this different/better than using a strong static encryption for data and then using "normal" redundant cloud storage services like backblaze? Also, why did you choose Nettle's pbk
36.
▲
by
2ton_jeff
11y ago
On my list of things to do is to write an article titled "VDSO and why you should care." Interestingly, syscall indirection isn't among my reasons (maybe I am too comfortable in my SSE2+ x86_64 environment). If anyone is inte
37.
▲
by
2ton_jeff
11y ago
This is a beauty, thanks for sharing! I second the recommendation.
38.
▲
by
2ton_jeff
11y ago
IMO, bootloader/video memory is quite a distance from the traditional model of what "Hello World" is meant to be about, no? If anyone's interested, there are lots of very simple bootloader Hello World goods around: http
39.
▲
by
2ton_jeff
11y ago
By default all code/RIP addresses are <32 bit, no harm no foul.
40.
▲
by
2ton_jeff
11y ago
Much nicer, thanks!
41.
▲
by
2ton_jeff
11y ago
Thanks for that, and a tip of my hat to the HN community. Love this place. Having written the aforementioned, I thought maybe y'all would be interested in a very very lightweight version of same done w/ my assembler of choice (onl
42.
▲
by
2ton_jeff
11y ago
Late Sunday night here, but before I sign off for the night, thought you'd be amused to know that the name rwasa really, truly was an acronym from "Rapid Web Application Server in Assembler". I have historically sucked at com
43.
▲
by
2ton_jeff
11y ago
I am aware of Intel's patch re: psubusw usage, and interestingly chose the same solution when hand-compiling it as theirs well before I saw their patch to it (in fill window, which does make a substantial difference). Have you compared
44.
▲
by
2ton_jeff
11y ago
Admittedly I haven't checked recently, but before I released 2 Ton Digital I did a few test github projects and they all looked horrific so yeah I left it out on purpose. It's been on my "someday when I am bored" list si
45.
▲
by
2ton_jeff
11y ago
> It's my understanding that random padding doesn't in fact make the attacker's job "much more" difficult. Only a little more, or not at all? The BREACH attack verbage at http://breachattack.com spell
46.
▲
by
2ton_jeff
11y ago
Hey thanks! Contrary to popular belief, x86_64 assembler isn't really that bad to deal with. An eagle-eye perspective is simply that regardless of how good optimising compilers get, they can never really know my intent. My zlib impleme
47.
▲
by
2ton_jeff
11y ago
Agreed regarding general trust in any crypto stack. I've been doing commercial software development for 28 years now, and my company's products all reflect this. Whether I expect high-value security sites to use my software in pro
48.
▲
by
2ton_jeff
11y ago
Do you have specific criticisms of my work and/or attention to detail re: the TLS specification, and/or my library's application of modular arithmetic et al?
49.
▲
by
2ton_jeff
11y ago
h2o is cool too, I contributed to that project early this year for their OpenSSL/DHE parameter settings. Re: How much time, hard to say from my perspective since a fair amount of rwasa's functionality resides in the library itself
50.
▲
by
2ton_jeff
11y ago
Author here: Feature request noted, although the one-logfile-per-day for me doesn't seem too unwieldy. I have not seen webserver logs stored in the way you describe, is that a common practice (each month's worth in its own separat
51.
▲
by
2ton_jeff
11y ago
WYSIWYG sadly, hnwatch grabs the ID list to fetch from the SSE direct from firebaseio (and thus the public API). It was working a treat (and accurately reproducing everything from HN web-proper) prior to my releasing this... IDK what the pr
52.
▲
by
2ton_jeff
11y ago
I attempted to call the 1 (844) 843-3473 number on the firebaseio.com site, I suspect it may be before their waking hours though.. my hnwatch now is not behaving at all like it was earlier though, and the only difference is that I released
53.
▲
by
2ton_jeff
11y ago
wow really bad now, my program is mostly useless without firebaseio... should I ring them?
54.
▲
by
2ton_jeff
11y ago
outside curios request related to this submission, I have always configured webservers to return "400 Bad Requests" on HTTP/1.1 requests that lack a Host: header. Still, every interaction I have had with HN this year always r
55.
▲
by
2ton_jeff
11y ago
You obviously didn't scrutinize my code :-)
56.
▲
by
2ton_jeff
11y ago
Coming back around, my automated syntax highlighter for sources doesn't like HTML entities, and the source_as_html you reference is indeed broken, but only for the HTML/browser case. Tah for the positive attitude, most of my sourc
57.
▲
by
2ton_jeff
11y ago
Nice to meet you, too. Curious as to what your intention is by pointing out my investment in years of profit-free GPLv3 development, and that somehow that is tied to the BSD license of the compiler's creator. Care to elaborate on a bet
58.
▲
by
2ton_jeff
11y ago
again FWIW, I am the co-founder of a proper Australian registered business, I appreciate your concern. In an isolated environment, run it with strace -o nasties.txt or something similar. I assure you personally that the only outbound connec
59.
▲
by
2ton_jeff
11y ago
See prior comment about the intentional omission of "/list" functionality
60.
▲
by
2ton_jeff
11y ago
I noticed that the API from firebaseio has been really lagging since I turned this loose, not sure what is up, the code for the retrievals is pure REST though, nothing hardcore or nonstandard.
More ›