Daži prasīja kā noskaidrot vai telefonam ir NFC un kur to var ieslēgt.
Var meklēt telefona specifikācijā, bet var arī ieskatīties tīkla uzstādījumu sadaļā.
Uzskatāmībai ieliku ekrānšāviņus:
Ja iespēja pie uzstādījumiem nav atrodama, ierīcei visdrīzāk nav NFC. 
Citreiz gribas noskaidrot cik braucieni palikuši dzeltenajā e-talonā, nemeklējot tuvāko e-talona automātu. Protams, negribas arī aplauzties sabiedriskajā, pērkot dārgo biļeti (šogad vēl 70 sant.?).
Uzrakstīju Android aplikāciju, kura ļauj apskatīt dzeltenās kartes saturu un mēģina atšifrēt biļetes veidu un braucienu skaitu.
Dotajā brīdī aplikācija ir īpaši primitīva, negarantēju, ka atšifrējumi ir korekti visos gadījumos (nebija man tik daudz kartes ar kurām testēt). Ar laiku pieslīpēšu un pievienošu kādu jauku fīču (piem., laika biļetes atšifrēšanu?) vai vizuālo noformējumu.
Veidošanā noderēja (daļēji kļūdainā) informācija no Jāņa pierakstiem un citu cilvēku padomiem.
Interesentiem – aplikācija novelkama Android Marketā.
Lai aplikācija darbotos, nepieciešams Android >2.3.3 tālrunis ar NFC.
Updeits: Updeitoju .apk, lai saprot derīgo biļešu skaitu jaunajiem e-taloniem. Šķiet, ka Rīgas Satiksme tos bieži maina.
Pieļauju, ka būtu labi savākt daudzus e-talona dumpus vai tikt pie tiem, kuri Jānim bija pieejami pirms pāris gadiem, lai izveidotu maksimāli labu atpazīšanu.
Update 2: Uploadoju aplikāciju uz Android Market, lai būtu vieglāk updeitoties. Darbojas arī vecais links.
Izlasīju Krizdabz emocionālo rakstu, kurā viņš pēc “WINDOWS BUILD” apmeklēšanas sūkstās, kāpēc viņam neiet pie sirds Android OS un iekārtas, uz kurām tas uzstādīts.
Ikdienā lietoju Nexus S, uz kura darbojas Android 2.3.4. Neskatoties uz to, ka ir manītas dažādas nepilnības, es pilnīgi noteikti neesmu saskāries ar tik daudzām Android ekosistēmas problēmām, tāpēc uzrakstīšu savus komentārus.
Apskatīšu un pakomentēšu viņa raksta apakštēmas.
It is interesting that my “torrent auto uploader” has become one of the best (or maybe even the best) and most accessible tool in this field.
And it is interesting that lately more and more people want to use my uploader for downloading from sites that are already using it.
Let’s see if it gets more interesting after I test and add support for downloading from FTP servers.
P.S. Yes, I know, some of you were waiting long time for this.
In one of my previous blog posts I mentioned hiding your server behind proxy to protect yourself from long downtime.
Since some of you wanted more information, I figured I should write about it. This will still only scratch the surface of it and you should do some additional reading if you want to get a better understanding of how these things work and what they can be used for.
Let’s begin!
Šodien kārtējo reizi saņēmu zvanu no kompānijas IZZI, saruna aptuveni šāda:
I: Labdien, vai Jānis?
J: Klausos!
I: Šeit zvana Ilze no kompānijas IZZI...<neļauju pabeigt teikumu>
J: Es ceru, ka nemēģināsiet atkal piedāvāt savus pakalpojumus.
I: Mēs jums piedāvājam kļūt par IZZI Premium...<un atkal neļauju pabeigt>
J: Es jums piedāvāju manu telefona numuru izņemt no savas spamlistes... patiesībā es jums to lūdzu izdarīt!
I: Kāpēc?
J: Jo es nevēlos saņemt citus sliktus IZZI pakalpojumus.
I: Labi, piedāvāsim jūsu kaimiņiem, pal... <nolieku klausuli>
Mēneša laikā šis bija kāds ceturtais vai piektais zvans no IZZI.
Ja viņi tikpat neatlaidīgi darbotos, lai uzlabotu sava interneta kvalitāti, IZZI būtu labākais ISP Latvijā. 
Kamēr rūteris down, vajadzēja no windows izprintēt dokumentu un padot netu uz laptopiem.
Pirmais failure sanāca, jo windows 7 nesuportē pārāk veco tīkla karti, kuru atradu Jāņa veco datoru lūžņu kaudzē. Es saprotu, ja nepazīst jaunas iekārtas, bet vecās!?
Otrais fail – ar printēšanu. Kamēr CUPS uz Linux lieliski saprot, ka printerī tinte vairāk kā vajag, uz windows, ar desmito ofisu, tas pirms printēšanas pogas nospiešanas pagaida ~ minūti iefrīzojis, tad pasaka, ka tinte beigusies, tomēr sāk drukāt, izdrukā pusi no lapas (turklāt nerodas iespaids, ka nebūtu tinte), apstājas, un ar to visi prieki beidzas. Interesanti vai uz W7 tie tintes trūkuma paziņojumi regulāri parādās pirms laika un vai tas atkarīgs no ražotāja? Varbūt tur kāda krāpšana aiz tā visa, lai civlēki biežāk jaunus kartridžus pirktu?
Un Linux rūtera piedzīvināšana iebremzē, jo otra tīkla karte daļēji atdeva galus. Un pats rūteri arī nav no tiem spīdošākajiem – pavecs TOSHIBA laptops (pentium 4), ar pa pusei nosvilušu video karti, bez ekrāna un BIOS konfigurējamu tikai no Windows XP (tātad nekonfigurējamu). Tiesa, ja uz tā aparāta sanāk piedzīvināt Linux, strādā tīri jauki. Jau dažus gadus lietoju (sākumā Debian, tad Ubuntu Server un ja izdosies, tad turpmāk Arch). Šobrīd lielākā problēma ir ar CF karti IDE diska vietā (jo kādi 3 IDE diski jau atmira), kurā var iebūtoties tikai no CD, jo USB memory stiku boot nesuportē un no CF kartes (aiz IDE to CF adaptera) iebūtoties nemāk. Varbūt laiks meklēt jaunu kasti? Kaut vai tādu, kura māk no flash atmiņas startēties, lai nebūtu jātur kompaktdisks ar GRUB.
Jā, šādās dienās var novērtēt to cik strauji attīstās tehnoloģijas, un nopriecāties par to, ka aizvien retāk nākas saskarties ar šādiem gadījumiem.
Knowing that internet is not all cute and cuddly and that the line between real and virtual sometimes gets kind of blurry, it is important to think a bit before acting, and possibly save you from getting in trouble.
What I meant by “blurry line between real world and virtual one” is that what happens on internet not always stays on internet. If you read news, it is possible that you have noticed articles about police raids on some sort of network based service providers or their servers, governments asking communication service providers (e-mail, IM, others) to hand them private conversations to help in their investigations, or blocking network access and disturbing donation receiving.
While some “shady” network services were started by paranoid people (in a good sense), who think a lot about their security and anonymity, most others don’t realise how important it could be or just don’t care.
Who should care about this? People who call themselves media, political organisations, internet pirates and people who want to stay anonymous.
Here are some quick tips that could be of some use to you:
Since most of the visitors reach your service through domain name, make sure you use domain name(s) that can’t be easily taken away by your country’s government or get you in problems for using them.
Make sure your files are hosted on servers outside of your government’s reach. In case of piracy, countries that don’t care about piracy or anti-piracy are best suited for this (Canda?).
Also make sure that your country doesn’t have official international investigation agreements with the hoster country.
It would not hurt if the data center would be located deep under ground in some fortress that was previously used as a bomb shelter. Probably most countries have those.
If there is something physical that can’t be encrypted and hidden, don’t keep it at home. Hell, don’t keep it at home even if it is encrypted!
In certain cases, make sure that you can’t be extradited to other country. If necessary, move to new home. If you are dealing with some really powerful people, this could be really tricky (Wikileaks case).
Nothing scares away users more than leaving them wondering what is going one. Make sure you have some social messaging account that is hosted on safe grounds, that all your users know about. In case of problems inform them using those tools.
Keep your data encrypted and don’t give the key to anyone. Also recommend this to your clients.
Since computers are getting more powerful all the time, complaining about CPU power needed to use data encryption is silly.
Also make sure that your encryption key can’t be accessed using cold boot attack. If needed, glue the RAM to the motherboard! Seriously, this could help.
Use connection encryption between your server and clients.
If you don’t trust your government and certificates given out by some companies, make your own and make sure your clients recognize it.
Good old saying “Real men don’t make backups” is meant more like a joke and should not be taken seriously. Do make backups! Keep them far away from your main server, hide them, encrypt them, but make sure you have them (and try not to loose the key).
Having not only your data but also server configuration backed up could help reduce downtime in case of server change.
Hiding your super powerful server behind cheap, anonymous VPS could help you stay unidentified by less powerful people. There are some hosting companies that provide cheap VPS hosting and allow you to enter fake owner data for small fee. If you can then hide your payment account and fake your domain name owner data, you could stay anonymous as long as your proxy hoster doesn’t give out your real server address. In this case even if your proxy is taken down, reopening is just a matter of getting new proxy server in some other part of the world.
There is always some risk that your server could be taken and data searched for leads.
If possible, leave no log files about your clients and administrators or make up some fake ones.
Use proxy! Tor Project should help you hide yourself.
Since Skype was bought by Micro$oft, it can’t provide anonymous communication anymore. As an extra, they probably added the famous “generic crash library” to it. OK, to be serious, most of the public IM and e-mail networks should be considered unsafe. Set up your own private encrypted IM network and don’t log stuff.
But if we keep talking about Micro$soft, try to stay away from it. You never know what is hiding in their lame binaries and “security through obscurity” (M$’s motto?) is stupid. Open source software is the future, go with it, explore how “security by design” works.
It is hard to write universal hiding guide for every project and each case is different. If you think it is necessary, get someone to give you good advices.
Remember that it takes only one small mistake to fail completely.
Most importantly keep your conscience clean and be good! If you are doing it for the right reasons (and have good PR campaign), people will support you (shouldn’t they?).
P.S. Feel free to add more tips or point to some errors in the comment section. I’l try to keep this post up to date.
I didn’t want to write longer title so let me explain what I meant with it. Instead of “unsafe”, I should probably use “relatively not as safe as smaller and not so popular Bittorrent trackers”.
But let me start from the beginning.
Some time ago I read this article in TorrentFreak about using Bittorrent as a DDoS tool. Of course then I tested it on my own server to see how it works. Because I didn’t send too many fake announcements my box didn’t “go down” but I sure got a lot of incoming traffic. That PDF that can be found in the previously mentioned article states that their box received Bittorrent handshake requests long after they sent the last announcement. They suggest that those connections are made by some anti piracy organisations to sniff what kind of torrents you have loaded in your Bittorrent client.
Since I specified my webserver’s port 80 as a target, I can see all the Bittorrent handshakes in my Nginx access log.
And even after about 6 months I still get them a lot.
This clearly shows that public Bittorrent network is full of crap. Probably in most countries you won’t be too worried about this but you never know what and when they intend to do with this data.
So what can you do?
If you have blocked incoming connections, no need to worry (but this also makes it harder to download and share stuff). In other cases using random ports each time you start your Bittorrent client could help a bit.
Also using not so popular and private Bittorrent trackers should be safer. Another nice thing about them is that they usually have some high speed servers dedicated for seeding torrents resulting in faster download speeds for you.
Tiem, kuri tankā:
Malacis!
Redzēs vai sanāks, bet ideja laba.
Update: Un šķiet, ka sanāks, jo… lasīt te.