Hi Noel, would you upload a compiled hex file for the Attiny85? I would like to try your code

Hi Daniel, 

sure I've uploaded the .hex file here:

https://mega.nz/#!bYhGnaSC!-X49n6WVDzrn4mFcGfjKwPt9VyKq0tybNDqc9qqRFV0

Anyway you can clone the git and "make hex" if you want to make further tests :)

EDIT:

The link is not working anymore as it was deprecated by new features implemented, get the firmware from github instead :)

Paste h lp me

Great work, i have also build a bigger password keeper: https://github.com/seeers/PW-Stick 

Thanks! PW-Stick looks nice too :)

Using KeePas as GUI to import keys is a nice idea for this project too..?

hi @Frank Weissenborn! Keepass only works on windows and it's a little bit convoluted to use, so we decided to make a very simple GUI that could run on any OS: https://github.com/oyzzo/MemTypeTool

What could be a great idea is to be able to import from keepass to MemTypeTool easily and at some point we'll implement that feature as there are some users that already have their credentials on keepass :)

Great job, Miguel and Noel. Starting with DigiSpark and two butons last year, I gave up yesterday when I saw this cool project.

Hello, i received memtype one week ago and now test it. This is an amazing and useful thing!!! But there are some bugs and inaccuracies:

First - memtype can't type symbol "@". May be it don't available for russian keyboard? Symbol "@" very usefull for typing Login where Login is e-mail.

Second - "mingw32" do not work on Windows 10. But it work well on Windows 7. In this way, i builded "mttool" on Windows 7, and then launched "mttool" on Windows 10.

Third - very short description for installation "mingv32". If user are not advanced, then he don't understand, how it works and how to install it. For example from MemTypeGettingStarted.pdf: "4. Add your gcc into windows PATH (example: C:\ProgramFiles\mingww64\x86_645.2.0posixsehrt_v4rev0\mingw64\bin)". It is not simple to make. User must know where windows PATH is.

Fourthly - i don't understand how to make keyboard file by myself. What do i do to correctly compose file?

Fifthly - sorry for my english ))

Hello sergey, thanks for your help ! we appreciate your feedback !

1.- The "@" is supported, the only think is that you currently don't have a russian keyboard layout configured in your Memtype device. In order to check it's working properly you can try to load the English keyboard layout to Memtype, change your OS keyboard to English and test it.

2.-  We didn't tested on a Windows 10 OS, so thanks for your feedback. Maybe we can release the binaries for the different OS.

3.- We are currently migrating mttool to python and a friendly user interface, so hopefully it will be fully supported in Windows and you won't need to build mttool using Mingw.

4.- We have a custom Memtype firmware to generate keyboard layouts doing some bruteforce, I will try to generate the Russian one and publish it to the develop github branch: https://github.com/jim17/memtype/tree/develop/mttool/keyboards

Regards,

Noel & Miguel.

Just received mine today, Thanks!! 

Yeah!! we didn't had brasilian keyboard layout generated at the moment of sending the unit (you have the english one) but now you have it available on mttool/keyboards folder and you can change it.

I'll take a look, Thanks!!

Hello,

I dont know if this is the best adress to ask my question: when I plug the memtype in, nothing happens, nothing if I press the joystick. With the 'dmesg | grep usb' I get:

[  683.492114] usb 5-2: new low-speed USB device number 2 using uhci_hcd
[  683.612146] usb 5-2: device descriptor read/64, error -71
[  683.836169] usb 5-2: device descriptor read/64, error -71
[  684.052166] usb 5-2: new low-speed USB device number 3 using uhci_hcd
[  684.172181] usb 5-2: device descriptor read/64, error -71
[  684.396135] usb 5-2: device descriptor read/64, error -71
[  684.612142] usb 5-2: new low-speed USB device number 4 using uhci_hcd
[  685.020118] usb 5-2: device not accepting address 4, error -71
[  685.132146] usb 5-2: new low-speed USB device number 5 using uhci_hcd
[  685.540091] usb 5-2: device not accepting address 5, error -71

is this meaningful for anyone? Best regards

Hello Look Right ! Try to remove other HID devices from the USB port, insert memtype first and check if this works for you !

Hey just tried on another computer. Found the system sound play like plug and unplug the usb-device when I switch the joystick. A closer look shows a not so good soldered pin on the attiny. Heating um the iron and now the memtype is a keyboard. Now the next steps. 'MemTzpe 3.0.0'

Yeah, hand soldered units and a mistake in the uC footprint made us to have some difficulties on soldering. Hmmm if you are german compile mttool and do:  ./mttool -k keyboards/keyboard_DE.txt to change the keyboard to the german one.

Got mine today as well, messing about with it as we speak. I haven't tried it yet but seems it would work a treat on a laptop. desktop doesn't seem to be to much at home as its finicky to mess with on a wired hub. Other than that its looking pretty awesome.

I'll keep you updated.

I have a quick query:

I am unable to use the mttool on my work PC due to restrictions on installing things. Is there any alternative way to get my details on this little beauty?

The only way to store credentials, change PIN or change keyboard layout is by using mttool. What OS do you use ? The best way can be to store the credentials in your home and bring the device to your work. If you have troubles with mttool you can send us a private message and we can do a skype call or something.

Thanks for the swift reply buddy!

That's no worries, I will certainly be bringing it home to load up with credentials! We have Win7 on most machines at work but the IT dept have them locked down pretty tight so no way of installing the required elements and path info for mttool. The memtype works an absolute treat though, was recognised as a device immediately!

Hey Miguel - Just a quick one

I have received my Memtype unit to put through it's paces. I have only pressed the button a few times, yet already I have found myself thinking "this is ****ing AWESOME".

What a great product!

"Shut up and take my money". How much does it cost?

Hi Sergey,  we're still not selling them, but if you want one for free just take a look to the project log titled "Who wants a free memtype?..." and comment asking for one!

On December 25th we'll send the 15 units to the 15 users who ask for them  ^_^

wanted to make this myself, glad someone already did, this is great!!!!

Yeah, after contributing to mooltipass project. I decided together with my mate to make a cheaper and simple implementation.

There are different implementations of a device like this:
http://hackaday.com/2014/01/21/final-key-a-mooltipass-like-device/

http://hackaday.com/2014/01/01/usbpass-a-mooltipass-like-project/ 

I think our implementation is very simple and effective, though it can be improved anyway.

Hi Miguel, your password manager is brilliant! It is a pity you haven't entered the Square inch Project. If I knew your project before the deadline of the contest I would have adviced you to try to fit the board diagonally or to use an USB connector. 

Hello danjovic, happy to know you like the project!!! Yeah, when the project started #The Square Inch Project wasn't announced yet so... we were focused on making a cheap hardware. I think we can easily reduce the size of the board by changing the 4 way switch to smd and adding a USB type A connector. We are open to do changes on the next hardware release, so do not hesitate to contact us and do some suggestions :).

Hi Miguel, I REALLY liked your project. If you allow me a suggestion that would be to redesign your board so it can fit inside one of those plastic enclosures available from china (http://www.aliexpress.com/item/20-pieces-a-lot-small-plastic-USB-enclosure-40-17-10-mm-1-57-0-67/1623217148.html) . I have bought some of these boxes and If you wish I can share the eagle library that I have created based upon the drawings that the seller sent me.

Hi, just want to say that this is a great project! If you are considering software and/or hardware improvements it would be great to replace the joystick with fingerprint scanner and also add the ability to generate complex passwords from your user app. Congrats again!

Hi Drulex, 

Thank you very much! sure we consider all kind of improvements :)

We considered the fingerprint scanner on the early design stages but finally we discarded it because of some of this issues: http://hackaday.com/2015/11/10/your-unhashable-fingerprints-secure-nothing/ . Also one of the main goals of the project is being very simple and low priced, so we decided to use a classical pin instead. 

The ability to generate complex passwords is a great feature that will be added for sure on the user GUI app.

Hi, is it possible to add pads on the other end of the board for a micro USB OTG connector so this can be used on phones and tablets?

Nice project!

