Spyware now implementing on FreeBSD.org

While browsing through the FreeBSD mailing lists, I came across a very alarming piece of development at FreeBSD’s official website.

Quote taken from the thread:

The FreeBSD Project’s Web developer announced his intent to incorporate corporate spyware into the FreeBSD.org Web site.

Horrifying as it is, it is not surprising that such proprietary friendly organisation would do such a thing. Since the 1990s, the BSDs as a whole has been assisting the proliferation of proprietary systems such as Microsoft Windows and Apple Macintosh in a hope that they can use them as a vehicle to destroy GNU/Linux, the operating system that champions individual freedom. This move in some sense backfired on the BSD projects as they are now forced into servitude by these tyrants they help thus resulting in little code contributions and lost of developers to these tyrants or (if the developer excepts the the facts) GNU/Linux and worst of all, infiltration and influence by proprietary interests. Today, many BSD project members area in fact operatives from proprietary and freedom hating entities steering the BSD projects to for their own ends keeping BSD from being usable and instead making the project produce code fragments that used as fuel for the development of proprietary software.

Posted in Uncategorized | 4 Comments

FreeBSD is more Insecure then Windows

Yesterday, We received information from a friend about some alarming information about FreeBSD and the attitude that the FreeBSD community (more like cult) has to this issue.

After being banned from accessing forum.FreeBSD.org for simply mentioning this problem, Felix Doggoson deciding to share with us this information. Here is what he says:

By Felix Doggoson


I was doing an analysis for my company who is looking to select a new operating system
for their recently created server farm. I was analyzing FreeBSD when I found something
alarming about it.

I ran a program that I made called simplegets, and then I looked at it’s layout in virtual
memory while running and this is what I got:

doggoson@fbsd:/home/doggoson % ps aux | grep simplegets

doggoson 13381 0.0 0.1 9920 1416 0 I+ 2:07PM 0:00.00 ./simplegets

doggoson 13398 0.0 0.1 16288 1776 1 S+ 2:08PM 0:00.00 grep simplegets

doggoson@fbsd:/home/doggoson % cat /proc/13381/map

0x400000 0x401000 1 0 0xfffffe003c103828 r-x 1 0 0x1000 COW NC vnode
/usr/home/doggoson/simplegets NCH -1

0x600000 0x800000 2 0 0xfffffe0016de89f8 rw- 1 0 0x3000 NCOW NNC default - CH
1001

0x800600000 0x800618000 24 0 0xfffffe00076ed658 r-x 90 0 0x1004 COW NC vnode
/libexec/ld-elf.so.1 NCH -1

0x800618000 0x800639000 21 0 0xfffffe001e195828 rw- 1 0 0x3000 NCOW NNC
default - CH 1001

0x800817000 0x800819000 2 0 0xfffffe0023bf22b8 rw- 1 0 0x3000 NCOW NNC default
- CH 1001

0x800819000 0x800947000 258 0 0xfffffe00076ed000 r-x 166 76 0x1004 COW NC
vnode /lib/libc.so.7 NCH -1

0x800947000 0x800b46000 0 0 0xfffffe005afdc9f8 --- 1 0 0x2000 NCOW NNC default -
NCH -1

0x800b46000 0x800b51000 11 0 0xfffffe00374cd9f8 rw- 1 0 0x3000 COW NNC vnode
/lib/libc.so.7 CH 1001

0x800b51000 0x800b6c000 8 0 0xfffffe0067d37740 rw- 2 0 0x3000 NCOW NNC default
- CH 1001

0x800c00000 0x801000000 8 0 0xfffffe0067d37740 rw- 2 0 0x3000 NCOW NNC default
- CH 1001

0x7ffffffdf000 0x7ffffffff000 3 0 0xfffffe00790363a0 rw- 1 0 0x3000 NCOW NNC default
- CH 1001
0x7ffffffff000 0x800000000000 0 0 0xfffffe0007515cb0 r-x 94 0 0x4 COW NC default -
NCH -1

doggoson@fbsd:/home/doggoson %


The suprise came when I ran simplegets a second time:

doggoson@fbsd:/home/doggoson % ps aux | grep simplegets

doggoson 13446 0.0 0.1 9920 1416 0 S+ 2:12PM 0:00.00 ./simplegets

doggoson 13449 0.0 0.1 16288 1776 1 S+ 2:12PM 0:00.00 grep simplegets

