Skip to content
This repository has been archived by the owner on Apr 15, 2022. It is now read-only.

Configuration Zone Write #38

Open
imuguruza opened this issue Oct 16, 2014 · 9 comments
Open

Configuration Zone Write #38

imuguruza opened this issue Oct 16, 2014 · 9 comments

Comments

@imuguruza
Copy link

Hey there!

I have started using hashlet to configure and use an ATSHA294 device. I was wondering if personalize command allows you to write the Configuration Zone bytes.

Thanks

@jbdatko
Copy link
Member

jbdatko commented Oct 16, 2014

Do you mean AtSHA204? If so, than personalize does set the configuration
zone and otp zone. However, it doesn't let you specify a different
configuration than my defaults.

I've been playing with the idea of a user supplied XML file for the
configuration which would let the user have much more flexibility, but it's
still a work in progress.
On Oct 16, 2014 4:19 AM, "Iñigo Muguruza" [email protected] wrote:

Hey there!

I have started using hashlet to configure and use an ATSHA294 device. I
was wondering if personalize command allows you to write the
Configuration Zone bytes.

Thanks


Reply to this email directly or view it on GitHub
#38.

@imuguruza
Copy link
Author

OK, thanks for the rapid answer! First, I think I'll give a try to your settings. I think it would be great to have a way of configurating the zones. Thanks for this great tool!

@jbdatko
Copy link
Member

jbdatko commented Oct 16, 2014

Just be aware that once you write the configuration zone (or personalize) it can't be undone. This XML feature exists on a branch in libcrypti2c. My ultimate goal for this software, which I should document somewhere, is to use this kernel module, libcrypti2c, and then truly device features in hashlet.

@imuguruza
Copy link
Author

That sounds great! BTW another question if you run ./hashlet personalize , instead of ./hashlet personalize -f keys.txt , where are the keys saved?

@jbdatko
Copy link
Member

jbdatko commented Oct 16, 2014

They go to ~/.hashlet.

On Thu, Oct 16, 2014 at 8:38 AM, Iñigo Muguruza [email protected]
wrote:

That sounds great! BTW another question if you run ./hashlet personalize
, instead of ./hashlet personalize -f keys.txt , where are the keys saved?


Reply to this email directly or view it on GitHub
#38 (comment).

@imuguruza
Copy link
Author

Thanks again! If you don't mind, I have another doubt: I am sending mac command with a challenge that I have created, like this:
sudo hashlet -k 1 - c 3ACEC5DB23F39FF87B88D48D4D365E563AA2A85E929CC1BA1A164EA7B74423B mac

In order to verify later the response using the key 1. I'm not receiving any answer using my own -c, is it possible to do so??

@jbdatko
Copy link
Member

jbdatko commented Oct 17, 2014

Ok, this is probably a problem with my interface. At the moment, you can't send a challenge in directly, it will be SHA256 hashed first. If that's OK with you, than you could do:

echo 3ACEC5DB23F39FF87B88D48D4D365E563AA2A85E929CC1BA1A164EA7B74423B | hashlet mac

But that 3ac... will be SHA256'd first.

@imuguruza
Copy link
Author

ok thanks for your support ;)

@N5066
Copy link

N5066 commented Jan 25, 2021

I have been trying to use ATSHA204.. I have personalized the chip and got the key zone from ~./hashlet. But when I run the command ./hashlet personalize -f keys.txt the error comes failed to import the key file.

Same with the mac command ./hashlet mac --file test.txt...Then it comes Failed to open file..

What could be done in both the cases

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants