<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[Proxmark developers community]]></title>
	<link rel="self" href="http://www.proxmark.org/forum/feed/atom/"/>
	<updated>2010-03-16T16:19:02Z</updated>
	<generator>PunBB</generator>
	<id>http://www.proxmark.org/forum/</id>
		<entry>
			<title type="html"><![CDATA[how to start camera in Imote2 IIB400?]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/523/how-to-start-camera-in-imote2-iib400/new/posts/"/>
			<summary type="html"><![CDATA[<p>Recently i am doing some work on imote2 board and now stopped at the point of<br />how to start the camera(IIB400) on the board.</p><p>1111-------What was done is followed the instruction of this website:<br /><a href="http://sourceforge.net/apps/mediawiki/imote2-linux/index.php?title=IMB400_Multim\">http://sourceforge.net/apps/mediawiki/i &#133; 00_Multim\</a><br />edia_Sensorboard</p><p>2222-------The main steps is:<br /># I2C<br />cd /lib/modules/2.6.29.1.rc1_1/kernel/drivers/i2c/algos<br />insmod i2c-algo-bit.ko<br />cd ../busses<br />insmod i2c-gpio.ko</p><p># CAMERA<br />cd /lib/modules/2.6.29.1_r1.1/kernel/drivers/media/video<br />insmod videobuf-core.ko<br />insmod videodev.ko<br />insmod v4l2-common.ko<br />insmod v4l2-int-device.ko<br />insmod videobuf-dma-sg.ko<br />insmod soc_camera.ko<br />insmod pxa_camera.ko<br />insmod ov7670_soc.ko</p><p>mknod /dev/video0 c 81 0</p><p>3333-------and i can get the /dev/video0 appeared, however ,when i tried:<br />capture -d/dev/video0</p><p>the message comes out like this:<br />[root@SG2-3 webcam]#./capture -d /dev/video0<br />Can&#039;t open device /dev/video0</p><p>4444-------The same result comes out again when i wrote a c program to test the drivers by<br />myself :<br />[root@SG2-3 /root]#./cameraTest<br />v4l_open:: No such device or address</p><p>5555-------If anyone has any experience ,suggestions or knows how to solve it ,please give<br />me a hand . Thanks million in advance!!!</p><br /><p>Starry</p>]]></summary>
			<author>
				<name><![CDATA[stary]]></name>
				<uri>http://www.proxmark.org/forum/user/1410/</uri>
			</author>
			<updated>2010-03-16T16:19:02Z</updated>
			<id>http://www.proxmark.org/forum/topic/523/how-to-start-camera-in-imote2-iib400/new/posts/</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Buffer overflow when issuing "data plot"]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/522/buffer-overflow-when-issuing-data-plot/new/posts/"/>
			<summary type="html"><![CDATA[<p>Hi folks,</p><p>I am running into problems, when issuing the command &quot;data plot&quot; in my proxmark3 binary compiled with the lates svn sources on linux kernel 2.6.31-20 with libqt4-dev present. Compilation runs without errors:</p><p>(....)<br />g++ -DQT_SHARED -I/usr/include/qt4 -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui&nbsp; &nbsp;-Wall -O3 -c -o obj/proxgui.o proxgui.cpp<br />g++ -DQT_SHARED -I/usr/include/qt4 -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui&nbsp; &nbsp;-Wall -O3 -c -o obj/proxguiqt.o proxguiqt.cpp<br />/usr/bin/moc-qt4 -oproxguiqt.moc.cpp proxguiqt.h<br />g++ -DQT_SHARED -I/usr/include/qt4 -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui&nbsp; &nbsp;-Wall -O3 -c -o obj/proxguiqt.moc.o proxguiqt.moc.cpp<br />g++ -DQT_SHARED -I/usr/include/qt4 -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui&nbsp; &nbsp;-Wall -O3 obj/proxmark3.o obj/crc16.o obj/iso14443crc.o obj/data.o obj/graph.o obj/ui.o obj/cmddata.o obj/cmdhf.o obj/cmdhf14a.o obj/cmdhf14b.o obj/cmdhf15.o obj/cmdhflegic.o obj/cmdhw.o obj/cmdlf.o obj/cmdlfem4x.o obj/cmdlfhid.o obj/cmdlfti.o obj/cmdparser.o obj/cmdmain.o obj/proxusb.o obj/proxgui.o obj/proxguiqt.o obj/proxguiqt.moc.o -L/opt/local/lib -L/usr/local/lib -lusb -lreadline -lpthread -lQtGui -lQtCore&nbsp; &nbsp;-o proxmark3<br />(....)</p><p>The binary works perfectly well - until it comes to the point where I want to plot the data. Here I get a buffer overflow with the following Backtrace:</p><p>proxmark3&gt; data plot<br />proxmark3&gt; *** buffer overflow detected ***: ./proxmark3 terminated<br />======= Backtrace: =========<br />/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0x75ced8]<br />/lib/tls/i686/cmov/libc.so.6[0x75bf10]<br />/lib/tls/i686/cmov/libc.so.6[0x75b648]<br />/lib/tls/i686/cmov/libc.so.6(_IO_default_xsputn+0x9e)[0x6e559e]<br />/lib/tls/i686/cmov/libc.so.6(_IO_vfprintf+0xe1c)[0x6b995c]<br />/lib/tls/i686/cmov/libc.so.6(__vsprintf_chk+0xad)[0x75b6fd]<br />/lib/tls/i686/cmov/libc.so.6(__sprintf_chk+0x2d)[0x75b63d]<br />./proxmark3[0x805798c]<br />/usr/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x524)[0xa65dd4]<br />/usr/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xb4)[0xa10f54]<br />/usr/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0xda)[0xa185ca]<br />/usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x7b)[0x5886cb]<br />/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate10drawWidgetEP12QPaintDeviceRK7QRegionRK6QPointiP8QPainterP19QWidgetBackingStore+0x525)[0xa6de25]<br />/usr/lib/libQtGui.so.4[0xbfc2f8]<br />/usr/lib/libQtGui.so.4[0xbfc77a]<br />/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate16syncBackingStoreERK7QRegion+0x65)[0xa5f055]<br />/usr/lib/libQtGui.so.4[0xa77090]<br />/usr/lib/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0x1462)[0xa856f2]<br />/usr/lib/libQtGui.so.4[0xab2502]<br />/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1f8)[0x7f9e88]<br />/lib/libglib-2.0.so.0[0x7fd730]<br />/lib/libglib-2.0.so.0(g_main_context_iteration+0x73)[0x7fd863]<br />/usr/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5c)[0x5b302c]<br />/usr/lib/libQtGui.so.4[0xab1be5]<br />/usr/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x49)[0x586c79]<br />/usr/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xfa)[0x5870ca]<br />/usr/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0xaf)[0x58953f]<br />/usr/lib/libQtGui.so.4(_ZN12QApplication4execEv+0x27)[0xa10dd7]<br />./proxmark3[0x8055c07]<br />./proxmark3[0x804b49f]<br />/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x692b56]<br />./proxmark3[0x804b391]</p><p>Has anybody here an idea how to solve this problem?!</p><p>Any help is greatly appreciated!</p><p>Regards,<br />Tom</p>]]></summary>
			<author>
				<name><![CDATA[TomCyber]]></name>
				<uri>http://www.proxmark.org/forum/user/1427/</uri>
			</author>
			<updated>2010-03-15T13:18:52Z</updated>
			<id>http://www.proxmark.org/forum/topic/522/buffer-overflow-when-issuing-data-plot/new/posts/</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Hitag2 crack ne1?]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/222/hitag2-crack-ne1/new/posts/"/>
			<summary type="html"><![CDATA[<p>Hi all, </p><p>i was wondering, since the Hitag2 algorithm is practically the same as crypto1, is there anyone who has modified crapto1 to crack hitag2 keys? As far as I can tell, one would need to change some constants, but does hitag2 possess the same weaknesses as crypto1?</p>]]></summary>
			<author>
				<name><![CDATA[CardSaysMoops]]></name>
				<uri>http://www.proxmark.org/forum/user/17/</uri>
			</author>
			<updated>2010-03-15T04:12:05Z</updated>
			<id>http://www.proxmark.org/forum/topic/222/hitag2-crack-ne1/new/posts/</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[PM3 LCD]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/436/pm3-lcd/new/posts/"/>
			<summary type="html"><![CDATA[<p>I&#039;ve uploaded the required files to build the portable LCD version PM3 for those that were keen on it. Currently sitting in /Uploads but Roel might move them to /Hardware Revisions/experimental/PM3-LCD soon <img src="http://www.proxmark.org/forum/img/smilies/wink.png" width="15" height="15" alt="wink" /></p><p>All the parts required to build it can be obtained from 3 suppliers, PCB from batchpcb.com (3 weeks lead), LCD from sparkfun.com (1 week) everything else from Digikey.com (1 week).</p><p>Read the readme file, any other questions, post them here on the forum and I&#039;ll answer them. As I&#039;ve said before, I&#039;ve built this already and field tested it without any real issues but I sent the assembled device to someone. I have more parts coming next week to make another one for myself.</p><p>I understand that most people don&#039;t want to make their own due to the difficulty of soldering small parts. I&#039;m half thinking at looking into getting some assembled. If for argument&#039;s sake a complete board cost, say $350 USD (same as the original PM3) would you consider purchasing?</p><p><a href="http://farm3.static.flickr.com/2679/4247225606_939c63f8c7_b.jpg"><span class="postimg"><img src="http://farm3.static.flickr.com/2679/4247225606_939c63f8c7_m.jpg" alt="http://farm3.static.flickr.com/2679/4247225606_939c63f8c7_m.jpg" /></span></a> <a href="http://farm5.static.flickr.com/4061/4247225730_91878b45d0_b.jpg"><span class="postimg"><img src="http://farm5.static.flickr.com/4061/4247225730_91878b45d0_m.jpg" alt="http://farm5.static.flickr.com/4061/4247225730_91878b45d0_m.jpg" /></span></a></p>]]></summary>
			<author>
				<name><![CDATA[d18c7db]]></name>
				<uri>http://www.proxmark.org/forum/user/120/</uri>
			</author>
			<updated>2010-03-14T20:56:19Z</updated>
			<id>http://www.proxmark.org/forum/topic/436/pm3-lcd/new/posts/</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Proxmark3 not found]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/521/proxmark3-not-found/new/posts/"/>
			<summary type="html"><![CDATA[<p>/proxmark3/linux# ./proxmark3<br />detach kernel driver failed: (-113) could not detach kernel driver from interface 0: No route to host!<br />claim failed: could not claim interface 0: No such file or directory!<br />PROXMARK3: NOT FOUND!<br />proxmark3&gt; exit</p><br /><p>I am in a Mac Book running this thru a Linux VM.&nbsp; <br />Any ideas?</p>]]></summary>
			<author>
				<name><![CDATA[loganWHD]]></name>
				<uri>http://www.proxmark.org/forum/user/1513/</uri>
			</author>
			<updated>2010-03-12T22:01:03Z</updated>
			<id>http://www.proxmark.org/forum/topic/521/proxmark3-not-found/new/posts/</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Compiling Errors]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/520/compiling-errors/new/posts/"/>
			<summary type="html"><![CDATA[<p>Ok so I got the p3 and tried with Make had a few errors<br />came here and saw the post on the armdevkit<br />Tried that.<br />I am on a Debian Based System, BackTrack 4</p><p>When I go to the dir I get this:<br />bt4:~/proxmark3/linux/proxmark3-read-only# make<br />make -C bootrom all<br />make[1]: Entering directory `/root/proxmark3/linux/proxmark3-read-only/bootrom&#039;<br />perl ../tools/mkversion.pl .. &gt; version.c || cp ../common/default_version.c version.c<br />arm-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=gnu99 -I. -mthumb -mthumb-interwork -o obj/version.o version.c<br />make[1]: arm-eabi-gcc: Command not found<br />make[1]: *** [obj/version.o] Error 127<br />make[1]: Leaving directory `/root/proxmark3/linux/proxmark3-read-only/bootrom&#039;<br />make: *** [bootrom/all] Error 2</p>]]></summary>
			<author>
				<name><![CDATA[loganWHD]]></name>
				<uri>http://www.proxmark.org/forum/user/1513/</uri>
			</author>
			<updated>2010-03-12T21:47:48Z</updated>
			<id>http://www.proxmark.org/forum/topic/520/compiling-errors/new/posts/</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Contents of a legic card]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/519/contents-of-a-legic-card/new/posts/"/>
			<summary type="html"><![CDATA[<p>Hi all,</p><p>I read the contents of a legic card (has 2 segments).<br />I have some questions regarding there segments:<br />- I think 2 segments = 2 card applications, right?<br />- contain the segments any further structure or are they plain playload data (e.g. like file contents)<br />- has the content any relation to legic (or any other standard) or is the manfucturer free to write what he wants in the payload (use his own &quot;standard&quot;)?</p><p>Thanks in advance ...</p><br /><p>Best regards from Germany</p><p>BKone</p>]]></summary>
			<author>
				<name><![CDATA[BKone]]></name>
				<uri>http://www.proxmark.org/forum/user/1209/</uri>
			</author>
			<updated>2010-03-12T16:38:04Z</updated>
			<id>http://www.proxmark.org/forum/topic/519/contents-of-a-legic-card/new/posts/</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[iso15693 cards crashing proxmark3]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/488/iso15693-cards-crashing-proxmark3/new/posts/"/>
			<summary type="html"><![CDATA[<p>current firmwares are crashing when using &quot;hi15reader&quot;/&quot;hf 15 reader&quot; with an iso15693 skidata card. they finish correctly when no card is in reading distance:</p><p>&gt; hi15reader<br />#db# 0 octets read from IDENTIFY request: 0 0 0 0 0 0<br />#db# 0 octets read from SELECT request: 0 0 0 0 0 0 0<br />#db# 807415840 octets read from XXX request: 0 0 0 0 </p><p>when a card is in vicinity:<br />&gt; hi15reader<br />#db# 12 octets read from IDENTIFY request: 0 0 55 4e <br />proxmark3&gt; read failed: No error(-19)!<br />Trying to reopen device...</p><p>i&#039;ve tested this behavior with different skidata iso15k cards.</p><p>I remember older firmwares, worked fine.</p>]]></summary>
			<author>
				<name><![CDATA[*dudux]]></name>
				<uri>http://www.proxmark.org/forum/user/1277/</uri>
			</author>
			<updated>2010-03-11T17:09:37Z</updated>
			<id>http://www.proxmark.org/forum/topic/488/iso15693-cards-crashing-proxmark3/new/posts/</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Was decoding wonderfully, but now isn't?? (Windows binary Winter 2010)]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/516/was-decoding-wonderfully-but-now-isnt-windows-binary-winter-2010/new/posts/"/>
			<summary type="html"><![CDATA[<p>I am using the windows binary package Winter 2010, all the firmware flashed to those versions, and the client from that too.&nbsp; I was able to decode a 125KHz card that is just like in this article:<br /><a href="http://code.google.com/p/proxmark3/wiki/TagOps">http://code.google.com/p/proxmark3/wiki/TagOps</a><br />And all the traces looked the same as in the article, and I was able to correlate the number on the card with the stuff I decoded - woot!</p><p>However, I then decided to further explore the commands available in the Help system, to see what they all did.&nbsp; At some point the traces STOPPED looking like the article...&nbsp; So I did a device reset, and still, the same commands with the same card no longer produce any meaningful output!&nbsp; I still get a significant tune voltage drop when the card is on the antenna, but the data plot output is not all nice like it used to be.&nbsp; Sadly I didn&#039;t save the trace when it was nice, but it really looked exactly like this, from that tutorial:<br /><span class="postimg"><img src="http://proxmark3.googlecode.com/svn/wiki/symbol-1.png" alt="Good looking trace" /></span></p><p>Now here&#039;s what it looks like, it varies between these two patterns.&nbsp; I&#039;ve included trace files:<br /><span class="postimg"><img src="http://imgur.com/HYP3w.jpg" alt="http://imgur.com/HYP3w.jpg" /></span><br /><a href="http://www.mediafire.com/file/yezng25tjzy/%20badtrace">http://www.mediafire.com/file/yezng25tjzy/%20badtrace</a> Trace file 1</p><p><span class="postimg"><img src="http://imgur.com/ywAvi.jpg" alt="http://imgur.com/ywAvi.jpg" /></span><br /><a href="http://www.mediafire.com/file/mit3j42ykjw/%20badtrace2">http://www.mediafire.com/file/mit3j42ykjw/%20badtrace2</a> Trace file 2</p><p>Any suggestions on getting that nice mode back?<br />Thank you<br />CSM</p>]]></summary>
			<author>
				<name><![CDATA[CardSaysMoops]]></name>
				<uri>http://www.proxmark.org/forum/user/1494/</uri>
			</author>
			<updated>2010-03-10T15:56:08Z</updated>
			<id>http://www.proxmark.org/forum/topic/516/was-decoding-wonderfully-but-now-isnt-windows-binary-winter-2010/new/posts/</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Winter '10 - test release]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/506/winter-10-test-release/new/posts/"/>
			<summary type="html"><![CDATA[<p>Hello,</p><p>I just uploaded a binary beta release<br /><a href="http://proxmark3.googlecode.com/files/proxmark3_win_bins_beta.zip">http://proxmark3.googlecode.com/files/p &#133; s_beta.zip</a></p><p>if you guys (well, people with some knowledge, because there are no documentation yet) could give it a try, if possible from a pristine windows (so I know whether or not I forgot some DLLs), that&#039;d be great.</p><p>to flash the proxmark with it, just use:<br />flasher.exe ..\arm\fullimage.elf<br />from the bin directory.</p><p>Let me know how it goes...</p><p>(on a pristine windows computer, you&#039;ll *first* have to install the proxmark driver I included, since it will install the libusb0 DLL. The installation procedure *will* be documented of course...)</p><p>Edit: A bootrom is included. If someone (with JTAG ^^) can test it as well...</p><p>Edit2: I have updated the link to the beta version <img src="http://www.proxmark.org/forum/img/smilies/smile.png" width="15" height="15" alt="smile" /></p>]]></summary>
			<author>
				<name><![CDATA[Cex]]></name>
				<uri>http://www.proxmark.org/forum/user/1232/</uri>
			</author>
			<updated>2010-03-10T07:04:29Z</updated>
			<id>http://www.proxmark.org/forum/topic/506/winter-10-test-release/new/posts/</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Ordered 125K kits from qKits]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/518/ordered-125k-kits-from-qkits/new/posts/"/>
			<summary type="html"><![CDATA[<p>I didnt really feel like running tune 47 times to get a perfect antenna. I ordered two AN0201 and AN0301 types, ill test them out and let you guys know.</p><p><a href="http://store.qkits.com/moreinfo.cfm/AN0201">http://store.qkits.com/moreinfo.cfm/AN0201</a></p><p><a href="http://store.qkits.com/moreinfo.cfm/AN0301">http://store.qkits.com/moreinfo.cfm/AN0301</a></p>]]></summary>
			<author>
				<name><![CDATA[terrizzi]]></name>
				<uri>http://www.proxmark.org/forum/user/1487/</uri>
			</author>
			<updated>2010-03-10T03:49:44Z</updated>
			<id>http://www.proxmark.org/forum/topic/518/ordered-125k-kits-from-qkits/new/posts/</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[ripped antenna from HID reader]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/517/ripped-antenna-from-hid-reader/new/posts/"/>
			<summary type="html"><![CDATA[<p>thought it could just hook it up since HID makes readers, but my vaules are all screwy.</p><p># LF antenna:&nbsp; 6.18 V @&nbsp; &nbsp;125.00 kHz<br /># LF antenna:&nbsp; 6.31 V @&nbsp; &nbsp;134.00 kHz<br /># LF optimal: 40.82 V @&nbsp; &nbsp;203.39 kHz<br /># HF antenna:&nbsp; 0.10 V @&nbsp; &nbsp; 13.56 MHz<br /># Your HF antenna is unusable.</p><p>any ideas,&nbsp; remove some coils?</p>]]></summary>
			<author>
				<name><![CDATA[d18c7db]]></name>
				<uri>http://www.proxmark.org/forum/user/1487/</uri>
			</author>
			<updated>2010-03-10T03:46:34Z</updated>
			<id>http://www.proxmark.org/forum/topic/517/ripped-antenna-from-hid-reader/new/posts/</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[HID iClass.  Anyone have experience?]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/514/hid-iclass-anyone-have-experience/new/posts/"/>
			<summary type="html"><![CDATA[<p>I&#039;m fascinated by the HID iClass cards.&nbsp; The technology seems very MIFARE-like.&nbsp; The only way to deal with them that I&#039;ve found is with Omnikey readers (now HID) and their SyncAPI (Windows/Linux).&nbsp; It&#039;s not very open.</p><p>Has anyone done anything with these cards?&nbsp; I&#039;ve seen a couple dead-end threads regarding iClass on here before, but I&#039;m hoping maybe a few new people might have something to add or a latent interest</p><p>I have a stack of iClass P16K cards with the additional 125Khz Prox chips, so if you&#039;re in the US and want one or two through first-class mail, let me know.&nbsp; If you&#039;re not in the US, maybe we can trade cards.</p><p>Here&#039;s a good overview, &quot;Contactless Developer Guide - 5321-903_A.1.20&quot;:&nbsp; <a href="http://www.hidglobal.com/documents/ok_contactless_developer_guide_an_en.pdf">http://www.hidglobal.com/documents/ok_c &#133; _an_en.pdf</a></p><p>I have links to other docs, but none are as useful as that one.</p>]]></summary>
			<author>
				<name><![CDATA[wrc]]></name>
				<uri>http://www.proxmark.org/forum/user/369/</uri>
			</author>
			<updated>2010-03-10T01:30:25Z</updated>
			<id>http://www.proxmark.org/forum/topic/514/hid-iclass-anyone-have-experience/new/posts/</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[if selfbuild: what's the smallest size possible?]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/513/if-selfbuild-whats-the-smallest-size-possible/new/posts/"/>
			<summary type="html"><![CDATA[<p>hello :-)</p><p>I&#039;m interest in a really really small rfid-reader - so my question is:<br />what&#039;s the smallest size possible if one would build an own?</p><p>i saw these: <a href="http://www.proxmark.org/forum/topic/264/my-portable-proxmark3-setup/">http://www.proxmark.org/forum/topic/264 &#133; rk3-setup/</a><br />they are really nice! but what&#039;s the smallest size possible?</p><p>thanks in advance for your help!<br />oliver</p><p>@marauder <br />thanks - I edited my post :-)</p>]]></summary>
			<author>
				<name><![CDATA[wbahn]]></name>
				<uri>http://www.proxmark.org/forum/user/1489/</uri>
			</author>
			<updated>2010-03-09T03:27:17Z</updated>
			<id>http://www.proxmark.org/forum/topic/513/if-selfbuild-whats-the-smallest-size-possible/new/posts/</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[My set of antennas]]></title>
			<link rel="alternate" href="http://www.proxmark.org/forum/topic/90/my-set-of-antennas/new/posts/"/>
			<summary type="html"><![CDATA[<p>OK I&#039;m getting real excited now, the prox is built and it was high time I tested it, but for that I needed some antennas.</p><p>At first I used a piece of wirewrap &quot;green wire&quot; and rolled a 5 turn aircoil 43mm diameter, then experimentally played around with adding or removing a turn while issuing the tune command to get a voltage reading. It mostly sat around 1.3V except when I let the coil turns lose and unravelled and the coil looked like a deformed spring the voltage jumped to over 10V but that was not really an option for an antenna. I then returned to the 43mm diameter coil with 4 turns and taped the coil with sellotape to keep it together then started deforming it to see what difference that made. It looks like I got lucky as squashing it to an elongated and slighlty rectangular shape moved the voltage to about 16V.</p><p>This is how I ended up with this shape. It used to be straighter but the coil has been through a lot. It&#039;s soldered direct to the test pads as somebody forgot to order the mating hirose connector <img src="http://www.proxmark.org/forum/img/smilies/roll.png" width="15" height="15" alt="roll" /> when buying the parts...</p><p><span class="postimg"><img src="http://farm4.static.flickr.com/3056/3044704721_880f7309cf.jpg" alt="http://farm4.static.flickr.com/3056/3044704721_880f7309cf.jpg" /></span></p><p>The picture below is a typical setup where a RFID snapper card is sandwitched between the proxmark3 antenna and a snapper feeder (card reader, the black thing that looks like a USB flash key)</p><p><span class="postimg"><img src="http://farm4.static.flickr.com/3243/3044733519_0b837bcf97.jpg" alt="http://farm4.static.flickr.com/3243/3044733519_0b837bcf97.jpg" /></span></p><p>While in this close proximity, I issue the hi14asnoop command on the prox, then drive the snapper feeder with some python script for example issuing four consecutive list card commands in my python shell, like so:<br /></p><div class="quotebox"><blockquote><p>&gt;&gt;&gt; b.snapper_send_data(PN5XX_LIST_TAG)<br />sent: 0000FF04FCD44A0100E100<br />recv: 0000FF14ECD54B010104002004086B64BE08578002011000092600<br />&gt;&gt;&gt; b.snapper_send_data(PN5XX_RF_OFF)<br />sent: 0000FF04FCD4320100F900<br />recv: 0000FF02FED533F800<br />&gt;&gt;&gt; b.snapper_send_data(PN5XX_LIST_TAG)<br />sent: 0000FF04FCD44A0100E100<br />recv: 0000FF14ECD54B01010400200408DC78E708578002011000097800<br />&gt;&gt;&gt; b.snapper_send_data(PN5XX_RF_OFF)<br />sent: 0000FF04FCD4320100F900<br />recv: 0000FF02FED533F800<br />&gt;&gt;&gt; b.snapper_send_data(PN5XX_LIST_TAG)<br />sent: 0000FF04FCD44A0100E100<br />recv: 0000FF14ECD54B01010400200408E743D10857800201100009B800<br />&gt;&gt;&gt; b.snapper_send_data(PN5XX_RF_OFF)<br />sent: 0000FF04FCD4320100F900<br />recv: 0000FF02FED533F800<br />&gt;&gt;&gt; b.snapper_send_data(PN5XX_LIST_TAG)<br />sent: 0000FF04FCD44A0100E100<br />recv: 0000FF14ECD54B0101040020040841B32908578002011000099600<br />&gt;&gt;&gt; b.snapper_send_data(PN5XX_RF_OFF)<br />sent: 0000FF04FCD4320100F900<br />recv: 0000FF02FED533F800</p></blockquote></div><p>Then stopping the snoop (press the prox button) and issuing the hi14alist command we can see what the prox snooped. Note that the card&#039;s UID changes every time, so it moves through UIDs 086B64BE, 08DC78E7, 08E743D1, 0841B329 and these UIDs in the snooped prox output match the returned values in the python debug output.<br /></p><div class="quotebox"><blockquote><p>&gt;&gt;&gt;&gt; hi14alist<br />recorded activity:<br /></p><div class="codebox"><pre><code> ETU     :rssi: who bytes
---------+----+----+-----------
 +      0:   0: TAG 04  00    
 +   1304:    :     93  20    
 +     64:   0: TAG 08  6b  64  be  b9    
 +   3471:    :     93  70  08  6b  64  be  b9  55  34    
 +     64:   0: TAG 20  fc  70    
 +   1488:    :     e0  50  bc  a5    
 +     88:   0: TAG 08  57  80  02  01  10  00  09  94  da    
 + 828164:    :     26    
 +   5142:    :     26    
 +     64:   0: TAG 04  00    
 +   1304:    :     93  20    
 +     64:   0: TAG 08  dc  78  e7  4b    
 +   3472:    :     93  70  08  dc  78  e7  4b  ac  f2    
 +     64:   0: TAG 20  fc  70    
 +   1488:    :     e0  50  bc  a5    
 +     88:   0: TAG 08  57  80  02  01  10  00  09  94  da    
 + 612070:    :     26    
 +   5142:    :     26    
 +   1368:    :     93  20    
 +     64:   0: TAG 08  e7  43  d1  7d    
 +   3472:    :     93  70  08  e7  43  d1  7d  84  67    
 +     64:   0: TAG 20  fc  70    
 +   1488:    :     e0  50  bc  a5    
 +     88:   0: TAG 08  57  80  02  01  10  00  09  94  da    
 + 578188:    :     26    
 +   5144:    :     26    
 +     64:   0: TAG 04  00    
 +   1303:    :     93  20    
 +   3536:    :     93  70  08  41  b3  29  d3  ab  fc    
 +     64:   0: TAG 20  fc  70</code></pre></div></blockquote></div><p>Finally for completeness I took Roel&#039;s idea of using a toilet paper roll, cut a slice and wound 150 turns of 0.125mm wire on it. I knew people had success in the past with around 100 turns so I started high and removed turns to get the tuning right. With 150 turns I used to get 45V on 125khz and about 20V on 136khz and as I removed turns these numbers moved closer to each other. There isn&#039;t much point going higher than 40V as the zenners will clip the voltage so I removed enough turns (lost count) until tune reported 29V at 125khz and 30V at 136khz. The picture below shows the final coil, sellotape is holding the coil to the TP roll <img src="http://www.proxmark.org/forum/img/smilies/smile.png" width="15" height="15" alt="smile" /> and in the picture it&#039;s not actually soldered to the board as it&#039;s a little cumbersome to carry that around so I only fit it when needed. Currently I&#039;m not doing any LF work so this coil isn&#039;t needed but it has successfully read some HID tags I have (in raw data mode).</p><p><span class="postimg"><img src="http://farm4.static.flickr.com/3070/3044733465_1a60627648.jpg" alt="http://farm4.static.flickr.com/3070/3044733465_1a60627648.jpg" /></span></p>]]></summary>
			<author>
				<name><![CDATA[d18c7db]]></name>
				<uri>http://www.proxmark.org/forum/user/120/</uri>
			</author>
			<updated>2010-03-08T23:47:35Z</updated>
			<id>http://www.proxmark.org/forum/topic/90/my-set-of-antennas/new/posts/</id>
		</entry>
</feed>