doggoson@fbsd:/home/doggoson % cat /proc/13446/map

0x400000 0x401000 1 0 0xfffffe003c103828 r-x 1 0 0x1000 COW NC vnode
/usr/home/doggoson/simplegets NCH -1

0x600000 0x800000 2 0 0xfffffe004a9b3910 rw- 1 0 0x3000 NCOW NNC default - CH
1001

0x800600000 0x800618000 24 0 0xfffffe00076ed658 r-x 90 0 0x1004 COW NC vnode
/libexec/ld-elf.so.1 NCH -1

0x800618000 0x800639000 21 0 0xfffffe00660a13a0 rw- 1 0 0x3000 NCOW NNC
default - CH 1001

0x800817000 0x800819000 2 0 0xfffffe00790390e8 rw- 1 0 0x3000 NCOW NNC default
- CH 1001

0x800819000 0x800947000 258 0 0xfffffe00076ed000 r-x 166 76 0x1004 COW NC
vnode /lib/libc.so.7 NCH -1

0x800947000 0x800b46000 0 0 0xfffffe00486fd910 --- 1 0 0x2000 NCOW NNC default -
NCH -1

0x800b46000 0x800b51000 11 0 0xfffffe00600819f8 rw- 1 0 0x3000 COW NNC vnode
/lib/libc.so.7 CH 1001

0x800b51000 0x800b6c000 8 0 0xfffffe00302672b8 rw- 2 0 0x3000 NCOW NNC default
- CH 1001

0x800c00000 0x801000000 8 0 0xfffffe00302672b8 rw- 2 0 0x3000 NCOW NNC default
- CH 1001

0x7ffffffdf000 0x7ffffffff000 3 0 0xfffffe007219f740 rw- 1 0 0x3000 NCOW NNC default
- CH 1001

0x7ffffffff000 0x800000000000 0 0 0xfffffe0007515cb0 r-x 94 0 0x4 COW NC default -NCH -1

doggoson@fbsd:/home/doggoson %


As you can see, all the memory addresses have not changed which shows that FreeBSD
lacks Address Space Layout Randomization or ASLR, an important security feature that all
other operating systems including Windows have.

Linux has ASLR as shown when simplegets is executed once:

doggoson@bluebook ~ $ ps aux | grep simplegets

doggoson 4134 0.0 0.0 4080 348 pts/0 S+ 13:59 0:00 ./simplegets

doggoson 4145 0.0 0.0 8052 916 pts/1 S+ 13:59 0:00 grep --colour=auto simplegets

doggoson@bluebook ~ $ cat /proc/4134/maps

00400000-00401000 r-xp 00000000 08:06 261421
/home/doggoson/Workspace/CC+/simplegets

00600000-00601000 rw-p 00000000 08:06 261421
/home/doggoson/Workspace/CC+/simplegets

7f704e324000-7f704e4c6000 r-xp 00000000 08:08 4461920 /lib/x86_64-linux
gnu/libc-2.17.so

7f704e4c6000-7f704e6c6000 ---p 001a2000 08:08 4461920 /lib/x86_64-linux
gnu/libc-2.17.so

7f704e6c6000-7f704e6ca000 r--p 001a2000 08:08 4461920 /lib/x86_64-linux
gnu/libc-2.17.so

7f704e6ca000-7f704e6cc000 rw-p 001a6000 08:08 4461920 /lib/x86_64-linux
gnu/libc-2.17.so

7f704e6cc000-7f704e6d0000 rw-p 00000000 00:00 0

7f704e6d0000-7f704e6f1000 r-xp 00000000 08:08 4461916 /lib/x86_64-linux
gnu/ld-2.17.so

7f704e8d0000-7f704e8d3000 rw-p 00000000 00:00 0

7f704e8ee000-7f704e8f1000 rw-p 00000000 00:00 0

7f704e8f1000-7f704e8f2000 r--p 00021000 08:08 4461916 /lib/x86_64-linux
gnu/ld-2.17.so

7f704e8f2000-7f704e8f4000 rw-p 00022000 08:08 4461916 /lib/x86_64-linuxgnu/ld-2.17.so

7fffdca09000-7fffdca2a000 rw-p 00000000 00:00 0 [stack]

7fffdca49000-7fffdca4b000 r-xp 00000000 00:00 0 [vdso]

ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]

doggoson@bluebook ~ $


and again

doggoson@bluebook ~ $ ps aux | grep simplegets

