|
2018-05-13
, 00:06
|
|
Posts: 592 |
Thanked: 1,603 times |
Joined on Apr 2010
@ Berlin / Germany
|
#12
|
|
2018-05-13
, 16:26
|
Posts: 74 |
Thanked: 52 times |
Joined on Jul 2015
@ İstanbul
|
#13
|
|
2018-05-14
, 21:07
|
Posts: 74 |
Thanked: 52 times |
Joined on Jul 2015
@ İstanbul
|
#14
|
The Following 2 Users Say Thank You to Anatolian For This Useful Post: | ||
|
2018-05-15
, 09:53
|
Posts: 807 |
Thanked: 1,589 times |
Joined on Aug 2014
|
#15
|
The Following User Says Thank You to aspergerguy For This Useful Post: | ||
|
2018-05-15
, 16:58
|
Posts: 1,293 |
Thanked: 4,319 times |
Joined on Oct 2014
|
#16
|
Guys thank you all,
ı put the file to MyDocs and run this command: “ dpkg -i ( pathway) sample.deb"
it said: "signaturecheck failed"
And ı changed the time to 2013 and it installedç
So ı want to ask that what happen to aegis hack ?
So its still asking certificate time... Even the hack installed !
The Following 3 Users Say Thank You to nieldk For This Useful Post: | ||
|
2018-05-25
, 10:06
|
Posts: 74 |
Thanked: 52 times |
Joined on Jul 2015
@ İstanbul
|
#17
|
Thats really a known issue, and would be solvable, if developers could get a new certificate, which, oh well, not for quite some time possible.
It is the mechanism of security trust, and is working as intended.
bypass: set date to a time after certificate issue, and before certificate expiration.
usually, 2013 is a good "choice".
Tags |
debian archieve, installation, loadind policy |
Thread Tools | |
|
İf ı cant solve this ı will try to change main.bin version