Sender | Message | Time |
---|---|---|
29 Nov 2020 | ||
propensive | I'd be interested in having a security manager which a) always grants any permission it's asked for without question, but b) records those requests, and converts them to a set of commands that can be simply invoked in the shell to grant all the permissions. | 11:54:54 |
propensive | A further option would be an interactive security manager which asks the user if they want to grant each permission as it's run. | 11:56:31 |
propensive | If that sounds interesting, I'll open an issue and add some more details for you. | 12:01:16 |
GitHub#0000 removed their profile picture. | 14:43:11 | |
GitHub#0000 | [fury:issue/1586] 1 new commit
| 14:43:11 |
GitHub#0000 set a profile picture. | 14:58:52 | |
GitHub#0000 | [fury:issue/1586] 1 new commit
| 14:58:53 |
GitHub#0000 | [fury:issue/1585] 1 new commit
| 15:34:41 |
GitHub#0000 | [fury:main] 1 new commit
| 15:35:55 |
GitHub#0000 | [fury:main] 1 new commit
| 15:36:09 |
GitHub#0000 | [fury:main] 1 new commit
| 15:36:27 |
GitHub#0000 | [fury:issue/1559] 19 new commits
| 15:42:23 |
GitHub#0000 | [fury:issue/1559] 1 new commit
| 15:58:48 |
GitHub#0000 | [fury:issue/1559] 1 new commit
| 16:06:26 |
GitHub#0000 | [fury:main] 1 new commit
| 16:42:45 |
GitHub#0000 | [fury:issue/1589] 1 new commit
| 21:04:31 |
GitHub#0000 | [fury:issue/1589] 1 new commit
| 21:25:24 |
30 Nov 2020 | ||
GitHub#0000 | [fury:issue/1589] 2 new commits
| 00:29:54 |
GitHub#0000 | [fury:main] 1 new commit
| 00:40:41 |
GitHub#0000 | [fury:main] 1 new commit
| 00:41:28 |
GitHub#0000 | [fury:main] 1 new commit
| 00:41:37 |
jozinek#0918 | propensive I mean, you clearly want users to use your layer, so the library you are referencing will extract the used permissions and save them (into layer probably) and it is up to user of layer to decide which permission can/cannot be activated? | 10:59:28 |
propensive | jozinek Something like that. The idea is that an application module in a layer should define the permissions it needs, and as a separate step, the user of that layer can grant them (once they've looked at them). | 13:08:21 |
propensive | A layer is a bit like an Android app which declares the permissions it needs when it's published, and the user has to accept them before running it. | 13:09:17 |
propensive | I guess an Android app could also choose not to declare the permissions it needs, and would potentially fail with a runtime exception if it tries to use an API it's not entitled to (though I don't know about this). | 13:09:59 |
1 Dec 2020 | ||
GitHub#0000 removed their profile picture. | 10:08:52 | |
GitHub#0000 | [fury:issue/1569] 21 new commits
| 10:08:52 |
chuchulo joined the room. | 17:04:53 | |
chuchulo | * Hello Guys. I am trying to build the fury from main from github with jozinek and We are getting this error: Fetching layer propensive/guillotine@0 (XV5VjxPM) Fetching layer propensive/contextual@0 (dJxSATbo) Fetching layer propensive/kaleidoscope@0 (V6sZJmJC) Checking out src/main/java from repository java-multiaddr An error occurred while running: git -C /home/tom/.cache/fury/sources/EA0F270A11847496 fetch --all Fetching origin fatal: '/home/tom/.cache/fury/repos/t2CWKenbohXC7T4MCbPVlg' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. error: Could not fetch origin [make] Failed make: *** [Makefile:42: tmp/lib/fury.jar] Error 1 | 17:05:54 |
chuchulo set a profile picture. | 17:05:54 |