doggoson 4173 0.0 0.0 4080 348 pts/0 S+ 14:02 0:00 ./simplegets

doggoson 4176 0.0 0.0 8052 916 pts/1 S+ 14:02 0:00 grep --colour=auto simplegets

doggoson@bluebook ~ $ cat /proc/4173/maps

00400000-00401000 r-xp 00000000 08:06 261421
/home/doggoson/Workspace/CC+/simplegets

00600000-00601000 rw-p 00000000 08:06 261421
/home/doggoson/Workspace/CC+/simplegets

7f1e449ac000-7f1e44b4e000 r-xp 00000000 08:08 4461920 /lib/x86_64-linux
gnu/libc-2.17.so

7f1e44b4e000-7f1e44d4e000 ---p 001a2000 08:08 4461920 /lib/x86_64-linux
gnu/libc-2.17.so

7f1e44d4e000-7f1e44d52000 r--p 001a2000 08:08 4461920 /lib/x86_64-linux
gnu/libc-2.17.so

7f1e44d52000-7f1e44d54000 rw-p 001a6000 08:08 4461920 /lib/x86_64-linux
gnu/libc-2.17.so

7f1e44d54000-7f1e44d58000 rw-p 00000000 00:00 0

7f1e44d58000-7f1e44d79000 r-xp 00000000 08:08 4461916 /lib/x86_64-linux
gnu/ld-2.17.so

7f1e44f58000-7f1e44f5b000 rw-p 00000000 00:00 0

7f1e44f76000-7f1e44f79000 rw-p 00000000 00:00 0

7f1e44f79000-7f1e44f7a000 r--p 00021000 08:08 4461916 /lib/x86_64-linux
gnu/ld-2.17.so
7f1e44f7a000-7f1e44f7c000 rw-p 00022000 08:08 4461916 /lib/x86_64-linux
gnu/ld-2.17.so

7fff4049f000-7fff404c0000 rw-p 00000000 00:00 0 [stack]

7fff405fe000-7fff40600000 r-xp 00000000 00:00 0 [vdso]

ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]

doggoson@bluebook ~ $


As you can see, not only is the address space layout of simplegets neater and simpler but
more importantly, the memory addresses have changed showing that Linux is well
protected using ASLR.

It just goes to show, FreeBSD is not safer then Linux but rather the other way round.

As what Felix himself said, FreeBSD and possibly all other BSDs include OpenBSD lack modern security features. By comparison, even Microsoft Windows has an implementation of ASLR.

In the case of FreeBSD, it is particularly alarming as the FreeBSD project under IXsystems has been suspected of working with malicious organizations such as Apple, Microsoft, the CIA, NSA, and possibly even the KGB.

FreeBSD’s voluntary exclusion of protection mechanisms and the unwillingness of the FreeBSD community to discuss this issue with Felix shows that it is very likely that the FreeBSD project like the OpenBSD project intentionally makes their OS releases less secure to allow easy access for malicious agencies.

Richard Stallman, Linus Torvalds and the GNU/Linux community by contrast have show that such things are unacceptable in their OS releases and go though every measure to prevent that from happening.

Posted in Uncategorized | 9 Comments

“BSD hacker” – A self contradicting term

When ever I take a look at the BSD mailing lists, often see the term “BSD hacker” been used which is a huge irony.

The term hacker (before popular media used it for something else) is to describe a people how goes through lengths at trying to discover new ways to get more out of a piece of software or a piece engineering even to a extent in which it was not originally designed for. Hackers avoid reinventing the wheel and instead focus on discovering new things. This is in exact contrast BSD developers who consistently reinvent the wheel and stubbornly stick to outdating practices and technology even then it is causing them to fall behind. BSD developers thus are the extreme opposite of hackers.

Posted in Uncategorized | 4 Comments

Why do BSD people fear systemd?

Lets face it, it’s a software engineering marvel. There is no two ways about it. Fast, reliable, versatile and maintainable, systemd is an extremely powerful piece of technology that has revolutionized GNU/Linux and it has been working wonders on my new Arch Linux box and has made my life much easier. No doubt I have heard from many others saying the same thing all around blogs and forums. The one place I did not hear nice things about systemd is the same place in which I never hear anything nice about Linux. BSD people’s mouths (example: scalisblog, freebsd forums etc.).

But systemd was not made for BSD and has not been running on BSD ever so why are these mindless zealots making such fuss and accusations about it?