Hi, it could be possible but with the current version you are able to do this with a USB A to USB micro adapter cable (like this one: http://www.amazon.com/eForCity-Micro-USB-Adapter-Cable/dp/B005QX7KYU ). The reason of not having connectors on the board is to minimize BOM costs and make it cheaper. We appreciate your feedback and in the next board revision we wil consider your suggestion and we will try to add micro USB connector directly on the PCB.

Kindly regards,

Miguel.

I love the comparison between the prototype and the current version! How has your luck been with PCB-based USB connectors? Any tips? Gold plating, etc?

PCB USB based connector has been done using a 2mm PCB instead of standard 1.6mm one. As ENIG has excellent corrosion resistance we choose ENIG as PCB surface finish.

The PCB width is 12mm and finally... the best tip I can tell you is to follow the USB norm as much as you can:  

http://www.usb.org/developers/docs/devclass_docs/CCWG_A_Plug_Form_Factor_Guideline_Revision_1.0_.pdf 

Ah, good to know. 2mm PCB.. interesting. Thanks!

You probably should use "hard gold" instead of the usual ENIG to get a more reliable contact.

http://www.omnicircuitboards.com/blog/bid/337154/Understanding-PCB-Manufacturing-Hard-Gold-Plating

Proper USB connectors are $0.10 a piece from China and they are superior than the usual PCB fingers.

Of course, proper USB connectors are the right thing. We wanted to have a small batch of units to finish the firmware on them and beta testing. 

Once software is finished and testing is done we'll make a new batch with all the improvements that we see.

A plastic case is on the way so the pcb will have to be adapted to it a little bit,  having a hole for a keyring is important too for such a small device, a proper USB connector, change from 2mm to standard 1.6mm will reduce a little bit of cost too and maybe adding led if we have some space and can give it some use. 

looks a bit like the Google Authenticator U2F Security compatible USB Keys

Hi dodoutils, you're right it's very similar, but maybe easier as you just store your credentials in it and it types them for you, no need for software to support for any protocol. 

Actually I think they complement each other, as with the U2F keys the sites can simplify passwords to a 4 PIN key without compromising security, but won't it happen similar thing than using usual passwords? how many PINs can people remember? and what happens with software outside a browser that doesn't support U2F? 

Think of ssh for example, VNC, RDP.or any other, on memtype you can even have the full command so it can type it for you, for example:

name: SSH_user@machine

user: ssh user@machine.com -p 22 

hop: '\n'

password: p094jfcqriqueorqmpqoiernlfnfdaWhatEver

submit: '\n'

Now to use it, scroll until you see the name on the terminal prompt, then accept it and everything is typed for you, even ascii SYN characters can be included to make the memtype wait, to be sure it types the password when ssh is actually asking for it and not before.

It's a simple device with a lot of power :)

I never said it's better or worst just it was similar way of working (injecting keyboard strokes).

But question is, if it can store multiple passwords/keyboard sequences, how will the user select the good one ? (I do have some ideas of how to handle this but I suppose the mini joystick instead of simple button is for this purpose).

dodutils, 

hehe I know,  just tried to show the differences :) , but I have to admit I'm not an expert on the U2F devices or protocol.

You are right, the mini joystick is for this purpose, and also for unlocking the device when plugged before using it. 

So for choosing the password that you want it's very easy. Each of them has a name, so whenever you have a prompt where you can type, be it a terminal, the user field of the log in form etc... you can move the tinny joystick up or down, and it'll print previous or next name of password. 

When the name of the password you want is typed, you press the joystick on the direction of the usb connector (inside the pc) and it'll erase what it typed, then type the user, type a tab (or anything else) to jump to the password text edit, type the password and finally type an enter (or anything else) to submit the log in. 

You can see a video here http://www.area0x33.com/blog/?page_id=329

In that video it's also shown the process of entering the pin the first time you plug it into the USB so it can use it to decrypt the passwords.

Tell us your ideas, or even better, grab the code and help us haha :) 

PS: I couldn't reply to your reply, so I hope it's easy to follow if I write it here.

hello, how did you render your boards and how long did it take to render, on what resolution ? thanks!

Hi Mario, we exported the model from Kicad into Blender, then created the materials to look like the actual pcb colors, set a couple of lights and some minor modifications to the joystick model and click to render. I used a resolution of 1920x1080 px, it took less than 5 seconds to render in my laptop :) 

Seems like a good fit for #The Square Inch Project!

Board size is 1.26x0.47 inches so I think we are outside #The Square Inch Project boundaries.