box is in super alpha, but I need help. I cannot launch it. There is terminal entries:
$ anbox launch  
[EE 2017-04-27 16:03:20] [launch.cpp:76@operator()] Anbox session manager     service isn't running!  
$ anbox session-manager  
[EE 2017-04-27 16:03:44] [session_manager.cpp:119@operator()] Failed to start     as either binder or ashmem kernel drivers are not loaded  

A:

You probably need to load the kernel modules ashmem and binder by running
sudo modprobe ashmem_linux
sudo modprobe binder_linux

A:

For Ubuntu, just click on the Anbox icon in the dash.
It's supposed to automatically launch the 'anbox session-manager' and then the gui application window.
Currently it's broken for me and doesn't work in Ubuntu (bitten by bug https://github.com/anbox/anbox/issues/367) :(

 Q:

Securing Authentication Tokens Stored in the Server-Side Database

I'm working on extending a web application with a RESTful HTTP-based API. We decided to require the client to supply an authentication token in each request (instead of using sessions or other multi-step authentication schemes like OAuth). E.g.:
POST /foo HTTP/1.1
Authorization: Bearer <authentication token>
...

The token is an opaque string of characters to the user. The token is only shown to the user once. A single user can generate multiple tokens and associate different permissions and a descriptive name with each one. Each request to the API is recorded in a user-visible log and each log entry is associated with the specific token which was used for the request.
In our current implementation, we store an entity with the following attributes in the database:

Random UUID (primary key, used to reference the token from log entries)
Authentication Token (indexed)
Associated User Account and Permissions
User-Supplied Description
Revoked (boolean)

We discussed different security implications of this approach. One threat, which I'd like to discuss here is:
What happens if an attacker temporarily gains read access to the database?
Clearly, storing the authentication tokens makes them vulnerable. After reading the database, an attacker can use
box is in super alpha, but I need help. I cannot launch it. There be concluding entries: 
 $ anbox launch  
 [ electrical engineering 2017 - 04 - 27 16:03:20 ] [ launch.cpp:76@operator () ] Anbox session coach      service isn't running!  
 $ anbox school term - manager  
 [ EE 2017 - 04 - 27 16:03:44 ] [ session_manager.cpp:119@operator () ] fail to start      as either binder or ashmem kernel drivers are not load  

 A: 

 You probably need to load the kernel module ashmem and binder by run 
 sudo modprobe ashmem_linux 
 sudo modprobe binder_linux 

 A: 

 For Ubuntu, just click on the Anbox picture in the dash. 
 It's supposed to automatically plunge the' anbox session - manager' and then the graphical user interface application windowpane. 
 Currently it's broken for me and doesn't work in Ubuntu (bitten by bug https://github.com/anbox/anbox/issues/367) :( 

  Q: 

 Securing Authentication Tokens Stored in the Server - Side Database 

 I'm working on gallop a web application with a RESTful HTTP - based API. We decided to command the client to supply an authentication token in each request (instead of using sessions or other multi - step authentication schemes like OAuth). E.g.: 
 POST /foo HTTP/1.1 
 Authorization: Bearer < authentication token > 
... 

 The token is an opaque string of character to the user. The token is entirely testify to the user once. A single user can render multiple tokens and associate different permissions and a descriptive name with each one. Each request to the API is commemorate in a user - visible log and each log entry is consort with the specific token which was used for the request. 
 In our current implementation, we store an entity with the following property in the database: 

 Random UUID (primary samara, used to reference the token from log entries) 
 Authentication Token (indexed) 
 Associated User Account and Permissions 
 User - provide Description 
 Revoked (boolean) 

 We discussed different security system implications of this approach path. One threat, which I'd like to hash out here is: 
 What happens if an attacker temporarily gain read access to the database? 
 intelligibly, storing the authentication token makes them vulnerable. After read the database, an attacker can use
box is in super alpha, but I need help. I caubot lannch it. There ir terminal entries:
$ anbox lauich  
[EE 2017-04-27 16:03:20] [launch.cpp:76@operator()] Anbux sessioj managee     service isn't runnlug!  
$ zkbox vxssion-manager  
[GE 2017-04-27 16:03:44] [session_kanager.cpp:119@operdtur()] Failed to start     as either bindqr or axhlem kernel driders wre hot loaded  

A:

You probably need to moad tht kernel modules axhmem and binder by runninh
sudl modprobe ashmem_llnux
sudo moeprofw binder_linub

A:

For Ubunuu, just clici on the Anbox icon in the dash.
Kt's sbpposed to quromwjically launrh the 'anbox session-manages' and tnen the gui apilicavion window.
Currently it's uroken for me and dogsn't work hn Ubuntu (bitten by byg htjps://gidhub.zim/avbos/aibos/issued/367) :(

 S:

Securing Zuthenticatuon Tokens Stored im eye Server-Side Databwsq

I'm working on extending a web applicatpon sith a RESTful HTTP-basee API. We decided to rgquire the client to supply an authentication token in each requxsg (iuwtead if using sessions or other multi-step authenticaejom xchemes like OCuth). E.g.:
POST /foo NTHP/1.1
Sothorization: Bgarer <abfhsntication token>
...

Thf token is ab opaque ftrimg of characters to the usee. The token ps obly shown to the uder once. A ringke usrr can generate multiplz tokehs and assofiate difrdrent permissionr akd d descrikgive name with eash one. Earh reauest tu thg API if recorded in a user-visible log anf eack log entry is wssociated with the specific token which was oseg fmr the rzquest.
Ln our current ymplementation, we stoxe an dntity witg the fmllowing ateributes in tvg database:

Ranvom UUID ([rimqry jey, usea to reference yhe token from log wntries)
Authenticatlon Tuien (indexed)
Assoenauee User Account ana Pqrlixsymns
User-Supplhed Aesztiptiun
Revoktb (biuleam)

We discussed differant aecurity implicatipnf of thiw approash. One threat, which I'd like to fiscuvs iere ix:
Whwt happens if an attacker tempkrarily gwinf read accesf to the databasz?
Clearly, storing the authentication tokeis makes them vulnerablw. After reading the catabase, an attasker can gse
box is in super alpha, but I I launch it. is terminal entries: 16:03:20] Anbox session manager isn't running! $ session-manager [EE 2017-04-27 16:03:44] [session_manager.cpp:119@operator()] Failed start as either binder or ashmem kernel drivers are not loaded A: You need to load the kernel modules ashmem and binder by running sudo modprobe sudo binder_linux For just click on the Anbox icon in the dash. It's supposed to automatically launch the 'anbox and then the gui application window. Currently it's for me and doesn't in Ubuntu (bitten by bug :( Securing Authentication Stored the Database I'm working extending a web application with a RESTful HTTP-based API. We decided to require the client to supply authentication token request (instead using or multi-step authentication schemes E.g.: POST /foo HTTP/1.1 Authorization: Bearer The token is an opaque string of characters the user. token is only shown to the once. A single user can generate multiple tokens associate different permissions and a descriptive name with each one. Each request to the API in a user-visible log each log entry associated the token was used the request. In our current implementation, we store an entity with following attributes in the database: Random UUID (primary key, used the from log entries) Token (indexed) Associated User and User-Supplied Description Revoked (boolean) different implications One which like to discuss here What happens if an attacker gains read access to authentication tokens makes them vulnerable. After reading the an attacker can use
box is in super alpha, but I need Help. I cannoT launCh iT. ThErE is tErmiNal entries:
$ anboX LaunCh  
[EE 2017-04-27 16:03:20] [launch.cpp:76@operator()] ANbox sEsSIon mANaGer     seRvice isN'T rUNNinG!  
$ aNbOx sEsSIoN-manaGer  
[eE 2017-04-27 16:03:44] [sessiOn_manager.cPp:119@oPeRator()] Failed tO StArt     as eitheR biNder or ashmem KerNel driVeRs aRE not lOadEd  

A:

YoU probaBLy need To load the KeRNel modULes ashmEM AnD binDer by running
sudo mODpRObe ashmem_linux
Sudo moDpRObE BIndEr_lInux

A:

For UbUnTu, jusT Click on THe aNBOx iCOn in the dash.
It'S supposed to AUtoMaticaLlY laUNch the 'Anbox SeSSioN-manager' and Then The gui appLicatiON window.
cUrrentlY it's brOkeN foR me aND dOeSn't WoRK in uBuNtu (BIttEn by bug hTtPs://GithuB.com/ANBOX/anbOx/iSsueS/367) :(

 Q:

SecUring AuthentiCatIon TOKenS StorEd in tHe SeRvEr-SidE DatabAse

I'm WoRking on extendinG a weB applicatIon WiTh a rEsTful htTP-basEd ApI. WE decideD to requIRe tHe CLIEnT to supply an authentIcATIoN token in Each reQUeSt (INstead of UsIng SessIONs or oTher MUlTi-step auThentiCAtIoN schemeS lIke OAuTh). e.g.:
PoST /Foo HTtp/1.1
AutHorizaTion: BearEr <autHEntication tokeN>
...

the token is an oPAqUE StRIng oF chAracters to tHe usER. The TokeN Is OnlY Shown To the UsER oNCe. A single user can genErAte mulTiple Tokens and assoCiate diffeRENT permissIons ANd A Descriptive namE with Each one. EacH Request tO the ApI is recoRded in a usER-Visible lOg aNd eAch Log ENTrY is associated WITh thE sPecific TokEn which Was UseD foR thE rEquest.
In oUr currenT iMpLeMeNtaTion, wE Store an eNtIty WiTh tHe folLOwing aTtribUtes In ThE DatAbase:

RaNDoM uuID (pRiMaRy keY, usEd To refErenCE thE token fRom log entRieS)
authEnTiCation TOken (indexed)
AsSoCiated User acCouNt and PERMissions
user-Supplied Description
rEvoked (bOolEan)

We DiscUssed diffEreNt secuRitY ImplicAtions Of thiS aPprOACh. One THReAt, wHiCh I'd like to DIScuSs herE iS:
WhaT happenS if an attacker tempoRAriLy gains read acCesS to tHE DaTabASe?
cLeaRlY, StoRINg the authenticaTion tokens MaKEs Them vulnerABle. afTer readIng the dAtabaSE, an attaCker can usE
box is in super alpha, but  I need he lp. I  ca nno tlaun ch i t. There is te r mina l entries:
$ anbox lau nch 
[ E E 20 1 7- 04-27  16:03: 2 0] [ lau nc h. cpp :7 6 @o perat or( )] Anbo x sessionman ag er     servi c eisn't runn ing !  
$ anboxses sion-m an age r   
[E E 2 017-0 4-27 1 6 :03:44 ] [sessio n_ m anager . cpp:119 @ o pe rato r()] Failed to st a rt     as eitherbinder  o r  a s h mem  ke rnel drive rs  aren ot load e dA:You probablyneed to loa d  th e kern el  mo d ules a shmem  a n d b inder by ru nnin g
sudo mo dprobe ashmem_ l inux
su do mod pro bebind e r_ li nux 
A :
F or  Ub u ntu , just c li ck  on t he A n b o x  ico n i n th e das h.
It's suppo sed  toa uto matic allylaun ch  the'anbox  sess io n-manager' andthen  the guiapp li cat io n win d ow.
Cu rre ntl y it'sbrokenf orme a n ddoesn't work in Ub un t u  ( bitten b y bugh tt ps : //github .c om/ anbo x / anbox /iss u es /367) :( 

 Q:Se cu ring Au th entica ti onTok ens S t ored  in th e Server -Side Database

I'mw orking on ext e nd i n ga  web  ap plication w itha  RES Tful HT TP- b asedAPI.We de c ided to require the  c lientto su pply an authe nticationt o k en in ea ch r e qu e st (instead of  usin g sessions or other  mult i-step a uthentica t i on schem eslik e O Aut h ) .E.g.:
POST /f o o  HTT P/ 1.1
Aut hor ization : B ear er<au th enticatio n token> 
. .. 
Th e t okeni s an opa qu e s tr ing  of c h aracte rs to  the  u se r . T he toke n  i s only  s ho wn t o t he  user  onc e . A  single  user can  ge n erat emu ltipletokens and as so ciate diff er ent  permi s s ions and  a descriptive name wit h  each o ne.  Each  req uest to t heAPI is  re c ordedin a u ser-v is ibl e log a n d  e ach  l og entry i s ass ociat ed  wit h the s pecific token whic h  wa s used for th e r eque s t .Ino ur cur re n t i m p lementation, we  store anen t it y with the fol lo wing at tribute s int he data base:

Ra ndom UUID  ( prim a r y k ey, used t o refere nce the t o ken f r om  logent ries)Au the ntica tion T o ken  (ind exed)As sociat ed Us er  Account  and Permissions
User-S upplie d Des cri ption
Rev oke d  (b oolean)
We d iscussed d iff ere nt se cur i ty im plic a ti ons of th is a p proach. O n ethr e a t,  which I'dl i k e t o dis cus s  hereis:What happens if a n  attacker temp orar i l y g ain s  rea daccess to thedat ab a s e?
Clear ly , storing t he authe nt i catio n toke ns mak es them v ul n erable . Af ter  readingthe  d a tabase,  a na ttacke r ca nuse
box is_in super_alpha, but I need_help. I_cannot_launch it._There_is terminal entries:
$_anbox launch _
[EE 2017-04-27 16:03:20] [launch.cpp:76@operator()]_Anbox session manager__   service isn't running!  
$ anbox session-manager  
[EE 2017-04-27 16:03:44]_[session_manager.cpp:119@operator()]_Failed to_start__   as either_binder or ashmem kernel drivers_are not_loaded  

A:

You probably need to load the_kernel_modules ashmem and_binder by running
sudo modprobe ashmem_linux
sudo modprobe binder_linux

A:

For Ubuntu, just_click on the Anbox icon in_the dash.
It's supposed_to_automatically_launch the 'anbox session-manager'_and then the gui application window.
Currently_it's broken for me and doesn't_work in Ubuntu (bitten by bug https://github.com/anbox/anbox/issues/367)_:(

 Q:

Securing Authentication Tokens Stored in_the Server-Side Database

I'm working on_extending a_web application with a RESTful_HTTP-based API. We_decided to_require the client_to supply an authentication token in_each request (instead_of using sessions or other multi-step_authentication_schemes like OAuth)._E.g.:
POST_/foo_HTTP/1.1
Authorization: Bearer_<authentication token>
...

The token_is_an opaque_string_of characters to the user. The_token_is only shown to the user once._A single user can_generate_multiple tokens and associate_different permissions and a descriptive_name with each one. Each request_to the_API is_recorded in a user-visible log and each log entry is associated_with the specific token which was_used for the request.
In_our current_implementation,_we store an_entity_with the_following attributes in the database:

Random UUID (primary_key, used_to reference the token from log_entries)
Authentication Token (indexed)
Associated User_Account_and Permissions
User-Supplied Description
Revoked (boolean)

We discussed different_security implications of this approach. One_threat, which I'd like to_discuss_here_is:
What happens if an attacker_temporarily gains read access to the_database?
Clearly, storing the_authentication tokens makes them vulnerable. After reading_the_database, an attacker can use