It’s because more and more FLOSS applications are integrating with systemd and thus making use of the advanced features it offers. However in doing so, they effectively incorporate features that can only be satisfied by the Linux kernel and thus making them difficult or impossible to port to other non-Linux kernels such as the BSDs. This will inevitably lead to the BSD’s being starved of both properly working server and desktop applications and environments (e.g. GNOME, Xfce etc.) which will in turn reduce the usefulness and attractiveness of BSD even farther.

So is it the GNU/Linux people’s problem that this sort of thing happened? Absolutely not. The fault is with the BSDs which fail to keep up as they cannot expect GNU/Linux developers to slow down just for them. GNU/Linux developers also should not be burdened with making their software portable and helping BSD as it would be silly to help out your competitors especially in this case when the competitors are proprietary friendly pieces of junk. In fact the greatest advantage of systemd is that it can be used as a tool for free software projects to prevent their software from being ported to BSD.

In effect, systemd is becoming the bane of BSD.

Posted in Uncategorized | 7 Comments

BSD encourages slavery: Sony’s Orbis OS

As you know, news has been that Sony’s new Orbis OS is based on FreeBSD. This new BSD based operating system will include the latest of Sony’s DRM tracking system which will be used to control the machines of it’s customers. All this using BSD: the Operating system what is claimed to be freer and more secure then Linux by it’s zealots. No doubt a lot of right minded people hate BSD people because of it’s prostitute like attitude towards proprietary companies like Apple, Microsoft and lately, Sony (except that prostitutes demand money in return while BSD people let it be taken away free and later beg for money). Phoronix has some exceptional thinkers commenting about this issue faced by free and open source software community as shown here:

Three of the most respectable people I find here are brosis, Pawlerson and especially 0xBADCODE as shown by their arguments against moronic BSD supporters. I know 0xBADCODE from his posts, and his a very smart and wise guy. Like me, he tried out FreeBSD before and experienced the horrors of it’s poor design and just how much BSD developers do not care about their users and instead focus on pleasing their proprietary masters. In the Phoronix trend (link above), 0xBADCODE explains in the greatest detail possibly which BSD should not be used by anyone and for anything.

Going back to Sony and BSD, Sony’s misuse of BSD licensed code to create freedom stripping software/spyware makes it clear that BSD’s license has not guaranteed more freedom to both users and developers. On the contrary it has merely done the opposite and the effects are so much worse then what Microsoft has done.

Sony and Freedom

Sony is a company that is obsess with surveillance, control and domination of not just it’s customers but of people in general and so much so that they resort to security cracking techniques and practices to achieve those ends. An example of this is the ‘Sony BMG “copy protection” rootkit scandal’ where Sony programmed musics CDs such that when they are inserted into a computer, they install a rootkit which modifies the victim operating system to prevent users from burning CDs of any type even if they weren’t from Sony. The rootkit was also programmed to report all user activities to Sony and also allow Sony to remotely wipe the victim’s hard drive or force shutdown their computer. When the sandal was revealed, Sony decided to defend it’s actions and continue instead of stopping and hiding what it has done. They smirking replied that: “Most users do not know what a rootkit is and therefore they should not care about it”. It just goes not show that Sony is nothing more then a “Company” of black-hat crackers who’s purpose is to subvert people’s freedoms. And they do it with BSD license code.

Sony has use GNU/Linux in some of it’s hardware but with the creation of the new GPLv3 and it’s anti-DRM clauses, Sony was forced to abandon it as much of the GNU tools and software that came with GNU/Linux became GPLv3.

BSD licenses and Malicious DRMs

Analysis of Sony’s rootkit and many of other Sony and Apple products shows that they contain BSD code fused together with a DRM or corporate originated rootkits. As a matter of fact, a number research projects have found that 99% of all previously and currently BSD-licensed code are shipped with DRMs or other types of tracking and remote control software. This includes Microsoft Windows, Apple Mac OSX, Solaris, AIX, HP-UX and OpenVMS. The only BSD licensed code that comes DRM free are the ones in GNU/Linux in which the GPL prevents DRMs and other company created spyware form being added to the code.

If you are use one of the “free” BSD versions such as “Free”BSD, OpenBSD and NetBSD and think you are running BSD code without any DRMs or spyware whatsoever, think again. “Free”BSD’s proprietary NVidia graphics driver was found to be a DRM rootkit that allows remote control and access of any “Free”BSD machine even if the driver is not in use. Apple has apparently added a DRM in it’s clang compiler that causes FreeBSD to slow down and sometimes even crash when GCC is being used instead.

