Also posted as a story comment on Slashdot.
An LG spokesperson clarified, that the court situation does not affect supplies of Qualcomm chips to LG. Source.
Therefore, the 'concerns about rollout' is speculation (IMO) by an analyst whose assertion got a signal boost from Reuters.
Any possible delay — which is just a rumour — could be attributed to a thorough testing of hardware and software.
Judge Lucy Koh ruled, that Qualcomm has had onerous prices for use of its patents, and that Qualcomm should 'sign new patent licensing deals without Qualcomm's offending terms,' which is what LG wants.
But Qualcomm apparently wants the antitrust decision to not be enforced and to be set aside in licensing negotiations with LG (and possibly others) as one of the delay tactics in legal proceedings so as to demand the fulfilment of Qualcomm's previous and onerous terms on pricing. If LG caves, the ruling by the honourable Judge Koh will be pointless.
This would simply mean more expensive phones.
For LG, that would mean releasing kit with a bigger sticker price, which isn't exactly enticing to consumers, and, of course, LG either.
LG would still have a good position, because the U.S. Federal Trade Commission, who originated the case, also asked the court to deny Qualcomm's request for stay.
The pricing and antitrust issues notwithstanding, the LG mobile business has a decent opening with the ongoing brouhahae surrounding Huawei.
It should be noted, that like Samsung, LG is a Very Large(tm) company in South Korea, with 222,000 employees in 2012, and $147.2 billion in revenue plus a $2.4 billion profit for the year 2018.
It is strange, though, that LG terminated their previous patent licensing deal with Qualcomm instead of renegotiating that deal, or negotiating a new deal while the previous deal was still in effect. Currently, both have an interim deal.
There was a similar case with Apple suing Qualcomm over prices, and plenty of people whined, as if Apple and its consumers weren't rich enough to pay up.
Apple and Qualcomm settled, with 'Apple paying $4.5 billion to settle a case and obtain a license for 5G modem technology.' That settlement will stand, even if Qualcomm's request to stay is denied. Very suddenly, Intel announced that it was shutting down its modem business and the relevant research and development, while a rumour surfaced, that Apple wants to buy just that, and Intel is looking for a buyer (story at URL above).
The Apple and Intel story is interesting, but at this point, I do not know if regulators in the European Union will approve the sale, as the modem business is in Germany, and is based on Infineon, which was purchased by Intel. Apple would certainly be poised to have and develop competing modems, as some of the former Infineon employees are already at Apple.
Regulators should watch the movements closely. See, when Apple purchased AuthenTec, a company with the best fingerprint sensor in the market, then the other phone makers could no longer use it. As much was implied by Mr. Dennis Woodside, then-the-CEO of Motorola, who told The Telegraph, that Motorola and the others were left with the 'second-best supplier in the market, who weren't there yet.'
Saturday, June 15, 2019
Saturday, February 16, 2019
Looking back on an advert: Samsung Galaxy Mini II vs Nokia Asha 311
Five years ago (as of February 2019), this photo comparing Samsung Galaxy Mini II and Nokia Asha 311 caught my eye. On the surface, both had comparable specifications to what I wanted, but I'd preferred a Nokia phone simply on the strength of the Nokia brand. What follows, is a comment that I recently posted.
When my primary phone was a flip-phone with just a 2 Mpix camera, then I dreamed of getting that Nokia Asha 311 one day, as it had all of the new features that I thought I could want.
A young relative got that one for his birthday, but lost it soon after under a tree in the countryside (it was found a year later in a bit disheveled state, but it still worked).
In late 2013, I got the Galaxy Mini II as a hand-me-down (used). It's got a better camera than the flip phone (3.15 Mpix), and comes with Android 2.3 Gingerbread, ended up with a longer useable lifetime and with more functionality and apps than I would have had with Asha 311.
For instance, I could install Firefox on Android, and that extended the Mini II's useable lifetime for quite a bit longer than it would with just the default Android browser.
If equipped with NoScript, and configured properly, then Firefox is the browser that can prevent the planned obsolescence of many old Androids.
When several apps stopped working on Android 2.3, I could use their mobile web equivalents in Firefox. Even Skype for Web, which needed specific work to function in Firefox on Gingerbread.
Five years after I got the Mini II, by Christmas 2018, I finally got an upgrade, which is a hand-me-down from an elder relative, who got a substantial phone upgrade themselves, and had no need for the old phone.
The 'newer' phone has almost the same specs, but a 5 Mpix camera, and had Android 4.0.3 Ice Cream Sandwich (ICS), which I'd upgraded it to Android 4.1.2 Jelly Bean through the phone's official connectivity software.
I would have stayed with Android 4.0.3, but I needed the upgrade, as 4.1 Jelly Bean is the earliest version supported by the Smart ID app, without which I wouldn't be able to do online banking on my phone, should the need arise. I don't have the SmartID app yet, but now I have the possibility to eventually find out, if I can run it there.
When my primary phone was a flip-phone with just a 2 Mpix camera, then I dreamed of getting that Nokia Asha 311 one day, as it had all of the new features that I thought I could want.
A young relative got that one for his birthday, but lost it soon after under a tree in the countryside (it was found a year later in a bit disheveled state, but it still worked).
In late 2013, I got the Galaxy Mini II as a hand-me-down (used). It's got a better camera than the flip phone (3.15 Mpix), and comes with Android 2.3 Gingerbread, ended up with a longer useable lifetime and with more functionality and apps than I would have had with Asha 311.
For instance, I could install Firefox on Android, and that extended the Mini II's useable lifetime for quite a bit longer than it would with just the default Android browser.
If equipped with NoScript, and configured properly, then Firefox is the browser that can prevent the planned obsolescence of many old Androids.
When several apps stopped working on Android 2.3, I could use their mobile web equivalents in Firefox. Even Skype for Web, which needed specific work to function in Firefox on Gingerbread.
Five years after I got the Mini II, by Christmas 2018, I finally got an upgrade, which is a hand-me-down from an elder relative, who got a substantial phone upgrade themselves, and had no need for the old phone.
The 'newer' phone has almost the same specs, but a 5 Mpix camera, and had Android 4.0.3 Ice Cream Sandwich (ICS), which I'd upgraded it to Android 4.1.2 Jelly Bean through the phone's official connectivity software.
I would have stayed with Android 4.0.3, but I needed the upgrade, as 4.1 Jelly Bean is the earliest version supported by the Smart ID app, without which I wouldn't be able to do online banking on my phone, should the need arise. I don't have the SmartID app yet, but now I have the possibility to eventually find out, if I can run it there.
Sunday, February 3, 2019
The origins of 'free Wi-Fi everywhere in Estonia'
This was initially written as a reply, so I've expanded this post with more links. This blogpost is meant to point out wifi.ee as one of the places where it all began.
There's a very insightful thread on reddit about the history of the notion of "free Wi-Fi everywhere in Estonia".
As of 2019, free Wi-Fi in Estonia hasn't gone anywhere, and continues to thrive in many places.
But there were free Wi-Fi hotspots ten and even fifteen years ago, too, and even earlier (802.11b). Generally, the newer 802.11g Wi-Fi standard was first adopted in January 2003, which is almost exactly 16 years ago.
The earliest Internet Archive snapshot of wifi.ee, a website that began mapping public Wi-fi hotspots in Estonia, dates back to 7 march 2002. That's 17 years ago; there were only 7 public hotspots in all of Estonia on 14 March 2002.
Just look at this archived photo made in Tartu Lõunakeskus. That's seventeen years ago!
The Reddit thread is insightful, as several posts point out, that this kind of connectivity was almost unheard of elsewhere, and was like science fiction to people visiting the country.
The current 2019 map has 1225 free/public Wi-Fi networks.
There's a very insightful thread on reddit about the history of the notion of "free Wi-Fi everywhere in Estonia".
As of 2019, free Wi-Fi in Estonia hasn't gone anywhere, and continues to thrive in many places.
But there were free Wi-Fi hotspots ten and even fifteen years ago, too, and even earlier (802.11b). Generally, the newer 802.11g Wi-Fi standard was first adopted in January 2003, which is almost exactly 16 years ago.
The earliest Internet Archive snapshot of wifi.ee, a website that began mapping public Wi-fi hotspots in Estonia, dates back to 7 march 2002. That's 17 years ago; there were only 7 public hotspots in all of Estonia on 14 March 2002.
Just look at this archived photo made in Tartu Lõunakeskus. That's seventeen years ago!
The Reddit thread is insightful, as several posts point out, that this kind of connectivity was almost unheard of elsewhere, and was like science fiction to people visiting the country.
The current 2019 map has 1225 free/public Wi-Fi networks.
Tuesday, December 25, 2018
The official YouTube app no longer works on Android Gingerbread (2018). Remedies.
This is meant to be a reply in a thread at Google Product Forums. I've posted it here first. The official YouTube app stopped functioning in Android 2.3 in late-late October 2018.
Just an update: Logging out in the non-functional YouTube app in Gingerbread made it impossible to log in again. The error message (roughly translated) reads:
On the other hand, I got yet another opportunity to check out a device with Android 4.0 Ice Cream Sandwich (ICS), and the YouTube app does work there, provided, that some of the software components are kept up-to-date.
The example ICS setup with a working YouTube app has the following component versions:
* Android 4.0.3
* Google Play Store 8.0.76.R-all [0] [PR] 163912422
* Google Play Services 14.5.74 (000302-219897028)
* YouTube app version 11.01.70
People with Android 2.3 Gingerbread and a non-functioning YouTube app can do the following:
• Continue using the mobile YouTube site in the default browser that would launch videos in an external player.
The reason I suggest using the default browser ("Internet"), is, that while older versions of Mozilla Firefox and derivatives can run on Android 2.3, and while they do also support HTML5 video, then Firefox is resource-intensive on low-end devices. Such devices do not have enough RAM memory, and/or cannot run anything greater than Gingerbread. With these, video playback might work in Firefox, but not satisfactorily, or might not work at all.
• Or they can upgrade to at least Android 4.0 — either by updating the software, if a device manufacturer and/or mobile operator has an update on offer; or by obtaining a device installed with at least ICS.
This I left out of the reply:
It appears, that this time, the YouTube app not working on Android Gingerbread is final, hence 'no longer' in the title of this post. I don't think it will be fixed, and it would be a miracle, if it were. If someone has Android 2.3 with a working YouTube app, while most others don't have that, then the most likely explanation could be expired certificates in the app and Gingerbread itself, and updated certificates on the YouTube end. Such is life.
In this case, I follow a personal policy of not suggesting alternative apps. Therefore, if the official app doesn't work, use the browser.
Just an update: Logging out in the non-functional YouTube app in Gingerbread made it impossible to log in again. The error message (roughly translated) reads:
A problem occurred during launch. Check the network connection and system time.It seems to me, that Error 410 probably appeared when an account is set as logged-in in the YouTube app, though I cannot claim this for certain. The error cited above now appears when attempting to log in, or when trying to play videos.
On the other hand, I got yet another opportunity to check out a device with Android 4.0 Ice Cream Sandwich (ICS), and the YouTube app does work there, provided, that some of the software components are kept up-to-date.
The example ICS setup with a working YouTube app has the following component versions:
* Android 4.0.3
* Google Play Store 8.0.76.R-all [0] [PR] 163912422
* Google Play Services 14.5.74 (000302-219897028)
* YouTube app version 11.01.70
People with Android 2.3 Gingerbread and a non-functioning YouTube app can do the following:
• Continue using the mobile YouTube site in the default browser that would launch videos in an external player.
The reason I suggest using the default browser ("Internet"), is, that while older versions of Mozilla Firefox and derivatives can run on Android 2.3, and while they do also support HTML5 video, then Firefox is resource-intensive on low-end devices. Such devices do not have enough RAM memory, and/or cannot run anything greater than Gingerbread. With these, video playback might work in Firefox, but not satisfactorily, or might not work at all.
• Or they can upgrade to at least Android 4.0 — either by updating the software, if a device manufacturer and/or mobile operator has an update on offer; or by obtaining a device installed with at least ICS.
This I left out of the reply:
It appears, that this time, the YouTube app not working on Android Gingerbread is final, hence 'no longer' in the title of this post. I don't think it will be fixed, and it would be a miracle, if it were. If someone has Android 2.3 with a working YouTube app, while most others don't have that, then the most likely explanation could be expired certificates in the app and Gingerbread itself, and updated certificates on the YouTube end. Such is life.
In this case, I follow a personal policy of not suggesting alternative apps. Therefore, if the official app doesn't work, use the browser.
Saturday, December 15, 2018
Primer: How to avoid a wall of text in comments, and in life
This was meant to be a reply to someone who submitted a wall of text in a comment in YouTube. I'd decided against posting that reply, because the person used a nickname instead of a real name and photo, and that person's comments showed early signs of aggressive behavior (calling a person who complained about lack of punctuation and grammar a "budddy"), if he felt, that my reply would escalate the debate.
Your comment text anywhere — including in social media — would be much easier to read and quite a bit more useful, if you were to use punctuation, paragraph breaks, and correct spelling. Then people will take all the written comments and the comment writer more seriously. And not just comments, but really most everything you write.
Instead of offering a long search link that tells more about you than you'd volunteer, it would be more convenient to either submit a truncated search link, like this:
https://www.google.com/search?q=q6600+for+sale
or say, that: 'if people would search for
q6600 for sale
— they'd find results starting at the ballpark of U.S. $7.95 to $10.88.'
Currently, your search link tells everyone in plaintext [the commenter posted a very long search results URL], that you have an HTC phone with Android, and it could be inferred from "android-home", that you might have possibly made a voice-based search (via speech-to-text). It could then be further deduced, that your entire comment was dictated through your phone.
It may be tedious, but you will reveal less information about yourself, when you copy the search result, and shorten it in your browser's address bar, leaving only the
Your comment text anywhere — including in social media — would be much easier to read and quite a bit more useful, if you were to use punctuation, paragraph breaks, and correct spelling. Then people will take all the written comments and the comment writer more seriously. And not just comments, but really most everything you write.
Instead of offering a long search link that tells more about you than you'd volunteer, it would be more convenient to either submit a truncated search link, like this:
https://www.google.com/search?q=q6600+for+sale
or say, that: 'if people would search for
q6600 for sale
— they'd find results starting at the ballpark of U.S. $7.95 to $10.88.'
Currently, your search link tells everyone in plaintext [the commenter posted a very long search results URL], that you have an HTC phone with Android, and it could be inferred from "android-home", that you might have possibly made a voice-based search (via speech-to-text). It could then be further deduced, that your entire comment was dictated through your phone.
It may be tedious, but you will reveal less information about yourself, when you copy the search result, and shorten it in your browser's address bar, leaving only the
/search?q=searchable+thing part after the domain.
Thursday, November 1, 2018
The two forks of Pale Moon for Windows XP
This was posted as a reply at Google Product Forums. This concerned video stopping every 25 minutes on YouTube during HTML5 playback.
I got to test a long-form YouTube video with New Moon 27.6.0a1, and the 25-minute video lag still happens.
At that point (when video stops during playback), I pause, or move the video progress indicator back a little to keep the video going.
I treat the breaks every 25 minutes like the breaks during tv ads
I'm most likely stuck with that videolag stoppage, as I've chosen to keep a fork of Pale Moon Moon 27.6.x, because that branch still supports cookie prompting.
There are two forks of Pale Moon for Windows XP:
* New Moon — available at RT's Free Soft blog at Blogspot.
This browser is not my main driver.
* MyPal. Of the two, MyPal 27.6.2 is a somewhat later release than New Moon 27.6.0a1, so I just might consider replacing New Moon with MyPal.
The positive side is, that unlike Firefox, the forks support H.264 video, which should play most videos on YouTube, and clips on twitter.
To switch on support for WebM/VP9 in New Moon 27.6.0a1, one can uncheck "Use MSE asynchronously", and then check "Enable MSE for WebM video" in the Content section of the Options window.
Newer versions of forks most likely have H.264 support as built-in. Older versions of New Moon require extracting the lav extension file(s) from lav.7z into the folder where the browser is installed in Program Files.
It should be noted, that New Moon and MyPal 27.6.x are older versions, but support a few bits more functionality than a comparable version of Firefox (38.8).
I got to test a long-form YouTube video with New Moon 27.6.0a1, and the 25-minute video lag still happens.
At that point (when video stops during playback), I pause, or move the video progress indicator back a little to keep the video going.
I treat the breaks every 25 minutes like the breaks during tv ads
I'm most likely stuck with that video
There are two forks of Pale Moon for Windows XP:
* New Moon — available at RT's Free Soft blog at Blogspot.
This browser is not my main driver.
* MyPal. Of the two, MyPal 27.6.2 is a somewhat later release than New Moon 27.6.0a1, so I just might consider replacing New Moon with MyPal.
The positive side is, that unlike Firefox, the forks support H.264 video, which should play most videos on YouTube, and clips on twitter.
To switch on support for WebM/VP9 in New Moon 27.6.0a1, one can uncheck "Use MSE asynchronously", and then check "Enable MSE for WebM video" in the Content section of the Options window.
Newer versions of forks most likely have H.264 support as built-in. Older versions of New Moon require extracting the lav extension file(s) from lav.7z into the folder where the browser is installed in Program Files.
It should be noted, that New Moon and MyPal 27.6.x are older versions, but support a few bits more functionality than a comparable version of Firefox (38.8).
Monday, October 22, 2018
Eesti ID-kaart ja Knoppix 7.2
Algupäraselt on blogipostitus kirjutatud käigupealt, mistõttu on seesinane küljendamata kujul. Artikkel on mõeldud kõigile, kes oskavad natuke terminali (käsurida) kasutada.
Kindlasti võis midagi kahe silma vahele jääda, kuid suures osas peaks andmed paika pidama.
Estobuntu plaadile keevitamine ei aidanud, sest selle versioon on samuti aegunud ja uut pole välja lastud. Kui seda reklaamitakse kui eestikeelset distrot, mis "toetab ID-kaarti", peaks see pidevalt kaasaegne olema.
Estobuntu põhineb Lubuntu 14.04-l, mis lasti välja 17.04.2014. Estobuntu DVD-tõmmise juures on kuupäev 02.05.2014.
Lisaks: Estobuntu 14.04 DVD Live-versiooni puhul sai värskeima Firefoxi installimisel miskipärast mäluruum otsa, sest minu masinal on vaid 1 Gb RAM-mälu (muutmälu). Kõvakettale ma tõmmise sisu ei salvestanud, sest kõvakettal on teine opsüsteem; seetõttu läks käiku vaid Live-variant, mille puhul kasutatakse ramdisk-i.
Seevastu Knoppix Live-CD puhul mälu kohese otsasaamise kartust gigabaidise RAM-mahuga pole. Etteruttavalt võib juba nentida, et Knoppixist oli kasu.
29.0 21.0.
Osad tarkvarapaketid on Knoppixil juba olemas; siin artiklis tõin välja vaid puuduvad või uuendatavad.
Näiteks mida vanem Linuxi-distributsooni versioon, seda rohkem uuemaid ja puuduvaid pakette ja nende sõltuvusi (omakorda pakette) peab peale panema.
Sellest johtuvalt osutus valik vähemas osas Ubuntu 14.04 LTS Trusty Tahr (edaspidi Trusty) ja suuremas osas Debian 8 Jessie (25–26.04.2015) distrodele kompileeritud ühilduvatele pakettidele — põhimõttel, et mida vanemale distrole tehtud ühilduv pakett, seda vähem tuleks selle jaoks sõltuvusi tõmmata.
Kompromissi ei saanud teha konkreetselt ID-kaarti puudutavate pakettidega, nagu opensc jt., mis tähendas, et osa vajaliku versiooniga pakette on Debian 10 Buster-nimelisest kõige värskemast enam-vähem stabiilsest distro-versioonist.
Kui mõni muu ühilduv pakett oli vanemas distros olemas, langes valik selle kasuks.
dpkg siis vastavalt annab teada, kas install õnnestus või mitte ja mis lisapaketti täiendavalt vaja on.
Ennetavalt on võimalik kasutada dpkg-query võimalust, et teada saada, millise paketi versioon installitud on:
Esmapilgul vajalike teekide paketid (info sain siit) —
Tsitaat:
Kui käsurea käsklus
Kuna ma aga tahtsin vaid kellaaega ja failinime, tuli käskluse väljund lasta toru abil ("piibu", i.k. pipe) läbi awk-i:
Võib kasutada ka lihtsamat varianti
— See koostab pakettide lihtsa nimekirja ajalises järjekorras vanimast salvestatust kõige uuemani suunaga ülevalt alla.
Vajadus on seega järgmiste pakettide järele (tabel on veel pooleli) —
opensc-pkcs11 paketil on omad sõltuvused:
* libglib2.0 >= 2.39.4 (Knoppix 7.2-s: libglib2.0-0:i386 2.36.3-1)
* libssl1.1 >= 1.1.0 (Knoppix: Puudub; on libssl1.0.0:i386 1.0.1e-2)
libglib2.0-0_2.40.2-0ubuntu1.1_i386.deb ubuntu trusty
4. Mingi hetk tekkis tahtmine tõmmata peale ka uusim opensc:
opensc (0.19.0-1) debian buster
Sõltuvused:
* libglib2.0-0 >= 2.16.0 — esmapilgul polnud vaja, aga siis opensclite1 (üleval) tahtis ikkagi uuemat.
* libreadline7 >= 6.0 (Knoppix: Puudub; kõige hiljutisem on libreadline6:i386 6.2+dfsg-0.1)
** libtinfo5_6.0+20161126-1+deb9u2_i386.deb debian stretch (i386)
* libssl1.1 >= 1.1.0 (Knoppix: puudub, on libssl1.0.0 1.0.1e-2)
libssl1.1_1.1.0f-3+deb9u2_i386.deb — ilmselt stretch; i386
* opensc-pkcs11 = 0.19.0-1 (Knoppix: puudub täielikult)
opensc-pkcs11_0.19.0-1_i386.deb debian buster i386
Edasi tuli installida opensc pakett:
opensc (0.19.0-1) buster i386 (Knoppix: Puudub täielikult)
Edasi: pcsd
pcscd (1.8.24-1) buster i386 (Knoppix: puudub täielikult)
aga sellel on õige mitu sõltuvust:
* libccid >= 1.4.1~ (Knoppix 7.2-s libccid justkui eksisteerib, aga uuendust sellele on ikka vaja)
libccid (1.4.18-1) jessie i386
* libsystemd0 (215-17+deb8u7) jessie i386 (Puudub täielikult)
Sõltuvused:
** libgcrypt20 (>= 1.6.1) 1.6.3-2+deb8u5 jessie dl (Knoppix: Antud versioon puudub, on libgcrypt11 1.5.0-5 )
Sõltuvused:
*** libgpg-error0 (>= 1.14), Knoppix 7.2-s 1.10-3.1 1.17.3
debian jessie i386
* libudev1 (>= 183) (Knoppixis puudub) 215-17+deb8u7 jessie i386
Kokku on pakette umbes kuue megabaidi jagu.
*Minu panka sai Iceweasel 21.0 lehitsejaga sisse logitud;
*Eraldi tõmmatud Firefox ei toeta PIN2 koodi mehhanismi üldse. Iceweaseliga oli ka võimatu PIN2 koodi kasutada, kuid peale esmaselt vajalike pakettide installimist esitatakse päring selle järele, kui katsetasin ülekande tegemist. Iceweaseli uuendamisel versioonile 38.0 erilist abi kahjuks ei olnud, kuid asja tasub veel uurida.
Mozilla "FTP"-sait sidaldaaab (jutumärkides, sest see on http) Mozilla Firefoxi ja teiste programmide kõiki versioonie. Postituse tegemise kuupäeval on uusima eestikeelse Firefoxi asukoht see:
Kui Firefoxi pakitud fail on näiteks Iceweasel lehitsejaga salvestatud, avada faili kataloog pcmanfm failihalduris.
* firefox-62.0.3.tar.bz2 peale saab ühe korra peale klikkida, ja siis avaneb see XArchiver programmis.
* Alternatiiv on failile parema osutinupuga vajutada ja validaExtract To... käsk, mis aktiveerib XArchiver programmi lahtipakkimise mooduli. Selles tuleb valida Firefoxi installatsiooni asukoht. Kuna tegemist on Knoppixiga, võib Firefoxi rahumeeli pakkida lahti /home/knoppix kataloogi. Seal jääb see omakorda
Firefoxi saab edasi käivitada terminalist:
Minna Firefoxi lahtipakitud kataloogi
*
*
Kuna Firefoxi uuendatakse tihti, siis Mozilla "ftp"
(Synapticut või muud paketihaldurit ära kasuta, sest see tõmbab kaasa liiga suure arvu muid pakette).
Alles siis tuleb Firefoxi laadida onepin moodul.
Firefoxi ingliskeelses variandis:
https://addons.mozilla.org/firefox/addon/open-eid/
Edasi tuleb Firefox sulgeda, alles siis kaart sisestada kaardilugejasse, ning lehitseja siis taaskäivitada.
Kui kaarti parasjagu enam vaja pole, siis sulgeda terve Firefox ja kaart lugejast välja võtta. Kui kaart on kaardilugejas ja lugeja indikaator vilgub, siis kaarti välja võtta ei maksa. (Kui lamp jääb pikaks ajaks vilkuma, siis tasuks proovida süsteemi kinnipanekut või restarti.)
Vähemalt eesti.ee-sse ja panka sisselogimiseks kõlbab küll, kuigi allkirjastamist pole ma proovinud (näiteks ülekande tegemiseks).
Kindlasti võis midagi kahe silma vahele jääda, kuid suures osas peaks andmed paika pidama.
Intro
Ehk kuidas saada tööle panka sisselogimiseks vajalik ID-kaardi tarkvara Knoppixi 7.2 Live-CD-le, ja millised on selleks vajalikud .deb-paketid. Kuna Knoppix on Debiani-põhine, on artiklis väljatoodud pakettide arv minimaalne ja vaid antud Knoppixi-versiooni jaoks, kuid võib kasuks tulla ka teiste Debiani- kui ka mitte-Debiani-põhiste distrodega opereerimisel.Sissejuhatus
Niisiis tekkis mullegi lõpuks permanentne ID-kaardilugeja (OmniKey CardMan 1021) ja võib-olla ka võimalus seda kasutada, et sisse logida panka. Nimelt otsustas minu pank koodikaardi võimaluse (need, mis numbritega) ära kaotada. Ainult et mul on Windows XP, ning see pole ID-kaardi tarkvara poolt enam toetatud.Estobuntu plaadile keevitamine ei aidanud, sest selle versioon on samuti aegunud ja uut pole välja lastud. Kui seda reklaamitakse kui eestikeelset distrot, mis "toetab ID-kaarti", peaks see pidevalt kaasaegne olema.
Estobuntu põhineb Lubuntu 14.04-l, mis lasti välja 17.04.2014. Estobuntu DVD-tõmmise juures on kuupäev 02.05.2014.
Lisaks: Estobuntu 14.04 DVD Live-versiooni puhul sai värskeima Firefoxi installimisel miskipärast mäluruum otsa, sest minu masinal on vaid 1 Gb RAM-mälu (muutmälu). Kõvakettale ma tõmmise sisu ei salvestanud, sest kõvakettal on teine opsüsteem; seetõttu läks käiku vaid Live-variant, mille puhul kasutatakse ramdisk-i.
Seevastu Knoppix Live-CD puhul mälu kohese otsasaamise kartust gigabaidise RAM-mahuga pole. Etteruttavalt võib juba nentida, et Knoppixist oli kasu.
• Knoppix Live-CD (mitte DVD!) ja värske Firefoxi käitamiseks on vaja vähemalt 1 Gb RAM-mälu.Kaalukausile jäigi Knoppix 7.2 Live-CD, mis on Estobuntust vanemgi, aga ka viimane Knoppixi CD-versioon (24.06.2013. väljalase). Sellel on näiteks Firefoxil põhinev Iceweasel
• Estobuntu töötab rahuldavalt, kui arvutis on vähemalt 2 Gb RAM-mälu.
Iceweasel 21.0 ei toeta TLS turvaprotokolli versiooni 1.1 (järgmist) ja uuemaid. Toetatud on ainult TLS 1.0. See tähendab seda, et arvestatav osa turvatud https: veebisaite ei ole kättesaadavad, kuna: nad kasutavad TLS 1.1 protokolli, nad kasutavad TLS 1.2 protokolli, ning vähesed juba TLS 1.3 protokolli. Google, GMail ja Blogger töötavad, samuti DuckDuckGo otsing. YouTube ei tööta.Et Knoppix 7.2 on veidi üle aasta vanem kui Estobuntu, ning kuna Knoppix ei ole varustatud ID-kaardi kasutamise jaoks vajalike teekidega, tuleb Knoppixile peale panna terve posu pakette ja omakorda nendest sõltuvaid pakette. (Mitte, et Estobuntuga oleks vähem vaeva, aga Knoppix ei võta kõike mälu endale.)
19.11.2018. Üks hea uudis ka: Firefoxi ei pea eraldi all tõmbama, sest Iceweaseliga sai panka ilusti sisse. Allpool olev pakettide installimise kadalipp tuleb ikkagi läbida, misjärel Iceweaselis digiallkirjastamise mehhanism pangaülekane (PIN2) tegemiseks erinevalt allatõmmatud Firefoxist isegi kuidagimoodi eksisteerib, kuid ei tööta, ning ma kaldun arvama, et siin on tegemist lihtsalt vananenud lehitsejaga. Üks võimalik lahendus oleks installida Iceweaseli uuendus koos vajalike sõltuvustega ja siis võimaluse tekkides proovida, kas pangaülekande tegemine õnnestub.
• Knoppix 7.x versioonidel on probleeme Synaptics puutepatjadega, millest olen ma varem inglise keeles kirjutanud. Ajutine lahendus on kasutada välimist osutusseadet (USB-põhine hiir);
• Tähtsamad käsud Knoppix 6.x ja uuemate käitamiseks, sh. sõrmistiku keele valik ja kasutajakeskkonna välimus (samuti inglise keeles).
Paketid
Synaptic paketihaldurit ei soovita ma praegu üldse, sest pakettide vaikimisi aktiivseks seatud allikatega andmebaasi uuendamisel tuleb Firefoxi (või sellel põhineva Iceweaseli) uuendamist valides ette sisuliselt kogu opsüsteemi uuendamise protsess, sest välja vahetada tuleks liigagi suur arv pakette. Firefox koos vajalike lisadega tuleb installida eraldi, aga sellest jutu lõpupoole.Osad tarkvarapaketid on Knoppixil juba olemas; siin artiklis tõin välja vaid puuduvad või uuendatavad.
Valikupõhimõtted
Pakettide valikul osutus määravaks versiooniühilduvus, lähtudes printsiibist, et kui süsteemis on juba vajaliku paketi ühilduv versioon olemas, siis ei pea sellele uuendust tõmbama.Näiteks mida vanem Linuxi-distributsooni versioon, seda rohkem uuemaid ja puuduvaid pakette ja nende sõltuvusi (omakorda pakette) peab peale panema.
Sellest johtuvalt osutus valik vähemas osas Ubuntu 14.04 LTS Trusty Tahr (edaspidi Trusty) ja suuremas osas Debian 8 Jessie (25–26.04.2015) distrodele kompileeritud ühilduvatele pakettidele — põhimõttel, et mida vanemale distrole tehtud ühilduv pakett, seda vähem tuleks selle jaoks sõltuvusi tõmmata.
Kompromissi ei saanud teha konkreetselt ID-kaarti puudutavate pakettidega, nagu opensc jt., mis tähendas, et osa vajaliku versiooniga pakette on Debian 10 Buster-nimelisest kõige värskemast enam-vähem stabiilsest distro-versioonist.
Kui mõni muu ühilduv pakett oli vanemas distros olemas, langes valik selle kasuks.
Installimisjuhis ja versioonide kontrollimine
Esialgu on targem tõmmata individuaalseid pakette, jälgida nende sõltuvusi ja alles siis need vaid dpkg kaudu installida nii:$ sudo dpkg -i paketi_failinimi_koos_versioonigadpkg siis vastavalt annab teada, kas install õnnestus või mitte ja mis lisapaketti täiendavalt vaja on.
Ennetavalt on võimalik kasutada dpkg-query võimalust, et teada saada, millise paketi versioon installitud on:
dpkg-query -W paketi_nimi_suurversioonEsmapilgul vajalike teekide paketid (info sain siit) —
Tsitaat:
* openssl (1.1.0h) * libpcsclite1 (1.8.23) * pcsc-lite (1.8.23) * QT (5.9.4) (Miks küll?) — See muuseas jäigi installimata.Et hoida kokku vaba RAM-mälu, võib tarkvarapaketid tõmmata ja salvestada mitte tingimata Knoppixi Downloads või Desktop (töölaua) kataloogi, vaid kõvakettale või mälupulgale konkreetsesse kataloogi, mis tuleb ise luua.
Pakettide nimekirja loomine
Terminalis koostatud mittetäielik nimekiri tõmmatud pakettidest koos sõltuvustega, kõige varasemast kõige hilisemani:08:51 pcsc-lite-1.8.24.tar.bz2 — Selgus, et polnud vaja09:08 libsigsegv2_2.10-4+b1_i386.deb — Polnud ka vaja09:14 libpcsclite1_1.8.24-1_i386.deb 09:24 dpkg_1.17.5ubuntu5.8_i386.deb 09:37 libreadline7_7.0-3_i386.deb 09:42 libtinfo5_6.0+20161126-1+deb9u2_i386.deb 09:47 libssl1.1_1.1.0f-3+deb9u2_i386.deb 09:50 opensc-pkcs11_0.19.0-1_i386.deb 14:49 libglib2.0-0_2.40.2-0ubuntu1.1_i386.debKataloogis olevate failide ajaliselt sorteeritud järjekord
ls käsuga:Kui käsurea käsklus
ls -l näitab nimekirja failidest ja nende atribuutidest, siis -ltr parameetrid näitavad detailset nimekirja ajalises järjekorras vanimast uuemani ("modifitseeritud" ehk salvestamise aja järgi) —l — list — detailne nimekirit — time and date — kellaaeg ja kuupäevr — reverse order — "taguridi järjestus", ehk vanima salvestusajaga fail on kõige ülevalKuna ma aga tahtsin vaid kellaaega ja failinime, tuli käskluse väljund lasta toru abil ("piibu", i.k. pipe) läbi awk-i:
$ ls -ltr | awk '{print $8, $9}'print käseb trükkida, ning $8 ja $9 määravad vajalike veergude numbrid. Veerude number tuleb mõistatada ls -l käsuga tehtud nimekirjast. Koma veerunumbrite parameetrite vahel on tähtis. Ilma komata võib ka, aga siis ei tule kellaaja ja failinime või muude esemete vahele tühikut.Võib kasutada ka lihtsamat varianti
$ ls -tr— See koostab pakettide lihtsa nimekirja ajalises järjekorras vanimast salvestatust kõige uuemani suunaga ülevalt alla.
Pakettide asukohad ja nende installimine
Tuleb tähele panna, et antud Knoppix 7.2 on 32-bitine, ning pakettide tõmbamisel tuleb valida i386 arhitektuur. Arhitektuurinimetuse puudumisel on arhitektuuri asemel kirjasall (i.k. kõik).Vajadus on seega järgmiste pakettide järele (tabel on veel pooleli) —
| Link kirjeldusele | Link paketile | ||||||
| # | Pakett | Vajaminev versioon | Knoppix 7.2-s? | Paketi versoon | distro | distro ver. | Sõltuja |
|---|---|---|---|---|---|---|---|
| libpcsclite1 1.8.24-1 — paketis olev üks või enam faile sai pakendatud xz formaadis. Sellest ka vajadus uuema dpkg versiooni järele. Jäi meelde, et see dpkg versioon pidi olema just see konkreetne ja mitte mingi muu. Võimalik, et Ubuntu või Debiani ametlikel lehtedel olevad dpkg versioonid kas (veel) ei sisaldanud xz formaadi toetust, või olid pakettide sõltuvusversioonid liiga suured. | |||||||
| 1. | dpkg 1.17.5ubuntu5.8 | 1.17.5 | 1.16.10 | 1.17.5ubuntu5.8 | ubuntu | trusty | libpcsclite1 |
| 2. | libpcsclite1 1.8.24-1 | uusim | 1.8.8-3 | 1.8.24-1 | debian | buster | |
| * | opensc-pkcs11 0.19.0-1 | uusim | Puudub | 0.19.0-1 | debian | buster | |
| # | |||||||
* libglib2.0 >= 2.39.4 (Knoppix 7.2-s: libglib2.0-0:i386 2.36.3-1)
* libssl1.1 >= 1.1.0 (Knoppix: Puudub; on libssl1.0.0:i386 1.0.1e-2)
libglib2.0-0_2.40.2-0ubuntu1.1_i386.deb ubuntu trusty
4. Mingi hetk tekkis tahtmine tõmmata peale ka uusim opensc:
opensc (0.19.0-1) debian buster
Sõltuvused:
* libglib2.0-0 >= 2.16.0 — esmapilgul polnud vaja, aga siis opensclite1 (üleval) tahtis ikkagi uuemat.
* libreadline7 >= 6.0 (Knoppix: Puudub; kõige hiljutisem on libreadline6:i386 6.2+dfsg-0.1)
libreadline7_7.0-3_i386.deb debian stretch (i386)** Omakorda sõltuvus: libtinfo6 >= 6 (Knoppix: puudub; on libtinfo5:i386 5.9-10)
** libtinfo5_6.0+20161126-1+deb9u2_i386.deb debian stretch (i386)
* libssl1.1 >= 1.1.0 (Knoppix: puudub, on libssl1.0.0 1.0.1e-2)
libssl1.1_1.1.0f-3+deb9u2_i386.deb — ilmselt stretch; i386
* opensc-pkcs11 = 0.19.0-1 (Knoppix: puudub täielikult)
opensc-pkcs11_0.19.0-1_i386.deb debian buster i386
Edasi tuli installida opensc pakett:
opensc (0.19.0-1) buster i386 (Knoppix: Puudub täielikult)
Edasi: pcsd
pcscd (1.8.24-1) buster i386 (Knoppix: puudub täielikult)
aga sellel on õige mitu sõltuvust:
* libccid >= 1.4.1~ (Knoppix 7.2-s libccid justkui eksisteerib, aga uuendust sellele on ikka vaja)
libccid (1.4.18-1) jessie i386
* libsystemd0 (215-17+deb8u7) jessie i386 (Puudub täielikult)
Sõltuvused:
** libgcrypt20 (>= 1.6.1) 1.6.3-2+deb8u5 jessie dl (Knoppix: Antud versioon puudub, on libgcrypt11 1.5.0-5 )
Sõltuvused:
*** libgpg-error0 (>= 1.14), Knoppix 7.2-s 1.10-3.1 1.17.3
debian jessie i386
* libudev1 (>= 183) (Knoppixis puudub) 215-17+deb8u7 jessie i386
Kokku on pakette umbes kuue megabaidi jagu.
Firefoxi tõmbamine ja installimine
Nagu ülevalpool mainitud, siis eraldi Firefoxi tõmbamine ei ole tingimata kohustuslik. Seda kahel põhjusel:*Minu panka sai Iceweasel 21.0 lehitsejaga sisse logitud;
*Eraldi tõmmatud Firefox ei toeta PIN2 koodi mehhanismi üldse. Iceweaseliga oli ka võimatu PIN2 koodi kasutada, kuid peale esmaselt vajalike pakettide installimist esitatakse päring selle järele, kui katsetasin ülekande tegemist. Iceweaseli uuendamisel versioonile 38.0 erilist abi kahjuks ei olnud, kuid asja tasub veel uurida.
Mozilla "FTP"-sait sidaldaaab (jutumärkides, sest see on http) Mozilla Firefoxi ja teiste programmide kõiki versioonie. Postituse tegemise kuupäeval on uusima eestikeelse Firefoxi asukoht see:
https://ftp.mozilla.org/pub/firefox/releases/62.0.3/linux-i686/et/firefox-62.0.3.tar.bz2Kui Firefoxi pakitud fail on näiteks Iceweasel lehitsejaga salvestatud, avada faili kataloog pcmanfm failihalduris.
* firefox-62.0.3.tar.bz2 peale saab ühe korra peale klikkida, ja siis avaneb see XArchiver programmis.
* Alternatiiv on failile parema osutinupuga vajutada ja valida
firefox/ kataloogi.Firefoxi saab edasi käivitada terminalist:
$ cd /home/knoppix/firefoxMinna Firefoxi lahtipakitud kataloogi
$ ./firefox -P &*
-P avab Firefoxi profiilihalduri, sest Iceweasel ja Firefox kasutavad sama profiiliarhitektuuri. Seepärast on parem Firefoxis luua uus kasutajaprofiil.*
& tõstab graafilise programmi eraldi terminaliaknast.Kuna Firefoxi uuendatakse tihti, siis Mozilla "ftp"
releases kataloogis on kõige uuem versioon, aga mitte päris alguses. Otsida tuleb 62.0.3-st edasi.(Synapticut või muud paketihaldurit ära kasuta, sest see tõmbab kaasa liiga suure arvu muid pakette).
Alles siis tuleb Firefoxi laadida onepin moodul.
Firefoxi ingliskeelses variandis:
- Mine seadistustesse (about:preferences) >
- Privacy & Security (ülevaltpoolt paremalt) >
- alaosa Certificates (lehekülje kõige all) >
- nupp
[ Security Devices...] > - uuel aknal vajuta
[ Load... ] nupule > - tekkinud kastis kirjuta ülemisele reale
Module Name juurde mooduli nimi (mul on lihtsaltonepin) - Ning siis failikorjajast leia see fail:
/usr/lib/i386-linux-gnu/onepin-opensc-pkcs11.so
— opensc deb-faili järgi pistab dpkg programm onepin-mooduli installimisel sinna.
dpkg-põhise installiprotseduuri kõige lõppeks panin peale ka esteidfirefoxplugin_3.12.2.1145beta-1404_i386.deb paketi, mille tõmbasin Ubuntu Trustyle mõeldud RIA varamust.Küll panin Firefoxile peale Open-eID lehitsejalisa. Kätte saab selle Firefoxis aadressilt
Kas sellest ka mingit kasu oli, ei ole selge.
esteidpks11loader paketi unustasingi peale panna, aga tuleb välja, et ülejäänust ja allolevast piisas, et sisse logida.
Selle saab kätte samuti RIA poolt Ubuntu Trustyle koostatud varamust.
https://addons.mozilla.org/firefox/addon/open-eid/
Edasi tuleb Firefox sulgeda, alles siis kaart sisestada kaardilugejasse, ning lehitseja siis taaskäivitada.
Kui kaarti parasjagu enam vaja pole, siis sulgeda terve Firefox ja kaart lugejast välja võtta. Kui kaart on kaardilugejas ja lugeja indikaator vilgub, siis kaarti välja võtta ei maksa. (Kui lamp jääb pikaks ajaks vilkuma, siis tasuks proovida süsteemi kinnipanekut või restarti.)
Vähemalt eesti.ee-sse ja panka sisselogimiseks kõlbab küll, kuigi allkirjastamist pole ma proovinud (näiteks ülekande tegemiseks).
Subscribe to:
Posts (Atom)