text:
Today marks the final installment in our faith and parenting series with a guest post from one of my very favorite bloggers, and people—Kathy Escobar. Kathy is the co-pastor of The Refuge, an eclectic faith community in north Denver. She is the author of Down We Go: Living Into the Wild Ways of Jesus, which will totally transform the way you think about "church," I guarantee it. Kathy is married to Jose and is the mother of five. What I love most about Kathy's writing is that it is real—representative of a life spent "in the trenches" of loving God and loving people. It consistently inspires me to love and follow Jesus better. I really look up to Kathy because her actions line up so consistently with her words, which is a rare and beautiful thing indeed. Be sure to subscribe to Kathy's blog. (It's a favorite.) You can also follow her on Twitter. Enjoy!
"In your anger, do not sin"
- Ephesians 4:26
When I was a kid, I was taught that anger was bad. It had nothing to do with Christianity because I was not raised in a family of faith; rather, in a home with an alcoholic, there was an underground but extremely strong message that negative emotions should be avoided at all costs.
Happy, thankful, quiet, and easy-going were highly valued but mad, frustrated, hurt, or sad, not so much. That was reserved for the parents.
When I became a Christian and started learning more about Jesus in "church", I discovered that some of the same rules applied. Messy feelings were ones to avoid. They were equated with a lack of faith or an inability to turn it over to God properly in the moment. For me, honestly, it didn't work half bad because I was already a master at stuffing negative feelings and pretending like nothing was wrong.
20 years ago, my husband Jose and I had our first son. Two years after that, a daughter. And two years after that, another son. In a wild twist of events known as "almost the immaculate conception" we had twin sons three and a half years later. My claim to fame was having five children under the age of seven.
And yeah, there was a lot of emotion in the house.
During the early years, however, Jose and I practiced a parenting style consistent with what we were learning in church—negative emotions were "bad" and somehow needed to be avoided or at least taken care of quick. For our kids, this looked like being mad at them for being mad (yes, I get the irony). Things like "Go to your room if you are angry and come out when you're happy again!" "Stop crying now!" and "You need to change your attitude right this minute!" flowed freely from our lips.
We had good intentions. We weren't abusive. We were just following the books that temper tantrums were a sign of faulty parenting and kids needed to learn emotion control.
I know there are all kinds of ways children need their parents to guide, teach, and set limits on what is appropriate and what's not. But looking back, I have learned something very painful about our early parenting years—we sent our children a strong message that we didn't tolerate negative emotions, only positive ones.
Oh how I regret this!
The church is really good at this, too. As a body of believers, it does seem like anger, sadness, and hurt are not tolerated very well. We want people to go to their room when they're angry and come out when they're happy again, to change their attitudes quick, to get on with the business of feeling good as quickly as possible.
Even though we say it's not true, it sends a message to all of us that God loves us more when we're happy and is disappointed with us when we're sad. This message gets all tangled up with our faith.
We forget that Jesus, God in the flesh, embodied a full range of emotions. He cried. He yelled. He lamented. His blood boiled.
He was human.
Part of my shift in faith and parenting has been about embracing the full range of my humanness. Much of how I was operating in our faith was about rejecting parts of me to somehow "please God more."
The scripture reminds us that in our anger, we shouldn't sin. Not that anger is bad.
And what I have learned, and keep learning, is that God wants all of us, all of the time. He doesn't send us away when we are pissed off or turn away from us until we are happy again. Even though I am human and not God, part of my responsibility as a parent is to reflect to my babies my full, deep, wide, and as-unconditional-as-possible love in the midst of their real lives, their real emotions, so that they can feel more secure and free.
But that shift had to happen in me first.
Part of my responsibility as a woman of faith was to begin to accept that God wants all of me—the angry, sad, hurt, frustrated parts of me along with the happy ones, too.
As Jose and I shifted, how we parented our children did, too. We have made many an amends to our older kids, who received the brunt of thinking that any negative emotion was a sin. Thankfully, they have offered their grace (and told us that they had been pretty mad about it, ha!).
We keep learning. We keep stumbling and bumbling and making all kinds of mistakes along the way. But I'm more sure of this than ever for myself and my kids, too—anger's not a sin.
Shareable Permalink
© 2012 All rights reserved.
Copying and republishing this article on other Web sites without written permission is prohibited.


text:
Nation & World
SEC said to weigh shining light on broker role in routing trades
The Securities and Exchange Commission is weighing a requirement that brokers tell investors exactly where their stock trades go to be executed, a proposal that may address complaints that the decisions are sometimes made against the client's best interests.
The proposal could give investors more insight into whether they are getting the best price when they buy and sell large numbers of shares, according to three people familiar with the matter. Brokers entrusted with orders in the U.S. stock market can choose from dozens of exchanges and private venues. Some money managers such as T. Rowe Price Group have told regulators that incentives offered by exchanges for attracting orders can put a broker's financial interest at odds with the customer's.
The SEC faces pressure to overhaul trading after Michael Lewis's "Flash Boys" book made the claim that high-frequency traders hurt other investors by learning which shares investors plan to buy, purchasing them and selling them back at a higher price. The SEC has said it's reviewing every aspect of how stocks are traded, and regulators are trying to identify changes that could be implemented quickly, the people said.
"We've actually started this conversation about what can we do right now," SEC Commissioner Kara Stein said in an interview. "All five commissioners are very focused on these issues and are committed to making sure the market is fair and efficient and promoting capital formation."
There is a lot of "low-hanging fruit" that should be considered, said Stein, who declined to discuss specific measures. Commissioners expect the SEC's staff to present them potential policy options "in the near term," Commissioner Luis A. Aguilar said in an interview.
Judith Burns, an SEC spokeswoman, didn't respond to e-mail and telephone messages seeking comment.
Brokers can face a conflict of interest as they select where to send customer orders. Brokers can either capture a rebate or pay a fee to an exchange depending on the type of order used, while private venues known as dark pools charge lower fees but don't have to disclose how they treat customers.
Requiring brokers to report every step they took to fill a customer's order could help investors defend against the predatory traders described by Lewis, said Andy Brooks, head of U.S. equity trading at Baltimore-based T. Rowe Price. While large investors can demand such reporting, regulators could require "a very detailed and comprehensive template" that would allow investors to compare the brokers they use, he said.
"It's where you went and didn't get an execution that begs the question of why did you go there?" Brooks said in an interview. "Why is a broker sending an order to a venue where you get no execution?"
Greater transparency is one idea being weighed by the SEC's Division of Trading and Markets, the people said. Regulators could decide to publicly encourage more uniform order-routing notices instead of imposing a new requirement on brokers, the people said.
While improved disclosure is helpful, the SEC should experiment with altering the economic incentives that affect how orders are handled, Brooks said. T. Rowe has joined the New York Stock Exchange, Royal Bank of Canada and IEX Group Inc. in lobbying regulators to ban the "maker-taker" system, which pays rebates to large brokers to attract trades.
Brokerages often put their own self-interest in front of their clients' under maker-taker, according to a study by Robert Battalio and Shane Corwin of the University of Notre Dame and Robert Jennings of Indiana University.
"Simply saying to brokers, 'give us more disclosure' " isn't enough, Brooks said. "The effort needs to be more robust than that if we are really going to go after this."

subset: commoncrawl


text:
greeni.info needed a new logo design and created a contest on 99designs.
A winner was selected from 66 designs submitted by 30 freelance designers.
Pizzuti Development needs a logo... we are re-branding ourselves. We do a little bit of everything, but are starting to get more of a green focus, high quality and a bit more residential. We are looking for a very professional, classy logo.
Pizzuti Development
Desired Color Scheme:
Art Deco a plus! No real color scheme. Perhaps some maroon, but not required
Desired Style:
Professional, strong, clear, prestigious
Accepted File Formats:
jpg, pdf, psd, etc
We are looking for a logo for "Pizzuti Development" that is strong, professional, and ideally with a hint of a building in it (not a single family house, but more of a mixed use taller building perhaps). There are a lot of possibilities - it can suggest partnership, working together, green development, community, profitable... anything along those lines.
Would prefer to have multiple formats of the image from the winner. We can discuss what formats you submit.
Find out how a design contest works or learn more about our logo design services.


text:
Technical Support Services
At JMP Technical Support, our mission is to "help our customers make the best use of our software products through effective and responsive support, active advocacy, and a broad and flexible range of self-help resources." In support of this mission, the following services set the expectations for your relationship with JMP Technical Support.
Support Services for Current and Prior Releases of Software
Software Maintenance and Bug Fixes
General Support Services
- Telephone support
- Access to support resources on our JMP Support web site
- E-mail support
Some of the ways in which we can help you successfully use our software are:
- Suggest the appropriate JMP platform, JSL feature, or products for the particular type of analysis or functionality that is requested.
- Answer questions about specific details of platforms, such as discussing available features, options, and limitations.
- Provide references for formulas and statistical techniques that our algorithms use, where possible.
- Provide limited guidance and references to help you interpret the output that is produced by statistical procedures.
- Isolate, document, and find circumventions for reported software defects.
- Work with JMP software development staff to provide safe updates for our software, as we deem appropriate.
- Provide limited and general statistical advice on a case-by-case basis; however, it is your responsibility to determine which type of statistical analysis is appropriate for your needs.
- Address concerns with printed or online documentation by providing additional examples, if necessary, or explanation for concepts that require clarification.
- Provide guidance during JMP software installation.
- Provide limited assistance with programming logic.
- Provide a broad overview of hardware tuning, operating system modifications, JMP performance enhancements, and methods of efficient programming for achieving optimal performance; however, we do not provide benchmarking for specific hardware or operating systems.
- Provide support for the interaction between JMP and any third-party software that ships with JMP.
- For other third-party applications, we are glad to convey any knowledge that we have, but we cannot provide comprehensive support for another vendor's software.
- Due to limited resources and knowledge of any particular customer's data analysis situation, we cannot provide customized consulting services. Nor can we provide customized JMP code, for example, contrasts, custom tests, or JSL. You can visit the JMP Mentoring website to learn more about the consulting services that are offered by JMP. Your Account Representative can also assist you in engaging the appropriate professional services.
Support Services for Current and Prior Releases of Software
JMP provides three levels of support for generally available JMP software applications running on supported operating systems. These levels of support are described in the following table:
Support Levels for JMP® and JMP® Pro Software
|Support Level
|Activity by Technical Support Staff
|Support for Executable Modules and Maintenance Updates
Web Interface
|Investigates all reported problems; Provides circumventions, where possible
|Provided for selected critical problems
Web Interface
|Investigates all reported problems; Provides circumventions, where possible
|Might be provided for selected critical problems. Provides fixes where already available.
Web Interface
Identifies and provides self-help resources and/or previously-documented, known circumventions.**
(In addition, your SAS account representative can identify options for you to migrate to a SAS product or release at a higher support level, if desirable.)
|Provides fixes where already available
*Phone support available for annually licensed JMP® and JMP® Pro Software. Support for single user licensed JMP® Software is primarily through e-mail and web interface. Phone support may be offered at the discretion of JMP Technical Support.
**Note: After-hours support for Level C-supported software is limited to searching the Technical Support database for known, readily-identifiable potential circumventions to previously-encountered similar problems.
The support levels for annually licensed JMP and JMP Pro software releases are indicated in the following table:
Support Levels for Annually Licensed JMP® and JMP® Pro Software Releases
|JMP® Software Release
|Level A
|Level B
|Level C
|Generally available March 2018. For information, see the JMP® Software web page.
Generally available September 2016. For information, see the JMP® Software Updates web page.
Reduction to Level B support occurred in March 2018.
|12.x and earlier
|Reduction to Level C support for JMP 12.x occurred in March 2018. All previous releases in Level C support.
|Non-GA* products developed on obsolete platforms
*Generally available
The support levels for single user licensed JMP software releases are indicated in the following table:
Support Levels for Single User Licensed JMP® Software Releases
|JMP® Software Release
|Level A
|Level B
|Level C
|Generally available March 2018. For information, see the JMP® Software web page.
Generally available September 2016. For information, see the JMP® Software Updates web page.
Reduction to Level B support occurred in March 2018.
|Earlier than 13.x*
|Support services are expired.
*Due to various operating system updates, activation is only guaranteed for the current (14.x) and prior (13.x) release installed on supported operating systems.
JMP Student Edition installation support is provided by the publisher of the textbook.
Software Maintenance and Bug Fixes
JMP provides maintenance through software updates. The availability of updates is announced on the Support Downloads webpage and via e-mail by subscribing to our JMP Newswire mailing list.
While we attempt to provide updates for serious problems, there might be cases where it is impractical or impossible to generate a fix, due to compatibility issues or the potential for introduction of unwanted side effects.
Problem and Product Change Notifications
JMP documents Alert Priority issues, as well as problems that are not of alert status, in the form of JMP Notes. You can search for Alert Priority issues in our Knowledge Base.
Contact Technical Support
- Report a Problem
- firstname.lastname@example.com


text:
|2000 meetup
Aim of this project is to collect all physical access methods used these days, and analyze possibilities of reading, copying and emulating their tokens.
As a result, this document should provide practical guide for working with access tokens.
The most versatile tool for card reading and emulation is Proxmark3. There are two repositories containing code of x86 client, FPGA and ARM firmware:
The best revision for OS code is rev 838 from old SVN repo. All the stuff that I checked that should work works.
The latest versions of new repo cause always bootloader to be somehow bricked and requires JTAG to reflash old bootloader (even if fullimage is flashed - bootloader + OS + FPGA image). Instructions for unbricking can be found at the end of ARM debugging page.
There is also a library available for PC/SC readers that supports many kinds of cards, but you need specific reader for each separate card - https://github.com/islog/liblogicalaccess/wiki
There are new versions of Proxmark, which are more compact, see the comparison table in the links at the bottom of the page
PN532 based readers:
v2.0 branch with new stuff and rewrite
Suppose, that you have unknown token in your hand, and you don't know anything about access tokens. Idiot's guide goes here:
1. Is it contact or contactless? Contact: goto 2, Contactless: goto 100.
2. Does it have only 2 contacts or more? If two, goto 4, if more, goto 10.
4. It is probably dalas ibutton, using 1-wire protocol
10. It is probably some type of contact smartcard. Can you recognize the access interface? If it is usb, (XX picture) goto 15. If it looks like smart card (XXX picture) goto 20.
15. Deskey? XXX
20. Smartcard, XXX
100. Contactless token. If you see "HID" written somewhere on the token, you may try to go directly to 150. Otherwise go to 101.
101. You need to start reading token. Try HF (high frequency) RFID reader and run isotype or lsnfc on the token. Is it recognized? If yes, goto 120. If no, It is probably LF (low frequency) card. Go to 140.
120. High frequency RFID card. (XXX link) So, now determine type of card. In output of isotype or lsnfc you should see some identification string. This is hard to describe in algorithmic way, so use your intelligence and go to 125 or XXX
125. Mifare. In output of isotype or lsnfc you should see some identification string. If you see exact type, go to 127, 128 o 129. If not you can try readmifare1k. If readmifare1k fails (no login failed or unknown key messages, but completely failed to read other sectors), it is probable Mifare Ultralight. UltraLight "cards" tend to be quite small, often flexible. Goto 127. If you can read other sectors, or get login failed messages, it is Mifare Classic or Desfire. Try cracking it with mfoc. XXX link If you succeed, it is Classic, goto 128. Otherwise, it is probably Desfire, goto 129.
127. Mifare UltraLight. See XXX
128. Mifare Classic. Can have 1K or 4K capacity. See XXX
129. Mifare Desfire. Can have 1K or 4K capacity. See XXX
140. Low frequency RFID card. (XXX picture or link) You need to start reading token. Try LF (high frequency) RFID reader and run (on proxmark)
lf search
Is it recognized? If no, goto 200.
150. EM Microelectronic
200. You are in trouble, the token was not recognized. Try walking whole tree one more time, maybe you made some mistake. Alternatively, you can try to look for all pictures in this document, and identify tag visually. Otherwise, it may be token not known to authors of this guide, or not available at the time of writing. You are dead, sorry.
Mifare cards can have various forms. Here are some examples: Token that can be caried on keys, plain card, and isic card.
Very basic device, only UID transmitter. Get id:
~> lsnfc device = ACS ACR38U-CCID 00 00 / ACR122U102 - PN532 v1.4 (0x07) UID=042cad51962280 * NXP MIFARE UltraLight 1 tag(s) on device.
Get id: Id is stored in first sector, not encrypted (Answer to Reset contains UID, reading Block 00 should not be necessary to get UID only). For example touchatag can be used for quick read of ID.
lsnfc: UID=1ca8xxxx Several possible matches: * NXP MIFARE Classic 4k * NXP MIFARE Plus 4k
Full read: Use MFOC form nfc-tool to decrypt all encrypted sectors, then whole card can be read, for example by
mfoc -P 500 -O dump.file ./readmifare -r 0
from RFIdiot or
./readmifare -r 0
dumps the card after cracking all keys as well.
MFOC employs the "nested attack" and requires that at least one of the keys is a default key (i.e. requires one known key). Cracking the first key can be done via Proxmark (may not work if the card is new and has PRNG fixed):
hf mf mifare
After the first key is cracked, Proxmark also has an implementation of nested attack (A0A1A2A3A4A5 is the known key, the "1" stands for 1K card, "0" means the key is for sector 0):
hf mf nested 1 0 A A0A1A2A3A4A5
Scripting the attack is possible via Lua script, see HOWTO part 1 and part 2.
Clone: There is problem with cloning first sector. All other sectors can be cloned, once decrypted.
No completly rewritable cards available on the market now afaik. You can get 1K and 4K mifare classic rewritable cards on many eshops.
These Mifare Classic cards have a special HW modification that allows writing block 0 and read/write without knowing A|B key. Writing the first block with UID (01020304 here in sample):
hf mf csetblk 0 01020304040804000910111213141516
First four bytes of sector 0 are the UID.
Important: offset 0x04 is BCC, which is XOR of four previous UID bytes. If you set wrong BCC, you may render the card unselectable (=brick it). Especially if you use first byte of UID 0x88, which is magic number for "Cascading Tag". It is not possible to emulate more than 4-byte UID - the card does not support SELECT cascading level 2 (command 0x95).
Offset 0x5 contains SAK, two bytes at 0x06 denote ATQA (you might fool readers that card is of different type by changing SAK). In the above example, SAK 0x8 stands for Mifare Classic, ATQA 0x0004 means that anticollision is supported by the card (mind the reversed byte order).
Reading and writing chinse magic mifare can be done in "unlocked" mode with libfnc's utility nfc-mfclassic:
nfc-mfclassic R A magic.mfd #read whole card without specifying key nfc-mfclassic W A magic.mfd #write whole card without specifying key, including rewrite of sector 0
Unbricking Chinese Magic Mifare Classic:
If you set the wrong BCC for UID and can't read the card anymore, you can use some backdoor commands to change sector 0 using Proxmark:
hf 14a raw -a -p -b 7 40 hf 14a raw -p 43 hf 14a raw -p -c a0 00 hf 14a raw -p -c de ad be ef 22 08 04 00 46 59 25 58 49 10 23 02
Alternatively, libfnc has nfc-mfsetuid utility that can set UID of the magic card or can revert bad BCC (may not always work). If stuck, put together a working normal Mifare card and a bricked magic Mifare card, then run nfc-mfsetuid (anticollision will work with first card, but the bricked card will "hear" the change sector commands).
Proxmark currently implements "chinese backdoor check" as extra functionality (tested on version 2.3.0 from April 2016). It's implemented via 0x40 and 0x43 backdoor commands:
proxmark3> hf 14a reader UID : 34 79 5f ad ATQA : 00 04 SAK : 88 [2] TYPE : Infineon MIFARE CLASSIC 1K proprietary non iso14443-4 card found, RATS not supported Answers to chinese magic backdoor commands: YES
Block 0 is writable through normal Mifare Classic commands, i.e. there is not special "unlocked" read/write like in "magic Mifare 1k" version.
Writing block 0 with Proxmark, UID 01020304, using key A being FFFFFFFFFFFF:
hf mf wrbl 0 a FFFFFFFFFFFF 01020304040000000000000000000000
Again, watch out to have correct BCC and avoid Cascading Tag (0x88) as first byte of UID, or you may make the card unselectable (i.e. brick it).
hf mf sim 123456AB
123456AB is card id in this example.
Currently, proxmark have an issue, so you may need to set mode first:
hf mf eset 0 123456AB112233445566778899001122
to tell proxmark to use 8-byte ID. The longe number here is the firs sector of card. (containing ID, btw)
with emulation of whole card.
Many of proxmark3 revisions are buggy when it comes to simulating, known good revision is for example old SVN rev 839.
Multiple versions available
In order to find out you have Desfire, check SAK in anticollision. Then use get version command to see which Desfire version it is.
Has "applications" and several file types, but much more limited than Javacard (read, write, increase, decrease, add record, …, see specs below). Some features:
Command specifications (non-NDAed), with detailed formats for command data request and response formats: https://www.jadaktech.com/skyetekfiles/docs/m2/desfire.pdf
Short MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC. Contains command list, memory organization, file types, etc.
Desfire Access Tool - old Qt4 application for accessing and managing Desfire cards. Still works as of Nov 2018, though expect bugs. Uses libfreefare, which in turn uses libnfc and PN53x readers.
Has native and wrapped ISO 7816 command modes: https://ridrix.wordpress.com/tag/desfire-commands/
Full read: No working crpyto attack so far, unencrypted sectors can be read, also you can try to look for default keys.
Clone: probably require full read
Emulate: probably require full read
Relay: see Relay attack; EV2 spec says it has relay attack protection, but no details.
EV1 compared to old Ultralight has added 32-bit password for read/write access, ECC signature (static over UID, so copyable), OTP.
Ultralight C has 3DES authentication on top of Ultralight features.
NTAG2 is succesor to NTAG1, serves as NDEF Forum Type 2 tag. Has ECC signature, read counter, 7 byte UID, SLEEP mode (enable/disable card).
Proxmark3 can simulate some of the features of Ultralight EV1/C, though the ECC signature seems missing (read works). There is iceman's fork which seems to be able to simulate EV1.
Ultralight EV1 and NTAG2/1 can be copied onto Magic NTAG21x with proxmark.
IceSql sells "magic" cards to simulate NTAG2/NTAG1, Ultralight EV1 and others.
There is a special Lua script for proxmark to program them.
Information about the cards from proxmark (hf mfu i):
proxmark3> hf mfu i --- Tag Information --------- ------------------------------------------------------------- TYPE : MIFARE Ultralight (MF0ICU1) <magic> UID : 11 22 33 55 66 77 88 UID[0] : 11, Emosyn-EM Microelectronics USA BCC0 : 44, crc should be 88 BCC1 : FF, crc should be CC Internal : FF, not default Lock : ff ff - 1111111111111111 OneTimePad : ff ff ff ff - 11111111111111111111111111111111 proxmark3> hf mfu i --- Tag Information --------- ------------------------------------------------------------- TYPE : MIFARE Ultralight C (MF0ULC) <magic> UID : 00 00 00 00 00 00 00 UID[0] : 00, no tag-info available BCC0 : 00, crc should be 88 BCC1 : 00, Ok Internal : 00, not default Lock : 00 00 - 0000000000000000 OneTimePad : 00 00 00 00 - 00000000000000000000000000000000 --- UL-C Configuration Higher Lockbits [40/0x28] : 00 00 00 00 - 0000000000000000 Counter [41/0x29] : 00 00 00 00 - 0000000000000000 Auth0 [42/0x2A] : 00 00 00 00 default Auth1 [43/0x2B] : 00 00 00 00 read and write access restricted deskey1 [44/0x2C] : 00 00 00 00 [] deskey1 [45/0x2D] : 00 00 00 00 [] deskey2 [46/0x2E] : 00 00 00 00 [] deskey2 [47/0x2F] : 00 00 00 00 [] 3des key : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
This shop sells lot of different changeable UID cards and keyfobs, 4-byte and 7-byte, including UID changeable Desfire/
The "magic Desfire" is far from real Desfire, e.g.
In short, waste of money.
Setting UID on magic Desfire with Proxmark:
hf 14a raw -s -c 02 00 ab 00 00 07 UID
There are some other types of mifare cards, but now widely deployed, at least no in .cz and .sk:
see http://en.wikipedia.org/wiki/Mifare for more info.
All MIFARE cards are prone to relay attack (cz: přepojovací útok). It will be interresting to design a low-cost relaying device. Google 'mifare relay attack' for more…
NXP claims the the upcoming DESFire EV2 will have countermeasures against relay attack, but there is no available documentation as of now.
You need two PN532 devices to use with libnfc and use
nfc-relay-picc. There is an issue if you use forwarding over TCP/IP as described in the manual - it doesn't work, see patch.
You need a third reader if you want to test it (not necessarily PN532). Two devices relay and the third will be your "original reader"
If the third device is Proxmark, you can send APDUs like this (an example how to read NDEF 4 Forum tag) :
hf 14a raw -p -b 7 -a 26 hf 14a raw -p 93 20 hf 14a raw -p -c 93 70 88 04 3a 14 a2 hf 14a raw -p 95 20 hf 14a raw -p -c 95 70 82 cc 22 80 ec hf 14a raw -p -c e0 50 hf 14a raw -p -c 02 00 a4 04 00 07 d2 76 00 00 85 01 01 hf 14a raw -p -c 03 00 a4 00 0c 02 e1 04 hf 14a raw -p -c 02 00 b0 00 00 00
The lines with '93 20' and '95 20' commands contain two halves of Desfire 7-byte UID, 0x88 is the cascading tag. An example with 4-byte UID (happens usually when relaying via nfc-relay-picc) :
hf 14a raw -p -b 7 -a 26 hf 14a raw -p 93 20 hf 14a raw -p -c 93 70 08 3A 14 82 A4 hf 14a raw -p -c e0 50 hf 14a raw -p -c 02 00 a4 04 00 07 d2 76 00 00 85 01 01 hf 14a raw -p -c 03 00 a4 00 0c 02 e1 04 hf 14a raw -p -c 02 00 b0 00 00 00
These are vicinity cards on 13.56 MHz that are commonly found on ski lifts. In theory ISO15693 is designed to work up to 1.5 m distance.
Proxmark can read them and so can some android phones.
They contain UID and 64 bytes of data. Reading with proxmark can be done with:
hf 15 dumpmemory
Latest proxmark 2.3.0 has some basic ISO 15693 simulation functionality, but it's not working properly yet.
AFAIK there are no "Chinese backdoored clones" that would allow changing of UID.
Emulation in general: http://www.t4f.org/en/projects/open-rfid-tag/55 this looks like a very nice generic emulator for LF, some hw guru could look into assembling it? lukash willing to help :)
proxmark - determine LF card type: New: You can use command
lf search
Manual way http://code.google.com/p/proxmark3/wiki/TagOps (outdated, bud principles are still same) in short:
proxmark> lf read proxmark> data samples 2000 proxmark> data plot XXX
Usage around: Quite common building access system
Get id/Read:
Put tag onto the antenna, following code will read HID tags in a loop:
proxmark3> lf hid fskdemod
proxmark3> lf hid sim 01020304
proxmark3> lf hid clone
Cloning requires writable T55xx card.
Proxmark has a standalone mode that will read and then emulate HID Prox card.
Usage around: several parking lots in Prague, some building access systems
Get id/Read:
proxmark> lf em4x em410xwatch
The em410xwatch command may not always correctly guess the clock speed on some cards. You might have to specify clock speed as last parameter of 'em410xread' command (may take several tries). Here is an example for a 134 kHz card (note the 'h' after 'lf read')
proxmark3> lf read h proxmark3> data samples 40000 proxmark3> lf em4x em410xread 32
Emulation with Proxmark works great Emulator like this http://www.t4f.org/en/projects/open-rfid-tag/57 in progress (lukash working on it)
EDIT: site is down right now, downloaded data available at http://kyberia.cz/~niekt0/openrfid/ and http://pain.backstep.net/lukash/openrfidtag/
XXX This hw works http://www.dealextreme.com/p/125khz-rfid-card-copier-duplicator-with-writable-rfid-card-and-keychain-standalone-operation-17230 XXX cloning/writing with proxmark?
Cloning to writable T55xx should work.
Get id/Read:
proxmark data samples 1000 proxmark> lf indalademod
Usage around: building access system
This information pertains to model Paradox C704. Full decoding in proxmark is implemented, in the latest git version. The modulation is Fc/8/10 FSK, thus raw data transmitted by the tag can be read with:
proxmark3> lf read proxmark3> data samples 40000 loaded 40000 samples proxmark3> data plot proxmark3> lf paradox demod Paradox TAG ID: 000328176 (Full ID: 0ca05dadf) - FC: 50 - Card: 33142 - Checksum: b7 - RAW: 0f555555a5995566a699a6aa
Latest proxmark code has clone Paradox to T5577 command. Iceman's fork has emulation.
pm3 --> lf paradox sim 50 33142 Simulating Paradox - Facility Code: 50, CardNumber: 33142
The T55x7 card can be configured to emulate many of the 125 kHz tags. Proxmark forum gives general configuration and also some specific configurations for common cards.
HID cards have explicit command in Proxmark client:
lf hid clone 2006ca4b3b
Similarly, there are builtin commands to clone EM410x, Indala cards, for example:
lf indalaclone 50920439d lf em4x em410xwrite 1a007940fd 1 64
Wiegand is:
Magnetic cards can be relatively easily readed and modified. Typicall card contains 2 or 3 track, each with few dozens of characters. More detailed information can be found on Wikipedia
We made a HIGH POWER MagneticCard emulator based on MAgnetic card sp00fer . We used Brmduino for generating the signal so the coil is powered only by 5V (the laptop is just the power source for brmduino). Source code download. (magnetic_card_emulator.pde)
Another solution is to use professional reader/writer. At brmlab, we have available MSR605 reader/writer supporting 3 tracks, working under Linux.
userland driver and documentation available here
Reading values from the card:
$ python msr.py -r -d /dev/ttyUSB0 1=None 2=;1234567890? 3=None
Writing values to the card:
$ python msr.py -w -d /dev/ttyUSB0 -t 23 --write "1234" "5678"
Datasheet here: http://www.maxim-ic.com/datasheet/index.mvp/id/2829
Get id (~= read): It's very easy to read this tag with Arduino, you need OneWire library to make it even easier, downloadable here: http://www.pjrc.com/teensy/td_libs_OneWire.html
Schematics: http://tushev.org/images/stories/arduino/scheme4ibutton.png (forget the display, code has been modified for Serial only!)
Code for Arduino:
#include <OneWire.h> OneWire ds(12); byte addr[8]; String keyStatus=""; void setup(void) { Serial.begin(115200); } void loop(void) { Serial.println("Reading now.."); getKeyCode(); if(keyStatus=="ok"){ for(int j = 0; j < sizeof(addr); j++) { Serial.print(addr[j], HEX); if (j<sizeof(addr)-1) { Serial.print(":"); } } Serial.println(""); } else if (keyStatus!="") { Serial.print(keyStatus);} delay(1000); } void getKeyCode(){ byte present = 0; byte data[12]; keyStatus=""; if ( !ds.search(addr)) { ds.reset_search(); return; } if ( OneWire::crc8( addr, 7) != addr[7]) { keyStatus="CRC invalid"; return; } if ( addr[0] != 0x01) { keyStatus="not DS1990A"; return; } keyStatus="ok"; ds.reset(); }
Example output:
Reading now.. Reading now.. 1:AA:BB:CC:DD:EE:FF:2F Reading now..
0x1 - 1 byte - Tag identifier
0xAA - 0xFF - 6 bytes - UID itself
0x2F - 1 byte - CRC8 over previous 7 bytes
nice emulation for ID-only iButtons: http://www.reteam.org/board/showthread.php?t=1332
Writing/cloning: http://www.youtube.com/watch?v=KBX_BcFEcAI XXX
smart card emulator project …
What wikipedia tell us about ISO/IEC 7816
Electronic stethoscope - http://siliconchip.com.au/cms/A_112547/article.html
Proof of concept for printing FAB keys: http://kyberia.cz/~niekt0/fap-fap
TODO: OpenScad program to be released under gnu-gpl, input: long/short, profile number (int), key combination (from 00000 to 99999)
ala http://eclecti.cc/hardware/physical-keygen-duplicating-house-keys-on-a-3d-printer
TODO: key combination extraction from photography, ala http://vision.ucsd.edu/~blaxton/sneakey.html


text:
Lifehacker Android apps pack
We recently put together our list of the best Android apps, but college students need a different type of mobile toolkit. To that end, we've gathered up the best Android apps to track your schedule, assignments, and more.
You have a ton of options for different to-do apps, but we like a few that stand above the rest. Any.DO has a ton of extra features so you can make it work how you want, Google Keep keeps things simple, while Wunderlist is packed with great features and works across a ton of different devices.
Evernote is an excellent resource for students to capture everything they have going on in class. If you need a little inspiration for how to use Evernote, Shep McAllister's guest post on the Evernote blog outlines a lot of ways you can use Evernote in school, including taking snapshots of notes, blackboards, organizing research, and more.
We mention Dropbox in our annual Lifehacker Packs, but it's worth noting again for students. Not only is Dropbox a handy place to store all your files, it can also be a lifesaver when you realize you forgot to bring in an assignment. Simply pop into Dropbox, and email the link directly to your professor from any computer.
Let's face it, sometimes you're not going to pay attention in class. In fact, you'll probably fall asleep at least once. For those days an audio recorder can be a lifesaver. On Android we like Tape a Talk Voice Recorder. It supports FTP, Dropbox and attachments.
Studious is a to-do manager and calendar built specifically for a student. It's packed with all the features you'd expect from a to-do manager, but it also comes with a notes feature, and more importantly, ringer automation so the app automatically turns your phone to silent when you're in class. If you're looking for a more traditional to-do manager, we recommend Wunderlist.
Unless you want to give yourself a workout every time you walk to class, you'll want to get as many of your books digitally as you can. Between the Kindle app and the Play Books app, you should be able to get everything you need easily.
Internet and Communication
Chrome is a fantastic browser for students because it syncs all your settings, history, and bookmarks across platforms. That means if you forget your computer one day and need to do some research on your phone, you'll be able to start right where you left off. Dolphin's also a great browser that has a ton of extra features that make reading on your device a little nicer.
Hangouts does pretty much everything you need from an IM and video client. You can chat with friends, do video chat with your family, and even organize bigger group chats with fellow students.
The Extended Pack
Unless you're actually getting your major in mathematics, you probably don't need an expensive graphing calculator. To fill in for Math 101, this free Android app should do everything you need.
Keeping track of your limited finances in college is tough, but Mint makes the whole process easier. It also helps you create and stick with a budget. We know it's probably not the most exciting thing on this list, but it's better to know how little is in your account whenever possible.
Love them or hate them, flashcards are a great way to memorize information. GFlash+ is an app that not only allows you to make your own, but you can also search through thousands that have already been created for classes, or collaboratively make a set of flashcards with your fellow students with Google Docs. It's incredibly simple, but if you're lucky enough to be in a class that already has cards made, gFlash+ will make your life a lot easier.
Pushbullet started as a way to send links between your devices, but now it's a do-everything bridge between your devices. It even added a complete SMS client, so you can read and reply to text messages from your computer, with your professors being none the wiser that you're texting during class.
Let's face it: you're in college, you're short on cash, and you're hungry. Yelp is one of the best ways to quickly search your surroundings and find a cheap place to eat or a quiet place to grab a drink.
Going out for cheap drinks and cheap food during happy hour is a college tradition. If you need some help finding new places to go, Happy Hour Finder will do the trick well enough. It's not exactly the most up-to-date listings, but it is nationwide and seems to do a pretty good job of at least nailing the right times. If you go to college in a large enough city, it's also worth looking to see if you can find an app dedicated to your city.
Source: lifehacker.com
ReadIt Pro
Mobile Application (BraydenJames)
You might also like:
Mobile Application (BraydenJames)


text:
A race in open country along the 'Grande Randonnée' paths crossing though the Mont-Blanc, Beaufort, Tarentaise and Aosta valley countryside.
A mountainous event, including numerous sections at altitude (>2,500m), in weather conditions which can be very difficult (night, wind, cold, rain or snow), requiring a very good level of fitness, the appropriate equipment and a real capacity for personal autonomy.
The two Savoie and the Aosta valleys are some of the provinces that once made up the Savoie State. Line up to discover these 3 regions which are united around Mont-Blanc, and borrow the paths where history and the mountains meet.
First of all you will experience the very special ambiance of the start of the race from the centre of Courmayeur. Passing by "Maison Vieille" at the col Checrouit (1st refreshment point), you will go up along the UTMB® path to the refuge Elisabetta. Then you turn upwards towards the Col Chavannes (2603m) which is next to the col de la Seigne. Even if you are a regular runner of the UTMB®, this long ascent of the Valley Veny in the early morning light will certainly help you discover a new perspective of it, in all its magnificence. Open you eyes wide because it is a view of rare beauty! Then you will experience, throughout the long descent on gentle slopes, the splendid wilderness of the Vallon de Chavannes' pastures before joining the Vallon de la Doire de Verney which you will go up to reach the Lac de Verney before reaching the Col du petit Saint-Bernard (2188m, refreshment post). You then leave the Aosta valley and will begin your trip in the Haute Tarentaise with a long descent along the Roman way which, since the year 2 AD, has linked Rome to Lyon by passing through the Alps. Profit from the party which will be awaiting you when you cross through Séez and then Bourg Saint-Maurice (refreshment point), because it is followed by a serious ascent of almost 2000m! You will pass the forts of Truc and la Patte which were built at the end of the XIX° century, when Franco/Italian relations were turning sour, to protect the valley from eventual attack by Italian troops. You then reach the wonderful area of the 5 lakes. Just after the Col de la Forclaz (2354m), you pass along the lac Esola, and then you climb up over the Passeur de Pralognan (2567m). A descent, very steep at first, then gentler, leads you to the volunteers from Beaufort at the Cormet de Roselend (refreshment post). You then have to go up to the Col de la Sauce, then by taking the amazing passage du Curéto the hamlet of la Gitte (have a quick look, just next to the security point, at the chapelle de Notre-Dame des Neiges, dating from 1639) then go up towards the Col de Gitte to 2322m from where one can see the extraordinary view of the Mont-Blanc, Aiguilles Rouges, Fiz and Aravis chains of mountains... before taking, a little known path, across the "Grande Pierrière" to the Col du Joly where you will experience the welcome from the team from Hauteluce (refreshment point). This wild walk along the most beautiful paths of the Tarentaise, Beaufort and Mont-Blanc country continues with a descent into Les Contamines (refreshment point), before going up to the col du Tricot passing the chalets du Truc and Miage. You cross the nose of the Bionnassay glacier by footbridge and go up to Bellevue before plunging down into Les Houches (refreshment point). All that remains is to reach the centre of Chamonix for a triumphal and well deserved finish!
Distance : around 119 km
Positive height gain : around 7,250m
Time limit : 33:00
Refreshments : the principal of the event is to be semi-self-sufficient. Seven posts will be supplied with drinks and/or food to be consumed in situ.
Main difficulties : Arête du Mont-Favre (2435m), Col Chavannes (2603m), Col du Petit Saint-Bernard (2,188m), Passeur de Pralognan (2,567m), Col de la Gitte (2,322m), Col du Tricot (2,120m)
The start will take place at the centre of Courmayeur, on the Brocherel Place, Wednesday 29th August 2018 at 6am.
This race will be limited to 1,600 competitors.


text:
GREEN BAY, Wis., Oct. 28 (UPI) -- Aaron Rodgers threw two touchdown passes Sunday and the Green Bay Packers logged their third straight win, 24-15 over Jacksonville.
Rodgers finished 22-of-35 for 186 yards while Donald Driver and Randall Cobb each caught a touchdown pass as resurgent Green Bay (5-3) claimed its fourth victory in five games overall.
Alex Green led the Packers' ground game, carrying the ball 22 times for 54 yards.
The Jaguars (1-6) dropped their fourth straight as Blaine Gabbert was held to 27-of-49 passing for 303 yards and a touchdown while playing through a shoulder injury.
Rashad Jennings picked up 59 yards on 17 carries for Jacksonville.