D.i.N.S. v1.0C
Posted: Sun Jun 29, 2008 1:22 pm
Greetings once again!
For all the members that aren't logged in, I attached two screenshots to accompany this update.
In this update I have added a significant amount of client signatures and blocking techniques that reduce network overhead due to unecessary 'callback packets'. I have started to focus on filterring out 'info-retrieving' packets from various clients that send info about the host computer/user to the core server and to other users. I don't believe that this is meant to invade privacy, but other people may see otherwise.
I added a poll-based timer routine to test how long it takes to perform certain actions and see how they compare to various optimizations. I may be utilizing the timer routine later to set acceptable parameters in which a process must complete its task by. It isn't exactly a RT-OS, but its one step closer. Once again though, that is only an idea, and it hasn't been worked out as far as details or code goes; it may not even happen.
I added "-Os -march=pentium4 -ffast-math -funroll-loops" optimizations to the entire OS resulting in faster speeds (measured by the timer). It seems stable with the heavy optimizations, but its only been about 24-hours of burn-in, so I wont call it offically stable yet.
----------------------------------------------------------------------------------
The current p2p/bittorrent client blacklist is as follows:
Azureus v2.5.0.4,
Vuze v3.1.0.0,
uTorrent v1.8b,
KaZaA v3.2.5,
ARES v2.0.9,
LimeWire v4.18.3,
eMule v0.49a,
Shareaza v4,
BearShare v6,
BitTornado v0.4.17,
ABC v3.1,
Deluge v0.5.9.3,
BitComet v1.02,
XBT v0.7.3,
Arctic v1.2.3,
g3torrent v1.01,
Rufus v0.6.9,
mlDonkey v2.9.5,
BitTyrant v2.5.0.0,
Tribler v4.1.9
Bittorrent v6.0.3
----------------------------------------------------------------------------------
I also went through after blocking the default installs and re-ran all of the applicable clients with encryption enabled and went back through and added signatures based off of the encryption that was impelemented. The screenshot for the BitTorrent client shows the blocking of an early encryption handshakes.
The OS has been so stable in the past week or two that I have been running my personal computer through it and have actually forgotten that it was being tunneled through D.i.N.S., needless to say, I was displeased when my Ubuntu torrent wasn't downloading.
I began working on the base-code for the web UI. Nothing to really report yet, I havent even been able to dish out even the most basic of pages back, but I've been focusing on adding client signatures. I have decided on implementing both the Web UI and the Serial-based terminal UI. By default, the serial terminal UI will be enabled only, then through the terminal CLI the administrator could then enable the Web UI for added 0-day security.
Thanks for tuning in.
For all the members that aren't logged in, I attached two screenshots to accompany this update.
In this update I have added a significant amount of client signatures and blocking techniques that reduce network overhead due to unecessary 'callback packets'. I have started to focus on filterring out 'info-retrieving' packets from various clients that send info about the host computer/user to the core server and to other users. I don't believe that this is meant to invade privacy, but other people may see otherwise.
I added a poll-based timer routine to test how long it takes to perform certain actions and see how they compare to various optimizations. I may be utilizing the timer routine later to set acceptable parameters in which a process must complete its task by. It isn't exactly a RT-OS, but its one step closer. Once again though, that is only an idea, and it hasn't been worked out as far as details or code goes; it may not even happen.
I added "-Os -march=pentium4 -ffast-math -funroll-loops" optimizations to the entire OS resulting in faster speeds (measured by the timer). It seems stable with the heavy optimizations, but its only been about 24-hours of burn-in, so I wont call it offically stable yet.
----------------------------------------------------------------------------------
The current p2p/bittorrent client blacklist is as follows:
Azureus v2.5.0.4,
Vuze v3.1.0.0,
uTorrent v1.8b,
KaZaA v3.2.5,
ARES v2.0.9,
LimeWire v4.18.3,
eMule v0.49a,
Shareaza v4,
BearShare v6,
BitTornado v0.4.17,
ABC v3.1,
Deluge v0.5.9.3,
BitComet v1.02,
XBT v0.7.3,
Arctic v1.2.3,
g3torrent v1.01,
Rufus v0.6.9,
mlDonkey v2.9.5,
BitTyrant v2.5.0.0,
Tribler v4.1.9
Bittorrent v6.0.3
----------------------------------------------------------------------------------
I also went through after blocking the default installs and re-ran all of the applicable clients with encryption enabled and went back through and added signatures based off of the encryption that was impelemented. The screenshot for the BitTorrent client shows the blocking of an early encryption handshakes.
The OS has been so stable in the past week or two that I have been running my personal computer through it and have actually forgotten that it was being tunneled through D.i.N.S., needless to say, I was displeased when my Ubuntu torrent wasn't downloading.
I began working on the base-code for the web UI. Nothing to really report yet, I havent even been able to dish out even the most basic of pages back, but I've been focusing on adding client signatures. I have decided on implementing both the Web UI and the Serial-based terminal UI. By default, the serial terminal UI will be enabled only, then through the terminal CLI the administrator could then enable the Web UI for added 0-day security.
Thanks for tuning in.