Luke-Jr has quit [Remote host closed the connection]
Luke-Jr has joined #qi-hardware
nicksydney_ has quit [Read error: Connection reset by peer]
nicksydney has joined #qi-hardware
nicksydney_ has joined #qi-hardware
nicksydney has quit [Ping timeout: 264 seconds]
nicksydney has joined #qi-hardware
nicksydney_ has quit [Ping timeout: 264 seconds]
dos1 has quit [Ping timeout: 240 seconds]
lindi-_ has joined #qi-hardware
bartbes_ has joined #qi-hardware
freespace has quit [Ping timeout: 265 seconds]
woakas has quit [Ping timeout: 265 seconds]
bartbes has quit [Ping timeout: 265 seconds]
lindi- has quit [Ping timeout: 265 seconds]
woakas has joined #qi-hardware
freespace has joined #qi-hardware
arielenter has joined #qi-hardware
atommann has joined #qi-hardware
michael_lee has joined #qi-hardware
atommann has quit [Ping timeout: 250 seconds]
atommann has joined #qi-hardware
Luke-Jr has quit [Remote host closed the connection]
Luke-Jr has joined #qi-hardware
* whitequark
has devised an interesting system for data storage
<whitequark>
you know dropbox, right?
<whitequark>
well, it will be sort-of dropbox clone, if you think about the interface it shows the user
<whitequark>
but internally, it has all-consuming maniacal paranoia
<whitequark>
it doesn't trust: 1) network, over which you connect to server 2) the server itself 3) whatever storage mechanism server uses 4) other peers
<whitequark>
taking quite some inspiration from tahoe-lafs
arielenter has quit [Quit: Leaving.]
arielenter has joined #qi-hardware
Luke-Jr has quit [Remote host closed the connection]
Luke-Jr has joined #qi-hardware
Luke-Jr has quit [Remote host closed the connection]
Luke-Jr has joined #qi-hardware
Luke-Jr has quit [Remote host closed the connection]
Luke-Jr has joined #qi-hardware
Luke-Jr has quit [Remote host closed the connection]
Luke-Jr has joined #qi-hardware
Luke-Jr has quit [Remote host closed the connection]
Luke-Jr has joined #qi-hardware
arielenter has quit [Quit: Leaving.]
xiangfu has joined #qi-hardware
rta has quit [Ping timeout: 246 seconds]
kristianpaul has quit [Ping timeout: 250 seconds]
kristianpaul has joined #qi-hardware
kristianpaul has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
xiangfu has joined #qi-hardware
arielenter has joined #qi-hardware
rta has joined #qi-hardware
jekhor has joined #qi-hardware
arielenter has quit [Read error: Connection timed out]
mth has quit [Remote host closed the connection]
rz2k has joined #qi-hardware
wolfspraul has joined #qi-hardware
<wpwrak>
furthermore, it shall distrust: users, the CPU hardware, cryptography, causality
nicksydney has quit [Read error: Connection reset by peer]
nicksydney has joined #qi-hardware
michael_lee has quit [Quit: Ex-Chat]
sb0 has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
rz2k has quit []
xiangfu has joined #qi-hardware
dandon_ has joined #qi-hardware
dandon has quit [Ping timeout: 240 seconds]
dandon_ is now known as dandon
atommann has quit [Quit: Leaving]
xiangfu has quit [Ping timeout: 250 seconds]
xiangfu has joined #qi-hardware
xiangfu has quit [Ping timeout: 250 seconds]
xiangfu has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
jekhor has quit [Ping timeout: 240 seconds]
<whitequark>
that's not a bad idea in general, but no, not in this one :)
mth has joined #qi-hardware
bzb has joined #qi-hardware
bzb has quit [Read error: Connection reset by peer]
Luke-Jr has quit [Remote host closed the connection]
<wpwrak>
eintopf: one issue with making at86rf23x start sending before all data is in the chip's buffer is that you have to be sure you don't get any unexpected delays between commanding the transmission and the and of the data transfer
<wpwrak>
eintopf: in linux, you usually can't guarantee this yet it may still work most of the time. you should therefore be prepared to handle a frame buffer underrun (access violation)
<DocScrutinizer05>
and the first time I logged in they instantly kicked me "for security reasons" and next time they complained that I didn't log out ;-P
<DocScrutinizer05>
well, that's been obvious
<DocScrutinizer05>
may nave been exploited since 2 years, I'd say
<DocScrutinizer05>
even worse: I learned they also might have attacked *my* PC when I connected to a https:// URL
<wpwrak>
naw, not obvious. we didn't know it have been independently discovered
<wpwrak>
what they're saying is that evidence for heartbleed attacks have been found in honeypot going back as far as november 2013
<DocScrutinizer05>
ooooh
<DocScrutinizer05>
no surprise though
<DocScrutinizer05>
I had taken bets
<wpwrak>
seems that *someone* is reviewing that openssl code. it's just not the ones responsible ...
<DocScrutinizer05>
I'm just pondering a staeful packet inspection firewall that has a list of "hot terms"
<wpwrak>
some people may just record everything that goes to their honeypot. then, when something happens that makes them suspicious, they can examine the whole history of their traffic for clues
<DocScrutinizer05>
of course such firewall MUST be bomb proven by itself, otherwise it might make for a really worthy target
<wpwrak>
the recording in such a honeypot could be completely passive
<DocScrutinizer05>
sure sure, honeypot. fine. but hardly feasible for your private PC to harden it
<wpwrak>
a 1 TB disk would be enough for about a day of sustained 100 Mbps traffic. and a honeypot probably gets a lot less
<wpwrak>
naw, but for security firms. 1 disk per day is peanuts if it's part of your business
<DocScrutinizer05>
yep, I know a bit about how those companies work
<DocScrutinizer05>
most amazing thing is: how do they get all those IPs out of alien ranges
<DocScrutinizer05>
I mean, how would I set up a honeypot that has an IP that looks like it was in IBM offices India?
<DocScrutinizer05>
and they probably not only want the IP but also the traceroute look plausible
<wpwrak>
just put your own content there ? e.g., who really knows who is behind pics.nase-bohren.de ? :)
<DocScrutinizer05>
OK, to a certain degree you can fake traceroute
<wpwrak>
maybe fakebook is just one big honeypot and they record EVERYTHING ;)
<DocScrutinizer05>
that's been the basic idea when they invented it