the
infinite quark 00+-00 charged with N command virus synthetis took 2
million clorate particles to hang over an assymetric LAN where the orbit
lives
let
me try to divide this: the infinite electrical charge of a null number
on a loop command input over a virus cure took 2 million chemical
chlorate formulas to live over an orbit which is build on a LAN
why
not consider the universe as a vaccum without gas molecules, and make
an experience of creating an explosion by the chock of two vaccumns
libertation on hydrogene
and let's consider that the hydrogene is the pressure created by the vaccumns
Elsa David
I was crying over here, but not alone; this is so very difficult to
swallow, and Jesus did not ask me my opinion, if I would or would not
like to be part of a God's plan; Maybe he has a reward of me, I'm not
excpeting; but then, nevertheless, God has never been Justice; What's
God then? and why do we keep on trying to explain where the universes
begun? If the universes are infinite, God is infinite, the beggining is
infinite, and the end is infinite; if they have will meet? Well,
time as a measure shrinked in the year 2000, there's no more 24 hours,
but 23.57 minutes; the universe shrinked then, all the orbits
shrinked...are we running for the end? but ...why do we keep on using
the same category of measuring? time, has seconds, distance as meters,
liquids as gallons??? why not measure a neutron with the measure of
virus? of cells composition? and why using numbers for the couting of
cells, and not letters? and why are this language letters and not
numbers? and why computaion is symbols, letters and numbers, and not
cells? and why not giving cells chemical compositions with concepts and
not numbers? and so on..as soon we get to think without pre formed
languages, with numbers, we might make a different question, and get the
answer, who is God, where the begging of "virus" of choloratesynthesis
begun?
Wednesday, June 8, 2016
https://issuu.com/alabarga/docs/hacker_s_manual_2015_-_power_up_you/1 PAGE 81 Here is what happens in a minimal system boot: A typical small ARM-style system doesn't have a 'BIOS' or 'EFI' or
anything on it. When you 'turn on' the system then voltage is applied to
the 'SoC' and the processor immediately begins executing any code that
may exist at address 0x0 (or 0x8000 or whatever it is for that
particular processor). This corresponds to physical traces on the
motherboard and a flash chip. That flash will be programmed with your 'Boot loader'. You see the
SoC doesn't understand how the hardware is configured or anything like
that. It doesn't know what the pins on the processor does or how to use
main memory. It doesn't know how to read your SD card or turn on a
network interface or anything like that. The bootloader must actually
program the low-level interfaces on the SoC to even begin to be using
memory or anything like that. As a programmer it would be your job to
know how to flip the bits and detect memory so that the computer can
begin using it. Then whatever storage device you want to use for the
OS.. you have to configure that also. Just a minimal amount to activate
the larger storage device and load and execute the Linux kernel. So a operating system doesn't actually need any sort of 'firmware' at
all. There is no absolute need for a BIOS or EUFI or anything like
that. The Linux kernel itself can do all the configuration that is
necessary, but you need something very specific to that mainboard that
knows how to do the lowest levels of configuration.. which is what
coreboot is for. Which is why on your ARM-based phone or MIPS router or whatever you
can 'brick' it by a doing a bad bootloader flash. Without a functioning
bootloader there is no way to interact with the hardware. (Although
modern systems are incorporating more features to avoid these problems
and make it more friendly to ham-fisted firmware updaters) The BIOS originally was developed as a sort of ghetto operating system. It was designed for a era were you didn't have operating systems. You
had single-task machines that when they booted they just launched a
single application. The BIOS then provided a set of functions and resources that
applications could use to run. It had some fonts, CGA graphics API,
ability to read floppy drives and that sort of thing. The BIOS really is a API of sorts. Cracking and cloning the BIOS was a huge step forward for PC systems
because for the first time it allowed applications written for one PC to
be executed successfully on a PC clone. Later on people produced disk operating systems... which all they did
was provide a file system for managing files on a disk. MS-DOS was one
of many for x86 systems, but many other types of architectures had DOS
systems as well. When Microsoft finally started coming out with real operating systems
like Windows 95 for the PC the BIOS was used for boot strapping the OS.
The x86 'bootloader' is then really a x86 BIOS program used to launch
OSes. Of course Windows 95 wasn't that smart so you still relied on
the BIOS to configure bits and pieces of hardware. Later on, of course, you had things like ACPI so that the OS had a
standardized way to interact with the hardware for power management
among other things. So with x86 you had a sort of 'dual OS' thing going were you had this
stupid ghetto OS people referred to as the 'BIOS' or 'Firmware' and
then the real OS for running applications. The BIOSes typically are kinda shit. They are going to be specific to
specific hardware, but typically how they are programmed is that they
are copy and pasted from older mainboard designs and then screwed around
with until they boot windows. So in your BIOS-based x86 system you
will have lots of bastardized code that is floating around that is
designed to run hardware from 20 years ago. This sort of thing is why Linux kernel programmers have to spend a
great deal of time 'undoing' the damage caused to your system by it's
BIOS. These sorts of things have some benefits, of course. When you load a
OS and bootloader for x86 the hardware is 'made generic' through the
use of the BIOS. If you ever tried to build your own OS for a smart
phone you'd realize that you need to program and build the kernel and
bootloader for that specific device... that is a kernel/bootloader from a
different system won't work because the hardware is different. With
X86 systems the BIOS hides the details and allows a single binary
bootloader and kernel to easily work across a wide variety of systems. UEFI, is then, a modernized BIOS. Instead of having a mixture of
ancient x86 machine code and assembly written by retarded monkeys they
have much more 'modern' approach. It is much more sophisticated and flexible. It has it's own
programming languages and interpreters. Firmware on UEFI-enabled devices
like video cards can load their own 'drivers' that allow them to be
used directly by UEFI. All sorts of crap like that. Which is why now you can have these really fancy 'graphical' EUFI
configuration screens. The UEFI firmware on your peripheral devices can
provide rich interfaces for how to interact with the hardware. Unfortunately this means that it's extremely complicated and big. The
firmware is now as big and complicated as a full-fledged OS. Complicated and big is bad. This means more bugs. Some bugs are
security bugs so more bugs means more security holes. Also it's
generally proprietary so you have different groups of people trying to
write the same thing from scratch so they can inject their 'secret
sauce'. So now not only you have something that is big and buggy, but
also has lots of different sets of unique bugs. But it still allows Microsoft to crank out one binary that works generically across a bunch of different hardware. Also it allows for a lot of fancy new ways to manage your hardware
independently of the OS. Which while often convenient it is also going
to be full of bugs and is proprietary. Which is going to be especially
bad when the UEFI stuff allows for remote configuration and will piggy back on your network interfaces and doesn't go away completely when the real OS is loaded. edit: Thank you for the reddit gold very much.
XSS attacks are from
http://ha.ckers.org/xss.html. Caveats:Google.com has been programatically disallowed, but as you can
see, there are ways of getting around that, so coverage in this area
is not complete. Most XSS broadcasts its presence by spawning an alert dialogue.
The displayed code is not strictly correct, as linebreaks have been forced for
readability. Linewraps have been marked with ». Some tests are
omitted for your convenience. Not all control characters are displayed.
src="j%20a%20v%20a%20s%20c%2 »
0r%20i%20p%20t%20%3A%20a%20l »
%20e%20r%20t%20(%20'%20X%20S »
%20S%20'%20)" alt="j a v a s »
c r i p t : a l e r t ( ' X »
S" />
I will introduce you to new hacking tools
and techniques, though, one tool that we will be using in all of those
areas is called the Browser Exploitation Framework, or BeEF (don't ask
me what the lowercase "e" stands for).
Similar to Metasploit, BeEF is a
framework for launching attacks. Unlike Metasploit, it is specific to
launching attacks against web browsers. In some cases, we will be able
to use BeEF in conjunction with Metasploit to launch particular attacks,
so I think its time for us to become familiar with it.
BeEF was developed by a group of developers led by Wade Alcorn.
Built on the familiar Ruby on Rails platform, BeEF was developed to
explore the vulnerabilities in browsers and test them. In particular,
BeEF is an excellent platform for testing a browser's vulnerability to
cross-site scripting (XSS) and other injection attacks.
Step 1: Start Cooking BeEF
BeEF is built into Kali Linux, and it can be started as a service and
accessed via a web browser on your localhost. So let's start by firing
up Kali and cooking a bit of BeEF. Start the BeEF service by going to
"Applications" -> "Kali Linux" -> "System Services" -> "BeEF"
-> "beef start."
Step 2: Opening a Browser to BeEF
The BeEF server can be accessed via any browser on our localhost
(127.0.0.1) web server at port 3000. To access its authentication page,
go to:
http://localhost:3000/ui/authentication
The default credentials are "beef" for both username and password.
Great! Now you have successfully logged into BeEF and are ready to begin using this powerful platform to hack web browsers.
Note that in the screenshot below that
my local browser, 127.0.0.1, appears in the left hand "Hooked Browsers"
explorer after I clicked on the link to the demo page. BeEF also
displays its "Getting Started" window to the right.
Step 3: Viewing Browser Details
If I click on the local browser, it will
provide with more choices to the right including a "Details" window
where we can get all the particulars of that browser. Since I am using
the Iceweasel browser built into Kali, which is built upon Firefox, it
shows me that the browser is Firefox.
It also shows me the version number
(24), the platform (Linux i686), any components (Flash, web sockets,
etc.), and more information that we will be able to use in later web
application hacks.
Step 4: Hooking a Browser
The key to success with BeEF is to "hook" a browser. This basically
means that we need the victim to visit a vulnerable web app. This
injected code in the "hooked" browser then responds to commands from the
BeEF server. From there, we can do a number of malicious things on the
victim's computer.
BeEF has a JavaScript file called
"hook.js," and if we can get the victim to execute it in a vulnerable
web app, we will hook their browser! In future tutorials, we will look
at multiple ways to get the victim's browser hooked.
In the screenshot below, I have "hooked" an Internet Explorer 6 browser on an old Windows XP on my LAN at IP 192.168.89.191.
Step 5: Running Commands in the Browser
Now, that we have hooked the victim's browser, we can use numerous
built-in commands that can executed from the victim's browser. Below are
just a few examples; there are many others.
Get Visited Domains
Get Visited URLs
Webcam
Get All Cookies
Grab Google Contacts
Screenshot
In the screenshot below, I selected the
"Webcam" command that many of you may be interested in. As you can see,
when I execute this command, an Adobe Flash dialog box will pop up on
the screen of the user asking, "Allow Webcam?" If they click "Allow," it
will begin to return pictures from the victim's machine to you.
Of course, the text can be customized,
so be imaginative. For instance, you could customize the button to say
"You have just won the lottery! Click here to collect your winnings!" or
"Your software is out of date. Click here to update and keep your
computer secure." Other such messages might entice the victim to click
on the box.
Step 6: Getting Cookies
Once we have the browser hooked, there is almost unlimited possibilities
of what we can do. If we wanted the cookies of the victim, we can go to
"Chrome Extensions" and select "Get All Cookies" as shown in the
screenshot below.
When we click on the "Execute" button to
the bottom right, it will begin collecting all the cookies from the
browser. Obviously, once you have the user's cookies, you are likely to
have access to their websites as well.
BeEF is an extraordinary and powerful
tool for exploiting web browsers. In addition to what I have shown you
here, it can also be used to leverage operating system attacks. We will
be using it and other tools in my new series on hacking web
applications, mobile devices, and Facebook, so keep coming back, my
greenhorn hackers.