Theo de Raadt, the infamous dictator of the OpenBSD project and bondage enthusiast as made an agreement with proprietary company Secure Networks allowing them to place a rootkit in OpenBSD in exchange for Secure Networks to make OpenBSD more “secure” and also lately, the implementation of the FBI OpenBSD remote backdoor.

With all this happening people have to be thankful of Stallman’s creation of the GPLv3 which gives software and people protection from these horrible things.

What benefit do the BSD projects get from this?

The answer is the opposite, they literally give up code. Because their moronic BSD license allows the change of the copyright as modification of the source code, the BSD serfs will have to remove the part of their code that Sony used. Therefore the BSDs do not benefit, they don’t even get nothing. They lose the right to their code. This is why BSD is so far behind GNU/Linux in everything. There is no other word to call it. It’s slavery and the BSD people deserve it as well as their other misfortunes but what’s extremely sad is that their own actions are causing the slavery of others.

Really the only way to stop this atrocity by these BSD serfs is to ban BSD style licensing altogether.

Posted in Uncategorized | 4 Comments

PC-BSD is spyware

Recently, I found something interesting about PC-BSD in FreeBSD forums:

http://forums.freebsd.org/showthread.php?t=29432

Apparently, PC-BSD tracks and performs surveillance on its users using a harmless looking app called BSDstats thus intruding on the user’s privacy just as what Microsoft and Apple does with their products. I did more research and found out that there is something more sinister behind this and it is one of the things which shows to people why PC-BSD is dangerous to user’s who have sensitive information and that no one should even think about using it.

For those of you who don’t know, PC-BSD is an agreement and joint effort by Apple and IXsystems to create an operating system to lure Linux users and developers away from using and developing freedom respecting software like GNU/Linux to using and developing proprietary friendly software such as BSD. To hide their involvement with PC-BSD, IXsystems selected salesman and long time GNU/Linux hater and convicted serial killer Matt Olander to be the man in charge of ads and information censorship in the PC-BSD project. Meanwhile, Apple CEO Steve Jobs personally selected Kris Moore, an abusive Apple project manager and an intensely passionate free software hater to be the project figure-head. The PC-BSD project’s development team consist of ex-FreeBSD and Apple developers all of which were commissioned by Apple to develop FreeBSD into a more seemingly user-friendly system. However, their efforts when sour as PC-BSD turned out to be extremely slow, frequently crashes and could not be installed on most hardware just like FreeBSD. Attempts to improve PC-BSD in versions 8 and 9 have so far worsen the problem.

Due to all these difficulties, PC-BSD failed to achieve mass adoption and what little usage it originally had started to declined by 2009. Kris Moore and Matt Olander began looking for ways to make false statistical data in which PC-BSD usage seemed to be higher then it really is so as to be able to advertise their horrible mess much more favorably. They soon came up with enforcing a tracking system which sends information from a computer running PC-BSD back to Apple and IXsystem which adds a count to a database which they can then alter and then publish as advertisement. This tracking system would send this signal to Apple and IXsystem headquarters once a month to into a system which registers one signal as one PC-BSD machine coming online.

Moore and Olander soon came up with an extra use for BSDstats. Obtaining personal information on computers running PC-BSD. Olander, who has a history of murdering a number of Linux developers decided that he can use this system to track down and harm high profile Linux, GNU and FSF developers what he failed to remove. Apple and IXsystems meanwhile made a deal with the extremely anti-Free software company nVidia in which PC-BSD will be provided with the latest of NVidia proprietary blobs in exchange for transfer of private information and remote control of PC-BSD users’ computer through their NVidia binary blob drivers.

This is clearly a breach and violation of freedom and human rights and it just shows that PC-BSD is nothing more then spyware and that nobody should use it.

Posted in Uncategorized | 2 Comments

NetBSD: Proven insecure and flawed

we were browsing through google for some information and we found this conference talk about NetBSD rootkits also the mismanagement of security in NetBSD.

What shocked us most is the fact that NetBSD never bothers to update security software within their pkgsrc tree and thus NetBSD users are left with out-dated and useless anti-virus, firewalls and rootkit detection software. In Linux, this sort of thing is never tolerated and software are constantly patched and updated which just goes to show that Linux is still better then anything BSD can hope to be.

Video | Posted on by | 3 Comments